Unexpected I/O error 0xc00000e9 after install VLC, uTorrent

October 21, 2016 at 07:22:17
Specs: Windows 8.1, 16GB Crucial DDR4
Hello, guys!

Yesterday I've bought a new PC and successfully installed Windows 8.1.
After a few installations of software (vlc, utorrent...) I've had a blue error screen, after that I can't even get into login screen, windows just won't load "an unexpected i/o error has occurred 0xc00000e9"

I've tried to boot from usb with my windows 8.1, but after Asrock logo (sometimes even without it ) it is just a blank screen.
I can't get into safe mode either ( don't know how. F8 won't work ). First time I've managed to do this while booting the same usb, but now it won't work.

I've tried to install windows 10 on usb and oh yes... it booted after almost 2-3 hours of waiting and everything was very slow. I could not install it due to mbr error. Windows sees my SSD and HDD, so they must be fine, right?

So I installed a new copy of windows 10 into my usb ( gpt, fat32 ).

And... now I can't get past black screen after booting. I see basic screen with windows 10 + memory test. I select windows 10 install or recovery tools, I see Asrock logo and... black screen.

Same with windows 7. "Windows is loading files" and then there is just a black screen.

My motherboard is Asrock z170 Pro4s.

Help me please, I don't know what to do.

I am very sorry for my english.

Best,
Erik


See More: Unexpected I/O error 0xc00000e9 after install VLC, uTorrent

Report •

#1
October 21, 2016 at 07:39:35
Did you buy a brand new PC with no OS installed or did you build one? 0xc00000e9 generally indicates a hardware problem. It could be a failing HDD or just a problem with the BIOS settings. See the following:

https://appuals.com/how-to-fix-erro...


Report •

#2
October 21, 2016 at 07:49:31
@riider

Built Pc with no OS.

Hiren's:
Warning: the high memory area (HMA) is not available.
Additional low memory (below 640k) will be used instead.
Creating 64Mb Ram Drive as R:
Bad command or file name
Bad command or file name
Bad command or file name
Bad command or file name
Bad command or file name
Bad command or file name
Label not found.
R:\>

message edited by Erik94


Report •

#3
October 21, 2016 at 08:16:10
@riider
Built Pc with no OS.
Hiren's:
Warning: the high memory area (HMA) is not available.
Additional low memory (below 640k) will be used instead.
Creating 64Mb Ram Drive as R:
Bad command or file name
Bad command or file name
Bad command or file name
Bad command or file name
Bad command or file name
Bad command or file name
Label not found.
R:\>

Report •

Related Solutions

#4
October 21, 2016 at 08:24:28
Are you sure about the memory installed? Perhaps take out all the sticks (presuming there is more than one). Clean the edge connectors carefully with a soft pencil type eraser. Wipe edges afterwards with a tissue or similar. Replace one stick - carefully ensuring it's properly seated. Then remove it and re-insert.

If one stick is sufficient (enough memory) for the system to boot - try and do so.

If no joy, clean the second stick and try with that "single" stick as above. (Clean all sticks regardless too.)

If still no joy keep trying single sticks as appropriate; and finally insert all of them and try again.

Also have only one installed hard drive connected; obviously the one you want to install the OS; and ensure it's detected in the bios...


Report •

#5
October 21, 2016 at 09:46:20
Curious - did you do a bench build or just install all the hardware in the case without testing it 1st? I see your board has 4 memory slots - 2 x 8GB or 4 x 4GB? What about the BIOS settings - loaded defaults or manually configured? Have you tried testing the RAM with memtest? I did a quick search & found several hits regarding Hiren's & the HMA error. Try UBCD.

http://www.ultimatebootcd.com/

message edited by riider


Report •

#6
October 21, 2016 at 10:01:18
Build was made buy popular shop in my country.

I tried to remove SSD and windows boot installation is working fine with hdd only.

I did mem test previously and it resulted with no problems found.


Report •

#7
October 21, 2016 at 10:32:32
Upd: Tried to replace sata for ssd with the old one, still have this problem.
SSD is seen through UEFI, so cable must be stable, right? I am not good at this :/

What should I test with UBCD?

I might sound dumb, but I think that the main problem is somehow related to ssd read spead maybe? If it loaded that windows installer after a very long period of time ( a few hours ) and was very slow, maybe I should try to buy a new sata cable?

