Question BSOD Issue - ntoskrnl.exe - - - Tried several things but no luck ?

Jan 22, 2022
16
1
15
0
Hello,


Recently I've been having random crashes on my PC. I've tried several things at this point now but to no avail. It started approximately two weeks ago, on 01/09/22. I was share screening some youtube video on discord for a friend and my computer completely froze up, did that audio glitch noise and so I hard shut it down. I figured it was a one off crash. When I booted back up, I would periodically have my share screen crash on discord (not the computer, just had to reshare the discord screen) A few hours later, it began blue screen crashing at random intervals.

I tried changing a bunch of discord settings, (hardware acceleration, completely reinstalled discord). Nothing seemed to work. I did DDU and a fresh install in Safe Mode, reinstalled all of my lan/audio drivers, did a BIOS update, sfc scan - nothing worked. The crashes were seemingly random, but seemed to happen more when I was playing a game or sharescreening on discord.

So finally and reluctantly, I did a Windows Recovery (Using the Keep Personal Files setting) via the Cloud option. I reinstalled most of my programs (steam, discord, etc) and things were fine for a few days. Then the crashes started again. I moved the RAM around and booted in various configs. I Ran MemTest86+ for 9 consecutive clean passes (image attached). I ran Prime 95 for a few hours, ran FurMark several times to stress test GPU/CPU. Was completely fine for both of them, nothing insane on the temps. I've consulted with several knowledgeable friends and have probably tried a few other things not mentioned here but nothing helps. The crashes are completely random - I've been in bed reading at 1 am, CPU idle for hours, and noticed the light from the monitors change and see it blue screen. I reboot, it crashes again in 10 seconds. Then it's fine for 4 days of usage (gaming, discord, browsing) before I get another crash.

View: https://imgur.com/a/s1tz5JF
-Various bluescreens and their error messages, as well as the MemTest86+ 9 pass screenshot. One bluescreen was just two white dots on the screen(this one didn't showup in bluscreenview)

https://drive.google.com/file/d/1dmrNNkQ4yBGWZ0XvM-IaZguHprcm0yei/view?usp=sharing- Contains the MiniDump files for BlueScreenView (let me know you need me to upload these elsewhere -this link should not be restricted and should be open to all if I did the settings in MyDrive right)

https://drive.google.com/file/d/1Rwev0Ws_t1BsZHwTHh4D0vPf95FJVf-_/view?usp=sharing - Slightly newer dump - shortly after I posted this thread it crashed twice consecutively. It made me do the windows repair/diagnosing thing then rebooted as normal, but I have included this log as well in case it is needed.

List of Components:

CPU: Intel Core i7-9700K
GPU: Nvidia RTX 2070S (Super)
SSD: Intel 660p NVMe PCIe M.2 1TB
SSD: Tcsunbow X3 1TB
RAM: G.SKILL Ripjaws V DDR4 3200 C16 2x16GB
MBD: Asrock Z390 Pro4


Please let me know if you need any other information from me, or if I have formatted this thread incorrectly . I'll be monitoring this thread regularly and will try to respond quickly. I am extremely grateful for any expertise or insight that anyone can offer.
 
Last edited:

gardenman

Distinguished
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/9n023mLy/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:012222-6000-01.dmp (Jan 22 2022 - 02:18:41)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:memory_corruption (Process running at time of crash: svchost.exe)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 06 Sec(s)

File information:012022-8171-01.dmp (Jan 20 2022 - 03:31:48)
Bugcheck:PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:memory_corruption (Process running at time of crash: Discord.exe)
Uptime:5 Day(s), 3 Hour(s), 01 Min(s), and 09 Sec(s)

File information:012022-8078-01.dmp (Jan 20 2022 - 03:43:34)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process running at time of crash: chrome.exe)
Uptime:0 Day(s), 0 Hour(s), 11 Min(s), and 24 Sec(s)

File information:011222-7343-01.dmp (Jan 12 2022 - 22:34:48)
Bugcheck:KERNEL_SECURITY_CHECK_FAILURE (139)
Driver warnings:*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by:memory_corruption (Process running at time of crash: Hearthstone.exe)
Uptime:0 Day(s), 18 Hour(s), 38 Min(s), and 08 Sec(s)
Possible Motherboard page: https://www.asrock.com/mb/Intel/Z390 Pro4/index.asp
You have the latest BIOS installed.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Jan 22, 2022
16
1
15
0
Slight update - I had my computer completely turn off out of nowhere. Was across room on phone and not doing anything. When I attempted to reboot it wanted to try windows repair and kept BSODing. Eventually I had to choose a restore point from a few days ago when I was trying some driver uninstall. BlueScreenView looks like it lost the last few records, but for the first time I'm seeing a different "caused by address" - "Ntfs.sys + 4822".

