Help with Stop Error

mkr10001 · Nov 12, 2009

I followed your guide for debugging a memory dump but unfortunately i have no idea what it means. i have had 5 BSOD's since i got my laptop about mid september and i really want to know why it's getting it's knickers in a twist.
:major

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

Loading Dump File [C:\Windows\Minidump\Mini111109-02.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339
Machine Name:
Kernel base = 0x82640000 PsLoadedModuleList = 0x82757c70
Debug session time: Wed Nov 11 22:20:43.971 2009 (GMT+0)
System Uptime: 0 days 3:25:46.367
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {d, 8811d660, 20707249, 1000000}

Probably caused by : ntkrpamp.exe ( nt!ExpReleasePoolQuota+33 )

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: 0000000d, type of pool violation the caller is guilty of.
Arg2: 8811d660
Arg3: 20707249
Arg4: 01000000

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

FAULTING_IP:
nt!IopFreeIrp+56
826f25e6 e981000000 jmp nt!IopFreeIrp+0xdc (826f266c)

BUGCHECK_STR: 0xc2_d

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

IRP_ADDRESS: 878841e0

LAST_CONTROL_TRANSFER: from 826f2205 to 8270db0d

STACK_TEXT:
bb56cb54 826f2205 000000c2 0000000d 8811d660 nt!KeBugCheckEx+0x1e
bb56cb70 8272d73e 8273bc00 8811d660 0000000f nt!ExpReleasePoolQuota+0x33
bb56cbd0 826f25e6 8811d660 00000000 00000000 nt!ExFreePoolWithTag+0x738
bb56cbec 826f35e3 8811d660 3b41c4f1 00240dc8 nt!IopFreeIrp+0x56
bb56cc34 82674221 87884220 bb56cc64 bb56cc60 nt!IopCompleteRequest+0x40e
bb56cc80 828746ce bb56cc9c 3b41c401 00000001 nt!IopPostProcessIrp+0xdc
bb56ccc4 8284daf1 00000001 bb56ccfc bb56cd14 nt!IoRemoveIoCompletion+0xa2
bb56cd48 8268ac7a 000000b4 01e1f9a0 01e1f990 nt!NtRemoveIoCompletion+0x106
bb56cd48 77705e74 000000b4 01e1f9a0 01e1f990 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
01e1f978 00000000 00000000 00000000 00000000 0x77705e74

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExpReleasePoolQuota+33
826f2205 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExpReleasePoolQuota+33

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a77feb3

FAILURE_BUCKET_ID: 0xc2_d_nt!ExpReleasePoolQuota+33

BUCKET_ID: 0xc2_d_nt!ExpReleasePoolQuota+33

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

Major Attitude · Nov 12, 2009

Sounds like a hardware or driver issue. Easiest to fix if the crash is frequent, so you can run your PC with the minimal hardware. Here is what I would try, in order:

Going back with System Restore to before the problem started might help you know if it is a software problem since a hardware problem would continue even if you restored.

Make sure you have no yellow exclamation points icons in the control panel - system - device manager indicating an obvious hardware problem.

Be sure all your drivers are up to date. This includes sound, video and motherboard.

If that does not solve it, we need to elminate hardware. Best way to do this is to remove anything you can boot and run without. For example, if you have 4 sticks of ram, remove 3. Disconnect and CD\DVD drives. Remove any PCI cards you can run without.

Try Microsoft Windows Memory Diagnostic with all your memory plugged in:
http://majorgeeks.com/Microsoft_Windows_Memory_Diagnostic_d3955.html

FYI, the most difficult to diagnose would be a video card problem since most people do not have a spare video card. Next tough one would be the motherboard since it can cost a couple hundred bucks and take hours to remove.

Let me know if any of these find anything or if I can assist further.

Log in or Sign up

Help with Stop Error

mkr10001 Private E-2

Major Attitude Co-Owner MajorGeeks.Com Staff Member