Hi,
We have various bug checks:
KERNEL_SECURITY_CHECK_FAILURE (139)
This bug check indicates that the kernel has detected the corruption of a critical data structure.
BugCheck 139, {
3, ffffd00024629f40, ffffd00024629e98, 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
ffffd000`24629c18 fffff802`e435fae9 nt!KeBugCheckEx
ffffd000`24629c20 fffff802`e435fe10 nt!KiBugCheckDispatch+0x69
ffffd000`24629d60 fffff802`e435f034 nt!KiFastFailDispatch+0xd0
ffffd000`24629f40 fffff800`d628fb1c nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2462a0d0 fffff800`d6275430 dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x1a68c
ffffd000`2462a1a0 fffff800`d611f983 dxgmms1!VIDMM_GLOBAL::CloseAllocation+0x4c
ffffd000`2462a1e0 fffff800`d6110c24 dxgkrnl!DXGDEVICE::DestroyAllocations+0x183
ffffd000`2462a2f0 fffff800`d610f855 dxgkrnl!DXGDEVICE::TerminateAllocations+0x594
ffffd000`2462a390 fffff800`d610f354 dxgkrnl!DXGDEVICE::DestroyAllocationInternal+0x12d
ffffd000`2462a3e0 fffff800`d610ec11 dxgkrnl!DxgkDestroyAllocationInternal+0x264
ffffd000`2462a6d0 fffff802`e435f7b3 dxgkrnl!DxgkDestroyAllocation+0x301
ffffd000`2462ab00 00000000`7784741a nt!KiSystemServiceCopyEnd+0x13
00000000`345ce048 00000000`00000000 0x7784741a
DirectX Kernel/MMS throughout the stack, appearing to possibly cause list corruption when destroying allocations.
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
This indicates that the video scheduler has detected a fatal violation.
Code:
3: kd> k
Child-SP RetAddr Call Site
ffffd001`0b7ef928 fffff800`d47b69ca nt!KeBugCheckEx
ffffd001`0b7ef930 fffff800`d449de28 watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd001`0b7ef970 fffff800`d44903c2 dxgmms1!VidSchiProcessIsrCompletedPacket+0xd778
ffffd001`0b7efa60 fffff800`d449022a dxgmms1!VidSchDdiNotifyInterruptWorker+0x162
ffffd001`0b7efac0 fffff800`d463aa9e dxgmms1!VidSchDdiNotifyInterrupt+0x7a
ffffd001`0b7efaf0 fffff800`d4d87256 dxgkrnl!DxgNotifyInterruptCB+0x6e
ffffd001`0b7efb20 ffffd001`0b7efd10 nvlddmkm+0xcb256
ffffd001`0b7efb28 00000000`00000000 0xffffd001`0b7efd10
Code:
FAILURE_BUCKET_ID: 0x119_1_[COLOR=#ff0000]DRIVER_REPORTED_INVALID_FENCE_ID[/COLOR]_nvlddmkm+cb256
It appears the nVidia video driver reported that a fence ID(s) has/have been returned not in the expected and/or proper order, and DirectX says 'this isn't right', and calls the bug check.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This indicates that a system thread generated an exception which the error handler did not catch.
Code:
BugCheck 1000007E, {[COLOR=#ff0000]ffffffffc0000005[/COLOR], fffff801da98b574, [COLOR=#4b0082]ffffd000af6a6488[/COLOR], ffffd000af6a5c90}
The 1st parameter of the bug check is 0xc0000005 which indicates an access violation has occurred.
Code:
0: kd> .exr 0xffffd000af6a6488
ExceptionAddress: fffff801da98b574 ([COLOR=#4b0082]dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000001a4[/COLOR])
ExceptionCode: [COLOR=#ff0000]c0000005 (Access violation)[/COLOR]
The violation occurred in
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x00000000000001a4. This is the DirectX MMS.
1. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.
2. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it may be causing conflicts:
avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal
Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8
3. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
4. If the above fails, possibly faulty GPU.
-- Speaking of which, can you answer this question for me?
Gigabyte Geforce 660Ti OC
Is the
OC part of the model, or are you implying that this is an overclocked (non-factory) GPU? If so, reset it to defaults ASAP as it's unstable.
Regards,
Patrick