View: https://imgur.com/a/7XGbdQ5
 

Colif

Win 11 Master
Moderator
blue screen view tends to blame the process running at time for crash, which while technically correct, isn't likely actual cause. its just what was running. I actually asked Gardenman recently to change his description to what it says in his: Process running at time of crash - as it is closer to truth. Very rarely is it actual cause. More often the victim

Your dumps don't really tell me a lot.
I can guess it could be the Nvidia drivers
Dec 15 2021nvlddmkm.sysNvidia Graphics Card driver http://www.nvidia.com/
As although they are new, I have seen a number of people getting BSOD off them recently.
Try running DDU in safe mode and install newest Nvidia drivers - https://forums.tomshardware.com/faq/how-to-perform-a-clean-install-of-your-video-card-drivers.2402269/

try running https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html and see if newer LAN drivers or anything else for pc.
 
Jan 22, 2022
16
1
15
0
Hi Colif,


Thanks for the information - I went ahead and installed the intel driver support assistant. I updated the firmware for my SSD and it looks like I have everything up to date there.

I went ahead and did the DDU again (I think I did it before I reinstalled windows, but haven't on this build) - uninstalled the old drivers in Safe mode + reboot, and installed the latest nvidia drivers for my card. I will post again in this thread if I get another BSOD.

Thanks as well to you gardenman for running the files through the debugger.
 
Reactions: gardenman
Jan 22, 2022
16
1
15
0
Hello all,


:( unfortunately the issue seems to have returned. It worked fine for pretty much over two weeks - no crashes or any issues. Today however, it blue screen crashed and has done so repeatedly. It's still an ntoskrnl.exe issue, and I have attached the dump files for the BSOD's I've been getting today. If anyone has any ideas how why this could have returned or what is going on, I would be extremely grateful. Please let me know if you have any other questions or need anything else from me.

https://drive.google.com/file/d/1dmrNNkQ4yBGWZ0XvM-IaZguHprcm0yei/view?usp=sharing
 

gardenman

Distinguished
Moderator
ntoskrnl.exe is basically just "Windows" itself. It's not the actual issue. It's just that Windows cannot find anything else to blame, so it gets listed. It's at the bottom and holds everything up. I know that doesn't help much because it still doesn't give the real reason of why you are crashing.
 
Last edited:

gardenman

Distinguished
Moderator
I ran the dump files through the debugger and got the following information: https://jsfiddle.net/cavm6h79/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:020922-7171-01.dmp (Feb 9 2022 - 17:47:29)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP (7F)
Probably caused by:memory_corruption (Process running at time of crash: LOSTARK.exe)
Uptime:0 Day(s), 0 Hour(s), 16 Min(s), and 43 Sec(s)

File information:020922-6984-01.dmp (Feb 9 2022 - 13:15:37)
Bugcheck:UNEXPECTED_KERNEL_MODE_TRAP (7F)
Probably caused by:memory_corruption (Process running at time of crash: Discord.exe)
Uptime:0 Day(s), 7 Hour(s), 54 Min(s), and 35 Sec(s)

File information:020922-6843-01.dmp (Feb 9 2022 - 14:30:08)
Bugcheck:MEMORY_MANAGEMENT (1A)
Probably caused by:memory_corruption (Process running at time of crash: steamwebhelper.exe)
Uptime:0 Day(s), 0 Hour(s), 54 Min(s), and 43 Sec(s)

File information:020922-6187-01.dmp (Feb 9 2022 - 16:43:33)
Bugcheck:ATTEMPTED_WRITE_TO_READONLY_MEMORY (BE)
Probably caused by:memory_corruption (Process running at time of crash: MsMpEng.exe)
Uptime:0 Day(s), 1 Hour(s), 44 Min(s), and 59 Sec(s)

File information:020922-6984-02.dmp (Feb 9 2022 - 16:44:56)
Bugcheck:PFN_LIST_CORRUPT (4E)
Probably caused by:memory_corruption (Process running at time of crash: wevtutil.exe)
Uptime:0 Day(s), 0 Hour(s), 01 Min(s), and 02 Sec(s)
This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 11 Master
Moderator
I'm terribly sorry - that is the old link.
thats okay, i thought i was seeing double - I shouldn't have answered like I did.

I think the cause is LAN drivers still
May 07 2019e1d68x64.sysIntel(R) Gigabit Adapter driver
its strange the WiFi drivers are updated to even win 11 but the newest lan drivers on PC website are still 2019
https://www.asrock.com/mb/Intel/Z390 Pro4/index.asp#Download

I would try the ones here from December - https://www.intel.com.au/content/www/au/en/products/sku/82186/intel-ethernet-connection-i219v/downloads.html
 
Jan 22, 2022
16
1
15
0
No worries Colif, I wasn't offended by you pointing out my mistake, haha. I appreciate you and gardenman jumping back in on this thread for me. I grabbed the Wired_driver_26.8_x64 zip file and ran it. Shortly before I tried that I got another BSOD and this time it pretty much locked my computer for a while in an endless boot cycle. It kept giving me this error message about mvumis.sys issues. I have a windows installation media key on a USB that I popped in to try the windows repair tool and it wouldn't work - also tried doing cmd from there and doing /sfc scannow but it didn't show anything. Eventually after hitting "reboot" a bunch it let me get back in as usual where I checked this thread and tried the new drivers you suggested.

View: https://imgur.com/a/T0DUPh6
 
Jan 22, 2022
16
1
15
0
So I'm still getting BSOD's after updating the LAN Driver - they seem to happen more frequently when I play a game - I can seem to reliably blue screen myself when I play path of exile or lost ark after about 5-10 minutes. The BSOD's don't seem to be getting captured in bluescreenviewer anymore either. Really strange, and that nvumis.sys message doesn't seem to be popping up again.
 

Colif

Win 11 Master
Moderator
nvumbis.sys - it might be part of the Elan touchpad. I can't see Marvell mentioned on MB website, as in the past they used to supply USB chips, most new mb have enough now without extra chips.

could tie into this too
Jul 31 2018audientusbaudio.sysAudient USB Audio driver
Jul 31 2018audientusbaudioks.sysAudient USB Audio driver
i can't tell as searching for Marvell and its name just gets movie results.

is intel drive the boot one?
run crystalsidkinfo and let it check smart scores - it will auto. no need to run tests.
Blue icons here - https://crystalmark.info/en/
check both drives, never heard of other brand before
 

Colif

Win 11 Master
Moderator
it just reads what drive reports. Intel don't seem to have testing software of their own. Or I would have suggested it.

BSOD without dumps always make me question the drive.

cause seems to move, but you ran Prime & Memtest already, so its unlikely to be ram at this point.

if its a driver, its hiding

UNEXPECTED_KERNEL_MODE_TRAP
System was stuck in a loop, kept running same process and eventually crashed (this is in FILO Order, First IN, Last OUt. Top lines ended last
it repeated these actions at least 5 times
ffffe581fb819c90 fffff8011b0e8a84 : fffff8011ae00000 fffff80100000000 ffffffffffffffb6 00007ffffffeffff : nt!RtlpUnwindPrologue+0x248
ffffe581fb819cf0 fffff8011b0e719f : fffff8011aee39f4 ffffe58100000000 ffffe581fb81a380 fffff8011aee39f4 : nt!RtlpxVirtualUnwind+0x104
ffffe581fb819d70 fffff8011b0e6ebe : ffffe581fb81a330 0000000000000000 ffffe581fb81fa00 fffff8011b208dc0 : nt!RtlVirtualUnwind+0x5f
ffffe581fb819df0 fffff8011b0e5b86 : ffffe581fb81ad08 ffffe581fb81aa40 ffffe581fb81ad08 fffff8011aeb11f8 : nt!RtlDispatchException+0x1ce
ffffe581fb81a510 fffff8011b2094ac : ffffe581fb81abc0 0000000000000010 ffff8a22b3649ab5 0000000000000000 : nt!KiDispatchException+0x186
ffffe581fb81abd0 fffff8011b205643 : ff000000ff000000 ff000000ff000000 ff000000ff000000 ff000000ff000000 : nt!KiExceptionDispatch+0x12c
ffffe581fb81adb0 fffff8011b0e9018 : ff000000ff000000 ff000000ff000000 ff000000ff000000 ff000000ff000000 : nt!KiPageFault+0x443

At no stage did it touch storage, was all in ram. Page fault - A badly named action where CPU has to access ram to find data.

most of errors occurred in virtual memory. None of them show any interaction with the page file.

we can run this to see if it is a driver - follow the 3 steps - https://forums.tomshardware.com/threads/driver-verifier-instructions.3686888/
 
Jan 22, 2022
16
1
15
0
Looks like I got stuck in a boot loop so Ilm doing a restore point. It was giving me the driver device not verified message so I'm guessing I did it correctly
 

gardenman

Distinguished
Moderator
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/cdqh68ns/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:021022-7312-01.dmp (Feb 10 2022 - 02:54:59)
Bugcheck:DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Driver warnings:*** WARNING: Unable to verify timestamp for SteamStreamingMicrophone.sys
Probably caused by:memory_corruption (Process running at time of crash: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 04 Sec(s)

Comment: I don't think I've ever seen that driver crash before.
Jul 28 2017SteamStreamingMicrophone.sysSteam Streaming Microphone driver (Valve Corporation)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

ASK THE COMMUNITY

TRENDING THREADS