BSOD seemingly random most today are with FireFox open

Arc · 07 Mar 2015

snave said:

Thanks, Bear. Heres the two most recent .dmp files, one from today.

Blue Screen of Death (BSOD) Posting Instructions

snave · 08 Mar 2015

ICITLOL: Thanks.
No overclocking, wouldn't know where to start!
scannow run in elevated mode, nothing found.
chkdsk /F /R run with no errors.
I removed AVG at the beginning of this case as instructed by ARC, and not gone back.

snave · 08 Mar 2015

ARC: Sorry, DB log collector tool output enclosed here.

Arc · 08 Mar 2015

I am having symbol error in your dumps.

That may have two explanations. Either some problem from the MS symbol server (less possible because all other peoples dumps are fine) or it is a third party driver failing in your system that is having private symbol not accessible by other people.

In that situation it will be best to 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.

snave · 08 Mar 2015

ARC: DV enabled as requested. After enabling, the instructions say to reboot which I did. It had a BSOD on the way back up. I'll let it run a few hours now to see if there are any more occurrences.
I must say I am really impressed by the amount of support and knowledge I see on this forum. You guys are awesome.

snave · 08 Mar 2015

ARC: Two occurences since I turned on DV, both should be captured in this DM log collection. I've turned DV back off now.

Golden · 08 Mar 2015

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {1f0, 2, 0, fffff80002c989b5}

Probably caused by : CI.dll ( CI!A_SHAUpdate+60 )

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

Is Windows 7 completely updated?

Did you scan for rootkits as recommend previously?

snave · 08 Mar 2015

Golden: The following is in chronological order to the best of my memory:
(before opening case)
- run memtest64 overnight, no problems detected;
- run MBAM;
(open case on this forum)
- Uninstall AVG using the provided tool;
- Run anti rootkit;
- Run windows defender;
- Check registry for any AVG entry (none):
- run scannow;
- run a deep chkdsk;
- enable driver verifier.

edit to add: Windows is up to date, just installed 3008137 (I think that was the one anyway).

Golden · 08 Mar 2015

OK. Presumably TDDSKiller found nothing? Is Windows updated?

snave · 08 Mar 2015

Golden: Yes - Windows is up to date, just installed KB 3006137 (not 8137 as I said above).
I rebooted it after the install, it came up - I opened FF to update this - and It BSOD'ed again.