Multiple BSOD and crashes after windows reinstall

Quintet2448 · 22 Feb 2015

I had issues with BSOD and freezes (screen frooze couldn't do anything sound repeated last thing played), and restarts without any warning or blue screen. I have re-installed windows in the hope this would stop this, and though they are less regular I still have these errors. I have been able to fix a few of the these by updating drivers but the most recent 5 I have no idea how to solve. I have run memtest86+ for 8 passes, all drivers are up to date to the best of my knowledge, I have installed all windows updates, used chkdsk/f, and sfc.exe/scannow and nothing has returned any results. I do not overclock and the temperatures on my cpu and gpu are normal. Any ideas??? Thanks for any help

Arc · 22 Feb 2015

Code:

BugCheck 1000007E, {ffffffff80000003, fffff8800ca30850, fffff88003370098, fffff8800336f8f0}

Probably caused by : SRTSP64.SYS ( SRTSP64+2850 )

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

Driver Reference Table - SRTSP64.SYS

Code:

BugCheck 1E, {ffffffffc0000005, fffff8800d8ad302, 1, 100000007}

*** WARNING: Unable to verify timestamp for BHDrvx64.sys
*** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
Probably caused by : BHDrvx64.sys ( BHDrvx64+41302 )

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

Driver Reference Table - BHDrvx64.sys

Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Let us know for any further BSOD after doing it.

Quintet2448 · 22 Feb 2015

Ok I am unsure whether that is wise as I have only recently renewed my license and I have never had an issue with it before (Year and a half of use). Could Norton cause the ntoskrnl.exe and fltmgr.sys errors?

Arc · 23 Feb 2015

Could Norton cause the ntoskrnl.exe and fltmgr.sys errors?

We see it in this section of the forums almost everyday.

Quintet2448 · 23 Feb 2015

What confuses me is I have norton on this pc before with no problems until 3ish months ago (no hardware or software changes that I can think of)

Arc · 23 Feb 2015

Hi mate.

I am not forcing you into anything. You posted your issue. I just interpreted the dumps to detect the issue and suggested some precautionary/remedial actions.

The rest is totally on you. You are totally free to accept or reject the suggestions.

From my part, if you dont materialize the suggestions then I have nothing more to do. So let me know your stand about it so that I can decide whether I will continue with you or not.

There are 332,047 members in SF. So if not me, somebody else will help you with your issue.

Quintet2448 · 23 Feb 2015

Sorry man, I just thought it was odd that I hadnt had issues for such a long usage, and now this happens.
I appreciate your help and will give uninstalling norton a go. Will post back here if I continue to have the same issues

Quintet2448 · 23 Feb 2015

So I uninstalled norton and within 2 hours I had another BSOD caused by a system service exception with fltmgr.sys . I'm now completely stumped as to what is causing this, any ideas?

Layback Bear · 23 Feb 2015

I recommend following his instruction.

Also remember that you may have more than one problem and it will take logs and the sharp eye of someone like Arc to guide you along.

You wonder why Norton worked so long and then started causing problems after you got the new version. That is your answer. The new version does not get along with your system. Some other members do have the same problem with Norton.

We don't know why Norton causes problems. We just know that it does and leaves that information in the logs Arc looks at.

Now I will get out of the way and let Arc and you continue with a fix.

Arc · 24 Feb 2015

Two 0x3B BSODs with two different causes.

Code:

BugCheck 3B, {c0000005, fffff88006123986, fffff8800c19da60, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VidMmDestroyAllocation+46 )

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

Code:

BugCheck 3B, {c0000005, fffff880010f418e, fffff8800bc3ea30, 0}

Probably caused by : fltmgr.sys ( fltmgr!FltpPerformPostCallbacks+26e )

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

A stop 0x3B mostly refers to misbehaving system files (mostly caused by non updating the OS), a device driver malfunctioning or a failing RAM. As there are two different causes, it is hard to conclude and go for anything specifically at this stage.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

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.