• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Error message on startup after installing Java 5.0

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Eichhorn18

Member
Joined
Feb 2, 2005
Location
Alberta, Canada
Hey, my gf has a Toshiba laptop which is about 1.5 years old, not sure the modle #. She is running Windows XP home. Anyway the problem is:

She recently downloaded and installed Java 5.0 to use some online game. After she installed we restarted her computer to get it refreshed. Everything was fine until we restarted. A blue screen appeared with the following message:

STOP: c0000218 {registry file failure}
The registry canot load the hive(file):
\systemroot\system32\config\SECURITY
or its log or alternate

Beginning dump of physical memory
... it continues but i'm not going to write it all... it just talks about the memory dump being complete.

Then nothing happens. So we restarted and got the black screen where it asks to restart in normal mode, safe mode, or last known good configuration. We tried all of these and got the same blue screen every time.

What can be done to fix this.

I should say that wiping the harddrive is not an option.

Any info or suggestions anyone has would be appreciated.

Thanks
Eichhorn 18
 
Check out these two MSKB articles...

How to Recover from a Corrupted Registry that Prevents Windows XP from Starting:
http://support.microsoft.com/?id=307545

How to Troubleshoot Registry Corruption Issues
http://support.microsoft.com/?id=822705

... or you may want to try a repair install instead:

"How to Perform a Windows XP Repair Install"
http://www.michaelstevenstech.com/XPrepairinstall.htm

Either way... the registry is corrupted. If you can repair the registry and salvage the install, either by performing a repair or by following the steps in the first KB article re: recovery... you should probably have your girlfriend read the second article re: troubleshooting corruption issues.
 
Back