BSOD on Dell E6410, win7 professional 32 bit

[lenciel]

Hi, I'm so glad that I have a place to ask for this kind of questions. Thanks for everyone in advance!

My laptop keeps failing me when I switch the internet connection from wifi to LAN ethernet. Once I plugin the ethernet plug, I got a BSOD. The details are something like the image I attached.

Since it's complaining my nwifi.sys, I tried to download the latest driver from Dell, but it's still crashing. Then I directly downloaded the latest driver (newer than the one Dell put on their page) from intel, things still happen.

I've also tried to run with the verifier open, it will crash even earlier (before the windows os booted) and the dump file is still blame the nwifi.sys, not a third party driver.

All the files I collected are attached too.

FYI: When i run perfmon /report, the window opens and it keeps saying collecting data. It never finishes and creats the report. Any help would be appreciated.

 

[zigzag3143]

Hi, I'm so glad that I have a place to ask for this kind of questions. Thanks for everyone in advance!

My laptop keeps failing me when I switch the internet connection from wifi to LAN ethernet. Once I plugin the ethernet plug, I got a BSOD. The details are something like the image I attached.

Since it's complaining my nwifi.sys, I tried to download the latest driver from Dell, but it's still crashing. Then I directly downloaded the latest driver (newer than the one Dell put on their page) from intel, things still happen.

I've also tried to run with the verifier open, it will crash even earlier (before the windows os booted) and the dump file is still blame the nwifi.sys, not a third party driver.

All the files I collected are attached too.

FYI: When i run perfmon /report, the window opens and it keeps saying collecting data. It never finishes and creats the report. Any help would be appreciated.

Three problems


1-sptd.sys used in alcohol120 and daemon tools is a huge problem

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp,sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


2- Macaffee remove and replace with Microsoft security essentials

How to uninstall or reinstall supported McAfee consumer products using the McAfee Consumer Products Removal tool (MCPR.exe)

http://www.microsoft.com/security_essentials/


3-Update your old drivers including

CMBProtector.dat    1/18/2007 02:27:09 AM    0xa9098000    0xa9098e00    0x00000e00    0x45af133d                            
PBADRV.sys    1/7/2008 02:52:14 PM    0x86c00000    0x86c0b000    0x0000b000    0x478274de                            
Alidevice.SYS    7/13/2008 04:10:10 AM    0x93f41000    0x93f49000    0x00008000    0x4879b862                            
CertClient.dat    8/27/2008 03:22:01 AM    0xa9092000    0xa9098000    0x00006000    0x48b50099                            
iaStorV.sys    4/8/2009 12:54:58 PM    0x864d3000    0x865ae000    0x000db000    0x49dcd6e2                            
spldr.sys    5/11/2009 12:13:47 PM    0x86dee000    0x86df6000    0x00008000    0x4a084ebb                            
spsys.sys    5/11/2009 12:37:10 PM    0xabedc000    0xabf46000    0x0006a000    0x4a085436                            
GEARAspiWDM.sys    5/18/2009 08:16:53 AM    0x93fb1000    0x93fb6280    0x00005280    0x4a1151b5                            
cvusbdrv.sys    6/24/2009 04:42:04 PM    0x822c0000    0x822cc000    0x0000c000    0x4a428f9c                            
risdpe86.sys    6/30/2009 06:28:26 AM    0x93ede000    0x93eef000    0x00011000    0x4a49e8ca

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\041311-20373-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8344e000 PsLoadedModuleList = 0x83598850
Debug session time: Tue Apr 12 22:01:18.054 2011 (GMT-4)
System Uptime: 0 days 21:09:57.700
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {6, 2, 0, 99709a31}

Unable to load image \SystemRoot\system32\DRIVERS\dnelwf.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dnelwf.sys
*** ERROR: Module load completed but symbols could not be loaded for dnelwf.sys
Unable to load image \SystemRoot\system32\DRIVERS\e1k6232.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1k6232.sys
*** ERROR: Module load completed but symbols could not be loaded for e1k6232.sys
Probably caused by : nwifi.sys ( nwifi!MP6SendOneNBL+14d )

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: 00000006, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 99709a31, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 835b8718
Unable to read MiSystemVaType memory at 835981a0
 00000006 

CURRENT_IRQL:  2

FAULTING_IP: 
nwifi!MP6SendOneNBL+14d
99709a31 f6400605        test    byte ptr [eax+6],5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  8078a50c -- (.trap 0xffffffff8078a50c)
ErrCode = 00000000
eax=00000000 ebx=8b60a018 ecx=00000000 edx=000014b4 esi=86775d08 edi=a34b8420
eip=99709a31 esp=8078a580 ebp=8078a608 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nwifi!MP6SendOneNBL+0x14d:
99709a31 f6400605        test    byte ptr [eax+6],5         ds:0023:00000006=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 99709a31 to 8348f5cb

