Blue Screen and DATA DUMP

Thanks in advance.

I've had the BSOD numerous times recently, with various errors, e.g. once with IRQL_... and once with page fault in non page area. This first started when I plugged in my new iPod Shuffle a few weeks ago with USB. I also have FireWire (IEEE 1394) for an older iPod, and DigiDesign recording software (I'm thinking I have some driver conflict, but very unknowledgeable about this stuff). Now, IE, or McAfee, or Firefox will die immediately. Even clicking the start menu will cause an error. I'm in dire straits now, I can't do anything on the machine. Here is the data dump, and any help is greatly appreciated.
If you know how to fix the missing symbols that would be great too.

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:\WINDOWS\Minidump\Mini112706-06.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 Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon Nov 27 18:49:57.765 2006 (GMT-8)
System Uptime: 0 days 0:06:36.466
Loading Kernel Symbols
.....................................................................................................................................................
Loading User Symbols
Loading unloaded module list
............
*** ERROR: Module load completed but symbols could not be loaded for naiavf5x.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {7fffe8, 2, 1, 804e1928}

Probably caused by : naiavf5x.sys ( naiavf5x+11946 )

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

1: 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: 007fffe8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804e1928, address which referenced memory

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


WRITE_ADDRESS: 007fffe8

CURRENT_IRQL: 2

FAULTING_IP:
nt!ObfDereferenceObject+1c
804e1928 f00fc13e lock xadd dword ptr [esi],edi

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from edbe6946 to 804e1928

STACK_TEXT:
f91edbd4 edbe6946 ff709418 ff4711dc ff7e74c8 nt!ObfDereferenceObject+0x1c
WARNING: Stack unwind information not available. Following frames may be wrong.
f91edc04 edbdd177 82d3dedc f91edc48 ff709428 naiavf5x+0x11946
f91edc40 edbd7950 ff7e74c8 ff709428 836daee8 naiavf5x+0x8177
f91edc54 804e13d9 ffbb34c8 ff709418 ff709418 naiavf5x+0x2950
f91edc64 8057c457 ff7e74b0 00000000 00000000 nt!IopfCallDriver+0x31
f91edc9c 8056c78f 007e74c8 00000000 ff7e74b0 nt!IopDeleteFile+0x132
f91edcb8 804e1957 ff7e74c8 00000000 ff8094c4 nt!ObpRemoveObjectRoutine+0xdf
f91edcd0 804f5433 806ffa4c ff809460 806ffaa8 nt!ObfDereferenceObject+0x4c
f91edcfc 804f3aa7 00000001 8055e690 ffa034a8 nt!CcDeleteSharedCacheMap+0xe6
f91edd34 804e67c8 837c41e8 805694c0 837c78b8 nt!CcWriteBehind+0x357
f91edd7c 804e23b5 837c41e8 00000000 837c78b8 nt!CcWorkerThread+0x12f
f91eddac 80574128 837c41e8 00000000 00000000 nt!ExpWorkerThread+0xef
f91edddc 804efc81 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
naiavf5x+11946
edbe6946 c786c400000000000000 mov dword ptr [esi+0C4h],0

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: naiavf5x+11946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: naiavf5x

IMAGE_NAME: naiavf5x.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42ae0eb6

FAILURE_BUCKET_ID: 0xA_W_naiavf5x+11946

BUCKET_ID: 0xA_W_naiavf5x+11946

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

