New
#1
Windows 7 x64 BSOD
Background: The computer was running perfectly with 4 GB of OCZ DDR3 1333. I replaced the OCZ memory with 2 x 4 GB (8 GB total) ADATA DDR3 1600 at stock timings (9-9-9-24).
I ran Memtest+ for 3 hours with no errors. I installed Windows 7 x64 (RTM downloaded from TechNet) and got an error when installing updates. I eventually got all the updates installed and started getting random BSODs. I ran Memtest+ again and got errors after 7 minutes. I RMAed the memory and got and installed the replacement memory.
I ran Memtest+ for 3 hours with no errors. Windows 7 x64 installed and updated fine. Last night I got a BSOD, page fault in nonpaged area. I ran Memtest+ for 7 hours with no errors. I ran Western Digital Data Lifeguard Diagnostic for DOS from bootable CD and got 0 errors on the boot drive.
System specs:
Asus M4A79XTD-EVO with latest bios (2102)
AMD Phenom II X6 1090T
HIS Radeon 4650 with Catalyst 10.9 drivers
WD Caviar Black 640 GB boot drive
2 x WD Caviar Black 1 TB HD
Seagate 300 GB 7200 RPM SATA HD
Corsair TX650W PSU
Windows debug report:
Debug session time: Tue Sep 28 04:28:49.773 2010 (UTC - 5:00)
System Uptime: 1 days 5:27:16.801
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff880078bddb8, 1, fffff80002a66214, 1}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KeEnumerateKernelStackSegments+28 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff880078bddb8, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002a66214, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000001, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb50e0
fffff880078bddb8
FAULTING_IP:
nt!KeEnumerateKernelStackSegments+28
fffff800`02a66214 48894508 mov qword ptr [rbp+8],rax
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880031ed990 -- (.trap 0xfffff880031ed990)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880078b7000 rbx=0000000000000000 rcx=fffffa800ab2c060
rdx=fffff80002a65c20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a66214 rsp=fffff880031edb20 rbp=fffff880078bddb0
r8=fffff880031edbd0 r9=fffff88002fd9600 r10=fffff880031edcc0
r11=fffff880009b2180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KeEnumerateKernelStackSegments+0x28:
fffff800`02a66214 48894508 mov qword ptr [rbp+8],rax ss:0018:fffff880`078bddb8=fffff880078b7000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a2991d to fffff80002a7d740
STACK_TEXT:
fffff880`031ed828 fffff800`02a2991d : 00000000`00000050 fffff880`078bddb8 00000000`00000001 fffff880`031ed990 : nt!KeBugCheckEx
fffff880`031ed830 fffff800`02a7b82e : 00000000`00000001 00000000`00000000 fffff800`02c4b700 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x428ff
fffff880`031ed990 fffff800`02a66214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`031edb20 fffff800`02a66058 : 00000000`00000000 00000000`00000001 fffff880`031edcb8 fffffa80`0ab2c060 : nt!KeEnumerateKernelStackSegments+0x28
fffff880`031edbb0 fffff800`02a661a4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02a19f23 : nt!MmOutPageKernelStack+0x34
fffff880`031edc90 fffff800`02a71df0 : 00000000`00000000 00000000`00000080 fffffa80`06a0d9e0 fffffa80`06a0d900 : nt!KiOutSwapKernelStacks+0x11c
fffff880`031edd00 fffff800`02d21c06 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x48
fffff880`031edd40 fffff800`02a5bc26 : fffff880`02f64180 fffffa80`06a35600 fffff880`02f6f040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031edd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KeEnumerateKernelStackSegments+28
fffff800`02a66214 48894508 mov qword ptr [rbp+8],rax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KeEnumerateKernelStackSegments+28
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
FAILURE_BUCKET_ID: X64_0x50_nt!KeEnumerateKernelStackSegments+28
BUCKET_ID: X64_0x50_nt!KeEnumerateKernelStackSegments+28
Followup: MachineOwner
---------
Thanks for any help.
Quote