Blue screens

It's done here's the log again:

Opened log file 'c:\debuglog.txt'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/Symbols;C:\WINDOWS\symbols

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/Symbols;C:\WINDOWS\symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sun Jan 02 20:14:20 2005
System Uptime: 0 days 0:02:12.170
Loading Kernel Symbols
...................................................................................................................................................................................................
Loading unloaded module list
..........
Loading User Symbols
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, bf8010fd, f54b3a48, 0}

Probably caused by : win32k.sys ( win32k!TimersProc+45 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf8010fd, The address that the exception occurred at
Arg3: f54b3a48, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ( "%s ") op het geheugen is mislukt.

FAULTING_IP:
win32k!TimersProc+45
bf8010fd 8b4624 mov eax,[esi+0x24]

TRAP_FRAME: f54b3a48 -- (.trap fffffffff54b3a48)
.trap fffffffff54b3a48
ErrCode = 00000000
eax=9000004b ebx=000000be ecx=9000004b edx=00000204 esi=18e21678 edi=0000003d
eip=bf8010fd esp=f54b3abc ebp=f54b3ad4 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
win32k!TimersProc+0x45:
bf8010fd 8b4624 mov eax,[esi+0x24] ds:0023:18e2169c=????????
.trap
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf8aec95 to bf8010fd

STACK_TEXT:
f54b3ad4 bf8aec95 00000022 006dfff4 bf800fd1 win32k!TimersProc+0x45
f54b3d30 bf8c8594 f54c34a8 00000002 f54b3d54 win32k!RawInputThread+0x634
f54b3d40 bf800ff4 f54c34a8 f54b3d64 006dfff4 win32k!xxxCreateSystemThreads+0x60
f54b3d54 804df06b 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f54b3d54 7c90eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
006dffe0 75b053d6 75b0b10b 00000000 00000022 ntdll!KiFastSystemCallRet
006dffe8 00000000 00000022 00000004 00000000 winsrv!NtUserCallOneParam+0xc


FOLLOWUP_IP:
win32k!TimersProc+45
bf8010fd 8b4624 mov eax,[esi+0x24]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!TimersProc+45

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a

STACK_COMMAND: .trap fffffffff54b3a48 ; kb

BUCKET_ID: 0x8E_win32k!TimersProc+45

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

eax=ffdff13c ebx=bf8010fd ecx=00000000 edx=804dba16 esi=f54b39f4 edi=00000000
eip=805339ae esp=f54b35f8 ebp=f54b3610 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x1b:
805339ae 5d pop ebp
ChildEBP RetAddr Args to Child
f54b3610 8051dea6 0000008e c0000005 bf8010fd nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f54b39d8 804dfada f54b39f4 00000000 f54b3a48 nt!KiDispatchException+0x3b1 (FPO: [Non-Fpo])
f54b3a40 804dfa86 f54b3ad4 bf8010fd badb0d00 nt!CommonDispatchException+0x4d (FPO: [0,20,0])
f54b3a5c 804dbde0 f54b3ab4 855c49e8 ffdff120 nt!Kei386EoiHelper+0x18a
f54b3a70 804dc6bc 00000000 00000023 00000023 nt!KiSwapContext+0x2e (FPO: [EBP 0xf54b3ab4] [0,0,4])
f54b3ad4 bf8aec95 00000022 006dfff4 bf800fd1 nt!KiSwapThread+0x68 (FPO: [0,0,0])
f54b3d30 bf8c8594 f54c34a8 00000002 f54b3d54 win32k!RawInputThread+0x634 (FPO: [Non-Fpo])
f54b3d40 bf800ff4 f54c34a8 f54b3d64 006dfff4 win32k!xxxCreateSystemThreads+0x60 (FPO: [Non-Fpo])
f54b3d54 804df06b 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23 (FPO: [Non-Fpo])
f54b3d54 7c90eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f54b3d64)
006dffe0 75b053d6 75b0b10b 00000000 00000022 ntdll!KiFastSystemCallRet (FPO: [0,0,0])
006dffe8 00000000 00000022 00000004 00000000 winsrv!NtUserCallOneParam+0xc
start end module name
4a680000 4a685000 csrss csrss.exe Wed Aug 04 08:03:11 2004 (41107C1F)
75ae0000 75aeb000 CSRSRV CSRSRV.dll Wed Aug 04 10:02:06 2004 (411097FE)
75af0000 75b00000 basesrv basesrv.dll Wed Aug 04 10:01:54 2004 (411097F2)
75b00000 75b4a000 winsrv winsrv.dll Wed Aug 04 10:02:58 2004 (41109832)
75e30000 75ee0000 sxs sxs.dll Wed Aug 04 10:05:40 2004 (411098D4)
77b00000 77b22000 Apphelp Apphelp.dll Wed Aug 04 10:02:30 2004 (41109816)

There ya go

 

Well, thats a new one on me. I have no suggestions for whats causing this. These last two are pretty wierd crashes. Just based on the history, there must be some relationship to the video, but without debugging it myself, i can't be sure.

Lets cut to the chase on this one. We suspect the video card is causing the problem. We've tried a number of combinations of drivers with no results. Do you have access to a different video card, so we can pull this one out of the machine?

 

first of all, the last two posts I made are the same crashes, only one is with the updated symbols. Then I am now running omega drivers, could that be the problem? Ill try to make another crash, last crash happened after 5 mins of battle for middle earth, so who knows

 

i was referring to post #13 and #21 as the 'last two' crashes.

 

Here is another one, Ill try to get another video card I guess

Opened log file 'c:\debuglog.txt'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\WINDOWS\symbols

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\WINDOWS\symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Jan 03 16:46:33 2005
System Uptime: 0 days 0:28:06.783
Loading Kernel Symbols
.....................................................................................................................................................................................................
Loading unloaded module list
............
Loading User Symbols
...........................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, bfa435a7, f0bb0638, 0}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for nv4_disp.dll -
Probably caused by : nv4_disp.dll ( nv4_disp+705a7 )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bfa435a7, The address that the exception occurred at
Arg3: f0bb0638, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ( "%s ") op het geheugen is mislukt.

FAULTING_IP:
nv4_disp+705a7
bfa435a7 8938 mov [eax],edi

TRAP_FRAME: f0bb0638 -- (.trap fffffffff0bb0638)
.trap fffffffff0bb0638
ErrCode = 00000002
eax=00e4a757 ebx=00000000 ecx=e1c4e2c0 edx=e4a75781 esi=e4a75700 edi=80e4a757
eip=bfa435a7 esp=f0bb06ac ebp=e1c4e2c0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nv4_disp+0x705a7:
bfa435a7 8938 mov [eax],edi ds:0023:00e4a757=0340048d
.trap
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 00000000 to bfa435a7

STACK_TEXT:
e1c4e2c0 00000000 e4a95cc0 e24067d0 00003eb9 nv4_disp+0x705a7


FOLLOWUP_IP:
nv4_disp+705a7
bfa435a7 8938 mov [eax],edi

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nv4_disp+705a7

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 40f6d75c

STACK_COMMAND: .trap fffffffff0bb0638 ; kb

BUCKET_ID: 0x8E_nv4_disp+705a7

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

