Page 1 of 1 |
Gwuffy
Posts: 73
Location: Australia
|
Posted: Thu, 16th Feb 2006 07:32 Post subject: Cpu Ucode error |
|
 |
Recently install a celeron 2.8 775 cpu onto a ASUS p5s800-vm
Ive done this same combination a zillion times for customers.
But 2day on boot im getting
"Intel CPU uCode load error"
changed motherboard and cpu
using a 3ghz processor gives no error but 2x 2.8's ive been given this error
anyone know what the error is or how to fix it??????????
nananananana leader
nananananana
BATMAN
I mean Leader
|
|
Back to top |
|
 |
|
Posted: Thu, 16th Feb 2006 10:06 Post subject: |
|
 |
What Xp edition are you using?
A BIOS update can help, use a DOS boot floppy.
Reality is booring...
|
|
Back to top |
|
 |
pancake
Posts: 1091
Location: England
|
Posted: Thu, 16th Feb 2006 12:00 Post subject: |
|
 |
yea i would try and look for a new bios or maybe a older one as perhaps they removed suppoort for older chips in a newer bios
|
|
Back to top |
|
 |
Gwuffy
Posts: 73
Location: Australia
|
Posted: Thu, 16th Feb 2006 13:06 Post subject: |
|
 |
MariusED : not that xp edition would be relevant since this is on post. with no hdds attached. but it was xphome....
With the bios. i guess i should do it. but ive never come across the problem b4 and the bios is the same as another 2.8 and same board
nananananana leader
nananananana
BATMAN
I mean Leader
|
|
Back to top |
|
 |
kosmiq
Posts: 2304
Location: Somewhere
|
Posted: Thu, 16th Feb 2006 16:46 Post subject: |
|
 |
broken CPU's or perhaps chinese overclocked and reselled ones?
Just a thought, seen it happen with AMD Athlon XP's.
Behold his GLORY! Bow for the technical master!
|
|
Back to top |
|
 |
|
Posted: Thu, 16th Feb 2006 16:58 Post subject: |
|
 |
I'm sorry but I just had to register to let MariusED know that he/she is a fkn retard. Seriously dude, you really have NFI what you are talking about.
I'm really sick of backyard wannabe cowboys who just bought their first computer and think they know eveything about the universe, coming into forums and dispensing nonsensical advice about things they know absolutely nothing about, just for the sake of increasing their postcounts and trying to be cool because they think they have the solution to the worlds PC problems by asking which XP version they are using, then suggesting a BIOS update! I mean WTF!? What help is that? At least 'pancake' was thinking when he suggested the possibility that the manufacturer had removed support for the processor in question.
I have some sound advice for you MariusED... STFU unless you have something usefull to say... mmmkay?
/rant
Now to the problem at hand...
Motherboard manufacturers will rarely (if ever) remove support for a particular processor. The ASUS P5S800-VM has support for the Celeron 2.8GHz natively. However, there have been several revisions of the Celeron 2.8GHz since it's original release. Support for the different revisions are as follows...
*Celeron D 335J (2.80 GHz, 533 FSB, LGA775) .......... Since BIOS (ALL)
*Celeron D 336 (2.80 GHz, 533 FSB, LGA775)E0,EM64T .......... Since BIOS (1007)
*Celeron D 336 (2.80 GHz, 533 FSB, revG1, LGA775) .......... Since BIOS (1016.005)
The complete processor compatability list can be found here --> http://support.asus.com/cpusupport/cpusupport.aspx?SLanguage=en-us&model=P5S800-VM
My first suggestion is to check whether the motherboard is set too 533 FSB or 800 FSB (for which it was designed). Maybe the mobo can do this automatically depending on which processor is inserted? I have no idea. Best to check the manual.
The second suggestion is, that while you have been performing this operation for quite a while, a new Celeron 2.8 revision has been released. This will cause problems if you are not using the most recent BIOS. Perhaps when you tried the 3GHz proccessor it WAS in fact compatible with the current BIOS and did not cause a problem. In which case flashing the BIOS to version 1016.005 may provide a solution (easiest way with ASUS products is to boot up with a CPU that works and use the ASUS Update Utility from within Windows, it's next to foolproof). If that's not an option and you need to go the DOS path i'll speak to you in IRC lol.
Right now i'm drunk and in desperate need of sleep, gotta work in 5 hours ffs. Hope that has cleared up something. If not... I'll be back.
P.S. MariusED, stfu.
|
|
Back to top |
|
 |
kosmiq
Posts: 2304
Location: Somewhere
|
Posted: Thu, 16th Feb 2006 17:55 Post subject: |
|
 |
I am pretty sure Gwuffy knows how to flash a bios through DOS so no need to speak with him in IRC I think.
And I am not with you on the AsusUpdate thing. I would never flash the m/b bios through windows to be honest. I simply would not trust windows that much. Using either a discette or a CD-rom to flash the bios in DOS is the only way to do it IMHO.
Adding the fact that Asus pretty much screwed up AsusUpdate for A8N32-SLI Deluxe when it was released does not make me trust them more. Just think about it, the manufacturer of the motherboard failed to make a flash utility for windows that works as intended. Some people could flash, some people could not even run it, for others it crashed... I will never touch that thing again!
Also registering in order to just whine on someone is kinda low IMO. And in the end you suggested the same thing as him. Flash the bios, only you have some whine in it and a little more technical stuff.
Behold his GLORY! Bow for the technical master!
|
|
Back to top |
|
 |
[sYn]
[Moderator] Elitist
Posts: 8374
|
|
Back to top |
|
 |
Gwuffy
Posts: 73
Location: Australia
|
Posted: Fri, 17th Feb 2006 00:04 Post subject: |
|
 |
Bios update didnt fix it... so that still leaves me at stage1....
*edit*
Decided to go for broke and do the beta bios and it appears to be working....
no error
nananananana leader
nananananana
BATMAN
I mean Leader
|
|
Back to top |
|
 |
kosmiq
Posts: 2304
Location: Somewhere
|
Posted: Fri, 17th Feb 2006 01:36 Post subject: |
|
 |
Gwuffy wrote: | Bios update didnt fix it... so that still leaves me at stage1....
*edit*
Decided to go for broke and do the beta bios and it appears to be working....
no error |
Ok, nice that it worked out for you. Make sure you do some serious stability testing before it goes to your customer though.. could get some nasty errors otherwise.
Behold his GLORY! Bow for the technical master!
|
|
Back to top |
|
 |
Page 1 of 1 |
All times are GMT + 1 Hour |