debug experts needed: BSOD with Bad Pool Header, Bugcheck 19

[punner]

Hello, Debug Experts,

I need help with dump file interpretation:

My computer gives me BSOD from occasionally to every 20 minutes, quite randomly and independent of action and active programmes.

Always Bad Pool Header, BugCheck 19.

Memtest could not detect any errors. Haven't checked any other source of hardware failure, yet.

As this started soon after I bought the computer (14 months) - only very occasionally then - I have no 'working' system to restore. All drivers I could find are updated, including BIOS.

System AMD Athlon 3400, 512 MB RAM, Windows XP, SP2

Please find below result from windows debugger plus result from dumpchk.exe.

Who can help?

Thanks a lot.

Punner

Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Jan 30 22:40:08.765 2006 (GMT+1)

BugCheck 19, {20, e1b0ab48, e1b0abf8, c160402}

Probably caused by : win32k.sys ( win32k!HeavyFreePool+bb )
Followup: MachineOwner

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: e1b0ab48, The pool entry we were looking for within the page.
Arg3: e1b0abf8, The next pool entry.
Arg4: 0c160402, (reserved)

Debugging Details:

BUGCHECK_STR: 0x19_20
POOL_ADDRESS: e1b0ab48
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
LAST_CONTROL_TRANSFER: from 80543c86 to 804f8925
STACK_TEXT:
b023a6c8 80543c86 00000019 00000020 e1b0ab48 nt!KeBugCheckEx+0x1b
b023a718 bf802acb e1b0ab50 00000000 b023a734 nt!ExFreePoolWithTag+0x2a0
b023a728 bf800b93 e1b0ab50 b023a744 bf805a3c win32k!HeavyFreePool+0xbb
b023a734 bf805a3c 81fec290 e1b0ab50 b023a768 win32k!ExFreeToPagedLookasideList+0x1e
b023a744 bf805a7a e1b0ab50 00000004 bf814282 win32k!FreeObject+0x25
b023a750 bf814282 00000001 bf814375 e1b0ab50 win32k!REGION::vDeleteREGION+0x14
b023a758 bf814375 e1b0ab50 b023a7a4 b023a788 win32k!RGNOBJ::vDeleteRGNOBJ+0xc
b023a768 bf8145d7 e1b0ab50 b023a7d4 00000000 win32k!RGNOBJ::bCopy+0x7a
b023a788 bf8262cd b023a7b0 0012f3a0 0012f2d0 win32k!RGNOBJAPI::bCopy+0x23
b023a7bc 8053c808 cd0405e6 380404f0 00000000 win32k!GreCombineRgn+0x50
b023a7bc 7c91eb94 cd0405e6 380404f0 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f3b8 00000000 00000000 00000000 00000000 0x7c91eb94

FOLLOWUP_IP:
win32k!HeavyFreePool+bb
bf802acb 5d pop ebp

SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: win32k!HeavyFreePool+bb
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58
STACK_COMMAND: kb
FAILURE_BUCKET_ID: 0x19_20_win32k!HeavyFreePool+bb
BUCKET_ID: 0x19_20_win32k!HeavyFreePool+bb
Followup: MachineOwner

___________________________________

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 185202e0
PfnDataBase 80557b48
PsLoadedModuleList 805531a0
PsActiveProcessHead 80559258
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 00000019
BugCheckParameter1 00000020
BugCheckParameter2 e1b0ab48
BugCheckParameter3 e1b0abf8
BugCheckParameter4 0c160402
PaeEnabled 00000001
KdDebuggerDataBlock 80544ce0
MiniDumpFields 00000cff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 00002268
ThreadOffset 000024c0
CallStackOffset 00002720
SizeOfCallStack 000003c0
DriverListOffset 00002d70
DriverCount 00000077
StringPoolOffset 000050c8
StringPoolSize 00002330
BrokenDriverOffset 00000000
TriageOptions ffffffff
TopOfStack b023a6b0
DebuggerDataOffset 00002ae0
DebuggerDataSize 00000290
DataBlocksOffset 0000e7f0
DataBlocksCount 00000001


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Jan 30 22:40:08 2006
System Uptime: 0 days 0:05:58
start end module name
804d7000 806cdb80 nt Checksum: 001FAC83 Timestamp: Wed Mar 02 01:34:37 2005 (42250A1D)

Unloaded modules:
b0719000 b0743000 kmixer.sys Timestamp: unavailable (00000000)
ee581000 ee582000 drmkaud.sys Timestamp: unavailable (00000000)
b0743000 b0766000 aec.sys Timestamp: unavailable (00000000)
f860f000 f861c000 DMusic.sys Timestamp: unavailable (00000000)
f85ff000 f860d000 swmidi.sys Timestamp: unavailable (00000000)
f8a5b000 f8a5d000 splitter.sys Timestamp: unavailable (00000000)
ee733000 ee73d000 processr.sys Timestamp: unavailable (00000000)
f2fee000 f2ff3000 Cdaudio.SYS Timestamp: unavailable (00000000)
ee3e1000 ee3e4000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

 

[punner]

debug experts - still needed

Anyone?

Thanks

Punner

 

[cpc2004]

Hi,

You do'nt post the the output 'lm tn" (ie the module list) and it is very useful to diagnostic your problem. One minidump is insufficient to determine the culprit. The prelimary finding is faulty memory such as faulty ram or video memory.

Suggestion
1. Post the output of 3 to 4 minidumps here
2. If your windows has nVidia Firewall, de-install nVidia Firewall
3. Run memtest to stress test the ram
4. Run 3d Mark tp stress test your video card.

 

[punner]

Hi cpc2004,

thanks for your suggestions.
Have run memtest all night - no errors found.
No nVidia Firewall installed.
Have not yet run 3d mark video stress test.

I have attached the output of some more dump files, incl. lm tn (module list). Hope this makes it easier to identify the culprit.

Thanks again

Punner

 

[cpc2004]

Hi,

Your windows are crashed with bugcheck 19 and 8E. From the stack trace of the minidump, I believe that faulty ram is the culprit. Run memtest to stress test the ram.

 

[cpc2004]

Some faulty ram can pass memtest. Reseat the ram to another memory slot.

 

[punner]

Hi cpc2004,

I owe you an answer and a thank you.

Memtest still did not show any errors after 15 hours run for the first ram. I replaced this ram. This time memtest found lots of errors.

In the meantime a checking programme from the HD manufacturer showed that HD has physical failures and I began to think of problems caused by fluctuations of current.

Eventually, I replaced with yet another ram and received a new HD. Now the system seems to work fine.

Not sure why memtext found no problems with first ram and what caused the HD problems but pretty likely the culprit has been the ram, so I have disposed the two ram blocks.

Thanks
Punner

 

[cpc2004]

Hi punner,

Thanks for your reply. Repost if your problem is still un-resolved.