STACK_TEXT:  
8078a50c 99709a31 badb0d00 000014b4 860c3000 nt!KiTrap0E+0x2cf
8078a608 99709c6d 8b7c2008 8b60a018 8078a630 nwifi!MP6SendOneNBL+0x14d
8078a638 9970a23b 00000000 8b000302 894ce9e0 nwifi!MP6SendNBLInternal+0x51
8078a650 9970d3df 8b7c2008 8b60a018 00000000 nwifi!MP6Send+0x67
8078a668 8ccab4d8 894aaad0 8b60a018 00000000 nwifi!FilterSendNetBufferLists+0x19
8078a688 8ccab448 8b60a018 8b60a018 00000000 ndis!ndisFilterSendNetBufferLists+0x87
8078a6a0 928da599 894ce9e0 8b60a018 00000000 ndis!NdisFSendNetBufferLists+0x38
WARNING: Stack unwind information not available. Following frames may be wrong.
8078a6fc 928da7b9 8b60a0ec 8b60a0c0 00000000 dnelwf+0x2599
8078a724 8ccab4d8 00000000 88dbb828 00000000 dnelwf+0x27b9
8078a744 8ccab448 88dbb828 88dbb828 00000000 ndis!ndisFilterSendNetBufferLists+0x87
8078a75c 928adc20 894e36a0 88dbb828 00000000 ndis!NdisFSendNetBufferLists+0x38
8078a7d8 8ccab618 8a79cf68 88dbb828 00000000 pacer!PcFilterSendNetBufferLists+0x256
8078a804 8cd0fbad 892a50e0 88dbb828 00000000 ndis!ndisSendNBLToFilter+0xf2
8078a834 8ce7e344 894bfaa8 88dbb828 00000000 ndis!NdisSendNetBufferLists+0x162
8078a880 8cea08bc 894c2450 00000000 00000000 tcpip!FlSendPackets+0x416
8078a8d4 8ce888b0 8cf00da0 00000000 00000000 tcpip!IppFragmentPackets+0x2e2
8078a968 8ce8c25c 88ed7f08 00000000 00000001 tcpip!IpFlcReceivePackets+0xbf6
8078a9f4 8ce912dc 88ed7f08 8b2912e0 88ffcc98 tcpip!IpFlcReceivePreValidatedPackets+0x57b
8078aa1c 834d7654 00000000 a5e47d54 88a36428 tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xfc
8078aa84 8ce9146c 8ce911e0 8078aaac 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132
8078aac0 8cd0f18d 89118a02 8b291200 00000000 tcpip!FlReceiveNetBufferListChain+0x7c
8078aaf8 8ccfd5be 8911caa8 8b2912e0 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0x188
8078ab20 8ccfd4b2 00000000 892a02f8 8b291388 ndis!ndisIndicateSortedNetBufferLists+0x4a
8078ac9c 8cca8c1d 8919e0e0 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
8078acb8 8ccd956a 8919e0e0 8b2912e0 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2d
8078acd4 8ccd9504 892be140 8b2912e0 00000000 ndis!ndisFilterIndicateReceiveNetBufferLists+0x46
8078acf0 928daef3 892be140 8b2912e0 00000000 ndis!NdisFIndicateReceiveNetBufferLists+0x2f
8078ad2c 928db0d2 892a02f8 00000001 00000000 dnelwf+0x2ef3
8078ad54 8ccfd553 00000000 00000000 00000000 dnelwf+0x30d2
8078ad7c 8cca8c78 8919e0e0 890d7b78 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x62
8078ada4 92b68ea1 8919e0e0 890d7b78 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x52
8078adcc 92b68ff9 8931e000 890d7b78 00000001 e1k6232+0x25ea1
8078ae0c 92b5bfef 0131e000 8931fec0 8078af10 e1k6232+0x25ff9
8078ae80 92b5d928 8931e000 00000000 8078af10 e1k6232+0x18fef
8078aec4 92b5d964 8931e000 00000000 00000000 e1k6232+0x1a928
8078aee0 8ccfd892 8931e000 00000000 00000000 e1k6232+0x1a964
8078af20 8cca8a0f 88b39c6c 00b39b58 00000000 ndis!ndisMiniportDpc+0xda
8078af48 834c61b5 88b39c6c 88b39b58 00000000 ndis!ndisInterruptDpc+0xaf
8078afa4 834c6018 83579d20 88ffcc98 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 834c57dc b1f1bce4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 b1f1bce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
834c57dc 00000000 0000001a 00d6850f bb830000 0xb1f1bce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nwifi!MP6SendOneNBL+14d
99709a31 f6400605        test    byte ptr [eax+6],5

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nwifi!MP6SendOneNBL+14d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nwifi

IMAGE_NAME:  nwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc89f

FAILURE_BUCKET_ID:  0xD1_nwifi!MP6SendOneNBL+14d

BUCKET_ID:  0xD1_nwifi!MP6SendOneNBL+14d

Followup: MachineOwner

---------