Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Asus P9X79 Deluxe 0E error


  • Please log in to reply
7 replies to this topic

#1 Kilroy

Kilroy

  • BC Advisor
  • 3,413 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Launderdale, MN
  • Local time:10:24 AM

Posted 13 March 2016 - 10:20 AM

On boot or restart I get an 0E error which according to the manual means Microcode not found.  I've been searching for a few weeks and haven't been able to find what that means exactly, so I can fix it.  The odd thing is that it will eventually boot, taking up to 45 minutes of multiple attempts.  When it does boot I get the over clock failed message.  This has been going on for about two weeks.  The last Windows 8 updates hosed my Windows 8 install so I switched over to my Windows 10 drive, no change in problem.

 

I have replaced the CMOS battery, no change.

 

Once it is up and running things are fine.  I've taken to leaving it running so I don't have to deal with the issue, prior I would shut down when I was finished using it.

 

Any ideas or suggestions?  My machine details are in my profile



BC AdBot (Login to Remove)

 


#2 ScathEnfys

ScathEnfys

    Bleeping Butterfly


  • Members
  • 1,375 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Deep in the Surface Web
  • Local time:11:24 AM

Posted 13 March 2016 - 11:04 AM

over clock failed message.

If you replaced the CMOS battery that should have reset any overclocks, but were you running one prior to this issue?

 

Have you tried reflashing the BIOS?


Proud system builder, modder, and watercooler.

GitHub | SoundCloud | Keybase

#3 Kilroy

Kilroy
  • Topic Starter

  • BC Advisor
  • 3,413 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Launderdale, MN
  • Local time:10:24 AM

Posted 14 March 2016 - 09:13 AM

I didn't have any overclocks in place.  I haven't tried reflashing the BIOS, but will try that next.  The thing that gets me is that eventually it will work, so the code is there some where.

 

I shut it down this morning before going to work, so I'll see if I have the issue.  I really wish that Asus would give you some information on things you should look at when you have this error.  Without any information the error might as well be Me Not Work.



#4 ScathEnfys

ScathEnfys

    Bleeping Butterfly


  • Members
  • 1,375 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Deep in the Surface Web
  • Local time:11:24 AM

Posted 14 March 2016 - 10:21 AM

Hmmm... microcode... have you attached any new hardware recently?
Proud system builder, modder, and watercooler.

GitHub | SoundCloud | Keybase

#5 Kilroy

Kilroy
  • Topic Starter

  • BC Advisor
  • 3,413 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Launderdale, MN
  • Local time:10:24 AM

Posted 14 March 2016 - 01:18 PM

No, nothing has changed in months.  I just started a couple of weeks ago.

 

I downgraded the BIOS to 4701 from the Beta BIOS of 4801 that I had been running, again for quite some time.  So far it seems like the issue is resolved, it rebooted two times for the BIOS update.  Hopefully that's all it was.  Would have been nice if the manual said BIOS corrupted reflash BIOS when you receive error 0E.



#6 ScathEnfys

ScathEnfys

    Bleeping Butterfly


  • Members
  • 1,375 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Deep in the Surface Web
  • Local time:11:24 AM

Posted 14 March 2016 - 01:33 PM

Yea... let me know if you start having issues again.
Proud system builder, modder, and watercooler.

GitHub | SoundCloud | Keybase

#7 Kilroy

Kilroy
  • Topic Starter

  • BC Advisor
  • 3,413 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Launderdale, MN
  • Local time:10:24 AM

Posted 15 March 2016 - 11:38 AM

I officially declare the problem resolved. I have rebooted multiple times since the BIOS update and CMOS battery replacement and have not had any times that required multiple attempts. I no longer fear how long it will take to turn my machine back on if I turn it off.

#8 ScathEnfys

ScathEnfys

    Bleeping Butterfly


  • Members
  • 1,375 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Deep in the Surface Web
  • Local time:11:24 AM

Posted 15 March 2016 - 12:32 PM

Definitely strange, but glad it was a simple fix!
Proud system builder, modder, and watercooler.

GitHub | SoundCloud | Keybase




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users