Damn BSOD...

R.C.Anderson

R.C.Anderson

R.C.Anderson

Associate
Joined
20 Feb 2009
Posts
2,260
Location
Ashton-Under-Lyne
Ok, so I've had this a few times over the last few days, I initially thought it was due to an updated network manager gadget I installed (as it first happened within seconds of installing it), however now, it's happened again, after I have removed it.

Unfortunately my PC resets too quick to be able to get what the error code it (although I've now remembered to disable auto restart, so I can get it next time).

Just before the BSOD, I get my monitors going blank (except the cursor), one, by one, with a couple of seconds gap between each screen going blank (centre screen goes black > 2 seconds > Right screen goes black > 2 seconds > left screen goes black > 2 seconds > BSOD

I did wonder if it could be a graphics glitch, but then I thought it's unlikely that each screen would go at a different time, if that was the case.

I've also thought, could it be a problem with my SSD (OCZ vertex 3), as I know some people have problems with OCZ drives, and I bought mine pretty soon after they came out, so would only have the early firmware.

So, anyone else had a similar thing & been able to fix it, or have any other ideas?
 
disable automatic restart and the BSOD should give you more ideas.
Go to Start> Control Panel> Sysytem> Advanced> Startup and Recovery settings>
Then untick the Auto Reboot Box
After that any blue screen will stay on.
 
what are the specs of the machine? any overclocking? are you doing anything in particular when it happens? have you checked your event logs at the time of BOSD?
 
Specs are in my build log, but to make it easier:

Asus P67 Pro
2500k
8GB Corsair XMS3
XFX 6950 (Unlocked)
All powered by a Corsair HX750

Currently, everything is stock (except 6950), as I haven't got round to OCing since I installed watercooling.

Not doing anything in particular, but each time, it's been whilst I've just been web browsing etc (never happened during a game)

I've checked the event logs, but can't see anything about it, only Kernel power errors, because of an improper shutdown...
 
I would certainly start the diagnostic ball rolling by starting to eliminate individual components.

Start with your memory.

Check that you memory is running at the recommended timings and voltage for the speed they are set to.

If your memory setting are correct, then test your memory by running only one module at a time and test that module in different banks. Repeat this process for each of the modules you have in all the banks, one at a time.
If all your modules fail in one bank but not the others then it's likely you have a faulty IMC or mother board. If one module fails in all banks but the others are fine, you have located faulty memory module. It’s just a process of elimination. Keep a note of what you are testing as you’re going through.
If your memory looks fine with one module at a time, repeat the process by adding back another module and retest until you are back to the full 8 GB. If the system works fine say on 6GB but not 8Gb, it could be a capacity problem which the chipset doesn't like.
Don’t worry about dual channel memory performance during the test. It’s irrelevant.

Your next port of call is the power.

You can use my guide here
http://www.huddysworld.co.uk/index....rking&catid=40:techie-talk-hardware&Itemid=72

See how that goes for now :)
 
Ok, well it doesn't seem to have happened again since I posted here (& remembered to turn off auto restart).

I have, however, noticed that every time I try to shutdown my PC, I get a message saying "sidebar.exe is preventing windows from shutting down" which I'm pretty sure started appearing at the same time the BSODs started, so think they must be related.

Anyone else had this & been able to sort it? I've tried disabling & re-enabling the sidebar, but it doesn't help (error went when I had it disabled, but came back, as soon as it was started again), seems like windows doesn't actually uninstall & reinstall, it just disables the ability to use it...
 
Unfortunately it has happened again today :(

Managed to get a photo of the BSOD this time at least, here it is:

EDIT: stupid thing doesn't give me a thumbnail preview, so I'll just link the photo here

I'm assuming that's a display driver issue (going by the file name starts with ATI) but I already have the latest drivers. If someone else confirms that it's a display driver issue, I'll do a driver re-install & hope that helps.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom