Random BSOD while computer was idling KMODE_EXCEPTION_NOT_HANDLED

Hello all, wish I didn't have to post here but it seems the few times I visit this forum is to get help from you wizards due to my computer misbehaving again.

My computer suffered its first BSOD late last month due to playing a game called Frostpunk. That game was built on the unity engine and apparently I wasn't the only one to suffer as it was very unstable. Anyways since then, once a week at least, I suffer a random BSOD, always when I don't have an eye on my computer.

I've reinstalled my graphics drivers as those were the culprit of a similar I problem I had last year (which you folks helped me resolve) as well as any other drivers I could think off.

I then ran windows driver verifier for a few hours, it crashed and apparently that culprit was Logitech Gaming software program for my mouse which I did a clean reinstall. I then rank driver verifier for about half a day and then turned it off.

That was about a week ago but I got another random BSOD an hour ago, they always seem to happen when I leave the computer on. I've tried to resolve the problem myself, checked all my hardware with testing programs or the windows built in ones and so far they are in the green. I checked all my minidumps and they all say the same thing and I think I narrowed them down to drivers as my hardware seems ok and temperature is not a problem (I stripped my computer down every month to give it a clean and my temperatures don't exceed 50-60 Celsius for CPU/GPU during gaming. Rest of the things idle around 25-35 Celsius)

This was probably caused by the following module: ntoskrnl.exe (nt+0xA44A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Overall computer is usable, I can still game and more importantly work on it. the BSOD seem to happen randomly once or twice a week now. If one of you tech wizards can take a look at the minidumps and help me pinpoint the faulty drivers I would be very grateful. Worse case fix is to do a complete windows 7 reinstall which I'm hoping to avoid. Thanks in advance

P.S. Just to add, I've had shutdown problems also, usually after the computer has been on or been in just for at least a few hours. What normally happens is that windows tries to shut down everything and I have verbose on so it says it shuts everything down but just hangs at the shutting down screen. I suspect the reason for the random BSOD might also be connected, some sort of stray process in the background?

Hi Planeswalker85,
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
Defective RAM can cause all sorts of problems. If you're suffering from frequent crashes, freezes, reboots, or Blue Screens of Death, a bad RAM chip could be the cause of your travails. If these annoyances tend to happen when you're using a memory-intensive application or game, bad RAM is a very likely culprit.
Your post doesn't appear to include RAM Test. Run a ram test!
Your specs say you are using Norton 360, and logs say Windows Defenders is also enabled. Not recommended that you run 2 AVs simultaneously.