BSOD - Most likely graphical drivers/hardware

AlvitrValkyrie · 14 Jan 2012

SYSTEM INFO:
System Model: ASUS Notebook G73Sw
CPU: Intel Core i7-2630QM (Quad) @ 2GHz (~2.5 on turboboost) [39*C]
GPU: 1024MB GeForce GTX 460M [41*C]
RAM: 8.00 GB Dual-Channel DDR3 @ 665MHz
OS: Windows 7 Home Premium SP1 x64 OEM
Age: Few months, and have not switched the OS.

CIRCUMSTANCES:
Started BSODing recently. Just got it back from bestbuy, actually. Needed a new charging port. Took the HDD out beforehand. Put it back in. Worked fine. I'm not overclocked, and all my system temps seem to be fine. Windows detects all my RAM, and my RAM usage isn't higher than normal.

I have two external displays connected, and the laptop display is disabled. Both are HP S2031 monitors.

Code:

Generic PnP Monitor (1600x900@60Hz)
Generic PnP Monitor (1600x900@60Hz)

My notebook is connected to my Kensigton Universal Notebook Docking Station with VGA/DVI and Ethernet. One monitor is connected via the dock's DVI port, and one is connected to a USB slot on the dock via a Kensigton Universal Multi-Display Adapter (DVI). The drivers for both devices, and the monitors, were installed from the disks I got, and are fully up to date.

I have absolutely no fragmentation on my display. No particles. Only happened once, but I think that was from accessing nTune. BSOD right after.

Interesting note. I can force a BSOD via some of the nTune settings in the nVidia control settings. nTune is enabled upon startup. That's the only program that isn't required for my computer to be operational that's enabled, or so I believe. I should disable and see what happens, but I want to get this out before I BSOD again.

With 3 external displays plugged in, the BSOD shows up on the very right monitor. With two, the laptop display re-enables to display the BSOD. Idk if this has any relevance. It might!

I'm using a non-beta driver that's an update from the nvidia site, and have been for a while now. There are no later versions. I checked a few days ago. The driver: 285.62

Also, ran CCleaner to fix registry items and clean my system. Then rebooted and ran Spybot and Superantispyware in safe move. No viruses. Just cookies. Rebooted, and ran TrendMicro, HitmanPro, and TDSSKiller. Absolutely clean. Nothing mysterious running (using procexp). Explorer was crashing upon reboot, but I discovered Stardock's Fences was the culprit. Uninstalled, and all is working totally fine now.

Everything from the "BSOD - Posting instructions" is attached ^_^ The full dump, compressed, times up before upload :l ^_^ And no I do not have an installation CD, but have one from my previous Alienware laptop (also x64).

What the BSOD displays

Code:

Technical information:
*** STOP: 0x0000003B (yata yata)
*** nvoclk64.sys (yata yata)

How do I go about fixing all this?
The $evtx_sys_dump files points to an opengl driver issue.

usasma · 14 Jan 2012

I've only used this (or a similiar) device once before (on an HP Envy system that didn't have an ethernet port).

LAN9500 USB 2.0 to Ethernet 10/100 Adapter

As I recall, it was a bit quirky.
Why use it instead of the built in ethernet port (Realtek PCIe GBE Family Controller)?

MSINFO32 points to NETwNs64.sys as the cause for 4 STOP 0xD1 BSOD's
This driver belongs to your Intel wireless drivers. Please do the following:
- get the latest version of the wireless drivers from http://downloadcenter.intel.com
- uninstall the current wireless drivers from the system
- install the freshly downloaded drivers
- monitor for further BSOD's

I notice that you have both Intel ProSet and Intel WiMax installed. I'd suggest removing BOTH of them before installing the freshly downloaded driver.

The memory dumps blame the same driver - with one notable exception (the nvoclk64.sys driver)
For that, I'd suggest you uninstall the nVidia tools, and then download/install the latest version of the nVidia System Tools from here: NVIDIA DRIVERS 6.08

