Hello all,
I suffer regular BSODs and random reboots without any clear reason behind them.

Typically I grind until I can fix the problem, but this is a case when I am out of answers and very much looking to avoid reinstalling windows. Here is the pertinent system information:

CPU: AMD Athlon X2 4400
Motherboard: Asus A8N32-SLI
Ram: 2 x 1GB Corsair XMS PC3200
GPU: eVGA 7800 GT
PSU: Antec TPII 550W
OS: WindowsXP-SP2

MISC:
memtest86 - no errors
no OC'ing (processor/video)

I've attached a bevy of minidumps. I've also included a couple text files that I created via the instructions here:

http://www.techspot.com/vb/all/windo...minidumps.html

I only did two since I wasn't sure that they were coming out correct at all (not to mention it looks like nonsense to me).

I hope someone out there can help. Thanks in advance for any time you're willing to throw at this one.

Attached Files

BSOD_dmp.zip (89.4 KB, 4 views)

Here is the latest dmp and debug log ....

Completely clueless as this happened at 2:00AM .... perhaps my dog is moonlighting as a computer crasher.

Thanks.

Attached Files

dmp_420.zip (35.7 KB, 4 views)

desperately seeking help (bump)

still don't understand ...

yet another late night crash.

Attached Files

dmp_421.zip (32.7 KB, 4 views)

last attempt before I give up ....

I hope someone can help.

Attached Files

dmp_421-2.zip (33.5 KB, 1 views)

Hi,

From the stack trace of two minidumps (Mini041906-01.dmp and Mini042106-01.dmp), your windows is crashed after page fault. Probably the paging space is bad or faulty ram. Run chkdsk /r and re-allocate the paging space. Run memtest to stress test the ram.

STACK_TEXT:
88262b7c 8065e0aa 000000c4 00000090 ffdff120 nt!KeBugCheckEx+0x1b
88262b9c 8065e398 88262bc8 8065e95f 00000000 nt!ViDeadlockCheckStackLimits+0x6e
88262ba4 8065e95f 00000000 00000000 00000000 nt!ViDeadlockCanProceed+0x2a
88262bc8 8054a38d 89041ad8 00000050 89c026f8 nt!VfDeadlockDeleteMemoryRange+0x13
88262c0c 8054a95f 89041ad8 00000000 88262c28 nt!ExFreePoolWithTag+0xad
88262c1c 804e8f64 89041ad8 88262c58 8065d19d nt!ExFreePool+0xf
88262c28 8065d19d 80555d80 89041ad8 80656140 nt!ExFreeToNPagedLookasideList+0x1e
88262c34 80656140 89ea9578 03db3000 87dee7d8 nt!VfIrpReleaseCallStackData+0x15
88262c58 804ef8a9 00000000 87dee7c8 87dee7d8 nt!IovCallDriver+0xb8
88262c6c 804ef8d1 89c026f8 87dee812 87dee7e0 nt!IopPageReadInternal+0xf3
88262c8c 8051581e 89ea9578 87dee800 87dee7e0 nt!IoPageRead+0x1b
88262d08 8051f347 c0708c78 e118fa3d c0708c78 nt!MiDispatchFault+0x292
88262d74 80543568 00000000 e118fa3d 00000000 nt!MmAccessFault+0x877 <-- Page faulty
88262d74 aefa6f05 00000000 e118fa3d 00000000 nt!KiTrap0E+0xd0
WARNING: Stack unwind information not available. Following frames may be wrong.
88262dfc 00000000 e14a0008 e14a006d e1183008 SAVRT+0x34f05

Thank you very much for the response. I truly appreciate it.

I re-allocated the page file, ran chkdsk /r /f, and am currently on pass #4 of Memtest86 (w/o failures).

If it crashes again, I will post the dump file accordingly.

In the meantime, any other ideas?

Thanks,

Matt