• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Getting so many ntoskrnl.exe BSOD (PLEASE HELP)

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

ahmedennab704

Prominent
May 19, 2018
22
0
510
Hello, I keep getting a bsod error related to ntoskrnl.exe [strike]every 2 days, if not daily[/strike] I am getting it daily, which seems very very often. running on widows 10 pro
I have tried reinstalling windows 4 times, same issue.
I have my cpu overclocked from 3.0 ghz to 3.7 ghz but it should be stable since I did a stress test for like 10 hours?
I tried using driver verifier but I just got into a infinite loop of bsods with "driver_fail_error (something near this)"
Also tried running memtest86 twice, no errors.
I have tried everything, can anyone please be kind and help me?
Thanks

P.S, I just got bsod when writing this thread....

WhoCrashed dump: https://pastebin.com/BkSk4Ngj

PC specs:

Operating System
Windows 10 Pro 64-bit
CPU
AMD Ryzen 7 1700 43 °C
Summit Ridge 14nm Technology
RAM
16.0GB Dual-Channel Unknown @ 1599MHz (16-16-16-36)
Motherboard
Micro-Star International Co. Ltd X370 GAMING PRO CARBON (MS-7A32) (AM4) 39 °C
Graphics
LG Ultra HD (3840x2160@60Hz)
4095MB NVIDIA GeForce GTX 1080 (MSI) 55 °C
Storage
931GB Seagate ST1000DM010-2EP102 (SATA) 31 °C
931GB Seagate ST31000528AS (SATA) 30 °C
232GB Samsung SSD 960 EVO 250GB (Unknown)
Optical Drives
No optical disk drives detected
Audio
Realtek High Definition Audio

UPDATE: I removed my CPU overclock and don't get as much as bsods lately, but I still get it every 3-4 days.
Same error log
 
Solution
It's not a guarantee to hit high memory clocks with Ryzen. Even Ryzen+ is only officially rated up to 2933.

If you want some sort of assurance, which really still won't guarantee you reach any top rated speed, you would need to purchase a memory kit listed on your motherboard's QVL list of supported memory. You can also choose to buy modules that have specifically been programmed to work on Ryzen systems.

Due to variations from one motherboard to the next, and even one CPU to the next, you still may not hit the highest frequencies as a guarantee, or may have to hand tune to get there.

Folks reporting the highest RAM module compatibility are using modules that employ Samsung B-die memory chips on them, and that's likely a trend you'll...
I just finished going over the entire thread, I think we can get you squared away.

You had a failed oc .
I'd hard reset the BIOS back to default settings and go from there. I have high confidence a hard BIOS reset will fix your problems.

Unplug the PSU, remove the battery and then press the power switch to remove residual power. Replace battery, plug in PSU and power on and set the BIOS to default.

The failed oc may have corrupted system files and they will still be corrupted after the oc was removed. I'd do a fresh install after the hard BIOS reset.
Good luck.
 

by the battery you mean the motherboard's?

 


yes

Personally I leave the battery out for a few minutes after I press the power switch.
 

"and then press the power switch to remove residual power. Replace battery, plug in PSU and power on and set the BIOS to default."
what do you mean by this? what power switch? the psu's? like switch off the psu's?

 

done all that, even a clean install of windows
whilst downloading my apps and stuff, got bsod'd, twice :/
https://drive.google.com/open?id=1vq1sCVHy22fvJ4YcqKu1xKR0ELntkKix
https://drive.google.com/open?id=100ct1_oUWD1x_lXjEmyIwDeOXgmMoH1w
one is the usual (system_service_exception) other is (kmode_exception_not_handled)
just got another
https://drive.google.com/open?id=1LV1thO929OyTMG6yvqvFG0y4IPlbdM1o

its raining bsod's today wtf

and another: https://drive.google.com/open?id=1qXrUD_lb3AdNGklBltEy951apCgSsUiW

Dont understand why is this happening, on bios I only turned ox xmp profile 2 to get my ram to 3200mhz instead of the default 2133hz :/ (timings,volt and frequency is correct)
and this is without trying to game on it, wonder how worse it'll even become
 
I ran the dump files through the debugger and got the following information: https://pste.eu/p/4Inx.html

File: 062618-6406-01.dmp (Jun 26 2018 - 05:20:54)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: WinRAR.exe)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 15 Sec(s)

File: 062618-5968-01.dmp (Jun 26 2018 - 05:17:00)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 12 Sec(s)

File: 062618-5765-01.dmp (Jun 26 2018 - 05:10:29)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 49 Sec(s)

File: 062618-5687-01.dmp (Jun 26 2018 - 05:07:51)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: memory_corruption (Process: ui32.exe)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 37 Sec(s)
The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner)
And this is a clean install?

According to BIOS (from previous dump files): Processor Version: AMD Ryzen 7 1700 Eight-Core Processor
and according to current dump file: MHZ: 3000
That would mean it's not overclocked according to: https://www.amd.com/en/products/cpu/amd-ryzen-7-1700 which says "Base Clock 3GHz".

I can't help you with this. Wait for additional replies. Good luck.
 
Why is nobody harping on the RAM?

Does nobody trying to help have a Ryzen based system that they've tuned RAM timings on? This sounds exactly like the OP's problem. Either the CPU has a bad overclock, or the RAM is unstable, making it look like everything is unstable by means of erroneous, random bug checks. Ditch the XMP profile altogether and dial back the RAM module speeds to default. Also, dial back the CPU overclock to default. Run until you can determine that it's either stable at that point or it's not. It's entirely possible that your RAM modules just don't work well with the Ryzen memory controller.
 


