XP New Installation Dump Data

I decided to bite the bullet and install XP. Installed all updates from Microsoft and ran Spybot SD and Pest Patrol. All seems to be going smoothly, aside from XP thinking it hasn't installed my printer yet (Which it has, it works and everything) and one random restart that happened without warning while I was checking my yahoo mail.

I immediately went hunting for a dump file, but all I could find was a "minidump ". I ran that though the Wizard, so here's hoping...



Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini033005-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: 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
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Mar 30 17:11:37.656 2005 (GMT-5)
System Uptime: 0 days 0:30:01.247
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
.............
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, 80042000, 0, 0}

Probably caused by : win32k.sys ( win32k!NtGdiDrawStream+9f )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from bf817e3e to f33ca754

UNALIGNED_STACK_POINTER: f33da636

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f33ca728 bf817e3e 1d0105f6 00000000 00000000 0xf33ca754
f33ca870 804df06b 1d0105f6 00000060 0013b3a0 win32k!NtGdiDrawStream+0x9f
f33ca870 7c90eb94 1d0105f6 00000060 0013b3a0 nt!KiFastCallEntry+0xf8
0013b214 00000000 00000000 00000000 00000000 0x7c90eb94
f33cab44 80566730 f33cac00 f33cac04 f33cabd4 nt!KiCallUserMode+0x4
f33caba0 bf813d09 00000002 f33cabe4 00000018 nt!KeUserModeCallback+0x87
f33cac24 bf813ea0 bbe6a528 0000000f 00000000 win32k!SfnDWORD+0xa8
f33cac6c bf814092 40e6a528 0000000f 00000000 win32k!xxxSendMessageToClient+0x176
f33cacb8 bf80f470 bbe6a528 0000000f 00000000 win32k!xxxSendMessageTimeout+0x1a6
f33cacdc bf81eee5 bbe6a528 0000000f 00000000 win32k!xxxSendMessage+0x1b
f33cad08 bf81edb5 bbe6a528 00000001 0013e124 win32k!xxxUpdateWindow2+0x79
f33cad28 bf8319f6 bbe6a528 00000001 f33cad54 win32k!xxxInternalUpdateWindow+0x6f
f33cad38 bf831a4d bbe6a528 0013e124 00000000 win32k!xxxUpdateWindow+0xf
f33cad54 804df06b 00050218 0000005e 0013e124 win32k!NtUserCallHwndLock+0x4b
f33cad54 7c90eb94 00050218 0000005e 0013e124 nt!KiFastCallEntry+0xf8
0013e0e8 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
win32k!NtGdiDrawStream+9f
bf817e3e 8985e0feffff mov [ebp-0x120],eax

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!NtGdiDrawStream+9f

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x7f_8_win32k!NtGdiDrawStream+9f

BUCKET_ID: 0x7f_8_win32k!NtGdiDrawStream+9f

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

