BSOD - ntkrnlpa.exe

Ok, so tonight I installed an upgrade of Home Premium onto my system.
Everything was going fine until I decided I should probably upgrade my video
drivers for my 6600GT. Upon doing that, I restarted and got a BSOD with the
words:

SYSTEM_EXIT_OWNED_MUTEX

Couldn't get the 0x0* numbers, but I finally figured out it was a hardware
problem. Tried reverting back to old drivers, reinstalling drivers, and
updating to new beta drivers with no avail. I did a windbg on the dump file
and found this:

*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 39, {8198c85f, 83bfdd58, 83bfdd58, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntkrnlpa.exe ( nt+18c85f )


So, its definately something to do with the video driver but now... How do I
fix this? I can't even enter Vista normally, I can only do it in safe mode.
Luckly my XP partition is still there so I can use my computer, but this is
an annoyance.

If anyone has any suggestions, I would highly appreciate it so I can get
back on my feet and actually ENJOY Vista instead of fighting with it...

 

On Saturday, February 17, 2007 4:34:03 PM UTC+8, Kyle wrote:
> Ok, so tonight I installed an upgrade of Home Premium onto my system.
> Everything was going fine until I decided I should probably upgrade my video
> drivers for my 6600GT. Upon doing that, I restarted and got a BSOD with the
> words:
>
> SYSTEM_EXIT_OWNED_MUTEX
>
> Couldn't get the 0x0* numbers, but I finally figured out it was a hardware
> problem. Tried reverting back to old drivers, reinstalling drivers, and
> updating to new beta drivers with no avail. I did a windbg on the dump file
> and found this:
>
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 39, {8198c85f, 83bfdd58, 83bfdd58, 0}
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *************************************************************************
> *** ***
> *** ***
> *** Your debugger is not using the correct symbols ***
> *** ***
> *** In order for this command to work properly, your symbol path ***
> *** must point to .pdb files that have full type information. ***
> *** ***
> *** Certain .pdb files (such as the public OS symbols) do not ***
> *** contain the required information. Contact the group that ***
> *** provided you with these symbols if you need this command to ***
> *** work. ***
> *** ***
> *** Type referenced: nt!_KPRCB ***
> *** ***
> *************************************************************************
> Probably caused by : ntkrnlpa.exe ( nt+18c85f )
>
>
> So, its definately something to do with the video driver but now... How do I
> fix this? I can't even enter Vista normally, I can only do it in safe mode.
> Luckly my XP partition is still there so I can use my computer, but this is
> an annoyance.
>
> If anyone has any suggestions, I would highly appreciate it so I can get
> back on my feet and actually ENJOY Vista instead of fighting with it...

I got the same problem with ntkrnlpa.exe unable to run on win32