Solved Completely unable to boot into Windows after sudden BSOD

[italnsd]

Hello all,
A few days ago my pc suddenly crashed showing a BSOD (attached is the file bsod.bmp with a pic of the BSOD that I took with my phone). I don't recall exactly what I was doing, just a common task like maybe browsing the news. After that I have not been able to start Windows ever again, nor in normal mode, nor in safe mode, nor in the last good configuration. I have tried a few things, none of which solved the problem. Here it's a concise list:

1) I ran Startup Repair from the System Recovery Options in the hard disk (from the advanced boot option menu after pressing F8). After running the first time, it stated that it cannot repair this computer automatically. In the diagnostic and repair details, I found:

Root cause found:
---------------------------
A patch is preventing the system from starting.

Repair action: System files integrity check and repair
Result: Failed. Error code = 0x17
Time taken = 160525 ms

Subsequent attempts to run Startup Repair again (after having done all the other attempts below) would instead terminate with the message "Startup Repair could not detect a problem. If you have recently attached a device to this computer, such as a camera or portable music player, remove it and restart your computer. If you continue to see this message , conatact your system administrator or computer manufacturer for assistance."


2) Since I had been foolish enough not to save any previous restore points or system images, the only other possibility left in the System Recovery Options was to go to Command Prompt.

I ran chkdsk /r /f d: a few times with a gradually declining number of bad sector found, until it terminated with no problems found. chkdsk /r /f c: returned no problems.

I ran sfc /scannow /offbootdir=c: /offwindir=d:\windows\
and I parsed the CBS.log extracting the lines containing [SR].A zipped copy of the resulting file sfcdetails.txt is attached (as well as sfc3.txt in which I further extracted only those lines showing potential problems). The choices of drives c: and d: are based on the output of diskpart
Disk ID: 177A27F9
Type : ATA
Status : Online
Path : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1100)#ATA(C00T00L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 C System Rese NTFS Partition 350 MB Healthy
Volume 2 D NTFS Partition 931 GB Healthy

Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 350 MB 1024 KB
Partition 2 Primary 931 GB 351 MB


3) I booted from the Recovery DVD that I received from the pc manufacturer CyberPower and tried to run Startup Repair, which terminated unsuccessfully with the error message "This version of System Recovery Options is not compatible with the version of Windows you are trying to repair. Try using a recovery disc that is compatible with this version of Windows".

4) I tried the same as in step 3 booting from a DVD containing a .iso image of a retail Windows 7 Home Premium 64bit that I created as described in http://www.sevenforums.com/tutorials/31541-windows-7-usb-dvd-download-tool.html. Also in this case Startup Repair terminated unsuccessfully, but with a different error message "Startup Repair could not detect a problem. If you have recently attached a device to this computer, such as a camera or portable music player, remove it and restart your computer. If you continue to see this message , conatact your system administrator or computer manufacturer for assistance."

5) Unfortunately I was not able to run the recommended dm log collector tool, probably because there are not enough resources to do so in the system recovery command prompt environment. When I tried, I got the error message "The subsystem needed to support the image type is not present". Please let me know if there is any relevant log that I can search through the command line of the recovery environment and I will provide them.

I guess my questions are: does sfcdetails.txt show what the problem is? If so, how can I fix it? If not, what other extra info can I provide and what other procedures can I try to solve the problem?

Thank you in advance,
Marco

 

[axe0]

This sounds like your file system is corrupted.

Do you have a spare hard drive you can use?

Please try running all the tests in SeaTools DOS

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums

   Note

Do not run SeaTools on an SSD as the results will be invalid.

 

[italnsd]

Hi axe0, thanks for your prompt reply.
I followed your instructions and both the short and the long tests operated by SeaTools for DOS failed.
The corresponding log is attached.
I will also try to run the diagnostic tools that I downloaded from my HD manufacturer, Western Digital, and post the results.

Please let me know if the SeaTools results are already a show stopper.

 

[axe0]

The SeaTools is a show stopper, your hard drive needs to be replaced.

 

[italnsd]

Thanks for confirming that. I had also run the WD Data Lifeguard Diagnostic for DOS whose Quick Test terminated with "Seek not complete Error/status code: 0108". After that I have not been able to see the HD anymore from the DOS prompt.

When I boot from a Windows 7 DVD, I get a screen that says
Auto-Detecting SATAII_1...IDE Hard Disk
but further down
3rd Master Hard Disk Error

In the BIOS Setup Utility, I can see the Hard Disk in the Storage Configuration menu, but it completely disappeared from the Boot Devices menu. In the command prompt recovery environment both C: and D: are gone.

I mentioned all the above because I am wondering if there is anything useful that I can try to get out of the hard drive before trashing it, besides the contents of My Documents (%userprofile%\documents) that I had previously backed up.
If so, what else can I try to save and what's the best way (I read about booting from a Linux DVD or connecting the failed HD to another computer via a universal USB adapter) considering the situation as described above?
I also came across the description of a possible way to take an image of the failing hard drive through a program like Macrium Reflect, and use it on a new HD which will be the best scenario. However, given the level of my HD failure I am not sure if it's worth a shot or better to go with a completely new installation.

I would appreciate any advice or possibly the indication of a more appropriate forum for this matter.
Thank you very much for the assistance provided so far.

 

[axe0]

There are quite some methods to recover data from a hard drive, if you'd ask me it is the best to first replace the hard drive so that at least your system is stable again (test the new hard drive please!)

You could try

• using Linux as you mentioned,
• connecting via USB as you mentioned,
• using a docking station,
• an image as you mentioned (not always the best method as the data may be damaged (corrupted)

it is certainly possible that there are more methods, but I think these are mostly used.

 

[italnsd]

Hi axe0, my idea is to replace the failed HD with a SSD, which is supposed to be much more reliable. Please let me know if you think there is any caveat to that choice, otherwise we can mark this thread as solved and, if necessary, I will open a new one in the Installation and Setup forum for help on that activity.
Thanks for sharing all your expertise!

 

[axe0]

What caveat would there be with that choice? I have done it myself and still no caveat after months.

 

[italnsd]

Thanks!

 

[italnsd]

BTW, I just noticed that someone is using my question for marketing purposes, by falsely claiming that the "Top Rated Answer" to solve my problem is to use their product. Not sure what to do about it, but at least I wanted to bring it to your attention.

 

[axe0]

That happens with a lot it seems, that site doesn't seem very well, I would ignore it