Another BSOD-Help

[nuke49]

Trying to get to the bottom of my BSOD problem, could someone please interpret this for me ?
Thanks in advance.

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


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

Symbol search path is: SRV*C:\SymCache*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8280e000 PsLoadedModuleList = 0x82956810
Debug session time: Mon Dec 14 18:12:52.584 2009 (GMT-4)
System Uptime: 3 days 1:13:59.413
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.........
kd> ! analyze -V

Unknown option '-V'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fdf63238, fdf632b8, 4a100018}

Probably caused by : win32k.sys ( win32k!WMsg_midl_user_free+10 )

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

kd> !analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fdf63238, fdf632b8, 4a100018}

Probably caused by : win32k.sys ( win32k!WMsg_midl_user_free+10 )

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

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

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: fdf63238, The pool entry we were looking for within the page.
Arg3: fdf632b8, The next pool entry.
Arg4: 4a100018, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from 82976718
Unable to read MiSystemVaType memory at 82956160
fdf63238

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: EXCEL.EXE

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 947f8c45 to 8292d1b6

STACK_TEXT:
bc833bdc 947f8c45 fdf63240 00000000 bc833bf8 nt!ExFreePoolWithTag+0x1b1
bc833bec 947fa82c fdf63240 bc833c08 947fd588 win32k!WMsg_midl_user_free+0x10
bc833bf8 947fd588 85d47450 fdf63240 bc833c54 win32k!ExFreeToPagedLookasideList+0x1e
bc833c08 947fdaa0 fdf63240 00000004 9480e6f6 win32k!FreeObject+0x23
bc833c14 9480e6f6 bc833c74 9480e11e 28175c52 win32k!REGION::vDeleteREGION+0x14
bc833c1c 9480e11e 28175c52 00000000 00000000 win32k!DC::vReleaseVis+0x29
bc833c54 9480dd5a bc833c74 ffb83008 00000000 win32k!bDeleteDCInternalWorker+0x159
bc833c80 947ae5ce 170119a8 00000001 00000000 win32k!bDeleteDCInternal+0x30
bc833c98 947ad560 170119a8 ffa87160 00000001 win32k!GreDeleteDC+0x13
bc833cb8 94804d28 fe0778e8 170119a8 00000001 win32k!DestroyCacheDC+0xdd
bc833cd4 947c608f 170119a8 00000000 00000000 win32k!ReleaseCacheDC+0x58
bc833ce8 9480dd86 170119a8 170119a8 00000000 win32k!UserReleaseDC+0x15
bc833d08 947ef9d9 170119a8 00000000 00000000 win32k!bDeleteDCInternal+0x5c
bc833d28 8285142a 170119a8 0012e304 77f064f4 win32k!NtGdiDeleteObjectApp+0xa0
bc833d28 77f064f4 170119a8 0012e304 77f064f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e304 00000000 00000000 00000000 00000000 0x77f064f4


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!WMsg_midl_user_free+10
947f8c45 5d pop ebp

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: win32k!WMsg_midl_user_free+10

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc2a2

FAILURE_BUCKET_ID: 0x19_20_win32k!WMsg_midl_user_free+10

BUCKET_ID: 0x19_20_win32k!WMsg_midl_user_free+10

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

 

[zigzag3143]

Nuke49

Bad pool error description and possible fis here Bad Pool Header - How to Fix the Blue Screen Bad Pool Header Error

Ken J+

 

[nuke49]

Registry Cleaner

Could you recommend a free registry cleaner, what is your opinion of CCleaner?

 

[Tews]

What about your initial problem... was that resolved??

 

[nuke49]

BSOD

According to Ken J it was a registry problem and I never touched a thing but haven't had a problem for 4 days.