Solved BSOD after updating Video Drivers (Crimson 16.4.1 Win7)

IoNGeNeRaL · Apr 9, 2016

Hey guys.

So I updated my video card drivers to the latest Crimson 16.4.1 (hotfix) and my system started crashing to random BSODs. First it was 0x0AE (or EA) and now it's "DRIVER_CORRUPTED_EXPOOL (c5)". Unfortunately CCleaner cleaned and removed the other BSOD so I only have 0x0C5. Here's the dump info.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\040916-14617-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19110.amd64fre.win7sp1_gdr.151230-0600
Machine Name:
Kernel base = 0xfffff800`06804000 PsLoadedModuleList = 0xfffff800`06a4b730
Debug session time: Sat Apr 9 14:44:21.431 2016 (UTC + 1:00)
System Uptime: 0 days 0:01:37.649
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {8, 2, 0, fffff800069b0b15}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+249 )

Followup: Pool_corruption
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800069b0b15, address which referenced memory

Debugging Details:
------------------

BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+249
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: fffff88003999940 -- (.trap 0xfffff88003999940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80006a0c6d0
rdx=fffffa800016e350 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800069b0b15 rsp=fffff88003999ad0 rbp=0000000000000000
r8=0000000000000000 r9=fffffa800016e350 r10=0000000000000001
r11=fffffa800016e360 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!ExDeferredFreePool+0x249:
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11 ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800068771a9 to fffff80006877c00

STACK_TEXT:
fffff880`039997f8 fffff800`068771a9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03999800 fffff800`06875e20 : fffffa80`0b1fcb10 fffffa80`0b36b040 fffffa80`0b273040 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03999940 fffff800`069b0b15 : 00000000`00000000 00000000`00000000 00000000`00000000 70696d57`00000000 : nt!KiPageFault+0x260
fffff880`03999ad0 fffff800`069b01b1 : 00000000`00000000 fffffa80`1082ba70 00000000`00000000 fffff800`06acf180 : nt!ExDeferredFreePool+0x249
fffff880`03999b60 fffff800`06acf5b5 : 00000000`c0000001 fffffa80`1082ba80 fffff8a0`3377444e 00000000`00000324 : nt!ExFreePoolWithTag+0x411
fffff880`03999c10 fffff800`06acf484 : fffffa80`1082ba80 00000000`00000000 fffffa80`0eaab901 00000000`00000000 : nt!WmipProcessEvent+0x101
fffff880`03999c80 fffff800`06881a69 : fffff800`06a22200 fffff800`06b71401 fffffa80`0b273000 fffffa80`0b273040 : nt!WmipEventNotification+0x38
fffff880`03999cb0 fffff800`06b10926 : 00000000`00000000 fffffa80`0b273040 00000000`00000080 fffffa80`0b1fcb10 : nt!ExpWorkerThread+0x111
fffff880`03999d40 fffff800`068690e6 : fffff880`038a4180 fffffa80`0b273040 fffff880`038af040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03999d80 00000000`00000000 : fffff880`0399a000 fffff880`03994000 fffff880`039999e0 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+249
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!ExDeferredFreePool+249

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: X64_0xC5_2_nt!ExDeferredFreePool+249

BUCKET_ID: X64_0xC5_2_nt!ExDeferredFreePool+249

Followup: Pool_corruption
---------

1: kd> lmvm Pool_Corruption
start end module name
1: kd> !driver
No export driver found
1: kd> .trap 0xfffff88003999940
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80006a0c6d0
rdx=fffffa800016e350 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800069b0b15 rsp=fffff88003999ad0 rbp=0000000000000000
r8=0000000000000000 r9=fffffa800016e350 r10=0000000000000001
r11=fffffa800016e360 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!ExDeferredFreePool+0x249:
fffff800`069b0b15 4c395808 cmp qword ptr [rax+8],r11 ds:00000000`00000008=????????????????

I should provide notice that my system was not BSODing before I installed/updated the video drivers. I have new RAM too. (all 4 sticks are brand new) I will be having a new model motherboard on Monday installed so I'll need to do a clean-up of all the old board drivers.

System seems stable in Safe Mode with Networking. (I did the minidump stuff in SMw/Networking.

EDIT: It may also seem I have some errors when I ran chkdsk in SafeModew/ Networking.

axe0 · Apr 9, 2016

Hi IoNGeNeRaL,

Before we proceed, please remove all kinds of piracy from your system.
Troubleshooting a system where piracy is present may cause various of trouble, noticeable and in the background, and may make it difficult to proper troubleshoot problems. This is an important reason why with BSOD analysis most analysts won't try to analyze a dump where there is piracy present on the system.

Another important reason is that all sorts of piracy: asking for guidance with a crack, asking for a crack, discussing piracy, illegal programs present on a system when troubleshooting is going on and all other forms of piracy is against Forum Rule #4

Code:

127.0.0.1 3dns.adobe.com 3dns-1.adobe.com 3dns-2.adobe.com 3dns-3.adobe.com 3dns-4.adobe.com activate.adobe.com activate-sea.adobe.com activate-sjc0.adobe.com activate.wip.adobe.com
127.0.0.1 activate.wip1.adobe.com activate.wip2.adobe.com activate.wip3.adobe.com activate.wip4.adobe.com adobe-dns.adobe.com adobe-dns-1.adobe.com adobe-dns-2.adobe.com adobe-dns-3.adobe.com adobe-dns-4.adobe.com
127.0.0.1 adobeereg.com practivate.adobe practivate.adobe.com practivate.adobe.newoa practivate.adobe.ntp practivate.adobe.ipp ereg.adobe.com ereg.wip.adobe.com ereg.wip1.adobe.com
127.0.0.1 ereg.wip2.adobe.com ereg.wip3.adobe.com ereg.wip4.adobe.com hl2rcv.adobe.com wip.adobe.com wip1.adobe.com wip2.adobe.com wip3.adobe.com wip4.adobe.com
127.0.0.1 www.adobeereg.com wwis-dubc1-vip60.adobe.com www.wip.adobe.com www.wip1.adobe.com
127.0.0.1 www.wip2.adobe.com www.wip3.adobe.com www.wip4.adobe.com wwis-dubc1-vip60.adobe.com crl.verisign.net CRL.VERISIGN.NET ood.opsource.net

IoNGeNeRaL · Apr 9, 2016

Hey Axe. Thanks for your response.

The only thing I can see in my hosts file is the following. Not sure where or which hosts file that is in.

axe0 · Apr 9, 2016

There is only 1 hosts file present on a system used by Windows which doesn't have an extension, when I look at your pic it shows hosts.ics, wondering if that is right.

IoNGeNeRaL · Apr 10, 2016

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {fffffa800e527610, 0, 0, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa800e527610, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------


FAULTING_THREAD:  fffffa800e527610

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88005247f63 to fffff800068c53c0

STACK_TEXT:  
fffff880`02fe02a8 fffff880`05247f63 : 00000000`000000ea fffffa80`0e527610 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fe02b0 00000000`000000ea : fffffa80`0e527610 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`05247f63
fffff880`02fe02b8 fffffa80`0e527610 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`05247e28 : 0xea
fffff880`02fe02c0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`05247e28 00000000`00000028 : 0xfffffa80`0e527610


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

Followup: MachineOwner
---------

4: kd> lmvm Unknown_Module
start             end                 module name

Piracy removed. Hosts file edited and removed adobe activation server links.

This new BSOD was today, and another graphics driver fault. My Graphics Card was fine before I tried to update it's drivers. The card itself is not faulty.

axe0 · Apr 10, 2016

This is from the BSOD from yesterday

Please replace Kaspersky with Microsoft Security Essentials while troubleshooting

Code:

fffff880`039996f8  fffff880`0469e670Unable to load image \SystemRoot\system32\DRIVERS\kneps.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kneps.sys
*** ERROR: Module load completed but symbols could not be loaded for kneps.sys
 kneps+0x22670
fffff880`03999700  fffffa80`0fce65b0
fffff880`03999708  fffff880`00c064bdUnable to load image \SystemRoot\system32\DRIVERS\kltdi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for kltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for kltdi.sys
 kltdi+0x64bd

What exactly were you doing at the time the BSOD occcured today?

IoNGeNeRaL · Apr 10, 2016

I'd rather not replace my KIS with MSE as I still have 253 days of my license left. (Yes, I bought a year license

) I was listening to this on YouTube:

Whenever I seem to watch something on YouTube or stream something my graphics drivers go into an infinite loop for some reason. my display goes blank, reappears, goes blank, and so on. Then it crashes to the BSOD.

EDIT: And MSE doesn't protect my system well enough like KIS does. I've had issues with MSE letting some infectious diseases in whereas KIS and MBAM stop them in their tracks.

EDIT#2: I just tried to launch GTA V and it crashed. (the game)

axe0 · Apr 10, 2016

Replacing Kaspersky with MSE is only temporary while troubleshooting, not trying this would make troubleshooting only difficult.

Regarding your display issues, please try following
Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to ONLY install the drivers using custom/advanced options.
View attachment 384925

IoNGeNeRaL · Apr 10, 2016

It just crashed again as I was downloading the new display drivers and trying to sfc /scannow.

IoNGeNeRaL · Apr 10, 2016

For some reason I can't uninstall KIS. I get this error.

axe0 · Apr 10, 2016

Try to run the Kaspersky Product Removal tool

IoNGeNeRaL · Apr 10, 2016

KIS is removed. MSE is installed. I can't uninstall AMD OverDrive though as it just says this.

axe0 · Apr 10, 2016

Run DDU again and follow http://www.sevenforums.com/tutorial...install-without-catalyst-install-manager.html to only install the drivers.
If the most recent drivers don't help, try some of the older drivers

IoNGeNeRaL · Apr 10, 2016

I'm about to reboot my system after manually updating the drivers as per that article. I'll report back in a few minutes.

IoNGeNeRaL · Apr 10, 2016

At the moment it's okay, but when I was on YT it froze a second and did that beep/buzz noise as if it was about to BSOD.

axe0 · Apr 10, 2016

Keep me posted on the situation

IoNGeNeRaL · Apr 10, 2016

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\041016-23665-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.19135.amd64fre.win7sp1_gdr.160121-1718
Machine Name:
Kernel base = 0xfffff800`06868000 PsLoadedModuleList = 0xfffff800`06aaf730
Debug session time: Sun Apr 10 17:23:44.434 2016 (UTC + 1:00)
System Uptime: 0 days 0:50:47.682
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {fffffa800cbc1b50, 0, 0, 0}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )

Followup: MachineOwner
---------

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa800cbc1b50, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------


FAULTING_THREAD:  fffffa800cbc1b50

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880048d1f63 to fffff800068dc3c0

STACK_TEXT:  
fffff880`03e622a8 fffff880`048d1f63 : 00000000`000000ea fffffa80`0cbc1b50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03e622b0 fffff880`048d2112 : fffff880`03e62388 fffff880`11038988 fffff880`03e62388 fffff880`11049fab : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`03e62320 fffff880`11049fb3 : fffffa80`0c28f000 00000000`00000000 fffffa80`0c28f000 fffff880`11038960 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`03e62360 fffffa80`0c28f000 : 00000000`00000000 fffffa80`0c28f000 fffff880`11038960 00000000`01c9c380 : atikmdag+0x45fb3
fffff880`03e62368 00000000`00000000 : fffffa80`0c28f000 fffff880`11038960 00000000`01c9c380 00000000`00000028 : 0xfffffa80`0c28f000


STACK_COMMAND:  .thread 0xfffffa800cbc1b50 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`048d1f63 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

Followup: MachineOwner
---------

4: kd> lmvm dxgkrnl
start             end                 module name
fffff880`048cb000 fffff880`049c0000   dxgkrnl    (pdb symbols)          c:\symbols\dxgkrnl.pdb\6EA4BB76A6FE42778EBB996CA1F665ED1\dxgkrnl.pdb
    Loaded symbol image file: dxgkrnl.sys
    Mapped memory image file: c:\symbols\dxgkrnl.sys\539E411Cf5000\dxgkrnl.sys
    Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
    Image name: dxgkrnl.sys
    Timestamp:        Mon Jun 16 01:58:04 2014 (539E411C)
    CheckSum:         000FF01E
    ImageSize:        000F5000
    File version:     6.1.7601.18510
    Product version:  6.1.7601.18510
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgkrnl.sys
    OriginalFilename: dxgkrnl.sys
    ProductVersion:   6.1.7601.18510
    FileVersion:      6.1.7601.18510 (win7sp1_gdr.140615-1511)
    FileDescription:  DirectX Graphics Kernel
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Just got back from Subway and my system BSOD earlier.

axe0 · Apr 10, 2016

Please downgrade your BIOS to a stable version
https://www.asus.com/Motherboards/CROSSHAIR_IV_FORMULA/HelpDesk_Download/

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {fffffa800cbc1b50, 0, 0, 0}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )

Followup:     MachineOwner
---------

Processing initial command '!analyze -v; !sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time;'
4: kd> !analyze -v; !sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time;
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: fffffa800cbc1b50, Pointer to a stuck thread object.  Do .thread then kb on it to find
	the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:
------------------


SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  System Version

BIOS_DATE:  10/09/2012

BASEBOARD_PRODUCT:  Crosshair IV Formula

BASEBOARD_VERSION:  Rev 1.xx

BUGCHECK_P1: fffffa800cbc1b50

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FAULTING_THREAD:  0cbc1b50

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT

CPU_COUNT: 6

CPU_MHZ: c8a

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 10

CPU_MODEL: a

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LAST_CONTROL_TRANSFER:  from fffff880048d1f63 to fffff800068dc3c0

STACK_TEXT:  
fffff880`03e622a8 fffff880`048d1f63 : 00000000`000000ea fffffa80`0cbc1b50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03e622b0 fffff880`048d2112 : fffff880`03e62388 fffff880`11038988 fffff880`03e62388 fffff880`11049fab : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`03e62320 fffff880`11049fb3 : fffffa80`0c28f000 00000000`00000000 fffffa80`0c28f000 fffff880`11038960 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`03e62360 fffffa80`0c28f000 : 00000000`00000000 fffffa80`0c28f000 fffff880`11038960 00000000`01c9c380 : atikmdag+0x45fb3
fffff880`03e62368 00000000`00000000 : fffffa80`0c28f000 fffff880`11038960 00000000`01c9c380 00000000`00000028 : 0xfffffa80`0c28f000


STACK_COMMAND:  .thread 0xfffffa800cbc1b50 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
fffff880`048d1f63 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c

IMAGE_VERSION:  6.1.7601.18510

FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys

PRIMARY_PROBLEM_CLASS:  X64_0xEA_IMAGE_dxgkrnl.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xea_image_dxgkrnl.sys

FAILURE_ID_HASH:  {b58a0dfd-90f3-63cd-1b07-7ce1b53744cb}

Followup:     MachineOwner
---------

[SMBIOS Data Tables v2.6]
[DMI Version - 0]
[2.0 Calling Convention - No]
[Table Size - 2751 bytes]

[BIOS Information (Type 0) - Length 24 - Handle 0000h]
  Vendor                        American Megatrends Inc.
  BIOS Version                  3029   
  BIOS Starting Address Segment f000
  BIOS Release Date             10/09/2012
  BIOS ROM Size                 200000
  BIOS Characteristics
       04: - ISA Supported
       07: - PCI Supported
       09: - Plug and Play Supported
       11: - Upgradeable FLASH BIOS
       12: - BIOS Shadowing Supported
       14: - ESCD Supported
       15: - CD-Boot Supported
       16: - Selectable Boot Supported
       17: - BIOS ROM Socketed
       19: - EDD Supported
       23: - 1.2MB Floppy Supported
       24: - 720KB Floppy Supported
       25: - 2.88MB Floppy Supported
       26: - Print Screen Device Supported
       27: - Keyboard Services Supported
       28: - Serial Services Supported
       29: - Printer Services Supported
       30: - CGA/Mono Services Supported
       32: - BIOS Vendor Reserved
  BIOS Characteristic Extensions
       00: - ACPI Supported
       01: - USB Legacy Supported
       04: - LS120-Boot Supported
       05: - ATAPI ZIP-Boot Supported
       08: - BIOS Boot Specification Supported
       10: - Specification Reserved
  BIOS Major Revision           8
  BIOS Minor Revision           15
  EC Firmware Major Revision    255
  EC Firmware Minor Revision    255
[System Information (Type 1) - Length 27 - Handle 0001h]
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
  Version                       System Version
  Serial Number                                     
  UUID                          00000000-0000-0000-0000-000000000000
  Wakeup Type                   Power Switch
  SKUNumber                     To Be Filled By O.E.M.
  Family                        To Be Filled By O.E.M.
[BaseBoard Information (Type 2) - Length 15 - Handle 0002h]
  Manufacturer                  ASUSTeK Computer INC.
  Product                       Crosshair IV Formula
  Version                       Rev 1.xx
  Serial Number                              
  Asset Tag                                           
  Feature Flags                 09h
       -775935680: - (null)
       -775935632: - (null)
  Location                      To Be Filled By O.E.M.
  Chassis Handle                0003h
  Board Type                    0ah - Processor/Memory Module
  Number of Child Handles       0
[System Enclosure (Type 3) - Length 21 - Handle 0003h]
  Manufacturer                  Chassis Manufacture
  Chassis Type                  Desktop
  Version                       Chassis Version
  Serial Number                                      
  Asset Tag Number                              
  Bootup State                  Safe
  Power Supply State            Safe
  Thermal State                 Safe
  Security Status               None
  OEM Defined                   17
  Height                        0U
  Number of Power Cords         1
  Number of Contained Elements  0
  Contained Element Size        0
[Processor Information (Type 4) - Length 42 - Handle 0004h]
  Socket Designation            AM3
  Processor Type                Central Processor
  Processor Family              ech - Specification Reserved
  Processor Manufacturer        AMD              
  Processor ID                  a00f1000fffb8b17
  Processor Version             AMD Phenom(tm) II X6 1090T Processor                
  Processor Voltage             8dh - 1.3V
  External Clock                200MHz
  Max Speed                     3200MHz
  Current Speed                 3200MHz
  Status                        Enabled Populated
  Processor Upgrade             Specification Reserved
  L1 Cache Handle               0005h
  L2 Cache Handle               0006h
  L3 Cache Handle               0007h
  Serial Number                                       
  Asset Tag Number                                    
  Part Number                   To Be Filled By O.E.M.
[Cache Information (Type 7) - Length 19 - Handle 0005h]
  Socket Designation            L1-Cache
  Cache Configuration           0180h - WB Enabled Int NonSocketed L1
  Maximum Cache Size            0300h - 768K
  Installed Size                0300h - 768K
  Supported SRAM Type           0010h - Pipeline-Burst 
  Current SRAM Type             0010h - Pipeline-Burst 
  Cache Speed                   1ns
  Error Correction Type         Specification Reserved
  System Cache Type             Unified
  Associativity                 2-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 0006h]
  Socket Designation            L2-Cache
  Cache Configuration           0181h - WB Enabled Int NonSocketed L2
  Maximum Cache Size            0c00h - 3072K
  Installed Size                0c00h - 3072K
  Supported SRAM Type           0010h - Pipeline-Burst 
  Current SRAM Type             0010h - Pipeline-Burst 
  Cache Speed                   1ns
  Error Correction Type         Specification Reserved
  System Cache Type             Unified
  Associativity                 16-way Set-Associative
