Code:
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Crommitra\Crom Windows_NT6_BSOD_jcgriff2\010312-34101-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a61000 PsLoadedModuleList = 0xfffff800`02ca6670
Debug session time: Tue Jan 3 15:56:18.240 2012 (UTC - 7:00)
System Uptime: 0 days 8:18:30.194
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80097db4e0, fffff88004387a48, 0, 2}
Unable to load image atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+7a48 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80097db4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004387a48, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
atikmpag+7a48
fffff880`04387a48 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`070399c8 fffff880`0454c000 : 00000000`00000116 fffffa80`097db4e0 fffff880`04387a48 00000000`00000000 : nt!KeBugCheckEx
fffff880`070399d0 fffff880`0454bd0a : fffff880`04387a48 fffffa80`097db4e0 fffffa80`055503e0 fffffa80`077db010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`07039a10 fffff880`0440ff07 : fffffa80`097db4e0 00000000`00000000 fffffa80`055503e0 fffffa80`077db010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`07039a40 fffff880`04439b75 : 00000000`ffffffff 00000000`001d40b6 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`07039b20 fffff880`044382bb : 00000000`00000102 00000000`00000003 00000000`001d40b6 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`07039b50 fffff880`0440b2c6 : ffffffff`ff676980 fffffa80`077db010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`07039bf0 fffff880`04437e7a : 00000000`00000000 fffffa80`07bc4ab0 00000000`00000080 fffffa80`077db010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`07039d00 fffff800`02d78fee : 00000000`fffffc32 fffffa80`07af0b60 fffffa80`05508990 fffffa80`07af0b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`07039d40 fffff800`02acf5e6 : fffff880`009eb180 fffffa80`07af0b60 fffff880`009f60c0 00000000`000c2bb3 : nt!PspSystemThreadStartup+0x5a
fffff880`07039d80 00000000`00000000 : fffff880`0703a000 fffff880`07034000 fffff880`0a1dfb00 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+7a48
fffff880`04387a48 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+7a48
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e31cc72
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------
ASACPI.SYS is a known BSOD problem on Windows 7 (See the code block that follows the next set of instructions). Update the driver by:
1. Going to the Asus motherboard support site
When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
a. Click Start Menu
b. Click My Computer
c. Go to C:\WIndows\System32\drivers\
d. Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
Thanks to JMH and zigzag3143 for the above information.
Code:
ASACPI fffff880`045e3000 fffff880`045eb000 Sun Mar 27 20:30:36 2005 (42476c4c) 00003c77 ASACPI.sys
If the above does not resolve your conflict due to your display driver blamed in the blue screen error above, do the following steps:
1. Download and install Driver Sweeper
2. Download the latest driver for your display card
3. Click Start Menu
4. Right Click My Computer
5. Click Manage
6. Click Device Manager from the list on the left
7. Click the + next to Display adapter
8. Right click your display/graphics card device
9. Click Uninstall
10. Check the box to Delete driver software for the device
11. Click OK
12. Restart your computer in safe mode
13. Run Driver Sweeper, select display card manufacturer's drivers, analyze, clean
14. Restart your computer
15. Install the latest drivers
Quote