Windows 7: Random BSOD at night, error 0x0000001e, Updates possibly installing.

The Tehkwhiz · 18 Feb 2012

Quote: Originally Posted by usasma

Some people notice the system lagging, others don't.

Now that you mention it, the system was EXTREMELY laggy last night. I had Spotify open, and a Windows Virtual PC session with Win98, that only had 256MB RAM. I couldn't even open Google Chrome, it crashed every time I opened it! Even if I closed out of VPC, and rebooted the machine, it was laggy as heck!

usasma · 18 Feb 2012

Well, the memory dump blames a Windows driver - which wasn't tested for with our settings in Driver Verifier. What this means is that it's either a Windows problem (not real likely), or a hardware problem (which includes compatibility issues, low-level driver problems, and even malware).

IMO, it's due to the wireless USB device.
Try temporarily using a wired connection (and uninstalling/removing the wireless USB device) to see if that stops the BSOD's.

Please see the drivers below in RED. They are from 2008 - which was before Windows 7 was released. They must be updated. If you can't find updates, then they've gotta be removed from the system.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


vmbus.sys             Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys             Sat Nov 20 04:20:02 2010 (4CE792C2)
amdxata.sys           Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmXlCore.sys          Tue Apr 27 16:09:26 2010 (4BD74476)
MDFSYSNT.sys          Mon Oct 03 17:52:38 2011 (4E8A2EA6)
MDPMGRNT.SYS          Mon May 09 12:37:37 2011 (4DC81851)
MpFilter.sys          Wed Apr 06 16:07:29 2011 (4D9CC801)
CBDisk.sys            Wed Jan 13 04:15:47 2010 (4B4D8F43)
vmm.sys               Tue Feb 12 06:38:20 2008 (47B1852C)
e1y60x64.sys          Mon Aug 18 17:45:05 2008 (48A9ED61)
HCW85BDA.sys          Tue Jul 14 16:46:46 2009 (4A5CEEB6)
VMNetSrv.sys          Wed Jan 16 06:52:01 2008 (478DEFE1)
WmBEnum.sys           Tue Apr 27 16:10:19 2010 (4BD744AB)
WUSB54GSCV2_AMD64.sys Tue Jan 08 15:52:33 2008 (4783E291)
NisDrvWFP.sys         Wed Apr 06 16:08:53 2011 (4D9CC855)
MpNWMon.sys           Wed Apr 06 16:07:23 2011 (4D9CC7FB)
nvlddmkm.sys          Sat May 21 00:07:04 2011 (4DD73A68)
nvBridge.kmd          Fri May 20 23:58:23 2011 (4DD7385F)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021812-25006-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb 18 06:24:54.176 2012 (UTC - 5:00)
System Uptime: 0 days 6:10:09.129
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClasspPowerDownCompletion+26d )
BUGCHECK_STR:  0xc9_21a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_21a_CLASSPNP!ClasspPowerDownCompletion+26d
Bugcheck code 000000C9
Arguments 00000000`0000021a fffff880`016c42fd fffffa80`069f8110 00000000`00000000
BiosVersion = 1.1.4
BiosReleaseDate = 12/21/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2660
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

The Tehkwhiz · 18 Feb 2012

Quote: Originally Posted by usasma

Well, the memory dump blames a Windows driver - which wasn't tested for with our settings in Driver Verifier. What this means is that it's either a Windows problem (not real likely), or a hardware problem (which includes compatibility issues, low-level driver problems, and even malware).

IMO, it's due to the wireless USB device.
Try temporarily using a wired connection (and uninstalling/removing the wireless USB device) to see if that stops the BSOD's.

Please see the drivers below in RED. They are from 2008 - which was before Windows 7 was released. They must be updated. If you can't find updates, then they've gotta be removed from the system.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


