When Windows boots up, everything is fine until it is logging on locally. Whenever it gets to the part where it says "applying personal settings" I get a blue screen with the following error message:
***STOP: 0x 0000001E (0xC0000005, 0x804B837A, 0x 00000000, 0x 00000 FF8) KMODE_EXCEPTION_NOT_HANDLED

*** Address 804B837A base at 80400000, Date Stamp 3d366b8b- ntoskrnl.exe

I've tried loading in safe mode, safe mode Command Prompt Only, Last-Known-Good, and even remote desktop, but as the desktop initializes, the above BSOD occurs.
I can connect to the server using the C$ share, and have identified and renamed the video driver, but this does not help, I just get lower resolution. Administrator is the only known username with local logon rights, and I have tried removing the profile from C:\Doc & settings but cannot (File In use) as I thought this may be corrupt.

There was a similar posting (ev14363 - 5th Feb 2004) but no posted resolution.

Does anybody have any ideas?

Install PC Anywhere lately?

http://support.microsoft.com/?kbid=811014

Otherwise, try:

A. Use an ASR disk to restore.
B. Restore registry to previous working state.

"Milk was a bad choice!"

Attach the minidump at
http://www.rapidshare.de/ and I will analyse your minidump.

Oh my, you didn't know?
KMODE is KILL mode.

You mishandled it and now it wants you. Your going to need a few things to get out of this one. Being that kill mode is engaged by the Lord of Hell, Mr. Diablo himself, you're going to need to get a young priest and an old priest. They need to have exactly 483.44444_ (repeating) ounces of holy water on each of them. A cross blessed by Baron Bill Gates. A stuff animal that resembles a 3 month old panda cub. 2 bottles of poweraid for when your priest gets tired.

God bless, good luck.

KMODE_EXCEPTION_NOT_HANDLED

Holy Wow.

Jestible,

Smoking crack sets a bad example to other people.

"Milk was a bad choice!"

<itches neck>
I want some crack!

Holy Wow.