I have slowly descended to Hell where I currently reside.
My desktop computer now will not boot. Consequently, there are no attachments to this post though (after moving the entire drive to another computer) I tried to move the Minidump file from the non-bootable drive over to the other computer’s C:Windows\Minidump folder where it could be read. Unfortunately, the original file reads empty.
I have moved my boot disk drive (one of two) onto another computer to confirm that all of its files are still viewable (they are). It isn’t clicking and appears to be alive. Yet none of the several listed Microsoft Startup Repair options have worked to redeem the non-bootable drive. I received various BSODs when I could boot-up and run successfully for many hours. During that several week period I searched for the sometimes differing error codes that I received (0x1, 0xD1, 0xC24, 0xe, 0x2, 0x490) and tried solutions that I found on the web. I tried the Event Viewer and BlueScreen View (but never found the dump files where they were supposed to be viewed). I downloaded the Western Digital Diagnostic tool for my disk: it said there were too many bad sectors but I received no confirmation from any other source. Even though the drive is one year old, I would tend to believe the disk manufacturer’s own diagnostic tool that there were in fact bad sectors, plus the drive is hot to the touch.
None of the efforts I made to find or correct the BSOD problems seemed to confirm a problem, yet I was getting a message from those screens that seemed to point toward a Boot Record or driver virus. After getting a “Boot Critical file is corrupt” message, I tried to rebuild the boot file in the Command Module but I couldn’t do it successfully. I was keeping notes as I continued down my spiral path but now the notes are not even accessible so I must remember most of these events. I did receive notations (when the blue screen clicked my work away) that the volsnap.sys, then vsflt53.sys drivers were the corrupt culprits. But it was your Microsoft site that said don’t touch these, so I, being an inveterate fraidy cat, didn’t. I thought I might have a RootKit virus problem, but even that has come up empty. I disconnected all USB cables but that didn’t work.
Woe is me. Woe is me.
I tried all these scans too but no virus or corruption was identified.
Microsoft Fixit
WinUtilities.
Doctor Web
Scannow
AVG
Kaspersky Virus Scan
TDSSKiller
AVZ4
GMER
Edit 1:
I have now installed a second Western Digital drive with second copy of W7 on the same computer. So there is now a separate working disk drive, of two. From that new drive I ran a System Diagnostics Report which is attached.
The problem may have been a cracked SATA plug causing a bad connection on the primary bootup disk. Still checking.
Edit2:
Regarding disk Management jpg: Drive 0 has not been formatted or used yet. Disk 1 is being used for bootup here and it has the backup and disk image of Disk 2. Disk 2 is the previous bootup drive but now is inaccessible.
Edit3:
After disconnecting the power to two (of three) other drives on my computer, I followed the Startup Repair Infinite Loop procedure (completed once, and no files showed as zero capacity). But I then booted up to the identical Recovery Screen with the same options which were either Repair or Startup Normally. The Repair option did the same thing as before...endless loop. Yet the Startup Normally option worked to boot up. That is great! Still checking and creating additional System Recovery options.....
Edit4:
Trying to clone the "old" to a new drive before it crashed and failed again, I received an Error 0x74 Bad_System_Config_Info. Haven't succeeded yet.
Edit5:
Was able to start cloning using EaseUS and disabling other Start programs. Yet when the program had to reboot into its own screen in the middle of cloning, I received a message after its reboot and entry into the cloning program: "Failed to find the specific disk." So I had no choice but to back out. On another reboot with W7 OS, I received a 0x18 Blue Screen (Reference by Pointer). On the next reboot I was given a choice to System Restore, which I did. As it was booting up to the desktop, the computer just clicked off.
My desktop computer now will not boot. Consequently, there are no attachments to this post though (after moving the entire drive to another computer) I tried to move the Minidump file from the non-bootable drive over to the other computer’s C:Windows\Minidump folder where it could be read. Unfortunately, the original file reads empty.
I have moved my boot disk drive (one of two) onto another computer to confirm that all of its files are still viewable (they are). It isn’t clicking and appears to be alive. Yet none of the several listed Microsoft Startup Repair options have worked to redeem the non-bootable drive. I received various BSODs when I could boot-up and run successfully for many hours. During that several week period I searched for the sometimes differing error codes that I received (0x1, 0xD1, 0xC24, 0xe, 0x2, 0x490) and tried solutions that I found on the web. I tried the Event Viewer and BlueScreen View (but never found the dump files where they were supposed to be viewed). I downloaded the Western Digital Diagnostic tool for my disk: it said there were too many bad sectors but I received no confirmation from any other source. Even though the drive is one year old, I would tend to believe the disk manufacturer’s own diagnostic tool that there were in fact bad sectors, plus the drive is hot to the touch.
None of the efforts I made to find or correct the BSOD problems seemed to confirm a problem, yet I was getting a message from those screens that seemed to point toward a Boot Record or driver virus. After getting a “Boot Critical file is corrupt” message, I tried to rebuild the boot file in the Command Module but I couldn’t do it successfully. I was keeping notes as I continued down my spiral path but now the notes are not even accessible so I must remember most of these events. I did receive notations (when the blue screen clicked my work away) that the volsnap.sys, then vsflt53.sys drivers were the corrupt culprits. But it was your Microsoft site that said don’t touch these, so I, being an inveterate fraidy cat, didn’t. I thought I might have a RootKit virus problem, but even that has come up empty. I disconnected all USB cables but that didn’t work.
Woe is me. Woe is me.
I tried all these scans too but no virus or corruption was identified.
Microsoft Fixit
WinUtilities.
Doctor Web
Scannow
AVG
Kaspersky Virus Scan
TDSSKiller
AVZ4
GMER
Edit 1:
I have now installed a second Western Digital drive with second copy of W7 on the same computer. So there is now a separate working disk drive, of two. From that new drive I ran a System Diagnostics Report which is attached.
The problem may have been a cracked SATA plug causing a bad connection on the primary bootup disk. Still checking.
Edit2:
Regarding disk Management jpg: Drive 0 has not been formatted or used yet. Disk 1 is being used for bootup here and it has the backup and disk image of Disk 2. Disk 2 is the previous bootup drive but now is inaccessible.
Edit3:
After disconnecting the power to two (of three) other drives on my computer, I followed the Startup Repair Infinite Loop procedure (completed once, and no files showed as zero capacity). But I then booted up to the identical Recovery Screen with the same options which were either Repair or Startup Normally. The Repair option did the same thing as before...endless loop. Yet the Startup Normally option worked to boot up. That is great! Still checking and creating additional System Recovery options.....
Edit4:
Trying to clone the "old" to a new drive before it crashed and failed again, I received an Error 0x74 Bad_System_Config_Info. Haven't succeeded yet.
Edit5:
Was able to start cloning using EaseUS and disabling other Start programs. Yet when the program had to reboot into its own screen in the middle of cloning, I received a message after its reboot and entry into the cloning program: "Failed to find the specific disk." So I had no choice but to back out. On another reboot with W7 OS, I received a 0x18 Blue Screen (Reference by Pointer). On the next reboot I was given a choice to System Restore, which I did. As it was booting up to the desktop, the computer just clicked off.
Last edited:
My Computer
- Computer Manufacturer/Model Number
- Generic
- OS
- W7 64
- CPU
- 2.67 gigaherts Intel Core i5 750
- Motherboard
- ASUSTeK P7H57D-V
- Memory
- 8 MB
- Graphics Card(s)
- NVIDIA GeForce 9500 GT
- Sound Card
- USB 2861; Also: Logitech Pro 9000; ScreenCamera HR;
- Monitor(s) Displays
- 2 x ViewSonic G800
- Hard Drives
- 2 Western Digital 1 Terrabyte Drives
- Case
- Antec