eax=00000058 ebx=00000000 ecx=f33ca724 edx=00000000 esi=0013b400 edi=f33ca7b4
eip=f33ca754 esp=f33da636 ebp=f33ca728 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
f33ca754 53 push ebx
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
f33ca728 bf817e3e 1d0105f6 00000000 00000000 0xf33ca754
f33ca870 804df06b 1d0105f6 00000060 0013b3a0 win32k!NtGdiDrawStream+0x9f (FPO: [Non-Fpo])
f33ca870 7c90eb94 1d0105f6 00000060 0013b3a0 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f33ca884)
0013b214 00000000 00000000 00000000 00000000 0x7c90eb94
f33cab44 80566730 f33cac00 f33cac04 f33cabd4 nt!KiCallUserMode+0x4 (FPO: [2,3,4])
f33caba0 bf813d09 00000002 f33cabe4 00000018 nt!KeUserModeCallback+0x87 (FPO: [Non-Fpo])
f33cac24 bf813ea0 bbe6a528 0000000f 00000000 win32k!SfnDWORD+0xa8 (FPO: [Non-Fpo])
f33cac6c bf814092 40e6a528 0000000f 00000000 win32k!xxxSendMessageToClient+0x176 (FPO: [Non-Fpo])
f33cacb8 bf80f470 bbe6a528 0000000f 00000000 win32k!xxxSendMessageTimeout+0x1a6 (FPO: [Non-Fpo])
f33cacdc bf81eee5 bbe6a528 0000000f 00000000 win32k!xxxSendMessage+0x1b (FPO: [Non-Fpo])
f33cad08 bf81edb5 bbe6a528 00000001 0013e124 win32k!xxxUpdateWindow2+0x79 (FPO: [Non-Fpo])
f33cad28 bf8319f6 bbe6a528 00000001 f33cad54 win32k!xxxInternalUpdateWindow+0x6f (FPO: [Non-Fpo])
f33cad38 bf831a4d bbe6a528 0013e124 00000000 win32k!xxxUpdateWindow+0xf (FPO: [Non-Fpo])
f33cad54 804df06b 00050218 0000005e 0013e124 win32k!NtUserCallHwndLock+0x4b (FPO: [Non-Fpo])
f33cad54 7c90eb94 00050218 0000005e 0013e124 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f33cad64)
0013e0e8 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806eb780 nt ntoskrnl.exe Wed Aug 04 02:19:48 2004 (41108004)
806ec000 8070c380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
bf000000 bf011580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf012000 bf425a80 nv4_disp nv4_disp.dll Wed Aug 04 03:57:11 2004 (411096D7)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 02:17:30 2004 (41107F7A)
ee262000 ee28bf00 kmixer kmixer.sys Wed Aug 04 02:07:46 2004 (41107D32)
f321a000 f325a100 HTTP HTTP.sys Fri Oct 08 19:48:20 2004 (41672744)
f3463000 f34b5180 srv srv.sys Wed Aug 04 02:14:44 2004 (41107ED4)
f3506000 f3532400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
f373a000 f374e400 wdmaud wdmaud.sys Wed Aug 04 02:15:03 2004 (41107EE7)
f389f000 f38add80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
f3a93000 f3a96280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
f3c87000 f3c9e480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f3cc7000 f3ce7f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f3ce8000 f3d56400 mrxsmb mrxsmb.sys Tue Jan 18 23:26:50 2005 (41EDE18A)
f3d57000 f3d81a00 rdbss rdbss.sys Wed Oct 27 21:13:57 2004 (418047D5)
f3d82000 f3da3d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f3da4000 f3dcbc00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f3dcc000 f3e23a80 tcpip tcpip.sys Wed Aug 04 02:14:39 2004 (41107ECF)
f3e24000 f3e36400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f3e7f000 f3eb1a00 Dot4 Dot4.sys Wed Aug 04 01:58:28 2004 (41107B04)
f6f66000 f6f68900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f6f7a000 f6fad200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f6fae000 f6fde100 rdpdr rdpdr.sys Wed Aug 04 02:01:10 2004 (41107BA6)
f6fdf000 f6fefe00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f6ff0000 f7006680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f7007000 f701a900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f701b000 f702e780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f702f000 f71fe3c0 nv4_mini nv4_mini.sys Wed Apr 07 22:30:48 2004 (4074B958)
f71ff000 f7221680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7222000 f7245980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f7246000 f730d100 cmuda cmuda.sys Mon Feb 23 20:28:12 2004 (403AA8AC)
f730e000 f7330e80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f7655000 f766f580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7670000 f769ca80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f769d000 f7729480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f772a000 f7740780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f7741000 f7752f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f7753000 f7771780 fltmgr fltmgr.sys Wed Aug 04 02:01:17 2004 (41107BAD)
f7772000 f7789480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f778a000 f77af700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
f77b0000 f77ce880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f77cf000 f77dfa80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f77e0000 f780dd80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f782f000 f7837c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f783f000 f7849500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f784f000 f785bc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f785f000 f7867e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f786f000 f787b200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f78ef000 f78f8200 amdk7 amdk7.sys Wed Aug 04 01:59:19 2004 (41107B37)
f78ff000 f790db80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f790f000 f791b180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f791f000 f792d080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f792f000 f7939380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f793f000 f794ed80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f794f000 f795be00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f795f000 f796b880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f796f000 f7979200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f797f000 f798ad00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f798f000 f7997900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f799f000 f79a8f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f79af000 f79bd100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f79bf000 f79c8480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f79ef000 f79f7700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7a0f000 f7a17880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f7a1f000 f7a27700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f7a3f000 f7a4e900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f7a4f000 f7a57d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f7aaf000 f7ab5200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f7ab7000 f7abb900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7b07000 f7b0b280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7b0f000 f7b15800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7b1f000 f7b24200 RTL8139 RTL8139.SYS Fri Jun 13 01:29:46 2003 (3EE9614A)
f7b27000 f7b28000 fdc fdc.sys unavailable (00000000)
f7b2f000 f7b34a00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7b37000 f7b3b880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7b3f000 f7b43580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7b47000 f7b4b080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7b4f000 f7b55000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7b5f000 f7b64000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7b6f000 f7b75180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f7b77000 f7b7c200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f7b7f000 f7b83a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f7b87000 f7b8e880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f7b97000 f7b9eb80 usbccgp usbccgp.sys Wed Aug 04 02:08:45 2004 (41107D6D)
f7b9f000 f7ba3500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f7c3f000 f7c42000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7cb7000 f7cb9580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f7cbb000 f7cbea00 kbdhid kbdhid.sys Wed Aug 04 01:58:33 2004 (41107B09)
f7ccb000 f7ccec80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f7ccf000 f7cd1980 gameenum gameenum.sys Wed Aug 04 02:08:20 2004 (41107D54)
f7cd3000 f7cd5580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7cef000 f7cf2c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7d1b000 f7d1e280 Dot4Prt Dot4Prt.sys Fri Aug 17 16:47:25 2001 (3B7D82DD)
f7d2b000 f7d2d280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f7d2f000 f7d30b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7d31000 f7d32100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7d33000 f7d34700 dmload dmload.sys Fri Aug 17 16:58:15 2001 (3B7D8567)
f7d3b000 f7d3c100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7d3d000 f7d3e280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7d43000 f7d44f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7d45000 f7d46080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7d47000 f7d48080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7d49000 f7d4a080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7d4b000 f7d4c100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7da3000 f7da4a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
f7df7000 f7df7d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7e3f000 f7e3fa00 winio winio.sys Fri Mar 01 16:20:59 2002 (3C7FF0BB)
f7e67000 f7e67d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f7f52000 f7f52b80 msmpu401 msmpu401.sys Fri Aug 17 16:59:59 2001 (3B7D85CF)
f7f53000 f7f53c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f7f84000 f7f84b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)

