Going NUTS

here are my last 2 mini dumps. I keep getting BSOD and doesnt always point to the same thing. Any Ideas?

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


Loading Dump File [C:\WINDOWS\Minidump\Mini102107-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:
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 Oct 21 19:46:55.843 2007 (GMT-5)
System Uptime: 0 days 1:10:32.425
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
...........
Unable to load image NVENETFD.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for NVENETFD.sys
*** ERROR: Module load completed but symbols could not be loaded for NVENETFD.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {120014, 2, 0, b9deb7d5}

*** WARNING: Unable to verify timestamp for NVNRM.SYS
*** ERROR: Module load completed but symbols could not be loaded for NVNRM.SYS
Probably caused by : NVENETFD.sys ( NVENETFD+38f0 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: 00120014, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: b9deb7d5, address which referenced memory

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


READ_ADDRESS: 00120014

CURRENT_IRQL: 2

FAULTING_IP:
NDIS!ethFilterDprIndicateReceivePacket+f7
b9deb7d5 035014 add edx,dword ptr [eax+14h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b88938f0 to b9deb7d5

STACK_TEXT:
805503b4 b88938f0 89248008 891b7c94 00000001 NDIS!ethFilterDprIndicateReceivePacket+0xf7
WARNING: Stack unwind information not available. Following frames may be wrong.
805503f0 b801ccc1 00000001 b802f580 896ad544 NVENETFD+0x38f0
806e4830 05c7fffe fffe0080 00000041 0f04eac1 NVNRM+0x8cc1
806e4834 fffe0080 00000041 0f04eac1 f21882b6 0x5c7fffe
806e4838 00000000 0f04eac1 f21882b6 0ff0806e 0xfffe0080


STACK_COMMAND: kb

FOLLOWUP_IP:
NVENETFD+38f0
b88938f0 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: NVENETFD+38f0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NVENETFD

IMAGE_NAME: NVENETFD.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 42e6d9db

FAILURE_BUCKET_ID: 0xD1_NVENETFD+38f0

BUCKET_ID: 0xD1_NVENETFD+38f0

Followup: MachineOwner

---------


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


Loading Dump File [C:\WINDOWS\Minidump\Mini102007-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:
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: Sat Oct 20 18:24:12.866 2007 (GMT-5)
System Uptime: 0 days 5:03:21.919
Loading Kernel Symbols
............................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 80544a16, 80550338, 0}

Probably caused by : ntkrpamp.exe ( nt!KiInterruptDispatch+36 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* 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: 80544a16, The address that the exception occurred at
Arg3: 80550338, 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!KiInterruptDispatch+36
80544a16 f00fba2e00 lock bts dword ptr [esi],0

TRAP_FRAME: 80550338 -- (.trap ffffffff80550338)
ErrCode = 00000002
eax=00000001 ebx=80550450 ecx=00000002 edx=00002e3e esi=00000000 edi=89846bb0
eip=80544a16 esp=805503ac ebp=805503c0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KiInterruptDispatch+0x36:
80544a16 f00fba2e00 lock bts dword ptr [esi],0 ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from ba1ca062 to 80544a16

STACK_TEXT:
805503c0 ba1ca062 badb0d00 00002e3e 00009d83 nt!KiInterruptDispatch+0x36
80550450 805450cc 00000000 0000000e 00000000 intelppm!AcpiC1Idle+0x12
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiInterruptDispatch+36
80544a16 f00fba2e00 lock bts dword ptr [esi],0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

SYMBOL_NAME: nt!KiInterruptDispatch+36

FAILURE_BUCKET_ID: 0x8E_nt!KiInterruptDispatch+36

BUCKET_ID: 0x8E_nt!KiInterruptDispatch+36

Followup: MachineOwner

 

The first thing i would suggest is to update your nvidia drivers[display], you might have to pick and choose a few times. ed

 

Just did that, latest drivers. This has been happening off and on for a year.

 

uninstal NVidia LAN driver and install it again.You will find this on your MOBO CD.

 

Why do u say this and what is a LAN driver and a MOBO CD?

 

OK,I say you should uninstall LAN driver(this is your network driver),or if you can't find it in add& remove section,find the motherboard drivers in add&remove also,and uninstall it,and reboot.After reboot,do a fresh install from your Motherboard CD (you do have,right)(this CD goes with your Motherboard-MOBO,when you bought it).And NVENETFD.sys is part of LAN driver setup.I think this is clear for you.GOOD LUCK!!!!

 

Yeah- the NVENETFD file is part of your NVidia EtherNET drivers and should be on your system drivers CD. If you don't have a system driver CD, go to your PC maker's web site, and search for the driver using the model number of your PC. You can also try the NVidia web site if you can't find what you need at the PC manufacturer's site.
NVidia's chipset drivers link: http://www.nvidia.com/object/nforce_nf4_winxp32_8.26_11.09.html This is for nForce 400 series chipsets (MCP51 or MCP61). You should probably run a system info program to get the exact chipset number. Try Everest or PCWizard...
Everest: http://www.majorgeeks.com/download.php?det=4181
PCWizard: http://www.majorgeeks.com/PC_Wizard_d3846.html