locked
BSOD at system shut down with automatic restart. RRS feed

  • Question

  • Hi all,

    After upgrading from Windows7 to Windows 10 (which went OK) I can no longer shut down my PC.  During the shutdown process, I get a BSOD with a KMODE_EXCEPTION_NOT_HANDLED message (without further details), after which the PC automatically restarts.  The same thing happens when I try to put my PC in sleep mode. 

    After reading some postings on the internet relating to similar problems, I checked my drivers and upgraded the display drivers from the NVIDIA site.

    Here's a link to my system configuration and a minidump:

    https://onedrive.live.com/redir?resid=2471B54652D68D12!4820&authkey=!AJidOeNGTWRQms4&ithint=folder%2cdmp

    Hope someone can help me with this: I am tired of pulling the plug on my PC everytime I want to switch it off ;(.

    Tuesday, August 18, 2015 3:10 PM

Answers

  • This was Related to AppleCharger from GIGA-BYTE TECHNOLOGY CO., LTD.  I would simpy remove it  (yours is from 2010)

    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\081715-15656-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 10 Kernel Version 10240 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10240.16393.amd64fre.th1_st1.150717-1719
    Machine Name:
    Kernel base = 0xfffff800`3c408000 PsLoadedModuleList = 0xfffff800`3c72d030
    Debug session time: Mon Aug 17 05:13:38.081 2015 (UTC - 4:00)
    System Uptime: 0 days 0:38:43.748
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff8003c49a892, 0, 4e}
    
    *** WARNING: Unable to verify timestamp for AppleCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
    Probably caused by : AppleCharger.sys ( AppleCharger+270c )
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8003c49a892, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 000000000000004e, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    BIOS_DATE:  03/21/2012
    
    BASEBOARD_PRODUCT:  PH67A-UD3-B3
    
    BASEBOARD_VERSION:  x.x
    
    BUGCHECK_P1: ffffffffc0000005
    
    BUGCHECK_P2: fffff8003c49a892
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 4e
    
    READ_ADDRESS: fffff8003c7cc500: Unable to get MiVisibleState
     000000000000004e 
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    FAULTING_IP: 
    nt!IopBuildDeviceIoControlRequest+32
    fffff800`3c49a892 0fb6524c        movzx   edx,byte ptr [rdx+4Ch]
    
    EXCEPTION_PARAMETER2:  000000000000004e
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CPU_COUNT: 4
    
    CPU_MHZ: ce0
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  wininit.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    TRAP_FRAME:  ffffd00164fc22a0 -- (.trap 0xffffd00164fc22a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc0009ea7d470 rbx=0000000000000000 rcx=0000000000220448
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8003c49a892 rsp=ffffd00164fc2430 rbp=000000000000016d
     r8=0000000000000000  r9=fffff8013f38270c r10=00000000656e6f4e
    r11=ffffd00164fc24e8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!IopBuildDeviceIoControlRequest+0x32:
    fffff800`3c49a892 0fb6524c        movzx   edx,byte ptr [rdx+4Ch] ds:00000000`0000004e=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8003c58f8c2 to fffff8003c555220
    
    STACK_TEXT:  
    ffffd001`64fc19d8 fffff800`3c58f8c2 : 00000000`0000001e ffffffff`c0000005 fffff800`3c49a892 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`64fc19e0 fffff800`3c55fc82 : fffff800`3c74ea80 00000000`00000000 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2bac2
    ffffd001`64fc20c0 fffff800`3c55e3a2 : fffff800`3c74f080 ffffe001`36f05ef8 00000000`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
    ffffd001`64fc22a0 fffff800`3c49a892 : 8000ffff`fffff97b 00000000`cf7a0000 00000000`000007ff ffffe001`362ec000 : nt!KiPageFault+0x222
    ffffd001`64fc2430 fffff800`3c49a853 : ffffc000`9ea7d470 00000000`00000000 ffffc000`9ea7d470 00000000`00000001 : nt!IopBuildDeviceIoControlRequest+0x32
    ffffd001`64fc2490 fffff801`3f38270c : fffff800`0000074d 00000000`0000016d 00000000`0000016d fffff800`00000000 : nt!IoBuildDeviceIoControlRequest+0x4f
    ffffd001`64fc24f0 fffff800`0000074d : 00000000`0000016d 00000000`0000016d fffff800`00000000 ffffc000`9ea7d470 : AppleCharger+0x270c
    ffffd001`64fc24f8 00000000`0000016d : 00000000`0000016d fffff800`00000000 ffffc000`9ea7d470 ffffa2e2`0000016d : 0xfffff800`0000074d
    ffffd001`64fc2500 00000000`0000016d : fffff800`00000000 ffffc000`9ea7d470 ffffa2e2`0000016d 00000000`00000000 : 0x16d
    ffffd001`64fc2508 fffff800`00000000 : ffffc000`9ea7d470 ffffa2e2`0000016d 00000000`00000000 ffffd001`64fc2550 : 0x16d
    ffffd001`64fc2510 ffffc000`9ea7d470 : ffffa2e2`0000016d 00000000`00000000 ffffd001`64fc2550 ffffd001`64fc2540 : 0xfffff800`00000000
    ffffd001`64fc2518 ffffa2e2`0000016d : 00000000`00000000 ffffd001`64fc2550 ffffd001`64fc2540 00000000`00000001 : 0xffffc000`9ea7d470
    ffffd001`64fc2520 00000000`00000000 : ffffd001`64fc2550 ffffd001`64fc2540 00000000`00000001 00000000`00000000 : 0xffffa2e2`0000016d
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    AppleCharger+270c
    fffff801`3f38270c ??              ???
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  AppleCharger+270c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AppleCharger
    
    IMAGE_NAME:  AppleCharger.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bd65fdd
    
    BUCKET_ID_FUNC_OFFSET:  270c
    
    FAILURE_BUCKET_ID:  0x1E_c0000005_R_AppleCharger!Unknown_Function
    
    BUCKET_ID:  0x1E_c0000005_R_AppleCharger!Unknown_Function
    
    PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_AppleCharger!Unknown_Function
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_applecharger!unknown_function
    
    FAILURE_ID_HASH:  {fb99847c-8868-32be-391c-0a3180598ea8}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm AppleCharger
    Browse full module list
    start             end                 module name
    fffff801`3f380000 fffff801`3f388000   AppleCharger T (no symbols)           
        Loaded symbol image file: AppleCharger.sys
        Image path: \SystemRoot\system32\DRIVERS\AppleCharger.sys
        Image name: AppleCharger.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Apr 26 23:54:05 2010 (4BD65FDD)
        CheckSum:         000093A3
        ImageSize:        00008000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Michael_LS Wednesday, August 19, 2015 6:40 AM
    • Marked as answer by Michael_LS Friday, August 21, 2015 5:27 AM
    Tuesday, August 18, 2015 4:33 PM