Unloaded modules:
ee262000 ee28c000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3038000 f3062000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7e28000 f7e29000 winio.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f36ed000 f3717000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3717000 f373a000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7eaa000 f7eab000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f385f000 f386c000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f386f000 f387d000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d71000 f7d73000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79ff000 f7a08000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d27000 f7d2b000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b67000 f7b6c000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d23000 f7d26000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

This could be the result of a video card driver malfunction. Has it happened more than once? Make sure you are running the latest drivers. If it happens again, post it up.

 

Joe - it's the machine from This thread (with dumps) but after the user replaced 2K with XP.

 

I upgraded to the latest driver (a beta from NVIDIA) but it has restarted twice today (Thursday), at intervals of several hours. Wish I had looked at the time. On the second one I had some idea what was about to happen some half a second before it did, though I don't remember what tipped me off. I think something internal stopped functioning, like the fan. The video card is built into the motherboard, which is one of the parts I recently installed. (A Chaintech Summit 7NJL_)

Am still having trouble locating dump files in XP- where should I look for evidence of what's causing the restarts?

My monitor is a rather old Optiquest- could that have something to do with it? We're talking... possibly as old as 6years, more likely 4yr old CRT. (I'm resisting flat screens because I do a lot of graphic work and remain unimpressed with the quality.)

 

On the second one I had some idea what was about to happen some half a second before it did, though I don't remember what tipped me off. I think something internal stopped functioning, like the fan.
Software doesnt make fans spin or not. That would generally be a symptom of a hardware problem. BTW,The monitor shouldnt have anything to do with it.

Am still having trouble locating dump files in XP- where should I look for evidence of what's causing the restarts?
Out of the box, you should be getting a minidump in c:\windows\minidump. Look for a file with the date/time that matches the time it crashed, or just search your drives for *.DMP.

 

Most recent minidump (from latest crash)

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini040105-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: 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
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Fri Apr 1 12:42:43.109 2005 (GMT-5)
System Uptime: 0 days 0:28:46.688
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
...........
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {c536de3b, 0, bf80f7fb, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!PFEOBJ::bEmbPvtOk+8 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: c536de3b, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf80f7fb, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: c536de3b

FAULTING_IP:
win32k!PFEOBJ::bEmbPvtOk+8
bf80f7fb 8b00 mov eax,[eax]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from bf811377 to bf80f7fb

STACK_TEXT:
f3575750 bf811377 f35757e4 0013e234 bf80ff05 win32k!PFEOBJ::bEmbPvtOk+0x8
f35757a0 bf80feae f35757e0 f35757c4 f35757bc win32k!LFONTOBJ:pfeMapFont+0x19f
f35757d8 804df06b e18c39c8 0013e238 7c90eb94 win32k!GreGetCharSet+0xa9
f35757d8 7c90eb94 e18c39c8 0013e238 7c90eb94 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013e224 00000000 00000000 00000000 00000000 0x7c90eb94
f3575aa0 80566730 f3575b5c f3575b60 f3575b30 nt!KiCallUserMode+0x4
f3575afc bf813d09 00000002 f3575b40 00000018 nt!KeUserModeCallback+0x87
f3575b80 bf813ea0 bbe89c48 0000000f 00000000 win32k!SfnDWORD+0xa8
f3575bc8 bf814092 40e89c48 0000000f 00000000 win32k!xxxSendMessageToClient+0x176
f3575c14 bf80f470 bbe89c48 0000000f 00000000 win32k!xxxSendMessageTimeout+0x1a6
f3575c38 bf81eee5 bbe89c48 0000000f 00000000 win32k!xxxSendMessage+0x1b
f3575c64 bf81edb5 bbe89c48 00000001 01040044 win32k!xxxUpdateWindow2+0x79
f3575c84 bf8154d3 bbe89c48 00000001 00000000 win32k!xxxInternalUpdateWindow+0x6f
f3575cc8 bf815359 bbe89c48 00000001 00001101 win32k!xxxInternalInvalidate+0x148
f3575cf4 bf81ed2b bbe89c48 00000000 00000000 win32k!xxxRedrawWindow+0x103
f3575d4c 804df06b 000203fc 00000000 00000000 win32k!NtUserRedrawWindow+0xac
f3575d4c 7c90eb94 000203fc 00000000 00000000 nt!KiFastCallEntry+0xf8
0013e9b8 00000000 00000000 00000000 00000000 0x7c90eb94


FOLLOWUP_IP:
win32k!PFEOBJ::bEmbPvtOk+8
bf80f7fb 8b00 mov eax,[eax]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!PFEOBJ::bEmbPvtOk+8

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107f7a

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0x50_win32k!PFEOBJ::bEmbPvtOk+8

BUCKET_ID: 0x50_win32k!PFEOBJ::bEmbPvtOk+8

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

eax=c536de3b ebx=f35757d4 ecx=f3575774 edx=85b8a8dc esi=00000000 edi=e18c3ab0
eip=bf80f7fb esp=f357574c ebp=f3575750 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
win32k!PFEOBJ::bEmbPvtOk+0x8:
bf80f7fb 8b00 mov eax,[eax] ds:0023:c536de3b=????????
ChildEBP RetAddr Args to Child
f3575750 bf811377 f35757e4 0013e234 bf80ff05 win32k!PFEOBJ::bEmbPvtOk+0x8 (FPO: [Non-Fpo])
f35757a0 bf80feae f35757e0 f35757c4 f35757bc win32k!LFONTOBJ:pfeMapFont+0x19f (FPO: [Non-Fpo])
f35757d8 804df06b e18c39c8 0013e238 7c90eb94 win32k!GreGetCharSet+0xa9 (FPO: [Non-Fpo])
f35757d8 7c90eb94 e18c39c8 0013e238 7c90eb94 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f35757e4)
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013e224 00000000 00000000 00000000 00000000 0x7c90eb94
f3575aa0 80566730 f3575b5c f3575b60 f3575b30 nt!KiCallUserMode+0x4 (FPO: [2,3,4])
f3575afc bf813d09 00000002 f3575b40 00000018 nt!KeUserModeCallback+0x87 (FPO: [Non-Fpo])
f3575b80 bf813ea0 bbe89c48 0000000f 00000000 win32k!SfnDWORD+0xa8 (FPO: [Non-Fpo])
f3575bc8 bf814092 40e89c48 0000000f 00000000 win32k!xxxSendMessageToClient+0x176 (FPO: [Non-Fpo])
f3575c14 bf80f470 bbe89c48 0000000f 00000000 win32k!xxxSendMessageTimeout+0x1a6 (FPO: [Non-Fpo])
f3575c38 bf81eee5 bbe89c48 0000000f 00000000 win32k!xxxSendMessage+0x1b (FPO: [Non-Fpo])
f3575c64 bf81edb5 bbe89c48 00000001 01040044 win32k!xxxUpdateWindow2+0x79 (FPO: [Non-Fpo])
f3575c84 bf8154d3 bbe89c48 00000001 00000000 win32k!xxxInternalUpdateWindow+0x6f (FPO: [Non-Fpo])
f3575cc8 bf815359 bbe89c48 00000001 00001101 win32k!xxxInternalInvalidate+0x148 (FPO: [Non-Fpo])
f3575cf4 bf81ed2b bbe89c48 00000000 00000000 win32k!xxxRedrawWindow+0x103 (FPO: [Non-Fpo])
f3575d4c 804df06b 000203fc 00000000 00000000 win32k!NtUserRedrawWindow+0xac (FPO: [Non-Fpo])
f3575d4c 7c90eb94 000203fc 00000000 00000000 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f3575d64)
0013e9b8 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806eb780 nt ntoskrnl.exe Wed Aug 04 02:19:48 2004 (41108004)
806ec000 8070c380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
bf000000 bf011580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf012000 bf3dc300 nv4_disp nv4_disp.dll Thu Feb 24 11:08:56 2005 (421DFC18)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 02:17:30 2004 (41107F7A)
f275b000 f2784f00 kmixer kmixer.sys Wed Aug 04 02:07:46 2004 (41107D32)
f3242000 f3282100 HTTP HTTP.sys Fri Oct 08 19:48:20 2004 (41672744)
f34b3000 f3505180 srv srv.sys Wed Aug 04 02:14:44 2004 (41107ED4)
f370e000 f373a400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
f39e2000 f39f6400 wdmaud wdmaud.sys Wed Aug 04 02:15:03 2004 (41107EE7)
f3bef000 f3bfdd80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
f3c53000 f3c56280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
f3de7000 f3dfe480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f3e27000 f3e47f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f3e48000 f3eb6400 mrxsmb mrxsmb.sys Tue Jan 18 23:26:50 2005 (41EDE18A)
f3eb7000 f3ee1a00 rdbss rdbss.sys Wed Oct 27 21:13:57 2004 (418047D5)
f3ee2000 f3f03d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f3f04000 f3f2bc00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f3f2c000 f3f83a80 tcpip tcpip.sys Wed Aug 04 02:14:39 2004 (41107ECF)
f3f84000 f3f96400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f3fb7000 f3fe9a00 Dot4 Dot4.sys Wed Aug 04 01:58:28 2004 (41107B04)
f70b2000 f70e5200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f710e000 f713e100 rdpdr rdpdr.sys Wed Aug 04 02:01:10 2004 (41107BA6)
f713f000 f714fe00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f7150000 f7166680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f7167000 f717a900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f717b000 f718e780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f718f000 f74da4c0 nv4_mini nv4_mini.sys Thu Feb 24 11:13:44 2005 (421DFD38)
f74db000 f74fd680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f74fe000 f7521980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f7522000 f75e9100 cmuda cmuda.sys Mon Feb 23 20:28:12 2004 (403AA8AC)
f75ea000 f760ce80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f7625000 f7627280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f7655000 f766f580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7670000 f769ca80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f769d000 f7729480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f772a000 f7740780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f7741000 f7752f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f7753000 f7771780 fltmgr fltmgr.sys Wed Aug 04 02:01:17 2004 (41107BAD)
f7772000 f7789480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f778a000 f77af700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
f77b0000 f77ce880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f77cf000 f77dfa80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f77e0000 f780dd80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f782f000 f7837c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f783f000 f7849500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f784f000 f785bc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f785f000 f7867e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f786f000 f787b200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f78cf000 f78de900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f792f000 f7938200 amdk7 amdk7.sys Wed Aug 04 01:59:19 2004 (41107B37)
f793f000 f794db80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f794f000 f795b180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f795f000 f796d080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f796f000 f7979380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f797f000 f798ed80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f798f000 f799be00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f799f000 f79ab880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f79af000 f79b9200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f79bf000 f79cad00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f79cf000 f79d7900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f79df000 f79e8f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f79ef000 f79fd100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f79ff000 f7a08480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f7a1f000 f7a27700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7a3f000 f7a47880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f7a4f000 f7a57700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f7a6f000 f7a77d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f7aaf000 f7ab5200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f7ab7000 f7abb900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7ae7000 f7aeb500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f7af7000 f7afb280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7aff000 f7b05800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7b07000 f7b0c200 RTL8139 RTL8139.SYS Fri Jun 13 01:29:46 2003 (3EE9614A)
f7b0f000 f7b16000 GEARAspiWDM GEARAspiWDM.sys Tue Sep 14 10:58:38 2004 (4147071E)
f7b17000 f7b18000 fdc fdc.sys unavailable (00000000)
f7b1f000 f7b24a00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7b27000 f7b2b880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7b2f000 f7b33580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7b37000 f7b3b080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7b3f000 f7b45000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7b47000 f7b4c000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7b57000 f7b5d180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f7b5f000 f7b64200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f7b67000 f7b6ba80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f7b6f000 f7b76880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f7b77000 f7b7eb80 usbccgp usbccgp.sys Wed Aug 04 02:08:45 2004 (41107D6D)
f7c3f000 f7c42000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7cc7000 f7cc9580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f7ccb000 f7ccea00 kbdhid kbdhid.sys Wed Aug 04 01:58:33 2004 (41107B09)
f7ccf000 f7cd1900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f7cdb000 f7cdec80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f7cdf000 f7ce1980 gameenum gameenum.sys Wed Aug 04 02:08:20 2004 (41107D54)
f7ce3000 f7ce5580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7d03000 f7d06c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7d2b000 f7d2e280 Dot4Prt Dot4Prt.sys Fri Aug 17 16:47:25 2001 (3B7D82DD)
f7d2f000 f7d30b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7d31000 f7d32100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7d33000 f7d34700 dmload dmload.sys Fri Aug 17 16:58:15 2001 (3B7D8567)
f7d3b000 f7d3c100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7d3d000 f7d3e280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7d3f000 f7d40f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7d41000 f7d42080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7d43000 f7d44080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7d45000 f7d46080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7d63000 f7d64a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
f7d9f000 f7da0100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7df7000 f7df7d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7ea7000 f7ea7d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f7efd000 f7efdb80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
f7f07000 f7f07b80 msmpu401 msmpu401.sys Fri Aug 17 16:59:59 2001 (3B7D85CF)
f7f08000 f7f08c00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)

Unloaded modules:
f3088000 f30b2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f38f5000 f391f000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7f5e000 f7f5f000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3ac7000 f3ad4000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3ad7000 f3ae5000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f391f000 f3942000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7df3000 f7df5000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7a2f000 f7a38000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7629000 f762d000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b4f000 f7b54000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f762d000 f7630000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Ok, now we have a better picture of what happened. There are a few possible causes.

The machine crashed while manipulating graphics, specifically a font, either for a print job, or a WYSIWYG program.

a) bad font - you may have installed an application that brought along a custom font that is not a happy font. If the dump was a full dump, rather than a minidump, I could give you some commands to run in the debugger to extract the name of the font being manipulated.

b) bad printer driver - The graphics subsystem works closely with your default printer, and your video card. If either of these components returned or sent bad data, you could get into this state. (what kind of printer do you have, and where did you obtain the drivers, make sure they are latest availible, or switch fromt he OEM website to the windows update versions).

c) bad memory - this is unlikely, since both crashes are in the same place for the same reason, but with a small sample of data, i cannot completely rule this out.

My gut feeling is its probably A, but possibly B. Reconfigure for a FULL MEMORY dump in the Startup and recovery option of My computer->properties. Collect a new dump, post it to confirm we have what we think we have, and then we get to go spelunking for Font names.

(note i'm not around over the weekend).

 

I've enabled full dumps, but now I can't stimulate a crash!! It's early morning and I'm going to leave it running into the wee hours if I have to to get it generate a complete dump.

Irony.

I'm running two printers at the moment:
1. A 16-yr-old HP Laserjet (Never throw those away- they last FOREVER.) via our LAN that the system recognized right away and hasn't had an obvious problem with.
2. An HP Officejet T45 (All-in-one). I had trouble installing this, as I couldn't put my hand on the disk, and downloaded drivers from HP. Windows kept trying to install it several times over and then kept insisting that new hardware was found (until I launched the driver, it hadn't picked up the printer at all). From the looks of the board, this is a pretty common problem.

Memory IS a possibility, as it's one of the things I recently installed.

 

Those multi-function printers are basically evil. I have fought the drivers for those things since the days in win98. If there comes a point when we have to guess the problem, that printer is getting thrown in a lake.

If you are trying to induce the problem, your best bet is to stress graphics and fonts. Have you tried going into control panel->fonts. Highlite 15 or 20 at a time, hit enter, let the windows open, then using the grouping feature in XP, 'close group' fromt he task bar, and move on to the next 15. Open some of the documents you looked at last week, use print preview.. etc..

 

It FINALLY crashed again today, prompted by an elaborate flash website. (DonnieDarko.com) It went to blue memory dump twice in succession, citing first nv4_disp (an NVIDIA file?) and then win32k.sys as causing the errors.

I did try opening multiple font files at once, but never got even the slightest error. I even got all 90-something files to open at once, and close without problem. Very odd.

All-in-one printers are absolute hazards. But, this one has held up pretty well, considering that it didn't come with a Win2k driver and I've been making it work on only Win2k systems since we got it. I'd be sad to have to unplug it- I use it quite a bit.

And now, the uber dump:

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini040905-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: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sat Apr 9 00:05:48.125 2005 (GMT-4)
System Uptime: 0 days 9:28:59.708
Loading Kernel Symbols
....................................................................................................................
Loading unloaded module list
.......................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {85eb90f8, 86520740, f7c56cb4, 1}

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
Probably caused by : watchdog.sys ( watchdog!WatchdogKernelApc+13b )

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

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 85eb90f8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 86520740, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7c56cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: mssmbios!SMBIOS_DATA_OBJECT ***
*** ***
*************************************************************************

FAULTING_THREAD: 85eb90f8

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

LAST_CONTROL_TRANSFER: from 804e3f4e to 804dbd78

STACK_TEXT:
f3216234 804e3f4e f7c56b40 f7c56b70 00000000 nt!KiUnlockDispatcherDatabase+0x77
f3216248 f275ba67 f7c56b94 00000000 00000000 nt!KeSetEvent+0x74
f321653c 804ed15a f7c56b40 f3216588 f321657c watchdog!WatchdogKernelApc+0x13b
f321658c 804dbda9 00000000 00000000 00000000 nt!KiDeliverApc+0xb3
f32165ac 804ea3a4 85eb92c0 85eb90f8 8055a540 nt!KiUnlockDispatcherDatabase+0xa8
f32165c4 805ded3c 866b83c8 00000001 00000001 nt!KeReleaseSemaphore+0x70
f32165f8 80621ec3 e1687960 866b83c8 f321662c nt!LpcpRequestWaitReplyPort+0x3ff
f3216610 80659974 e1687960 f32167a4 f321662c nt!LpcRequestWaitReplyPortEx+0x21
f321678c 8060fec7 f32167a4 e1687960 00000000 nt!DbgkpSendApiMessageLpc+0x49
f321681c 8051de84 f3216bf8 00000000 00000001 nt!DbgkForwardException+0x84
f3216bdc 804dfada f3216bf8 00000000 f3216c4c nt!KiDispatchException+0x38f
f3216c44 804dfa86 f3216cf0 804dfa41 badb0d00 nt!CommonDispatchException+0x4d
f3216cf0 bf804035 80000002 00000340 00000000 nt!Kei386EoiHelper+0x18a
f3216d30 bf803c96 bbebdf00 00000000 00010002 win32k!_GetDCEx+0x4d7
f3216d44 bf8044ab bbebdf00 f3216d64 0012f5f8 win32k!_GetDC+0x35
f3216d58 804df06b 00200220 0012f62c 7c90eb94 win32k!NtUserGetDC+0x6d
f3216d58 7c90eb94 00200220 0012f62c 7c90eb94 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f5e8 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: .thread ffffffff85eb90f8 ; kb

FOLLOWUP_IP:
watchdog!WatchdogKernelApc+13b
f275ba67 8b4dfc mov ecx,[ebp-0x4]

SYMBOL_STACK_INDEX: 2

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: watchdog!WatchdogKernelApc+13b

MODULE_NAME: watchdog

IMAGE_NAME: watchdog.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d24

FAILURE_BUCKET_ID: 0xEA_watchdog!WatchdogKernelApc+13b

BUCKET_ID: 0xEA_watchdog!WatchdogKernelApc+13b

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

 

eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=804dbd78 esp=f3216228 ebp=f3216248 iopl=0 nv up di pl nz na pe nc
cs=0008 ss=0010 ds=0000 es=0000 fs=0000 gs=0000 efl=00000000
nt!KiUnlockDispatcherDatabase+0x77:
804dbd78 0ac0 or al,al
ChildEBP RetAddr Args to Child
f3216234 804e3f4e f7c56b40 f7c56b70 00000000 nt!KiUnlockDispatcherDatabase+0x77 (FPO: [EBP 0xf3216248] [0,0,4])
f3216248 f275ba67 f7c56b94 00000000 00000000 nt!KeSetEvent+0x74 (FPO: [Non-Fpo])
f321653c 804ed15a f7c56b40 f3216588 f321657c watchdog!WatchdogKernelApc+0x13b (FPO: [Non-Fpo])
f321658c 804dbda9 00000000 00000000 00000000 nt!KiDeliverApc+0xb3 (FPO: [Non-Fpo])
f32165ac 804ea3a4 85eb92c0 85eb90f8 8055a540 nt!KiUnlockDispatcherDatabase+0xa8 (FPO: [EBP 0xf32165c4] [0,0,4])
f32165c4 805ded3c 866b83c8 00000001 00000001 nt!KeReleaseSemaphore+0x70 (FPO: [Non-Fpo])
f32165f8 80621ec3 e1687960 866b83c8 f321662c nt!LpcpRequestWaitReplyPort+0x3ff (FPO: [Non-Fpo])
f3216610 80659974 e1687960 f32167a4 f321662c nt!LpcRequestWaitReplyPortEx+0x21 (FPO: [Non-Fpo])
f321678c 8060fec7 f32167a4 e1687960 00000000 nt!DbgkpSendApiMessageLpc+0x49 (FPO: [Non-Fpo])
f321681c 8051de84 f3216bf8 00000000 00000001 nt!DbgkForwardException+0x84 (FPO: [Non-Fpo])
f3216bdc 804dfada f3216bf8 00000000 f3216c4c nt!KiDispatchException+0x38f (FPO: [Non-Fpo])
f3216c44 804dfa86 f3216cf0 804dfa41 badb0d00 nt!CommonDispatchException+0x4d (FPO: [0,20,0])
f3216cf0 bf804035 80000002 00000340 00000000 nt!Kei386EoiHelper+0x18a
f3216d30 bf803c96 bbebdf00 00000000 00010002 win32k!_GetDCEx+0x4d7 (FPO: [Non-Fpo])
f3216d44 bf8044ab bbebdf00 f3216d64 0012f5f8 win32k!_GetDC+0x35 (FPO: [Non-Fpo])
f3216d58 804df06b 00200220 0012f62c 7c90eb94 win32k!NtUserGetDC+0x6d (FPO: [Non-Fpo])
f3216d58 7c90eb94 00200220 0012f62c 7c90eb94 nt!KiFastCallEntry+0xf8 (FPO: [0,0] TrapFrame @ f3216d64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012f5e8 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806eb780 nt ntoskrnl.exe Wed Aug 04 02:19:48 2004 (41108004)
806ec000 8070c380 hal halaacpi.dll Wed Aug 04 01:59:05 2004 (41107B29)
bf000000 bf011580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf012000 bf3dc300 nv4_disp nv4_disp.dll Thu Feb 24 11:08:56 2005 (421DFC18)
bf800000 bf9c0380 win32k win32k.sys Wed Aug 04 02:17:30 2004 (41107F7A)
f05eb000 f0614f00 kmixer kmixer.sys Wed Aug 04 02:07:46 2004 (41107D32)
f1907000 f1947100 HTTP HTTP.sys Fri Oct 08 19:48:20 2004 (41672744)
f1d58000 f1daa180 srv srv.sys Wed Aug 04 02:14:44 2004 (41107ED4)
f1dfb000 f1e27400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
f2007000 f201b400 wdmaud wdmaud.sys Wed Aug 04 02:15:03 2004 (41107EE7)
f21dc000 f21f3480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f21f4000 f2217000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
f275b000 f275f500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f27c2000 f27c5280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
f27ce000 f27d0900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f2898000 f289e780 USBSTOR USBSTOR.SYS Wed Aug 04 02:08:44 2004 (41107D6C)
f28f1000 f2900900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f2bcd000 f2bd5d80 HIDCLASS HIDCLASS.SYS Wed Aug 04 02:08:18 2004 (41107D52)
f2c26000 f2c2c6c0 secdrv secdrv.sys Fri Feb 09 11:51:30 2001 (3A842012)
f2f42000 f2f62f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
f2f74000 f2fe2400 mrxsmb mrxsmb.sys Tue Jan 18 23:26:50 2005 (41EDE18A)
f2fe7000 f2fe9f80 mouhid mouhid.sys Fri Aug 17 16:47:57 2001 (3B7D82FD)
f2ff3000 f2ff6a00 kbdhid kbdhid.sys Wed Aug 04 01:58:33 2004 (41107B09)
f2fff000 f3001580 hidusb hidusb.sys Fri Aug 17 17:02:16 2001 (3B7D8658)
f300b000 f3035a00 rdbss rdbss.sys Wed Oct 27 21:13:57 2004 (418047D5)
f3036000 f3057d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
f3058000 f307fc00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f308a000 f30e1a80 tcpip tcpip.sys Wed Aug 04 02:14:39 2004 (41107ECF)
f30e2000 f30f4400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f312d000 f3134b80 usbccgp usbccgp.sys Wed Aug 04 02:08:45 2004 (41107D6D)
f3165000 f3197a00 Dot4 Dot4.sys Wed Aug 04 01:58:28 2004 (41107B04)
f3227000 f3235d80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
f670b000 f6713700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f671b000 f6723880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f673b000 f6743700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f681f000 f6826880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f6827000 f682ba80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f682f000 f6834200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f6837000 f683d180 HIDPARSE HIDPARSE.SYS Wed Aug 04 02:08:15 2004 (41107D4F)
f6c96000 f6c96b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
f6e20000 f6e53200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f6e60000 f6e62280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f6e70000 f6e73280 Dot4Prt Dot4Prt.sys Fri Aug 17 16:47:25 2001 (3B7D82DD)
f6e7c000 f6eac100 rdpdr rdpdr.sys Wed Aug 04 02:01:10 2004 (41107BA6)
f6f7f000 f6f8fe00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f6f90000 f6fa6680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f6fa7000 f6fba900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f6fbb000 f6fce780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f6fcf000 f731a4c0 nv4_mini nv4_mini.sys Thu Feb 24 11:13:44 2005 (421DFD38)
f731b000 f733d680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f733e000 f7361980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f7362000 f7429100 cmuda cmuda.sys Mon Feb 23 20:28:12 2004 (403AA8AC)
f742a000 f744ce80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f7625000 f7628c80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7655000 f766f580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f7670000 f769ca80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f769d000 f7729480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f772a000 f7740780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f7741000 f7752f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f7753000 f7771780 fltmgr fltmgr.sys Wed Aug 04 02:01:17 2004 (41107BAD)
f7772000 f7789480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f778a000 f77af700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
f77b0000 f77ce880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f77cf000 f77dfa80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f77e0000 f780dd80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f782f000 f7837c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f783f000 f7849500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f784f000 f785bc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f785f000 f7867e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f786f000 f787b200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f789f000 f78a7900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f78bf000 f78c8f00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f78df000 f78ed100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f78ef000 f78f8480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f7a0f000 f7a18200 amdk7 amdk7.sys Wed Aug 04 01:59:19 2004 (41107B37)
f7a1f000 f7a2db80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f7a2f000 f7a3b180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f7a3f000 f7a4d080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f7a4f000 f7a59380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f7a5f000 f7a6ed80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f7a6f000 f7a7be00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f7a7f000 f7a8b880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f7a8f000 f7a99200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f7a9f000 f7aaad00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f7aaf000 f7ab5200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f7ab7000 f7abb900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f7b8f000 f7b94000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7bbf000 f7bc3280 usbohci usbohci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7bc7000 f7bcd800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7bcf000 f7bd4200 RTL8139 RTL8139.SYS Fri Jun 13 01:29:46 2003 (3EE9614A)
f7bd7000 f7bde000 GEARAspiWDM GEARAspiWDM.sys Tue Sep 14 10:58:38 2004 (4147071E)
f7bdf000 f7be5b00 fdc fdc.sys Wed Aug 04 01:59:25 2004 (41107B3D)
f7be7000 f7beca00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7bef000 f7bf3880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7bf7000 f7bfb580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7bff000 f7c03080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7c07000 f7c0d000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7c3f000 f7c42000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7d13000 f7d16c80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f7d17000 f7d19980 gameenum gameenum.sys Wed Aug 04 02:08:20 2004 (41107D54)
f7d1b000 f7d1d580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7d2f000 f7d30b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7d31000 f7d32100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7d33000 f7d34700 dmload dmload.sys Fri Aug 17 16:58:15 2001 (3B7D8567)
f7d35000 f7d36da0 PenClass PenClass.sys Mon Apr 09 17:44:59 2001 (3AD22D5B)
f7d67000 f7d68100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7d69000 f7d6a280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7d9b000 f7d9cf00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7d9d000 f7d9e080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7d9f000 f7da0080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7da1000 f7da2080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7db7000 f7db8a80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
f7de7000 f7de8100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7df7000 f7df7d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7e5e000 f7e5eb80 msmpu401 msmpu401.sys Fri Aug 17 16:59:59 2001 (3B7D85CF)
f7e5f000 f7e5fc00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f7ea2000 f7ea2d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)

Unloaded modules:
f05eb000 f0615000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f05eb000 f0615000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f05eb000 f0615000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f05eb000 f0615000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f05eb000 f0615000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f0e78000 f0ea2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f0e78000 f0ea2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f0e78000 f0ea2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f0e78000 f0ea2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f0e78000 f0ea2000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f16db000 f1705000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f16db000 f1705000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f16db000 f1705000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f1fba000 f1fe4000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7eee000 f7eef000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f31f7000 f3204000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f1fe4000 f2007000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f3207000 f3215000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d83000 f7d85000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f672b000 f6734000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6e64000 f6e68000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7aff000 f7b04000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f6e68000 f6e6b000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

This dump is pretty different than the last one. You can ignore all that watchdog nonsense. This is a busted Win32k DC. Put the two dumps together, and youve got bad ram, or pool corruption.

You can turn on special pool, or fool around with your memory sticks trying to eliminate a potential bad stick. The frequency of the phenomenon would mean that your gonna be running for a while.

Please note that this can put you into a nasty reboot loop, that safe mode may or may not fix. Do not follow these directions unless you are prepared for the worst.

Note that special pool can cause it to crash on boot. If you are not comfortable using safemode and the recovery console, you can get yourself into a pickle.
------------------------------------------------
You will need to enable "special pool" and get another crash dump. When it crashes with special pool enabled, you should see the bad driver right on the stack.

Using the registry to enable special pool <---recommended proceedure using *
http://support.microsoft.com/kb/188831/EN-US/

Turn this on, get a new dump.

Things to consider before you enable Driver Verifier Manager on production servers
http://support.microsoft.com/kb/251233/EN-US/

Note that this will increase the frequency of the crashes

 

did you give up?

 

No, all signs seem to point to the memory, so I'm using process of elimination to see which one is buggy. I'm running on one stick at a time and waiting for errors. More fun.

If I don't get errors from either stick, I'll try your options- scary as they are. I have my teched-up father around to help make sure I don't blow anything up.

...and so we wait... again...

 

very well. Let us know how it turns out.