Code:
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Cyro\010612-33087-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03249000 PsLoadedModuleList = 0xfffff800`0348e670
Debug session time: Fri Jan 6 10:43:13.973 2012 (GMT-7)
System Uptime: 0 days 0:20:47.831
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff800032cd72c}
Probably caused by : dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::Acquire+bb )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032cd72c, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f8100
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeWaitForSingleObject+17c
fffff800`032cd72c 4c8938 mov qword ptr [rax],r15
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002b8c630 -- (.trap 0xfffff88002b8c630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8a00c15a338
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032cd72c rsp=fffff88002b8c7c0 rbp=0000000000000000
r8=fffff78000000008 r9=0000000000000000 r10=0000000000000000
r11=fffff880009e9180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x17c:
fffff800`032cd72c 4c8938 mov qword ptr [rax],r15 ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032c51e9 to fffff800032c5c40
STACK_TEXT:
fffff880`02b8c4e8 fffff800`032c51e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02b8c4f0 fffff800`032c3e60 : fffff880`101ed80c fffffa80`0bdaf000 fffffa80`0d9905d0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02b8c630 fffff800`032cd72c : fffffa80`0c845b60 fffff880`009e9180 fffffa80`0c845c20 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02b8c7c0 fffff880`02f4ef8b : 00000000`00000000 fffffa80`00000000 fffffa80`0ca50a00 00000000`00000000 : nt!KeWaitForSingleObject+0x17c
fffff880`02b8c860 fffff880`02f6cfba : 00000000`00000001 fffff8a0`0f7ab000 00000000`00000000 fffff880`009e9180 : dxgmms1!DXGFASTMUTEX::Acquire+0xbb
fffff880`02b8c8a0 fffff880`02f69ee4 : fffff8a0`0f7ab000 fffffa80`0e264c38 fffffa80`0ca78000 fffffa80`0ca68750 : dxgmms1!VIDMM_GLOBAL::EvictAllocation+0x2e
fffff880`02b8c8e0 fffff880`02f66ed3 : 00000000`00000000 fffffa80`0dd28410 00000000`000000df 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x218
fffff880`02b8c910 fffff880`02f8165d : 00000000`00000000 fffff8a0`00d896e0 fffffa80`00000000 fffffa80`0a23f450 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`02b8cae0 fffff880`02f81398 : fffff800`00b96080 fffff880`02f80d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02b8ccd0 fffff880`02f80e96 : 00000000`00000000 fffffa80`0d90f490 00000000`00000080 fffffa80`0ca50410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02b8cd00 fffff800`03560fee : 00000000`041ce730 fffffa80`0c845b60 fffffa80`09d43740 fffffa80`0c845b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02b8cd40 fffff800`032b75e6 : fffff800`0343be80 fffffa80`0c845b60 fffff800`03449cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02b8cd80 00000000`00000000 : fffff880`02b8d000 fffff880`02b87000 fffff880`02b8c680 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!DXGFASTMUTEX::Acquire+bb
fffff880`02f4ef8b 48833b00 cmp qword ptr [rbx],0
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dxgmms1!DXGFASTMUTEX::Acquire+bb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0xA_dxgmms1!DXGFASTMUTEX::Acquire+bb
BUCKET_ID: X64_0xA_dxgmms1!DXGFASTMUTEX::Acquire+bb
Followup: MachineOwner
---------
Follow the steps for Diagnosing basic problems with DirectX
For changing out drivers for your graphics/display card, use 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
Also, very imporant, update the following drivers using information from Driver References and Manufacturer References.
Code:
ASACPI fffff880`02e4b000 fffff880`02e53000 Sun Mar 27 20:30:36 2005 (42476c4c) 00003c77 ASACPI.sys
Lycosa fffff880`046a7000 fffff880`046ab980 Fri Jan 18 01:51:42 2008 (4790689e) 0000e99d Lycosa.sys
ASACPI.SYS is a known BSOD problem on Windows 7. 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.
Quote