Solved Windows 7, winload 0x00000e9 I/O error

[chris7021]

file: windows/system32/winload.exe
code: 0x00000e9
info: an unexpected I/O error has occured.


This comes up after a fresh install of Windows 7 Ultimate. I have done plenty of research but I cannot find anything about this error. Can someone please help?

hmm thats a pain in the a_ _ job. well here are some quick solutions:

1) if you have the OS dvd, do the "repair my pc" by booting from the dvd. If it doesnt work after the first try, doit like 3 times in a row.

2) Remove the hd and leave it out for like 30 mins and then put it back. Most of the time it works on me after i do a fresh reinstallation on a laptop (windows 7).

3) if both tips dont work on you, then it might be a hd issue (do the hd test on the bios).

4) last try is just do the reinstallation again, if it happens again and the hd is good it must be a motherboard issue. is it a DELL? cuz if its a new DELL. some of the new DELL inspirons have some issues with the USB ports.

1. Well first off it detects the hard drive and I can actually install the OS onto it.
2. Will that work on a Desktop as well?
3. I searched the entire BIOS for the HD test and no luck on finding it.
4. It is a combination of manufacturers, it has a Cool Master tower case with a Emachine motherboard and Seagate hard drive, that is IDE, while the DVD is SATA.

Does this help you out?

KIND OF..

1) but still doesnt boot to windows right?

2) yeah that works too on the desktops. by the way i just did that on a dell inspiron 3000 desktop that im working on it and it worked fine (windows xp). did a fresh reinstallation on it and when it finish doing some updates it didnt boot up (missing files). so i just disconneted and i left it for 1hr then plug it back and it boot up with no problem.

3) oh wow that sucks then.. custom desktop?

4) yeah thats k. doesnt matter.


i think with the experience i have with IDE hard drives it seems that you might need to get a new 1. and is it possible you can install a SATA hd instead?

 

[countryb]

ISO Image, but I know for a fact that the ISO is not damage in any way because I use it in VMware, and Virtualbox and those always work perfect.

 

[countryb]

Well I was able to turn a 8 GB MicroSD Memory Card with a USB Adapter into a USB Bootable Device so I will install this and see if it will work.

 

[countryb]

Ok Well I tried the 8 GB card install and the same error, so I am going to try a different version of Win 7 and see how that works.

 

[Bobbyb]

Sorry not to hijack your thread, but I am in the same boat as you right now. I was hoping I could get some help with out starting another thread.

I've done hours of trouble shooting, with no avail. 1st off the reason I did a clean re-install was because my machine was soo slow everything was lagging. With nothing running every thing was not responding or taking forever.

So after the clean install, my monitor stopped coming on, the monitor is fine I checked its just not getting a single. So I turn the machine off wait 20 minutes and turn it back on and the monitor came back on. So ok, but then the winload.exe error.

So I re-installed 3 times, twice with the same disk, and once with a new copy. My monitor would fail to come on when Windows Install reboots the machine the 3 or 4 times. In the end I have the same problem, winload.exe error.

I read this thread and I'm starting to think I may have some bad sectors on my HDD or its just going bad. (to add when, I've done clean installs on this machine 3 time throughout its life and never had problem with a second HDD or having my wireless keyboard plugged in)

So what do you guys/gals think? Could a bad hdd stop the computer from sending video single to the monitor? I'm gonna try to do a chkdsk now.

Thanks, and again sorry to OP no hijack intended.

 

[TVeblen]

The reason for doing diagnostic tests is to rule out all other possible explanations for a problem before accepting the obvious, but costly reason: the hardware is damaged or defective.

The worst diagnostic method, IMHO, is just replacing parts until you find the broken one. Or discovering it was a software problem.

But if you have satisfied yourself that you have tried everything you can to correct the installation, check the devices and drivers, and test the hardware then it is time to try a replacement.

The most important diagnostic test that both of you do not want to miss is the hard drive diagnostic utility program, downloaded from your hard drive manufacturer's website, ISO file burned to a CD, and booted from the CD to run. Don't skip it!

 

[countryb]

Well in the end, I ended up just replacing the Hard drive and Data cable, so now I have it working, I am just thankful I have alot of extra cables and drives.

Thank you for all your help

 

[TVeblen]

Glad to hear you are up and running!

 

[Caltrin]

0x00000e9 I/O error possible solution

Though this thread is like several years old, maybe this solution can still benefit someone...

Through several processes of elimination we have found only one solution that works for this issue.

In the BIOS under "boot options" the "launch csm" entry is set to ALWAYS. (standard)

Change this setting to NEVER, making sure the HD is selected as first boot option; save and reboot.

If like me, your drive is empty and technically ready for a fresh install, the system will tell you it has "not found bootmgr" or something like that which is only logical.

Reboot again, enter BIOS again, and set the option back to ALWAYS.
Save and reboot once more, enter BIOS and now select the DVDdrive as first boot option.
Save and boot again to find your system now willing to boot from the Win 7 ULT install disc (in my case).

Hope this helps!

 

[placemat]

errors loading Win 7 to SSD...

I followed EVERY thread possible to sort out this problem. With me it ended up being my removable drive tray. I have 3 separate drives, video editing, audio production and flight simulator. The flight sim drive is the SSD and the other two drives are WD Blue drives. Win 7 64bit loaded perfectly to the WD drives but the SSD would load windows but upon the first reboot it would come up with the 000000e9 error etc. The very last attemp of salvation was when I removed the SSD from the tray and connected it directly to the power and SATA cable. It then loaded perfectly. I put it back in the tray and it had the problem again, so I've transferred it to a new tray and all is well.
This may help someone!

 

[placemat]

Update to previous post...

Well, to my surprise, it started happening again as soon as I changed the removable boot HDD to a different one with Win 7 installed. Then when I changed drives back to the SSD that was previously working, it was coming up with the error text again.
I currently now have 3 removable boot drives that are all working fine. The problem was that somewhere along the line, a windows installation installed some boot files onto one of the internal slave drives. There were no partitions and I couldn't find ANY rogue files on any of the drives. Drastically I had to wipe all of the internal HDDs, by removing the partitions and reformatting them. Once they were all blank, I reinstalled windows on each of the removable HDDs WITHOUT any slave drives installed. I then powered down, hooked up all of the slaves and each boot drive then picked them all up. All load into windows fine. I stupidly hadn't backed up every last file so I have lost some important stuff, but that's a hard lesson learnt.
It's the long haul now of loading everything back on again!:shock: