Laptop suddenly wont start!

Golden said:

Yes....the ED bugcheck pointed to a very serious problem. There is a very strong posssibility that the drive is dying or already dead.

However, don't rush into anything yet - please try this:

1. Leave the long test to run for another hour (make a note of the progress and errors encountered)
2. If you have any data on that disk that you need, we can try rescue it, but the chances are extremely slim.

Lets get step 1 out the way first, and then we will try step 2.

I'll be here the whole day, so just post back and I'll get notified of the thread.

I would have left it running, but it seems that there were too many errors, as soon as it hit 100, the test completely stopped.
pictures as promised:
seagste test - Imgur
I took a picture of everything that popped up.

Golden said:

Do you need to extract any data off that drive?

No I dont, I have all of my very important files on my desktop

Golden said:

OK. Lets try something before you throw the disk away.

1. Boot from the installation USB as if you were going to do a clean install
2. At the Languages screen, press SHIFT+F10
3. A command window will open. In it, type DISKPART and hit enter
4. Now type list disk and hit enter

What does the window report back when you do that?

well it does let me type DISKPART, but after I hit enter it wont let me type after that.
EDIT!
I let it sit on the screen while waiting for a response and I guess it was just VERY delayed.
2 disks, Disk 0 and Disk 1, both online.
Disk 0: Size:149 GB Free:0 Dyn: (blank) Gpt: (blank)
Disk 1: Size:3819 mb Free:0 Dyn: (blank) Gpt: (blank)

Golden said:

You should be able to do this....the prompt will be different, but thats OK. You might have to wait a bit before you can type the next command

Attachment 312758

you're right, it was delayed.
I edited the last post with what it says

djthurman said:

Golden said:

You should be able to do this....the prompt will be different, but thats OK. You might have to wait a bit before you can type the next command

Attachment 312758

you're right, it was delayed.
I edited the last post with what it says

I have come to the conclusion that D: is what is messed up. While doing chkdsk /r, c runs perfectly fine, but D freezes at about 30%.
I've also run some other commands with D and have gotten "this request could not be preformed because of an I/O device error"