Chkdsk/R on startup process terminated twice by BSOD

[sassofalco]

I have been experiencing issues with a number of failed attempts to complete a full backup of this laptop. These result in the backup being aborted at about 60% completion. To try and resolve the issue I decided to run the Check Disk/R process.

Two attempts to complete the Check Disk/R process on startup, were terminated each time by a BSOD event.

Files that may help determine the cause of these failures are attached.

View attachment 380536

View attachment 380537

View attachment 380538

View attachment 380541

View attachment 380539

Cheers

 

[whs]

I think your disk has gone south.

 

[Golden]

Tony,

The .dmp file points to Intel Storage driver issues (dated 2010) and doesn't yet conclusively point to disk failure. The fact that it BSOD's on chkdsk is a worry though.

Manually copy off any user data/files to an external drive, then run the DOS version of the LONG GENERIC TEST of SeaTools, and report the outcome:
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[sassofalco]

Tony,

The .dmp file points to Intel Storage driver issues (dated 2010) and doesn't yet conclusively point to disk failure. The fact that it BSOD's on chkdsk is a worry though.

Thanks Colin,

My first reaction was "OUCH"!

Looks like I have to give the old grey matter a bit of a hiding and will do a lot of reading before I try your recommended DOS report action.

But in the meantime, is there any way that I am able to search for and perhaps update the Intel Storage Driver?

Further, can you elaborate a bit more on the "BSOD during chkdsk" issue.

If all fails, I do have a purchased full version W7 Home Premium sitting in a drawer, but prefer to try and get this issue sorted before turning to the disk as a last resort.

 

[Golden]

Tony,

Use this to check for updates to the Intel storage driver:
Intel® Driver Update Utility

Concerning the BSOD during chkdsk: its concerning that it should do that. Tyhe implication is there is an error in the hard disk, or perhaps the SATA cable connecting it to the motherboard.

If the hard disk is failing, then a new install won't help the situation. The best bet is to confirm/deny that the disk is actually terminal by running SeaTools.

SeaTools will give us a clear picture what is going on.