BSOD while using computer normally.

[Damien324]

Would really appreciate some help here if possible, first time posting in this fourm and for a good reason I have no idea what is happening to my computer all I know is that it has something to do with NT Kernal & system I have uploaded a file for people to look at. Please it would be awesome if I could get some help

Also forgot to mention the symptons they are basically random crash dumps appearing here and there but becoming more frequent and also my computer just sometimes freezes and doesn't unfreeze at all

 

[Arc]

Hi Damien324.

The crash dumps are giving a hint of memory corruption. Not necessarily the physical RAM, but there is the chance of any driver is passing bad information to the memory, too.

Let us check both the possibilities one by one.

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.
______________________________________________

BugCheck 50, {fffffa880a2230b0, 1, fffff80002ec6f96, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ExpReleaseResourceForThreadLite+46 )

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

BugCheck 3B, {c0000005, fffff80002cf2ff3, fffff8800be3e8e0, 0}

Probably caused by : memory_corruption ( nt!MmCopyToCachedPage+223 )

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

 

[Golden]

Same person, same issue...not very smart to post the same issue across two related forums since we don't know whats been attempted.

Luckily the advice is the same - run MemTest86+.....not Memtest!

Decide which forum you want to be helped at, and then stick to it!

In desperate need of help with a BSOD