DS3 weirdness

E

Eagle156

2[H]4U
Joined
Jan 21, 2006
Messages
2,242
I set the FSB to 333 X 8multiplier X 2mem multiplier. At POST it showed 333X8 = 2.6 like it should, but in Orthos I get 2.9ghz and in cortemp it shows it as (373.51 X 8.0). Furthermore, in CPU-z it shows the 2.6ghz freq while with Gigabyte's easytune program it states it as 2.9ghz, all while having them both open right next to each other. WTF?:eek:

BTW, I'm following Bill's o/cing guide and I'm using the settings he suggests (+.1v everything, 102mhz PCIE, 3.75vcore, etc.) and Orthos fails about 5 mins in with these settings. Before I had vdimm at +.0 (my RAM is rated at 1.8v) and it failed about 30 sec in, now with .1v it fails at 5min. Is my RAM the culprit? My coretemps are about 58C with orthos stress testing with the stock hsf, 40C idle. I'd think that the e6600 would handle such a mild OC with ease (got it in september 06, should be one of those highly overclockable ones right?).

EDIT: I changed my FSB to 332mhz in the bios and it still shows it as 373 in coretemp and all, however I've been running the blend orthos test for about 20 mins now and it hasn't failed , yet. I guess I have to go trolling on the interweb for 6 more hours before it's considered stable.:rolleyes: Is there a way to figure out if my cpu is actually running at 2.9 or 2.6ghz?
EDIT #2: BSOD while opening AIM (orthos running in the background for 25 mins). Back to stock I go.:( Any tips?
 
chewing on it, back in a bit.

ok easy bit first, Orthos and (stupidly enough Gigabytes own utility) Easytune dont know you reduced your mulit to 8, they assume its the stock 9 so 9x333 = 2.99, cpu-z is smarter and actually looks at what the mulit is so it calculates it correctly. Dont let it bother you, the First Law of Computing is that computers can and will lie to you. The Second Law of Computing is that you will lie to your wife about the actual cost of a computer or upgrade.

Think I read a recent post newest version of coretemp has freq wrong too, not sure, but just use coretemp for temps and cpu-z for the other info.

hmm temps seem ok , 333 x 8 aye, should do that easy, and with 2.0 mulit memory is running right on spec at 667MHz you gave it a little boost (a very good idea) , dropped it just one MHz and it stayed up a bit longer.


EDIT: drop the FSB to 300 and see what happens. I am thinking you need some air on the NB/MCH. Stick a finger on the fairly large heatsink near the cpu and try to slowly count to 5 (careful that sucker can get hot), did you have to pull you finger off before you got to 5 ? Still thinking. ( you shoul be able to do 2.8MHZ all day long, so somthing is going on. )
 
I'm testing 300X9X2 right now. The gold heatsink near the cpu is a little hot but I can stick my finger there for much more than 5 seconds. Same with the RAM. I assume the intel heatsink throws enough air around it to keep things cool. I'm thinking the RAM is the problem. Last time when I tried o/cing unsuccesfully I raised the ram timings a little but that just made it worse... BSODing on boot up. This would be so much easier if it had an unlocked mulitiplier so I could just overclock the cpu alone without the whole system coming under stress.

BTW, can I open other programs while orthos is running or just let it do its thing? And what's the best test in it to test overall stability?


EDIT: I've run it for 1 hour now, seems stable. Max cpu temp was 59c.
 
I'm running 334x9 w/ 2.5x DRAM multi and it survived Orthos for almost 2 hours. My setup is as follows:

965P-DS3 v2.0
E4300
2 GB OCZ Platinum XTC Series PC6400
XFX 7900 GS

Ran rock solid and didn't even get terribly warm with the stock heatsink. I bumped all my voltages as the guide suggested and matched the memory settings in the BIOS to the manufacturer's specs as suggested. I'd suggest checking your memory settings before swapping it out, just to make sure you're not going around and around with no results.
 
I tried 334 as well and it failed just a few seconds in. I'm testing 310 right now. Also, while ocing the fsb to around 333 I got a lot of short beeps at POST. I looked it up in the manual and apparently this means a "power error". Could it be that my psu isn't up to the task?
 
get a new mobo that thing is a pos

sorry i had the same mobo gave me weird stupid shit problems
then i got aDFI P-965-s all my problems went away
 
Eagle156 said:
I tried 334 as well and it failed just a few seconds in. I'm testing 310 right now. Also, while ocing the fsb to around 333 I got a lot of short beeps at POST. I looked it up in the manual and apparently this means a "power error". Could it be that my psu isn't up to the task?
Click to expand...


I have to check, is the aux 12V 4 pin power connector plugged in ? It is easy to miss it on a first time build.

that supply should be ok if its working correctly, its better than mine.

there is something simple we are missing, hang in there you will find it,

Set your ram like this, it should take it out of the mix, once we get the cpu acting right you can go back and tighten up the ram.
DRAM Timing Selectable_______ SPD __ [Auto]

I think the options read Auto/Manual it might say SPD I cant remember exactly, but anyway we want to let the ram use its pre-programed "universal" settings. double check your memory ratio is still 2.0 I seem to recall it would like to go back to auto or set some odd mulitplier if the machine resets the bios settings after a failed boot attempt.
 
I've set the DRAM timing schedule to auto and it was still unstable at 333. I'm not really sure why it would make a difference? After all, my manual settings were 4-4-4-12, same as the settings the ram is rated for.

Update: The max it will go is 320X9. I tried 325, it's unstable. Back down to 322, and still no go. Interesting thing I found in cpu-z is that my ram is actually at 5-4-4-12 when setting timings to auto and overclocking it to 320.

EDIT: Well what do you know, now 320X9 isn't stable. Failed just 4 mins in when previously, with the same settings, it ran for at least 8mins with the same settings before I closed it. Perhaps heat IS the issue? Also, I did the large FFTs test to supposedly test ram and it failed just seconds in. Now with the small FFTs test to stress the CPU it's stable. I've no idea why the ram would be stressed if it's actually being underclocked right now with the 2x ram multiplier.
 
Ok, heat isn't the issue. I took the side off and put a house fan running at max blowing into it and it was unstable at 320 X 9. I'm back at stock now; I've wasted half a day on this with no gain; still open to suggestions though. Maybe if I get some extra $$$ I could buy some Crucial Ballistix sticks, but I've heard this patriot ram oced well. *shrug*
 
Eagle156 said:
I've set the DRAM timing schedule to auto and it was still unstable at 333. I'm not really sure why it would make a difference? After all, my manual settings were 4-4-4-12, same as the settings the ram is rated for.

Update: The max it will go is 320X9. I tried 325, it's unstable. Back down to 322, and still no go. Interesting thing I found in cpu-z is that my ram is actually at 5-4-4-12 when setting timings to auto and overclocking it to 320.

EDIT: Well what do you know, now 320X9 isn't stable. Failed just 4 mins in when previously, with the same settings, it ran for at least 8mins with the same settings before I closed it. Perhaps heat IS the issue? Also, I did the large FFTs test to supposedly test ram and it failed just seconds in. Now with the small FFTs test to stress the CPU it's stable. I've no idea why the ram would be stressed if it's actually being underclocked right now with the 2x ram multiplier.
Click to expand...

I admit it, you got me on this one. It makes no sense. Something very simple is wrong but its not obvious, only thing I can suggest is to go through the whole build double checking everything, heatsink mounting, connectors tight cards seated you get the idea.
 
You must log in or register to reply here.
Back
Top