BleepingComputer.com: Bad Pool Caller

That was just from the minidump after the last of the three crashes I just had (not bothering writing down the error messages anymore)

After googeling the first minidump there, I disabled all login screens, figuring that if it didn't fix the underlying problem, it might stop the bluescreening. I have since not had one when coming out of standby (although it didn't always happen before, so that's no clear sign that it workend). Then I got another bluescreen while watching a file in wmp and having ie running in the backgroud, and it pointed to win32k.sys. More memory problems... Here is the minidump analysis:


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


Loading Dump File [C:\WINDOWS\Minidump\Mini041309-04.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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.080814-1236
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Apr 13 16:34:24.776 2009 (GMT+2)
System Uptime: 0 days 6:56:25.079
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf82a074, 99438afc, 0}

Probably caused by : win32k.sys ( win32k!jMapCharset+61 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf82a074, The address that the exception occurred at
Arg3: 99438afc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
win32k!jMapCharset+61
bf82a074 8b30 mov esi,dword ptr [eax]

TRAP_FRAME: 99438afc -- (.trap 0xffffffff99438afc)
ErrCode = 00000000
eax=22000008 ebx=99438bee ecx=99438bd0 edx=000e8001 esi=e2d1aac4 edi=e2d1ce18
eip=bf82a074 esp=99438b70 ebp=99438b7c iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!jMapCharset+0x61:
bf82a074 8b30 mov esi,dword ptr [eax] ds:0023:22000008=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from bf87db0e to bf82a074

STACK_TEXT:
99438b7c bf87db0e 000000ee 99438bd0 99438cb4 win32k!jMapCharset+0x61
99438b98 bf8e51ff 99438cb4 00000001 99438cb4 win32k!PFEOBJ::bFilteredOut+0xbc
99438bd4 bf87dc3f 99438c7c 00000003 99438cb4 win32k!FHOBJ::bScanLists+0x79
99438bf4 bf87dbb5 99438c74 00000001 99438c7c win32k!bScanTheList+0x53
99438c14 bf87e921 99438c74 00000002 99438c74 win32k!bScanFamily+0x43
99438c84 bf87d6ed 00000000 000000ee 00000003 win32k!hefsEngineOnly+0x7b
99438ce8 bf87d80e e1c79008 00000003 e1fb3268 win32k!GreEnumFontOpen+0x136
99438d40 8054162c d2011191 00000003 00000000 win32k!NtGdiEnumFontOpen+0xd5
99438d40 7c90e4f4 d2011191 00000003 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0210a65c 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!jMapCharset+61
bf82a074 8b30 mov esi,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!jMapCharset+61

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49900fc9

FAILURE_BUCKET_ID: 0x8E_win32k!jMapCharset+61

BUCKET_ID: 0x8E_win32k!jMapCharset+61

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

I now got a bluescreen implicating ati3duag.dll

If you can't help, it's understandable. It doesn't seem to easy. But I'd like to know if you've given up on me, so I know to look somewhere else....