Windows Vista Bsod: BugCheck 124

HI, I am getting a bsod, not sure why, but I will past the dump file if I am doing it correct? If not I will include the rar files for them thanks


Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini011307-04.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Sat Jan 13 15:17:29.519 2007 (GMT-6)
System Uptime: 0 days 13:31:44.209
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.........................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, 8335e7d8, b2000010, 10c0f}

***** 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+d85c9 )

Followup: MachineOwner
---------

 

While you're waiting for someone more experienced at dump reports than I am, you may want to check your video drivers and update them to the latest Vista version available at the nVidia website.

The reason that I mention this is that there was a bug in the nVidia v95 drivers that gave this particular bug error.

 

Hi

I'm getting the same exact Bug Check 124 but mine is possiby caused by the intelppm.sys file per WinDbg. I'm able to correct it by switching HAL modes from x86 ACPI to ACPI Standard PC.

I'm working with Microsoft to find out why so hopefully there will be a resolution soon as I feel it's something with the OS and not my hardware.

The reason why I say that is I have installed a new motherboard, new video card, new memory and it still crashes after reinstalling everything. Also I have a dual boot and if I boot into XP the system is flawless and I can stress test it to the cows come home and no crashes!

I would check on guru3d for beta drivers as they post them for people to download and try for Nvidia cards.

Cheers