BSOD on firefox, chrome and driver booster

[jeroenlucassen]

Hi all,

Without having changed anything on my pc that i build myself a few years ago, it seems im having a few BSOD lately. I tried running driver booster to repalce outdated drivers, tho the problem continues. I configured w7 to log a kernel dump. I ran SF diagnostics and attached the zip file. Hope u guys can help me out.

Jeroen

 

[Arc]

Hi jeroenlucassen.

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 memtest86+ 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.
________________________________________________________________________________________

BugCheck 1A, {[B]41201[/B], fffff6800005a228, d9, fffffa800ff1bd90}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )

Followup: MachineOwner
----------------------------------------------------------------------------
BugCheck 1A, {41790, fffffa800a4abdc0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

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

 

[jeroenlucassen]

Hi,

Thanks for the fast responce. I ran driver verifier. Systems crashed twice, only 5 min in run. I attached the new SF diagnostics.

 

[Arc]

Driver verifier did not catch any driver as failing (but that may not be the final idea about drivers).

Better you run memtest at first and let us know the results.

BugCheck 3B, {c0000005, 0, fffff8800a541e90, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )

Followup: MachineOwner
---------------------------------------------------------------------------
BugCheck 44, {fffff9802043cee0, 346, 0, 0}

Probably caused by : Npfs.SYS ( Npfs!NpFsdWrite+76 )

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