I just need some advice on the steps to solve a BSOD. My specific situation is at the end for anyone who cares to help with that.
The steps / order that I have come up with so far.
1. Determine what was running during crash (try to replicate)
2. Determine if any new software or hardware was installed prior to crash (remove and test)
3. Remove / replace RAM
4. Review crash log
5. Remove video card and use onboard video
6. Reinstall OS or reinstall image of drives
7. Test PSU (have no idea if this is possible)
Any suggestions on the order of this list or things to add remove.
Ok so my specific situation
Machine
Intel E8400
3 Gb Ram
Nvideo 8800 Gt
2 x HDD SATA
1 x DVD rom
1 x WinTV (tv tuner)
500 W antec (came with the case)
So far (my actual order of testing):
1. Determine what was running during crash (try to replicate)
- At first I thought it was steam (Killing Floor newest thing I installed)
- But crash would happen on file copy / web search etc etc
2. Determine if any new software or hardware was installed prior to crash (remove and test)
- Removed steam -> still crashed (at varying times)
- Removed HDD (the only thing, other that 2gb of ram, that I have installed since original build 1 year ago) -> still crashed (at varying times)
3. Reinstall OS or reinstall HDD Image
- Since my copy of vista was “yarred” I decided to install a fresh legal Win 7 (didn’t format drive) Install was fast and easy -> still crashed (at varying times)
- Don’t have an image of my C drive as its just my gaming computer, the only things I really care about are my pictures and music which is all backed up.
4. Remove / replace / Test RAM
- Removed the new RAM I bought two months ago -> still crashed (at varying times)
- Used Windows Memory tests no issues
I’m here now.
5. Review crash log
- I have the debug tool but I can’t seem to get it to load the symbols files
- So right now I have no idea how to actually review the log, therefore this step my be over my head.
6. Remove video card and use onboard video
7. Test PSU (have no idea if this is possible)
8. Replace PSU.
A few questions
1. Does ram testing actually rule out Ram as cause, or should I get other ram ot test?
2. My Video cards is super hot to the touch (fan is still working) could this be the cause?
3. Should I just jump to 8 and get a newer PSU
Cheers,
Posts
I never bothered with crash logs and the debug tool, most often my BSODs were logged into the event viewier (start> run> eventvwr.msc), if they weren't then there was a hardware failure (insufficient power, cpu locked due to overheating, etc).
RAM testing may or may not point out the problem. It's possible you could get errors and it not be the problem, or not get errors and it still would be the problem anyway. It wouldn't hurt to run a test anyway.
SC2 NA: exoplasm.519 | PA SC2 Mumble Server | My Website | My Stream
As far as solutions if heat is the problem, you can add fans, get a better case (I've always bought Antec. Build quality versus ease of use versus cooling they've always done it for me. Currently got a 900 v1, built several Sonata II machines), or underclock the GPU or CPU, depending.
You noted that an antec PSU came with your case. What case model?
How long have you been running this current setup? Any new power-intensive games? I sincerely doubt that it's insufficient power, but there is the chance that the stock Antec PSU skimped on the 12v rails.
My issue with the BSOD's we've been getting at work is that there doesn't seem to be a fix =/
Best advice ever, thanks. Stopped it from rebooting and read the full BSOD.
Found the the issue was with the afd.sys. I "Googled" well actually "binged" that shit and found that it was likely a network adapter error.
I have two network adaptors. One on my MB that vista does't support but Windows 7 does. And a pci card. I turned off the onboard one and I have not crashed since.
Its wierd the crashes started when I was using vista and the pci adaptor. The onboard adaptor was never on/used.
Also why the hell doesn't windoes dump the contents of the BSOD screen to a easily accessible text file?
It's generally not all that useful. This is a better way to debug BSODs caused by software.
http://tinyurl.com/d5r9v3
or the official Windows 7 RC Support Forum located here:
http://tinyurl.com/9fhdl5
They usually respond pretty quickly. This is especially useful if you can't find the answer through a quick search for the crash codes on the BSOD screen