BSOD: Happened when logging out and shutting down Windows.

Page 1 of 2 12 LastLast
  1. Jesse Williams's Avatar
    Posts : 1,548
    Windows 10 Home 64-bit

    BSOD: Happened when logging out and shutting down Windows.

    I was logging my computer off this morning and then I shut it down. When I clicked shut down, it had a blue screen of death message. I don't know if this had to do with the latest update or not. Is there a way for me to analyze the dump file to see what happens with future BSOD's?

    HP Pavilion 550-153w Desktop PC with Windows 10 factory installed.

    I have attached the dump log in this thread below.
      My ComputersSystem Spec

  2. Jesse Williams's Avatar
    Posts : 1,548
    Windows 10 Home 64-bit
    Thread Starter

    I think it has to do with a driver. Someone's help would be appreciated.
      My ComputersSystem Spec

  3. Jesse Williams's Avatar
    Posts : 1,548
    Windows 10 Home 64-bit
    Thread Starter

    Can anyone help me with this?
      My ComputersSystem Spec

  4. philc43's Avatar
    Posts : 3,968
    64bit Win 10 Pro ver 1809 Build 17763.379 and W10 Insider Build 18356 and 18855

    Hello Jesse,

    Yes, it is due to the graphics driver that needs updating. Intel HD Graphics 4400 Driver c:\windows\system32\drivers\igdkmd64.sys (, 7.60 MB (7,972,144 bytes))

    Since the one you have is the latest on the HP site you are going to have to try and download one from Intel's download page:

    This was found by scanning the rawstack at the time of the crash. Graphics related calls were in progress.

    0: kd> .load pde;!dpx
     PDE v11.3 - Copyright 2017 Andrew Richards
    Start memory scan  : 0xffff8882ede05798 ($csp)
    End memory scan    : 0xffff8882ede07000 (Kernel Stack Base)
                   rsp : 0xffff8882ede05798 : 0xfffff80274bda74f : nt!PspSystemThreadStartup$filt$0+0x44
                   r14 : 0xffff8882ede05e40 : 0xfffff80274a95bc5 : nt!PspSystemThreadStartup+0x55
    0xffff8882ede05798 : 0xfffff80274bda74f : nt!PspSystemThreadStartup$filt$0+0x44
    0xffff8882ede057b0 : 0xfffff8027f6d3a34 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x804
    0xffff8882ede057d8 : 0xfffff80274b9d41f : nt!_C_specific_handler+0x9f
    0xffff8882ede05808 : 0xfffff8027f6d3219 : dxgmms2!VidMmWorkerThreadProc+0x9
    0xffff8882ede05838 : 0xfffff80274a95bc5 : nt!PspSystemThreadStartup+0x55
    0xffff8882ede05848 : 0xfffff80274bcb0cf : nt!RtlpExecuteHandlerForException+0xf
    0xffff8882ede05870 : 0xffff8882ede05e40 : 0xfffff80274a95bc5 : nt!PspSystemThreadStartup+0x55
    0xffff8882ede05878 : 0xfffff80274a35b20 : nt!RtlDispatchException+0x430
    0xffff8882ede059b8 : 0xfffff80274bc9a3c : nt!KiStartSystemThread+0x1c
    0xffff8882ede059c8 : 0xfffff80274ad3862 : nt!KiChooseTargetProcessor+0x172
    0xffff8882ede059f8 : 0xfffff8027f654707 : dxgmms2!VidSchiInterlockedInsertTailList+0x57
    0xffff8882ede05a68 : 0xfffff80274b211d2 : nt!ExReleaseResourceLite+0xd2
    0xffff8882ede05a88 : 0xfffff80274b224b0 : nt!ExAcquireResourceSharedLite+0x40
    Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    0xffff8882ede05ba8 : 0xfffff8027fb39a86 : dxgkrnl!DXGADAPTER::ReleaseDdiSync+0x66
    0xffff8882ede05bd8 : 0xfffff8027fc05106 : dxgkrnl!ADAPTER_RENDER::DdiBuildPagingBuffer+0x176
    0xffff8882ede05c18 : 0xfffff80274b20700 : nt!ExReleasePushLockExclusiveEx+0x190
    0xffff8882ede05c58 : 0xfffff80274ba48bb : nt!memcpy_s+0x3b
    0xffff8882ede05c88 : 0xfffff8027fb39269 : dxgkrnl!ADAPTER_RENDER_DdiBuildPagingBuffer+0x9
    0xffff8882ede05cb8 : 0xfffff80274ba48bb : nt!memcpy_s+0x3b
    0xffff8882ede05cd8 : 0xfffff80274ba48bb : nt!memcpy_s+0x3b
    0xffff8882ede05ce8 : 0xfffff8027f6be5ca : dxgmms2!VIDMM_GLOBAL::UpdatePageTable+0x46a
    0xffff8882ede05d18 : 0xfffff80274b30288 : nt!KeQueryCurrentStackInformation+0x68
    0xffff8882ede05d38 : 0xfffff80274a363e0 : nt!RtlGetExtendedContextLength2+0x3c
    0xffff8882ede05d48 : 0xfffff80274b30204 : nt!RtlpGetStackLimits+0x14
    0xffff8882ede05d78 : 0xfffff80274a35796 : nt!RtlDispatchException+0xa6
    0xffff8882ede05dc8 : 0xfffff80274a0f000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
    0xffff8882ede05e18 : 0xfffff80274ef989c : "nt!Ports <PERF> (nt+0x4ea89c)"
    0xffff8882ede05e40 : 0xfffff80274a95bc5 : nt!PspSystemThreadStartup+0x55
    0xffff8882ede05e48 : 0xfffff80274a0f000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
    0xffff8882ede05e50 : 0xfffff80274ef989c : "nt!Ports <PERF> (nt+0x4ea89c)"
    0xffff8882ede05e70 : 0xfffff80274b9d380 : nt!_C_specific_handler
    0xffff8882ede05ea8 : 0xfffff80274a95b70 : nt!PspSystemThreadStartup
    0xffff8882ede05eb8 : 0xfffff8027f650000 : "dxgmms2!VidSchMarkDeviceAsError <PERF> (dxgmms2+0x0)"
    0xffff8882ede05ec0 : 0xfffff8027f6a2bc0 : "dxgmms2!__PchSym_ <PERF> (dxgmms2+0x52bc0)"
    0xffff8882ede05ec8 : 0xfffff8027f650000 : "dxgmms2!VidSchMarkDeviceAsError <PERF> (dxgmms2+0x0)"
    0xffff8882ede05ed0 : 0xfffff8027f6a2bb4 : "dxgmms2!__PchSym_ <PERF> (dxgmms2+0x52bb4)"
    0xffff8882ede05ed8 : 0xfffff80274a0f000 : "nt!MmFreeIndependentPages <PERF> (nt+0x0)"
    0xffff8882ede05ee0 : 0xfffff80274ef989c : "nt!Ports <PERF> (nt+0x4ea89c)"
    0xffff8882ede05f18 : 0xfffff80274a7b321 : nt!KiPreprocessFault+0xb1
    0xffff8882ede05f40 : 0xffff8882ede05f50 : 0xfffff8027f6d3a34 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x804
    0xffff8882ede05f48 : 0xfffff80274a364ba : nt!RtlInitializeExtendedContext2+0x32
    0xffff8882ede05f50 : 0xfffff8027f6d3a34 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x804
    0xffff8882ede05f58 : 0xfffff8027f6d3a44 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x814
    0xffff8882ede05f60 : 0xfffff8027f6d3a35 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x805
    0xffff8882ede05f78 : 0xfffff8027f6d3a34 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x804
    0xffff8882ede05f88 : 0xfffff80274a7b1ee : nt!KdTrap+0x22
    0xffff8882ede05fc8 : 0xfffff80274a7ae74 : nt!KiDispatchException+0x144
    0xffff8882ede060f8 : 0xfffff8027f6d3a34 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x804
    0xffff8882ede06108 : 0xfffff80274ad3862 : nt!KiChooseTargetProcessor+0x172
    0xffff8882ede06138 : 0xfffff8027f654707 : dxgmms2!VidSchiInterlockedInsertTailList+0x57
    0xffff8882ede06340 : 0xfffff80274e4c880 : nt!MiSystemPartition
    0xffff8882ede06398 : 0xfffff80274b0f418 : nt!MiResolveTransitionFault+0x468
    0xffff8882ede06400 : 0xfffff80274e4c880 : nt!MiSystemPartition
    0xffff8882ede06458 : 0xfffff80274a363e0 : nt!RtlGetExtendedContextLength2+0x3c
    0xffff8882ede06478 : 0xfffff80274b03400 : nt!MiInPagePageTable+0x290
    0xffff8882ede06488 : 0xfffff80274a8652d : nt!EtwpGetPerfCounter+0xd
    0xffff8882ede06498 : 0xfffff80274a362d9 : nt!RtlGetExtendedContextLength+0x2d
    0xffff8882ede064e8 : 0xfffff80274ad1ed7 : nt!KeSetEvent+0xb7
    0xffff8882ede06548 : 0xfffff80274ac8168 : nt!EtwpLogKernelEvent+0x368
    0xffff8882ede065e8 : 0xfffff80274a48032 : nt!EtwTraceSiloKernelEvent+0xbe
    0xffff8882ede06678 : 0xfffff80274bd3e42 : nt!KiExceptionDispatch+0xc2
    0xffff8882ede067c8 : 0xfffff8027f6d3a34 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x804
    0xffff8882ede06858 : 0xfffff80274bd0168 : nt!KiPageFault+0x428
    0xffff8882ede06860 : 0xffffda00e4531180 :  Trap @ ffff8882ede06860
    0xffff8882ede06878 : 0xfffff80274b281f8 : nt!KiCommitThreadWait+0x508
    0xffff8882ede06948 : 0xfffff80274b20a79 : nt!ExAcquirePushLockSharedEx+0xe9
    0xffff8882ede06958 : 0xfffff80274a22163 : nt!ExfTryToWakePushLock+0x23
    0xffff8882ede06988 : 0xfffff80274b2071f : nt!ExReleasePushLockExclusiveEx+0x1af
    0xffff8882ede069c8 : 0xfffff8027f6d3a34 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x804
    0xffff8882ede06a88 : 0xfffff8027f691248 : dxgmms2!EventDestroyMonitoredFence+0x18
    0xffff8882ede06ac8 : 0xfffff8027f691240 : dxgmms2!EventDestroyMonitoredFence+0x10
    0xffff8882ede06ae8 : 0xfffff80274b88620 : nt!EtwpCCSwapTrace+0x1b0
    0xffff8882ede06bc0 : 0xfffff8027f6d3210 : dxgmms2!VidMmWorkerThreadProc
    0xffff8882ede06bd8 : 0xfffff8027f6d3219 : dxgmms2!VidMmWorkerThreadProc+0x9
    0xffff8882ede06c08 : 0xfffff80274a95bc5 : nt!PspSystemThreadStartup+0x55
    0xffff8882ede06c18 : 0xfffff8027f6d3210 : dxgmms2!VidMmWorkerThreadProc
    0xffff8882ede06c58 : 0xfffff80274bc9a3c : nt!KiStartSystemThread+0x1c
    0xffff8882ede06c70 : 0xfffff80274a95b70 : nt!PspSystemThreadStartup
      My ComputersSystem Spec

  5. Jesse Williams's Avatar
    Posts : 1,548
    Windows 10 Home 64-bit
    Thread Starter

    @philc43, okay. I will update the driver now. Thanks so much for your help! :)
      My ComputersSystem Spec

  6. Jesse Williams's Avatar
    Posts : 1,548
    Windows 10 Home 64-bit
    Thread Starter

    @philc43, I can't find a driver that goes for my processor. Mine has the Intel Core i3-4170 processor.
      My ComputersSystem Spec

  7. philc43's Avatar
    Posts : 3,968
    64bit Win 10 Pro ver 1809 Build 17763.379 and W10 Insider Build 18356 and 18855

    Did you let the Intel website search for updated drivers for your system? Usually it will offer the correct driver to update the graphics GPU (not the CPU).
      My ComputersSystem Spec

  8. Jesse Williams's Avatar
    Posts : 1,548
    Windows 10 Home 64-bit
    Thread Starter

    @philc43, I will try that now. I didn't do that but I did run the Intel Driver & Support Assistant, but it didn't find anything out of date.
      My ComputersSystem Spec

  9. Jesse Williams's Avatar
    Posts : 1,548
    Windows 10 Home 64-bit
    Thread Starter

    It says everything is up to date.
      My ComputersSystem Spec

  10. Posts : 24,482
    windows 10 professional version 1607 build 14393.969 64 bit

    A new Windows version can become corrupt.
    In a similar fashion the most up to date driver can become corrupt.

    Replace the Intel GPU driver: igdkmd64.sys or IGFX following the information in this link:

    Updating a driver. - Microsoft Community

    After replacing the driver download and install: HD Diagnostics Windows: (right upper area of this link)
    HP PC Hardware Diagnostics | HP® Official Site

    Launch the application
    Click system tests > click system extensive test > click run once > post an image of the results into the thread
    After the extensive test has completed click component tests > click video > check all boxes > click run once > post an image into the thread
    Last edited by zbook; 5 Days Ago at 21:23.
      My ComputerSystem Spec

