Hi,

I keep getting the following blue screen:

BAD_POOL_CALLER

STOP: 0X000000C2 (0X00000007, 0X0000113D, 0X00000000, 0XACEBF008)

This is 2 week old laptop so I dont understand why I am getting errors like this already but as usual Dell are useless.

I have tried to follow the steps to display the information from the minidump:


Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** 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 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Feb 18 18:34:27.126 2008 (GMT+0)
System Uptime: 0 days 0:01:22.907
Map \SystemRoot\system32\ntkrnlpa.exe:
Image region f2a00:180400 does not fit in mapping
*** 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
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 113d, 0, b352d008}

***** 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!PVOID ***
*** ***
*************************************************************************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+d8681 )

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

Thanks for your help

Elliot

(Moderator edit: added Topic Description. jgweed)

You have a conflict with either a new device driver or a newly installed program. What have you recently installed?

Its a new system, so lots of things have been installed:

- Microsoft Office
- iTunes
- Dreamweaver
- Photoshop
- Firefox
- MSN Live Messenger

Thats about it software wise.

The only hardware I have installed is a cordless USB mouse.

Thanks for any information!

The correct symbols weren't loaded for the debugger, so it's impossible to tell what's causing this. Please follow the directions here to load the symbols and run the debugger: http://forums.majorgeeks.com/showthread.php?t=35246

I followed the instructions before, I have followed them again and got the same.

I am setting the symbol search path as: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

But it dosent seem to be working??

Appreciate any help.

Does the computer that's running the debugger have an active Internet connection? If not, you'll have to download the symbols and use them from the local machine (I'm not familiar with doing that).

Ok I had another go, I think previously I only had a few of the symbols not all.

This is the ouput I got this time:


Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Mon Feb 18 18:34:27.126 2008 (GMT+0)
System Uptime: 0 days 0:01:22.907
Loading Kernel Symbols
................................................................................
................................................................................
..
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 113d, 0, b352d008}

GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
*** WARNING: Unable to verify timestamp for CI.dll
*** ERROR: Module load completed but symbols could not be loaded for CI.dll
*** ERROR: Module load completed but symbols could not be loaded for spldr.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for iastor.sys
*** ERROR: Module load completed but symbols could not be loaded for iastor.sys
*** WARNING: Unable to verify timestamp for iastorv.sys
*** ERROR: Module load completed but symbols could not be loaded for iastorv.sys
*** WARNING: Unable to verify timestamp for bcm4sbxp.sys
*** ERROR: Module load completed but symbols could not be loaded for bcm4sbxp.sys
*** WARNING: Unable to verify timestamp for rimmptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rimmptsk.sys
*** WARNING: Unable to verify timestamp for xaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for xaudio.sys
*** WARNING: Unable to verify timestamp for OEM02Vfx.sys
*** ERROR: Module load completed but symbols could not be loaded for OEM02Vfx.sys
*** WARNING: Unable to verify timestamp for btwrchid.sys
*** ERROR: Module load completed but symbols could not be loaded for btwrchid.sys
*** WARNING: Unable to verify timestamp for rimsptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rimsptsk.sys
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for OEM02Dev.sys
*** ERROR: Module load completed but symbols could not be loaded for OEM02Dev.sys
*** WARNING: Unable to verify timestamp for apf7o3pp.SYS
*** ERROR: Module load completed but symbols could not be loaded for apf7o3pp.SYS
*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
*** WARNING: Unable to verify timestamp for rixdptsk.sys
*** ERROR: Module load completed but symbols could not be loaded for rixdptsk.sys
*** WARNING: Unable to verify timestamp for igdkmd32.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
*** WARNING: Unable to verify timestamp for secdrv.SYS
*** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS
*** WARNING: Unable to verify timestamp for NETw4v32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v32.sys
*** WARNING: Unable to verify timestamp for HSXHWAZL.sys
*** ERROR: Module load completed but symbols could not be loaded for HSXHWAZL.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for stwrt.sys
*** ERROR: Module load completed but symbols could not be loaded for stwrt.sys
*** WARNING: Unable to verify timestamp for HSX_CNXT.sys
*** ERROR: Module load completed but symbols could not be loaded for HSX_CNXT.sys
*** WARNING: Unable to verify timestamp for HSX_DPV.sys
*** ERROR: Module load completed but symbols could not be loaded for HSX_DPV.sys
*** WARNING: Unable to verify timestamp for dump_iaStor.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_iaStor.sys
*** WARNING: Unable to verify timestamp for btwavdt.sys
*** ERROR: Module load completed but symbols could not be loaded for btwavdt.sys
*** WARNING: Unable to verify timestamp for btwaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for btwaudio.sys
*** WARNING: Unable to verify timestamp for cdd.dll
*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
*** WARNING: Unable to verify timestamp for ATMFD.DLL
*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
*** ERROR: Symbol file could not be found. Defaulted to export symbols for spsys.sys -
*** WARNING: Unable to verify timestamp for mdmxsdk.sys
*** ERROR: Module load completed but symbols could not be loaded for mdmxsdk.sys
GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0


