Forum Thread

Error 0xc00000e9 on Clean Windows 7 install on new build

helloha1 2,683 1,076 January 1, 2013 at 04:20 PM
I just finished a new build with a combination of old parts I had lying around and some slickdeals I managed to snag.

I have a ECS g41T-m7 motherboard (FAR, Woo!) paired with a q8300 I just grabbed used. I've got a SATA Samsung DVD burner and an old IDE ST3160021A (Seagate Barracuda 160 gig) and a 1 gig Crucial DDR3 stick. Don't criticize the components, the system was nearly free out of pocket woot

I'm trying to do a clean install with Windows 7 Pro. Every time I finish the install, the system doesn't boot, instead going to a black screen with Error 0xc00000e9 and a suggestion to run system repair. When I reboot, it shows the same error with a message either about an IO error or that the system registry file is missing, or corrupt.

I tried reinstalling 2 or 3 times and still the same issue. I saw people say that the DVD was a potential issue, so I created a bootable USB drive from the ISO and installed. Again, same issue. I've unplugged any unnecessary components including the DVD drive, leaving only the Hard drive connected. The error still shows up.

I looked it up and it seems a lot of people say this is due to a failed hard drive. When I was building, I did drop my hard drive a short distance (about a foot onto carpet), but it still passes the SeaTools long test (ran about 3 or 4 times). I also did a full wipe in SeaTools and tried installing windows, again no luck.

Is my drive shot, or is there anything I can do? Are there any BIOS setting I need to tinker with? It's been ages since I used an IDE drive... The jumper is set on Cable Select, and it's connected to the master on the IDE Cable...

TIA!

UPDATE: Looks like the hard drive's definitely fine. See my latest post.

19 Comments

1 2

Sign up for a Slickdeals account to remove this ad.

#2
Quote from helloha1 View Post :
I just finished a new build with a combination of old parts I had lying around and some slickdeals I managed to snag.

I have a ECS g41T-m7 motherboard (FAR, Woo!) paired with a q8300 I just grabbed used. I've got a SATA Samsung DVD burner and an old IDE ST3160021A (Seagate Barracuda 160 gig) and a 1 gig Crucial DDR3 stick. Don't criticize the components, the system was nearly free out of pocket woot

I'm trying to do a clean install with Windows 7 Pro. Every time I finish the install, the system doesn't boot, instead going to a black screen with Error 0xc00000e9 and a suggestion to run system repair. When I reboot, it shows the same error with a message either about an IO error or that the system registry file is missing, or corrupt.

I tried reinstalling 2 or 3 times and still the same issue. I saw people say that the DVD was a potential issue, so I created a bootable USB drive from the ISO and installed. Again, same issue. I've unplugged any unnecessary components including the DVD drive, leaving only the Hard drive connected. The error still shows up.

I looked it up and it seems a lot of people say this is due to a failed hard drive. When I was building, I did drop my hard drive a short distance (about a foot onto carpet), but it still passes the SeaTools long test (ran about 3 or 4 times). I also did a full wipe in SeaTools and tried installing windows, again no luck.

Is my drive shot, or is there anything I can do? Are there any BIOS setting I need to tinker with? It's been ages since I used an IDE drive... The jumper is set on Cable Select, and it's connected to the master on the IDE Cable...

TIA!
A quick google points to it could be a hard drive issue, A quick test would be to run it though the diagnostics by the manufacture.
Reply Helpful Comment? 0 0
....


...
Joined Nov 2009
L7: Teacher
2,683 Posts
1,076 Reputation
Original Poster
#3
Quote from mrbobhcrhs View Post :
A quick google points to it could be a hard drive issue, A quick test would be to run it though the diagnostics by the manufacture.
Yeah, as I mentioned I ran a long test in SeaTools [wikipedia.org] 3 or 4 times with no errors, I also tried doing a full wipe before installing... Still have the issue.
Reply Helpful Comment? 0 0
#4
Quote from helloha1 View Post :
Yeah, as I mentioned I ran a long test in SeaTools [wikipedia.org] 3 or 4 times with no errors, I also tried doing a full wipe before installing... Still have the issue.
Hmmm Missed that line, maybe try the other sata port? Maybe its the sata controller, you could try installing Ubuntu or another linux distro and see if it boots or also has issues.
Reply Helpful Comment? 0 0
Joined Nov 2009
L7: Teacher
2,683 Posts
1,076 Reputation
Original Poster
#5
Quote from mrbobhcrhs View Post :
Hmmm Missed that line, maybe try the other sata port? Maybe its the sata controller, you could try installing Ubuntu or another linux distro and see if it boots or also has issues.
It's an old IDE drive and I only have 1 IDE port on the motherboard. As far as I'm aware I have all the jumpers set up correctly and I think I'm fine on the BIOS end as well... The motherboard is brand new so all of the controllers should be working fine (hopefully)

