- Jul 26, 2009
- 4
- 0
- 18,510
Hi everyone,
I currently have an Asus P6T, i7 920 c-step, CNPS 9900 HS, 6gb 1600 OCZ platinum DDR3 memory, 2 BFG 285gtx OCX in SLI, and 1000w PSU to juice it. With that said, and who knows how many have before, I'm not entirely new to overclocking or computers, however I'm running into a concrete wall with the overclocking.
I've searched countless forums and tried countless suggestions, guides, possibilities, but am unable to push my cpu past 3.3 with all settings auto. I have updated every component that could be updated and although I'm sure I wasn't by the book I will try to note everything i did notice wrong that raises a few questions in my opinion.
Now, I did not go from the grassroots settings and raise the clock/voltage in 10 or so increments at a time - adjusting voltage as needed ... and I know most have you have labored endless hours to get the results you did, as i should...But when i follow a rough bios settings equivalent of "forum poster/computer article" and tweak as necessary nothing I do helps the near seconds of instability and blue screen PRIME 95 causes after initiating.
So if i was at about 3.8, 1.35v on both vcore/qpi, ram speed toward the default side, all spectrums disabled, turbo off, lowest qpi/uncore necessary i would boot into windows...hell, try a few games without problems(although they're not a stability test by any means) as soon as i ran prime 95 within minutes it would crash - with temps around 70-75(TJunction)....I'd usually up vcore/qpi and try again - the same bsod. Just to see if voltage was even an issue i would put it at about 1.42 to see if it could make it to the second thread of prime tests...nope.
I have tweaked using dozens of other nearly identical setups, upping and decreasing as needed. No luck. Now while i can see how this is lacking any solid numbers, or maybe clarity and i can get any add. info you need, but some of the potential problems i thought might be causing it were when i tried a different stress test...Everests' included stability test and unchecked everything but cpu, 10+ minutes without a problem versus the on the clock crash prime produced after just under a minute.
I dont know if that's indicating or showing a likely weak link, but when i did check cpu and fpu and tried the test again it copied prime's signature death kiss. It's getting fairly frustrating which I'm sure is part of the game, but i was hoping someone might have an idea what could be causing wall. I know all cpu's arent able to hit the norm...But, i figured it was worth a shot. Lastly, i'm not positive on this but i read somewhere that with a 3.8 or so OC, a handful of peripherals and 285 gtx in sli with modest overclocks that it might be pushing 800-900 watts under full load. I know prime doesnt put 100 percent on each component but maybe it could be a 1000w PSU that was "always" reliable can't hack it's expectations?
Thank you for any help guys... I appreciate it
I currently have an Asus P6T, i7 920 c-step, CNPS 9900 HS, 6gb 1600 OCZ platinum DDR3 memory, 2 BFG 285gtx OCX in SLI, and 1000w PSU to juice it. With that said, and who knows how many have before, I'm not entirely new to overclocking or computers, however I'm running into a concrete wall with the overclocking.
I've searched countless forums and tried countless suggestions, guides, possibilities, but am unable to push my cpu past 3.3 with all settings auto. I have updated every component that could be updated and although I'm sure I wasn't by the book I will try to note everything i did notice wrong that raises a few questions in my opinion.
Now, I did not go from the grassroots settings and raise the clock/voltage in 10 or so increments at a time - adjusting voltage as needed ... and I know most have you have labored endless hours to get the results you did, as i should...But when i follow a rough bios settings equivalent of "forum poster/computer article" and tweak as necessary nothing I do helps the near seconds of instability and blue screen PRIME 95 causes after initiating.
So if i was at about 3.8, 1.35v on both vcore/qpi, ram speed toward the default side, all spectrums disabled, turbo off, lowest qpi/uncore necessary i would boot into windows...hell, try a few games without problems(although they're not a stability test by any means) as soon as i ran prime 95 within minutes it would crash - with temps around 70-75(TJunction)....I'd usually up vcore/qpi and try again - the same bsod. Just to see if voltage was even an issue i would put it at about 1.42 to see if it could make it to the second thread of prime tests...nope.
I have tweaked using dozens of other nearly identical setups, upping and decreasing as needed. No luck. Now while i can see how this is lacking any solid numbers, or maybe clarity and i can get any add. info you need, but some of the potential problems i thought might be causing it were when i tried a different stress test...Everests' included stability test and unchecked everything but cpu, 10+ minutes without a problem versus the on the clock crash prime produced after just under a minute.
I dont know if that's indicating or showing a likely weak link, but when i did check cpu and fpu and tried the test again it copied prime's signature death kiss. It's getting fairly frustrating which I'm sure is part of the game, but i was hoping someone might have an idea what could be causing wall. I know all cpu's arent able to hit the norm...But, i figured it was worth a shot. Lastly, i'm not positive on this but i read somewhere that with a 3.8 or so OC, a handful of peripherals and 285 gtx in sli with modest overclocks that it might be pushing 800-900 watts under full load. I know prime doesnt put 100 percent on each component but maybe it could be a 1000w PSU that was "always" reliable can't hack it's expectations?
Thank you for any help guys... I appreciate it
I double checked everything you didnt mention was on auto and entered the values as you listed but windows couldnt boot. I tried upping the voltage a little to see if that'd help, maybe a a slim percent room for varying boards/configs - but couldnt boot with the 1.3v i tried. I left vcore on auto to see what would happen and it made it into windows, CPUZ said the vcore was a 1.312, but still failed after a few minutes of small--fft prime 95 testing. Ugh, well - no one said it was easy right...Thanks anyway though
Facebook
Twitter
Instagram