BSOD intermittantly - no new hardware

Hi DeeJay1.

There is memory corruption. Either the RAM is corrupt or any driver is passing bad information to the memory.

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, 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 1E, {ffffffffc0000005, fffff80002e5da69, 0, 88}

Probably caused by : memory_corruption ( nt!MiValidateImagePages+339 )

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

Code:

BugCheck A, {ffffff0000000048, 2, 1, fffff80002ec1929}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+109 )

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

DeeJay1 said:

I will change it again and see what happens.

Before that, do some additional tests.

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. You may change the RAM in this case.

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. Dont use this slot.

Well done, and right inference. :)

You need to get a new kit of RAM.

That's very good.

Let us know the situation after replacing the RAM.