eax=ffdff13c ebx=bfa435a7 ecx=00000000 edx=804dba16 esi=f0bb05e4 edi=00000000
eip=805339ae esp=f0bb01e8 ebp=f0bb0200 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x1b:
805339ae 5d pop ebp
ChildEBP RetAddr Args to Child
f0bb0200 8051dea6 0000008e c0000005 bfa435a7 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f0bb05c8 804dfada f0bb05e4 00000000 f0bb0638 nt!KiDispatchException+0x3b1 (FPO: [Non-Fpo])
f0bb0630 804dfa86 e1c4e2c0 bfa435a7 badb0d00 nt!CommonDispatchException+0x4d (FPO: [0,20,0])
f0bb0644 804f2355 e3c9b124 c038f26c 00000000 nt!Kei386EoiHelper+0x18a
f0bb06b0 bfa45cf2 e4a75700 e4a75781 e4a75700 nt!MiDispatchFault+0xf9 (FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be wrong.
e4a75700 e4a74e80 0000001f 00000000 00000000 nv4_disp+0x72cf2
e4a75700 e4a74e80 0000001f 00000000 00000000 0xe4a74e80
e494ea80 e4a75700 00000002 00000000 00000000 0xe4a74e80
e25fad80 e494ea80 00000002 00000000 00000000 0xe4a75700
e25fae80 e25fad80 00000002 00000000 00000000 0xe494ea80
e25faf80 e25fae80 00000002 00000000 00000000 0xe25fad80
e25fb080 e25faf80 00000002 00000000 00000000 0xe25fae80
e4931dc0 e25fb080 00000002 00000000 00000000 0xe25faf80
e25fd680 e4931dc0 00000002 00000000 00000000 0xe25fb080
e25fd780 e25fd680 00000002 00000000 00000000 0xe4931dc0
e25fd880 e25fd780 00000002 00000000 00000000 0xe25fd680
e25fd980 e25fd880 00000002 00000000 00000000 0xe25fd780
e4a8bd00 e25fd980 00000006 00000000 00000000 0xe25fd880
e4a8bf40 e4a8bd00 00000006 00000000 00000000 0xe25fd980
e4a8c180 e4a8bf40 00000006 00000000 00000000 0xe4a8bd00
start end module name
00400000 01455000 game game.dat Mon Nov 15 00:31:17 2004 (4197EAC5)
02800000 028ec000 DBGHELP DBGHELP.DLL Thu Oct 23 20:11:02 2003 (3F9819B6)

 

Another one, happened when firefox and Msn were running:

Opened log file 'c:\debuglog.txt'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\WINDOWS\symbols

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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\WINDOWS\symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Jan 03 21:58:39 2005
System Uptime: 0 days 5:06:21.662
Loading Kernel Symbols
.....................................................................................................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
..........................................................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, e2ec8368, e2ec83a0, c070401}

*** ERROR: Module load completed but symbols could not be loaded for msnmsgr.exe
Probably caused by : win32k.sys ( win32k!HeavyFreePool+bb )

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

kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* 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: e2ec8368, The pool entry we were looking for within the page.
Arg3: e2ec83a0, The next pool entry.
Arg4: 0c070401, (reserved)

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


BUGCHECK_STR: 0x19_20

POOL_ADDRESS: e2ec8368 Paged pool

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8054be41 to 805339ae

