• Notice regarding image hosts and attachments. See here.

Rare BSOD's on bootup

Associate
Joined
4 Jan 2012
Posts
7
Hello, every so often (Usually when my computer is turned off for an extended amount of time, overnight say) I would boot up the computer and the screen would have artifacts, white lines as such up until the windows loading screen then it would BSOD.

The problem presists after a restart and it ONLY occurs every few days or so, I've had it happen four of five times now with the same four to five days in between each BSOD. The only solution when it does happen, is to switch off the power by the mains and wait atleast ten seconds before turning it back on.

This has solved the problem every time it's happened and I've tried various things such as running Furmark for 20+ minutes, such intel burn test (30 times) On maximum without any errors, prime 95 for three hours without a single error. I've also tested ram with the windows inbuilt memory diagnostics without any problems and my next step will be to run memtest overnight (Hopefully tonight)

This is the error message I'm getting:
http://i44.tinypic.com/1052ys6.jpg

Other than this, I could say the system is running flawlessly on anything I've ran so far. Battlefield, Rendering on UDK and various other games.

System specs:

OcUK Geforce GTX 560ti 2048mb (Factory settings)
Corsair XMS3 2x4GB DDR3 1600MHz (I'm running the ram on 1333MHz as this specific ram requires 1.65v at 1600MHz and from what I've read, sandybridge systems dont support that much voltage running through the ram)
OCZ 650W Bronze PSU
Gigabyte Z68X-UD5 Intel Z68
1TB Seagate Barracuda 7200
I5-2500k 3.30Ghz sandybridge CPU (Overclocked to 4.5GHz)
OCZ Agility 3 60GB SSD
Antec Kuhler H20 920 CPU cooler

Regards
Aaron
 
Last edited:
After your BSOD's do you get minidumps?

Also, good idea to run memtest. From your picture it looks like a driver issue, according to google this has something to do with DirectX, I would update your graphics drivers and see if it fixed. I'd have thought the best thing to do is to reinstall Windows
 
I'm running the latest drivers which are 285.62 although I could give the latest beta drivers (295.51) a try and see if that solves anything.

If memtest doesn't report any errors and updating drivers doesn't solve the problem, I guess my next step is reinstalling windows.

And yeah, I've got dumps for each BSOD thus far.
 
Before resorting to resinstalling the OS have you tried removing the Graphics drivers & rebooting & reinstalling?

Also have you tried running your memory @ 1600mhz on 1.5v? Many modules (including mine) run at their full speed fine on 1.5v.
 
Before resorting to resinstalling the OS have you tried removing the Graphics drivers & rebooting & reinstalling?

Also have you tried running your memory @ 1600mhz on 1.5v? Many modules (including mine) run at their full speed fine on 1.5v.

I've read up and this specific ram requires 1.65v to run 1600Mhz, no big deal though I just tuned it down to 1.5v at 1333Mhz for now until I can afford to replace the ram to something that runs at 1600Mhz on 1.5v. I have also reinstalled the drivers, but it was from I think 275.51 to my current which is 285.61, I'll try a fresh reinstall of my current drivers to see if that helps.
 
Back
Top Bottom