You have not been ignored. You are in my list of to do crashes. We volunteer our time on here to help others. By thinking that you are more important than other people on here and should have yours looked at NOW, you are going to rub the helpers the wrong way and fall further down in their priorities.
Possible out of date drivers:
Code:
AtiPcie fffff880`01600000 fffff880`01608000 Tue May 05 09:00:22 2009 (4a005486) 000134c7 AtiPcie.sys
AtiPcie.sys
Code:
-
Loading Dump File [D:\Kingston\BSODDmpFiles\redaces\Windows_NT6_BSOD_jcgriff2\030812-18283-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e15000 PsLoadedModuleList = 0xfffff800`0305a670
Debug session time: Thu Mar 8 20:26:08.366 2012 (UTC - 7:00)
System Uptime: 0 days 0:03:47.614
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, c, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'dump_dumpfve' and 'crashdmp.sys' overlap
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c4100
0000000000000000
CURRENT_IRQL: c
FAULTING_IP:
+3839623231383732
00000000`00000000 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff88008b2a700 -- (.trap 0xfffff88008b2a700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80002ea1858 rbx=0000000000000000 rcx=fffff80003007e80
rdx=fffff88008b2a920 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff88008b2a898 rbp=fffff680000d5000
r8=0000000000000000 r9=fffff80003007e80 r10=0000000000000000
r11=fffff88008b2a928 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e911e9 to fffff80002e91c40
FAILED_INSTRUCTION_ADDRESS:
+3839623231383732
00000000`00000000 ?? ???
STACK_TEXT:
fffff880`08b2a5b8 fffff800`02e911e9 : 00000000`0000000a 00000000`00000000 00000000`0000000c 00000000`00000008 : nt!KeBugCheckEx
fffff880`08b2a5c0 fffff800`02e8fe60 : 00000000`00000001 fffff800`030c7a80 fffff800`03007e80 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffff880`08b2a700 00000000`00000000 : fffff800`02ea170b fffff880`08b2a920 fffff800`03007e80 fffff880`08b2a900 : nt!KiPageFault+0x260
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02e8fe60 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\redaces\Windows_NT6_BSOD_jcgriff2\030812-19468-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`0304e670
Debug session time: Thu Mar 8 20:21:56.165 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:19.430
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff7ffabd5e3ac, 2, 8, fffff7ffabd5e3ac}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff7ffabd5e3ac, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff7ffabd5e3ac, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b8100
fffff7ffabd5e3ac
CURRENT_IRQL: 2
FAULTING_IP:
+3736303361366162
fffff7ff`abd5e3ac ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff8800874d510 -- (.trap 0xfffff8800874d510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000062b3e0
rdx=0000000000020e6a rsi=0000000000000000 rdi=0000000000000000
rip=fffff7ffabd5e3ac rsp=fffff8800874d6a0 rbp=fffff8800874d700
r8=fffffa800062b3e0 r9=0000000000000000 r10=fffffa8003900430
r11=fffff800030bba80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
fffff7ff`abd5e3ac ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e851e9 to fffff80002e85c40
FAILED_INSTRUCTION_ADDRESS:
+3736303361366162
fffff7ff`abd5e3ac ?? ???
STACK_TEXT:
fffff880`0874d3c8 fffff800`02e851e9 : 00000000`0000000a fffff7ff`abd5e3ac 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0874d3d0 fffff800`02e83e60 : fffffa80`00000000 fffffa80`03ac9310 00000000`00000000 fffffa80`00627ae0 : nt!KiBugCheckDispatch+0x69
fffff880`0874d510 fffff7ff`abd5e3ac : fffffa80`00671d90 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0874d6a0 fffffa80`00671d90 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff7ff`abd5e3ac
fffff880`0874d6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`00671d90
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02e83e60 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_nt!KiPageFault+260
Followup: MachineOwner
---------
-
Loading Dump File [D:\Kingston\BSODDmpFiles\redaces\Windows_NT6_BSOD_jcgriff2\030812-15038-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`03095670
Debug session time: Thu Mar 8 16:42:18.752 2012 (UTC - 7:00)
System Uptime: 0 days 0:14:56.001
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002edbce0, fffff88007edde10, 0}
Probably caused by : memory_corruption ( nt!MiCheckAging+50 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002edbce0, Address of the instruction which caused the bugcheck
Arg3: fffff88007edde10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!MiCheckAging+50
fffff800`02edbce0 48c1e80c shr rax,0Ch
CONTEXT: fffff88007edde10 -- (.cxr 0xfffff88007edde10)
rax=000007fffffeffff rbx=00000000000fff2e rcx=fffff800031025c0
rdx=0000000000000111 rsi=0000000000000000 rdi=fffff800031025c0
rip=fffff80002edbce0 rsp=fffff88007ede7f0 rbp=fffffa80040e0b60
r8=0000000000000111 r9=fffffa80034fde50 r10=000000000008815f
r11=fffff781c0000488 r12=0000000000000000 r13=fffff8a009bb8000
r14=fffff800031025c0 r15=0000000000000111
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!MiCheckAging+0x50:
fffff800`02edbce0 48c1e80c shr rax,0Ch
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002edbce0
STACK_TEXT:
fffff880`07ede7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiCheckAging+0x50
FOLLOWUP_IP:
nt!MiCheckAging+50
fffff800`02edbce0 48c1e80c shr rax,0Ch
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiCheckAging+50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
STACK_COMMAND: .cxr 0xfffff88007edde10 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiCheckAging+50
BUCKET_ID: X64_0x3B_nt!MiCheckAging+50
Followup: MachineOwner
---------
- Possible cause is drivers... (typically, though yours may be hardware)
- Possible cause is drivers... (typically, though yours may be hardware)
- You had this crash three times. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
Code:
AODDriver2 fffff880`05cf7000 fffff880`05d28000 Mon Dec 19 00:30:03 2011 (4eeee7fb) 00018588 AODDriver2.sys
Remove: AMD Overdrive, Gigabyte Easytune6, or AMD Vision Engine Control Center from your computer. It uses the above driver which is known to cause crashes on some systems.
I suspect memory problems despite you passing Memtest. And when you say Memtest, do you mean Memtest86+?
What BIOS version are you running? What is the date of the current version? Start Menu -> type into Search programs and files: msinfo32 -> hit enter.
Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
Also, go into your BIOS and post all Voltages (CPU, RAM, NB, IMC, etc.) and all RAM settings (timings, frequency, etc.)
Thanks to Dave76 for help learning RAM Stability