Mobile 2400+ OC woes, what went wrong?

S

shaocaholica

Limp Gawd
Joined
Aug 9, 2002
Messages
196
I just got a 2400+ mobile barton yesterday and my troubles keep getting worse. I popped it in and fired it up at the normal speed. Ran about 30min of prime95 and all seems good. So I get antsy and jack up the speed to 2.4. Fails prime95 within minutes. I suspect my voltage and ram are to blame. For some reason, my MSI KT3 Ultra2(KT333) will only let me go as high as 1.675V for this CPU instead of 1.825V which it lets me for older Athlons. So I back off to 2.3. Run prime95 for another 30 min and seems ok. I then play and hours worth of games. Go back into the bios and try to tweak my memory. Didn't gain anything there so I stayed at 2.3(170x13.5@1.675V). I deciced to run some more prime95....fail in 10 min. So I back off to 2.0ghz, fail. 1.8ghz, fail. Damn. Now Im underclocking at 1.4, fail again. I know its not heat since Im using an Alpha 8045 and the cpu temp never breaks 40C under load.

I guess I still have ~28 to return this thing. I turned the comp off and I'll try again after letting it rest for a few hours. Got any ideas what went wrong? I guess if it keeps doing this I'll have to RMA it.

Also, is there anyway to get my mobo to supply this cpu with more vcore?
 
Okay, run memtest86, your RAM might have flaked out on you. And don't run it for just 5 minutes, gotta let it go a few passes for assurance that's it not your RAM.

Plus, it worked just fine at stock right? I wouldn't think you'd have borked it, but RMAing after you overclock is a no-no.
 
It worked at stock speed for 10min. I guess I was hasty. I also tested the ram in my previous machine and it was fine. However, I have yet to do that in this machine. I guess I'll try that tonight.

As far as I can tell, I did not do anything harmful to the core at all. Stock barton voltage is 1.65 and my mobos max for this chip is 1.675. I've never 'broken' a CPU simply by running it at a higher speed before nor have I heard of anyone else. The only damage related incident usually involve over volting and over heating, both of which did not happen.
 
Yeah, running it at stock for just a short time really does nothing. I ran Prime95 on my machine at stock overnight to make sure it was stable.

It could be that you just have a bad CPU. Test the RAM with memtest in the current system, and if errors come up, test it in another system to make sure it's the RAM or not. Otherwise, you can probably point to the CPU if there's errors on the current machine, but none on the other.
 
You must log in or register to reply here.
Back
Top