I'm downloading ubuntu right now, let's see how that goes.
Reply Helpful Comment? 0 0
Last edited by helloha1 January 1, 2013 at 04:52 PM
#6
Quote from helloha1 View Post :
It's an old IDE drive and I only have 1 IDE port on the motherboard. As far as I'm aware I have all the jumpers set up correctly and I think I'm fine on the BIOS end as well...
Hmm I would still try the linux route.. if its a hardware issue it should show up there also.
Reply Helpful Comment? 0 0
Joined Dec 2007
L10: Grand Master
7,631 Posts
1,489 Reputation
#7
Quote from helloha1 View Post :
It's an old IDE drive and I only have 1 IDE port on the motherboard. As far as I'm aware I have all the jumpers set up correctly and I think I'm fine on the BIOS end as well... The motherboard is brand new so all of the controllers should be working fine (hopefully)

I'm downloading ubuntu right now, let's see how that goes.
Hi there! I'd try this [sevenforums.com] as from the reading of it, it worked for the user if you read the whole thread.
Reply Helpful Comment? 0 0

Joined Nov 2009
L7: Teacher
2,683 Posts
1,076 Reputation
Original Poster
#8
Quote from menace33 View Post :
Hi there! I'd try this [sevenforums.com] as from the reading of it, it worked for the user if you read the whole thread.
Quote from mrbobhcrhs View Post :
Hmm I would still try the linux route.. if its a hardware issue it should show up there also.
That actually basically details my troubleshooting process so far. Whenever I ran startup repair, it just failed saying that it was unable to fix any problems.

