Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: Can't boot after chkdsk. BSOD 0xED after the windows 7 logo.

16 Sep 2011   #1

Windows 7 Ultimate x64
Can't boot after chkdsk. BSOD 0xED after the windows 7 logo.

Hey. Okay.. My situation is my laptop was very VERY slow and i kept getting message on every program i opened like this:

"Internet Explorer has stopped working."
" has stopped responding."
"Skype has stopped working."

I figured it was a software/os issue so i re-installed windows with a clean install.
Same issues.

Now I figured it was a Hardware problem. So I tried removing one stick of RAM. When i turned the laptop back on. It gave me a chkdsk screen. I let it do its thing and it recovered some files and stuff so I thought, "Well, that might have fixed the problem. =D" So the computer restarted automatically. And after the Windows 7 Boot Logo... My laptop crashed. My face went from this: to this:

I got a BSOD that said:


Stop 0x000000ED

It only happens for like a split second, so I recorded it with my camera and extracted the picture from that video. That picture is in the attachments. Anyways.

So i tried switching the RAM sticks and still, the problem persists. That's where I'm at currently.

By the way,
I have Windows 7 Ultimate 64-bit

Any Help would be greatly appreciated!!
Thanks in advanced!

My System SpecsSystem Spec
16 Sep 2011   #2

Windows 7 Ultimate x64

Did you try the chkdsk /r method of checking the volume. Load up you installation DVD and click on the repair my computer when it gets to the install screen and then open a command prompt from there and type in chkdsk /r it will check the disk for bad sectors and it file system as well. I found some other solutions but I don't feel that they are applicable to you but I'll put them here anyhow:

Advanced troubleshooting

These methods are intended for advanced computer users. If you are not comfortable with advanced troubleshooting, you might want to ask someone for help, use the Microsoft Customer Support Services Web site to find other solutions, or contact Support. See the "Next steps" section for more information about the Microsoft Customer Support Services Web site.

Begin by reading the "Technical information about the error" section to understand why the error might be generated and the purpose of the message. Otherwise, you can skip this information and begin with "Method 1: Check the error message" to help you resolve the issue. Technical information about the error

This section provides some technical background about the cause of this error message and why it might be generated.

This behavior can occur if either of the following conditions is true:
  • Your computer uses an Ultra Direct Memory Access (UDMA) hard disk controller, and the following conditions are true:
    • You use a standard 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable.
    • The basic input/output system (BIOS) settings are configured to force the faster UDMA modes.
  • The file system is damaged and cannot be mounted.
The purpose of this error message is to prevent the following two things:
  • Potential data loss caused by using an incorrect IDE cable for the faster UDMA modes. An IDE cable is a kind of cable used to connect storage devices, such as hard disks, inside a computer.
  • Continued access to a drive on which the file system is damaged
Method 1: Repair the volume

Note the second parameter (0xbbbbbbbb) in the error message. You might have to regenerate the error in order to write it down.

If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, the cause of the error is that the file system is damaged. You can try to repair the volume to see whether this resolves the error. If the second parameter is not 0xC0000032, see "Method 2: Check the IDE cable and load Fail-Safe settings" for help.Some things that you should know before you try this solution

  • If the file system is damaged, you can use chkdsk /r command to repair the volume. However, if you use the chkdsk /r command, you may lose some data.
  • You will need the Windows startup disks or the Windows installation disk. If you do not have them, contact the computer manufacturer for help in obtaining the disks.
  • You will need the administrator password to complete the steps.
To repair the volume, follow these steps:
  1. Start your computer by inserting the Windows startup disks or the Windows installation disk if your computer can start from the CD drive.
  2. When the Welcome to Setup screen appears, press R to select the repair option.
  3. If you have a dual-boot or multiple-boot computer, select the Windows installation that you want to access from the Recovery Console.
  4. Type the administrator password when you are prompted to do this.

    Note If no administrator password exists, press ENTER.
  5. At the command prompt, on the drive where Windows is installed, type chkdsk /r, and then press ENTER.
  6. At the command prompt, type exit, and then press ENTER to restart your computer.
  7. After you repair the volume, check your hardware to isolate the cause of the file system damage.