vmbus.sys             Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys             Sat Nov 20 04:20:02 2010 (4CE792C2)
amdxata.sys           Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmXlCore.sys          Tue Apr 27 16:09:26 2010 (4BD74476)
MDFSYSNT.sys          Mon Oct 03 17:52:38 2011 (4E8A2EA6)
MDPMGRNT.SYS          Mon May 09 12:37:37 2011 (4DC81851)
MpFilter.sys          Wed Apr 06 16:07:29 2011 (4D9CC801)
CBDisk.sys            Wed Jan 13 04:15:47 2010 (4B4D8F43)
vmm.sys               Tue Feb 12 06:38:20 2008 (47B1852C)
e1y60x64.sys          Mon Aug 18 17:45:05 2008 (48A9ED61)
HCW85BDA.sys          Tue Jul 14 16:46:46 2009 (4A5CEEB6)
VMNetSrv.sys          Wed Jan 16 06:52:01 2008 (478DEFE1)
WmBEnum.sys           Tue Apr 27 16:10:19 2010 (4BD744AB)
WUSB54GSCV2_AMD64.sys Tue Jan 08 15:52:33 2008 (4783E291)
NisDrvWFP.sys         Wed Apr 06 16:08:53 2011 (4D9CC855)
MpNWMon.sys           Wed Apr 06 16:07:23 2011 (4D9CC7FB)
nvlddmkm.sys          Sat May 21 00:07:04 2011 (4DD73A68)
nvBridge.kmd          Fri May 20 23:58:23 2011 (4DD7385F)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021812-25006-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb 18 06:24:54.176 2012 (UTC - 5:00)
System Uptime: 0 days 6:10:09.129
Probably caused by : CLASSPNP.SYS ( CLASSPNP!ClasspPowerDownCompletion+26d )
BUGCHECK_STR:  0xc9_21a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_21a_CLASSPNP!ClasspPowerDownCompletion+26d
Bugcheck code 000000C9
Arguments 00000000`0000021a fffff880`016c42fd fffffa80`069f8110 00000000`00000000
BiosVersion = 1.1.4
BiosReleaseDate = 12/21/2009
CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2660
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

How am I going to get internet!? I don't have a wired connection, I'm on the second floor of my house! The router is in the basement!

usasma · 18 Feb 2012

Well, the easiest thing is to carry your computer down to the basement and put it next to the router for a couple of days.

If this proves that it's the wireless device, then you'll need to get a wireless device that plugs into your motherboard in order to have wireless upstairs.

The Tehkwhiz · 18 Feb 2012

Just got another C9 BSOD! It said the problem was with CLASSPNP.SYS. Photo below.

usasma · 18 Feb 2012

That's the same one that was blamed with the other memory dump.
We're sure that the Driver Verifier isn't pointing out a 3rd party driver - so it's time to shut it off.

To do this, open up Verifier and select "Delete existing settings", then click on "Finish"
Reboot the system for the changes to take affect.

The Tehkwhiz · 18 Feb 2012

Quote: Originally Posted by usasma

That's the same one that was blamed with the other memory dump.
We're sure that the Driver Verifier isn't pointing out a 3rd party driver - so it's time to shut it off.

To do this, open up Verifier and select "Delete existing settings", then click on "Finish"
Reboot the system for the changes to take affect.

If it's not a 3rd party driver, what do you think it is?

usasma · 19 Feb 2012

It's most likely a hardware error.
And the most likely piece of hardware is the wireless USB device.

The Tehkwhiz · 19 Feb 2012

Quote: Originally Posted by usasma

It's most likely a hardware error.
And the most likely piece of hardware is the wireless USB device.

Well, I guess I'll be buying a PCI-Express card then.

Do you have any recommendations? I would prefer a card with 802.11N. 5GHz is preferred, but not needed. I found this card on Newegg. Does this look good?

Rosewill RNX-N250PCe (RNWD-11005) Wireless Adapter IEEE 802.11b/g/n

Something that's under $30 would be preferred.

usasma · 19 Feb 2012

Don't just go out and buy stuff on my say-so! I'll be really embarrassed if it doesn't work!
Test it first by running it without the device - if that stops the BSOD's, then you can go out and spend money.

Frankly, I buy the cheapest wireless card that I can find - I don't need anything fancy.
I'd check in some Gamers forums to see what they recommend.

Windows 7: Random BSOD at night, error 0x0000001e, Updates possibly installing.

Random BSOD at night, error 0x0000001e, Updates possibly installing. problems?