[Cache Information (Type 7) - Length 19 - Handle 0007h]
  Socket Designation            L3-Cache
  Cache Configuration           0182h - WB Enabled Int NonSocketed L3
  Maximum Cache Size            1800h - 6144K
  Installed Size                1800h - 6144K
  Supported SRAM Type           0010h - Pipeline-Burst 
  Current SRAM Type             0010h - Pipeline-Burst 
  Cache Speed                   1ns
  Error Correction Type         Specification Reserved
  System Cache Type             Unified
  Associativity                 Other
[OEM Strings (Type 11) - Length 5 - Handle 0033h]
  Number of Strings             4
   1                            To Be Filled By O.E.M.
   2                            To Be Filled By O.E.M.
   3                            To Be Filled By O.E.M.
   4                            To Be Filled By O.E.M.
[Physical Memory Array (Type 16) - Length 15 - Handle 0036h]
  Location                      03h - SystemBoard/Motherboard
  Use                           03h - System Memory
  Memory Error Correction       03h - None
  Maximum Capacity              14680064KB
  Memory Error Inf Handle       [Not Provided]
  Number of Memory Devices      4
[Memory Array Mapped Address (Type 19) - Length 15 - Handle 0037h]
  Starting Address              00000000h
  Ending Address                00ec0000h
  Memory Array Handle           0036h
  Partition Width               255
[Memory Device (Type 17) - Length 28 - Handle 0038h]
  Physical Memory Array Handle  0036h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          2048MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM0
  Bank Locator                  BANK0
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  Corsair       
  Serial Number                         
  Asset Tag Number                          
  Part Number                   CMZ4GX3M2A1600C9  
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 0039h]
  Starting Address              00000000h
  Ending Address                001fffffh
  Memory Device Handle          0038h
  Mem Array Mapped Adr Handle   0037h
  Partition Row Position        [Reserved]
  Interleave Position           [Unknown]
  Interleave Data Depth         [Unknown]
[Memory Device (Type 17) - Length 28 - Handle 003ah]
  Physical Memory Array Handle  0036h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM1
  Bank Locator                  BANK1
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  Corsair       
  Serial Number                         
  Asset Tag Number                          
  Part Number                   CMZ12GX3M3A1600C9 
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 003bh]
  Starting Address              00200000h
  Ending Address                005fffffh
  Memory Device Handle          003ah
  Mem Array Mapped Adr Handle   0037h
  Partition Row Position        [Reserved]
  Interleave Position           [Unknown]
  Interleave Data Depth         [Unknown]
[Memory Device (Type 17) - Length 28 - Handle 003ch]
  Physical Memory Array Handle  0036h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM2
  Bank Locator                  BANK2
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  Corsair       
  Serial Number                         
  Asset Tag Number                          
  Part Number                   CMZ12GX3M3A1600C9 
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 003dh]
  Starting Address              00000000h
  Ending Address                00000000h
  Memory Device Handle          003ch
  Mem Array Mapped Adr Handle   0037h
  Partition Row Position        [Reserved]
  Interleave Position           [None]
  Interleave Data Depth         [None]
