Link to home
Start Free TrialLog in
Avatar of peterdeyes
peterdeyes

asked on

BOOT ERROR "STOP C 0000218 UNKNOWN HARD ERROR"

I have Mesh Desktop computer purchased new February 2004, it has a AMD Athlon(tm) 64 FX-51 Processor, 1GB Ram, Maxtor 7 Y250M0 SCSI Hard drive and is running windows xp home SP2.  It is generally been quite stable with few problems. However, when I came to start it up after being away for 5 days or so it just boots into the DOS start up options screen. It will not start on any of the safe mode options and the normal and last good config modes allow the system to try again.  Windows starts to boot but then comes the dread blue screen with the error message STOP  C 0000218 UNKNOWN HARD ERROR
UNKNOWN HARD ERROR. All my back up files are on a network storage device which is coincidentally also playing up at the moment and I am currently corresponding with IOMEGA to get this fixed separately.

Do you have any advice please on what the error might be and the best way to fix it - hopefully without erasing all the data on the drive.

Thanks
Avatar of laskovd
laskovd
Flag of Israel image

Hi peterdeyes
1. Before problem occurred - any changes in hardware\software?
2. Since Xp and 2000 have same error-report system, please check the following thread:
https://www.experts-exchange.com/questions/20847736/c0000218-Unknown-Hard-Error-when-loading-Windows-2000.html
chkdsk might solve ur problem.
Avatar of peterdeyes
peterdeyes

ASKER

I am following the advice on emergency recovery . chdisk.  I have not made any recent software updates ( other than routine windows update). I have not added any hardware though my Imoga NAS back up strted playing up last week  - wouldnt have thought that would have any affect.
See if this article helps.  It shows the various reasons for the problem ...

<Quote> A necessary Registry hive file couldnt be loaded. The file may be corrupt or missing (requiring either an Emergency Repair Disk or a Windows reinstallation). The Registry files may have been corrupted because of hard disk corruption or some other hardware problem. A driver may have corrupted the Registry data while loading into memory, or the memory where the Registry is loading may have a parity error (turn off the external cache and check the physical RAM).  <Unquote>

"0xC0000218: UNKNOWN_HARD_ERROR":
http://aumha.org/a/stop.htm

You may need this one >
"How to recover from a corrupted registry that prevents XP from starting":
http://support.microsoft.com/?kbid=307545&sd=RMVP
In above link, see right hand column then select 218.

Here's an advanced RAM Tester ..                        
memtest86+  v1.70 :
http://www.memtest.org/
Please take a look under "Resolution" for further advice >

"How to Troubleshoot a Stop": 0xC0000218 Error Message
http://support.microsoft.com/kb/156640
> have not made any recent software updates ( other than routine windows update) <

The finally, if you still cannot resolve it, do you recognise any of your most recent MS updates >>
http://support.microsoft.com/default.aspx?scid=kb;en-us;325192

If yes, you may want to try to remove the problematic update(s), or/and consider a "System Restore".
Sorry guys...  I am having trouble getting into the recovery console / starting from the CD. I have tried pressing the F1 & 2 buttons during the boot sequence but this doesnt seem to be working - any advice please ?
Try to configure boot order in BIOS - on boot press Del, enter BIOS menu and configure CD-rom as first boot device.
Then - You have already enough solutions to try :)
ASKER CERTIFIED SOLUTION
Avatar of Jonvee
Jonvee

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
To Jonvee et all
Thank you all for your support.  Alas I think that Jonvee's final analysis is the truth. When I finally got the emergency dik to run.  The recovery console wouldnt work cos it couldnt see the hard drive so I guess the drive is damaged to some extent. I will try the final advice using diagnostics advised - but it now looks like ahrdware problem.  Thanks again y'all
PD
Thanks for the report, it's appreciated!  
Good luck with the HD diagnostics check ...  & thank you, we're glad to help.