Page 1 of 2 12 LastLast

Related Threads
After some confusion about this section last time, I'm pretty sure that blue screen that came up and said AHHHHH YOU DIED!!!!!! (well it didn't say that, I translated), was a BSOD. My computer crashes regularly, and since I am about to build a...
Good evening, everybody I'm sorry to bother by asking for some help, but i got a weird BSOD just hours ago and i can't figure out what caused it. I tried BlueScreenView from Nirsoft but it gave me a not-so-helpful "ntoskrnl.exe caused it", which...
Logging Out and Shutting Down with Error(s) in BSOD Crashes and Debugging
Each time I log out of my computer to shut it down, an error pops up and the computer chimes letting me know about the error. I have saved the Error Logs as text files that I am uploading to this thread. I hope someone can help me get this issue...
BSOD happened Ex-Nihilo in BSOD Crashes and Debugging
Good day all; I got this after running for weeks without incident. The only system change was 48 hours ago which was a bug fix to "Spybot Search & Destroy". All recommended fixes seemed to work well with that. Any way, I got this little surprise...
Hi, I put a new SSD in my PC, installed it clean with windows 7 from my DVD, then I used an ISO on my memory stick to upgrade to windows ten. Everything was working fine, graphics drivers installed, headset working, steam working, skype working....
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 22:46.
Find Us