Random BSOD's, tried most things

Page 1 of 2 12 LastLast

  1. Posts : 24
    Windows 7 Ultimate SP1 x64
       #1

    Random BSOD's, tried most things


    I installed a fresh copy of Windows 7 Ultimate x64 a few months ago due to BSOD and update issues with a previous install. I'm not sure if I'm having a continuation of the same problems or not. I thought it was most likely related to my OCZ Gold 2GB x 6 ram, which 3 sticks were 1600 and 3 sticks were 2000. I replaced them with G.SKILL Ripjaws 4GB x 3 and did the fresh install of Windows 7 around the same time. I did have a bad stick of G.SKILL and had it replaced and did another Memtest86+ pass to confirm it was fine this time.

    Most of the BSOD dump files blame random things like ieexplorer and firefox I believe. I tried the simplest solution of uninstalling and re-installing the nvidia drivers. I still got more BSOD's. Next time I uninstalled the nvidia drivers and then ran DDU to make sure everything was removed. Then later I started with driver verifier. At first it blamed an nvidia driver so I uninstalled the nvidia drivers again, ran DDU in safemode this time, then installed only the graphics driver, physx driver, and hd audio driver.

    Next driver verifier blamed my ESET smart security. I uninstalled and reinstalled that. Next it blamed my acronis true image. I uninstalled and reinstalled that. After that driver verifier would BSOD before windows login screen, an issue I had on my last windows 7 install. It would only flash the BSOD and not leave a dump file.

    I ran Memtest86+ for 8 hours which only completed 3 passes, no errors. I'm not sure if I should check each individual stick in each slot, I thought I'd wait to see what direction others thought I should go first. I also ran checkdisk which said there were no bad sectors. Though I didn't think there would be since I use HD Tune to check my hard drives after a seagate 1.5TB started failing.

    At this point I'm not sure if I need to do more ram tests, stress the graphics card, or try replacing ESET Smart Security with MSE. Though I've been using ESET Smart Security for years and would hate to have to replace it. I have family members that use it and have almost the same setup and have no issues.

    I've also done sfc /scannow quite a few times and also a repair windows 7 install trying to fix a possibly unrelated svchost.exe memory leak problem related to network store interface service and internet explorer (nsi memory leaks fixed yet? - Microsoft Community). Which I've uninstalled and reinstalled the latest realtek network driver quite a few times for that. Still no fix for that besides another fresh install of Windows 7 apparently.

    So I'm hoping someone more of an expert than I can help me figure this out. I usually use BlueScreenView and then WinDbg to look at the BSOD dump files. My last 2 BSOD's were for NETIO.SYS and fitmgr.sys. Which sounded like it could point more towards ESET this time.
    Last edited by Yajiro; 21 Feb 2014 at 04:54.
      My Computer


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

    Hi Yajiro.

    You debugged the issue in almost the correct way. But the argument you stand for not uninstalling ESET is not very valid. Every computer is different. And ESET, though not very frequently, but contributes in BSODs that we have experienced many a times.

    ESET is causing BSODs here.
    Code:
    BugCheck A, {0, 2, 1, fffff800030efbe6}
    
    *** WARNING: Unable to verify timestamp for epfw.sys
    *** ERROR: Module load completed but symbols could not be loaded for epfw.sys
    Probably caused by : epfw.sys ( epfw+2069d )
    
    Followup: MachineOwner
    ---------
    So, why dont you uninstall it, at least as a test? In the mean time, use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.


    Acronis is causing BSODs, too.
    Code:
    BugCheck CC, {fffff980129f8fe0, 0, fffff800035772aa, 0}
    
    *** WARNING: Unable to verify timestamp for snapman.sys
    *** ERROR: Module load completed but symbols could not be loaded for snapman.sys
    
    Could not read faulting driver name
    Probably caused by : snapman.sys ( snapman+26235 )
    
    Followup: MachineOwner
    ---------
    Uninstall it, too.

    There may be some other things. Specially memory. 3 passes are not enough. To make it sure that the RAM is not failing, run memtest86+ for at least 8 passes.

    Let us know the results.
      My Computer


  3. Posts : 24
    Windows 7 Ultimate SP1 x64
    Thread Starter
       #3

    Alright, I'll uninstall ESET Smart Security and install MSE and MBAM and use windows firewall to test. I'll uninstall Acronis True Image as well. Also, while my ESET is all up to date, my Acronis True Image is 2013. It didn't look like updating to 2014 was worth it so much but do you think the latest version of that could possibly help? I use it for my full hard drive backups and run weekly incremental backups.

    For Memtest86+ I might run the 8 passes on 1 stick at a time while sleeping over 3 nights. I don't have a tablet or laptop so it wouldn't be fun not using my computer for 16+ hours testing 3 sticks at once. Unless it really needs to be tested with all 3 sticks?
      My Computer


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

    About Acronis, updating is a worthy try.

    About memtest86+, there is a specific methodology to obtain at the decision; and that needs to run the test with all the installed RAM on as the beginning.

    The rest is obviously on you. You may not follow the standard ways. But that will complicate the troubleshooting procedure only.
      My Computer


  5. Posts : 24
    Windows 7 Ultimate SP1 x64
    Thread Starter
       #5

    I just had another BSOD after nearly 5 days of uptime. I haven't run memtest86+ yet since I wanted to check how stable it was after the uninstall of ESET Smart Security and Acronis True Image. The dump file blamed iexplore.exe and ntkrnlmp.exe. I guess it's time to run the memtest86+ since I don't think the dump file was useful.
      My Computer


  6. Posts : 24
    Windows 7 Ultimate SP1 x64
    Thread Starter
       #6

    Here are the dump files for my last 2 BSOD's and the results of memtest86+. Which I ran it for 8 passes and there were no errors.
      My Computer


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

    Post it following the BSOD posting instructions including all the files in the zip?
      My Computer


  8. Posts : 24
    Windows 7 Ultimate SP1 x64
    Thread Starter
       #8

    What? You want me to re-do the zip file in my first post? My last post included the latest information.
      My Computer


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

    Post it following the Blue Screen of Death (BSOD) Posting Instructions.

    Don't alter the original post. Add the data in the next post.
      My Computer


  10. Posts : 24
    Windows 7 Ultimate SP1 x64
    Thread Starter
       #10

    Alright, here is the latest zip file.
      My Computer


 
Page 1 of 2 12 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 15:45.
Find Us