BSOD whilst online 4 times in a row

Hi ramsdenjamie85.

Can you uninstall Trusteer Rapport, at least as a test? I know that the program is important, but this test is important, too.

Let us know how the computer is running without Rapport. We have to decide about our next course of actions after seeing the results.
_________________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff8a032a2f680, fffff8a032a2f480, fffff8a032a2f680}

Unable to load image \??\C:\ProgramData\Trusteer\Rapport\store\exts\RapportCerberus\baseline\RapportCerberus64_59849.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RapportCerberus64_59849.sys
*** ERROR: Module load completed but symbols could not be loaded for RapportCerberus64_59849.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c96 )

Followup: Pool_corruption
---------

You know how important the program is.

If it can be isolated that the crash dump is reporting correctly and the BSODs are truly being caused by it, contract with the developer and ask for solution, as a consumer.

So this time is to observe the situation. Let us know how things are going.

Both of them are giving some hints of memory failure. It may be either the phycial memory or any driver passing bad information to the memory. So ......

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 at all, 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.
____________________________________________________________________________________

Code:

BugCheck 1A, {41790, fffffa80068f7840, ffff, 0}

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

Followup: MachineOwner
----------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80002f24cec, fffff88008b3ee50, 0}

Probably caused by : memory_corruption ( nt!MiCaptureProtectionFromProto+1c )

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

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
It is a motherboard issue. The particular slot is bad.

But, you need to give a time to the tests. Errors must not to show up instantly.

Good news that it is running smoothly :)

Let us know for any further issue.