XP Crashing, I have no Idea what is going on...

The problem occurs when the user is using Outlook 2003. The PC has had the operating system reinstalled, I have checked the RAM, The Hard Drive and even replaced a scanner. I cannot find the root cause of the issue and I have been using my google-fu to the best of my abilities and as far as I can tell I am the only person in the world who as either had this problem or cannot figure it out. I have here is the dump check analysis. Any assistance that you can offer would be greatly appreciated.

Opened log file 'c:\debuglog.txt'

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


Loading Dump File [c:\Gord_Minidump\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Tue Jul 10 13:20:26.109 2007 (GMT-4)
System Uptime: 1 days 1:55:34.803
Loading Kernel Symbols
..............................................................................................................................................
Loading User Symbols

Loading unloaded module list
.................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 0, f79acac4, f79ac7c0}

Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_FdoRemoveDevice+ac )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: f79acac4, Exception Record Address
Arg4: f79ac7c0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

FAULTING_IP:
+0
00000000 ?? ???

EXCEPTION_RECORD: f79acac4 -- (.exr fffffffff79acac4)
.exr fffffffff79acac4
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT: f79ac7c0 -- (.cxr fffffffff79ac7c0)
.cxr fffffffff79ac7c0
eax=85c65030 ebx=00000000 ecx=00000001 edx=85a530c0 esi=85c650e8 edi=86cc6d50
eip=00000000 esp=f79acb8c ebp=f79acbb8 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210286
00000000 ?? ???
.cxr
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

READ_ADDRESS: 00000000

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f77b56ff to 00000000

FAILED_INSTRUCTION_ADDRESS:
+0
00000000 ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f79acb88 f77b56ff 00000000 68627375 70646f52 0x0
f79acbb8 f77bc661 85c65030 86cc6d50 85a53008 usbhub!USBH_PdoRemoveDevice+0x41
f79acbd8 f77b5952 85c650e8 85a53008 00000002 usbhub!USBH_PdoPnP+0x5b
f79acbfc f77b31d8 01c650e8 85a53008 f79acc30 usbhub!USBH_PdoDispatch+0x5a
f79acc0c 804e13d9 85c65030 85a53008 86cb1c80 usbhub!USBH_HubDispatch+0x48
f79acc1c f78c3db4 86cb1bc8 86cb1c80 85a53008 nt!IopfCallDriver+0x31
f79acc30 f78c5980 86cb1bc8 85a53008 85a530e4 USBSTOR!USBSTOR_FdoRemoveDevice+0xac
f79acc48 804e13d9 86cb1bc8 85a53008 f79accd4 USBSTOR!USBSTOR_Pnp+0x4e
f79acc58 8059a5c6 85c65030 85c65030 00000002 nt!IopfCallDriver+0x31
f79acc84 805b7a56 86cb1bc8 f79accb0 00000000 nt!IopSynchronousCall+0xb7
f79accd8 8050f161 85c65030 00000002 00000000 nt!IopRemoveDevice+0x93
f79acd00 805b8a7e e16b3a40 00000018 e1d78800 nt!IopRemoveLockedDeviceNode+0x160
f79acd18 805b7d2c 85baec80 00000002 e1d78800 nt!IopDeleteLockedDeviceNode+0x34
f79acd4c 805b8f68 85c65030 02d78800 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
f79acd7c 804e23b5 86cc6388 00000000 86fc2da8 nt!IopDelayedRemoveWorker+0x4b
f79acdac 80574128 86cc6388 00000000 00000000 nt!ExpWorkerThread+0xef
f79acddc 804ec781 804e22f1 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
USBSTOR!USBSTOR_FdoRemoveDevice+ac
f78c3db4 ff760c push dword ptr [esi+0Ch]

SYMBOL_STACK_INDEX: 6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBSTOR

IMAGE_NAME: USBSTOR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d6c

SYMBOL_NAME: USBSTOR!USBSTOR_FdoRemoveDevice+ac

STACK_COMMAND: .cxr 0xfffffffff79ac7c0 ; kb

FAILURE_BUCKET_ID: 0x7E_NULL_IP_USBSTOR!USBSTOR_FdoRemoveDevice+ac

BUCKET_ID: 0x7E_NULL_IP_USBSTOR!USBSTOR_FdoRemoveDevice+ac

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

