BSOD on Dell XPS M1330 -- poss. culprit Intel wifi 3945

miko1010 · 26 Jan 2010

I hope this question / machine combination has not been posted already.

Expericing random BSOD with Dell XPS M1330 Notebook.
BSOD occurs during web surfing, skype calls, idle, or bt downloading (basically, "random")

Using windows 7 ultimate 64-bit english - as far as I can tell all drivers are up-to-date. (used "drivermax" application to get a diagnostic, then went out to search for all individual drivers)

Install is OEM upgrade disc and did clean install from working XP pro on the machine

from my own testing nearly 99% sure it's the wireless acting up --reasons:
1) no BSOD occurs if i plug in an usb external wifi dongle or use the wired NIC
2) no BSOD occurs if i turn-off the on-board Intel wifi using the physical wifi on/off switch on the compter.
3) BSOD occurs randomly when on-board Intel wifi is on, no matter which power setting or action.

my laptop is a Dell XPS M1330
Core Duo T7500
4GB DD2-667 Ram (Kingston - self upgraded)
Bios A15
Geforce 8400GS
Dell 355 bluetooth
Intel Pro Wireless A/B/G 3495
8x slot DVD-RW Matsushita
UPEK fingerprint reader
Sigmatel (IDT?) HD audio
Ricoh card reader (don't have specifi model with me)
- Have had my mobo/gpu replaced once due to Geforce 8400 issues

This error occurs constantly whenever wifi and computer is on. I can post additional dump files that shows basically same error code but sometimes the source of crash is ntkernel while other times it's ntwifi or something similar.

any help or advice is greatly appreciated.

M

usasma · 26 Jan 2010

It looks like you've done all the work for us! That's some nice troubleshooting!

Well, if the wifi is bad - then it's either the driver or the hardware. So, let's start with the driver (it's free, and it's easier than messing with the wifi card).

Download Intel wireless driver from Intel ( http://downloadcenter.intel.com/Default.aspx )
Uninstall the current Intel wireless driver from your Dell
Install the freshly downloaded driver and see if the BSOD's stop.

Running the dump files, will be right back.....

miko1010 · 26 Jan 2010

Hi Usasma,

thanks for the quick feedback and advice!
I am running the latest wifi drivers downloaded from intel already when i produced dmp file.

I was even desparate enough to listen to the Dell tech guy and try installing the vista64 drivers 2 weeks back.
Either of the two drivers are working an I still get te same BSOD. Unfortunately, Dell guy tells me that only my original OS is supported (vista 32bit) and insists that I would need to have the same errr occur in vista for them to send someone out to check or replace.

I've run memtest all last night (expat working in Asia) And after 6 passes no errors found.

If it helps i would upload all other dmp files I have in additon to the memtest screens

looking forward to finding out the diagnosis from the dmp file! You and all the experts here are my ray of hope now.

Thanks again.

usasma · 26 Jan 2010

The dump files all point to NETw4v64.sys/NETw5v64.sys - a component of the Intel wireless driver package.

It appears that you updated the drivers for this device on January 8 or 9 - yet you're still getting errors. You now have this driver installed: netw5v64.sys Tue Sep 15 15:34:16 2009 FYI - The latest driver is the Sep 15, 2009 version that you have.

As such, this seems to indicate that the driver probably isn't to blame. That leaves us with wondering if there's another driver that's causing this, if it's a hardware issue, or if it's Windows causing this.

But, please try this next:
Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated 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.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers:

Code:

AegisP.sys   Thu Jul 12 15:57:49 2007 - AEGISP.SYS is related to AEGIS Client 3.4.0.1.
Manufacturer: Meetinghouse Data Communications www.mtghouse.com or Cisco (www.cisco.com)
OEM04Vfx.sys Mon Mar 05 05:55:47 2007 - Dell/Creative Integrated WebCam
OEM04Vid.sys Wed Oct 10 22:45:45 2007 - Dell/Creative Integrated WebCam
tcusb.sys    Sat Mar 10 08:41:41 2007 - TCUSB.SYS is a TouchChip USB Kernel Driver (FingerPrint Sensor).
Manufacturer: UPEK Inc. www.upek.com

Then, the sequence that I suggest is first reseating the wireless card and it's connections.
If that doesn't fix it, then try running Driver Verifier for 3rd party drivers.
If that doesn't identify the culprit, then we'll run it for ALL drivers
If that doesn't identify it, then we'll have to presume that it's a hardware issue.

To reseat it, you've gotta unplug the AC adapter and remove the battery
Page 35 of this file shows you where the wireless card is located: http://support.dell.com/support/edoc...10P.pdf#72Page 134 shows a sequence for removing and replacing the card. Do this to ensure that it's tightly connected and properly seated.

If the BSOD's continue, then try running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Here's a summary of the BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan  7 12:35:10.090 2010 (GMT-5)
System Uptime: 0 days 0:25:33.135
BugCheck A, {0, 2, 0, fffff80002814477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  TrustedInstall
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan  7 12:56:43.699 2010 (GMT-5)
System Uptime: 0 days 0:21:06.744
BugCheck A, {0, 2, 0, fffff8000280e477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+5b7d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan  7 14:12:24.348 2010 (GMT-5)
System Uptime: 0 days 1:05:57.393
BugCheck A, {0, 2, 0, fffff80002ddf477}
*** WARNING: Unable to verify timestamp for NETw4v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v64.sys
Probably caused by : NETw4v64.sys ( NETw4v64+874c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Jan  7 20:05:33.641 2010 (GMT-5)
System Uptime: 0 days 0:08:21.685
BugCheck A, {0, 2, 0, fffff8000280b477}
*** WARNING: Unable to verify timestamp for NETw4v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v64.sys
Probably caused by : NETw4v64.sys ( NETw4v64+874c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jan  8 10:40:11.585 2010 (GMT-5)
System Uptime: 0 days 14:34:07.629
BugCheck A, {0, 2, 0, fffff80002817477}
*** WARNING: Unable to verify timestamp for NETw4v64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v64.sys
Probably caused by : NETw4v64.sys ( NETw4v64+874c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan  9 11:08:43.622 2010 (GMT-5)
System Uptime: 0 days 2:42:04.542
BugCheck A, {0, 2, 0, fffff80002816477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan  9 13:52:16.743 2010 (GMT-5)
System Uptime: 0 days 0:14:56.788
BugCheck A, {0, 2, 0, fffff80002805477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan  9 23:17:27.528 2010 (GMT-5)
System Uptime: 0 days 9:24:17.572
BugCheck A, {0, 2, 0, fffff80002df3477}
*** WARNING: Unable to verify timestamp for netw5v64.sys
*** ERROR: Module load completed but symbols could not be loaded for netw5v64.sys
Probably caused by : netw5v64.sys ( netw5v64+b4eb )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe

***************************************************************************
Here's how Mark Russinovich does it :) Mark's Blog : The Case of the Crashed Phone Call (actually, it's a very good description of why we ask users to go to the device manufacturer's website for the latest drivers).

usasma · 26 Jan 2010

I just saw your last post.

I think the most likely problem is that it's the wifi card. If it's broken, you can purchase a new one online for about $29 (US). But if it's anything else and if you have a Dell service contract, it may be worthwhile installing Vista and having them come out. You could image the Win7 installation and save if for after they fix the hardware.

miko1010 · 26 Jan 2010

Wow super!!

You must have been typing up that response when I was typing my short reply.

Will give that a try and hopefully you'll hear back from me after 24-36(?) hours.

Thanks,
M

miko1010 · 28 Jan 2010

Hi usasma, or anyone out there who's reading this post - Issue still occurrs so now even more desparate for help. >_<

a few complications occurred:

- somehow got the dell guy to come out to my work office. he replaced the wifi card, no ques asked (even I was using win7) - we connected to the home network on the new wifi and after 5-10 minutes no BSOD... thought it was fine.

- came home, still BSOD under same conditions

- ran driver verifier and computer does not BSOD while using the PC but only when idle for 5-15 minutes

- ran verifier with intel wifi off -- over 24 hours no crash

- somehow i killed (?) the bluetooth on the machine while trying to find the latest drivers. the bluetooth radio 'on' light is off but the syste is able to detect there is a bluetoot device ?! now when I try to install what i believed to be the latest bluetooth driver from broadcom, it says 'cannot detect bluetooth device"

- re: updating of old drivers - i'v found a new driver for the UPEK fingerprint device, updated the sound card driver (which seem to do with the aegis.sys file). Could not find anyting new for Creative webcam and also i realized the driver on the bluetooth was old / provided by M$ so i thought I'd try to update it (hence the previous point on kill the bluetooth)

so here are the attached files
- the latest set of minidump (all that's found in C:\windows\minidmp)
- screen of my device manager in Win7
- anything else I can provide?

thanks again and hope the infomation does point to the root of th problem.

usasma · 30 Jan 2010

Sorry for the delay, was in the hospital for a couple of days

It seems to me that you've found the problem:
- Wifi on = BSOD
- Wifi off = no BSOD

You've replaced the Wifi card and the drivers - so all that's left is the motherboard.
I wonder about your wireless router at home (just a suspicion - nothing firm points at it).
Do you have another wireless network that you can connect to to see if it BSOD's there also?
Try it both with and without Driver Verifier.

The last 3 dump files were:
STOP 0xA (Verifier enabled) in nvlddmkm.sys
STOP 0xA (not Verifier enabled) in netw5v64.sys
STOP 0xD1 (Verifier enabled) in netw5v64.sys

This series also points to a hardware issue (the nvlddmkm.sys shouldn't be showing up if this is a networking error). You can rule this one out by replacing your nVidia video drivers - but that still leaves the netw5v64.sys problem - which you've already fixed (both the drivers and the wireless card).

Now, I'd suspect that this is sufficient reason to have Dell give you a new computer - BUT the Aegis drivers are also a concern (as they're networking drivers). Most search results for this are centered around a wireless USB adapter - which I presume that you're not using (If so, please let us know).

If using one - please uninstall the software. If not using one, then please use this free program to stop the AEGISP.SYS driver from loading: Autoruns for Windows Alternatively, search your system for AEGISP.SYS, then rename it to AEGISP.BAK Reboot and see if it stays renamed.