Maybe cause neither of us can afford a new PC right now and don't know those details.

 
Sorry, wasn't meaning to sound negative or be derogatory.

Just surprised nobody is looking at the RAM modules running at 3200 MHz on a Ryzen system. If the modules are dual-rank, you can almost guarantee stability issues at those speeds. You might be able to hand-tune the timings and get them to 3200, but you will probably have to up the CPU's SOC voltage in the process, since the CPU runs the Infinity Fabric at the RAM module speed.

The simple fix is to roll the memory back to 2133 MHz while also running the CPU at stock settings. If the system is determined stable at that point, then the OP can start exploring different RAM timings, but using the XMP profile is likely out of the question.

I wouldn't spend any time analyzing a bunch of dump files until it can be determined that the RAM is stable.

Overnight runs of one or more memory test programs should be a minimum in this case, unless they throw errors right away, which is a dead giveaway.
 

CPU's not overclocked, removed the overclock in a while + already did a cmos clear so it rest the bios


It is a clean install and I did not install that software, however, I installed MSI Gaming App (it has a overclock feature in it, which I did not touch) but I immediately removed it

Did not tune the CPU settings, will turn off xmp 2 now
however, on the official site for my ram, the ram timings on specs matches the official site, that's why I used xmp

Also, I did run memtest before for like 8 hours and did not get a single error


 

safe to say that it's the ram.
I know that 3 days is not enough to stay its stable, but with the rate of my bsod's it is + I ran a gpu test (ran that before, and still got bsod's with xmp) with xmp off, ran it for an hour, no issue, restarted and activated xmp 3 mins of the test and pc gets frozen (I know freeze is not the same as bsod but I believe this freeze is like a pre-stage to bsod but it can't reach it + PC generates a dump file whenever I get frozen so it detects as bsod)

How is it possible to get the ram stable on 3200mhz? Since the stated specs on the official site are not stable for me

cheers
 
It's not a guarantee to hit high memory clocks with Ryzen. Even Ryzen+ is only officially rated up to 2933.

If you want some sort of assurance, which really still won't guarantee you reach any top rated speed, you would need to purchase a memory kit listed on your motherboard's QVL list of supported memory. You can also choose to buy modules that have specifically been programmed to work on Ryzen systems.

Due to variations from one motherboard to the next, and even one CPU to the next, you still may not hit the highest frequencies as a guarantee, or may have to hand tune to get there.

Folks reporting the highest RAM module compatibility are using modules that employ Samsung B-die memory chips on them, and that's likely a trend you'll see in kits that are marketed for use in Ryzen systems.

If you want to try hand tuning your system, I would start by acquiring Thaiphoon Burner. The free version is enough to Read and then Export a Complete HTML Report.

Once you have exported a Complete HTML Report using Thaiphoon Burner, you can then use the Import XMP function in Ryzen DRAM Calculator.

If you prefer, you can find and enter the values manually. HWINFO can also read SPD timings for you. You will want to make sure settings such as Memory Rank, Memory Type, and the other variables are correct in the calculator tool.

The tool is a work in progress and I take no credit for it, but it should be more than enough to get things going. Once you import your settings, or type them in, click the Calculate SAFE button, and there are your timings and other CPU settings.

Once you have the values, take a snapshot with a camera, write them down, or print them, so you can enter them in the memory section of your UEFI.

Pay attention to the SOC Voltage and adjust it accordingly. It's likely you'll have to bump this up to get the memory controller stable at higher frequencies.

Hopefully your UEFI has the other settings mentioned, as they are sometimes necessary to get the RAM to boot with the higher speeds. There are a few more settings you might want to tweak in UEFI on the Advanced tab of the calculator.
 
Solution

just set most of the settings, left out a couple as I didn't have them (hopefully won't be an issue)
PC booted up just fine, now running a GPU stress test. I really hope this will work

Thanks a lot man, will post back with a result after afew days (or much sooner if I get bsod again)
 
Good luck, and try not to get too discouraged yet! 🙂 Once you get Ryzen dialed in it's as solid as a rock. Also, even if you can't hit the 3200 mark with your current modules, you're going to be hard pressed to benchmark a significant difference if you're just a few hundred MHz shy of that.

When I first got going with Ryzen, the UEFI was far more immature. It wouldn't even POST for the first few minutes, which were a tad stressful as the system just kept power cycling, but the UEFI finally found some working timings with my RAM kit and that was enough to get my foot in the door and start tinkering.
 


well that's a rip lol, just bsod'd twice, one's related to my nivided driver and other is related to windows (this time KMODE_EXCEPTION_NOT_HANDLED instead of SYSTEM_SERVICE_EXCEPTION)

https://drive.google.com/open?id=1KrsNF0HwtyB2hYcLRm83wyP4BUmgc_9Q
https://drive.google.com/open?id=1AzOmoDvXFJ9wXAIkbtT9k2_IqZt5x5Hp

 

I think I got it stable on 2933 (tried 2666 and 28xx but pc wouldnt boot up). ran a stress test for 12 hours
but I guess there's no way to see if it's stable until I try it out, so will post a result in few days 😛
 
If you haven't already, you might get better stability if you tweak the CPU voltages a little. SOC voltage should be safe up to 1.2 volts.

I find more instability when I game than when I stress test, and it's usually a bit more entertaining than just watching a PC tread water. If the system becomes unstable, I just bump a setting like SOC voltage (depending on what I'm testing of course) and try again.