BSOD and ntoskernal.exe is my memory or my drivers faulty?

valeoncat13

Prominent
Jul 18, 2017
3
0
510
I've been getting BSODs pretty frequently lately but I'm also not super knowledgeable on identifying the issues outright. From what I've been using (bluescreen viewer and online-crash-dmp-viewer and going through the forums) it seems like my case is memory related? I've also run the Windows Memory Diagnostic Tool, but have been told that is pretty unreliable, haha. But I just can't be too sure.


My Specs:

MohterBoard: MSI Z97 PC Mate (MS 7850)
Graphics Card: Nvidia GeForce GT 740
Memory: 16gb DDR3
Windows 10 Home-64bit

Here's what my dmp files say through BlueScreenViewer:


Crash 1:
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00000782
Parameter 2 : ffffc387`16343600
Parameter 3 : ffffd702`d2280000
Parameter 4 : ffff8802`ad8a4060
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c3f0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.15063.483 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+16c3f0

Crash 2:
Bug Check Code : 0x00000109
Parameter 1 : a39ff4e5`f8b545f7
Parameter 2 : b3b7016c`4b334322
Parameter 3 : fffff800`9b5f5000
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c4c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.15063.483 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+16c4c0

Crash 3:
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000005
Parameter 2 : fffff800`1a2c3d79
Parameter 3 : ffff8681`a625ae60
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c4c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.15063.483 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+16c4c0

I've also tried updating my drivers but I'm not quite sure which ones are actually out-of-date anymore with how many I've been keeping tabs on. They all seem fine. Anyways, thanks in advance!
 

Abdul Malek

Prominent
Jun 21, 2017
26
0
540
your system just shows memory corruption and you have so many suspect drivers you would have to run verifier.exe and change the memory dump type to full or kernel (not minidump) to prove what corrupted the memory.
how to run verifier:
http://www.sevenforums.com/crash-lockup-debug-how/65331...

you have many suspect drivers but here are two that are high suspect drivers just based on the dates:
C:\Windows\system32\drivers\LUMDriver.sys Fri Feb 16 05:14:48 2007
\C:\Windows\system32\Drivers\SSPORT.sys Thu Aug 11 16:07:32 2005
this driver tends to also cause bugchecks due to memory corruption:
\SystemRoot\system32\DRIVERS\dtscsibus.sys Mon Oct 29 02:28:48 2012 (daemon tools i think)

also you are running windivert.sys it captures and insert data into network packets, it causes bugchecks and could be malware to capture passwords and redirect web searches. Most non malware related uses seem to be to cheat on online games.
just be aware it is on your system.
 

valeoncat13

Prominent
Jul 18, 2017
3
0
510


I'm still fairly new to figuring out how all this works, but I've isolated a few drivers and updated. No BSOD yet, but still can't be sure.

I've tried searching for the 3 drivers you mentioned on my computer and I can't find them in the addresses you provided nor in any folders on the computer. Is there some sort of special way to access them that I missed?

I'll be trying the method in the video shortly as well.
 

valeoncat13

Prominent
Jul 18, 2017
3
0
510


So I did both of the suggested options in the video. My harddrive passed with flying colors. But in doing the Memtest, it ran into 4 errors. I don't overlcock or do anything extra with my rig, so I'm assuming it's most likely a memory issue as the test suggests! Thanks for the help.
 

Abdul Malek

Prominent
Jun 21, 2017
26
0
540


You're welcome. Good luck!
 

TRENDING THREADS