Solution
Updating through Windows Update or Device Manager is only good if you're not experiencing problems. They both look at the Windows Update site for drivers - and the manufacturer's just don't update them very often (I've seen drivers from 2005 there that are listed as current). Microsoft provides the server space, but doesn't test these drivers.
The memory dump blames networking, but doesn't point at that specific driver this time.
The raw stack text only shows one 3rd party driver - Netwsw00.sys This is another component of your Intel Wireless Network device drivers. Try:
- download a fresh copy from the PC manufacturer's website (NOT from Intel this time - just a hunch on my part)
- Un-install the current wireless networking...
The memory dump blames networking, but doesn't point at that specific driver this time.
The raw stack text only shows one 3rd party driver - Netwsw00.sys This is another component of your Intel Wireless Network device drivers. Try:
- download a fresh copy from the PC manufacturer's website (NOT from Intel this time - just a hunch on my part)
- Un-install the current wireless networking...
kemical
Essential Member
- Joined
- Aug 28, 2007
- Messages
- 36,176
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\NETwNs64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETwNs64.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwNs64.sys
Probably caused by : NETwNs64.sys ( NETwNs64+99abc )
Followup: MachineOwner
Hi,
your bsod's are being caused by this driver:
NETwNs64.sys :Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7
Please update:
Link Removed
In fact all drivers need updating to their latest versions.
- Thread Author
-
- #3
Hi,
your bsod's are being caused by this driver:
NETwNs64.sys :Intel(R) Wireless WiFi Link 5000 Series Adapter Driver for Windows 7
Please update:
Link Removed
In fact all drivers need updating to their latest versions.
I have updated all the ones listed on intel.com but I just went through my drivers yesterday and tried to update with the device manager and none of them needed updating... I'm no tech whiz though is there a better way for me to do it? I really don't like to muck around with stuff on my laptop lol.
- Thread Author
-
- #5
Ok..well let's see how things go as it was really the driver above that causing the issue. If you bsod again please send the new dmp file.
Thank you
No go,Link Removed another blue screen.
- Joined
- Mar 22, 2010
- Messages
- 3,046
Updating through Windows Update or Device Manager is only good if you're not experiencing problems. They both look at the Windows Update site for drivers - and the manufacturer's just don't update them very often (I've seen drivers from 2005 there that are listed as current). Microsoft provides the server space, but doesn't test these drivers.
The memory dump blames networking, but doesn't point at that specific driver this time.
The raw stack text only shows one 3rd party driver - Netwsw00.sys This is another component of your Intel Wireless Network device drivers. Try:
- download a fresh copy from the PC manufacturer's website (NOT from Intel this time - just a hunch on my part)
- Un-install the current wireless networking stuff through Control Panel...Programs...Uninstall a program.
- install the freshly downloaded copy
- monitor for further BSOD's
I'd then suggest:
Next I'd suggest updating your NEC Electronics USB 3.0 Host Controller Drivers as the 2010 version (which you have) is also known to cause some BSOD's in Win7 systems.
Then we wait and see what comes up next.....
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
cyhid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
The memory dump blames networking, but doesn't point at that specific driver this time.
The raw stack text only shows one 3rd party driver - Netwsw00.sys This is another component of your Intel Wireless Network device drivers. Try:
- download a fresh copy from the PC manufacturer's website (NOT from Intel this time - just a hunch on my part)
- Un-install the current wireless networking stuff through Control Panel...Programs...Uninstall a program.
- install the freshly downloaded copy
- monitor for further BSOD's
I'd then suggest:
Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):[DEL] Link Removed [/DEL]Link broken as of 21 Jul 2012
New link (15 Aug 2012): Link Removed (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help
Next I'd suggest updating your NEC Electronics USB 3.0 Host Controller Drivers as the 2010 version (which you have) is also known to cause some BSOD's in Win7 systems.
Then we wait and see what comes up next.....
Analysis:
The following is for informational purposes only.
Code:
[font=lucida console]**************************Wed Dec 12 14:10:13.045 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121212-24944-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17944.amd64fre.win7sp1_gdr.120830-0333
System Uptime:[B]0 days 0:25:04.888[/B]
Probably caused by :[B]NETIO.SYS ( NETIO!RtlCopyBufferToMdl+1d )[/B]
BugCheck [B]D1, {28, 2, 0, fffff880016106fd}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016106fd, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]X64_0xD1_NETIO!RtlCopyBufferToMdl+1d[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[font=lucida console]**************************Wed Dec 12 14:10:13.045 2012 (UTC - 5:00)**************************
[B]pcouffin.sys Tue Dec 5 09:39:30 2006 (457584A2)[/B]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
PxHlpa64.sys Tue Oct 20 14:08:42 2009 (4ADDFCAA)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
stdcfltn.sys Fri Aug 20 14:05:01 2010 (4C6EC3CD)
IntcDAud.sys Fri Oct 15 04:28:17 2010 (4CB810A1)
HECIx64.sys Tue Oct 19 19:33:43 2010 (4CBE2AD7)
jmcr.sys Wed Nov 10 04:31:51 2010 (4CDA6687)
[B]nusb3hub.sys Thu Nov 18 20:34:24 2010 (4CE5D420)[/B]
[B]nusb3xhc.sys Thu Nov 18 20:34:25 2010 (4CE5D421)[/B]
TurboB.sys Mon Nov 29 18:02:31 2010 (4CF43107)
btmaux.sys Fri Dec 3 11:37:22 2010 (4CF91CC2)
Accelern.sys Mon Dec 13 12:33:51 2010 (4D0658FF)
L1C62x64.sys Mon Dec 27 21:42:39 2010 (4D194E9F)
iaStor.sys Wed Jan 12 20:50:12 2011 (4D2E5A54)
CtClsFlt.sys Wed Jan 19 22:20:46 2011 (4D37AA0E)
igdkmd64.sys Sun Mar 6 23:52:16 2011 (4D746480)
WDKMD.sys Wed Mar 9 18:43:12 2011 (4D781090)
iwdbus.sys Wed Mar 9 18:43:23 2011 (4D78109B)
nvBridge.kmd Thu Apr 21 21:01:09 2011 (4DB0D355)
cymfltr.sys Sun May 22 15:05:02 2011 (4DD95E5E)
cyhid.sys Mon May 23 02:03:35 2011 (4DD9F8B7)
cykbfltr.sys Wed May 25 05:44:46 2011 (4DDCCF8E)
RTKVHD64.sys Tue May 31 05:18:41 2011 (4DE4B271)
SASKUTIL64.SYS Tue Jul 12 17:00:01 2011 (4E1CB5D1)
SASDIFSV64.SYS Thu Jul 21 19:03:00 2011 (4E28B024)
Sftvollh.sys Fri Sep 30 12:42:46 2011 (4E85F186)
Sftplaylh.sys Fri Sep 30 12:43:05 2011 (4E85F199)
Sftfslh.sys Fri Sep 30 12:43:06 2011 (4E85F19A)
Sftredirlh.sys Fri Sep 30 12:43:14 2011 (4E85F1A2)
btmhsf.sys Wed Nov 2 08:26:12 2011 (4EB136E4)
iBtFltCoex.sys Fri Dec 9 14:45:13 2011 (4EE26549)
[B]dtsoftbus01.sys Fri Jan 13 08:45:46 2012 (4F10358A)[/B]
HipShieldK.sys Fri Apr 20 17:32:16 2012 (4F91D5E0)
GEARAspiWDM.sys Thu May 3 15:56:17 2012 (4FA2E2E1)
mfehidk.sys Wed May 30 11:35:13 2012 (4FC63E31)
mfewfpk.sys Wed May 30 11:35:28 2012 (4FC63E40)
mfeapfk.sys Wed May 30 11:35:57 2012 (4FC63E5D)
mfeavfk.sys Wed May 30 11:36:18 2012 (4FC63E72)
mfefirek.sys Wed May 30 11:38:10 2012 (4FC63EE2)
cfwids.sys Wed May 30 11:38:43 2012 (4FC63F03)
AMPPAL.sys Wed Jul 18 03:48:59 2012 (50066A6B)
point64.sys Tue Sep 18 06:18:08 2012 (50584A60)
dc3d.sys Tue Sep 18 06:18:24 2012 (50584A70)
Netwsw00.sys Sun Sep 30 14:24:04 2012 (50688E44)
nvlddmkm.sys Tue Oct 2 14:21:13 2012 (506B3099)
nvpciflt.sys Tue Oct 2 14:21:40 2012 (506B30B4)
nvkflt.sys Tue Oct 2 14:21:49 2012 (506B30BD)
[/font]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
cyhid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
- Joined
- Mar 22, 2010
- Messages
- 3,046
Not a problem, it happens to all of us at one time or another.Thanks John, real world events took precedent.
Similar threads
- Article
- Replies
- 0
- Views
- 30
- Article
- Replies
- 0
- Views
- 696
- Solved
- Replies
- 3
- Views
- 9K