BSOD, no one specific error. 0x0000003b, 0x00000024, and more!

Hi imBurger.

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.

Let us know the result. That will decide the further course of action.
______________________________________________

Code:

BugCheck 19, {3, fffffa80082c0110, fffffa80082c0110, fffffb80082c0110}

Probably caused by : ntkrnlmp.exe ( nt!ExAllocatePoolWithTag+140b )

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

Code:

BugCheck 3B, {c0000005, fffff800032a253c, fffff8800591af00, 0}

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

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

I hope you ran it for 9 consecutive passes?

If it did not show any error, enable Driver Verifier to monitor the drivers, as the next step.

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.

Well, then right now we dont have any more place to look at.

Your previous BSODs were memory caused ones. That means, either it is a physical RAM or any driver passing bad info to the RAM. We have checked both the possibilities with no definite results.

Now let us wait and see how it goes. If there are further BSODs, let us see the logs, and expect that those will give some more finite information about the causes of the BSODs.

imBurger said:

Understood. That kind of stinks, was hoping to fix this problem. Would running verifier or the memtest again possibly yield some results?

You may try. It may yield a result. Sometimes a second run may be helpful.