Hi all.  I've been having a PROBLEM with my computer where it randomly give a BSOD.  I'm not sure what's causing it as I'm never doing anything intensive when it happens.  Here are my specs:
OS: Windows XP (SP2)
Processor: 2.8 ghz dual core
Memory: 3gigs
Video card: Nvida GeForce 8600 GT

Here's my latest crash dump if that helps: Code: [Select]Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070208-02.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 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Jul  2 22:23:28.494 2008 (GMT-5)
System Uptime: 0 days 4:31:42.958
Loading Kernel Symbols
...
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf808bf5, b5366828, 0}

Probably caused by : win32k.sys ( win32k!DC::bSetDefaultRegion+82 )

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: bf808bf5, The address that the exception occurred at
Arg3: b5366828, 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!DC::bSetDefaultRegion+82
bf808bf5 8b830c040000    mov     eax,dword ptr [ebx+40Ch]

TRAP_FRAME:  b5366828 -- (.trap 0xffffffffb5366828)
ErrCode = 00000000
eax=89d63cb0 ebx=00000080 ecx=00000000 edx=00000000 esi=e1eba2d8 edi=b53668c8
eip=bf808bf5 esp=b536689c ebp=b53668d8 iopl=0         nv up EI ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
win32k!DC::bSetDefaultRegion+0x82:
bf808bf5 8b830c040000    mov     eax,dword ptr [ebx+40Ch] ds:0023:0000048c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  firefox.exe

LAST_CONTROL_TRANSFER:  from bf80d446 to bf808bf5

STACK_TEXT: 
b53668d8 bf80d446 e5a119c8 bf80d0ba 00000000 win32k!DC::bSetDefaultRegion+0x82
b536690c bf80d0fe e1eba2d8 00000001 00000000 win32k!GreCreateDisplayDC+0x118
b5366928 805409ac e5a119c8 0013e870 7c90eb94 win32k!GreCreateCompatibleDC+0x2c
b5366928 7c90eb94 e5a119c8 0013e870 7c90eb94 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013e870 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!DC::bSetDefaultRegion+82
bf808bf5 8b830c040000    mov     eax,dword ptr [ebx+40Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!DC::bSetDefaultRegion+82

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47e0e106

FAILURE_BUCKET_ID:  0x8E_win32k!DC::bSetDefaultRegion+82

BUCKET_ID:  0x8E_win32k!DC::bSetDefaultRegion+82

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

is the firmware on your bios up to date? if not, then update it.

also dust the inside to reduce heating of internal parts.Do I really need to update my bios?  For one thing that has been happening for a few months (~last september, although it has increased in frequency in the past month).  Also, I just cleaned out my case a few weeks ago so I don't think it's a build up of dust...FLUSHING BIOS is seldomly necessary. I wouldn't even think about it.

Your log shows win32k.sys several times as being at fault.
Possible numerous causes: bad RAM, bad driver, corrupt system file itself.
I'd start with couple of things...
Are there any errors in Device Manager?
Unistalling/reinstalling video driver may be worth trying.

Also, go Start>Run, type in:
sfc /scannow
Have Windows XP CD handy.