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

Page 1 of 3 123 LastLast

  1. Posts : 32
    Windows 8.1 Pro
       #1

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


    Basic System Specs:

    - x86 (32-bit) or x64 ? x64
    - the original installed OS on the system? No, shipped with Vista, upgraded to 7.
    - an OEM or full retail version? Full Retail Verison


    - What is the age of system (hardware)? Three years, one month, and 11 days old.
    - What is the age of OS installation (have you re-installed the OS?) Around one month old.

    ZIP folder with PERFMON HTML file and Windows_NT6_BSOD_jcgriff2 folder attached.

    OK,

    I'm a total noob on this forum, so I tried to follow the instructions on posting.

    Firstly, when you read PERFMON, it'll say my HDD is failing. I know that. I know it's stupid to use a failing HDD, but my data is backed up, and I get my Mac on Saturday. Anyways,

    Last night, around 1:30 AM, I got up to shut down my computer, it was on, and in the same room as me, and I wanted sleep. So, I went to the start menu, and saw the update icon next to shut down. I shut down the machine instead of sleeping, so it could update. I turn off the monitor to go to sleep. I then hear the fans ramp up, then slow down, and the computer "click" like it does when it shuts off. But, the fans were still running. I turned on a lamp, and sat down. I turned on the monitor, to be facing a big fat BSoD. It didn't give me an exact message of what happened, just a STOP error code. The STOP error code was 0x0000001e, and the BCCode is 1e. I haven't installed any new hardware, and the only software I've installed was Apple's AirPort Utility, for my new AirPort Extreme Base Station. Below you can find a copy of the window I saw when I restarted.


    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 1033

    Additional information about the problem:
    BCCode: 1e
    BCP1: 0000000000000000
    BCP2: 0000000000000000
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\021612-26676-01.dmp
    C:\Users\William\AppData\Local\Temp\WER-69623-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt


    Thanks for your help!

    - William
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    Failing hard drives can cause BSOD's. But most importantly - they can die without any notice at all. Backup all your stuff immediately!!!

    Win7 doesn't like wireless USB devices. You have a Compact Wireless-G USB Network Adapter with SpeedBooster ver.2
    Here's my rant about these devices:
    I do not recommend using wireless USB devices. Especially in Win7 systems.
    These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
    Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
    An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
    The memory dump points to networking stuff - and your networking drivers (both wired and wireless USB) are from 2008. This means that it's most likely that the wireless USB drivers are causing the error (although the wired drivers are suspect also).

    Please update all of your networking drivers. Be sure to use ONLY Win7 compatible drivers.

    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)
    vpchbus.sys           Sat Nov 20 06:35:38 2010 (4CE7B28A)
    MpFilter.sys          Wed Apr 06 16:07:29 2011 (4D9CC801)
    MDFSYSNT.sys          Mon Oct 03 17:52:38 2011 (4E8A2EA6)
    MDPMGRNT.SYS          Mon May 09 12:37:37 2011 (4DC81851)
    CBDisk.sys            Wed Jan 13 04:15:47 2010 (4B4D8F43)
    WmXlCore.sys          Tue Apr 27 16:09:26 2010 (4BD74476)
    vpcvmm.sys            Sat Nov 20 06:35:48 2010 (4CE7B294)
    NisDrvWFP.sys         Wed Apr 06 16:08:53 2011 (4D9CC855)
    vpcusb.sys            Sat Nov 20 06:35:31 2010 (4CE7B283)
    usbrpm.sys            Sat Nov 20 06:37:19 2010 (4CE7B2EF)
    vpcnfltr.sys          Sat Nov 20 06:35:20 2010 (4CE7B278)
    e1y60x64.sys          Mon Aug 18 17:45:05 2008 (48A9ED61)
    WmBEnum.sys           Tue Apr 27 16:10:19 2010 (4BD744AB)
    HCW85BDA.sys          Tue Jul 14 16:46:46 2009 (4A5CEEB6)
    WUSB54GSCV2_AMD64.sys Tue Jan 08 15:52:33 2008 (4783E291)
    nvlddmkm.sys          Sat May 21 00:07:04 2011 (4DD73A68)
    nvBridge.kmd          Fri May 20 23:58:23 2011 (4DD7385F)
    
    http://www.carrona.org/drivers/driver.php?id=vmbus.sys
    http://www.carrona.org/drivers/driver.php?id=winhv.sys
    http://www.carrona.org/drivers/driver.php?id=amdxata.sys
    http://www.carrona.org/drivers/driver.php?id=vpchbus.sys
    http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
    http://www.carrona.org/drivers/driver.php?id=MDFSYSNT.sys
    http://www.carrona.org/drivers/driver.php?id=MDPMGRNT.SYS
    http://www.carrona.org/drivers/driver.php?id=CBDisk.sys
    http://www.carrona.org/drivers/driver.php?id=WmXlCore.sys
    http://www.carrona.org/drivers/driver.php?id=vpcvmm.sys
    http://www.carrona.org/drivers/driver.php?id=NisDrvWFP.sys
    http://www.carrona.org/drivers/driver.php?id=vpcusb.sys
    http://www.carrona.org/drivers/driver.php?id=usbrpm.sys
    http://www.carrona.org/drivers/driver.php?id=vpcnfltr.sys
    http://www.carrona.org/drivers/driver.php?id=e1y60x64.sys
    http://www.carrona.org/drivers/driver.php?id=WmBEnum.sys
    http://www.carrona.org/drivers/driver.php?id=HCW85BDA.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvBridge.kmd

    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021612-26676-01.dmp]
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Debug session time: Thu Feb 16 01:18:35.222 2012 (UTC - 5:00)
    System Uptime: 0 days 23:30:33.063
    Probably caused by : NETIO.SYS ( NETIO!RtlGetNextExpiredTimerWheelEntry+ea )
    BUGCHECK_STR:  0x1E_0
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x1E_0_NETIO!RtlGetNextExpiredTimerWheelEntry+ea
    Bugcheck code 0000001E
    Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
    BiosVersion = 1.1.4
    BiosReleaseDate = 12/21/2009
    CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
    MaxSpeed:     2670
    CurrentSpeed: 2660
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    Uptime was 23 hours and related to netio.sys. Usually that means your malware application is the true cause.

    What malware app are you using?

    EDIT:

    Just noticed a 3 year old network driver
    Code:
    WUSB54GSCV2_AMD64.sys    1/8/2008 3:52:33 PM    fffff880`09b65000    fffff880`09ba7000    0x00042000    0x4783e291                            
    e1y60x64.sys    8/18/2008 4:45:05 PM    fffff880`04a6a000    fffff880`04ab3000    0x00049000    0x48a9ed61
    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
      My Computer


  4. Posts : 32
    Windows 8.1 Pro
    Thread Starter
       #4

    Linksys said that the newest drivers they have are the ones I have installed. The Windows Vista x64 drivers are the newest ones. They don't have Win7 drivers. I know that the HDD is failing, I backed it up. I am using Microsoft Security Essentials. I guess I'll go buy a PCI-E WiFi Card. So, basically, the network driver caused the BSOD?
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    The memory dump shows that there was a Windows networking driver that crashed.
    We presume that the Windows drivers are OK, because they are protected by the Windows System File Checker.

    Then, the wireless USB device is more prone to having problems than the wired networking device - so it's most likely that the wireless USB device drivers are at fault (also, there's no newer drivers for it, but there are newer drivers for the wired network device)

    You can try to force the memory dumps to reveal the actual name of the faulting driver by running Driver Verifier according to these instructions: Driver Verifier Settings
      My Computer


  6. Posts : 32
    Windows 8.1 Pro
    Thread Starter
       #6

    New development. I just woke up, to find the system on, and the fans and CPU way louder than normal, but, I have no video signal, so I can't see what's going on. Could this be from Driver Verifier? Is it safe to shut the system down and reboot?
      My Computer


  7. Posts : 5,705
    Win7 x64 + x86
       #7

    Shut it down if it's acting out of the ordinary.
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    Driver Verifier stresses the drivers. Some people notice the system lagging, others don't.
    While it seems theoretically possible, I can't recall having ever seen it do this.
      My Computer


  9. Posts : 32
    Windows 8.1 Pro
    Thread Starter
       #9

    I logged back in, and got the "Windows recovered...." window. I was a doofus and accidentally closed it. It said it was a C9 BSoD, and here's what the boys in Redmond said about BCCode C9. "STOP error 0xC9 is the STOP code code for all Driver Verifier I/O Verification violations. STOP code 0x000000C9 may also display "DRIVER_VERIFIER_IOMANAGER_VIOLATION" on the same STOP message."

    I'll make a post in 5 minutes with the ZIP when it's ready.
      My Computer


  10. Posts : 32
    Windows 8.1 Pro
    Thread Starter
       #10

    Here's your ZIP with all your debugging files! :)
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 17:23.
Find Us