Curse

MrGuildBoi · Sep 24, 2008, 05:55 AM // 05:55

I keep getting this error and was wondering how to fix it. I saw some solutions on google but it was all technical jargon to me. I think it said something about BiOS but I'm not sure what about it.

One Tall Amazon Btch · Sep 24, 2008, 06:45 AM // 06:45

Can you please post the message and what the maker of the motherboard is ??

Snograt · Sep 24, 2008, 10:39 AM // 10:39

Need a more info, MrGuildBoi - is it a new PC or is it an old PC and this has just started happening?

Possible cpu problem, more likely needs a BIOS flash.

(bet it's an Asus)

Elder III · Sep 24, 2008, 12:37 PM // 12:37

If you could take a screenshot of the error message that would be great... if not a quote and tell us what you were doing when it occurred too would be ok.

Snograt - maybe it's an ECS??? Lots of people having trouble with them of late. :/

MrGuildBoi · Sep 24, 2008, 10:27 PM // 22:27

My MoBo is ASUS P5K-E Wifi edition, old cpu started happening when more ram was put in i think.

Can't take screenshot of starting of CPU

but the message says

"Intel CPU uCode Loading Error
Press F1 to Resume"

When you press F1,

"Checking NVRAM"

And computer starts as normal.

Lord Sojar · Sep 24, 2008, 10:41 PM // 22:41

OH OH OH! Finally, a really cool thread!

The uCode on a processor is the identification code. Essentially what is happening is that your BIOS has been altered to where it can no longer ID the processor correctly. It can use most of the processors capabilities, but you will lose access to C halt states and dynamic systems.

The fix for this is easy actually. You simply need to flash a new BIOS to the board. This will update the uCode verifications and allow your BIOS to "see" newer model processors as well as graphics cards.

These errors are not too common, and are rather interesting. The real question is, why did inserting new RAM modules cause the error. The reason for that is that the CMOS settings you had were probably cached. When you installed the new RAM modules, the BIOS wasn't cleared. This caused the NVRAM (Non volatile RAM) to go through feedback to acquire these new configurations. A corruption in the uCode verification system probably occurred when IDing the new RAM modules. So now you know!

To flash your BIOS, all you need to do is go to ASUS website, and find your motherboards BIOS file to download. Once downloaded, ASUS should have a guide to your individual motherboard. Some manufacturers use a windows tool to flash the BIOS over.

Yours will use this:
Afudos BIOS update tool V2.36

The BIOS version you are looking for is this:
P5K-E/WiFi-AP BIOS 1102

You can find them here:
http://support.asus.com/download/dow...=P5K-E/WIFI-AP

MrGuildBoi · Sep 24, 2008, 10:51 PM // 22:51

Well, I think it happened after putting new ram in or changing to intel quad core not sure :P. Why is this a really cool thread? And I dl'ed the thing and got a file with a .ROM extention. Do I use the afudos thing with it?

EDIT: Found the afudos thing in bios utilities :P

Lord Sojar · Sep 24, 2008, 10:55 PM // 22:55

Use 2.29 then. Yes, .ROM files are for writing to the NVRAM (BIOS). Make sure you close all music players, browsers, and any other programs when you flash the new BIOS over.

This is a cool thread because it is an uncommon issue, and BIOS issues are always amusing to me because of my position.

And yes, it most likely happened when you put the new quad core in silly man! lol!!! But my RAM explanation holds (although the chances of that happening compared to this happening after a new CPU is installed is astronomical)

MrGuildBoi · Sep 24, 2008, 11:19 PM // 23:19

K Rahja.

BTW, completely offtopic but didn't want to make a new thread, but when I go to Sound and Audio Devices in Control panel and test hardware, it shows my microphone works but when in Vent, I get

Quote:

Originally Posted by Vent Error Message

"Unable to activate DirectSound for selected device.
DirectSoundCaptureCreate failed, hr = 88780078"

I searched and got weird answers like you need a codec but I don't know if that refers to a different sound card. lol i said video card

Lord Sojar · Sep 24, 2008, 11:55 PM // 23:55

Disable Directsound in the options menu, and just use the device itself for vent. It should be in the list. Or use the default system.

MrGuildBoi · Sep 25, 2008, 01:48 AM // 01:48

Ok, so back on topic. I dled the afudos thing and the bios .rom thing. i opened the afudos and all i got was a blank command prompt box. i tried putting the .rom in the same folder, same thing.

Lord Sojar · Sep 25, 2008, 03:27 AM // 03:27

Read the instructions on how to use it. Each manufacturer is different. I personally stopped buying ASUS products 7 years ago.