KERNEL_SECURITY_CHECK_FAILURE (139)
This bug check indicates that the kernel has detected the corruption of a critical data structure.
Code:
BugCheck 139, {3, ffffd00166f3f3d0, ffffd00166f3f328, 0}
The 1st parameter of the bugcheck is 3 which indicates that a LIST_ENTRY was corrupted. Code 3, LIST_ENTRY corruption. This type of bug check can be difficult to track down and indicates that an inconsistency has been introduced into a doubly-linked list (detected when an individual list entry element is added to or removed from the list).
Code:
0: kd> k
Child-SP RetAddr Call Site
ffffd001`66f3f0a8 fffff800`6ad63ae9 nt!KeBugCheckEx
ffffd001`66f3f0b0 fffff800`6ad63e10 nt!KiBugCheckDispatch+0x69
ffffd001`66f3f1f0 fffff800`6ad63034 nt!KiFastFailDispatch+0xd0
ffffd001`66f3f3d0 fffff800`85e6e801 nt!KiRaiseSecurityCheckFailure+0xf4
ffffd001`66f3f560 fffff800`85e51ab4 dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x1d1f1
ffffd001`66f3f690 fffff800`85e59ca7 dxgmms1!VIDMM_GLOBAL::PageInAllocations+0xd4
ffffd001`66f3f710 fffff800`85e63a6a dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd27
ffffd001`66f3f990 fffff800`85e65da5 dxgmms1!VidSchiSubmitRenderCommand+0x20a
ffffd001`66f3fb70 fffff800`85e65d1d dxgmms1!VidSchiRun_PriorityTable+0x85
ffffd001`66f3fbc0 fffff800`6acd3794 dxgmms1!VidSchiWorkerThread+0x8d
ffffd001`66f3fc00 fffff800`6ad5e5c6 nt!PspSystemThreadStartup+0x58
ffffd001`66f3fc60 00000000`00000000 nt!KiStartSystemThread+0x16
Code:
0: kd> .exr 0xffffd00166f3f328
ExceptionAddress: fffff80085e6e801 (dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x000000000001d1f1)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun
Code:
0: kd> !verifier -f
fffff8006aece680: Unable to get verifier list.
Okay, so this is conclusive and also not exactly what I was hoping for. This is
not a software problem, but instead a hardware problem. At the time of the crash, we have a lot of DirectX MMS Direct Memory Access (DMA) stuff going on, as well as video scheduler allocations. We can see that upon committing a resource, it actually then went ahead and corrupted the data structure so bad that a security check needed to be raised, and
fast.
Code:
nt!KiFastFailDispatch+0xd0
Right here, Windows is literally saying 'stop everything right
now, this is bad' as opposed to its usual error handling when a bug check is going to be called.
With all of this said, given we've already replaced the video card and Memtest has passed with flying colors multiple times, this is at this point a faulty motherboard. There's
one thing left to try, and that's a BIOS update if available.
Regards,
Patrick