BleepingComputer.com: Need help with debugged BSOD dump.

I followed this tutorial here on how to debug a BSOD dump file:

http://www.bleepingcomputer.com/forums/topic176011.html

And it told me to post my results here to recieve help with determining what caused the BSOD and how I can fix it. So here it is:

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


Loading Dump File [C:\Users\Kyle\AppData\Local\Microsoft\Windows\WER\ReportQueue\Report030bb4bd\Mini111208-01.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 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
Kernel base = 0x81e16000 PsLoadedModuleList = 0x81f2dc70
Debug session time: Wed Nov 12 00:03:00.360 2008 (GMT-5)
System Uptime: 0 days 6:09:01.587
Loading Kernel Symbols
..........................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 92ad7374, b25d5b08, 0}

Probably caused by : win32k.sys ( win32k!PFEOBJ::vFreepfdg+4a )

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

1: 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: 92ad7374, The address that the exception occurred at
Arg3: b25d5b08, 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!PFEOBJ::vFreepfdg+4a
92ad7374 66f741200080	test	word ptr [ecx+20h],8000h

TRAP_FRAME:  b25d5b08 -- (.trap 0xffffffffb25d5b08)
ErrCode = 00000000
eax=fe2812d8 ebx=00000000 ecx=00000001 edx=00000000 esi=b25d5ba4 edi=fcb893a8
eip=92ad7374 esp=b25d5b7c ebp=b25d5b8c iopl=0		 nv up ei pl nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000			 efl=00010213
win32k!PFEOBJ::vFreepfdg+0x4a:
92ad7374 66f741200080	test	word ptr [ecx+20h],8000h ds:0023:00000021=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  left4dead.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 92bb07aa to 92ad7374

STACK_TEXT:  
b25d5b8c 92bb07aa fd2e98e0 00000000 00000000 win32k!PFEOBJ::vFreepfdg+0x4a
b25d5bac 92c2bfd9 00000000 00000000 00000001 win32k!RFONTOBJ::vDeleteRFONT+0x1d
b25d5be4 92b884ca b25d5c08 00000000 fe1880f0 win32k!vRestartKillRFONTList+0x7b
b25d5c18 92b35742 0000000b fe1880f0 00000000 win32k!PFTOBJ::bUnloadWorkhorse+0x115
b25d5c44 92b35e2e fc8f2170 00000000 00000000 win32k!vCleanupPrivateFonts+0x4d
b25d5c5c 92b34ead fc8f2170 00000000 00000000 win32k!NtGdiCloseProcess+0x13d
b25d5c7c 92b36711 fc8f2170 00000000 866f5250 win32k!GdiProcessCallout+0x145
b25d5c98 82024ec3 84d3ed90 00000000 f4e84ffc win32k!W32pProcessCallout+0x5d
b25d5d04 820253fb 00000000 00000000 869a5d78 nt!PspExitThread+0x4a0
b25d5d24 81ff9160 869a5d78 00000000 00000001 nt!PspTerminateThreadByPointer+0x5b
b25d5d54 81e6da1a ffffffff 00000000 0012fe94 nt!NtTerminateProcess+0x1e0
b25d5d54 76f49a94 ffffffff 00000000 0012fe94 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fe94 00000000 00000000 00000000 00000000 0x76f49a94


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!PFEOBJ::vFreepfdg+4a
92ad7374 66f741200080	test	word ptr [ecx+20h],8000h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!PFEOBJ::vFreepfdg+4a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48d1b9ef

FAILURE_BUCKET_ID:  0x8E_win32k!PFEOBJ::vFreepfdg+4a

BUCKET_ID:  0x8E_win32k!PFEOBJ::vFreepfdg+4a

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

My system specs:

Windows Vista Home Premium 32-bit
nVidia geForce 8800 GTS 512mb
2GB DDR2 RAM
Intel Core 2 Duo E8400 Wolfdale 3.0GHz

Any help finding the source of my BSOD is greatly appreciated!

I suspect it's a game that runs the LEFT4DEAD.EXE file that's causing your issues.
It seems to cause a memory access crash in WIN32K.SYS (a critical Windows system file).

There's some question on the web about this being a virus. The 2 major causes of BSOD's are drivers and malware.

So, I'd suggest a couple of free, online scans that are in this link: http://www.bleepingcomputer.com/blogs/usas...?showentry=1252

If you come up clean, uninstall the LEFT4DEAD game and that will most likely cure the BSOD's

usasma, on Nov 12 2008, 06:15 AM, said:

Alright it looks like it's simply a matter of a poorly written program probably murdering my graphics card drivers or Windows.

I guess I'll just have to sit back and wait for the developers to fix the problems.