All replies

  • This was Related to AppleCharger from GIGA-BYTE TECHNOLOGY CO., LTD.  I would simpy remove it  (yours is from 2010)

    Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\081715-15656-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers.
    Windows 10 Kernel Version 10240 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10240.16393.amd64fre.th1_st1.150717-1719
    Machine Name:
    Kernel base = 0xfffff800`3c408000 PsLoadedModuleList = 0xfffff800`3c72d030
    Debug session time: Mon Aug 17 05:13:38.081 2015 (UTC - 4:00)
    System Uptime: 0 days 0:38:43.748
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................................
    Loading User Symbols
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff8003c49a892, 0, 4e}
    
    *** WARNING: Unable to verify timestamp for AppleCharger.sys
    *** ERROR: Module load completed but symbols could not be loaded for AppleCharger.sys
    Probably caused by : AppleCharger.sys ( AppleCharger+270c )
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8003c49a892, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 000000000000004e, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    BIOS_DATE:  03/21/2012
    
    BASEBOARD_PRODUCT:  PH67A-UD3-B3
    
    BASEBOARD_VERSION:  x.x
    
    BUGCHECK_P1: ffffffffc0000005
    
    BUGCHECK_P2: fffff8003c49a892
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 4e
    
    READ_ADDRESS: fffff8003c7cc500: Unable to get MiVisibleState
     000000000000004e 
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    
    FAULTING_IP: 
    nt!IopBuildDeviceIoControlRequest+32
    fffff800`3c49a892 0fb6524c        movzx   edx,byte ptr [rdx+4Ch]
    
    EXCEPTION_PARAMETER2:  000000000000004e
    
    BUGCHECK_STR:  0x1E_c0000005_R
    
    CPU_COUNT: 4
    
    CPU_MHZ: ce0
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 2a
    
    CPU_STEPPING: 7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  wininit.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10240.9 amd64fre
    
    TRAP_FRAME:  ffffd00164fc22a0 -- (.trap 0xffffd00164fc22a0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffc0009ea7d470 rbx=0000000000000000 rcx=0000000000220448
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8003c49a892 rsp=ffffd00164fc2430 rbp=000000000000016d
     r8=0000000000000000  r9=fffff8013f38270c r10=00000000656e6f4e
    r11=ffffd00164fc24e8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    nt!IopBuildDeviceIoControlRequest+0x32:
    fffff800`3c49a892 0fb6524c        movzx   edx,byte ptr [rdx+4Ch] ds:00000000`0000004e=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8003c58f8c2 to fffff8003c555220
    
    STACK_TEXT:  
    ffffd001`64fc19d8 fffff800`3c58f8c2 : 00000000`0000001e ffffffff`c0000005 fffff800`3c49a892 00000000`00000000 : nt!KeBugCheckEx
    ffffd001`64fc19e0 fffff800`3c55fc82 : fffff800`3c74ea80 00000000`00000000 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x2bac2
    ffffd001`64fc20c0 fffff800`3c55e3a2 : fffff800`3c74f080 ffffe001`36f05ef8 00000000`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
    ffffd001`64fc22a0 fffff800`3c49a892 : 8000ffff`fffff97b 00000000`cf7a0000 00000000`000007ff ffffe001`362ec000 : nt!KiPageFault+0x222
    ffffd001`64fc2430 fffff800`3c49a853 : ffffc000`9ea7d470 00000000`00000000 ffffc000`9ea7d470 00000000`00000001 : nt!IopBuildDeviceIoControlRequest+0x32
    ffffd001`64fc2490 fffff801`3f38270c : fffff800`0000074d 00000000`0000016d 00000000`0000016d fffff800`00000000 : nt!IoBuildDeviceIoControlRequest+0x4f
    ffffd001`64fc24f0 fffff800`0000074d : 00000000`0000016d 00000000`0000016d fffff800`00000000 ffffc000`9ea7d470 : AppleCharger+0x270c
    ffffd001`64fc24f8 00000000`0000016d : 00000000`0000016d fffff800`00000000 ffffc000`9ea7d470 ffffa2e2`0000016d : 0xfffff800`0000074d
    ffffd001`64fc2500 00000000`0000016d : fffff800`00000000 ffffc000`9ea7d470 ffffa2e2`0000016d 00000000`00000000 : 0x16d
    ffffd001`64fc2508 fffff800`00000000 : ffffc000`9ea7d470 ffffa2e2`0000016d 00000000`00000000 ffffd001`64fc2550 : 0x16d
    ffffd001`64fc2510 ffffc000`9ea7d470 : ffffa2e2`0000016d 00000000`00000000 ffffd001`64fc2550 ffffd001`64fc2540 : 0xfffff800`00000000
    ffffd001`64fc2518 ffffa2e2`0000016d : 00000000`00000000 ffffd001`64fc2550 ffffd001`64fc2540 00000000`00000001 : 0xffffc000`9ea7d470
    ffffd001`64fc2520 00000000`00000000 : ffffd001`64fc2550 ffffd001`64fc2540 00000000`00000001 00000000`00000000 : 0xffffa2e2`0000016d
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    AppleCharger+270c
    fffff801`3f38270c ??              ???
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  AppleCharger+270c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AppleCharger
    
    IMAGE_NAME:  AppleCharger.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bd65fdd
    
    BUCKET_ID_FUNC_OFFSET:  270c
    
    FAILURE_BUCKET_ID:  0x1E_c0000005_R_AppleCharger!Unknown_Function
    
    BUCKET_ID:  0x1E_c0000005_R_AppleCharger!Unknown_Function
    
    PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_AppleCharger!Unknown_Function
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_applecharger!unknown_function
    
    FAILURE_ID_HASH:  {fb99847c-8868-32be-391c-0a3180598ea8}
    
    Followup:     MachineOwner
    ---------
    
    0: kd> lmvm AppleCharger
    Browse full module list
    start             end                 module name
    fffff801`3f380000 fffff801`3f388000   AppleCharger T (no symbols)           
        Loaded symbol image file: AppleCharger.sys
        Image path: \SystemRoot\system32\DRIVERS\AppleCharger.sys
        Image name: AppleCharger.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Apr 26 23:54:05 2010 (4BD65FDD)
        CheckSum:         000093A3
        ImageSize:        00008000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Michael_LS Wednesday, August 19, 2015 6:40 AM
    • Marked as answer by Michael_LS Friday, August 21, 2015 5:27 AM
    Tuesday, August 18, 2015 4:33 PM
  • Thank you very much for your reply.  

    In short: my computer now works as it should (at least for now).

    Longer version: this utility (AppleCharger) from Gigabyte came with a bunch of other utilities that all broke down with the upgrade to Windows 10.  When I asked Gigabyte's tech support for help on how to remedy this, their reply was:

    "This MB not supports Windows 10, because we do not have the driver of this MB about windows 10.
    Maybe you can try test it with the Win 8.1 drivers, but I am not sure about that.
    If there is still problem, you should back to Win 8.1 or win 7."

    I managed to uninstall most of the utilities, and the computer stopped crashing, and shuts down normally.

    Again thank you very much.



    This MB not supports Windows 10, because we do not have the driver of this MB about windows 10.
    Maybe you can try test it with the Win 8.1 drivers, but I am not sure about that.
    If there is still problem, you should back to Win 8.1 or win 7.
    This MB not supports Windows 10, because we do not have the driver of this MB about windows 10.
    Maybe you can try test it with the Win 8.1 drivers, but I am not sure about that.
    If there is still problem, you should back to Win 8.1 or win 7.
    Wednesday, August 19, 2015 7:08 PM
  • LM

    Most computer makers bloatware can be removed without issue but if some is necessary you should try installing it in compatibility mode

    To install in compatibility mode do the following:

    Right click the installer>properties>compatibility>choose OS

    http://windows.microsoft.com/en-US/windows-vista/Make-older-programs-run-in-this-version-of-Windows?SignedIn=1
    (works in  win 7, win 8, and win 10)


    Wanikiya and Dyami--Team Zigzag

    Wednesday, August 19, 2015 9:45 PM