Sign in with
Sign up | Sign in
Your question

Cannot stress test OC settings.

Last response: in Overclocking
Share
July 31, 2008 6:09:27 PM

I couldn't find any related threads/questions/etc on this issue so here it is:

Asus P5K Motherboard
Intel Core2 Q6600 Quad Core (GO) CPU (Overclocked=3.6GHz [400x9] VCore=1.4625v [reported by CPU-Z = 1.36 - 1.39v])
Swifteck H2O-220 Compact 3/8IN Dual 120MM CPU Liquid Cooling Kit
OCZ NVIDIA SLI Ready XTC PC2-8500 4GB 4X1GB DDR2-1066 CL4-5-5-15 240PIN DIMM Dual Channel Memory Kit
FSB:D RAM ratio 3:4
OCZ EliteXtream OCZ1000EXS 1000W ATX12V 20/24 Pin Active PFC ATX PSU

Temps stay below 50'C as reported by Core Temp.

First time OC'ing any system.

I cannot run neither Prime95 nor OCCT, even before I started to OC (I wanted a baseline)
I did want to increase the OC but not before I can stress test the current settings.

Any help/suggestions would be appreciated. Thank you.

More about : stress test settings

July 31, 2008 10:40:24 PM

What is the exact problem in running PRIME95/OCCT? What happens when you try to run them? Also, have you downloaded and run memtest86+ through at least two complete passes without errors to make sure the basics are stable?
August 1, 2008 12:34:21 AM

Both programs crash as soon as the test is started.
Have not run Memtest86+. New build, default settings, shouldn't the memory be OK?
Related resources
August 1, 2008 2:53:50 AM

As a follow-up, just ran Memtest+ v2.01. 2 complete passes, wall time 1:01:08. NO errors.
This test was run using current overclock settings.
August 1, 2008 7:29:04 PM

I think you meant "memtest86+". That's good to make sure the basics are running right.
When you say both Prime programs "crash" right away, do you mean they report errors, or that the program hangs/disappears? I'd re-install Windows and Prime/OCCT to make sure it's not just that Windows and/or Prime have become corrupted. Also, make sure you have set you DIMM/RAM voltage in the BIOS to the spec voltage for your specific model number DIMMs.

August 2, 2008 6:36:52 AM

RAM/DIMM settings are correct for the sticks: 2.1v, 5-5-5-15 (manual) for the speed (533.9 x 2 = 1067). Also had tried Auto, no diff (except Auto placed the timings at 5-5-5-18).
EPP confirms the settings.
Windows was re-installed once, and both Prime95 and OCCT were re-installed several times to make sure I was using the most recent and an x64 (Vista) version.
Both programs hang and crash as soon as testing is started.
I get no reports from either so I believe they won't run under x64.
This is why I am posing the question, as I am hoping I am wrong.

August 2, 2008 8:26:34 AM

surely high end gamers with 64 bit OS's and high end gaming machines would be running those stress programs! i mean, who would be running an sli rig with 4 or 8GB of RAM with a 32 bit OS that holds em up!
August 2, 2008 2:38:41 PM

So any solutions?
August 2, 2008 10:44:11 PM

Sorry, I assumed you were running 32-bit Windows; 64-bit can make a BIG difference, mainly because a lot of drivers/programs haven't been updated for it yet.
August 2, 2008 11:30:57 PM

First set your RAM to 1:1 then, I'd guess you ned to increase the vcore a tad more. You've obviously have it at least boot stable (getting past that damned vista screen is such a tease :)  ), however to get it to bench stable you'll need a few more tiny vcore increments to get it at 24/7.

Once your bench stable then tweak the RAM, to be honest running it 1:1 maybe quicker even at 400FSB (test with super PI 1M test). If you want that RAM used then lower the multi to 7 and eek the max FSB from the mobo. A good board can hit 500 with a little tweaking 520 you only need 515 so maybe a goal to reach :D .
August 3, 2008 12:32:04 AM

"Intel Core2 Q6600 Quad Core (GO) CPU (Overclocked=3.6GHz [400x9] VCore=1.4625v"

Somehow you missed that. I am running 400FSB, with a x9 multiplier.
Max FSB on my Mobo would be 800.
My ultimate goal is 3.9G. (434x9)
August 3, 2008 12:34:40 AM

^800MHz FSB?!?!?! i hope you meant RAM LOL... best overclocking board on the market can only get to like 700MHz and thats with liquid nitrogen i assume :o 
August 3, 2008 3:26:39 AM

According to the mobo manual, FSB can be anywhere from 200-800MHz, entered directly from the keyboard (page 4-17, FSB Frequency).
That is were I got the FSB numbers from. I kid you not!
I just changed the RAM ratio to 1:1 and added 1 step higher to the V-Core voltage (now 1.475). Booted OK.
Then I attempted to play with higher FSB numbers (like 420, 434). Changed the RAM ratio to 1:1 to match. Upped the Vcore (in increments) to 1.525. Hardware crash every time, both FSB values. Since I am only using stock coolers on the North- and South-Bridge chips, would that have anything to do with the hardware crash at those higher speeds?
August 3, 2008 3:41:19 AM

yeah - i dare you to try 800MHz FSB rofl....u need 1600MHz RAM, and the QDR resulting from that is *!*3200MHz*!* i highly doubt that is possible with ANY mobo and cpu...
August 3, 2008 3:42:54 AM

I didn't say I was willing to run at that speed.
August 3, 2008 6:07:06 AM

Might be onto something here. I changed the NB voltage from Auto to 1.4v
Then I changed the FSB to 421, RAM at 1:1, Vcore at 1.5375. I was able to boot and log into Windows, no hardware crash.
I ran SuperPIMod 1.5, it got as far as 10 loops completed (at 32M setting).
56'C core 1, 42'C at core 4. Max load it placed though was 65%.
Still cannot run Prime95x64.
I did find one recent post on another board, the author was able to run his Prime95x64 under Vistax64 by not loading his nVidia drivers. ??
(I have a nVidia card, drivers loaded).
August 3, 2008 10:17:08 AM

umm u dont have a spare old copy of 32 bit winxp or something to stress test it...might be a good idea to dual boot it?

lolz @ "I didn't say I was willing to run at that speed."
August 3, 2008 10:42:41 AM

no, I don't. Actually, I did have a copy, oem, but the oem number on the computer case it came with didn't work (some variation, I discovered, made it incompatible with my oem disk. I have since sold that case with the disk.
(namely, when I had enough pieces to put this build together).
!