Boot Failure

[Corey Cooper]

My XP-pro system gave me a blue screen of death the other day when I shut it
down. That happened twice or three times. Then I got a Blue-screen when I
booted up, but it only stays up for 5 seconds and then re-boots the
computer. I discovered that after two or three times, it would finally
boot. That worked two or three times, and now I can't boot up at all. I
get a blue screen, which I've taken a picture of so I could read it before
it disappears, and it tells me that the error is

0x0000008E (0xC0000005, 0x80612856, 0xbab16ed4, 0x00000000)
MSDN tells me that this is a KERNEL_MODE_EXCEPTION_NOT_HANDLED, and
specifically that it's an access violation.

If I boot into safe mode, I get no error or warning, it just suddenly
re-boots before it finishes loading.

This sounded like a hardware problem to me, but I ran Memchk86 and the
memory checks out, and I pulled out a 9 month old bootable drive from this
system (saved it after I used Acronis to copy my intallation to a new larger
drive) and it boots up and runs fine (hence I can write this message).

I can read the 'problem' drive when I boot up using the older drive, so I
can manipulate files to my heart's content, but I'm at a loss to figure out
how to do anything useful. I found a couple of Minidump files, that might or
might not have been related to the boot issue, but couldn't get Visual
Studio to tell me anything from them, and Windbg gave me some info, but the
data didn't seem to match the blue screen info, so they might have been
generated only when I bootied into safe mode (or they are unrelated).

Any thoughts how I might resove this and make the disk bootable again?

Corey

 

[=?iso-8859-1?Q?_db_=B4=AF`=B7.._=3E=3C=29=29=29=BA]

I didn't spend a great deal of time
looking up the specific answer.

But I did provide a couple of
links that might help you figure
out the hardware issue.

Take a look at the links and
see if you find anything useful
towards your issue.

If you still cant' figure out
what is happening, maybe we
can take another look into it:
look

http://www.google.com/search?q=KERN...-us:IE-Address&ie=UTF-8&oe=UTF-8&sourceid=ie7

http://www.angelfire.com/ill/help2/StopErrors.htm
--

db ·´¯`·.¸. , .


..

 

[Ron Martell]

My XP-pro system gave me a blue screen of death the other day when I shut it
down. That happened twice or three times. Then I got a Blue-screen when I
booted up, but it only stays up for 5 seconds and then re-boots the
computer. I discovered that after two or three times, it would finally
boot. That worked two or three times, and now I can't boot up at all. I
get a blue screen, which I've taken a picture of so I could read it before
it disappears, and it tells me that the error is

0x0000008E (0xC0000005, 0x80612856, 0xbab16ed4, 0x00000000)
MSDN tells me that this is a KERNEL_MODE_EXCEPTION_NOT_HANDLED, and
specifically that it's an access violation.

If I boot into safe mode, I get no error or warning, it just suddenly
re-boots before it finishes loading.

This sounded like a hardware problem to me, but I ran Memchk86 and the
memory checks out, and I pulled out a 9 month old bootable drive from this
system (saved it after I used Acronis to copy my intallation to a new larger
drive) and it boots up and runs fine (hence I can write this message).

I can read the 'problem' drive when I boot up using the older drive, so I
can manipulate files to my heart's content, but I'm at a loss to figure out
how to do anything useful. I found a couple of Minidump files, that might or
might not have been related to the boot issue, but couldn't get Visual
Studio to tell me anything from them, and Windbg gave me some info, but the
data didn't seem to match the blue screen info, so they might have been
generated only when I bootied into safe mode (or they are unrelated).

Any thoughts how I might resove this and make the disk bootable again?

Corey

Use Start - Run - MSCONFIG and click on the Settings button in the
Startup and Recovery section. In the Startup and Recovery window
click on the checkbox for "automatically restart" to clear it then
click on OK and Apply as needed to exit. That will stop the
rebooting but not fix the original problem.

In the error message you quoted parameter 2 gives the address where
the error occurred (0x80612856). If that address remains consistent
then it is probably a software related issue and you need to identify
just which software item (device driver, application, Windows
component, etc.) is using that address. If the STOP code remains the
same but the parameter value changes, and even more so if the STOP
code changes, then that indicates that a hardware related issue is
more likely to be the culprit.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[CJC32768]

In case anyone is interested, after going through all the 'software'
fixes I could think of, I finally got my system up and running by
removing the ATI video card and replacing it (probably temporarily)
with a different brand. I don't think it's hardware, since it was
booting and running fine from another HD with a clean(er) install, so
I'll probably uninstall the driver and re-install the card and driver.

Corey