ntoskrnl.exe BSOD Windows 10

Hardtry

Honorable
Aug 6, 2013
35
0
10,530
Hey guys,

So, recently I upgraded my pc, from FX-8150+AMD M5A97 R2.0 to i5 4570+MSI Z87-G43-GAMING. The previous system ran fine with these memory sticks:
2x 4gb Kingston HyperX Fury 1866 MHZ at 1.5V
2x 2gb Teamgroup XtreemLV 2000 MHz at 1.67V

As I installed the new mobo+cpu the system would not boot. After placing in the memory one by one eventualy it managed to recognise 12GB, but the windows install would BSOD. So, I took out the Teamgroup memory, and had only 8GB of ram, everything ran fine. When I installed even one of those 2GB Teamgroup ones, random BSODs. So, I tought the problem was with the voltage differences. Went online, ordered another Kingston one. Installed it, and I have BSOD's yet again. They are pretty rare, maybe 1/day, and in the dump files ntoskrnl.exe is the one that is always there.They are completely random, one was when I was playing Mafia 3 today(CRITICAL_STRUCTURE_CORRUPTION) and other when I was listening to music on Spotify (DRIVER_IRQL_NOT_LESS_OR_EQUAL).

I tried a windows reinstall, did not help. Windows Memory Diagnostic found 0 problems, MemTest86(ran it once until it finished) same, 0 errors, so I don't understand where is the issue. In the BIOS, a suspicious thing that I've seen, is that the memory voltage is 1.67 (the Kingston sticker says 1.5) is that normal? Also, windows task manager states that the ram is at 1333 MHz, but the BIOS says 1866, CPU-Z also says 933. What should I try?
 
Solution
D
Do your existing, working sticks work in both slots 1 and 3 and slots 2 and 4? If so the board is fine. And buying a new board does not solve your problem of having mixed RAM that doesn't work together. RAM is sold in kits for a reason.
The RAM's are causing incompatibility. Its very normal. While upgrading, always be sure to get the exact same model of the pre-existing RAM even though its from the same brands. The incompatibilities are caused by varying latencies, voltages, speed,etc. there are a lot of variables. There is nothing much you can do here. Just keep the Teamgroup memory unplugged .
 


Yes.. the teamgroups are a no go and I am going to sell them. But my issue is/was that the 3 kingstons still caused BSOD's. Yesterday I reinstalled them, amd now they are in slot 1-2-3 and there was no bluescreen since(previously they were 2-3-4).
 
You mentioned 2 sticks in your question... Is the third stick the same model. By using 3 sticks of RAM, you wont be able to take advantage of dual memory channel.
And also maybe the 4th RAM slot is faulty; try running your machine with only one stick RAM in the 4th slot; and also do refer to your motherboard manual for optimal memory placement.
And also do a CMOS reset by taking out the battery, waiting for 30 seconds or more and reinserting it back again.
 
I had 2 sticks at the beginning, and the manual says that dual channel shpuld be used in slots 2-4. This worked fine. As I mentioned I ordered 1 more online, and after that the BSODs reapeared. Now I am waiting, maybe using 1-2-3 fixes it. The manual only has the 2-4 and the 1-2-3-4 option listed.
 
Here are the results(X.M.P. is not available with these Kingston memories):

bqZ7zP4.png

2PqupLp.png
 
The results are totally fine. Its because you are using 3 sticks, so dual memory channel is disabled and that why the low score in userbenchmark. The ram sticks are working as they should. You would although get higher performance by using two sticks rather than three. The bandwidth will jump up higher to like 22 gbps -23 gbps and you will see overall better performance. The extra 4 gb doesn't have that much of a benefit.
 
After 3 days since the last time it gave me a BSOD, today it striked again. Still the same, ntoskrnl.exe. So, what do you advise me Sohom? Send the new 4gb stick back, buy 1 more, so I have 4? Does that work in dual channel? I am not sure that 8gb is enough for gaming.

L.E. In Battlefield 1 and only one opera tab open, I had a usage of 9.4GB
 
