Recent Blue Screen Crash

[hambone2]

I recently had this error when rebooting my system



I sent an Error Report when Prompted by MS after the "This system has recovered from a serious error, Send Report...and I did just that.




Problem Caused By Hard Drive Disk Error

Windows was temporarily unable to read your hard disk drive. We do not know the exact cause of the problem. In most cases, this type of condition is momentary and does not indicate a serious problem, but sometimes it means that a hard disk is failing.

Common causes of this problem

*

Aging or failing hard disks. To prevent file corruption and data loss, we recommend that you back up all of your important files and folders immediately. See Step 1 in the Troubleshooting section below for more information.
*

Large file transfers from secondary media, such as an external hard drive, to a local hard drive.
*

Loss of power to a hard disk drive that causes inconsistent data sectors.
*

Hard drive slowness caused by disk-intensive processes such as antivirus scanners.
*

Recently installed hardware that might have compatibility and performance problems.

Lately, I had my Storage Drive Crash (heard it clicking, then it failed). I unplugged the Power Cord, but left the Data Cable in.

Now I was able to reboot OK after that....but I was wondering if this error message had to do anything with my OLD Hard drive Data Cable STILL being plugged in.

Hoping it's not my already working drive. But I'm thinking it's trying to read the old drive that isn't "powered up".

I am hoping it is MOMENTARY like M$ says.

[SuperSparks]

Download and run the hard drive manufacturer's diagnostic utility, and see what it reports. Here are the common ones:

Seagate Seatools

IBM / Hitachi Drive Fitness Test

Maxtor Maxblast 3

Maxtor PowerMax

Western Digital Software & Drivers

Fujitsu Utilities

[hambone2]

Stupid question...do I have to find out what Brand Hard drive is and use the corresponding Program?

[SuperSparks]

Use this utility to identify your hard drive:

PC Wizard

[jdc2000]

1. Open the case and look at the label on the drive.

2. If the system boots, Device Manager should show the drive model, and maybe the make. If model only, Google that.

[hambone2]

1. Open the case and look at the label on the drive.

2. If the system boots, Device Manager should show the drive model, and maybe the make. If model only, Google that.

LOL...yeah, that's always a challenge...find out what kind of hardware you have in your system that you haven't looked at in forever...without opening the case. lol

[Broni]

Your error indicates some registry problems.

Download, and install WhoCrashed: http://www.resplendence.com/download...ashedSetup.exe
Open it, click Analyze button.
The program will create report
Copy, and paste it into your next reply.

[hambone2]

Your error indicates some registry problems.

Download, and install WhoCrashed: http://www.resplendence.com/download...ashedSetup.exe
Open it, click Analyze button.
The program will create report
Copy, and paste it into your next reply.

OK here it is:

----------------------
Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Wed 12/24/2008 1:09:40 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xFFFFFFFFC0000218 (0xE1A18D08, 0x0, 0x0, 0x0)
Error: STATUS_CANNOT_LOAD_REGISTRY_FILE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

-------

[Broni]

I think, the best place to start would be...

Go Start>Run ("Start Search" in Vista), type in:
sfc /scannow
Click OK (hit Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) will find any errors, it may ask you for the CD/DVD.
If sfc won't find any errors in Windows XP, it'll simply quit, without any message.