A8N Sli users, oldie question

Soldato
Joined
24 Jul 2006
Posts
8,876
Location
Hoddesdon, London, UK
Is anyone using a high HTT bus? I'm diagnosing a mates overclock right now, under orthos load or 3dmark it internittenly cuts out (hard shut off), not everytime, sometimes it runs fine for 24+ hours looping 3dmark or orthos then sometimes it just cuts out in minutes.. Hes got an Opteron 165 @ 2.5Ghz (278x9), 1.5GB Kingmax Hardcore RAM and the HTT bus set to 4x (1112). I'm thinking it might be the HTT bus set too high. So far its going ok at 3x but since this problem is so intemitent i just wanna pick the brains of other A8N Sli users.

Specs are
Kingmax Hardcore 2x512 and 2x256 on 166 divider : 232MHz at 2.75v
Opteron at 2.51GHz : 1.4v (have tried it at 2.4Ghz and same issue, so cpu might not be the culprit)
PCie bus set to 105mhz
PCI bus locked to 33MHz
7600GT not overclocked
 
Well i might've gotten the solution, noticed anytime i run orthos and cpuz together i end up in a dead cut out i.e hard shutdown with no restart. Any ideas? Tried older versions of cpuz i had laying about with same result. Some clockspeed sensor/resource conflict?
 
I've had Prime95 refuse to play ball, but Orthos was fine for me, what version?



Also, you could lower the CPU's multi and then rake up the FSB by 5 or 10MHz. If the problem becomes more termittent then the HTT is too high.
 
See i built this rig about 2yrs ago for my mate, only now got it here to add a few more hdds and new cpu for him (later stepping Optie 170 that does 3Ghz on 1.4v, haven't put that in yet). It seems to be running Orthos just fine without cpuz opened, the second i open cpuz the entire pc conks out. I knew even back then that 300mhz was rock solid with a 4x HT, it primed for days and was 3d stable, also never gave any issues when he had it. The one thing thats different this time around is i'm using Orthos instead of dual prime (was orthos even around in 05?) and orthos also reads the clock speed intermittently, so i think theres a conflict between Orthos and cpuz wanting to read the clocks, it thats all i can live with that hehe.
 
Dropped the bus to 250MHz HT at 4x (1000MHz), cpu to 8x and RAM on 133 divider, did the same thing when cpuz was opened..hmmm :)
 
Update, installed fresh windows on a spare drive. So far its working fine with Orthos, coretemp and cpuz open. Orthos running over an hour now when before it crashed (hard shut down) in 5 mins with cpuz open. Suspect it might be some driver relating to AMDs dual core or maybe chipset related.
 
Back
Top Bottom