Dreaded BSOD

littledave · 31 Dec 2010 at 17:18

PC has been running fine for over a year now, however suddenly got the BSOD
irql_not_less_or_equal

PC wouldnt reboot into windows it seemed with my 3.8 overclock. PC is beening reloaded with win 7 as we speak on stock speeds.

PC is Intel Core i7 920 3.80GHz
Gigabyte EX58-UD5 Intel X58
Corsair 6GB DDR3 PC3-12800C8 1600MHz DDR3
Corsair H-50
GTX 280
Enermax Infinity 720W

My gut feeling is the memory has given up.

Can people advise as to the next steps was think about reloading completely, then slowly overclocking back up to 3.8.

Is the memory supposed to be ok with these speeds?

Maybe my BIOS settings are to blame i can post these up if needed

Sgt Tackleberry · 31 Dec 2010 at 17:21

Download memtest86 burn it to a disk or to a USB memory stick, boot up from it and I test you memory, then let us know how u get on with that.

littledave · 31 Dec 2010 at 17:26

Does it matter if im overclocked at the time?

MADEinSTOKE · 31 Dec 2010 at 17:29

I'd try memtest with it at stock first and if its ok then overclock and try again

Sgt Tackleberry · 31 Dec 2010 at 17:40

Have u tryed going back to stock and see if you get the BSOD?

littledave · 31 Dec 2010 at 18:28

Just finished reloading now, no BSOD's so far but im at stock speeds.

Have to try the memtest tomorrow, hopefully i wont be too hungover

bobert50 · 31 Dec 2010 at 18:43

Good luck

Sgt Tackleberry · 31 Dec 2010 at 18:47

That's good to here. Let us know how you get on.

Savvy · 31 Dec 2010 at 21:18

BSOD of that kind is defiantely hardware related

Justintime · 31 Dec 2010 at 21:20

Savvy said:
BSOD of that kind is defiantely hardware related

Software, drivers, hotfixes etc.. can do a good job of screwing your machine up. I had that exact error after i updated Kaspersky on a machine for instance, reload and downgrade to previous version and the machines been stable ever since, and has had the latest update without a hitch, likely a screwed up registry somehow. I agree though that the majority of time i've seen this was due to RAM or cpu.

Savvy · 31 Dec 2010 at 22:02

Justintime said:
Software, drivers, hotfixes etc.. can do a good job of screwing your machine up. I had that exact error after i updated Kaspersky on a machine for instance, reload and downgrade to previous version and the machines been stable ever since, and has had the latest update without a hitch, likely a screwed up registry somehow. I agree though that the majority of time i've seen this was due to RAM or cpu.

Personal experience with a P4 system and purple shirt brigade was the last voyage into vendor ****, On that occasion cpu was at fault. Most other times have being bad ram or psu.