Hi,
We have various different bug checks:
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (FC)
This indicates that an attempt was made to execute non-executable memory.
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
This indicates that the video memory manager has encountered a condition that it is unable to recover from.
Code:
2: kd> kv
Child-SP RetAddr : Args to Child : Call Site
ffffd000`23d1d558 fffff800`01e729ca : 00000000`0000010e 00000000`0000001f ffffc000`0aec19f0 00000000`00000000 : nt!KeBugCheckEx
ffffd000`23d1d560 fffff800`01ecfbbf : ffffe000`00ae7090 00000000`00531cbb ffffc000`0211fdb8 ffffd000`23d1d6a0 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffd000`23d1d5a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x18e2f
From the above call stack, we can see that a Direct X MMS routine called into a watchdog event error, and then the bugcheck. This is generally caused by the video driver behaving improperly, or a faulty video card.
SYSTEM_SERVICE_EXCEPTION (3b)
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
BugCheck 3B, {c0000005,
fffff803a9d1406c, ffffd0002a57ca40, 0}
Code:
2: kd> ln fffff803a9d1406c
(fffff803`a9d13e30) nt!ExDeferredFreePool+0x23c | (fffff803`a9d142d0) nt!ExFreePoolWithTag
^^ The exception occurred in
nt!ExDeferredFreePool which indicates probable pool corruption.
FOLLOWUP_NAME:
Pool_corruption
IMAGE_NAME:
Pool_Corruption
^^ This appears to be the case, indeed.
IRQL_NOT_LESS_OR_EQUAL (a)
This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
KERNEL_SECURITY_CHECK_FAILURE (139)
This bug check indicates that the kernel has detected the corruption of a critical data structure.
BugCheck 139, {
3, ffffd000208b36d0, ffffd000208b3628, 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).
-- FAILURE_BUCKET_ID: X64_0x139_
cng!g_pool+e0
^^ Windows Kernel Cryptography, Next Generation driver.
1. Uninstall Asus AI Suite (or PC Probe).
2. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's likely 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.
Code:
CORK95 fffff800`031d2000 fffff800`031e0000 Wed Oct 31 04:59:51 2012 (5090e887) 000090ab CORK95.sys
^^ I
believe this might be a trojan or some other form of malware. It has empty values and no documentation whatsoever. Due to this, I'm going to have you head over to the proper forum here.
Make a thread here - Security Arena - Sysnative Forums
Be sure to follow this first before making the thread - https://www.sysnative.com/forums/security-arena/2507-malware-removal-posting-instructions.html
4. 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.
5. 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.
Regards,
Patrick