Windows 10: Multiple BSOD's

Hello,

Last month i had my PSU replaced and added 2 RAM's since then i had some BSOD's related to ntoskrnl.exe (it might be not related to ram though) so i'm posting them here since i don't understand that much about these issues.
Some of them are related to driver verifier since i enabled it for a couple hours and disabled it afterwards in order to not damage anything.
I hope that someone can help me with this, its kinda driving me nuts >.<'

Some things that might help:
-did a sfc /scannow (no errors)
-2 months ago I took my computer for a diagnosis (every single component was perfectly fine)

:)

 

BSOD issues Windows 10 64bit

Okay turns out the network manager was the issue

Just the bare drivers does not cause BSOD (i read on multiple forums supporting this claim)

Will inform you if BSODs continue! Till then it looks fine

 

Multiple BSoDs

Sorry, No.

The ZIP was empty. You can directly share the DMP files, no need to zip.

 

You added ram and started having a problem. The first thing to do is remove the ram you added and see if it goes away. If it does then you can swap them one at a time with the original ram and see if the problem returns. If it does then RMA that memory module.
Alternatively you can test the ram. 16GB is going to take 12+ hours to run a minimum of 8 complete passes of memtest86+:
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

• RAM will accept and keep random patterns of data sent to it
• There are no errors when different parts of memory try to interact
• There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.



Warning MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.



Note MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

The 2/15 12:59PM dump indicates a problem with rzudd.sys:
Code: BugCheck D5, {ffffdc0265558ffa, 0, fffff801da5889e0, 0} *** WARNING: Unable to verify timestamp for rzudd.sys *** ERROR: Module load completed but symbols could not be loaded for rzudd.sys +Could not read faulting driver name Probably caused by : memory_corruption[/quote] \
Driver Description: Razer Rzudd Engine Driver
Driver Update Site: Razer Support

Check if there is an update for your Razer mouse and/or keyboard.

 

Hello Ztruker,

So i've ran memtest with a minimum of 8 passes, no errors (results attached).

I was searching some of the older posts with some issues related to mine like the BSoD (IRQL_NOT_LESS_OR_EQUAL) and those point to the Graphics Driver (Nvidia GeForce GTX980) which i unistalled/re-installed/updated without DDU, so i don't know if with it will make any difference.

About the rzudd.sys:
- I've downloaded Razer Synapse 2.0, it is now up-to-date.

Is there any other relevant thing in the dump files that needs to be checked?

 

The last dumpfile is
Code: BugCheck C2, {7, 62615448, 4810000, ffff948a8c593010} unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPagedPoolEnd unable to get nt!MmNonPagedPoolStart unable to get nt!MmSizeOfNonPagedPoolInBytes Probably caused by : tcpip.sys ( tcpip!TcpPeriodicTimeoutHandler+551 )[/quote] Usual causes:* Device driver, ?Memory

TCpip.sys could point to a network related problem.
According to your supportpage of your mobo the latest lan driver is from 2017-01-03. Check if you have this version installed.
Also check/update all the other driversfrom this supportpage.

Also your MSI gamingapp has drivers from 2014, check/update this driver see under utulities.

 

I had an update on MSI Live for the Network Drive, its up-to-date now.
I'm currently using a wireless adapter from TP-Link (TL-WN881ND) but the last update was in 21/05/13 for WinXP/Vista/7/8 and after i searched for the hardware ID, it led me to this driver (Atheros AR9287) for Win10 which i updated after the last BSoD, but i never had problems with it before.
I've updated all the drivers from MSI's support page for the motherboard.

I guess everything should be fine now, if theres no more BSoD's until the end of the week i'll mark this thread as solved.

And thank you for your help *Biggrin

 

You're welcome, good luck.