STACK_TEXT:
87ad5190 8054be41 00000019 00000020 e2ec8368 nt!KeBugCheckEx+0x1b
87ad51e0 bf8029ef e2ec8370 00000000 87ad5208 nt!ExFreePoolWithTag+0x2be
87ad51f0 bf80e42f e2ec8370 87ad5274 e2ec8370 win32k!HeavyFreePool+0xbb
87ad5208 bf80e57e e2ec8370 0006ec44 87ad5224 win32k!HMFreeObject+0xa0
87ad5218 bf802c9e e2ec8370 87ad523c bf80e522 win32k!FreeTimer+0x53
87ad5224 bf80e522 bc693f68 012b2a10 00000000 win32k!FindTimer+0x3c
87ad523c bf80e5a2 bc693f68 012b2a10 00000000 win32k!KillTimer2+0x1d
87ad5250 bf80e5d3 bc693f68 012b2a10 0006ec44 win32k!_KillTimer+0x12
87ad5264 804df06b 00010a38 012b2a10 0006ec68 win32k!NtUserKillTimer+0x2a
87ad5264 7c90eb94 00010a38 012b2a10 0006ec68 nt!KiFastCallEntry+0xf8
0006ec30 77d18c26 00546863 00010a38 012b2a10 ntdll!KiFastSystemCallRet
0006ec68 004a8ddf 01f92a40 01f92a40 0006ef18 USER32!NtUserKillTimer+0xc
WARNING: Stack unwind information not available. Following frames may be wrong.
0006ec84 004a8f78 01f92a40 00602ec0 00000000 msnmsgr+0xa8ddf
0006eee8 00675c9d 00dc8dc0 01f8ff38 0006ef80 msnmsgr+0xa8f78
0006ef28 00675d44 00dc8dc0 0006ef80 006810f9 msnmsgr+0x275c9d
0006ef6c 00671794 00dc8dc0 0006ef80 00000001 msnmsgr+0x275d44
0006ef94 00673485 00dc8dc0 00000002 000a0cc8 msnmsgr+0x271794
0006efe0 00673462 000a0cc8 00dc8d70 00673505 msnmsgr+0x273485
0006f024 00673462 000a0cc8 00dc8d20 00673505 msnmsgr+0x273462
0006f068 00673462 000a0cc8 00dc8cd0 00673505 msnmsgr+0x273462
0006f0ac 00673462 000a0cc8 00dc84b0 00673505 msnmsgr+0x273462
0006f0f0 00673462 000a0cc8 00dc8460 00673505 msnmsgr+0x273462
0006f134 00673462 000a0cc8 00dc83c0 00673505 msnmsgr+0x273462
0006f178 00673462 000a0cc8 00dc6190 00673505 msnmsgr+0x273462
0006f1bc 00673462 000a0cc8 00dc5dc0 00673505 msnmsgr+0x273462
0006f200 00673462 000a0cc8 00dc5d20 00673505 msnmsgr+0x273462
0006f244 00673462 000a0cc8 00dc5cd0 00673505 msnmsgr+0x273462
0006f288 00673462 000a0cc8 00dc5af0 00673505 msnmsgr+0x273462
0006f2cc 00673462 00010a38 00dc0300 00673930 msnmsgr+0x273462
0006f30c 0067f8b1 00dc2050 006854a9 00000000 msnmsgr+0x273462
0006f350 77d18709 00010a38 00000082 00000000 msnmsgr+0x27f8b1
0006f37c 77d187eb 006202de 00010a38 00000082 USER32!InternalCallWinProc+0x28
0006f3e4 77d1c00e 00000000 006202de 00010a38 USER32!UserCallWinProcCheckWow+0x150
0006f414 77d1c034 006202de 00010a38 00000082 USER32!CallWindowProcAorW+0x98
0006f434 773a1aeb 006202de 00010a38 00000082 USER32!CallWindowProcW+0x1b
0006f450 773a1e3e 00010a38 00000082 00000000 comctl32!CallOriginalWndProc+0x1a
0006f4ac 773a2000 01e8e0b0 00010a38 00000082 comctl32!CallNextSubclassProc+0x3c
0006f4d0 7740d5e8 00010a38 00000082 00000000 comctl32!DefSubclassProc+0x46
0006f4ec 773a1e3e 00010a38 00000082 00000000 comctl32!TTSubclassProc+0x59
0006f548 773a2063 01e8e0b0 00010a38 00000082 comctl32!CallNextSubclassProc+0x3c
0006f59c 77d18709 00010a38 00000082 00000000 comctl32!MasterSubclassProc+0x54
0006f5c8 77d1d297 773a200f 00010a38 00000082 USER32!InternalCallWinProc+0x28
0006f630 77d1b368 00000000 773a200f 00010a38 USER32!UserCallWinProcCheckWow+0xea
0006f684 77d1e639 00a13f68 00000082 00000000 USER32!DispatchClientMessage+0xa3
0006f6b4 7c90eae3 0006f6c4 00000018 00a13f68 USER32!__fnNCDESTROY+0x26
0006f6d8 77d1e672 004a067c 00010a36 00000010 ntdll!KiUserCallbackDispatcher+0x13
87ad5528 80566730 87ad55ec 87ad55e8 87ad55b8 nt!KiCallUserMode+0x4
87ad5584 bf8fc253 00000003 87ad55c8 00000018 nt!KeUserModeCallback+0x87
87ad560c bf813ea0 bc693f68 00000082 00000000 win32k!SfnNCDESTROY+0xac
87ad5654 bf814092 00693f68 00000082 00000000 win32k!xxxSendMessageToClient+0x176


FOLLOWUP_IP:
win32k!HeavyFreePool+bb
bf8029ef 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: 41107f7a

STACK_COMMAND: kb

BUCKET_ID: 0x19_20_win32k!HeavyFreePool+bb

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

