BSOD error occuring since I settled on my o/c speed

[ShyGuy91284]

My CPU temps are within range (never over 51), and passed a Prime95 burn-in. I've got an A7N8X mobo, 1 stick of Corsair 3200 low latency memory, and a Barton 2500 o/c to 3000, stock vCore. i've been getting a BSOD lately with the error code "DRIVER_IRQL_NOT_LESS_OR_EQUAL". Another forum said that could be caused by overclocking and bad bios settings, but idk. Anyone here familiar w/ that being caused by o/c? I'm running my system at the stock speed for now to see if o/c is the problem. If it is, anyone know how I could fix it?

 

[pspada]

The simple way to find out is to set the system back to default parameters for a day or two to see if the problem goes away. If so, you can then gradually increase your oc on various components until the problem reoccurs.

I have indeed seen this error when overly overclocking my Winblows XP system.

 

[ShyGuy91284]

I'm doin that. But how can I stop that from happening if it is due to o/c? Cuz it must be caused by something w/ overclocking. vCore maybe?

 

[Loobusk]

damn , another reason why corsair memory is a no go .

 

[Icewind]

Just tonight, I had my 2.8 at 3.15 on PC4800-E, running at 2.75 on the VIDIMM for my Corsair 3700TWinX 1 gig ram. First UT2k3 gave me a strange error and refused to run again without rebooting. Then when I had my system sitting idle, the entire OS crashed and it said there was no boot drive. Needless to say I freaked and immediatly reversed back to 215 FSB and so far no problems.

Theres nothing wrong with your corsair memory. The problem with pushing the FSB so hard is that eventually the data becomes corrupt or inaccurate and your system begins to go haywire. This is the sign you can no longer push anyharder without increase voltage or changing your ratios if you have a P4 sytem. In this case, I have to change my FSB ratio to 5:4 now to increase OC any higher.

Overclocking involves alot of trial and sometimes scary error. Just part of the game.

 

[ShyGuy91284]

Lmao, he dissed Corsair memory, the 2nd best you can get (second to Mushkin).
back to 215? What were you running it at before? lol.

My o/c speed was 10.5x200 FSB. My mobo supports it natively, and the processor is a barton, so it's natively supported. So idk if I was pushing the FSB too far. So far, no BSOD w/ it at it's native clocking. I don't wanna stay like this though, lol. And I don't think the data would be going haywire. Prime95 had no problems. And that would determine corrupted data.

 

[Sideswipe001]

How long did you run Prime for?

I would still probably try giving your CPU a bit more juice. If the error doesn't come up at all on stock speeds, then it's obvious it's an overclocking issue. Try giving your CPU and/or RAM more voltage to see if that solves it.

 

[pelikan]

You may just need to reformat and clean install Windows.
When I find my max overclock it involves pushing the system past its limits and getting BSOD's and lock-ups and reboots. That tends to trash the registry, especially when the memory is pushed too far, or with too tight timings. A reformat and clean install of Windows is always necessary for me.

 

[pspada]

I've changed my mobo, cpu, etc numerous time, overclocking each successive setup as much as possible - and I'm still using my original Windows XP installation, and it continues to work perfectly fine.