New UD5 prob

BigBruiserAl

BigBruiserAl

BigBruiserAl

Soldato
Joined
11 Sep 2008
Posts
3,322
Location
Co. Durham
Hello peeps

well the build has been fine since i bought it (self assembled and o/c) booted TF2 last night and within 20 min got BSOD with:

"a clock interrupt was not received on a secondary processor within the allocated time interval"

Very odd i thought tryed again lasted maybe an hour and the same BSOD, tryed to do some crunching and BSOD after 55min...now google dosent really give a clear answer to it and looking for some help if any one can, more vcore,more vtt :confused:?
debaiting trying the ud5 9a bios but not sure on beta bios

Running F7bios
Temps do not go over 68c in game 70 when crunching
GFX 280 81c max load latest drivers
 
iv looked on some websites, it indicates that youll either have to reupdate/install your bios also did you look for upgraded system drivers as well?

if all those fail then the only thing i can think of is a fresh install of windows, btw whatos u runin
 
mmj_uk said:
That error is usually associated with overclocking the CPU too far, have you tested it's stable with Linx or similar?
Click to expand...

Hmm you could right m8, lowered the clock to 3.8 and has been crunching for nearly 3hrs at 100% usage. will try some tf2 after the baby goes to bed
Im running vista 64 sp2 by the way.
ok now there is not much diff running 3.8 to 4.0 in real world but will bug the crap out me that D0 cant do 4.0 stable and yes it can prime for over 3 hrs np....do you think it worth uping the vcore from 1.3 to 1.32 or something or maybe a touch more vtt? it cant a driver/bios problem if its running at 3.8 right?
 
It is, as mmj_uk says, a simple overclocking error on this particular board. It just means that your rig is unstable, and either needs more volts, less heat, or less speed - or a combination of the above.


I have to say that I find this board a profoundly average overclocker: both my i920's go about a 100MHz further on my standard P6T than on my UD5. And both tend to fail with this error.


M
 
Meridian said:
It is, as mmj_uk says, a simple overclocking error on this particular board. It just means that your rig is unstable, and either needs more volts, less heat, or less speed - or a combination of the above.


I have to say that I find this board a profoundly average overclocker: both my i920's go about a 100MHz further on my standard P6T than on my UD5. And both tend to fail with this error.


M
Click to expand...

Hmm ill try out 3.8 over the weekend if stable ill bump up to 4.0 again and vcore up to 1.32 sigh trust me to get a lemon of cpu i thought someting was up when the box came opened and damaged :(
 
BigBruiserAl said:
Hmm ill try out 3.8 over the weekend if stable ill bump up to 4.0 again and vcore up to 1.32 sigh trust me to get a lemon of cpu i thought someting was up when the box came opened and damaged :(
Click to expand...

1.32? You'll need to go higher than that to get your best speed - 1.34 at least.


M
 
Meridian said:
1.32? You'll need to go higher than that to get your best speed - 1.34 at least.
Click to expand...

It's a D0 though. He's right at the high end of the VIDs for a D0. My best C0 only needs 1.4V for 4GHz and the worst only needs 1.45V.
 
yeah think i read 1.4 is there max on Do right?

3.8 seems fine at 1.26 done 3hrs crunching and 2hrs TF2 no prob dam that 4.0ghz:p was running 4.0 with 1.30625 before hmm maybe it time to sux it up save for 32nm gulftown :D
 
I hear different things about Vcore on these processors..

Several people on XS told me that 1.55v is the max amount of Vcore for these chips, they even posted up a chart thing showing the Intel specifications to.

2u8dz6p.png
 
I dunno mate, but the guys that told me this was the max Vcore seem like knowledgable people.

Some of which have used these voltages for quite a while now with no adverse effects.

I personally wouldn't like to put 1.55v through my chip, but there are plenty of guys on XS doing it for extreme overclocking, I've seen some guys putting even more than this through when benching with LN2 and DICE.

Same goes for the 1.65v limit for RAM, there are people that have been using 1.8 to 2.1v for months on end with no problems at all, they say that so long as QPI is within .5v of your VDimm then it is pretty much safe, though again, I like to stay within 1.65v.
 
DavyBoy said:
snip.
Click to expand...

Cheers mate lowered the vcore to dead on 1.3 gave the vtt a bump to 1.3 using 191x21= 4.ghz and been crunching for 2hrs at 100% maybe best left there only downside is memory is running 1500mhz not 1600mhz. temps today after 2 hrs crunching is 67c. Should be more then enough to run Aion online smoothly on the 6th :)
 
Glad you got it sorted out mate, tbh, you aint gonna notice much if any performance decrease with your RAM running at 1528MHz..

You could probably get the timings tightened up a little to make up for it, my Dominators are supposed to be at 8-8-8-24-2T, but I have them at 8-7-7-21-1T and they are perfectly stable.
 
BigBruiserAl said:
Cheers mate lowered the vcore to dead on 1.3 gave the vtt a bump to 1.3 using 191x21= 4.ghz and been crunching for 2hrs at 100% maybe best left there only downside is memory is running 1500mhz not 1600mhz. temps today after 2 hrs crunching is 67c. Should be more then enough to run Aion online smoothly on the 6th :)
Click to expand...


There's no substitute for just trying things: every rig is different, and this is genuinely the only way to find out what works. I've found that one of my rigs like high QPI voltages for instance, the other likes low ones.


M
 
Meridian said:
There's no substitute for just trying things: every rig is different, and this is genuinely the only way to find out what works. I've found that one of my rigs like high QPI voltages for instance, the other likes low ones.


M
Click to expand...

yeah your right mate funny thing was it had been at those setting for maybe 2 months then started BSOD oh well:D
 
You must log in or register to reply here.
Back
Top Bottom