If this procedure does not work, repeat it, but type fixboot instead of chkdsk /r in step 5.

If you are still unable to resolve the issue, please see the "Next steps" section for help.Method 2: Check the IDE cable and load Fail-Safe settings

If your computer uses a UDMA hard disk controller, try these steps. If your computer does not use a UDMA hard disk controller, see the "Next steps" section for help.
  • If your UDMA hard disk is connected to the controller with a 40-wire UDMA cable, replace the cable with an 80-wire cable.
  • In the BIOS settings for your computer, load the 'Fail-Safe' default settings, and then reactivate the most frequently used options, such as USB Support.
If you are not sure how to follow these steps, contact the manufacturer or refer to the user’s guide that was included with your hardware.
My System SpecsSystem Spec
16 Sep 2011   #3

Windows 7 Ultimate x64

Hey man! Thanks for the reply. I did what you said, but I stopped at the screen that shows the OS because i noticed something strange. Or at least I think it's strange. I could be wrong though. It says my windows 7 installation is on the "D" Drive and it says it's 0mb in size. =O Is that weird or is it just me?
My System SpecsSystem Spec

16 Sep 2011   #4

Windows 7 Ultimate x64

Ok I now finished what you said to do and I ran into a problem. (see attachment..) I'm assuming that's because of the dealio in my last post. But once again, I could be wrong. So I'm giving you every error I'm running into.

My System SpecsSystem Spec
16 Sep 2011   #5

Windows 7 Ultimate x64

In the command prompt say cd D: or something similar until it changes the directory to the correct drive.

Then chkdsk /r
My System SpecsSystem Spec
16 Sep 2011   #6

Windows 7 Ultimate x64

Ok I did that now and the attachment is what i got.

Attachment 175584

I tried 2 different ways.

cd D: {enter} chkdsk /r


cd D: chkdsk /r

It seems to want to stay on the X: drive. =\
Any more suggestions?

My System SpecsSystem Spec

 Can't boot after chkdsk. BSOD 0xED after the windows 7 logo.

Thread Tools

Similar help and support threads
Thread Forum
Artifacts During Boot Windows Logo.
About 3 weeks ago i installed Guild Wars 2 and was required to update my Video card drivers before i could play 306.23 i believe they were ( i have tried so many other versions and older ones now i forget) since then i have experienced Crashes, Artifacts and lock ups in all games i play including...
BSOD Help and Support
BSoD on boot after ending chkdsk
Okay. If someone can figure this out, I'll give them a cookie. K, so I primarily use Windows 7, but also have multiple OSes underneath it, such as Ubuntu and Joli OS installed by WUBI type of installer. Now, I decided to run a chkdsk because it's normally good to run it once in a while, right?...
BSOD Help and Support
BSOD during boot or Windows logo, TCPIP.SYS issue???
Hello, I've been reading a lot of threads on here for some time now trying to figure out how to fix this BSOD problem. I bought the parts in the computer back in 2008 (I know its old), and installing and running Windows XP Pro works just fine. Not a single blue screen to date. I started to...
BSOD Help and Support
BSOD on boot after Windows logo. Cause: ntoskrnl.exe ( nt+371610 )
Hello. I'm getting a BSOD on boot, immediately after the flying Windows logo (before login screen). The BSOD flashes on the screen for a second, and then the computer reboots. I'm running Windows 7 64 bit. This problem came out of nowhere as I've been running my PC flawlessly for years. ...
BSOD Help and Support
Windows 7 Boot Logo
Hi all... Is there any way by which we can change the Boot logo which comes like animated while Windows 7 starts. No disrespect to Windows but m bored of seeing that logo.... Thanks
General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:31.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App