RegHackr is of course correct
At least 3 of the crashes had the slnt.sys file in comman, I would update that and since its current date is 2005 and all the other critical drivers
I would also run a system file check to verofy and repair system files
to run type cmd in search>right click and run as admin> SFC /SCANNOW
let us know the results
Also note hte section below on the NDIS driver
AND AS AN ASIDE WOULD HAVE BEEN NICE TO KNOW YOU HAVE A RAID, AND IF YOU ARE OVERCLOCKING
Ken
\
slnt.sys slnt.sys+218d 0x9310b000 0x9310f640 0x00004640 0x43993b06 12/9/2005 3:06:30 AM
secdrv.SYS 0x9b8bd000 0x9b8c7000 0x0000a000 0x45080528 9/13/2006 8:18:32 AM
3xHybrid.sys 0x93110000 0x931ed480 0x000dd480 0x468ebf98 7/6/2007 5:18:00 PM
jraid.sys 0x835b4000 0x835c3e00 0x0000fe00 0x46fde30c 9/29/2007 12:30:52 AM
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\111809-17518-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a08000 PsLoadedModuleList = 0x82b50810
Debug session time: Wed Nov 18 06:25:43.176 2009 (GMT-5)
System Uptime: 0 days 0:17:20.955
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_NDIS_DRIVER (7c)
This is the NDIS Driver Bugcheck for Windows Server 2003 and later.
For Windows 2000 and Windows XP, see 0xD2, BUGCODE_ID_DRIVER.
Arguments:
Arg1: 00000005, An Ethernet driver indicated receiving a packet using a
packet descriptor that is currently in use by protocol
stack. (Caught by checking stack packet location)
Arg2: 85e890e0, A pointer to Miniport block. !ndiskd.miniport on
this pointer for more info.
Arg3: 861f9304, The packet descriptor used by the driver. Use
!ndiskd.pkt on this pointer for more info.
Arg4: 861dc99c, A pointer to the packet array that contained this
packet descriptor. (not much of a use)
Debugging Details:
------------------
Unable to load image \SystemRoot\system32\DRIVERS\slnt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for slnt.sys
*** ERROR: Module load completed but symbols could not be loaded for slnt.sys
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7
C
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 88cc44e8 to 82ae4d10
STACK_TEXT:
807e3e48 88cc44e8 0000007c 00000005 85e890e0 nt!KeBugCheckEx+0x1e
807e3eb0 9310d18d 003f0b28 861dc99c 00000002 ndis!ethFilterDprIndicateReceivePacket+0x8e7
WARNING: Stack unwind information not available. Following frames may be wrong.
807e3ee8 9310bc82 021dc648 7e7d2580 861dc650 slnt+0x218d
00000000 00000000 00000000 00000000 00000000 slnt+0xc82
STACK_COMMAND: kb
FOLLOWUP_IP:
slnt+218d
9310d18d ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: slnt+218d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: slnt
IMAGE_NAME: slnt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 43993b06
FAILURE_BUCKET_ID: 0x7C_slnt+218d
BUCKET_ID: 0x7C_slnt+218d
Followup: MachineOwner
---------