eax=f77f913c ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=8053738a esp=f79ac5b4 ebp=f79ac5cc iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00200286
nt!KeBugCheckEx+0x1b:
8053738a 5d pop ebp
ChildEBP RetAddr Args to Child
f79ac5cc 80633755 0000007e c0000005 00000000 nt!KeBugCheckEx+0x1b (FPO: [Non-Fpo])
f79ac5e8 8060381d f79ac610 804e2f39 f79ac618 nt!PspUnhandledExceptionInSystemThread+0x1a (FPO: [Non-Fpo])
f79acddc 804ec781 804e22f1 00000001 00000000 nt!PspSystemThreadStartup+0x5a (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start end module name
804d7000 806fd000 nt ntkrnlmp.exe Wed Feb 28 04:08:32 2007 (45E54690)
806fd000 8071dd00 hal halmacpi.dll Wed Aug 04 01:59:09 2004 (41107B2D)
a73b8000 a73e2180 kmixer kmixer.sys Wed Jun 14 04:47:45 2006 (448FCD31)
a7483000 a74a6000 Fastfat Fastfat.SYS Wed Aug 04 02:14:15 2004 (41107EB7)
a7ae9000 a7b0b080 RDPWD RDPWD.SYS Thu Jun 09 19:52:39 2005 (42A8D647)
a7f9a000 a7fae400 wdmaud wdmaud.sys Wed Jun 14 05:00:44 2006 (448FD03C)
a803f000 a804dd80 sysaudio sysaudio.sys Wed Aug 04 02:15:54 2004 (41107F1A)
a822f000 a82497c0 naiavf5x naiavf5x.sys Tue Nov 02 13:32:39 2004 (4187C4B7)
a8322000 a8324080 EntDrv51 EntDrv51.sys Tue Oct 05 19:23:52 2004 (41632D08)
a865a000 a86ab480 srv srv.sys Mon Aug 14 06:34:39 2006 (44E051BF)
a86d4000 a8714280 HTTP HTTP.sys Thu Mar 16 20:33:09 2006 (441A03C5)
a8765000 a8791400 mrxdav mrxdav.sys Wed Aug 04 02:00:49 2004 (41107B91)
a88ba000 a88c33c0 ATNT40K ATNT40K.SYS Tue Jul 26 20:19:20 2005 (42E6D308)
a8a12000 a8a21000 DgiVecp DgiVecp.sys Mon May 17 09:04:14 2004 (40A8B84E)
a8a7e000 a8a81280 ndisuio ndisuio.sys Wed Aug 04 02:03:10 2004 (41107C1E)
a8a8a000 a8aa27e0 tfsnudfa tfsnudfa.sys Wed Aug 06 12:45:19 2003 (3F31309F)
a8aa3000 a8abaee0 tfsnudf tfsnudf.sys Wed Aug 06 12:44:17 2003 (3F313061)
a8abb000 a8acf520 tfsnifs tfsnifs.sys Wed Aug 06 12:44:07 2003 (3F313057)
aadb8000 aadc07e0 tfsncofs tfsncofs.sys Wed Aug 06 12:44:38 2003 (3F313076)
aadc8000 aadd1540 drvnddm drvnddm.sys Fri Jun 20 19:55:12 2003 (3EF39EE0)
aae10000 aae27480 dump_atapi dump_atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
aae28000 aae96a00 mrxsmb mrxsmb.sys Fri May 05 05:41:42 2006 (445B1DD6)
aae97000 aaec1a00 rdbss rdbss.sys Fri May 05 05:47:55 2006 (445B1F4B)
aaec2000 aaee3d00 afd afd.sys Wed Aug 04 02:14:13 2004 (41107EB5)
aaef8000 aaefb760 tfsnopio tfsnopio.sys Wed Aug 06 12:44:47 2003 (3F31307F)
aaf0c000 aaf33c00 netbt netbt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
aaf34000 aaf54f00 ipnat ipnat.sys Wed Sep 29 18:28:36 2004 (415B3714)
aaf55000 aafacd80 tcpip tcpip.sys Thu Apr 20 07:51:47 2006 (444775D3)
aafad000 aafbf400 ipsec ipsec.sys Wed Aug 04 02:14:27 2004 (41107EC3)
bf800000 bf9c2180 win32k win32k.sys Thu Mar 08 08:47:34 2007 (45F013F6)
bf9c3000 bf9d4580 dxg dxg.sys Wed Aug 04 02:00:51 2004 (41107B93)
bf9d5000 bfa18000 ati2dvag ati2dvag.dll Tue Aug 22 21:53:30 2006 (44EBB51A)
bfa18000 bfa5f000 ati2cqag ati2cqag.dll Tue Aug 22 21:14:38 2006 (44EBABFE)
bfa5f000 bfaa5000 atikvmag atikvmag.dll Tue Aug 22 21:21:15 2006 (44EBAD8B)
bfaa5000 bfcef6c0 ati3duag ati3duag.dll Tue Aug 22 21:38:43 2006 (44EBB1A3)
bfcf0000 bff54fa0 ativvaxx ativvaxx.dll Tue Aug 22 21:33:45 2006 (44EBB079)
bff5a000 bff5c600 scddUtil scddUtil.DLL Wed Nov 23 14:45:11 2005 (4384C6C7)
f6e05000 f6e07900 Dxapi Dxapi.sys Fri Aug 17 16:53:19 2001 (3B7D843F)
f6e60000 f6e93200 update update.sys Wed Aug 04 01:58:32 2004 (41107B08)
f6e94000 f6ec4100 rdpdr rdpdr.sys Wed Aug 04 02:01:10 2004 (41107BA6)
f6ec5000 f6ed5e00 psched psched.sys Wed Aug 04 02:04:16 2004 (41107C60)
f6efe000 f6f14680 ndiswan ndiswan.sys Wed Aug 04 02:14:30 2004 (41107EC6)
f6f15000 f6f28900 parport parport.sys Wed Aug 04 01:59:04 2004 (41107B28)
f6f29000 f6f50c00 e100b325 e100b325.sys Mon Jun 13 16:58:01 2005 (42ADF359)
f6f51000 f6f70b80 ctsfm2k ctsfm2k.sys Sun Sep 21 20:48:04 2003 (3F6E46C4)
f6f71000 f6f9c8e0 ctoss2k ctoss2k.sys Sun Sep 21 20:47:37 2003 (3F6E46A9)
f6f9d000 f6fc0980 portcls portcls.sys Wed Aug 04 02:15:47 2004 (41107F13)
f6fc1000 f6fe3680 ks ks.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f6fe4000 f7128b80 P16X P16X.sys Mon Sep 22 00:43:04 2003 (3F6E7DD8)
f7129000 f714be80 USBPORT USBPORT.SYS Wed Aug 04 02:08:34 2004 (41107D62)
f714c000 f7304000 ati2mtag ati2mtag.sys Tue Aug 22 21:53:13 2006 (44EBB509)
f7304000 f7317780 VIDEOPRT VIDEOPRT.SYS Wed Aug 04 02:07:04 2004 (41107D08)
f7338000 f733bc80 mssmbios mssmbios.sys Wed Aug 04 02:07:47 2004 (41107D33)
f7371000 f738b580 Mup Mup.sys Wed Aug 04 02:15:20 2004 (41107EF8)
f738c000 f73b8a80 NDIS NDIS.sys Wed Aug 04 02:14:27 2004 (41107EC3)
f73b9000 f7445480 Ntfs Ntfs.sys Wed Aug 04 02:15:06 2004 (41107EEA)
f7446000 f745c780 KSecDD KSecDD.sys Wed Aug 04 01:59:45 2004 (41107B51)
f745d000 f7471240 drvmcdb drvmcdb.sys Thu Jul 31 20:51:10 2003 (3F29B97E)
f7472000 f7483f00 sr sr.sys Wed Aug 04 02:06:22 2004 (41107CDE)
f7484000 f74a3780 fltmgr fltmgr.sys Mon Aug 21 05:14:57 2006 (44E97991)
f74a4000 f74bb480 atapi atapi.sys Wed Aug 04 01:59:41 2004 (41107B4D)
f74bc000 f74e1700 dmio dmio.sys Wed Aug 04 02:07:13 2004 (41107D11)
f74e2000 f7500880 ftdisk ftdisk.sys Fri Aug 17 16:52:41 2001 (3B7D8419)
f7501000 f7511a80 pci pci.sys Wed Aug 04 02:07:45 2004 (41107D31)
f7512000 f753fd80 ACPI ACPI.sys Wed Aug 04 02:07:35 2004 (41107D27)
f7561000 f7569c00 isapnp isapnp.sys Fri Aug 17 16:58:01 2001 (3B7D8559)
f7571000 f757b500 MountMgr MountMgr.sys Wed Aug 04 01:58:29 2004 (41107B05)
f7581000 f758dc80 VolSnap VolSnap.sys Wed Aug 04 02:00:14 2004 (41107B6E)
f7591000 f7599e00 disk disk.sys Wed Aug 04 01:59:53 2004 (41107B59)
f75a1000 f75ad200 CLASSPNP CLASSPNP.SYS Wed Aug 04 02:14:26 2004 (41107EC2)
f75b1000 f75bb580 agp440 agp440.sys Wed Aug 04 02:07:40 2004 (41107D2C)
f75d1000 f75d9700 wanarp wanarp.sys Wed Aug 04 02:04:57 2004 (41107C89)
f75e1000 f75e9700 netbios netbios.sys Wed Aug 04 02:03:19 2004 (41107C27)
f7611000 f7619880 Fips Fips.SYS Fri Aug 17 21:31:49 2001 (3B7DC585)
f7661000 f7670900 Cdfs Cdfs.SYS Wed Aug 04 02:14:09 2004 (41107EB1)
f76c1000 f76c9a00 processr processr.sys Wed Aug 04 01:59:14 2004 (41107B32)
f76d1000 f76dfb80 drmk drmk.sys Wed Aug 04 02:07:54 2004 (41107D3A)
f76e1000 f76ede00 i8042prt i8042prt.sys Wed Aug 04 02:14:36 2004 (41107ECC)
f76f1000 f7700d80 serial serial.sys Wed Aug 04 02:15:51 2004 (41107F17)
f7701000 f770d180 cdrom cdrom.sys Wed Aug 04 01:59:52 2004 (41107B58)
f7711000 f771f080 redbook redbook.sys Wed Aug 04 01:59:34 2004 (41107B46)
f7721000 f772b380 imapi imapi.sys Wed Aug 04 02:00:12 2004 (41107B6C)
f7731000 f773d880 rasl2tp rasl2tp.sys Wed Aug 04 02:14:21 2004 (41107EBD)
f7741000 f774b200 raspppoe raspppoe.sys Wed Aug 04 02:05:06 2004 (41107C92)
f7751000 f775cd00 raspptp raspptp.sys Wed Aug 04 02:14:26 2004 (41107EC2)
f7761000 f7769900 msgpc msgpc.sys Wed Aug 04 02:04:11 2004 (41107C5B)
f7771000 f777af00 termdd termdd.sys Wed Aug 04 01:58:52 2004 (41107B1C)
f7781000 f778a480 NDProxy NDProxy.SYS Fri Aug 17 16:55:30 2001 (3B7D84C2)
f77b1000 f77bf100 usbhub usbhub.sys Wed Aug 04 02:08:40 2004 (41107D68)
f77d1000 f77df460 mvstdi5x mvstdi5x.sys Thu Oct 07 12:35:49 2004 (41657065)
f77e1000 f77e7200 PCIIDEX PCIIDEX.SYS Wed Aug 04 01:59:40 2004 (41107B4C)
f77e9000 f77ed900 PartMgr PartMgr.sys Fri Aug 17 21:32:23 2001 (3B7DC5A7)
f77f1000 f77f5de0 PxHelp20 PxHelp20.sys Wed Jan 26 20:32:51 2005 (41F844C3)
f7801000 f7805a80 Msfs Msfs.SYS Wed Aug 04 02:00:37 2004 (41107B85)
f7829000 f7830880 Npfs Npfs.SYS Wed Aug 04 02:00:38 2004 (41107B86)
f7839000 f783f500 usbprint usbprint.sys Wed Aug 04 02:01:23 2004 (41107BB3)
f7851000 f7855500 watchdog watchdog.sys Wed Aug 04 02:07:32 2004 (41107D24)
f78b1000 f78b7420 tfsnboio tfsnboio.sys Wed Aug 06 12:44:20 2003 (3F313064)
f78c1000 f78c7780 USBSTOR USBSTOR.SYS Wed Aug 04 02:08:44 2004 (41107D6C)
f78f9000 f78ff000 kbdclass kbdclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7901000 f7906a00 mouclass mouclass.sys Wed Aug 04 01:58:32 2004 (41107B08)
f7909000 f790e000 usbuhci usbuhci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7911000 f7917800 usbehci usbehci.sys Wed Aug 04 02:08:34 2004 (41107D62)
f7919000 f7920000 fdc fdc.sys unavailable (FFFFFFFE)
f7921000 f7925a80 point32 point32.sys Thu May 15 19:29:51 2003 (3EC422EF)
f7929000 f792d880 TDI TDI.SYS Wed Aug 04 02:07:47 2004 (41107D33)
f7931000 f7935580 ptilink ptilink.sys Fri Aug 17 16:49:53 2001 (3B7D8371)
f7939000 f793d080 raspti raspti.sys Fri Aug 17 16:55:32 2001 (3B7D84C4)
f7941000 f7945300 omci omci.sys Mon Nov 04 18:05:02 2002 (3DC6FD1E)
f7951000 f7956000 flpydisk flpydisk.sys Wed Aug 04 01:59:24 2004 (41107B3C)
f7959000 f795e500 TDTCP TDTCP.SYS Wed Aug 04 01:58:52 2004 (41107B1C)
f7961000 f7966a80 ssrtln ssrtln.sys Mon Jul 14 14:28:21 2003 (3F12F645)
f7969000 f796e200 vga vga.sys Wed Aug 04 02:07:06 2004 (41107D0A)
f7971000 f7974000 BOOTVID BOOTVID.dll Fri Aug 17 16:49:09 2001 (3B7D8345)
f7a09000 f7a0b280 rasacd rasacd.sys Fri Aug 17 16:55:39 2001 (3B7D84CB)
f7a19000 f7a1bf00 ws2ifsl ws2ifsl.sys Fri Aug 17 16:55:58 2001 (3B7D84DE)
f7a1d000 f7a20b00 usbscan usbscan.sys Wed Aug 04 01:58:44 2004 (41107B14)
f7a3d000 f7a3f980 gameenum gameenum.sys Wed Aug 04 02:08:20 2004 (41107D54)
f7a41000 f7a44c80 serenum serenum.sys Wed Aug 04 01:59:06 2004 (41107B2A)
f7a4d000 f7a4f580 ndistapi ndistapi.sys Fri Aug 17 16:55:29 2001 (3B7D84C1)
f7a61000 f7a62b80 kdcom kdcom.dll Fri Aug 17 16:49:10 2001 (3B7D8346)
f7a63000 f7a64100 WMILIB WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7a65000 f7a66700 dmload dmload.sys Fri Aug 17 16:58:15 2001 (3B7D8567)
f7a8d000 f7a8e300 kbstuff5 kbstuff5.sys Wed Nov 23 14:44:23 2005 (4384C697)
f7a99000 f7a9a5c0 sscdbhk5 sscdbhk5.sys Mon Jul 14 14:28:38 2003 (3F12F656)
f7a9b000 f7a9c100 swenum swenum.sys Wed Aug 04 01:58:41 2004 (41107B11)
f7a9d000 f7a9e280 USBD USBD.SYS Fri Aug 17 17:02:58 2001 (3B7D8682)
f7a9f000 f7aa1000 i2omgmt i2omgmt.SYS Wed Aug 04 02:00:50 2004 (41107B92)
f7aa1000 f7aa2f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 16:49:37 2001 (3B7D8361)
f7aa3000 f7aa4080 Beep Beep.SYS Fri Aug 17 16:47:33 2001 (3B7D82E5)
f7aa5000 f7aa6080 mnmdd mnmdd.SYS Fri Aug 17 16:57:28 2001 (3B7D8538)
f7aa7000 f7aa8080 RDPCDD RDPCDD.sys Fri Aug 17 16:46:56 2001 (3B7D82C0)
f7aad000 f7aaea80 ParVdm ParVdm.SYS Fri Aug 17 16:49:49 2001 (3B7D836D)
f7aaf000 f7ab0100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 17:07:23 2001 (3B7D878B)
f7ad3000 f7ad4100 PfModNT PfModNT.sys Wed Dec 15 23:14:08 1999 (38586710)
f7afd000 f7afe8a0 tfsnpool tfsnpool.sys Wed Aug 06 12:44:09 2003 (3F313059)
f7b29000 f7b29d00 pciide pciide.sys Fri Aug 17 16:51:49 2001 (3B7D83E5)
f7b5b000 f7b5bc00 audstub audstub.sys Fri Aug 17 16:59:40 2001 (3B7D85BC)
f7b77000 f7b77b80 Null Null.SYS Fri Aug 17 16:47:39 2001 (3B7D82EB)
f7b8d000 f7b8d880 tfsndres tfsndres.sys Wed Aug 06 12:45:28 2003 (3F3130A8)
f7b8e000 f7b8efe0 tfsndrct tfsndrct.sys Wed Aug 06 12:44:45 2003 (3F31307D)
f7c17000 f7c17d00 dxgthk dxgthk.sys Fri Aug 17 16:53:12 2001 (3B7D8438)
f7ca6000 f7ca6840 idisw2km idisw2km.sys Wed Nov 23 14:45:10 2005 (4384C6C6)

Unloaded modules:
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a73b8000 a73e3000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a74a6000 a74d1000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a7f4c000 a7f77000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7bb0000 f7bb1000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a801f000 a802c000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a7f77000 a7f9a000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
a802f000 a803d000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7abd000 f7abf000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7601000 f760c000 p3.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f75f1000 f75fa000 intelppm.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f7959000 f795e000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f7a01000 f7a04000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Hi T

The only thing that hasn't changed is the hardware.

Not practical to use outlook in safe mode but test it anyway to see if in fact outlook does or does not have the issue.

Try this. Even tho you have tested the memory, that can slip by some test programs so change the memory and test for problen. If you have 2 sticks of ram try them 1 at a time.

No joy then reset the Bios.
No joy then.. Download and update the motherboard chipset.

JJ

 

Thank you for the input. I realize now that I didn't specify that this is an intermittent issue, so any fix I test has to be tested for at least two weeks if not longer to be doubly sure that I am not left standing on an aircraft carrier with a banner that says "Mission Accomplished "...

 

I'm a rooke when reading Dump logs ...

First impression appears to relate to possible USB and or CD drives issue ...
see MSDN Identifiers Generated by USBSTOR.SYS
First check in device manager under USB ports and optical drives for problems ... then bounce over to Event Manager for any error issues. Also a Google on "USBSTOR.SYS" brings up a lot of hits.

 

I'm not a qualified dump reader either but it sure looks like there could be a flash drive or something plugged into a USB port that is causing a problem. As to your Outlook, if you go to add/remove programs in the control panel, you can repair your Office installation. You may also have a file store that has become too large for Outlook to manage. Check out the size of your .pst files and post those findings.

One can not rule out malware at this point either but I'd try a few things like the logs Dennis mentioned before going too far in any one direction. As to the pulling memory, resetting BIOS suggestion - I don't consider that at all applicable to your problem description.

 

You guys rock.

No flash drives. As for the repairing of the Office install, the problem is reoccurring even after a full format and OS re-install, therefore the office repair would not be the answer. As far as simply Googling usbstor.sys, most of the hits I found with any merit pertained more to making XP work off a CD or USB drive than anything I needed. I have created a New PST file due to the Size of the old one exceeding 1.5 GB. I just hope that was the problem. Again considering that the issue is more that a week or even a month old I have a feeling that it is not the answer. Thank you for all of the idea's. I just wish that this had a little bit more instant gratification than waiting a month and seeing if it happened again...

 

Did you have a chance to check in Device Manager / Universal Serial Bus Controllers (USB) and DVD/CD-ROM drives for any problems. Also in Event Viewer under System and Application for errors. The problem may not be related to "using the device" (USB or optical devices), but rather the presence and a possible driver issue. When in Event Viewer, if any error(s) are stated, they are date / time stamped .. does it date tie to crash/dump logs?

 

Nothing in the event viewer that stood out...

 

.... and Device Manager stated no problems for USB controller -(and)- Optical drives?

 

Nope...

 

I sure hope you do not have the same pain in backside problem that I did a few years ago. But it does sound familiar. It took me a long time and a LOT OF keeping track of what and when things were done.
Bottom line:
It turned out to be a conflict when a certain two programs were run in a certain order. A then B would be toruble but B then A would not. Or of I restarted the machine between A & B then no problem.

BillyBob

 

T-Bone:

First an apology - As much as I have tried, I can't be exactly sure of the cause because I just can't remember, however, I ran into an Outlook problem about 3-4 months ago that beat me up pretty good. It involved a corrupt file that the user had somehow managed to import into their data stores including Outlook.pst, archive.pst and extend.dat. No matter what I did, everything worked fine until I moved their saved Outlook stuff (those three files) back into place. KaBoom - total lockup each and every time. If I replaced the files with clean ones (not corrupted) - no problem. And, if I replaced the clean ones with their own files again - KaBoom - lockup. I did manage to get this corrected but it was through a lot of trial and error and I can't remember just what unlocked the puzzle. Perhaps this will be enough of a lead for someone else to pick up the ball and run with it. In the meantime, I'll keep scratching my head with the hope that some semblance of a memory comes back re: this particular issue. Although the issue I encountered was not intermittent, it may be the result of a similar cause.

Good Luck - keep us posted.

 

Why a USB driver might be linked to Outlook I wouldn't know The USB controller is part of the motherboard chipset. The chipset drivers are installed by Service Pack 2 (2004). In the last year or so, most chipset manufacturers have released updated drivers. Your chipset model will be listed in the specifications for the computer/motherboard. If you keep getting USB driver related dumps, find updated chipset drivers.

USB can only supply a limited amount of power. You cannot use more than one or two power hungry USB devices without using self-powered hubs. I would hope not, but just maybe, the USB system has been overloaded at some stage.

The USB ports at the back of the computer are connected directly to the motherboard. Any ports at the front of the computer have a cable connection to the motherboard. There is always a possiblity of a bad connection with those cables.

You will need to see what the next and future dumps say. We might concentrate on USB when there is a much more general problem (eg. have you cleaned all the dust out of the case in the recent past?). There should be temperature and voltage readouts in the BIOS/Setup settings at startup.

Matt

 

As to the pulling memory, resetting BIOS suggestion - I don't consider that at all applicable to your problem description.

I noticed the USB issue in the dump but also that you had reinstalled the OS and application multiple times and that is always related to outlook.

Since you have already reinstalled everything more than once. The only thing that hasn't changed is the hardware.

It is a waste of time doing it again.

I reccommend resetting the BIOs and updating the BIOS and Chipset if possible.

If not that it will be a USB power level problem or an actual bad or weak USB chipset.

Find out if this user backs up Outlook to a USB drive, and how often.

JJ

 

My first thought was a USB drive of some type too. You said there's no flash drive involved, how about a USB hard drive? Another thought though I don't really know if it could cause this or not, would be the printer. If it's USB, perhaps it has to do with Outlook trying to access it? I'm not an expert when it comes to reading dumps either but this one does seem to point to a usb problem of some type.

 

I'm not sure if this is going to be of any help but I pulled this information off of Google. You might want to try stopping the service and seeing what happens.

Also, in search of the elusive USB device we all keep asking about - does this machine have a card reader built in and if yes, could it be running off a USB header? If yes, you might want to try disconnecting it or go into the control panel, then to system, then to hardware, then to device manager and remove all things listed under USB. Reboot and let Windows rediscover all USB ports and devices.

 

I also had a feeling that it could possibly be the USB printer that is involved. As far as USB devices go the user only had A USB mouse, Printer, Scanner and hub plugged in. I am going to be interested to see if the printer is a factor... As far as estranged USB devices go I cannot find any that are being run through as a USB device. You guys are great and appreciate all of the help that you have provided.

 

If the USB hub is a "powered" hub then for sure get the 2 big boys (printer and scanner) on it.

If not powered then don't matter.

Also note the USB Hub may in fact be the problem powered unpowered or not.

So you may want to swap this out with another user to see if it corrrects the problem.

Or if unpowered consider a powered one. They are cheap.

JJ

 

The hub is unpowered and was actually the first thing that I removed. I will have to wait and see if this corrects the issue....

 

I'd call that a very smart move and would almost bet this is contributiing to the problem.

Excellent suggestion in my book.