My technical journal.

Maybe useful, maybe not.
posts - 105 , comments - 45 , trackbacks - 0

PC down

Last Saturday my Windows 10 PC refused to boot


There was a problem with a device connected to your PC
An unexpected I/O error hs occurred
Error code: 0xc00000e9
The problem can happen when a removable storage device is removed while it's in use or is failing. Properly connecting any removable storage and restarting your PC may fix this problem.


This screen would display for a while and then the PC would reboot, only to fail again.

Tried the basics, such as rebooting, unplugging from the mains for a few hours and rebooting, glaring, all to no affect.

Yesterday I popped the drive into the data centre server array that sits on top of the fridge in the study. This was to see if I could get any useful data off the drive before playing with it.

First thing that happened was that CHKDSK kicked in for a looooong time, eventually creating a 4.4 MB txt file report. No-one wants to see that amount of error reporting on a disk drive.


Huge amount of "Deleting extended attributes set due to the presence of reparse point in file xxxxxx."
I've looked up Reparse Points but am none the wiser.

After moving all user data to a safer place, I put the (much emptier) drive back in my PC and powered up, only to see the same recovery error.

Went off to look for some USB sticks to make into bootable repair tools. The first one (from work) was dead. Second, some shiny marketing thing for Biztalk 2004, was detected but failed to load. While I was searching for more USB sticks, I noticed my faulty PC had a log-on screen...

Seemed that it must have been rebooting quietly to itself and eventually repaired whatever was wrong.

Logged on, checked the event logs and found that the drive had a bad block (well diagnosed, Sue). Must have a look in the CHKDSK log file to see if the problem was fixed when I moved the drive to the server. Otherwise, all my work would have been for nothing as the solution would have been to just let Windows keep rebooting until it magically cured itself.

Print | posted on Wednesday, April 27, 2016 11:13 AM |


No comments posted yet.
Post A Comment

Powered by: