Code:
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\EffinCraig\Windows_NT6_BSOD_jcgriff2\011012-16442-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e62000 PsLoadedModuleList = 0xfffff800`030a7670
Debug session time: Tue Jan 10 06:56:20.599 2012 (UTC - 7:00)
System Uptime: 0 days 2:17:08.003
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffff, 2, 0, fffff80002ee2bb6}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+4da57 )
Followup: MachineOwner
---------
3: 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: ffffffffffffffff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002ee2bb6, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003111100
ffffffffffffffff
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeSetEvent+16
fffff800`02ee2bb6 f6037f test byte ptr [rbx],7Fh
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009b0950 -- (.trap 0xfffff880009b0950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007f20000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ee2bb6 rsp=fffff880009b0ae0 rbp=0000000000000004
r8=0000000000000000 r9=fffff880009b0c90 r10=fffffa8009ef4ef0
r11=fffff880009b0cf8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KeSetEvent+0x16:
fffff800`02ee2bb6 f6037f test byte ptr [rbx],7Fh ds:0010:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ede1e9 to fffff80002edec40
STACK_TEXT:
fffff880`009b0808 fffff800`02ede1e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b0810 fffff800`02edce60 : fffffa80`094d6df0 fffff880`00eff30f fffffa80`07321c01 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69
fffff880`009b0950 fffff800`02ee2bb6 : 00000000`000445a2 00000000`00000022 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009b0ae0 fffff880`04ad6a57 : 00000000`00000000 fffff880`00000000 fffffa80`09559400 fffffa80`09b5d9f0 : nt!KeSetEvent+0x16
fffff880`009b0b50 00000000`00000000 : fffff880`00000000 fffffa80`09559400 fffffa80`09b5d9f0 00000000`00000000 : atikmdag+0x4da57
STACK_COMMAND: kb
FOLLOWUP_IP:
atikmdag+4da57
fffff880`04ad6a57 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: atikmdag+4da57
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e
FAILURE_BUCKET_ID: X64_0xA_atikmdag+4da57
BUCKET_ID: X64_0xA_atikmdag+4da57
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\EffinCraig\Windows_NT6_BSOD_jcgriff2\011012-26286-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`03064670
Debug session time: Tue Jan 10 07:48:27.085 2012 (UTC - 7:00)
System Uptime: 0 days 0:29:53.100
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffffffffffffff, 2, 0, fffff80002e9fbb6}
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+4da57 )
Followup: MachineOwner
---------
3: 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: ffffffffffffffff, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002e9fbb6, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ce100
ffffffffffffffff
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeSetEvent+16
fffff800`02e9fbb6 f6037f test byte ptr [rbx],7Fh
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009b0950 -- (.trap 0xfffff880009b0950)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8007e9b000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e9fbb6 rsp=fffff880009b0ae0 rbp=0000000000000004
r8=0000000000000000 r9=fffff880009b0c90 r10=fffffa800a103ef0
r11=fffff880009b0cf8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KeSetEvent+0x16:
fffff800`02e9fbb6 f6037f test byte ptr [rbx],7Fh ds:e180:00000000`00000000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e9b1e9 to fffff80002e9bc40
STACK_TEXT:
fffff880`009b0808 fffff800`02e9b1e9 : 00000000`0000000a ffffffff`ffffffff 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b0810 fffff800`02e99e60 : fffffa80`0948cdf0 fffff880`00e9e30f 00000000`00000032 ffffffff`ffffffff : nt!KiBugCheckDispatch+0x69
fffff880`009b0950 fffff800`02e9fbb6 : 00000000`0000019c 00000000`00000022 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009b0ae0 fffff880`04aeea57 : 00000000`00000000 fffff880`00000000 fffffa80`09421000 00000000`00000000 : nt!KeSetEvent+0x16
fffff880`009b0b50 00000000`00000000 : fffff880`00000000 fffffa80`09421000 00000000`00000000 00000000`00000000 : atikmdag+0x4da57
STACK_COMMAND: kb
FOLLOWUP_IP:
atikmdag+4da57
fffff880`04aeea57 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: atikmdag+4da57
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ebb3c7e
FAILURE_BUCKET_ID: X64_0xA_atikmdag+4da57
BUCKET_ID: X64_0xA_atikmdag+4da57
Followup: MachineOwner
---------
First, make sure Catalyst Control Center/Vision Engine Control Center is not overclocking your display card. If it is, turn off overclocking.
If the above does not stop your blue screen crashes, uninstall your display card and re-install using 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