Yes, do send the new ram stick back and buy one more so you have a total of 4*4 GB RAM. When you will use 4 sticks, the dual memory channel gets activated.
Do a thing, download bluescreenview (http://www.nirsoft.net/utils/bluescreenview_setup.exe) Run it and it will automatically show the logs of all the bsod's till date. In the last bsod, try analysing the driver or file responsible for the bsod. And also post a log here, so i can check it.
 
One thing is unclear to me from your response.. Why would I send the new stick back, and then buy again? The stick must be fine I presume. Also, CPU-Z says that I am running in dual channel mode.. could that be some fault in the BIOS?

gYVozbh.png


I was using bluescreenview, that's how I knew that ntoskrnl.exe was the problem, because at first there were other drivers in there too, like the xbox 360 controller receiver and the nvidia display driver, bit only the ntoskrnl was the one that was always there, and the last BSODs were caused by him. Here is my last dump tho.

==================================================
Dump File : 081617-4484-01.dmp
Crash Time : 16.08.2017 18:40:06
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff802`c85652e0
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff802`c85652e0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+16c560
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.15063.540 (WinBuild.160101.0800)
Processor : x64
Crash Address : ntoskrnl.exe+16c560
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\081617-4484-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 15063
Dump File Size : 578.860
Dump File Time : 16.08.2017 18:40:36
==================================================
 
Ok, after a lot of thought, i conclude that the motherboard is at fault, i.e, memory channel B is somehow causing issues, can be a lot of things, for example, bent pins in the RAM slot, etc. You should send your board for RMA. Another workaround is to purchase two 8 gb sticks and use only memory channel A.
 
If a bios update is available, you can flash it and see if that fixes the issue. But always update bios in an orderly fashion, i.e, if you have version 1 and version 2,3 are available, download version 2, flash it; then download version 3 and flash it. After bios flash, reset the CMOS by pulling out the battery. Also be sure that the RAM's are seated properly.

Check each RAM slot by using a single memory stick. Run the system for 1 hour, with the RAM inserted in each RAM slot; this will determine which RAM slot is faulty; But its a long procedure, better send it for RMA and have them check it out for you.
 
Sadly I cannot RMA the board, I bought it second hand. I will check for a bios update but I am pretty sure I am on the latest version. I will try to test every slot, maybe I find the issue (changing from 2-3-4 to 1-2-3 helped last time). Also, why do you say that that channel B is at fault?
 
Mmm, not quite... you see, as I mentioned in the beginning, when I realized that the TeamGroup ones will not work by any chance, I set up these Kingstons on slots 2 and 4 (that's how the motherboard tells you, for dual channel mode). And for a couple of days it worked completely BSOD free, until I purchased the new Kingston ram, and mounted it into slot 3. I think it's some stupid motherboard issue but it's probably not related to the ram slots, but the chipset itself. I do not understand why running 1-2-3 is better than 2-3-4 but for some reason I stayed BSOD free for 3 days. I think I will buy 4 more GB, so that dual channel will work and maybe that will fix it for good.

L.E. so, I reseated every stick and cleared CMOS... you know that I mentioned that in the BIOS the DRAM Voltage was 1.67 or something like that, while the Kingston ones are running @ 1.5v... now that I cleared CMOS the DRAM Voltage is 1.5
 
Had a new BSOD today, SYSTEM_SERVICE_EXCEPTION this time but the same cause. I went on and updated every driver with Driver Booster, in the BIOS I set the tRFC and tRAS to the correct ones, and also, I ordered 1 more stick. So I will keep you posted with the results.. I really hope no more BSOD
 
Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will decode them and help us help you fix it :)

we will look and see if dumps point at anything other than the ram
 
Hi, that "Ext" thing on the URL code doesn't work. I'm not sure why no one hasn't fixed the instructions for that yet. I figured out the link anyway and was able to download the dump. I ran the dump file through the debugger and got the following information: https://pastebin.com/eAUkYLQi

File: 081917-4390-01.dmp (Sat Aug 19 12:26:21 2017)
BugCheck FC, {ffffd30b3dd333f0, 8a000004022009e3, fffff803229ff800, 3}
Probably caused by: memory_corruption (Process: System)

I can't help you with this. Wait for someone else to reply. Good luck.
 
Hey gardenman, thank you for your help. Edited my post, now it has the whole link, so others can access it easier. I changed the settings as you instructed Colif, if I get a new BSOD I will upload it in that format. Problem is I will be gone for a few days and only after that I will be able to use the PC again.
 
BTW, the memory corruption mentioned in Gardenman's post doesn't auto point to ram, the debugger has been reporting every error is caused by memory corruption since the latest version of win 10 was released

So how new is this install?

I would upgrade/remove these, everything else seems new.

MBfilt64.sys (Dated Thu Jul 30 2009) - realtek HD Audio drivers, wonder why latest version installs a 2009 file...
ISCTD64.sys (Dated Tue Nov 27 2012) Intel(R) Smart Connect Technology Device Driver

Overview
Intel® Smart Connect Technology is designed to update programs by periodically waking your computer from sleep/standby mode for a short time. This function works with applications that automatically get their data from the Internet, such as Outlook* and Windows* Live Mail.

Benefits
Intel® Smart Connect Technology automatically updates applications, such as e-mail and social networks, when your computer is asleep. With Intel Smart Connect Technology, you do not have to wait for your applications to update when you wake up your computer.

Features
The amount of time the feature waits to wake your computer can be set using the “Change Settings” option on the main user interface. You have an option to select between three time intervals: 15 minutes, 30 minutes, or 60 minutes. The longer the interval, the less the battery consumption.

Intel® Smart Connect Technology automatically adjusts the update frequency if your computer battery level is dropping, or if the system temperature rises. Even though you select a 15-minute update frequency, your computer can sleep longer between updates to save battery (if present), or keep the system cool.
- https://www.intel.com/content/www/us/en/support/technologies/000005632.html
Killer Ethernet drivers, get latest from here: http://www.killernetworking.com/driver-downloads (You have E2400)

 
I just installed the Killer Network Manager, with the MSI Live Update 6 tool, and it sais I have E2200 (online on specs it says E2205). The Intel Smart Connect as I recall is disabled in the bios but I will look after it and delete it and make sure it's disabled as it's useless. The realtek driver was installed by DriverBooster, should I try the MSI one? That has version 6.0.1.8010

L.E. that MBfilt seems to be related to the Creative Sound Blaster Cinema feature (I presume) but I couldn't find a software that would work on Windows 10 and on this board anywhere (although advertised on the MSI page, but every one of the versions kept saying I have no compatible device). I reinstalled windows since I tried that tho.
 
I only took your ethernet version from the drivers that were installed at time - e2xw10x64.sys (Dated Wed Sep 14 2016) Killer PCI-E Gigabit Ethernet Controller driver. That driver number corresponds with Killer e2400 PCI-E Gigabit Ethernet Controller - http://systemexplorer.net/file-database/file/e2xw10x64-sys

lol, MBfilt64.sys is mislabelled as Creative but if you look here it shows that is a mistake -

Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver) - Was found in the latest Win8 version available from Realtek on 07Sep2013

http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys

Now all these wrong drivers might be the result of you using Driver Booster as it will install the wrong drivers if you let it, I know as twice I used it and twice it broke windows by installing wrong software. Its only good pooint is it creates a system restore point so you can remove its mistakes. I cringe at the name now and wish there was a safe 3rd party driver installer that didn't make as many mistakes.

Especially since you have an MSI motherboard that comes with live update 6 which does same thing as driver booster except it comes from MSI and at least does get drivers they have for board, and there are a few there from this year.
 
I installed the one from MSI, the latest available there, and maybe just maybe something changes and no more BSODs. As I said I will be leaving so I won't test the PC for a while but I will come back if anything comes by. Thank you very much everyone for the great support so far!
 

TRENDING THREADS