Hey all!
please see latest post, can even skip to it really..
-------------
JUst looking for more experienced OCers to chime in with a "ya thats happened to me before".
System:
P5e3 Premium. x48
Q9550 @ 3.4 ghz (1.3 volts, 8.5 x 400 FSB)
4 gigs Patriot DDR3 @ 1600 9-9-9-24 CR2 (1.92 volts)
FSB Strap: 333
I've bumped the NB and that FSB termination voltage just a tad too.
OK so here's what happened:
- I did keep getting Prime errors until I relaxed the ram timings. THis is strange because the kit is rated at 7-7-7-20 @ 1600 and 1.9 volts. But with CPU underclocked to 2/4 ghz and RAM at above relaxed timings 9-9-9-24 I ran prime using more memory and had no errors for like close to 20 hours...
ok it was the ram I figured... now we know thats cool... i can tweak later lets get the CPU up!
- so I put the multiplier back to 8.5 and this puts CPU at 3.4 ghz. Looking around though plenty of peeps at that speed with my CPU and less voltage. It does run fine though @1.32 volts but I peel it back and get a few degrees saved an no errors in prime for 10 hours @1.3 volts.
Then, I'm thinking well ok then things are going great! Maybe I can reduce the voltage a bit more. BUt I stop Prime running cause I have some things to do and figure I'll resume it in a bit. BSOD.
One the IRQ LESS OR NOT EQUAL, one talking about NTFS.sys, and one with no real sign of what went wrong all happening pretty quickly one after the other...
Now I downlocked back to 2.4 ghz by reducing the multipler - have been stable since then.
So here is why I need the sanity check:
- Prime ran under settings where BSODs occured for like 10 hours with no BSODs, rounding errors or anything...
- these BSODs happen with no change to settings that were good for all that Prime work...
I guess my inuition was saying: well if Prime ran for so long then why the hell these BSODs? Why no BSODS during the 10 hour prime run?
I have not reformatted this WIn 7 install for a long time.. lots of uninstalled devices and programs, recently took out two internal cards for a pro audio external interface and a consumer end USB card from creative labs for gaming. Was thinking maybe this could be a coincidence of windows deterioration - but then, I[m solid at lower CPU clock...
I dunno just confused. I see my cpu running at 3.4 with no voltage bump sometimes out there in forums. I am suspicious of the RAM: not running at rated timings even with low CPU clocks.
I am curious: could my RAM be causing these problems, and act in such a way that they only come out at higher cpu clocks? Or is this a sign my particular CPU really does need more voltage than others at the same speed? Have any of you passed long prime runs only to have windows instability after?
One last q: my mobo is used to providing 1.9 volts to the ram, but most kits out there now take less voltage, 1.65 cause of the i7s. Its no issue running a 1.65 kit in an LGA 775 board eh? My mobo is such that it doesn't turn up in many QVL lists cause of its age, I know my board was popular though if anyone has good suggestions for it lemme know..
please see latest post, can even skip to it really..
-------------
JUst looking for more experienced OCers to chime in with a "ya thats happened to me before".
System:
P5e3 Premium. x48
Q9550 @ 3.4 ghz (1.3 volts, 8.5 x 400 FSB)
4 gigs Patriot DDR3 @ 1600 9-9-9-24 CR2 (1.92 volts)
FSB Strap: 333
I've bumped the NB and that FSB termination voltage just a tad too.
OK so here's what happened:
- I did keep getting Prime errors until I relaxed the ram timings. THis is strange because the kit is rated at 7-7-7-20 @ 1600 and 1.9 volts. But with CPU underclocked to 2/4 ghz and RAM at above relaxed timings 9-9-9-24 I ran prime using more memory and had no errors for like close to 20 hours...
ok it was the ram I figured... now we know thats cool... i can tweak later lets get the CPU up!
- so I put the multiplier back to 8.5 and this puts CPU at 3.4 ghz. Looking around though plenty of peeps at that speed with my CPU and less voltage. It does run fine though @1.32 volts but I peel it back and get a few degrees saved an no errors in prime for 10 hours @1.3 volts.
Then, I'm thinking well ok then things are going great! Maybe I can reduce the voltage a bit more. BUt I stop Prime running cause I have some things to do and figure I'll resume it in a bit. BSOD.
One the IRQ LESS OR NOT EQUAL, one talking about NTFS.sys, and one with no real sign of what went wrong all happening pretty quickly one after the other...
Now I downlocked back to 2.4 ghz by reducing the multipler - have been stable since then.
So here is why I need the sanity check:
- Prime ran under settings where BSODs occured for like 10 hours with no BSODs, rounding errors or anything...
- these BSODs happen with no change to settings that were good for all that Prime work...
I guess my inuition was saying: well if Prime ran for so long then why the hell these BSODs? Why no BSODS during the 10 hour prime run?
I have not reformatted this WIn 7 install for a long time.. lots of uninstalled devices and programs, recently took out two internal cards for a pro audio external interface and a consumer end USB card from creative labs for gaming. Was thinking maybe this could be a coincidence of windows deterioration - but then, I[m solid at lower CPU clock...
I dunno just confused. I see my cpu running at 3.4 with no voltage bump sometimes out there in forums. I am suspicious of the RAM: not running at rated timings even with low CPU clocks.
I am curious: could my RAM be causing these problems, and act in such a way that they only come out at higher cpu clocks? Or is this a sign my particular CPU really does need more voltage than others at the same speed? Have any of you passed long prime runs only to have windows instability after?
One last q: my mobo is used to providing 1.9 volts to the ram, but most kits out there now take less voltage, 1.65 cause of the i7s. Its no issue running a 1.65 kit in an LGA 775 board eh? My mobo is such that it doesn't turn up in many QVL lists cause of its age, I know my board was popular though if anyone has good suggestions for it lemme know..
Last edited:
