Constant BSOD errors (dump data)

Hey guys,

For the past couple months, I've been repeatedly been getting stop errors on my computer. They started when I installed the MMORPG World of Warcraft, and have continued since. Many have suggested updating drivers, which I did with no luck. I even bought and installed a new video card for my computer which definitely helped, but did not completely fix the problem. Most of the errors are DRIVER_IRQL_NOT_LESS_OR_EQUAL, and very rarely list a file that might be causing the problem. More recently I got an irql error that listed the usbport.sys underneath STOP: 0x000000D1. I also got a bad_pool_header error. I usually only get these errors after playing WoW for at least 30 minutes, sometimes after just loading a character, and occasionally at other times random too. If anyone has any help, I would be incredibly grateful. Here are some of my system specs:

---

Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2
System Manufacturer: Dell Inc.
System Model: Dell DV051
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz (2 CPUs)
Memory: 1014MB RAM
Page File: 643MB used, 1797MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)

Card name: VisionTek Radeon X1550 Series
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Driver Version: 6.14.0010.6755 (English)
DDI Version: 9 (or higher)

---

If this is insufficient information, please let me know what else you need. I also have a zip folder of all my minidumps from when this problem started, and if you would like those just tell me. Thanks in advance.

 

Hi, Mzh. Welcome to Windows BBS!

Thank you for your very detailed hardware configuration!

Please carefully follow the instructions in this link and paste THREE of your most recent BSOD dump logs in this thread.

We'll look at those logs to determine whether we can find a pattern (or lack of a pattern).

 

thanks

Hey there, thanks so much for replying,

I followed those instructions and the debuglog seemed so incredibly long, so I'm only posting the first one now. That way if its wrong I didn't waste too much board space. This is my most recent dump file

-----

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini011408-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) 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: Mon Jan 14 16:20:58.031 2008 (GMT-8)
System Uptime: 0 days 1:02:13.935
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {4, 1c, 1, 80501912}



Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+88 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80501912, address which referenced memory

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




WRITE_ADDRESS: 00000004

CURRENT_IRQL: 1c

FAULTING_IP:
nt!KiTimerExpiration+88
80501912 895f04 mov dword ptr [edi+4],ebx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: Steam.exe

LAST_CONTROL_TRANSFER: from 805451ff to 80501912

STACK_TEXT:
f7a1dfcc 805451ff 8055b4a0 00000000 0003a57b nt!KiTimerExpiration+0x88
f7a1dff4 80544d6b acbdbf18 00000000 00000000 nt!KiRetireDpcList+0x61
f7a1dff8 acbdbf18 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
WARNING: Frame IP not in any known module. Following frames may be wrong.
80544d6b 00000000 00000009 0081850f bb830000 0xacbdbf18


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTimerExpiration+88
80501912 895f04 mov dword ptr [edi+4],ebx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiTimerExpiration+88

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

FAILURE_BUCKET_ID: 0xA_W_nt!KiTimerExpiration+88

BUCKET_ID: 0xA_W_nt!KiTimerExpiration+88

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

eax=8055bb38 ebx=8055bb38 ecx=85ce5c80 edx=000000ff esi=0000007b edi=00000000
eip=80501912 esp=f7a1dfa8 ebp=f7a1dfcc iopl=0 nv up ei ng nz ac po cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
nt!KiTimerExpiration+0x88:
80501912 895f04 mov dword ptr [edi+4],ebx ds:0023:00000004=????????
ChildEBP RetAddr Args to Child
f7a1dfcc 805451ff 8055b4a0 00000000 0003a57b nt!KiTimerExpiration+0x88 (FPO: [Non-Fpo])
f7a1dff4 80544d6b acbdbf18 00000000 00000000 nt!KiRetireDpcList+0x61 (FPO: [0,1,0])
f7a1dff8 acbdbf18 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b (FPO: [Uses EBP] [0,0,1])
WARNING: Frame IP not in any known module. Following frames may be wrong.
80544d6b 00000000 00000009 0081850f bb830000 0xacbdbf18
start end module name
804d7000 806e2000 nt ntkrpamp.exe Wed Feb 28 01:15:54 2007 (45E5484A)
806e2000 80702c80 hal halmacpi.dll Wed Jun 22 17:05:52 2005 (42B9FCE0)
ab4c2000 ab4d4320 NAVENG NAVENG.SYS Tue Oct 30 13:39:40 2007 (4727968C)
ab4d5000 ab5a6c40 NAVEX15 NAVEX15.SYS Tue Oct 30 12:58:16 2007 (47278CD8)
ab5a7000 ab5d2000 SymIDSCo SymIDSCo.sys Sat Nov 03 10:22:18 2007 (472CAE4A)
abe4a000 abe4d200 SjyPkt SjyPkt.sys Tue Oct 01 17:57:11 2002 (3D9A4467)
abee2000 abf33480 srv srv.sys Mon Aug 14 03:34:39 2006 (44E051BF)
ac22c000 ac256180 kmixer kmixer.sys Wed Jun 14 01:47:45 2006 (448FCD31)
ac7f7000 ac837280 HTTP HTTP.sys Thu Mar 16 17:33:09 2006 (441A03C5)
ac84c000 ac84e6c0 mdmxsdk mdmxsdk.sys Wed Apr 09 13:48:53 2003 (3E948735)
acae0000 acb0c400 mrxdav mrxdav.sys Tue Aug 03 23:00:49 2004 (41107B91)
acb2d000 acb30e60 Aspi32 Aspi32.SYS Wed Jul 17 08:53:00 2002 (3D3592DC)
acf23000 acf37400 wdmaud wdmaud.sys Wed Jun 14 02:00:44 2006 (448FD03C)
ad360000 ad36ed80 sysaudio sysaudio.sys Tue Aug 03 23:15:54 2004 (41107F1A)
ad3e8000 ad3f8200 EAPPkt EAPPkt.sys Thu Mar 31 19:43:01 2005 (424CB535)
ad459000 ad45c900 ndisuio ndisuio.sys Mon Jun 20 18:52:55 2005 (42B772F7)
ad511000 ad5298c0 tfsnudfa tfsnudfa.sys Tue May 31 15:50:00 2005 (429CEA18)
ad52a000 ad542160 tfsnudf tfsnudf.sys Tue May 31 15:49:19 2005 (429CE9EF)
ad56b000 ad580320 tfsnifs tfsnifs.sys Tue May 31 15:49:14 2005 (429CE9EA)
ad68d000 ad690aa0 tfsnopio tfsnopio.sys Tue May 31 15:49:37 2005 (429CEA01)
adf99000 adfb0480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
adfd9000 adff8000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri Aug 24 18:52:21 2007 (46CF8B55)
adff8000 ae05b000 eeCtrl eeCtrl.sys Fri Aug 24 18:52:21 2007 (46CF8B55)
ae05b000 ae0c9a00 mrxsmb mrxsmb.sys Fri May 05 02:41:42 2006 (445B1DD6)
ae0ca000 ae0f4a00 rdbss rdbss.sys Fri May 05 02:47:55 2006 (445B1F4B)
ae0f5000 ae15e000 SPBBCDrv SPBBCDrv.sys Sat Apr 14 02:31:24 2007 (46209F6C)
ae19e000 ae1a75a0 drvnddm drvnddm.sys Thu Apr 21 13:43:05 2005 (42681059)
ae1fe000 ae21fd00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
ae220000 ae247c00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
ae273000 ae48e000 lvsvf2 lvsvf2.sys Fri May 27 09:23:35 2005 (42974987)
ae48e000 ae56cf80 LV302AV LV302AV.SYS Fri May 27 09:46:19 2005 (42974EDB)
ae56d000 ae58f000 SYMFW SYMFW.SYS Tue Oct 30 20:37:07 2007 (4727F863)
ae5a3000 ae5a5900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
ae5b7000 ae5dc000 SYMEVENT SYMEVENT.SYS Mon Sep 24 17:39:57 2007 (46F858DD)
ae5dc000 ae5fcf00 ipnat ipnat.sys Wed Sep 29 15:28:36 2004 (415B3714)
ae5fd000 ae62a200 SYMTDI SYMTDI.SYS Tue Oct 30 20:36:47 2007 (4727F84F)
ae62b000 ae682e80 tcpip tcpip.sys Tue Oct 30 10:20:52 2007 (472767F4)
ae683000 ae695400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
ae696000 ae6b1700 wg111v2 wg111v2.sys Wed Apr 20 22:33:11 2005 (42673B17)
ae7b7000 ae800000 SRTSP SRTSP.SYS Wed Nov 21 15:15:15 2007 (4744BC03)
bf000000 bf011580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
bf012000 bf058000 ati2dvag ati2dvag.dll Tue Dec 04 19:04:08 2007 (47561528)
bf058000 bf0d2000 ati2cqag ati2cqag.dll Tue Dec 04 18:11:17 2007 (475608C5)
bf0d2000 bf140000 atikvmag atikvmag.dll Tue Dec 04 18:19:14 2007 (47560AA2)
bf140000 bf170000 atiok3x2 atiok3x2.dll Tue Dec 04 18:14:59 2007 (475609A3)
bf170000 bf4774a0 ati3duag ati3duag.dll Tue Dec 04 18:44:52 2007 (475610A4)
bf478000 bf608700 ativvaxx ativvaxx.dll Tue Dec 04 18:33:46 2007 (47560E0A)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 05:47:34 2007 (45F013F6)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 00:56:56 2004 (411096C8)
f6359000 f635bf80 mouhid mouhid.sys Fri Aug 17 13:47:57 2001 (3B7D82FD)
f635d000 f6360a00 kbdhid kbdhid.sys Tue Aug 03 22:58:33 2004 (41107B09)
f6419000 f643a700 portcls portcls.sys Tue Mar 16 11:58:17 2004 (40574E49)
f643b000 f652cb20 sthda sthda.sys Wed Aug 17 12:39:31 2005 (43039273)
f6579000 f65d1e80 update update.sys Mon Apr 23 03:32:54 2007 (462C8B56)
f65d2000 f6602100 rdpdr rdpdr.sys Tue Aug 03 23:01:10 2004 (41107BA6)
f6603000 f6613e00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
f6614000 f662a680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
f662b000 f6651000 e100b325 e100b325.sys Thu Oct 14 16:30:44 2004 (416F0C24)
f6651000 f66f7300 HSF_CNXT HSF_CNXT.sys Mon Nov 17 05:58:00 2003 (3FB8D3E8)
f66f8000 f67f6800 HSF_DP HSF_DP.sys Mon Nov 17 05:56:13 2003 (3FB8D37D)
f67f7000 f6819680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f681a000 f684dd00 HSFHWBS2 HSFHWBS2.sys Mon Nov 17 05:59:18 2003 (3FB8D436)
f684e000 f6861780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
f6862000 f6b4d000 ati2mtag ati2mtag.sys Tue Dec 04 19:03:46 2007 (47561512)
f6b4d000 f6b6fe80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
f6b70000 f6b96000 HDAudBus HDAudBus.sys Thu Aug 12 17:45:52 2004 (411C0F40)
f6ba6000 f6ba9c80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
f72d4000 f72d6580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
f732d000 f7347580 Mup Mup.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f7348000 f7374a80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
f7375000 f7401400 Ntfs Ntfs.sys Fri Feb 09 03:10:31 2007 (45CC56A7)
f7402000 f7418780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
f7419000 f742e0c0 drvmcdb drvmcdb.sys Fri Apr 22 15:56:10 2005 (4269810A)
f742f000 f7440f00 sr sr.sys Tue Aug 03 23:06:22 2004 (41107CDE)
f7441000 f7460780 fltMgr fltMgr.sys Mon Aug 21 02:14:57 2006 (44E97991)
f7461000 f7478480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
f7479000 f749e700 dmio dmio.sys Tue Aug 03 23:07:13 2004 (41107D11)
f749f000 f74bd880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
f74be000 f74cea80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
f74cf000 f74fcd80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
f75fe000 f7606c00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
f760e000 f7618500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
f761e000 f762ac80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
f762e000 f7636e00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
f763e000 f764a200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
f764e000 f7656b60 PxHelp20 PxHelp20.sys Wed Aug 09 10:27:31 2006 (44DA1B03)
f766e000 f7677080 SRTSPX SRTSPX.SYS Wed Nov 21 15:17:28 2007 (4744BC88)
f76ae000 f76b6700 wanarp wanarp.sys Tue Aug 03 23:04:57 2004 (41107C89)
f76be000 f76c6d80 HIDCLASS HIDCLASS.SYS Tue Aug 03 23:08:18 2004 (41107D52)
f76ce000 f76d9000 lvusbsta lvusbsta.sys Fri May 27 09:31:26 2005 (42974B5E)
f76de000 f76e9e00 STREAM STREAM.SYS Tue Aug 03 23:07:58 2004 (41107D3E)
f76ee000 f76f6180 SYMIDS SYMIDS.SYS Tue Oct 30 20:37:14 2007 (4727F86A)
f76fe000 f7706d00 intelppm intelppm.sys Tue Aug 03 22:59:19 2004 (41107B37)
f770e000 f7718380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
f771e000 f772a180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
f772e000 f773c080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
f773e000 f774c780 usbaudio usbaudio.sys Tue Aug 03 23:07:52 2004 (41107D38)
f774e000 f7756700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
f776e000 f7776880 Fips Fips.SYS Fri Aug 17 18:31:49 2001 (3B7DC585)
f777e000 f77867e0 tfsncofs tfsncofs.sys Tue May 31 15:49:32 2005 (429CE9FC)
f778e000 f779a880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
f779e000 f77a8200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
f77ae000 f77b9d00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
f77be000 f77c6900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
f77ce000 f77d7f00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
f77de000 f77e7480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
f77ee000 f77fd900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
f780e000 f781cb80 drmk drmk.sys Tue Aug 03 23:07:54 2004 (41107D3A)
f784e000 f785c100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
f787e000 f7884200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
f7886000 f788a900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
f78be000 f78c3bc0 ssrtln ssrtln.sys Fri May 13 10:37:18 2005 (4284E5CE)
f78c6000 f78cc180 HIDPARSE HIDPARSE.SYS Tue Aug 03 23:08:15 2004 (41107D4F)
f78ce000 f78d3200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
f78d6000 f78d7000 Msfs Msfs.SYS unavailable (00000000)
f78de000 f78e5880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
f78e6000 f78ec780 USBSTOR USBSTOR.SYS Tue Aug 03 23:08:44 2004 (41107D6C)
f78f6000 f78fb200 SYMREDRV SYMREDRV.SYS Tue Oct 30 20:37:18 2007 (4727F86E)
f78fe000 f7904f00 SYMNDIS SYMNDIS.SYS Tue Oct 30 20:36:56 2007 (4727F858)
f7906000 f790c440 tfsnboio tfsnboio.sys Tue May 31 15:49:20 2005 (429CE9F0)
f797e000 f7982500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
f79a6000 f79ab000 usbuhci usbuhci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f79ae000 f79b4800 usbehci usbehci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f79be000 f79c5580 Modem Modem.SYS Tue Aug 03 23:08:04 2004 (41107D44)
f79c6000 f79cd000 GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 10:11:27 2006 (44D7743F)
f79ce000 f79d2880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
f79d6000 f79da580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
f79de000 f79e2080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
f79e6000 f79eb020 wanatw4 wanatw4.sys Tue Jul 16 08:23:14 2002 (3D343A62)
f79ee000 f79f4000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f79f6000 f79fba00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f7a06000 f7a0db80 usbccgp usbccgp.sys Tue Aug 03 23:08:45 2004 (41107D6D)
f7a0e000 f7a11000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
f7aa2000 f7aa5f00 MODEMCSA MODEMCSA.sys Fri Aug 17 13:57:37 2001 (3B7D8541)
f7ac2000 f7ac4280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
f7ad6000 f7ad8580 hidusb hidusb.sys Fri Aug 17 14:02:16 2001 (3B7D8658)
f7afe000 f7affb80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
f7b00000 f7b01100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f7b02000 f7b03580 intelide intelide.sys Tue Aug 03 22:59:40 2004 (41107B4C)
f7b04000 f7b05000 dmload dmload.sys unavailable (00000000)
f7b0a000 f7b0b500 dsunidrv dsunidrv.sys Sun Feb 18 10:31:02 2007 (45D89B66)
f7b1a000 f7b1b280 DSproct DSproct.sys Thu Oct 05 07:02:50 2006 (4525108A)
f7b36000 f7b375c0 sscdbhk5 sscdbhk5.sys Fri May 13 10:37:26 2005 (4284E5D6)
f7b4a000 f7b4b100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
f7b58000 f7b59280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
f7b5a000 f7b5c000 i2omgmt i2omgmt.SYS Tue Aug 03 23:00:50 2004 (41107B92)
f7b64000 f7b65f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 13:49:37 2001 (3B7D8361)
f7b66000 f7b67080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
f7b68000 f7b69080 mnmdd mnmdd.SYS Fri Aug 17 13:57:28 2001 (3B7D8538)
f7b6a000 f7b6b080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
f7b6e000 f7b6f8a0 tfsnpool tfsnpool.sys Tue May 31 15:49:15 2005 (429CE9EB)
f7b72000 f7b73800 SYMDNS SYMDNS.SYS Tue Oct 30 20:36:49 2007 (4727F851)
f7b74000 f7b75be0 lv302af lv302af.sys Fri May 27 09:37:58 2005 (42974CE6)
f7b90000 f7b91900 splitter splitter.sys Wed Jun 14 01:47:46 2006 (448FCD32)
f7bc0000 f7bc1100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f7bc6000 f7bc6d00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
f7bf6000 f7bf6c00 audstub audstub.sys Fri Aug 17 13:59:40 2001 (3B7D85BC)
f7c07000 f7c07880 tfsndres tfsndres.sys Tue May 31 15:50:05 2005 (429CEA1D)
f7c50000 f7c50980 Cdr4_xp Cdr4_xp.SYS Wed Aug 10 11:28:07 2005 (42FA4737)
f7c51000 f7c51a00 Cdralw2k Cdralw2k.SYS Wed Aug 10 11:28:04 2005 (42FA4734)
f7c74000 f7c75000 Null Null.SYS unavailable (00000000)
f7cdd000 f7cddd00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)
f7cff000 f7cfffe0 tfsndrct tfsndrct.sys Tue May 31 15:49:36 2005 (429CEA00)

Unloaded modules:
ae6d2000 ae6e5000 NAVENG.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ae6e5000 ae7b7000 NAVEX15.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ae248000 ae273000 SymIDSCo.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ace35000 ace60000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7cc9000 f7cca000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad018000 ad025000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad188000 ad196000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ace60000 ace83000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b84000 f7b86000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f775e000 f776e000 serial.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7abe000 f7ac2000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f769e000 f76ab000 i8042prt.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f78b6000 f78bb000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7ab6000 f7ab9000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b54000 f7b56000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f782e000 f7839000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b50000 f7b52000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f77ee000 f77f9000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b48000 f7b4a000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f777e000 f7789000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b44000 f7b46000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f776e000 f7779000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b40000 f7b42000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f775e000 f7769000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b3c000 f7b3e000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f774e000 f7759000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b38000 f7b3a000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f773e000 f7749000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7bf0000 f7bf1000 Cdralw2k.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7bf1000 f7bf2000 Cdr4_xp.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Thanks! That's what we're looking for. Please paste two more dump logs for your most recent dumps.

File name format is Minixxxxxx-yy.dmp where xxxxxx is the date in m/d/y format and yy is the crash count for that day.

 

(I deleted the contents of this post as they are no longer relevant.)

 

Dump data #2

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini011308-04.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
Mini Kernel Dump does not contain driver list
Debugger can not determine kernel base address
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Jan 13 20:46:28.312 2008 (GMT-8)
System Uptime: 0 days 0:08:49.203
Mini Kernel Dump does not contain driver list
Debugger can not determine kernel base address
Loading Kernel Symbols
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {40000608, 2, 0, f728e1a6}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Probably caused by : Unknown_Image ( lvusbsta+90fb )

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

0: kd> !analyze -v;r;kv;lmtn;.logclose;q
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 40000608, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f728e1a6, address which referenced memory

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
40000608

CURRENT_IRQL: 2

FAULTING_IP:
+fffffffff728e1a6
f728e1a6 8b7808 mov edi,dword ptr [eax+8]

CUSTOMER_CRASH_COUNT: 4

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from f77970fb to f728e1a6

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
abe69754 f77970fb 86491618 abe6976c abe69794 0xf728e1a6
abe69764 f779446b 85461360 abe69788 852ff810 <Unloaded_lvusbsta.sys>+0x90fb
abe69794 f7791abd 002f45b8 85844878 00000005 <Unloaded_lvusbsta.sys>+0x646b
abe697ac f6f3de98 852ff810 85844888 85844878 <Unloaded_lvusbsta.sys>+0x3abd
abe69810 f6f423b8 852ff810 00000005 e3a3fb78 0xf6f3de98
abe6983c f6f4ee79 852ff810 e3a3fb50 852f45ac 0xf6f423b8
abe69870 f6f3df85 86b2a4f0 852ff810 abe698bc 0xf6f4ee79
abe69880 804ef163 86b2a4f0 852ff810 852ff810 0xf6f3df85
abe698bc f7bb0c55 8574b4c0 00000000 002f0003 0x804ef163
abe698fc f6f3de98 852f8008 855411e0 855411d0 0xf7bb0c55
abe69960 f6f423b8 852f8008 00000004 e6cbbdc0 0xf6f3de98
abe6998c f6f4ee79 852f8008 e6cbbd98 85203414 0xf6f423b8
abe699c0 f6f3df85 85364d78 852f8008 abe69a0c 0xf6f4ee79
abe699d0 804ef163 85364d78 852f8008 852f8008 0xf6f3df85
abe69a0c ac1daf0c 8587bd68 00000000 002f0003 0x804ef163
abe69a5c ac1db4d9 856e9678 abe69a84 856e9678 0xac1daf0c
abe69a98 ac1ec36b 856e9678 85233d18 00000008 0xac1db4d9
abe69ab8 f6f3de98 854d1338 85342bd0 85342bc0 0xac1ec36b
abe69b1c f6f3dec9 854d1338 00000007 ac1dee30 0xf6f3de98
abe69b40 ac1dc3e1 854d1338 00000007 ac1dee08 0xf6f3dec9
abe69b68 f6f3df85 856c9f10 856e9678 abe69bd8 0xac1dc3e1
abe69b78 804ef163 856c9f10 854d1338 854d1338 0xf6f3df85
abe69bd8 ad17b2a2 854d1338 00000000 e6a062d8 0x804ef163
abe69c30 f6f3df85 858416b8 854d1338 abe69c64 0xad17b2a2
abe69c40 804ef163 858416b8 854d1338 806e4410 0xf6f3df85
abe69c64 8057f5e1 858416b8 854d1338 854ed8b0 0x804ef163
abe69d00 80578136 0000279c 000021a4 00000000 0x8057f5e1
abe69d34 805409ac 0000279c 000021a4 00000000 0x80578136
abe69d64 7c90eb94 badb0d00 0dbbfd74 abe69d98 0x805409ac
abe69d68 badb0d00 0dbbfd74 abe69d98 abe69dcc 0x7c90eb94
abe69d6c 0dbbfd74 abe69d98 abe69dcc 00000000 0xbadb0d00
abe69d70 abe69d98 abe69dcc 00000000 00000000 0xdbbfd74
abe69d74 abe69dcc 00000000 00000000 00000000 0xabe69d98
abe69d98 00000000 00000004 07e00968 00000000 0xabe69dcc


STACK_COMMAND: kb

FOLLOWUP_IP:
lvusbsta+90fb
f77970fb ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: lvusbsta+90fb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

eax=40000600 ebx=852e2000 ecx=abe6976c edx=00000000 esi=85844878 edi=85461360
eip=f728e1a6 esp=abe69744 ebp=abe69754 iopl=0 ov up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a16
f728e1a6 8b7808 mov edi,dword ptr [eax+8] ds:0023:40000608=????????
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
ChildEBP RetAddr Args to Child
WARNING: Frame IP not in any known module. Following frames may be wrong.
abe69754 f77970fb 86491618 abe6976c abe69794 0xf728e1a6
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69764 f779446b 85461360 abe69788 852ff810 <Unloaded_lvusbsta.sys>+0x90fb
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69794 f7791abd 002f45b8 85844878 00000005 <Unloaded_lvusbsta.sys>+0x646b
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe697ac f6f3de98 852ff810 85844888 85844878 <Unloaded_lvusbsta.sys>+0x3abd
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69810 f6f423b8 852ff810 00000005 e3a3fb78 0xf6f3de98
Mini Kernel Dump does not contain driver list

Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe6983c f6f4ee79 852ff810 e3a3fb50 852f45ac 0xf6f423b8
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69870 f6f3df85 86b2a4f0 852ff810 abe698bc 0xf6f4ee79
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69880 804ef163 86b2a4f0 852ff810 852ff810 0xf6f3df85
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe698bc f7bb0c55 8574b4c0 00000000 002f0003 0x804ef163
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe698fc f6f3de98 852f8008 855411e0 855411d0 0xf7bb0c55
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69960 f6f423b8 852f8008 00000004 e6cbbdc0 0xf6f3de98
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe6998c f6f4ee79 852f8008 e6cbbd98 85203414 0xf6f423b8
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe699c0 f6f3df85 85364d78 852f8008 abe69a0c 0xf6f4ee79
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe699d0 804ef163 85364d78 852f8008 852f8008 0xf6f3df85
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69a0c ac1daf0c 8587bd68 00000000 002f0003 0x804ef163
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69a5c ac1db4d9 856e9678 abe69a84 856e9678 0xac1daf0c
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69a98 ac1ec36b 856e9678 85233d18 00000008 0xac1db4d9
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69ab8 f6f3de98 854d1338 85342bd0 85342bc0 0xac1ec36b
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69b1c f6f3dec9 854d1338 00000007 ac1dee30 0xf6f3de98
Mini Kernel Dump does not contain driver list
Mini Kernel Dump does not contain driver list
abe69b40 ac1dc3e1 854d1338 00000007 ac1dee08 0xf6f3dec9
start end module name

Unloaded modules:
acfed000 ad018000 Unknown_Module_acfed000
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d14000 f7d15000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad2a8000 ad2b5000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f6b0f000 f6b1d000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad018000 ad03b000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7bc0000 f7bc2000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f76ce000 f76de000 serial.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7ae2000 f7ae6000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f768e000 f769b000 i8042prt.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f78d6000 f78db000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7ada000 f7add000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b5c000 f7b5e000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f783e000 f7849000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b58000 f7b5a000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f77ee000 f77f9000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b50000 f7b52000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f778e000 f7799000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b4c000 f7b4e000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f777e000 f7789000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b48000 f7b4a000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f776e000 f7779000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b44000 f7b46000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f775e000 f7769000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b40000 f7b42000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f774e000 f7759000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c30000 f7c31000 Cdralw2k.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c25000 f7c26000 Cdr4_xp.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

--

By the way, the log said 'Mini Kernel Dump does not contain driver list' about a million times so i cut some out to shorten it.

 

Dump data #3

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\WINDOWS\Minidump\Mini011308-03.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) 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: Sun Jan 13 20:36:51.390 2008 (GMT-8)
System Uptime: 0 days 4:01:14.272
Loading Kernel Symbols
..................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 804ef762, acb74c00, 0}



Probably caused by : ntkrpamp.exe ( nt!IopXxxControlFile+1aa )

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

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* 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: 804ef762, The address that the exception occurred at
Arg3: acb74c00, 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:
nt!IoGetRelatedDeviceObject+2c
804ef762 8b4008 mov eax,dword ptr [eax+8]

TRAP_FRAME: acb74c00 -- (.trap 0xffffffffacb74c00)
.trap 0xffffffffacb74c00
ErrCode = 00000000
eax=65536d4d ebx=00000000 ecx=8577b928 edx=8577b910 esi=85296568 edi=acb74d64
eip=804ef762 esp=acb74c74 ebp=acb74c7c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!IoGetRelatedDeviceObject+0x2c:
804ef762 8b4008 mov eax,dword ptr [eax+8] ds:0023:65536d55=????????
.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Steam.exe

LAST_CONTROL_TRANSFER: from 8057f1c6 to 804ef762

STACK_TEXT:
acb74c7c 8057f1c6 85296568 acb74d64 1026fb00 nt!IoGetRelatedDeviceObject+0x2c
acb74d00 80578136 00001f7c 00001ad8 00000000 nt!IopXxxControlFile+0x1aa
acb74d34 805409ac 00001f7c 00001ad8 00000000 nt!NtDeviceIoControlFile+0x2a
acb74d34 7c90eb94 00001f7c 00001ad8 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
1026fc04 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!IopXxxControlFile+1aa
8057f1c6 eb08 jmp nt!IopXxxControlFile+0x1b4 (8057f1d0)

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!IopXxxControlFile+1aa

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

FAILURE_BUCKET_ID: 0x8E_nt!IopXxxControlFile+1aa

BUCKET_ID: 0x8E_nt!IopXxxControlFile+1aa

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

eax=65536d4d ebx=00000000 ecx=8577b928 edx=8577b910 esi=85296568 edi=acb74d64
eip=804ef762 esp=acb74c74 ebp=acb74c7c iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!IoGetRelatedDeviceObject+0x2c:
804ef762 8b4008 mov eax,dword ptr [eax+8] ds:0023:65536d55=????????
ChildEBP RetAddr Args to Child
acb74c7c 8057f1c6 85296568 acb74d64 1026fb00 nt!IoGetRelatedDeviceObject+0x2c (FPO: [Non-Fpo])
acb74d00 80578136 00001f7c 00001ad8 00000000 nt!IopXxxControlFile+0x1aa (FPO: [Non-Fpo])
acb74d34 805409ac 00001f7c 00001ad8 00000000 nt!NtDeviceIoControlFile+0x2a (FPO: [Non-Fpo])
acb74d34 7c90eb94 00001f7c 00001ad8 00000000 nt!KiFastCallEntry+0xfc (FPO: [0,0] TrapFrame @ acb74d64)
WARNING: Frame IP not in any known module. Following frames may be wrong.
1026fc04 00000000 00000000 00000000 00000000 0x7c90eb94
start end module name
804d7000 806e2000 nt ntkrpamp.exe Wed Feb 28 01:15:54 2007 (45E5484A)
806e2000 80702c80 hal halmacpi.dll Wed Jun 22 17:05:52 2005 (42B9FCE0)
abf26000 abf29200 SjyPkt SjyPkt.sys Tue Oct 01 17:57:11 2002 (3D9A4467)
ac31a000 ac344180 kmixer kmixer.sys Wed Jun 14 01:47:45 2006 (448FCD31)
ac45d000 ac4ae480 srv srv.sys Mon Aug 14 03:34:39 2006 (44E051BF)
ac847000 ac887280 HTTP HTTP.sys Thu Mar 16 17:33:09 2006 (441A03C5)
aca24000 aca266c0 mdmxsdk mdmxsdk.sys Wed Apr 09 13:48:53 2003 (3E948735)
acae8000 acaebe60 Aspi32 Aspi32.SYS Wed Jul 17 08:53:00 2002 (3D3592DC)
acb08000 acb34400 mrxdav mrxdav.sys Tue Aug 03 23:00:49 2004 (41107B91)
ad03b000 ad04f400 wdmaud wdmaud.sys Wed Jun 14 02:00:44 2006 (448FD03C)
ad3e8000 ad3f8200 EAPPkt EAPPkt.sys Thu Mar 31 19:43:01 2005 (424CB535)
ad4a1000 ad4afd80 sysaudio sysaudio.sys Tue Aug 03 23:15:54 2004 (41107F1A)
ad511000 ad5298c0 tfsnudfa tfsnudfa.sys Tue May 31 15:50:00 2005 (429CEA18)
ad52a000 ad542160 tfsnudf tfsnudf.sys Tue May 31 15:49:19 2005 (429CE9EF)
ad543000 ad558320 tfsnifs tfsnifs.sys Tue May 31 15:49:14 2005 (429CE9EA)
ad565000 ad568900 ndisuio ndisuio.sys Mon Jun 20 18:52:55 2005 (42B772F7)
ad68d000 ad690aa0 tfsnopio tfsnopio.sys Tue May 31 15:49:37 2005 (429CEA01)
adf99000 adfb0480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
adfd9000 ae1f4000 lvsvf2 lvsvf2.sys Fri May 27 09:23:35 2005 (42974987)
ae264000 ae26c7e0 tfsncofs tfsncofs.sys Tue May 31 15:49:32 2005 (429CE9FC)
ae294000 ae372f80 LV302AV LV302AV.SYS Fri May 27 09:46:19 2005 (42974EDB)
ae373000 ae38e700 wg111v2 wg111v2.sys Wed Apr 20 22:33:11 2005 (42673B17)
ae38f000 ae3ae000 EraserUtilRebootDrv EraserUtilRebootDrv.sys Fri Aug 24 18:52:21 2007 (46CF8B55)
ae3ae000 ae411000 eeCtrl eeCtrl.sys Fri Aug 24 18:52:21 2007 (46CF8B55)
ae411000 ae47fa00 mrxsmb mrxsmb.sys Fri May 05 02:41:42 2006 (445B1DD6)
ae4a8000 ae4d2a00 rdbss rdbss.sys Fri May 05 02:47:55 2006 (445B1F4B)
ae4d3000 ae53c000 SPBBCDrv SPBBCDrv.sys Sat Apr 14 02:31:24 2007 (46209F6C)
ae53c000 ae55dd00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
ae55e000 ae585c00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
ae586000 ae5b1000 SymIDSCo SymIDSCo.sys Sat Nov 03 10:22:18 2007 (472CAE4A)
ae5b1000 ae5d3000 SYMFW SYMFW.SYS Tue Oct 30 20:37:07 2007 (4727F863)
ae5d3000 ae5f8000 SYMEVENT SYMEVENT.SYS Mon Sep 24 17:39:57 2007 (46F858DD)
ae5f8000 ae618f00 ipnat ipnat.sys Wed Sep 29 15:28:36 2004 (415B3714)
ae619000 ae646200 SYMTDI SYMTDI.SYS Tue Oct 30 20:36:47 2007 (4727F84F)
ae647000 ae69ee80 tcpip tcpip.sys Tue Oct 30 10:20:52 2007 (472767F4)
ae69f000 ae6b1400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
ae6d2000 ae6e4320 NAVENG NAVENG.SYS Tue Oct 30 13:39:40 2007 (4727968C)
ae6e5000 ae7b6c40 NAVEX15 NAVEX15.SYS Tue Oct 30 12:58:16 2007 (47278CD8)
ae7b7000 ae800000 SRTSP SRTSP.SYS Wed Nov 21 15:15:15 2007 (4744BC03)
bf000000 bf011580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
bf012000 bf058000 ati2dvag ati2dvag.dll Tue Dec 04 19:04:08 2007 (47561528)
bf058000 bf0d2000 ati2cqag ati2cqag.dll Tue Dec 04 18:11:17 2007 (475608C5)
bf0d2000 bf140000 atikvmag atikvmag.dll Tue Dec 04 18:19:14 2007 (47560AA2)
bf140000 bf170000 atiok3x2 atiok3x2.dll Tue Dec 04 18:14:59 2007 (475609A3)
bf170000 bf4774a0 ati3duag ati3duag.dll Tue Dec 04 18:44:52 2007 (475610A4)
bf478000 bf608700 ativvaxx ativvaxx.dll Tue Dec 04 18:33:46 2007 (47560E0A)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 05:47:34 2007 (45F013F6)
bffa0000 bffe5c00 ATMFD ATMFD.DLL Wed Aug 04 00:56:56 2004 (411096C8)
f5b93000 f5b95900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
f5bb3000 f5bb5f80 mouhid mouhid.sys Fri Aug 17 13:47:57 2001 (3B7D82FD)
f6357000 f6378700 portcls portcls.sys Tue Mar 16 11:58:17 2004 (40574E49)
f6379000 f646ab20 sthda sthda.sys Wed Aug 17 12:39:31 2005 (43039273)
f64b7000 f650fe80 update update.sys Mon Apr 23 03:32:54 2007 (462C8B56)
f6510000 f6540100 rdpdr rdpdr.sys Tue Aug 03 23:01:10 2004 (41107BA6)
f6541000 f6551e00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
f6552000 f6568680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
f6569000 f658f000 e100b325 e100b325.sys Thu Oct 14 16:30:44 2004 (416F0C24)
f658f000 f6635300 HSF_CNXT HSF_CNXT.sys Mon Nov 17 05:58:00 2003 (3FB8D3E8)
f6636000 f6734800 HSF_DP HSF_DP.sys Mon Nov 17 05:56:13 2003 (3FB8D37D)
f6735000 f6757680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f6758000 f678bd00 HSFHWBS2 HSFHWBS2.sys Mon Nov 17 05:59:18 2003 (3FB8D436)
f678c000 f679f780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
f67a0000 f6a8b000 ati2mtag ati2mtag.sys Tue Dec 04 19:03:46 2007 (47561512)
f6a8b000 f6aade80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
f6aae000 f6ad4000 HDAudBus HDAudBus.sys Thu Aug 12 17:45:52 2004 (411C0F40)
f72e0000 f72e3c80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
f732d000 f7347580 Mup Mup.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f7348000 f7374a80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
f7375000 f7401400 Ntfs Ntfs.sys Fri Feb 09 03:10:31 2007 (45CC56A7)
f7402000 f7418780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
f7419000 f742e0c0 drvmcdb drvmcdb.sys Fri Apr 22 15:56:10 2005 (4269810A)
f742f000 f7440f00 sr sr.sys Tue Aug 03 23:06:22 2004 (41107CDE)
f7441000 f7460780 fltMgr fltMgr.sys Mon Aug 21 02:14:57 2006 (44E97991)
f7461000 f7478480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
f7479000 f749e700 dmio dmio.sys Tue Aug 03 23:07:13 2004 (41107D11)
f749f000 f74bd880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
f74be000 f74cea80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
f74cf000 f74fcd80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
f75fe000 f7606c00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
f760e000 f7618500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
f761e000 f762ac80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
f762e000 f7636e00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
f763e000 f764a200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
f764e000 f7656b60 PxHelp20 PxHelp20.sys Wed Aug 09 10:27:31 2006 (44DA1B03)
f766e000 f7676180 SYMIDS SYMIDS.SYS Tue Oct 30 20:37:14 2007 (4727F86A)
f767e000 f7686700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
f769e000 f76a6880 Fips Fips.SYS Fri Aug 17 18:31:49 2001 (3B7DC585)
f76ae000 f76b75a0 drvnddm drvnddm.sys Thu Apr 21 13:43:05 2005 (42681059)
f76be000 f76cd900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
f76ce000 f76d6d00 intelppm intelppm.sys Tue Aug 03 22:59:19 2004 (41107B37)
f76de000 f76e8380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
f76ee000 f76fa180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
f76fe000 f770c080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
f770e000 f7716d80 HIDCLASS HIDCLASS.SYS Tue Aug 03 23:08:18 2004 (41107D52)
f771e000 f7729000 lvusbsta lvusbsta.sys Fri May 27 09:31:26 2005 (42974B5E)
f772e000 f7739e00 STREAM STREAM.SYS Tue Aug 03 23:07:58 2004 (41107D3E)
f773e000 f774c780 usbaudio usbaudio.sys Tue Aug 03 23:07:52 2004 (41107D38)
f775e000 f776a880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
f776e000 f7778200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
f777e000 f7789d00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
f778e000 f7796900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
f779e000 f77a7f00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
f77ae000 f77b7480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
f77de000 f77ecb80 drmk drmk.sys Tue Aug 03 23:07:54 2004 (41107D3A)
f781e000 f782c100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
f783e000 f7847080 SRTSPX SRTSPX.SYS Wed Nov 21 15:17:28 2007 (4744BC88)
f785e000 f7866700 wanarp wanarp.sys Tue Aug 03 23:04:57 2004 (41107C89)
f787e000 f7884200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
f7886000 f788a900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
f7896000 f789c180 HIDPARSE HIDPARSE.SYS Tue Aug 03 23:08:15 2004 (41107D4F)
f78b6000 f78bb200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
f78be000 f78bf000 Msfs Msfs.SYS unavailable (00000000)
f78c6000 f78cd880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
f78ce000 f78d3200 SYMREDRV SYMREDRV.SYS Tue Oct 30 20:37:18 2007 (4727F86E)
f78d6000 f78dcf00 SYMNDIS SYMNDIS.SYS Tue Oct 30 20:36:56 2007 (4727F858)
f7906000 f790c780 USBSTOR USBSTOR.SYS Tue Aug 03 23:08:44 2004 (41107D6C)
f7916000 f791a500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
f7936000 f793c440 tfsnboio tfsnboio.sys Tue May 31 15:49:20 2005 (429CE9F0)
f799e000 f79a3000 usbuhci usbuhci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f79a6000 f79ac800 usbehci usbehci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f79ae000 f79b5580 Modem Modem.SYS Tue Aug 03 23:08:04 2004 (41107D44)
f79b6000 f79bd000 GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 10:11:27 2006 (44D7743F)
f79be000 f79c2880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
f79c6000 f79ca580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
f79ce000 f79d2080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
f79d6000 f79db020 wanatw4 wanatw4.sys Tue Jul 16 08:23:14 2002 (3D343A62)
f79de000 f79e4000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f79e6000 f79eba00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f79f6000 f79fdb80 usbccgp usbccgp.sys Tue Aug 03 23:08:45 2004 (41107D6D)
f7a06000 f7a0bbc0 ssrtln ssrtln.sys Fri May 13 10:37:18 2005 (4284E5CE)
f7a0e000 f7a11000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
f7aa2000 f7aa5f00 MODEMCSA MODEMCSA.sys Fri Aug 17 13:57:37 2001 (3B7D8541)
f7ad2000 f7ad4280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
f7ade000 f7ae0580 hidusb hidusb.sys Fri Aug 17 14:02:16 2001 (3B7D8658)
f7af2000 f7af5a00 kbdhid kbdhid.sys Tue Aug 03 22:58:33 2004 (41107B09)
f7afa000 f7afc580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
f7afe000 f7affb80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
f7b00000 f7b01100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f7b02000 f7b03580 intelide intelide.sys Tue Aug 03 22:59:40 2004 (41107B4C)
f7b04000 f7b05000 dmload dmload.sys unavailable (00000000)
f7b36000 f7b375c0 sscdbhk5 sscdbhk5.sys Fri May 13 10:37:26 2005 (4284E5D6)
f7b3c000 f7b3d500 dsunidrv dsunidrv.sys Sun Feb 18 10:31:02 2007 (45D89B66)
f7b4a000 f7b4b100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
f7b5a000 f7b5b280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
f7b5c000 f7b5e000 i2omgmt i2omgmt.SYS Tue Aug 03 23:00:50 2004 (41107B92)
f7b60000 f7b61000 Fs_Rec Fs_Rec.SYS unavailable (00000000)
f7b62000 f7b63080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
f7b64000 f7b65080 mnmdd mnmdd.SYS Fri Aug 17 13:57:28 2001 (3B7D8538)
f7b66000 f7b67080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
f7b6c000 f7b6d800 SYMDNS SYMDNS.SYS Tue Oct 30 20:36:49 2007 (4727F851)
f7b6e000 f7b6fbe0 lv302af lv302af.sys Fri May 27 09:37:58 2005 (42974CE6)
f7b84000 f7b85100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f7b96000 f7b97280 DSproct DSproct.sys Thu Oct 05 07:02:50 2006 (4525108A)
f7b9e000 f7b9f8a0 tfsnpool tfsnpool.sys Tue May 31 15:49:15 2005 (429CE9EB)
f7bc2000 f7bc3900 splitter splitter.sys Wed Jun 14 01:47:46 2006 (448FCD32)
f7bc6000 f7bc6d00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
f7c38000 f7c38fe0 tfsndrct tfsndrct.sys Tue May 31 15:49:36 2005 (429CEA00)
f7c3b000 f7c3bc00 audstub audstub.sys Fri Aug 17 13:59:40 2001 (3B7D85BC)
f7c54000 f7c54d00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)
f7c84000 f7c84880 tfsndres tfsndres.sys Tue May 31 15:50:05 2005 (429CEA1D)
f7c99000 f7c99980 Cdr4_xp Cdr4_xp.SYS Wed Aug 10 11:28:07 2005 (42FA4737)
f7c9a000 f7c9aa00 Cdralw2k Cdralw2k.SYS Wed Aug 10 11:28:04 2005 (42FA4734)
f7cc2000 f7cc3000 Null Null.SYS unavailable (00000000)

Unloaded modules:
acfed000 ad018000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7d0b000 f7d0c000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad200000 ad20d000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad018000 ad03b000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ad210000 ad21e000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b48000 f7b4a000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f768e000 f769e000 serial.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7ac2000 f7ac6000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f784e000 f785b000 i8042prt.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f79fe000 f7a03000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7aba000 f7abd000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b54000 f7b56000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f77fe000 f7809000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b50000 f7b52000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f77be000 f77c9000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b48000 f7b4a000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f774e000 f7759000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b44000 f7b46000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f773e000 f7749000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b40000 f7b42000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f772e000 f7739000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b3c000 f7b3e000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f771e000 f7729000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7b38000 f7b3a000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f770e000 f7719000 lvusbsta.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c39000 f7c3a000 Cdralw2k.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7c38000 f7c39000 Cdr4_xp.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

The first dump is crashed with bugcheck 0A with IRQL x'1c' and this is the symptom of hardware error. The second dump has "Mini Kernel Dump does not contain driver list" and it means the dump is taken unsuccessfully and it is also the symptom of hardware error.

Possible cause
1. Faulty ram
2. Faulty PSU (power supply unit)

 

Thank you, cpc2004!

Mzh, cpc2004 is an expert at analyzing dump logs.

==========
NOTE: If your computer is currently covered by a warranty, then opening the case and/or removing/adding hardware components might void your warranty.
==========

Testing for Faulty RAM:

In case you decide to test your RAM for errors, all of the following RAM testers have been recommended in this forum. However, opinions differ about which RAM tester is "best ".

• DocMem
• Memtest86 (downloadable via the "Free Download" link on their home page menu)
• Microsoft's Windows Memory Diagnostic

If you discover an error with any of these RAM testers and the RAM tester does not identify which RAM module is defective, then re-run the test with only a single RAM module installed until you identify which module is defective. (I am not familiar with the exact information output of any of these RAM testers when they find errors.)


A More Reliable RAM Testing Method:

1. Remove some of the memory modules from the computer (while the computer is off, of course).
   • For example, if two RAM modules are installed in your computer, remove one of the RAM modules.
2. Start your computer and see if the problem goes away.
3. If you continue to have unexpected reboots/BSODs, then replace that RAM module with another module, or install the module in a different memory slot.
4. Start your computer and see if the problem goes away.

Continue this process to see if you can pinpoint the cause of your problem to a specific RAM module or slot.

==========

• Microsoft KB134503:
  

==========

We'll follow up on the possibility of a faulty or underpowered power supply unit (PSU) if necessary.

Is your computer still covered by a warranty?

 

thanks!

Thank you both so much! If either of those things were causing my problem, would it be difficult to fix?

I'm not entirely sure if my computer is still covered by a warranty, but we've already opened it up to replace my old intel chipset with a new radeon card, which probably would be against my warranty anyway. I'll run one of those tests and see if it does anything, then maybe try the second way too. I'll update you afterwards.

 

If necessary, I would be inclined to try all three RAM testers mentioned. Perhaps one tester will discover faults that the others may miss. cpc2004 seems to usually suggest Memtest so I would be inclined to try Memtest first.

Since you have already replaced the graphics card, I suspect your warranty would already be voided. You might want to check with Dell anyway before you try the more reliable RAM testing method I described above (which involves physically moving RAM sticks around) if the RAM testers do not identify any faults.

==========

No. Both the RAM and PSU are probably fairly easy to replace once you have the correct parts in hand. Only real difficulty might be parting with $$ for new parts or locating the specifications and/or parts for your particular computer.

You would need to be sure the hardware you get for replacement will be compatible with your particular computer. For example, some computers have PSUs that are odd-size and/or have odd connectors so you would need to be sure the replacement PSU will fit. The PSU should also be good quality with enough power (Watts) and sufficient current ratings for the "12V rail(s)" (at least 18A).

• 10stripe - The Big Power Supply Guide - Brands

• Newegg.com: "Today's Power Supplies Deals" and "See All Power Supplies "

Likewise, you would need to check to be sure the RAM you get for the computer is compatible (and good quality IMHO).

NOTE: The people who frequent the Hardware forum are probably better sources of helpful hardware suggestions.

==========

Can you provide any more specifics about your computer model? Perhaps you have the receipt for your computer handy which should identify the exact model.

According to the information in this link, I'm guessing your computer is either a "Dimension 3100" or "Dimension E310 ". If so, then please identify which one is your computer.

• Dell™ Dimension™ 3100/E310 Service Manual includes detailed RAM/PSU removal/replacement instructions.
  • Specifications
    
    230 Watts seems to be on the low side to me, especially for gaming with a high-performance graphics card. If this is the situation with your computer, then I would certainly investigate the possibility of upgrading the PSU. People who are into gaming with high-performance graphics cards seem to often recommend at least 450W with at least 18A on the 12V rail(s).

If your PSU is 230 Watts, then I suspect your PSU cannot supply enough juice. I would like us to get a 2nd opinion from Rockster2U or mattman. They have significantly more hardware experience than me.

==========

Have you "overclocked" your graphics card (and/or CPU) or are you running it at stock configuration? Have you modified memory timings in your RAM?

Did your computer come with any hardware monitoring software that may be used to check temperatures, voltages, etc.?

Do your crashes usually/always occur during periods of gaming? I wonder whether any temperatures might be climbing too high or voltages getting out of specs. I don't game much but I suspect WoW is pretty graphics-intensive, which would demand a lot from your hardware.


BTW, someone might request you run a handy hardware information tool called EVEREST. If so, please keep in mind EVEREST can produce information that may not be accurate. You should consult with hardware experts before making any decisions based on information EVEREST reports.

==========

One 1GB stick (1024MB)? Two 512MB sticks? Some other combination?

 

I think the first test can only be used if you save it to a bootable floppy, and I don't think I have a floppy drive unless its hidden somewhere. And I'm almost positive that my warranty was only a year old and is already up, but I'm also not worried about it.

---

My computer model is an E310. Is there any other information you might need?

---

If upgrading my PSU isn't overly expensive, I'll definitely look into it then. As of now, the only game I play is WoW but I'm sure it's a pretty graphic-intensive game.

---

I'm not even really sure what that means, so as far as I know, I haven't done any of those things. How can I check?
I downloaded a free trial of both everest and sensorview, but I think I'd have to get the full version for either to be helpful.
My errors almost always occur while the game is running, but one or twice have happened while rebooting.

---

In my directx information, it says 1014MB of RAM, and my system properties says .99GB of RAM, but that seems wrong doesn't it? I know I only have one memory stick though.

 

I expect you can burn DocMem to a CD (if you have a CD burner). I expect you can also make that CD bootable.

• 
  ComputerHope.com: How to make a bootable CD.

• 
  Another Current Windows BBS Discussion: How can I make a BOOTABLE CD if I have no floppy drive?

I think Memtest and the Windows Memory Diagnostic will be easier for creating a bootable diagnostic CD though. Those two are usually the ones suggested around here lately anyway. The Windows Memory Diagnostic bootable CD appears to me to be the simplest to create and use (thanks to Microsoft's detailed instructions).

Thanks! That's good for now. Good to know the links I provided above for the E310 will be helpful.

Might want to refer to the E310 manual I linked and pull your PSU out (if necessary) to measure its dimensions before investigating potential replacement PSUs. Also, take note of how long the main power connecting cable is. While you're at it, write down the specifications that are likely printed on the PSU in case someone asks about those specifications.

If you decide to make measurements, then please post the PSU dimensions and main power cable length so we might be able to help you with locating a suitable replacement PSU. That information may be helpful in determining whether a possible replacement PSU will fit. If we're lucky, it will be a standard size PSU.

If you also provide us with an acceptable price range for a PSU, we might be able to help you locate what we think might be suitable replacements.

In any case, I think we should get a 2nd opinion form Rockster2U, mattman, and/or Whiskeyman before making any final decisions regarding a PSU.

If I could, I would move this thread to the hardware forum since the focus is now firmly on hardware after cpc2004's post. Perhaps a forum moderator will be willing to do so. (PeteC, are you reading this? )

==========

BTW, I edited my post above (#11) to include links to PSUs sold by Newegg.com. I suggest you cross-reference the PSUs available at Newegg with the 10stripe recommendations I linked. That will at least help you get a feel for what a good quality new PSU would cost.

An advantage with shopping around at Newegg is the customer ratings/reviews that Newegg displays. Ratings are 1-5 gold eggs followed by a [number in brackets] which indicates how many people supplied their own ratings of the product. If you click on a link to details about a product, then you can read customer reviews about the product by clicking on the "Customer Reviews" tab. At the top of the "Review Summary (read all xxx Reviews, write a review)" you can click on the "read all xxx reviews" link to read 'em all if you wish.


Regarding "overclocking "...

If you don't know, then I strongly suspect you have not overclocked. (Good! ) We'll just leave that alone.

I expect the free version of EVEREST I linked above will suffice. I am not familiar with sensorview.

I'm curious about what EVEREST's sensors display immediately after a cold boot after being off for awhile (or while the computer has been idle for awhile) compared to their readings after you have been doing some heavy gaming for 15 or 20 minutes. If you're so inclined, please paste that information in a follow-up post.

Thanks. I doubt that is a cause for concern. I have seen similar RAM numbers elsewhere (when I searched Dell for "DV051 "). Perhaps a small portion of your RAM is reserved and/or hidden.

 

I forgot to mention something in my first post, and it just occurred to me that it might help..

When I first started getting these errors, I had an Intel express chipset, pretty basic, but just barely met the requirements for playing WoW. I got my first bsod while installing the game and then the patches. After everything was installed correctly, I was able to play the game for about an hour then it crashed. Next time I played for half an hour or so, it crashed. Then from that point, as soon as I loaded my character, it would crash. Updated drivers, etc. then bought a totally new card, the radeon one, and was able to play WoW for several hours no problem. Then the time I was able to stay on without it crashing decreased, and now I don't even bother playing on that computer because I'm afraid it will crash. If this changes anything, then sorry I didn't post it before, and if not then good.

 

I too, would concentrate on that PSU situation. I would not put anything less than a 350 Watt in a P4 based computer and I use that as only a starting base. I have enough power supply units to swap and test.
http://www.dellcommunity.com/suppor...ghw&message.id=115784&query.id=377353#M115784

Something I note

I have a P4 with 1GB RAM, Page File Used (dxdiag) is 200MB. Something appears to be making the system utilise Page File. When you startup, go to Task Manager -> Performance Tab and watch Physical Memory -> Available and the Page File Usage History. Keep tracking it as you open programs.
I expect you realise that you cannot open several/many programs and then try running a game with those open. Alternatively, something is running in the background and using a lot of memory (check the Processes tab -> Mem Usage). There may be a program that has a "memory leak ".

Did you remove the Intel software for the built-in graphics when you installed the new card? Check in Control Panel -> Add or Remove Programs.

(mailman) Don't get too tied up in Everest. It will say that the system is OEM. Rather, go into the BIOS/Configuration settings at startup. There should be temperature and voltage readouts there. Check temperatures when you restart after a crash, they may naturally be a little higher after running a game, but you can probably tell if they are unnaturally high (and watch them falling).

Get updated motherboard/chipset drivers from Dell dowloads (and maybe other drivers, but not the Intel graphics if you are not running them). Use the information about the "Service Tag" to help you select downloads.

Just a comment, the computer was not apparently designed to be a major gaming machine. To make it so, seems you will need to upgrade...graphics...then power...then...

Edit: don't take that as a harsh comment, I have had to wrestle with it many times myself, that is, how far do you need to go with upgrading.

Find out what is causing that Page File usage.

Matt

 

Hi, Matt! Thanks for putting your eyes on this thread!

Yeah...I'm still trying to feel out the usefulness of Everest. I know Everest's temperature readings often don't match the BIOS readings so I don't have any faith in Everest's accuracy any more. However, I thought Everest's differences in temperature (between fresh boot and after heavy gaming) might be more accurate though. Hmmmm, maybe not.

 

Hello mailman,
What I do is make certain that the readouts in Everest match those in the BIOS. I compare the BIOS readings to when I reach the desktop and/or check the Everest readings then reboot and check in the BIOS.

The system needs a good set of chipset drivers to read the sensors correctly. With OEM manufacturers, they may have proprietary drivers and a minimal BIOS. The Everest people (Lavalays) I think need to get a license to able to use them and that may be why they ask you to buy the program. Some OEM machines do not have sensor readouts.

If you are using Everest, I suggest verifying the readouts. I reckon it is still a great program, but would not take the readings on face value.

Matt

 

Hello everyone,

Sorry for the delay in any updates. But I did just try playing WoW and monitored the temperatures with sensorview. When my computer was idle, nothing going on, it was at 60°C/140°F. After 15 minutes of gaming, the temperature did not change, and after 30 minutes, the temperature went down to 58°C/137°F. I went and opened itunes and played my music in the background, and temperatures did not change for another 30 minutes. Then the game crashed, 0xD1 error with usbuhci.sys being said to cause the error. So I was able to play for one hour, half of that time with itunes running in the back. I'll post dump data in the next post.

(I have not been able to run any memory tests yet. I still need to figure out how to make my computer boot on a CD )

EDIT: The minidump was another "Mini Kernel Dump does not contain driver list" so I'm not sure if the dump data would be helpful or not. And I can't seem to remember how to create a log after opening the dump in windows debug :/

 

You are running Itunes at the same time as the game.

If your system is running 630MB of pagefile, I expect you have enough programs open for around 1600MB of memory (1GB of RAM + 600Mb of pagefile, pagefile should run on a "baseline" of maybe 150 - 200MB and only need to increased when physical memory is depleted). You could increase your RAM from 1GB to 2GB, but unless you found the reason, you could just fill that up as well.

Look at what might be overloading the memory (you seem to have Norton Internet Security installed which a lot of people would point the finger at, Itunes is primarily built for Mac computers).

There is troubleshooting here:
http://us.blizzard.com/support/article.xml?articleId=21020
and I would suggest paying close attention to the "Close background applications" section.

My guess:
The system, and particularly the memory, is being overloaded. If you want to run many applications at once, get a more powerful computer.

Matt

 

Thanks for your reply,

I tried the game again today, in windowed mode too, and now I cannot get past the loading screen to the game (I can log in and select a character, but when the game loads it crashes immediately). Once again, the minidumps seem to be taken incorrectly because it has the "Mini Kernel Dump does not contain driver list" message. Before replacing the video card, I had tried running the game with no background applications and it didn't help, but I'll try it again tonight. I understand that I do not have the ideal computer for gaming, or running several things at once, but the game runs fine on my mom's laptop which isn't a much more, if at all, powerful computer. I'm hoping I can solve this problem without having to buy an entirely new computer, because that would just be a drag.