Printable View
Is that voltage not a big high..Quote:
Originally Posted by iddqd
Im hoping to get 3gig from my chip, but I was hoping to use less voltage than that.
With th DFI UT I get array problems very easily, I bought a £15 Si sata raid card and it fixed all those sorts of problems.
IMO, that voltage (1.75v) is very high. My Newark didn't respond favorably at all to vcore that was any higher than 1.7v. But hey, iddqd's core stepping looks to be a tic better than mine, so maybe 1.75v+ will bring better results... :toast:Quote:
Originally Posted by Holst
The nForce SATA does indeed suck, however if you disable it, you can still use the other one, Marvell chip SATA which works just fine.Quote:
Originally Posted by Holst
As I have said many times before (and I'm sure this isn't the last) the "Detecting Array" message appears every time you boot. It's completely normal. However, usually it would fly by so fast, you can't even see it. However, when your CPU (or other components) are unstable, this would typically be the first thing that it crashes on, hence, you get to look at it for a few seconds, until the system reboots. Never limited my overclocking (i get BSODs in windows way before I run into array detection thing)
As for the voltage, 1.75 is nothing. I've tried as high as 1.95 with this chip, although it doesn't seem to improve stability. I haven't pushed past 2978 I can boot at as high as 3.2GHz, but it BSODs a lot (and that's only if i turn MBM off, otherwise, system freezes at MBM initialize)... I suppose I could try my luck in suicide shots, but then again, I think suicide shots are bull:banana::banana::banana::banana:.
suicideds may be pointless, but they're hella fun :D
i'll laugh at your 1.95v now though, that's quite a lot of voltage ;)
also.. while it is kinda useless, how high can you get the htt/fsb?
thats wierd i can get prime stable at 2880 at 1.625 on air at 240htt 1:1
and i have wenbt to 242 for the 2.9 thingie but 1.65 wasnt even enough for me there so im guessin maybe mem limited there or maybe not..
drop the ram divider to find out :D
Hmm... that's the thing. Not much past 250. Hell, it's unstable even at 250. I dropped all my multipliers/dividers to lowest to find out... it wouldn't even boot at 300 (it used to work fine with the claw). It seems that's what's holding me back. 255HTT = bsods, array detection freeze. Maybe I need a new BIOS? (250 crashes a lot)Quote:
Originally Posted by ozzimark
that's strange.. how are you getting to 3.2ghz then? 250*12 = 3.0 ;)
(or maybe boot simply means post)
and.. if that's the case.. hmm. take out all your sata! :p:
It does boot at 265. By no means stable. I've tried 300, and it doesn't boot at that anymore. haven't tried anything in between.
edit: i don't think this has anything to do with my sata. I could get over 300 mhz with the claw.
edit2: boot = boot into windows logon screen.
that really is strange. the only thing i can think of left is either the ht link multi or that the clock generator on your newark hates you :(
I just think that it's time to ditch the 6/28 betas for something more suited to mobiles.
i've done most of my overclocking with 5/4 modded.. it's served me well. i just want my >1:1 dividers :p:
i asked you where i could get a modded bios, but instead you linked me to the official site. :stick:
my bad *hides*
i forgot you have that bh-5 ;)
thanks for the linkage new-b!
i am searching for that prozessor but i cant find an europe online shop who sells the cpu??!! :confused:
Quote:
Originally Posted by JimPanse2k5
thats true...i cant find it in europe.....
can someone explain this to me? i reinstalled the TDX cause the tubing was messing with the mount... :confused:
http://www.xtremesystems.org/forums/...id=35214&stc=1
Bug in the bios maybe either that or you horribly screwed up mounting the block and its burning itself to death.
If its a bios bug it might require flashing to a different bios to get rid of it.
definitly not a bios bug, as nothing was changed aside from a remount of the cpu
if it was too hot, it wouldn't be stable at my normal overclocked settings, which it appears to be
checked with speedfan, it's fluctuating between -122 and -124c, regardless of load :confused:
edit: my guess would be that i did the same thing as conrad.. broke one of the little chips. mine happened to be with temp reporting? *shrug*
I've seen a few posts about these wierd temps (always -123 too?? ) but some had this on 2 or all 3 temps.....so I would think it has to do with a bios and or temp monitoring chip problem. I know one person said it went away after a few reboots.
well i'll unplug the computer.. typically that fixes many weird problems.. hopefully this is the same
edit: nope..
simply turned off and back on.. no change
unplugged.. still the same
cleared bios, load optimized defaults.. nope
oh well :p:
I've had that with my clawhammer. When running high vdimm, the temperature reported became something preposterous, like 125C or something.
For future reference, the height of the Newark core is the same as all the Athlons/AthlonXP cores, which I measured to be 0.78mm +/- 0.005mm. Therefore, a shim made for AthlonXP will be the correct height. They run for about $6-7 each, so you could just butcher one, if you're afraid of damaging your CPU.
would a shim like this work for say a De-ihs'd 2800+ newcastle? cause if it does, ill be all over it. cause thats my biggest fear, killing the chip cause of cracking it.
heh, it's not the core itself i'm worried about, but the little things around it :