BSOD 6 times, usually while Idle - ntoskrnl.exe

Page 2 of 3 FirstFirst 123 LastLast

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

    Entropy42 said:
    Yeah, from the crashes I submitted before, you said it was a hardware problem with my onboard NIC, but I disabled that and am still getting the crash, so I was hoping someone could look at the more recent crashes and see what they indicate the problem to be. I updated the previous post with the zip file from the SF tool, is that data uploaded wrong?
    Thanks for the help.
    The information obtained from the latest crash dump:
    Code:
    fffff880`035294f8  fffff880`07e7bd57Unable to load image 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
     Rt64win7+0x7d57
      My Computer


  2. Posts : 11
    Windows 7 Enterprise x64
    Thread Starter
       #12

    I'm not sure what that means, but it seems like its blaming my network drivers again. I uninstalled them and reinstalled the newest ones from Realtek's site (which I had already done, but maybe they've changed).

    Strangely, uninstalling/reinstalling the drivers caused my network card to claim that there was no network cable plugged in. It no longer recognizes the cable that I've been using for months, but is accepting a different cable.
      My Computer


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

    Yes, it means that the realtec NIC is still active and causing BSODs in he same way. And it nullifies your statement that realtek NIC is disabled, unfortunately.
      My Computer


  4. Posts : 11
    Windows 7 Enterprise x64
    Thread Starter
       #14

    I disabled the onboard NIC in BIOS, but had to install a PCI-E NIC in order to keep using my computer, it seems the new one also uses the Realtek chipset, and the same driver. The fact that I'm still getting the issue with a different NIC makes me think its a software rather than hardware issue though.
      My Computer


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

    Most possible.

    But it makes the situation complicated at the first look. Anyway, update the driver following post #2 and let us know for any further issue.
      My Computer


  6. Posts : 11
    Windows 7 Enterprise x64
    Thread Starter
       #16

    Yeah, unfortunately the driver update didn't fix it. BSOD after 4 days of uptime. Using "WhoCrashed" it says the last crash (and several before it) are due to ntoskrnl.exe, but that's the core of windows, so I guess it could be anything.
      My Computer


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

    Entropy42 said:
    Yeah, unfortunately the driver update didn't fix it. BSOD after 4 days of uptime. Using "WhoCrashed" it says the last crash (and several before it) are due to ntoskrnl.exe, but that's the core of windows, so I guess it could be anything.
    Post it following the Blue Screen of Death (BSOD) Posting Instructions.
      My Computer


  8. Posts : 11
    Windows 7 Enterprise x64
    Thread Starter
       #18

    Updated zip attached.
      My Computer


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

    Code:
    BugCheck D1, {fffff88041a86c9c, 2, 8, fffff88041a86c9c}
    
    Probably caused by : tcpip.sys ( tcpip!TcpPartitionGetNextExpirationTick+101 )
    
    Followup: MachineOwner
    ---------
    In short, it reports a network driver failure. No adequate reason of it, as your network driver is the latest version. Something else might be playing in the background.

    You need to enable driver verifier. But before enabling it, alter the display driver a bit, cause it is failing too.
    Code:
    fffff800`00b9c508  fffff880`07a46b36Unable to load image atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
     atikmpag+0x45b36
    Uninstall your installed latest version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    Lately we have seen a lot of issues with the latest 13.12 WHQL AMD Catalyst.

    Now enable Driver Verifier to monitor the drivers.
    Driver Verifier - Enable and Disable
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

       Information
    Why Driver Verifier:
    It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

    How Can we know that DV is enabled:
    It will make the system bit of slow, laggy.

       Warning
    Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

    If there is no points, make a System Restore Point manually before enabling DV.

       Tip



    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  10. Posts : 11
    Windows 7 Enterprise x64
    Thread Starter
       #20

    I did all of this and ran DV, selecting all non-MS drivers. The computer BSOD before the login prompt, both times with IRQL_NOT_LESS_EQUAL. It did not generate a log of the crash though. I am going through now and selecting smaller sets of drivers to try and find which driver caused me to be unable to boot. Is there a place I should be looking for the "results" of DV? Would it have recorded info about those crashes that is not a standard BSOD crash dump?
      My Computer


 
Page 2 of 3 FirstFirst 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 02:38.
Find Us