I also tried installing Ubuntu but the installer just got stuck. (this may just be a bad burn, I haven't checked yet)

Now after all of this, I figured that the hard drive was probably shot. Just for kicks, I decided to install it in my other system and try and install windows. The other system has an i7 920 on an AsRock x58 extreme mobo. Whaddya know, windows installed without a hitch.

Now I'm completely stumped. The hard drive isn't shot because I was able to install and run windows on another system with absolutely no issue. So it appears to be a hardware issue with my new build. I'm not sure where to start diagnosing this...
Reply Helpful Comment? 0 0
Last edited by helloha1 January 2, 2013 at 11:39 AM

Sign up for a Slickdeals account to remove this ad.

Joined Dec 2007
L10: Grand Master
7,631 Posts
1,489 Reputation
#9
Quote from helloha1 View Post :
That actually basically details my troubleshooting process so far. Whenever I ran startup repair, it just failed saying that it was unable to fix any problems.
Now it says in that article you may have to run Startup Repair like 3-4 times before it is able to fix so I'd recommend at least going through the process another 3-4 times.
Reply Helpful Comment? 0 0
Joined Nov 2009
L7: Teacher
2,683 Posts
1,076 Reputation
Original Poster
#10
Quote from menace33 View Post :
Now it says in that article you may have to run Startup Repair like 3-4 times before it is able to fix so I'd recommend at least going through the process another 3-4 times.
Yeah, I did run it quite a few times and it failed each time. Also, most of the people in that article had previously working installs before they got the error - my issue is on a brand new clean install (Tried clean installing 3-4 times).

Also, I ran Memtest 86+ to see if the RAM was bad, but it passed.
Reply Helpful Comment? 0 0
Joined Dec 2007
L10: Grand Master
7,631 Posts
1,489 Reputation
#11
Quote from helloha1 View Post :
Yeah, I did run it quite a few times and it failed each time. Also, most of the people in that article had previously working installs before they got the error - my issue is on a brand new clean install (Tried clean installing 3-4 times).

Also, I ran Memtest 86+ to see if the RAM was bad, but it passed.
Alright, did you try

System Repair Disc - Create
System Recovery Options
Repair Install

?
Reply Helpful Comment? 0 0
Joined Nov 2009
L7: Teacher
2,683 Posts
1,076 Reputation
Original Poster
#12
Quote from menace33 View Post :
Alright, did you try

System Repair Disc - Create
System Recovery Options
Repair Install

?
Haven't tried those yet, but those usually are to fix a previously working installation that has gone bad. I've done clean installs, which should be better than any of those options. I've tried installing windows 8 developer preview as well and I get the same error.

I'm beginning to think either the mobo or processor is bad since I've eliminated all the other components, but I'm not really sure how to go about narrowing the problem down...
Reply Helpful Comment? 0 0
#13
Without getting into nitty gritty my finger points to windows loosing track of the hdd ie its configuring itself such a way that it thinks the drive is drive x of the system on install but on load windows is setting it as drive y... problem also makes me think of same problem but in regards to multiple hdd partitions on that drive. thirdly, if the mobo has raid (even if not being used) could be jumbling up the drive assignments.
what partitions do you have on the drive?
are you completely blowing all partitions away when you setup windows?

when installing note what controller and drive # windows says your installing onto.
Does you mobo have raid drivers?
I had issues with my win7 build where I didn't account for the raid driver mucking things up:
http://globeadue.blogspot.com/200...te-ga.html
If your not using raid at all, maybe force disable it in bios and see if next install works?

you may need to get to a command prompt pre and post install and see what diskpart command can tell you about drive assignments...

Also when windows installs and asks if you have any raid drivers, might try installing providing the raid drivers.

Good luck
Reply Helpful Comment? 0 0
#14
I presume that you don't have a spare hard drive to try in the ECS machine, but if you do have one or you don't mind wasting a bit of time, you could shrink the drive in your i7 PC, make a partition to install Win 7 onto in the ECS machine, just to rule out a hard drive problem.

Now here are a couple of unusual suggestions, based on some unusual glitches I have run into in the past.
One is to put that IDE drive back into the i7 machine and do a slow format. I have had machines that would not boot XP, simply because I had done a quick format.
No, I've never seen it happen with Win 7, but you're running out of options, and that's the time when you have to pull out all your magic tricks.
The second one, might be the most promising.
Remove the jumper on the IDE drive and try the install again.
Cable select is for a double connector IDE cable that goes to two different IDE devices. There may be a jumper code map on the IDE drive itself for Master, but if there isn't, removing the jumper altogether often works.

I have presumed that you only have one IDE cable that you used on both machines. Is that correct?
If not, then try swapping out the cables, or if you happen to have any spare ones, just on the off chance that the cable is bad.
When diagnosing a computer problem, you have to keep your mind open to some things that don't quite add up. For instance, you might have a cable that could work on the i7 machine, yet it doesn't work properly on the ECS machine, so if you come to the conclusion that the IDE cable is good because it works in the i7 computer, you might never find the problem, assuming that is what it is, if you know what I mean.

To revise.... Installing Win 7 on another hard drive on the ECS machine will confirm whether the mobo/CPU/ram/PSU combo are good or not.
Removing the jumper on the IDE drive, or trying different positions, could possibly resolve the problem.
Do a slow format on the IDE drive, before installing Win 7 on the ECS machine.
Changing the IDE cable for another, couldn't hurt.
Reply Helpful Comment? 0 0
#15
Quote from globeadue View Post :
Without getting into nitty gritty my finger points to windows loosing track of the hdd ie its configuring itself such a way that it thinks the drive is drive x of the system on install but on load windows is setting it as drive y... problem also makes me think of same problem but in regards to multiple hdd partitions on that drive. thirdly, if the mobo has raid (even if not being used) could be jumbling up the drive assignments.
what partitions do you have on the drive?
are you completely blowing all partitions away when you setup windows?

when installing note what controller and drive # windows says your installing onto.
Does you mobo have raid drivers?
I had issues with my win7 build where I didn't account for the raid driver mucking things up:
http://globeadue.blogspot.com/200...te-ga.html
If your not using raid at all, maybe force disable it in bios and see if next install works?

you may need to get to a command prompt pre and post install and see what diskpart command can tell you about drive assignments...

Also when windows installs and asks if you have any raid drivers, might try installing providing the raid drivers.

Good luck
I like to keep my mind open to all possibilities, and a bios setting is one of them, but I can't see how drive assignments could produce the OP's problem.
It's been my experience that when a computer tries to boot from the wrong drive/partition, either you get a message telling you that it can't find a bootable device or you might get a black screen with a flashing straight line cursor at the top left, but never the error code that the OP gets.
I hope you understand that I'm only questioning this, based on my experiences and you may have run into something I don't know about, and there's a ton of stuff that I don't know about, so I'm all ears, specially when it's to resolve a mystery problem, such as what the OP has.
Reply Helpful Comment? 0 0
Page 1 of 2
1 2
Join the Conversation
Add a Comment
 
Copyright 1999 - 2016. Slickdeals, LLC. All Rights Reserved. Copyright / Infringement Policy  •  Privacy Policy  •  Terms of Service  •  Acceptable Use Policy (Rules)  •  Interest-Based Ads
Link Copied to Clipboard