What do you think, guys?

UPD: ViVARD SSD Diagnosis resulted in 0% errors found on SSD.

message edited by Erik94


Report •

#8
October 22, 2016 at 20:45:23
So you have two hard drives--one SSD and one probably just SATA. Are both configured right in cmos/bios setup? You say the installation is working fine with the 'hdd'. So maybe it's a combination of the drives that's causing the problem? If you just have the SSD installed will windows install and work OK?

Your Hirem's errors seem like it's not seeing the ram and maybe the hard drive(s) correctly. Maybe you're using one of their older versions?


Report •

#9
October 22, 2016 at 22:35:17
Yes, I hava A-Data SP550 SSD ( Windows 8.1. is there ) + Western Digital 1TB HDD.

I don't know if everything is right in uefi, but I tried reseting it to defaults + checked safe mode ( disabled ) and ahci mode is selected ( not raid ).

I also tried to switch their priority ( same problem ), and after I have unplugged HDD, I still have black screen problem with Windows Boot.
Updated BIOS and drivers through UEFI panel.

I downloaded Hirens 15.2 a day before, this must be the latest version.

What else should I try in UEFI or maybe Hirens?

I've also replaced CMOS. Same black screen and i/o

message edited by Erik94


Report •

#10
October 23, 2016 at 02:45:42
It's probably best to check the motherboard or system manual for questions about configuring bios setup.

If the hiren's isn't working then don't bother with it. I can't speak for any particular version but those type disks are just a collection of often older public domain utilities that are supposed to help diagnose problems.

I'd still try an OS install on the non-SSD drive, with the SSD drive removed, and see how it reacts.


Report •

#11
October 23, 2016 at 05:55:22
I am installing Win10 on HDD right now. After that I will try to connect SSD back and format it, because I think that the problem is somehow related to the SSD drivers.

Report •

#12
October 23, 2016 at 08:50:04
Okay, I have installed Windows 10 on HDD and connected SSD back.

Win10 runs slower with SSD connected and some apps ( ssd scan + driver update ) won't work. Without SSD everything is fine.

Launch from SSD still results in i/o error

I somehow need to update drivers for SSD now :/


UPD: Everytime on windows launch from HDD I see
Scanning and repairing drive (D:)

when ssd is connected


UPD2:
Is it bad or ok?
oi64.tinypic.com/2jfnn83.jpg

message edited by Erik94


Report •

#13
October 23, 2016 at 18:11:31
In this case drive D: is the SSD?

Maybe there's a problem with the drive or it needs additional configuration. Here's the support page for that model:

http://www.adata.com/en/ssd/downloa...

You might want to download their SSD Toolbox and at least run the diagnostics.


Report •

#14
October 23, 2016 at 22:39:21
SSD is drive E.
D is somehow C's subdrive in this copy of windows, it's vey small.

I've checked it ( E ) with adata and it seems ok.

They problem I see now is the File Type = Raw for E.

Can't fix it with TestDisk or cmd command.

message edited by Erik94


Report •

#15
October 23, 2016 at 22:58:58
Ok, I have managed to format Raw to NTFS and now windows is loading fine from HDD. Software also is working better now + I see my SSD from My Computer.

Tried to boot from USB with SSD first in priority, still black screen.

Adata soft test resulted in 100% good for both HDD and SSD

And I still see i/o error while booting from SSD. SSD was formated.

message edited by Erik94


Report •

#16
October 24, 2016 at 00:20:19
A black screen when booting from USB may be more about what you're trying to boot up from USB and not involve the other drives.

You seem to only be having the problem when booting from the SSD. You might try reinstalling windows on that drive, making sure you delete the existing partitions and then have windows setup recreate them. If the problem persists and the SSD is still under warranty you should probably return it.


Report •

#17
October 24, 2016 at 00:27:52
So I should delete them all from working windows on hdd, right? (Partitions)

Report •

#18
October 24, 2016 at 00:41:33
I'd disconnect the HDD and only connect the SSD and do the reinstall.

Report •

#19
October 24, 2016 at 00:56:41
I can't get past i/o or black screen Boot while only SSD is connected

Report •

#20
October 24, 2016 at 18:43:16
Don't boot from the SSD. Boot from whichever drive has the OS installation disk (or files).

Report •

Ask Question