eax=ffdff13c ebx=e2ec8368 ecx=00000000 edx=00000006 esi=e2ec8368 edi=e2ec8370
eip=805339ae esp=87ad5178 ebp=87ad5190 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000286
nt!KeBugCheckEx+0x1b:
805339ae 5d pop ebp
ChildEBP RetAddr Args to Child
87ad5190 8054be41 00000019 00000020 e2ec8368 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
87ad51e0 bf8029ef e2ec8370 00000000 87ad5208 nt!ExFreePoolWithTag+0x2be (FPO: [Non-Fpo])
87ad51f0 bf80e42f e2ec8370 87ad5274 e2ec8370 win32k!HeavyFreePool+0xbb (FPO: [Non-Fpo])
87ad5208 bf80e57e e2ec8370 0006ec44 87ad5224 win32k!HMFreeObject+0xa0 (FPO: [Non-Fpo])
87ad5218 bf802c9e e2ec8370 87ad523c bf80e522 win32k!FreeTimer+0x53 (FPO: [Non-Fpo])
87ad5224 bf80e522 bc693f68 012b2a10 00000000 win32k!FindTimer+0x3c (FPO: [Non-Fpo])
87ad523c bf80e5a2 bc693f68 012b2a10 00000000 win32k!KillTimer2+0x1d (FPO: [Non-Fpo])
87ad5250 bf80e5d3 bc693f68 012b2a10 0006ec44 win32k!_KillTimer+0x12 (FPO: [Non-Fpo])
87ad5264 804df06b 00010a38 012b2a10 0006ec68 win32k!NtUserKillTimer+0x2a (FPO: [Non-Fpo])
87ad5264 7c90eb94 00010a38 012b2a10 0006ec68 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ 87ad5274)
0006ec30 77d18c26 00546863 00010a38 012b2a10 ntdll!KiFastSystemCallRet (FPO: [0,0,0])
0006ec68 004a8ddf 01f92a40 01f92a40 0006ef18 USER32!NtUserKillTimer+0xc
WARNING: Stack unwind information not available. Following frames may be wrong.
0006ec84 004a8f78 01f92a40 00602ec0 00000000 msnmsgr+0xa8ddf
0006eee8 00675c9d 00dc8dc0 01f8ff38 0006ef80 msnmsgr+0xa8f78
0006ef28 00675d44 00dc8dc0 0006ef80 006810f9 msnmsgr+0x275c9d
0006ef6c 00671794 00dc8dc0 0006ef80 00000001 msnmsgr+0x275d44
0006ef94 00673485 00dc8dc0 00000002 000a0cc8 msnmsgr+0x271794
0006efe0 00673462 000a0cc8 00dc8d70 00673505 msnmsgr+0x273485
0006f024 00673462 000a0cc8 00dc8d20 00673505 msnmsgr+0x273462
0006f068 00673462 000a0cc8 00dc8cd0 00673505 msnmsgr+0x273462
start end module name
00400000 008be000 msnmsgr msnmsgr.exe Sat May 29 00:22:15 2004 (40B7BB97)
019a0000 019b1000 nl_msgc nl_msgc.dll Tue Mar 30 22:47:41 2004 (4069DCED)
03270000 032fc000 shdoclc shdoclc.dll Wed Aug 04 10:02:45 2004 (41109825)
0ffd0000 0fff8000 rsaenh rsaenh.dll Wed Jul 07 04:17:12 2004 (40EB5D28)


Looks like something new right? Thx for the help again

 

The first one is the video driver again. This latest one is a corrupt pool memory block

 

I think in the end I'll have to bring my computer store right? Problem as that standard procedure there is that if they haven't found the problem within 2 minutes, they format the HD, because that solves 98% of the problems they get there. And although I rather don't format my HD at all, I think I'll do it myself today or tomorrow, then I can at least make backups and install everything the way I like it.

Got any tips on general programs that are useful? (windows related, spyware etc.), or do you think formatting has a small chance of solving this problem?

 

Did you try Ben's suggestion he made in post #22? Here it is (with color added)...

It appears to me that Ben's trying to see if your problem is, in fact, related to the video card. If you could swap video cards and report back to Ben whether the blue screens continue or the problem goes away, then perhaps Ben can make a new suggestion based on that information.

Perhaps swapping out your suspect video card with a different one would be less hassle than reformatting the HD and reinstalling Windows. If you don't have a spare video card, perhaps one of your local shops or a friend would be willing to loan you one.