BSOD when shutting down after long hours usage


  1. Posts : 5
    Windows 10 Pro x64
       #1

    BSOD when shutting down after long hours usage


    Hi guys. I am running Windows 10 Pro. My computer had BSOD quite frequently these few days. It's kind of weird. I was unable to replicate the problem if I just use it for like 1-2 hours. If I use it for a little longer, BSOD will occur when I am trying to shut down. There were no problems at all when I am using it. It is not interrupting my usage but it is really annoying to see BSOD every time whenever I am shutting down. Please find my zipped log file attached.

    Attachment 58291

    Any help would be appreciated. Thank you in advance. :)
      My Computer


  2. Posts : 14,897
    Windows 10 Pro
       #2

    Hi joelting92,

    Welcome to the 10forums.

    Are you aware of this kind system wake events?
    These appear about 50 times in the event logs.
    Code:
    Event[6397]:  Log Name: System
      Source: Microsoft-Windows-Power-Troubleshooter
      Date: 2016-01-11T23:16:13.912
      Event ID: 1
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: NT AUTHORITY\LOCAL SERVICE
      Computer: DESKTOP-HBTEASR
      Description: 
    The system has returned from a low power state.
    
    
    Sleep Time: ?2016?-?01?-?11T15:11:30.353860500Z
    Wake Time: ?2016?-?01?-?11T15:16:11.932193800Z
    
    
    Wake Source: Unknown

    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Attachment 58345
      My Computers


  3. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #3

    Hi axe0,

    Thanks for the reply. I will try and do a clean install for nvidia and report whether it eliminates BSOD.
    As for the system wake event, I am not aware of it. What is it actually and usually what triggers it?

    I did not put my computer into sleep during that period and had never run it in power saving mode as well.
      My Computer


  4. Posts : 14,897
    Windows 10 Pro
       #4

    Do you frequently need to plug in the adapter?
      My Computers


  5. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #5

    axe0 said:
    Do you frequently need to plug in the adapter?
    Yes, I did plug in the adapter like all the time if I have access to electrical plugs because it ensures maximum performance for my laptop. Is the action of plugging in adapter at all times causing problems? After performing a clean install for my laptop, BSOD still occurs during the shutting down phase. I will attach my updated log files when I reach home after job today.

    Thanks for your time @axe0
      My Computer


  6. Posts : 14,897
    Windows 10 Pro
       #6

    I mean more like, do you plug in the adapter frequently when your laptop has a few % battery left? No, I don't think it is causing bluescreens, but I think it would explain the event logs I posted earlier.
      My Computers


  7. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #7

    axe0 said:
    I mean more like, do you plug in the adapter frequently when your laptop has a few % battery left? No, I don't think it is causing bluescreens, but I think it would explain the event logs I posted earlier.
    Nope. I allow my laptop to be fully charged the whole time. But it did have smart charging, like it will not charge between 95%-100%. By the way, please find my latest log file attached.

    It crashed the moment my laptop start shutting down.

    Attachment 58631
      My Computer


  8. Posts : 654
    windows 10 Pro
       #8

    All the dumpfiles are:
    Code:
     *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 139, {3, ffffd00023278260, ffffd000232781b8, 0}
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllDeviceState+1cb )
    Followup: MachineOwner
    ---------
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00023278260, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd000232781b8, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    Debugging Details:
    ------------------
    
    TRAP_FRAME:  ffffd00023278260 -- (.trap 0xffffd00023278260)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe00188402260 rbx=0000000000000000 rcx=0000000000000003
    rdx=ffffe001884023c0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f4d6ad82 rsp=ffffd000232783f0 rbp=ffffd000232784f9
     r8=ffffc001f5caba20  r9=0000000000000003 r10=7fffc001f5caba20
    r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt! ?? ::FNODOBFM::`string'+0x8c82:
    fffff803`f4d6ad82 cd29            int     29h
    Resetting default scope
    EXCEPTION_RECORD:  ffffd000232781b8 -- (.exr 0xffffd000232781b8)
    ExceptionAddress: fffff803f4d6ad82 (nt! ?? ::FNODOBFM::`string'+0x0000000000008c82)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    BUGCHECK_STR:  0x139
    PROCESS_NAME:  jusched.exe
    CURRENT_IRQL:  2
    In the dumpfiles every time is processname jusched.exe mentioned.
    The jusched.exe is the Java Update Scheduler.
    Search for it if it is in C:\Windows it could be malware or a virus.
    I suspect this preventing windows to shut down properly and causes the BSOD.
    Remove Java from your system or if you need Java disable the java update scheduler.
    For more info http://www.computertechtips.net/29/jusched-exe/
      My Computer


  9. Posts : 5
    Windows 10 Pro x64
    Thread Starter
       #9

    lifetec said:
    All the dumpfiles are:
    Code:
     *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 139, {3, ffffd00023278260, ffffd000232781b8, 0}
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllDeviceState+1cb )
    Followup: MachineOwner
    ---------
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: ffffd00023278260, Address of the trap frame for the exception that caused the bugcheck
    Arg3: ffffd000232781b8, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    Debugging Details:
    ------------------
    
    TRAP_FRAME:  ffffd00023278260 -- (.trap 0xffffd00023278260)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe00188402260 rbx=0000000000000000 rcx=0000000000000003
    rdx=ffffe001884023c0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff803f4d6ad82 rsp=ffffd000232783f0 rbp=ffffd000232784f9
     r8=ffffc001f5caba20  r9=0000000000000003 r10=7fffc001f5caba20
    r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt! ?? ::FNODOBFM::`string'+0x8c82:
    fffff803`f4d6ad82 cd29            int     29h
    Resetting default scope
    EXCEPTION_RECORD:  ffffd000232781b8 -- (.exr 0xffffd000232781b8)
    ExceptionAddress: fffff803f4d6ad82 (nt! ?? ::FNODOBFM::`string'+0x0000000000008c82)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    BUGCHECK_STR:  0x139
    PROCESS_NAME:  jusched.exe
    CURRENT_IRQL:  2
    In the dumpfiles every time is processname jusched.exe mentioned.
    The jusched.exe is the Java Update Scheduler.
    Search for it if it is in C:\Windows it could be malware or a virus.
    I suspect this preventing windows to shut down properly and causes the BSOD.
    Remove Java from your system or if you need Java disable the java update scheduler.
    For more info http://www.computertechtips.net/29/jusched-exe/
    @lifetec

    Thank you so much for your reply. I think my BSOD was solved. Thank you so much for your reply. It seems that there is a malware in my computer. I never install Java before. After removing the program, there were no more BSOD anymore. Thank you once again. I really appreciate your help. :)
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:58.
Find Us




Windows 10 Forums