STOP: 0x000000c5 (0x00002a98, 0x00000002, 0x00000000, 0x8290815e)

Status
Not open for further replies.
Hello, I had a bluescreen today on my HP HDX 9350EB.
I have them occasionally.
Here's the error code : 0x000000c5 (0x00002a98, 0x00000002, 0x00000000, 0x8290815e)
I'll also post the Windows Debugging Tools analysis:
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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


Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8281b000 PsLoadedModuleList = 0x82932c70
Debug session time: Sun Apr 12 17:56:55.469 2009 (GMT+2)
System Uptime: 0 days 0:00:19.344
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C5, {2a98, 2, 0, 8290815e}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+159 )

Followup: Pool_corruption
---------

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

DRIVER_CORRUPTED_EXPOOL (c5)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is
caused by drivers that have corrupted the system pool. Run the driver
verifier against any new (or suspect) drivers, and if that doesn't turn up
the culprit, then use gflags to enable special pool.
Arguments:
Arg1: 00002a98, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8290815e, address which referenced memory

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


BUGCHECK_STR: 0xC5_2

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeferredFreePool+159
8290815e 8b10 mov edx,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: 80599b0c -- (.trap 0xffffffff80599b0c)
ErrCode = 00000000
eax=00002a98 ebx=0000000b ecx=000001ff edx=8291d76c esi=8291d76c edi=8291d6e0
eip=8290815e esp=80599b80 ebp=80599bb8 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210202
nt!ExDeferredFreePool+0x159:
8290815e 8b10 mov edx,dword ptr [eax] ds:0023:00002a98=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8290815e to 82875d24

STACK_TEXT:
80599b0c 8290815e badb0d00 8291d76c 00000000 nt!KiTrap0E+0x2ac
80599bb8 829096e0 8291d6e0 00000001 8294fd48 nt!ExDeferredFreePool+0x159
80599c20 8298aaba 863c94c8 00000000 80812c34 nt!ExFreePoolWithTag+0x852
80599c38 82b7709d 8080e7c4 00000000 00000000 nt!IopCallDriverReinitializationRoutines+0x4f
80599c94 82b7acba 80812c34 85168910 851685e8 nt!IoInitSystem+0x654
80599d74 82973af1 80599dc0 829f0b18 80812c34 nt!Phase1InitializationDiscard+0xb86
80599d7c 829f0b18 80812c34 ab1469e3 00000000 nt!Phase1Initialization+0xd
80599dc0 82849a2e 82973ae4 80812c34 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExDeferredFreePool+159
8290815e 8b10 mov edx,dword ptr [eax]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!ExDeferredFreePool+159

FOLLOWUP_NAME: Pool_corruption

IMAGE_NAME: Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+159

BUCKET_ID: 0xC5_2_nt!ExDeferredFreePool+159

Followup: Pool_corruption
---------

I hope someone can help me out
Thanks,
Maarten
 
Your error is caused by either faulty drivers or buggy software. My first advice is go to HP's website, find your particular model, and and update your drivers for your system.
 
Status
Not open for further replies.
Back