eax=837c78b8 ebx=00800000 ecx=00800000 edx=00000000 esi=007fffe8 edi=ffffffff
eip=804e1928 esp=f91edbcc ebp=f91edc04 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!ObfDereferenceObject+0x1c:
804e1928 f00fc13e lock xadd dword ptr [esi],edi ds:0023:007fffe8=????????
ChildEBP RetAddr Args to Child
f91edbd4 edbe6946 ff709418 ff4711dc ff7e74c8 nt!ObfDereferenceObject+0x1c (FPO: [0,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
f91edc04 edbdd177 82d3dedc f91edc48 ff709428 naiavf5x+0x11946
f91edc40 edbd7950 ff7e74c8 ff709428 836daee8 naiavf5x+0x8177
f91edc54 804e13d9 ffbb34c8 ff709418 ff709418 naiavf5x+0x2950
f91edc64 8057c457 ff7e74b0 00000000 00000000 nt!IopfCallDriver+0x31 (FPO: [0,0,0])
f91edc9c 8056c78f 007e74c8 00000000 ff7e74b0 nt!IopDeleteFile+0x132 (FPO: [Non-Fpo])
f91edcb8 804e1957 ff7e74c8 00000000 ff8094c4 nt!ObpRemoveObjectRoutine+0xdf (FPO: [Non-Fpo])
f91edcd0 804f5433 806ffa4c ff809460 806ffaa8 nt!ObfDereferenceObject+0x4c (FPO: [0,0,0])
f91edcfc 804f3aa7 00000001 8055e690 ffa034a8 nt!CcDeleteSharedCacheMap+0xe6 (FPO: [Non-Fpo])
f91edd34 804e67c8 837c41e8 805694c0 837c78b8 nt!CcWriteBehind+0x357 (FPO: [Non-Fpo])
f91edd7c 804e23b5 837c41e8 00000000 837c78b8 nt!CcWorkerThread+0x12f (FPO: [Non-Fpo])
f91eddac 80574128 837c41e8 00000000 00000000 nt!ExpWorkerThread+0xef (FPO: [Non-Fpo])
f91edddc 804efc81 804e22f1 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
start end module name
804d7000 806fd000 nt ntkrnlmp.exe Tue Mar 01 16:57:27 2005 (42250F77)
806fd000 8071dd00 hal halmacpi.dll Tue Aug 03 22:59:09 2004 (41107B2D)
bf800000 bf9c1180 win32k win32k.sys Wed Oct 05 17:05:44 2005 (43446A58)
bf9c2000 bf9d3580 dxg dxg.sys Tue Aug 03 23:00:51 2004 (41107B93)
bf9d4000 bfd026a0 nv4_disp nv4_disp.dll Fri Oct 17 13:59:54 2003 (3F90584A)
ed86d000 ed86f580 hidusb hidusb.sys Fri Aug 17 14:02:16 2001 (3B7D8658)
ed9f5000 ed9f8a00 kbdhid kbdhid.sys Tue Aug 03 22:58:33 2004 (41107B09)
edbd5000 edbf0f20 naiavf5x naiavf5x.sys Mon Jun 13 15:54:46 2005 (42AE0EB6)
eddc1000 eddc9080 ipfltdrv ipfltdrv.sys Fri Aug 17 13:55:07 2001 (3B7D84AB)
eddf9000 ede4a480 srv srv.sys Mon Aug 14 03:34:39 2006 (44E051BF)
edf73000 edf76da0 PfModNT PfModNT.sys Tue Mar 04 20:19:28 2003 (3E657AD0)
ee141000 ee155400 wdmaud wdmaud.sys Wed Jun 14 02:00:44 2006 (448FD03C)
ee286000 ee2900c0 jsfax jsfax.sys Mon Jun 01 13:54:14 1998 (357314F6)
ee2c6000 ee2d4d80 sysaudio sysaudio.sys Tue Aug 03 23:15:54 2004 (41107F1A)
ee426000 ee43e7e0 tfsnudfa tfsnudfa.sys Wed Aug 06 09:45:19 2003 (3F31309F)
ee43f000 ee456ee0 tfsnudf tfsnudf.sys Wed Aug 06 09:44:17 2003 (3F313061)
ee457000 ee46b520 tfsnifs tfsnifs.sys Wed Aug 06 09:44:07 2003 (3F313057)
ee9a3000 ee9ba480 dump_atapi dump_atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
ee9bb000 eea29a00 mrxsmb mrxsmb.sys Fri May 05 02:41:42 2006 (445B1DD6)
eea2a000 eea54a00 rdbss rdbss.sys Fri May 05 02:47:55 2006 (445B1F4B)
eea55000 eea76d00 afd afd.sys Tue Aug 03 23:14:13 2004 (41107EB5)
eea9f000 eeac6c00 netbt netbt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
eeac7000 eeadab00 MpFirewall MpFirewall.sys Fri Nov 11 13:43:52 2005 (43751098)
eeadb000 eeafbf00 ipnat ipnat.sys Wed Sep 29 15:28:36 2004 (415B3714)
eeafc000 eeb54080 tcpip tcpip.sys Thu Apr 20 05:18:33 2006 (44477C19)
eeb55000 eeb67400 ipsec ipsec.sys Tue Aug 03 23:14:27 2004 (41107EC3)
eeb88000 eeb91540 drvnddm drvnddm.sys Fri Jun 20 16:55:12 2003 (3EF39EE0)
eec28000 eec47ba0 hap16v2k hap16v2k.sys Tue Mar 25 23:32:01 2003 (3E815771)
eec48000 eec67c80 ctac32k ctac32k.sys Thu Feb 20 00:22:35 2003 (3E54904B)
eec68000 eec862a0 ctsfm2k ctsfm2k.sys Thu Feb 20 00:24:32 2003 (3E5490C0)
eec87000 eeca1340 emupia2k emupia2k.sys Thu Feb 20 00:24:43 2003 (3E5490CB)
eeca2000 eed5e2c0 ha10kx2k ha10kx2k.sys Tue Mar 25 23:31:39 2003 (3E81575B)
f7e97000 f7eca200 update update.sys Tue Aug 03 22:58:32 2004 (41107B08)
f7ecb000 f7edbe00 psched psched.sys Tue Aug 03 23:04:16 2004 (41107C60)
f7edc000 f7ef2680 ndiswan ndiswan.sys Tue Aug 03 23:14:30 2004 (41107EC6)
f7ef3000 f7f06900 parport parport.sys Tue Aug 03 22:59:04 2004 (41107B28)
f7f07000 f7f2a800 e100b325 e100b325.sys Tue Mar 04 11:56:25 2003 (3E6504E9)
f7f2b000 f7f55d40 ctoss2k ctoss2k.sys Tue Mar 25 23:32:30 2003 (3E81578E)
f7f56000 f7f79980 portcls portcls.sys Tue Aug 03 23:15:47 2004 (41107F13)
f7f7a000 f7fe91a0 ctaud2k ctaud2k.sys Tue Mar 25 23:33:57 2003 (3E8157E5)
f7fea000 f807eb60 IntelC52 IntelC52.sys Fri Mar 05 11:15:31 2004 (4048D1D3)
f807f000 f81a56a0 IntelC51 IntelC51.sys Fri Mar 05 11:14:39 2004 (4048D19F)
f81a6000 f81c8680 ks ks.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f81c9000 f81ebe80 USBPORT USBPORT.SYS Tue Aug 03 23:08:34 2004 (41107D62)
f81ec000 f81ff780 VIDEOPRT VIDEOPRT.SYS Tue Aug 03 23:07:04 2004 (41107D08)
f8200000 f8334be0 nv4_mini nv4_mini.sys Fri Oct 17 13:54:52 2003 (3F90571C)
f8365000 f8374760 LMouFlt2 LMouFlt2.Sys Wed Dec 17 11:38:27 2003 (3FE0B0B3)
f8375000 f8384900 Cdfs Cdfs.SYS Tue Aug 03 23:14:09 2004 (41107EB1)
f8395000 f839d880 Fips Fips.SYS Fri Aug 17 18:31:49 2001 (3B7DC585)
f83a5000 f83ae980 jsscan jsscan.sys Mon Jun 01 13:54:18 1998 (357314FA)
f83b5000 f83bd3c0 jsmux jsmux.sys Mon Jun 01 13:54:22 1998 (357314FE)
f83c5000 f83d0620 js1284 js1284.sys Mon Jun 01 13:54:21 1998 (357314FD)
f8495000 f8498f00 MODEMCSA MODEMCSA.sys Fri Aug 17 13:57:37 2001 (3B7D8541)
f8b97000 f8b9ac80 mssmbios mssmbios.sys Tue Aug 03 23:07:47 2004 (41107D33)
f8bab000 f8bad580 ndistapi ndistapi.sys Fri Aug 17 13:55:29 2001 (3B7D84C1)
f8bb7000 f8bbac80 serenum serenum.sys Tue Aug 03 22:59:06 2004 (41107B2A)
f8bec000 f8c06580 Mup Mup.sys Tue Aug 03 23:15:20 2004 (41107EF8)
f8c07000 f8c33a80 NDIS NDIS.sys Tue Aug 03 23:14:27 2004 (41107EC3)
f8c34000 f8cc0480 Ntfs Ntfs.sys Tue Aug 03 23:15:06 2004 (41107EEA)
f8cc1000 f8cd7780 KSecDD KSecDD.sys Tue Aug 03 22:59:45 2004 (41107B51)
f8cd8000 f8ce9120 TPkd TPkd.sys Tue Sep 27 08:00:00 2005 (43395E70)
f8cea000 f8cfe240 drvmcdb drvmcdb.sys Thu Jul 31 17:51:10 2003 (3F29B97E)
f8cff000 f8d1e780 fltmgr fltmgr.sys Mon Aug 21 02:14:57 2006 (44E97991)
f8d1f000 f8d36480 atapi atapi.sys Tue Aug 03 22:59:41 2004 (41107B4D)
f8d37000 f8d55880 ftdisk ftdisk.sys Fri Aug 17 13:52:41 2001 (3B7D8419)
f8d56000 f8d66a80 pci pci.sys Tue Aug 03 23:07:45 2004 (41107D31)
f8d67000 f8d94d80 ACPI ACPI.sys Tue Aug 03 23:07:35 2004 (41107D27)
f8db6000 f8dbec00 isapnp isapnp.sys Fri Aug 17 13:58:01 2001 (3B7D8559)
f8dc6000 f8dd0500 MountMgr MountMgr.sys Tue Aug 03 22:58:29 2004 (41107B05)
f8dd6000 f8de2c80 VolSnap VolSnap.sys Tue Aug 03 23:00:14 2004 (41107B6E)
f8de6000 f8deee00 disk disk.sys Tue Aug 03 22:59:53 2004 (41107B59)
f8df6000 f8e02200 CLASSPNP CLASSPNP.SYS Tue Aug 03 23:14:26 2004 (41107EC2)
f8e06000 f8e0eb60 PxHelp20 PxHelp20.sys Wed Aug 09 10:27:31 2006 (44DA1B03)
f8e16000 f8e1f000 DigiFilt DigiFilt.sys Wed Oct 26 00:19:54 2005 (435F2E1A)
f8e26000 f8e30880 sbp2port sbp2port.sys Tue Aug 03 22:59:54 2004 (41107B5A)
f8e36000 f8e44e80 ohci1394 ohci1394.sys Tue Aug 03 23:10:05 2004 (41107DBD)
f8e46000 f8e53000 1394BUS 1394BUS.SYS Tue Aug 03 23:10:03 2004 (41107DBB)
f8e56000 f8e60580 agp440 agp440.sys Tue Aug 03 23:07:40 2004 (41107D2C)
f8ea6000 f8eaed00 intelppm intelppm.sys Tue Aug 03 22:59:19 2004 (41107B37)
f8eb6000 f8ec4220 IntelC53 IntelC53.sys Fri Mar 05 11:13:51 2004 (4048D16F)
f8ec6000 f8ed4b80 drmk drmk.sys Tue Aug 03 23:07:54 2004 (41107D3A)
f8ed6000 f8ee5180 nic1394 nic1394.sys Tue Aug 03 22:58:28 2004 (41107B04)
f8ee6000 f8ef2e00 i8042prt i8042prt.sys Tue Aug 03 23:14:36 2004 (41107ECC)
f8ef6000 f8f05d80 serial serial.sys Tue Aug 03 23:15:51 2004 (41107F17)
f8f06000 f8f12180 cdrom cdrom.sys Tue Aug 03 22:59:52 2004 (41107B58)
f8f16000 f8f24080 redbook redbook.sys Tue Aug 03 22:59:34 2004 (41107B46)
f8f26000 f8f30380 imapi imapi.sys Tue Aug 03 23:00:12 2004 (41107B6C)
f8f36000 f8f42880 rasl2tp rasl2tp.sys Tue Aug 03 23:14:21 2004 (41107EBD)
f8f46000 f8f50200 raspppoe raspppoe.sys Tue Aug 03 23:05:06 2004 (41107C92)
f8f56000 f8f61d00 raspptp raspptp.sys Tue Aug 03 23:14:26 2004 (41107EC2)
f8f66000 f8f6e900 msgpc msgpc.sys Tue Aug 03 23:04:11 2004 (41107C5B)
f8f76000 f8f7ff00 termdd termdd.sys Tue Aug 03 22:58:52 2004 (41107B1C)
f8f96000 f8f9f480 NDProxy NDProxy.SYS Fri Aug 17 13:55:30 2001 (3B7D84C2)
f8fa6000 f8fb4100 usbhub usbhub.sys Tue Aug 03 23:08:40 2004 (41107D68)
f8fc6000 f8fce2e0 LHidUsb LHidUsb.Sys Wed Dec 17 11:38:50 2003 (3FE0B0CA)
f8fd6000 f8fded80 HIDCLASS HIDCLASS.SYS Tue Aug 03 23:08:18 2004 (41107D52)
f8fe6000 f8fee7e0 tfsncofs tfsncofs.sys Wed Aug 06 09:44:38 2003 (3F313076)
f8ff6000 f8ffe700 wanarp wanarp.sys Tue Aug 03 23:04:57 2004 (41107C89)
f9006000 f9014d80 arp1394 arp1394.sys Tue Aug 03 22:58:28 2004 (41107B04)
f9016000 f901e700 netbios netbios.sys Tue Aug 03 23:03:19 2004 (41107C27)
f9036000 f903c200 PCIIDEX PCIIDEX.SYS Tue Aug 03 22:59:40 2004 (41107B4C)
f903e000 f9042900 PartMgr PartMgr.sys Fri Aug 17 18:32:23 2001 (3B7DC5A7)
f904e000 f9054420 tfsnboio tfsnboio.sys Wed Aug 06 09:44:20 2003 (3F313064)
f9066000 f906db80 usbccgp usbccgp.sys Tue Aug 03 23:08:45 2004 (41107D6D)
f90b6000 f90bcca0 jspclcap jspclcap.sys Mon Jun 01 13:54:20 1998 (357314FC)
f90ee000 f90f3000 usbuhci usbuhci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f90f6000 f90fc800 usbehci usbehci.sys Tue Aug 03 23:08:34 2004 (41107D62)
f90fe000 f9103be0 mohfilt mohfilt.sys Fri Mar 05 11:13:37 2004 (4048D161)
f9106000 f910d580 Modem Modem.SYS Tue Aug 03 23:08:04 2004 (41107D44)
f910e000 f910f000 fdc fdc.sys unavailable (00000000)
f9116000 f911c000 kbdclass kbdclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f911e000 f9125000 GEARAspiWDM GEARAspiWDM.sys Mon Aug 07 10:11:27 2006 (44D7743F)
f9126000 f912a880 TDI TDI.SYS Tue Aug 03 23:07:47 2004 (41107D33)
f912e000 f9132580 ptilink ptilink.sys Fri Aug 17 13:49:53 2001 (3B7D8371)
f9136000 f913a080 raspti raspti.sys Fri Aug 17 13:55:32 2001 (3B7D84C4)
f913e000 f9143a00 mouclass mouclass.sys Tue Aug 03 22:58:32 2004 (41107B08)
f9146000 f914a300 omci omci.sys Mon Nov 04 15:05:02 2002 (3DC6FD1E)
f914e000 f9154180 HIDPARSE HIDPARSE.SYS Tue Aug 03 23:08:15 2004 (41107D4F)
f915e000 f9163a80 ssrtln ssrtln.sys Mon Jul 14 11:28:21 2003 (3F12F645)
f9166000 f916b200 vga vga.sys Tue Aug 03 23:07:06 2004 (41107D0A)
f9176000 f917aa80 Msfs Msfs.SYS Tue Aug 03 23:00:37 2004 (41107B85)
f917e000 f9185880 Npfs Npfs.SYS Tue Aug 03 23:00:38 2004 (41107B86)
f919e000 f91a3f00 LHidFlt2 LHidFlt2.Sys Wed Dec 17 11:38:35 2003 (3FE0B0BB)
f91ae000 f91b2500 watchdog watchdog.sys Tue Aug 03 23:07:32 2004 (41107D24)
f91c6000 f91c9000 BOOTVID BOOTVID.dll Fri Aug 17 13:49:09 2001 (3B7D8345)
f924a000 f924d760 tfsnopio tfsnopio.sys Wed Aug 06 09:44:47 2003 (3F31307F)
f925e000 f9260280 rasacd rasacd.sys Fri Aug 17 13:55:39 2001 (3B7D84CB)
f926e000 f9270f00 ws2ifsl ws2ifsl.sys Fri Aug 17 13:55:58 2001 (3B7D84DE)
f928e000 f9290f80 mouhid mouhid.sys Fri Aug 17 13:47:57 2001 (3B7D82FD)
f92a2000 f92a4900 Dxapi Dxapi.sys Fri Aug 17 13:53:19 2001 (3B7D843F)
f92b6000 f92b7b80 kdcom kdcom.dll Fri Aug 17 13:49:10 2001 (3B7D8346)
f92b8000 f92b9100 WMILIB WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f92c8000 f92c9a80 ParVdm ParVdm.SYS Fri Aug 17 13:49:49 2001 (3B7D836D)
f92e8000 f92e9600 ctprxy2k ctprxy2k.sys Thu Feb 20 00:24:16 2003 (3E5490B0)
f92ea000 f92eb5c0 sscdbhk5 sscdbhk5.sys Mon Jul 14 11:28:38 2003 (3F12F656)
f92ec000 f92ed100 swenum swenum.sys Tue Aug 03 22:58:41 2004 (41107B11)
f92f4000 f92f5280 USBD USBD.SYS Fri Aug 17 14:02:58 2001 (3B7D8682)
f92f6000 f92f8000 i2omgmt i2omgmt.SYS Tue Aug 03 23:00:50 2004 (41107B92)
f92f8000 f92f9f00 Fs_Rec Fs_Rec.SYS Fri Aug 17 13:49:37 2001 (3B7D8361)
f92fa000 f92fb080 Beep Beep.SYS Fri Aug 17 13:47:33 2001 (3B7D82E5)
f92fe000 f92ff080 mnmdd mnmdd.SYS Fri Aug 17 13:57:28 2001 (3B7D8538)
f9300000 f9301080 RDPCDD RDPCDD.sys Fri Aug 17 13:46:56 2001 (3B7D82C0)
f930a000 f930b100 dump_WMILIB dump_WMILIB.SYS Fri Aug 17 14:07:23 2001 (3B7D878B)
f9334000 f93358a0 tfsnpool tfsnpool.sys Wed Aug 06 09:44:09 2003 (3F313059)
f937e000 f937ed00 pciide pciide.sys Fri Aug 17 13:51:49 2001 (3B7D83E5)
f93fa000 f93fac00 audstub audstub.sys Fri Aug 17 13:59:40 2001 (3B7D85BC)
f9472000 f9472b80 Null Null.SYS Fri Aug 17 13:47:39 2001 (3B7D82EB)
f947e000 f947e880 tfsndres tfsndres.sys Wed Aug 06 09:45:28 2003 (3F3130A8)
f9480000 f9480fe0 tfsndrct tfsndrct.sys Wed Aug 06 09:44:45 2003 (3F31307D)
f94ea000 f94ead00 dxgthk dxgthk.sys Fri Aug 17 13:53:12 2001 (3B7D8438)

Unloaded modules:
ed869000 ed86d000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ee11e000 ee141000 aec.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f93cc000 f93cd000 drmkaud.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ee0f3000 ee11e000 kmixer.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ee286000 ee293000 DMusic.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ee2a6000 ee2b4000 swmidi.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f937c000 f937e000 splitter.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f8e76000 f8e7f000 processr.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f9026000 f9031000 p3.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f9256000 f925a000 kbdhid.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
f9156000 f915b000 Cdaudio.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
f9252000 f9255000 Sfloppy.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
Closing open log file c:\debuglog.txt

 

Hi,

Windows in crashed at Mcafee Anti Virus Filter. Upgrade Mcafee Anti Virus Filter. However one minidump is insufficient to confirm the culprit. Post more debug report if you have.

 

Got another crash, here is the latest. If you know how to get the symbols, that would be great. I *think* I updated mcafee and ran mcafee technician, with no problems.


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


Loading Dump File [C:\WINDOWS\Minidump\Mini120306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Dec 3 10:24:20.937 2006 (GMT-8)
System Uptime: 0 days 0:15:46.640
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ff5285b0, 0, 804e9df3, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

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

0: kd> .reload /f @ "drmkaud.sys "
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

 

system crashing, hard for me to get this reply in. I updated mcafee, I think, and ran mcafee virtual technician with no issues. also ran system file check. here is latest dump, don't know how to get the symbols:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini120306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Dec 3 10:24:20.937 2006 (GMT-8)
System Uptime: 0 days 0:15:46.640
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
......................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ff5285b0, 0, 804e9df3, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

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

0: kd> .reload /f @ "drmkaud.sys "
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

 

Hi,

You forgot to set the symbolic path

SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

 

well, one more. I ran memtest and got numerous errors in just a few seconds. Any other tests I ran came back fine. I think that means I need to replace my ram. On a side note, I saw some stuff on the web that a faulty keyboard ground could have caused some of my errors, which I believe happened, b/c I heard some 'clicking' when I was playing my guitar and touching the keyboard (both electric devices). Not sure if this could have created a ram problem, not that knowledgeable about this; but I'm going to go ahead and replace my ram.
Any thoughts welcome.

 

If memtest reports errors, the ram is bad. Maybe the memory slot is bad or the dust inside memory slot. Clean the dust inside the memory slot and reseat the memory module. Re-run memtest. If it still crashes, replace the ram.

 

Thanks for your help. Yesterday, after taking the machine apart and dusting it (without removing anything except the side panel and all the cables), I ran a test that came with the Dell, which indicated that the RAM was fine (in contrast to memtest). {Surprise that their own test says everything is ok!}

I'll follow your instructions and re-run memtest (maybe the dusting was enough), and if it crashes, then re-seat & redust, run again, and if it crashes then replace.

Thanks again so much for your help.

 

ok, took out the ram cards and dusted. put them back in and I keep getting the bsod. so it sounds like I may need to replace them. EXACTLY which memtest do you recommend? I got one from hcidesign website. and it looks like Microsoft has one too. Just want to make sure I'm properly testing.

thanks again so much,
Jon

 

Hi, vaughanie. Welcome to Windows BBS!

I have seen a few RAM testers recommended here over the last several months:

• Microsoft's Windows Memory Diagnostic
• Memtest86
• DocMem

Unfortunately, opinions on these RAM testers vary.

 

thanks for your help. I struggled yesterday with the MS memory diagnostic, but could not get the computer to realize that it could boot from the CD I burned the diag to. Any advice on how to make a 'bootable' CD?

 

Try Prime 95. It test the memory at Windows Environment and not stand alone ebvironment.

http://www.mersenne.org/freesoft.htm

 

ok,I ran the windows memory diagnostic (finally created a bootable disk!), and it said I had errors on Channel B DIMM 0. I then swapped the locations of the two RAM pieces and re-ran the test. Got the same error. Should that happen, or would you expect it to say Channel A on the second test? I was trying to make sure it was the RAM, and not the connection to the RAM (motherboard??). Also, how does one figure out which physical piece in this Dell 4600 is Channel B, or A? There are 4 slots, 2 white, 2 black. Does it matter which the RAM are in? should I just try to move the RAM pieces around to see if I keep getting the same error?

Thanks for all your help.

 

alright, finally solved the problem with the help of WindowsBBS.
Thanks to all who responded, without you this would not have been possible as I would have been lost. You saved me a lot of time and a lot of headaches!!

thanks again.

 

Hi, vaughanie.

I'm glad you solved your problem.

Please let us know what you did to fix it so others who have the same or similar problem and run across this thread will benefit.

 

To recap:
I had the BSOD with all sorts of errors, in fact very different ones, so it was hard to pin down what was wrong. If you read the thread, some of those in the know thought it could be the ram. I tried Dell's PC diagnostics and it said the whole system was fine. I downloaded the windows memory diagnostic from MS and it determined that one of my 2 ram cards was bad. I went ahead and upgraded/replaced both of them and all my issues went away. I recommend the windows memory diagnostic. It was spot on.

thanks.

 

Hi, vaughanie.

Thanks for following up with your specific fix. I'm glad the culprit was the memory instead of the mobo. Much less hassle replacing RAM.