Regular BSOD when not using computer - new in last weeks


  1. Posts : 3
    Windows 7 Professional x64
       #1

    Regular BSOD when not using computer - new in last weeks


    After running perfectly for months, my Windows 7 x64 system started regularly crashing with a BSOD about a month ago. I leave my computer on, and when I was returning in the morning, I started noticing it was no longer running. I have been trying for several weeks to diagnose the issue. Interestingly, the computer has never crashed while I was using it, but always either overnight or when I was out of my home office.n

    The utility Who Crashed tells me the problem was probably caused by module ntoskrnl.exe or ntkrnlmp.exe. The bugcheck code is 0x9F. The reported error is DRIVER_POWER_STATE_FAILURE. I have tried various system restores to no avail. I have enclosed the log files after running DM Log Collector.

    Can anyone help me identify/fix the problem? A clean install would be a major project I was really trying to avoid right now. I will gladly provide any other information I can.

    My system is a Dell XPS 720 with an Intel Core2 Quad Q9450 @2.66 GHz., 8 GB RAM, C: drive is a Samsung 840 SSD. 2 more Raptor and 1 Seagate internal drives also installed.

    Thanks for any help.

    Tom Whedbee
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    The VIA Rhine III Compatible Fast Ethernet Adapter is too old to work properly with windows 7.
    Code:
        Image name: fet6x64.sys
        Timestamp:        Thu Jun 19 17:10:18 2008 (485A45A2)
    And it is rightly failing.
    Code:
    >[ 16, 2]   0 e1 fffffa800878f050 00000000 00000000-00000000    pending
              Unable to load image \SystemRoot\system32\DRIVERS\fet6x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for fet6x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for fet6x64.sys
     \Driver\FETNDIS
                Args: 00012200 00000001 00000004 00000002
    Search for any possible update to it in VIA Drivers Download - VIA Technologies, Inc.

    If available, apply it. If not, you may need to not use this device anymore.

    Let us know the results.
      My Computer


  3. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #3

    Thanks for your help! I could not update the VIA Rhine III ethernet card, so I purchased a new board -- from TP-Link (model TG-3269, PCI). It seemed that I went longer without a crash, but now I am getting regular BSODs as in my original post.

    I have included new log files. I don't know whether this is connected, but I have been having trouble with 3 recent Windows Updates (KB3033929, 3046049, and 3035131). I have run the System Update Readiness Tool which showed a number of problems. I have fixed several of these involving corrupt .cat and .mum files, but I cannot seem to fix problems with 7 .manifest files.

    One step forward, two steps back at the moment. Appreciate any help!

    Tom
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    twhedbee said:
    I purchased a new board -- from TP-Link (model TG-3269, PCI).
    Not seeing it there, but there is a Broadcom NetXtreme Gigabit Ethernet - NDIS 6.0 Running.

    Though this BSOD was caused by Realtek onboard LAN.
    Code:
    >[ 16, 2]   0 e1 fffffa80087e2050 00000000 00000000-00000000    pending
              Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
     \Driver\RTL8167
                Args: 00012200 00000001 00000004 00000002
    And this is very old, too.
    Code:
        Image name: Rt64win7.sys
        Timestamp:        Fri Jun 10 12:03:15 2011
    Update it from Realtek .... get the fourth item of the list (that is the "Win7 and Server 2008 R2 Auto Installation Program" one) and install it.

    One more thing you need to do, that is to free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus and Ipoint.exe.
    5. Apply > OK
    6. Accept then restart.

    Report us for any further BSOD after doing these two.
      My Computer


  5. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #5

    Thanks once again, Arc. I had a little trouble installing the new driver for the new TP-LINK network card (which used the Realtek driver) but was finally able to get it done successfully. I could never have found the latest driver without your link; the TP-LINK site's latest driver was at least a year older.

    I have my fingers crossed, but I have not had any BSOD crashes for about 5 days now. I'm hoping you led me through a successful fix. Consider this "case closed" unless you hear something from me in the next couple of days.

    Once again, I am very appreciative of your time and help. At the risk of sounding like the kid who asks the magician how he did his tricks, can I ask how you identified the errant driver from the minidump files? Particularly, where did those bits of code you inserted in your messages come from?

    Tom
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    twhedbee said:
    I have my fingers crossed, but I have not had any BSOD crashes for about 5 days now. I'm hoping you led me through a successful fix. Consider this "case closed" unless you hear something from me in the next couple of days.
    No problem, Tom. We will consider this case as closed as you wanted. If you get any further issue, unmark it and continue here.

    twhedbee said:
    Once again, I am very appreciative of your time and help. At the risk of sounding like the kid who asks the magician how he did his tricks, can I ask how you identified the errant driver from the minidump files? Particularly, where did those bits of code you inserted in your messages come from?

    Tom
    I trained myself (with the help of my senior debuggesr) to read the dump files using Windbg program. If you can read it, it is not any magic. It may take a time and effort, will need a good practice as well, but at the end it works.

    There are some good articles here: https://www.sevenforums.com/crash-lockup-debug-how/ .... you may go through these if you are interested. If it draws your interest, continue with us, see how others are doing it, and take some baby steps initially. Gradually you will understand the rest. :)
      My Computer


 

  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 06:15.
Find Us