The firmware makes your computer turn on and run. As long as your computer starts up, runs, and doesn't crash then the firmware is fine.

This is just a random thing about windows. Nothing to be concerned about.

Originally posted by Ontrix_Kitsune:

The firmware makes your computer turn on and run. As long as your computer starts up, runs, and doesn't crash then the firmware is fine.

This is just a random thing about windows. Nothing to be concerned about.

For some reason my video drivers keep crashing system, I am thinking if this has to do with video driver somehow, just several days ago I had bsod and then i went to microsoft forum and asked what is the cause (providing crash dump) of it and one dude pointed out it is caused by video driver so I installed new driver (old version). I am just getting worried if this is linked somehow.

Thanks for information!

Originally posted by Ice Scream:

Originally posted by Ontrix_Kitsune:

The firmware makes your computer turn on and run. As long as your computer starts up, runs, and doesn't crash then the firmware is fine.

This is just a random thing about windows. Nothing to be concerned about.

For some reason my video drivers keep crashing system, I am thinking if this has to do with video driver somehow, just several days ago I had bsod and then i went to microsoft forum and asked what is the cause (providing crash dump) of it and one dude pointed out it is caused by video driver so I installed new driver (old version). I am just getting worried if this is linked somehow.

Thanks for information!

It's probably not related. I mean it could be but unlikely.

Originally posted by Ontrix_Kitsune:

Originally posted by Ice Scream:

For some reason my video drivers keep crashing system, I am thinking if this has to do with video driver somehow, just several days ago I had bsod and then i went to microsoft forum and asked what is the cause (providing crash dump) of it and one dude pointed out it is caused by video driver so I installed new driver (old version). I am just getting worried if this is linked somehow.

Thanks for information!

It's probably not related. I mean it could be but unlikely.

alrighty!

I usually just uninstall it, usually reboot will fix it, but never had problem with specifically those stuff so dont quote me, maybe asus know more

Originally posted by ˢᵈˣ FatCat:

I usually just uninstall it, usually reboot will fix it, but never had problem with specifically those stuff so dont quote me, maybe asus know more

the thing is that restart does not help with this issue. maybe you are right here, i should contact asus then.

grab all the drivers from the mobo mfg site for that specific board

Originally posted by _I_:

grab all the drivers from the mobo mfg site for that specific board

and.......... what board is that?

post a cpuz validation link
http://www.cpuid.com/softwares/cpu-z.html
cpuz -> validate button -> submit button
it will open a browser, copy the url (address) and paste it here

Code 10 on the firmware means you have an invalid or corrupted firmware image.
Install the BIOS again, if you have the BIOS already delete that and download again in case that file is corrupted.
Also worth running System File Checker in case it's a corrupted Windows file causing the issue, in fact do it first as it's quick and easy.
Open Command Prompt as an administrator and run sfc /scannow

bios has protections to stop it from flashing a corrupt image or incorrect version

device manager is basically saying it does not know what those devices are so its not using them

I'm just saying what Windows is reporting and that's what Code 10 means in relation to what it shows in device manager, now it's not always right but these error codes are there for a reason and the place to start seen as there is an indication.
Call me crazy but I always assume it's better than a best guess or pulling ideas from the ether.

Also I've seen corrupt BIOS before both installed corrupt and gone corrupt, and like I said it could be a component on the Windows system side that need a repair.

Clearly no-one knows what the issue is. Check for a bios update, after that update chipset and drivers as required and make sure all windows updates are in.

At least then you can assume known base to troubleshoot from, assuming OP has the ability to do so.

Originally posted by Carlsberg:

Clearly no-one knows what the issue is.

I have an idea, BIOS and Windows communicate with eachother, now BIOS has a small amount of memory for Windows to write to and it could lay in there that's giving a error, or the Windows side of it.
That's why I say sfc /scannow as BIOS communication has nothing to do with drivers but it's part of Windows, or the BIOS needs installing again.