BSOD Random Crashes Every couple of weeks

[darkstar9454]

Hello, I'm posting here because my computer will randomly bluescreen (ntoskrnl.exe) and I can not seem to figure out why. I have checked that all the right options are selected in my BIOS, done memory tests on my ram, updated all drivers and even re installed windows. At one point I did have some corrupt ram but I replaced it, so if that comes up in any of the test results it should no longer be an issue.

By posting here I was hoping that somebody could help me figure out the issue. I will happily post anymore information that is needed to fix the problem.

Thank you very much for your assistance in advance =)

 

[Arc]

Hi darkstar9454.

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.

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 109, {a3a039d89c83b5f5, b3b7465eef00855b, fffff800037624f0, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------