- Your vhidmini.sys driver dates from 2007. Please either uninstall it or update it - it belongs most likely an IVT Corporation BlueSolei Bluetooth HID Mini driver
- Your wacommousefilter.sys driver also dates from 2007. Please either uninstall it or update it - it belongs to a Wacom(tablet) Mouse Filter driver
- Your JmtFltr.sys driver also dates from 2007. Please either uninstall it or update it - it belongs to a JMicron JMB38X Memory Card Reader Driver Driver
- Your nvoclk64.sys driver also dates from 2007. Please either uninstall it or update it as I discussed previously
- Your Lycosa.sys driver dates from 2008. Older versions of this driver is known to cause BSOD's on Win7 systems. Please either uninstall it or update it from the Razer support website Razer Support
- Your vncmirror.sys driver dates from 2008. Please either uninstall it or update it - it is a VNC Mirror Miniport driver - VNC Server - RealVNC Ltd RealVNC - Obtaining technical support for VNC® software

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-19890-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 03:51:59.542 2012 (UTC - 5:00)
System Uptime: 0 days 0:19:05.415
BugCheck D1, {28, 2, 0, fffff88004cee4de}
*** 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+bb4de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+bb4de
Bugcheck code 000000D1
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`04cee4de
BiosVersion = G73Sw.205
BiosReleaseDate = 02/10/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-22526-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 03:31:09.317 2012 (UTC - 5:00)
System Uptime: 0 days 0:08:36.175
BugCheck D1, {28, 2, 0, fffff88004af34de}
*** 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+bb4de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+bb4de
Bugcheck code 000000D1
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`04af34de
BiosVersion = G73Sw.205
BiosReleaseDate = 02/10/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011412-22136-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 03:20:32.481 2012 (UTC - 5:00)
System Uptime: 0 days 1:42:46.449
BugCheck D1, {28, 2, 0, fffff88004ad24de}
*** 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+bb4de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+bb4de
Bugcheck code 000000D1
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`04ad24de
BiosVersion = G73Sw.205
BiosReleaseDate = 02/10/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-23883-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 01:35:31.752 2012 (UTC - 5:00)
System Uptime: 0 days 0:04:11.720
Probably caused by : nvoclk64.sys ( nvoclk64+1ab7 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  nvcplui.exe
FAILURE_BUCKET_ID:  X64_0x3B_nvoclk64+1ab7
Bugcheck code 0000003B
Arguments 00000000`c0000096 fffff880`0a32bab7 fffff880`0a535d10 00000000`00000000
BiosVersion = G73Sw.205
BiosReleaseDate = 02/10/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-35568-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Jan 14 00:24:40.190 2012 (UTC - 5:00)
System Uptime: 0 days 1:43:44.158
BugCheck D1, {28, 2, 0, fffff88004af94de}
*** 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+bb4de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+bb4de
Bugcheck code 000000D1
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`04af94de
BiosVersion = G73Sw.205
BiosReleaseDate = 02/10/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-27580-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 22:40:18.569 2012 (UTC - 5:00)
System Uptime: 0 days 0:25:08.426
BugCheck D1, {28, 2, 0, fffff88004af44de}
*** 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+bb4de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+bb4de
Bugcheck code 000000D1
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`04af44de
BiosVersion = G73Sw.205
BiosReleaseDate = 02/10/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011312-49358-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Jan 13 22:14:33.856 2012 (UTC - 5:00)
System Uptime: 0 days 0:20:57.824
BugCheck D1, {28, 2, 0, fffff88004b0a4de}
*** 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+bb4de )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_NETwNs64+bb4de
Bugcheck code 000000D1
Arguments 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`04b0a4de
BiosVersion = G73Sw.205
BiosReleaseDate = 02/10/2011
CPUID:        "Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz"
MaxSpeed:     2000
CurrentSpeed: 1995
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

zigzag3143 · 14 Jan 2012

Virtually all of these were Related to NETwNs64.sys Wireless WiFi Link Driver from Intel Corporation. I would re-install newest available.

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

AlvitrValkyrie · 14 Jan 2012

usasma said:

MSINFO32 points to NETwNs64.sys as the cause for 4 STOP 0xD1 BSOD's
This driver belongs to your Intel wireless drivers. Please do the following:
- get the latest version of the wireless drivers from http://downloadcenter.intel.com
- uninstall the current wireless drivers from the system
- install the freshly downloaded drivers
- monitor for further BSOD's

Which specific driver? Wireless Networking > Intel Centrino Wifi Products > ?

And how do I switch to the ethernet port? O.o? I may have fidgeted a bit when configuring connectify.

And btw dude, thanks

Freaking genius

usasma · 14 Jan 2012

The specific driver is NETwNs64.sys
As for which particular installation program, use this link to determine which wireless card you have installed: ASUSTeK Computer Inc. -Support-
Please make sure that you let us know the PCI\VEN_ and DEV_ characters

AlvitrValkyrie · 14 Jan 2012

Alright. Will continue in the morning. Rather late. Thanks for all your help! I'll report back soon

AlvitrValkyrie · 15 Jan 2012

usasma said:

The specific driver is NETwNs64.sys
As for which particular installation program, use this link to determine which wireless card you have installed: ASUSTeK Computer Inc. -Support-
Please make sure that you let us know the PCI\VEN_ and DEV_ characters

Under Network adapters, I have Hamachi Network Interface, Intel(R) Centurino(R) Advanced-N 6250 AGN, LAN9500 USB 2.0 to Ethernet 10/100 Adapter, Microsoft Virtual WiFi Miniport Adapter, and Realtek PCIe GBE Family Controller. Under Other Divices, I have Intel(R) Centrino(R) Advanced-N + WiMax 6250.

I am in a state of utter confusion. When it comes to NETwNs64.sys, google circlejerks me back to sevenforums. Which network adapter specifically am I trying to update the driver for? I can find all the drivers on the Asus and Intel sites, but I have no idea what I'm looking for, or rather, which adapter to select.

I can't even get network access to wireless when my laptop is off the dock. Speccy says I'm using LAN9500 USB 2.0 to Ethernet 10/100 Adapter. Nyarp?

AlvitrValkyrie · 15 Jan 2012

Wow. Asus is unimaginably horrible at packaging their drivers. That was one issue I didnt have with Dell.

usasma · 15 Jan 2012

I'm not real sure here. Please check the Hardware ID on the
Intel(R) Centurino(R) Advanced-N 6250 AGN
and
Intel(R) Centrino(R) Advanced-N + WiMax 6250

To do this, right click on the device and select "Properties"
Then select the Details tab - and in the dropdown box select "Hardware ID"
We need the 4 characters after the VEN_ and the 4 characters after the DEV_
This will (hopefully) tell us if they are the same device.

AlvitrValkyrie · 16 Jan 2012

Intel(R) Centurino(R) Advanced-N 6250 AGN
VEN_8086, DEV_0087

Intel(R) Centrino(R) Advanced-N + WiMax 6250
USB\VID_8086&PID_0186&REV_0000
uh o.o?