[Memory Device (Type 17) - Length 28 - Handle 003eh]
  Physical Memory Array Handle  0036h
  Memory Error Info Handle      [Not Provided]
  Total Width                   64 bits
  Data Width                    64 bits
  Size                          4096MB
  Form Factor                   09h - DIMM
  Device Set                    [None]
  Device Locator                DIMM3
  Bank Locator                  BANK3
  Memory Type                   18h - Specification Reserved
  Type Detail                   0080h - Synchronous
  Speed                         1333MHz
  Manufacturer                  Corsair       
  Serial Number                         
  Asset Tag Number                          
  Part Number                   CMZ12GX3M3A1600C9 
[Memory Device Mapped Address (Type 20) - Length 19 - Handle 003fh]
  Starting Address              00000000h
  Ending Address                007fffffh
  Memory Device Handle          003eh
  Mem Array Mapped Adr Handle   0037h
  Partition Row Position        [Reserved]
  Interleave Position           [Unknown]
  Interleave Data Depth         [Unknown]
Machine ID Information [From Smbios 2.6, DMIVersion 0, Size=2751]
BiosMajorRelease = 8
BiosMinorRelease = 15
BiosVendor = American Megatrends Inc.
BiosVersion = 3029   
BiosReleaseDate = 10/09/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To Be Filled By O.E.M.
SystemVersion = System Version
SystemSKU = To Be Filled By O.E.M.
BaseBoardManufacturer = ASUSTeK Computer INC.
BaseBoardProduct = Crosshair IV Formula
BaseBoardVersion = Rev 1.xx
sysinfo: unknown error 80004005
GetPointerFromAddress: unable to read from fffff80006b19000
THREAD fffffa800cbc1b50  Cid 0004.0238  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 4
Not impersonating
GetUlongFromAddress: unable to read from fffff80006a57bf0
Owning Process            fffffa800b2699c0       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      195353       
Context Switch Count      536512         IdealProcessor: 0             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address dxgmms1!VidSchiWorkerThread (0xfffff88004837f3c)
Stack Init fffff88003e62db0 Current fffff88003e61fb0
Base fffff88003e63000 Limit fffff88003e5d000 Call 0
Priority 16 BasePriority 15 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`03e622a8 fffff880`048d1f63 : 00000000`000000ea fffffa80`0cbc1b50 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`03e622b0 fffff880`048d2112 : fffff880`03e62388 fffff880`11038988 fffff880`03e62388 fffff880`11049fab : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
fffff880`03e62320 fffff880`11049fb3 : fffffa80`0c28f000 00000000`00000000 fffffa80`0c28f000 fffff880`11038960 : dxgkrnl!TdrTimedOperationDelay+0xbe
fffff880`03e62360 fffffa80`0c28f000 : 00000000`00000000 fffffa80`0c28f000 fffff880`11038960 00000000`01c9c380 : atikmdag+0x45fb3
fffff880`03e62368 00000000`00000000 : fffffa80`0c28f000 fffff880`11038960 00000000`01c9c380 00000000`00000028 : 0xfffffa80`0c28f000

Bugcheck code 100000EA
Arguments fffffa80`0cbc1b50 00000000`00000000 00000000`00000000 00000000`00000000
Debug session time: Sun Apr 10 18:23:44.434 2016 (UTC + 2:00)
System Uptime: 0 days 0:50:47.682

4: kd> lmvm atikmdag
Browse full module list
start             end                 module name
fffff880`11004000 fffff880`129a3000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Apr 04 04:46:46 2016 (5701D596)
    CheckSum:         019219C8
    ImageSize:        0199F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

IoNGeNeRaL · Apr 10, 2016

Not sure what good downgrading my BIOS will do but okay.

Here's another BSOD. Same bugcheck. Constantly. My system only started doing this BSOD rubbish when I updated the video drivers to the latest.

Won't I have to remove all of these drivers/chipset drivers from my system on Monday when my Crosshair V Formula-Z has been installed?

torchwood · Apr 10, 2016

apologies for butting in,
When your finished here please post in the windows update/activation section
You have more problems that need to be sorted
SFC errors/update probs, which might be fixed by Axe0

On a further note you appear to have had BSOD's for a number of years
Roy

Solved BSOD after updating Video Drivers (Crimson 16.4.1 Win7)

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

BSOD Analyst

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer