0x8e (0xc5)

June 4, 2009 at 14:33:47
Specs: Windows XP
I have been recently experiencing a 0x8e (0xc0000005) BSOD after entering from the login screen.

What I know:

0x0000008e and 0x10000008e are often caused by hardware incompatibility, device driver issues and sometimes bad RAM. The error message tends to be: KERNEL_MODE_EXCEPTION_NOT_HANDLED, which means a kernel application has commited an exception that the error handler did not catch. As of this day, after four days of relentlessly researching about what it meant in plain English, I got no answer.

0xc0000005 is STATUS_ACCESS_VIOLATION which indicates that a memory access violation occurred. Though again, what it really means I have no clue.

What I have tried:
- The first suspicion was the graphics driver and adapter. I recently updated the driver from ATI's main site then reverted back to the very disk that came with my computer. I even removed the adapter and booted the system to see if that was the issue. It crashed just the same.
- I tried a memory test, just in case it was a bad RAM, but after testing with both sticks in, each stick in (I have two), I practically invested 15 hours just testing the RAMs and they appear to be fine.
- I ran the debugging tools, and I could only pick up "Probably caused by ntoskrnl.exe" and a process called "services.exe". Another individual looked at one of my dmp files and pointed out a possible registry corruption which was 'probably caused by: ntkrpamp.exe'

BugCheck 1000008E, {c0000005, 80637712, a2dcb9d0, 0}
Probably caused by : ntkrpamp.exe ( nt!HvpIsFreeNeighbor+4a )

However most of the time it is just ntoskrnl.exe and services.exe. I am very well aware that there are service.exe and other trojans alike and I have done a thorough search for them and it is clean.

There could be a chance that it might be just dust, and I will be buying a canister tonight to blow the dust out of the GPU.

I should also mention the following:
I can run in:
> Safe Mode
> Safe Mode with Networking
> Directory Repair Service Mode

I cannot run in:
> Normal Mode (crashes after login)
> Last Known Good Configuration
> Boot Logging
> VGA Mode

I asked two forums before to help me, but it seems that it has gone dead cold for some reason.

Link 1: http://forums.techarena.in/windows-...

Link 2: http://www.techsupportforum.com/mic...

I am seriously stuck and frustrated and ran out of ideas.
Any help is greatly appreciated.

See More: 0x8e (0xc5)

Report •

June 4, 2009 at 14:50:28
Try this boring old standard:

Take out your RAM and clean it's edge connectors with a pencil eraser. Then pop them in and out a few times to clean any oxide off the sockets themselves, before pressing them firmly back into position. You might try the same with the video card while you are in there.

It's a long shot but I've been caught so many times before with problems due to edge connectors.

some other bloke...

Report •

June 4, 2009 at 14:54:58

Report •

June 4, 2009 at 15:29:43
The eraser and the connector bit was news to me and I'll probably do that tonight as well.

As for that suggested article, yes, I have before, but I will read it again in case I miss something. As far as I know, I checked in all the directories (at least ones I can navigate to) as suggested my Symantec. It isn't likely anyway because I haven't downloaded a file two days before the incident occurred.

Report •

June 4, 2009 at 16:58:44
An odd twist of fate for me, in a good way... I think?

I did a little more research and ended up with the UnHack Me software. Goes to show that Russian technology is often better than North American technology. After some deep cleaning of files that I had no idea was in there, my system booted up miraculously. I am now posting to you from my password-less admin account (rest assured that this won't be here for long). I will attempt to log in to my actual account and see if it works out.

Report •

June 4, 2009 at 18:44:26
Glad you got it sorted.

some other bloke...

Report •

Ask Question