New
#1
Random Windows 7 x64 BSOD - Need Help
Hopefully, I can get through posting this without another one. I just want to go on record that I have been working on this problem for weeks with no resolve. Currently, my system runs beautifully in Windows 7 Ultimate x64 until these random crashes occur causing BSODs. They are completely random, and happen when I'm just browsing the desktop, on the internet, in a game, whatever. They are frequent and of extreme nuisance.
I have run memory tests, hard drive tests, video card tests, board tests, etc., the whole lot, and everything comes back clean as a whistle. All GPU and CPU components have aftermarket cooling and run well below the normal temperature range when under load. I have the latest BIOS and driver updates for all my hardware components and have even tried older drivers and builds to resolve the problem, but to no avail.
Current system specs:
Motherboard: Gigabyte EP45-UD3R v1.1
CPU: Intel Core 2 Quad Q9550 2.8GHz (at stock clock for now) with aftermarket cooling
RAM: GSkill DDR2 1066 4GB (two 2GB Sticks)
Graphics: EVGA Nvidia Geforce 8800GT with aftermarket cooling
OS: Windows 7 Ultimate x64
I would like to point out that I built this rig less than a year ago, and it has run beautifully until a month or two ago when I've started getting these random blue screens. I have even sent my board and memory in for RMA, and have gotten replacements thinking that was the issue. Everything hardware tests perfectly.
On to the memory dump. When I use windbg.exe to debug the memory dump, it's always a random system component that is at fault. I have gotten almost every stop error known, and it always a different system component every time it crashes.
I will post the dumps periodically as they happen. This one occurred when I was trying to install Windows Debugging Tools for the first time:
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: fffff87fde4f844c, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88010b80145, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
WRITE_ADDRESS: fffff87fde4f844c
FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::StartPreparation+19
fffff880`10b80145 44894920 mov dword ptr [rcx+20h],r9d
MM_INTERNAL_CODE: 5
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
MODULE_NAME: dxgmms1
FAULTING_MODULE: fffff88010b5a000 dxgmms1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005bdf710 -- (.trap 0xfffff88005bdf710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88005bdfb04 rbx=0000000000000000 rcx=fffffa8005dca000
rdx=fffff8a00174fde0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88010b80145 rsp=fffff88005bdf8a0 rbp=fffff8a00174fde0
r8=fffffa800604ebd0 r9=0000000000000001 r10=0000000000000000
r11=000000000000001d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
dxgmms1!VIDMM_GLOBAL::StartPreparation+0x19:
fffff880`10b80145 44894920 mov dword ptr [rcx+20h],r9d ds:9060:a020=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b4eb91 to fffff80002ad0f00
STACK_TEXT:
fffff880`05bdf5a8 fffff800`02b4eb91 : 00000000`00000050 fffff87f`de4f844c 00000000`00000001 fffff880`05bdf710 : nt!KeBugCheckEx
fffff880`05bdf5b0 fffff800`02acefee : 00000000`00000001 00000000`c0000001 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`05bdf710 fffff880`10b80145 : 00000000`ffffd978 00000000`00000007 fffffa80`05dba000 fffffa80`05dbb750 : nt!KiPageFault+0x16e
fffff880`05bdf8a0 fffff880`10b77e34 : 00000000`c0000001 00000000`0000001d 00000000`00000000 fffffa80`05daf7a0 : dxgmms1!VIDMM_GLOBAL::StartPreparation+0x19
fffff880`05bdf8d0 fffff880`10b9265d : 00000000`00000000 fffff8a0`0174fde0 fffffa80`00000000 fffffa80`0604ebd0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x3a0
fffff880`05bdfaa0 fffff880`10b92398 : fffff800`00b96080 fffff880`10b91d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`05bdfc90 fffff880`10b91e96 : 00000000`00000000 fffffa80`06121530 00000000`00000080 fffffa80`05daf010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`05bdfcc0 fffff800`02d74166 : 00000000`03bfe2e6 fffffa80`05dc9060 fffffa80`036e5040 fffffa80`05dc9060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`05bdfd00 fffff800`02aaf486 : fffff800`02c49e80 fffffa80`05dc9060 fffff800`02c57c40 fffff880`01250534 : nt!PspSystemThreadStartup+0x5a
fffff880`05bdfd40 00000000`00000000 : fffff880`05be0000 fffff880`05bda000 fffff880`05bdf650 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::StartPreparation+19
fffff880`10b80145 44894920 mov dword ptr [rcx+20h],r9d
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::StartPreparation+19
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::StartPreparation+19
BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::StartPreparation+19
Followup: MachineOwner