Stop Errors and Memory Dumps - Help!

fatehavoc

Junior Member
May 17, 2005
9
0
0
My PC has been getting BSODs for a while, maybe a year now. There's no real rhyme or reason to it. Sometimes it works fine, sometimes it hard locks (screen freezes, nothing responds, caps lock, etc.) and sometimes it BSODs. There is no real pattern in the stop errors, so I thought I'd list them all here. First, however, my specs:

DFI Lan Party UT NForce3 250gb
AMD 64 3400+ Clawhammer (1 MB L2 Cache)
2x 512 Patriot XBL DDR 400
ATI Radeon 9800 PRO 128 MB (256-bit, the real ATI brand card)
Western Digital Raptor SATA 74 GB drive.
Rosewill 550w power supply (I can supply more details if needed).

Currently running onboard Ethernet, Sound.
Using Windows XP SP2, updated whenever MSFT releases patches.
Driver for ATI is Catalyst 6.1. It still crashed with Catalyst 5.1.
Replaced card with GeForce 5200 FX, still crashed.
Using the 6.37 NForce drivers. Read about problems with that version ethernet driver, but not sure if that's the culprit.

Also has crashed while running Wireless on D-Link DWL 520+ PCI card. Card is currently disabled but doesn't seem to affect crashing.

Switching RAM from slot to slot has occasionally remedied problems for a small period of time. System runs cold - 80-90 F.

I have played with voltages, giving ram 2.6-2.8 volts. I have given CPU 1.5-1.55 volts. These do not change the problem.

I have the most recent BIOS, updated just this month from DFI's forums.

My Stop Errors are (most recent posted first):

(I left this one here in case anyone needed a quick preview)
The computer has rebooted from a bugcheck. The bugcheck was: 0x100000be (0xf71e0568, 0x073e1121, 0x80548d70, 0x0000000a). A dump was saved in: C:\WINDOWS\Minidump\Mini020106-02.dmp.

***I UPLOADED THE MEMORY DUMPS ONLINE, SO YOU CAN DOWNLOAD THEM NOW. i DECIDED THAT WOULD BE MORE USEFUL THAN A PAGE OR SO OF BUGCHECK ERROR MESSAGES.***

They can be found at http://www.personal.psu.edu/dag5001/Minidump-Fatehavoc.zip
. Let me know if there's any trouble getting them.

Thanks in advance for any advice and help.
I've been pulling my hair out about this for months, and it seems to go heavily in spurts. I'd really like to fix this once and for all.

-Fate
 

BadThad

Lifer
Feb 22, 2000
12,099
47
91
First thing to eliminate is heat, what are your temperatures running at? Next, take a close look at the inside. Everything is clean, i.e. not coated with dust, fans are running full speed, CPU cooler is attached well? Check EACH capacitor on the mobo, look for signs of bulging or leaking.
 

BadThad

Lifer
Feb 22, 2000
12,099
47
91
Also, a hijackthis log would be helpful so we can elminiate viruses and malware.
 

fatehavoc

Junior Member
May 17, 2005
9
0
0
I run MS Antispyware daily, as well as Symantec Corporate antivirus. I'm fairly sure it's virus free.

As for heat, like i said, it runs 80-90 degrees F. Right now i'm running open case, and ITE SmartGuardian says 70 degrees F. I've got a Zalman heatsink on it and it's attached properly. I clean it out every month or so, so dust shouldn't be a problem.

Whenever I open the case for cleaning, i look at all the capacitors, simply because I've read about capacitors being culprits for bad mobos and undiagnosable crashes. It doesn't look like any are puffing up or showing any signs of wear.

On a side note, the hardware is about 1 year old. The exception is the video card, (Radeon) which is about 2-3 years old, but runs fine on other machines.

-Fate
 

BadThad

Lifer
Feb 22, 2000
12,099
47
91
Originally posted by: fatehavoc
I run MS Antispyware daily, as well as Symantec Corporate antivirus. I'm fairly sure it's virus free.

As for heat, like i said, it runs 80-90 degrees F. Right now i'm running open case, and ITE SmartGuardian says 70 degrees F. I've got a Zalman heatsink on it and it's attached properly. I clean it out every month or so, so dust shouldn't be a problem.

Whenever I open the case for cleaning, i look at all the capacitors, simply because I've read about capacitors being culprits for bad mobos and undiagnosable crashes. It doesn't look like any are puffing up or showing any signs of wear.

On a side note, the hardware is about 1 year old. The exception is the video card, (Radeon) which is about 2-3 years old, but runs fine on other machines.

-Fate

The fan on the video card is running at full speed?

Another easy thing to do is run memtest86 on EACH ram module, only do one at a time using the bootable Linux version of memtest.

EDIT - Oh, and install ccleaner to get rid of all the dmp and tmp files on your system. Also, since those freaking debug files are basically worthless, stopl Dr.Watson from creating those damn things:

START>RUN>DRWTSN32

Uncheck all the boxes in the lower part of the window.
 

fatehavoc

Junior Member
May 17, 2005
9
0
0
Fan on the video card runs fine. I've run memtest on both modules for something like 18 hours without any errors.

As for ccleaner, i'm not familiar with it. What is it?

No crashes yet today, so I'm feeling a bit better.

Also thought I'd mention it crashes more when running World of Warcraft than other things. Not sure if that helps.

-Fate
 

fatehavoc

Junior Member
May 17, 2005
9
0
0
Can I analyze the past memory dumps or will this allow me to look at the problem "on the fly"? I've never used MSFT debugging tools so this is whole new realm for me.

-Fate
 

eshbach

Junior Member
Mar 13, 2005
14
0
0
Originally posted by: fatehavoc
Can I analyze the past memory dumps or will this allow me to look at the problem "on the fly"? I've never used MSFT debugging tools so this is whole new realm for me.

-Fate

The Microsoft Debugger is used for analyzing the .DMP files that are created when a Blue Screen occurs.

If you want me to look at them for you, just zip or rar your \Windows\Minidump directory and email it to me. Lea should be able to give you my address.
 

fatehavoc

Junior Member
May 17, 2005
9
0
0
I just sent them over. Let me know if you have any suggestions.

-Fate

EDIT: They're also posted online now, in the top thread. In addition, I tried looking at them with the debugger but I kept getting read errors with symbols. I installed symbols and set the path correctly (I think) but was getting strange errors. Hopefully you'll have more luck.