Various BSOD in random situations

TygersTail · 20 Jun 2014

Good afternoon,

I'm requesting some help with this build I have. I was upgrading the motherboard and RAM in a Cyberpower. I have been running into various issues for the last 48 hours and I thought I had solved them all. Now I'm getting BSOD every so often and I'm unsure as to why.

I'll attach my information and anything else if requested.

The first bluescreen encounter was a ntfs.sys while verifying game integrity via Steam.
The second I didn't get a good look at, but I was just browsing the web while Steam was downloading.
So, maybe it's Steam? I had uninstalled and re installed it after the first BSOD

I would appreciate any help as this whole process has just been a nightmare for me.
I had reformatted the boot drive when I put in the new motherboard.

Thanks,
Tyger

Arc · 20 Jun 2014

Hi TygersTail.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us now the result.
_______________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

Followup: MachineOwner
---------

TygersTail · 23 Jun 2014

Okay, I did that and it certainly took a while. No errors through 8 passes, however I noticed my temperature was sitting at an inappropriate 79°C. I thought maybe this was an error or maybe I messed something up or maybe the cpu/heatsink weren't sitting right.

So I cleaned the heatsink/cpu and reapplied thermal paste. It now idles in the 50°C ranges (high 50s). Haven't had a bluescreen since. Is it probable that this was the root cause of my problems?

Arc · 24 Jun 2014

TygersTail said:

Okay, I did that and it certainly took a while. No errors through 8 passes, however I noticed my temperature was sitting at an inappropriate 79°C. I thought maybe this was an error or maybe I messed something up or maybe the cpu/heatsink weren't sitting right.

So I cleaned the heatsink/cpu and reapplied thermal paste. It now idles in the 50°C ranges (high 50s). Haven't had a bluescreen since. Is it probable that this was the root cause of my problems?

Very well done!

High temps can cause any sort of odd issues. You rightly found it and have taken the proper action.

Now observe the situation over a reasonable time.

TygersTail · 25 Jun 2014

Well, I thought I solved the issue. It went a few days without a problem and then BAM BSOD System_Service_Exception.

So, what's next to test? My video card? Did I burn a bad Win7 ISO? Is it (hopefully not) my motherboard?

Arc · 26 Jun 2014

The System_Service_Exception (0x3B) BSODs are very unpredictable and sticky in nature.

And apparently we are lucky that we have a prima facie cause of it. The filter service of the antivirus is causing storage malfunctioning, which is very common.

Code:

fffff880`0bc36b60  fffff880`0188deb4Unable to load image \SystemRoot\system32\DRIVERS\avgmfx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgmfx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgmfx64.sys
 avgmfx64+0x2eb4
-----------------------------------------------------
fffff880`0bc362e8  fffff880`012c1bf3*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
 Ntfs+0xacbf3

Description here: Driver Reference Table - avgmfx64.sys

At this point I would suggest you to uninstall AVG. Uninstall AVG using AVG Remover. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Let us know the situation after applying this change.

TygersTail · 26 Jun 2014

Arc, I don't know how you did that, but you're a wizard.

I'm going to post another log I might have missed from the 24th (while I was at work) if you don't mind (and if its not too much to ask)... I am curious to see it was AVG's fault as well. I apologize if I seem frantic. It has just been one hell of a process trying to diagnose this.

No doubt part of the problem was the temperature, but now this second part I'm nervous about.

I have followed the instructions and will run for a few days as I normally would.

Arc · 26 Jun 2014

If you know how it do it, it is extremely easy. :)

This one catches the Ntfs/Storage malfunctioning ....

Code:

fffff880`0334c518  fffff880`0121fa16*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
 Ntfs+0x9a16

.... but failed to catch what is behind it.

TygersTail · 27 Jun 2014

Feels like program crashes and bluescreens are getting less frequent at least. However, its still concerning that I'm experiencing them...

Document attached. I hope this one left some evidence for remedy.

Arc · 28 Jun 2014

Just same as the previous one.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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.