Random BSOD's, tried most things

[Yajiro]

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.

 

[Arc]

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.

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
[COLOR=Red]Probably caused by : epfw.sys[/COLOR] ( 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.

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
[COLOR=Red]Probably caused by : snapman.sys[/COLOR] ( 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.

 

[Yajiro]

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?

 

[Arc]

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.

 

[Yajiro]

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.

 

[Yajiro]

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.

 

[Arc]

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

 

[Yajiro]

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

 

[Arc]

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

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

 

[Yajiro]

Alright, here is the latest zip file.

 

[Arc]

Nothing very special is obtained from the files; other than memory error, but there hints to network, storage, storage controller and display failure.

These failures may be caused by the memory corruption, or by some virus infection.

Do two more things.

Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

And, do another run of 8 passes of memtest86+, with the version 4.20. Because, most of the senior members with ample experience finds that the latest version fails to detect errors in some cases.

If nothing is found, 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

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any, as per the Blue Screen of Death (BSOD) Posting Instructions.

 

[Yajiro]

I ran TDSSKiller and Windows Defender Offline (full scan), both were clean. I ran memtest86+ 4.20 for 8 passes, no errors. I've run Driver Verifier for 24 hours without a BSOD.

 

[Arc]

I ran TDSSKiller and Windows Defender Offline (full scan), both were clean. I ran memtest86+ 4.20 for 8 passes, no errors. I've run Driver Verifier for 24 hours without a BSOD.

Good.

Let us see what it comes out later.

 

[Yajiro]

My computer has been on 14 days without a BSOD. I'd say it appears to be fixed. I even left Driver Verifier running the whole time rather than restarting after 24 hours. The only thing I've done other than uninstall ESET Smart Security and Acronis True Image is update my nvidia drivers again and re-install my realtek network driver again since there seemed to be an odd 60 second delay after restarts before the network adapter would connect to the internet.

I'm going to try upgrading and re-installing my Acronis True Image and see how that goes for 2 weeks. After that I might give ESET Smart Security another try. Though I suppose I have no issue using Windows Firewall and Microsoft Security Essentials.

Thanks for all the help Arc.

 

[Yajiro]

It appears I will never get this problem fixed despite having had my computer running 18 days with Driver Verifier. The only thing I did after those 18 days was turn off Driver Verifier and restart, update my nvidia graphics driver from 334.89 to 335.23 and restart, and then get the latest windows updates and restart. I had 2 BSOD's, both were either as I was cloning my computer monitor to my TV or shortly after. I figured it was the new nvidia drivers so I used DDU in safemode to uninstall 335.23 and then re-installed 334.89. But after almost 2 days I had a BSOD after uncloning my TV from my computer monitor.

 

[Arc]

It is another stop 0x1A BSOD without any adequate reason.

Driver verifier did not catch anything, as you said.
RAM is not failing.

So only one thing remains there, that is system services. Activation hacks may cause it. Apparently an OEM ultimate license on a retail board is a mere possibility; But, as you edited some data in the uploaded zip (in the systeminfo.txt file), it is difficult to take decisions in this line.

Post a report following http://www.sevenforums.com/windows-...n-issue-posting-instructions.html#post1957831 ..... and dont alter/edit any part of the report.

 

[Yajiro]

Yeah I did remove the product ID from the systeminfo.txt, which I know is differant than the product key but I just don't like posting information related to the key. But there is nothing wrong with windows activation. My computer has never had a virus or been hacked. Plus I've run system file checker dozens of times and have done a repair install as well. I bought my copy of windows 7 at the same time as another family member who has almost the same hardware as me and they've had no BSOD issues or my strange svchost.exe memory leak problem.

I think I just need to try a fresh install again. I apparently have to do it anyways for the svchost.exe memory leak problem since nothing has fixed it and I can't use IE11 without svchost.exe using up to 1GB+ of ram in days.