Probably caused by : ntkrpamp.exe ( nt!ExFreePoolWithTag+17f )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000113d, (reserved)
Arg3: 00000000, Memory contents of the pool block
Arg4: b352d008, Address of the block of pool being deallocated

Debugging Details:
------------------

GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0



POOL_ADDRESS: GetPointerFromAddress: unable to read from 81d315ac
Unable to read MiSystemVaType memory at 81d117e0
b352d008

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: WmiPrvSE.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81ce7ce8 to 81cd8681

STACK_TEXT:
b304bb54 81ce7ce8 000000c2 00000007 0000113d nt!KeBugCheckEx+0x1e
b304bbc8 81d41385 b352d008 00000000 9032873c nt!ExFreePoolWithTag+0x17f
b304bbdc 81d4520b b30407c0 00000000 000000a6 nt!CmpCleanUpKcbValueCache+0x3a
b304bc80 81d3a398 b34ec9a8 b304bcf8 00000001 nt!CmSetValueKey+0xa24
b304bd44 81c8caaa 000001e8 0126eab0 00000000 nt!NtSetValueKey+0x30b
b304bd44 77420f34 000001e8 0126eab0 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0126ea84 00000000 00000000 00000000 00000000 0x77420f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+17f
81ce7ce8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExFreePoolWithTag+17f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

FAILURE_BUCKET_ID: 0xc2_7_nt!ExFreePoolWithTag+17f

BUCKET_ID: 0xc2_7_nt!ExFreePoolWithTag+17f

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



Thanks

Elliot

I would first suggest running a free, bootable memory test on the system. Here's the one that I use: http://www.memtest86.com/

After that it's a matter of looking for drivers that may be causing it. The dump file doesn't include enough info for me to suspect any one driver in particular. Since it's only 2 weeks old, I'd suggest returning it for a new one.

This is the 2nd system I have had, I sent the first 1 back after 2 weeks.

However after getting this system I guessed it was either a driver or software issue.

Is there anyway to test drivers or something of that nature?

I have recently updated the video driver and I havent had a blue screen since then, touch wood!

Cheers

Most often these errors are driver issues - but memory can be involved (since it's an error in accessing memory that actually causes the error).

There's a tool called Driver Verifier that can help - but it hasn't proven very useful to me. Type "verifier" at the Start prompt to activate it. Then you wait for a crash and it'll tell you what it thinks was involved.

Ok thanks, I ran that, dont really know what it did though!!

Annoying there isnt a proper tool to test drivers or whatever.

Thanks for your help anyway.

Driver verifier will help you if:
1) You have it set to check your drivers
2) You've set it to check the correct drivers
3) You remember to check it after the next crash.

But, as I've said before, it hasn't proved useful to me - so I haven't bothered to learn all about what it can do. FWIW - It did tell me what caused my recent crashes, but not why it was crashing.

Ok thanks.

Is there anything else I can do?

Cheers

If it's truly a driver issue - then updating your drivers "should" fix it. But that's a big "IF" and it doesn't always solve the problem. Turn the Driver Verifier on, tell it to monitor unsigned drivers, and keep your eyes open for a BSOD event. Then remember to run Driver Verifier again to see if it'll point out the driver.