So, basically, for awhile now I've been experiencing various BSOD errors, to the point that i know them by heart. page_fault, kmode... all of them, and have been trying to battle it on and off with no special result. Even reinstalling my Windows a few months ago helped only for awhile, 2 weeks tops. I use a fairly new desktop PC, one year old, and I'm pretty sure the issue is not hardware related. I've already done Memtest which showed no issues and I recall checking my hard disk in the past as well and I think there were no issues as well. It often happens when I play certain videogames (oddly enough, never when I play Blizzard games), but it sometimes also happens on startup, or when I use, say, Photoshop or watch a video via VLAN. I remember updating my NVIDIA Video Card driver and it didn't help.
I always considered myself an intermediate computer user, but now I see that when it comes to troubleshooting real problems, I have no clue, so I would appreciate your help.
Thanks in advance!
Here's my dump analysis by WhoCrashed:
------------------------------------------------------------
Computer name: DESKTOP-JKJIQ4G
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: MS-7A74, MSI, B250M PRO-VD (MS-7A74)
CPU: GenuineIntel Intel® Core i5-7400 CPU @ 3.00GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8555565056 bytes total
On Sun 11/18/2018 4:19:49 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111818-7703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFE69506881083, 0xFFFF8D0DF7A97EC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
-----------------------------------------------------------------------------