[SOLVED] KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe (Win10 21H1) ?

Aug 15, 2021
5
1
25
1
Hi,
I know that BSOD code is mentioned in multiple threads but nothing really makes things better in my case.

Computer crashes between just after the login screen to couple of minutes after.
I upgraded Windows 7 to latest Windows 10 version with in place upgrade. I would like to save everything that is installed but if nothing helps I will try clean install.
My assumption is that it's one of old drivers.

What I did:
  • sfc /scannow, which found two issues and fixed them - still crashing after that
  • chkdsk C (SSD), and F(HDD) which happens to be used always just before the crash - no errors on both
  • reinstalled gpu driver
  • removed Logitech G-Hub as one of the threads was pointing that it might be it
  • tried clean start
  • installed Intel driver update helper but it didn't found any updates for me
It's running without any issues in safe mode.

Computer specs:
i5-2500K
AsRock P67 Pro3 (old BIOS, but I'm afraid to update it as it might crash any moment)
8GB DDR3
GTX 970

More logs here: (with couple of minidumps)
https://drive.google.com/file/d/1v3fut5M57Z594OV1UGISfAoEvhAujVfk/view?usp=sharing
 
Aug 15, 2021
5
1
25
1
After updating BIOS to 3.4 beta version it looks like it's fixed now, running without a crash for 50 minutes already.
I will mark it as solved later if no crash happens for longer time.
 
Reactions: Colif

Colif

Win 10 Master
Moderator
Conversion - https://jsfiddle.net/g7fLd24t/show

I think the problem is caused by your Audio drivers, given their age
Jul 28 2010RTKVHD64.sysRealtek Audio System driver https://www.realtek.com/en/
2nd crash mentions HDAudioBus.sys which is a clue . Its part of windows but it leads me to looking at installed drivers.

rest of them don't offer as much of a clue. All 4 BSOD are Divide by zero which isn't something I see a lot.

The audio driver on here is 5 years newer - https://www.asrock.com/mb/Intel/P67 Pro3/index.asp#Download
 
Reactions: Phillip Corcoran
Aug 15, 2021
5
1
25
1
After updating realtek and intel drivers from asrock page (skipped the utilities) it's still happening. New minidumps here:
https://drive.google.com/file/d/1Or4tps3VEoDWoG9wgveve9K9qs8cOKcO/view?usp=sharing

Also this looks very strange:

(Usage, speed, processes, threads, haldnes, up time)

Tried to run with disabled device that uses the realtek (2015) driver but it again crashed.

Since it's working fine in safe mode I still believe that it's the driver and it can be fixed, but I'm slowly getting ready to do a clean install instead :|
 
Last edited:

Colif

Win 10 Master
Moderator
thats a pretty impressive overclock you have there - i don't think those intel drivers are right... wonder if you can roll back to drivers you had before

i wouldn't bother with bios update if its worked fine until now.

person who checks dumps for me is asleep but I will ask him to convert so they ready by time i see him.
 
Aug 15, 2021
5
1
25
1
Small update, I'm afraid that this might not be fixable. I found out similiar thread on asrock forums for a slighty different board but still P67. In their case fresh install also throws the same BSOD, and it's definitely a driver since it's working fine in safe mode. But the problem is that there is no newer compatible version of that driver, they also have the same issue with insane readings in task manager. In their case older version of Win10 was working fine.
So the solution with clean-install is a waste of time, as 20H1 and above will crash in the same way.
I see two possible solutions right now: rollback to win7, or rollback to older version of Win10.
Not sure which one is better, and if it's even possible to rollback the installation back to win7 without clean install of 7.

That update was a mistake :(
 
Last edited:

Colif

Win 10 Master
Moderator
How long ago did you upgrade?

If you can roll back it will be on settings/update & s Security/recovery page

if the problem is sound driver, we assume... then could use a DAC or something else instead of staying on 7 just for 1 driver.
 
Aug 15, 2021
5
1
25
1
Two days ago, no issues on Win7 previously. I'm trying to fix it for two days now, it's BSODing from first login to win10.
Again updated my previous post, I think I found the solution:

There is a beta version of BIOS that is a 'instant flash' installer, which is safe for me to do because flashing from normal startup might end with a BSOD. One person with exactly same setup and win version reported that it fixed both issues, BSODs and strange readings in CPU usage. Will update after BIOS update.
 
Aug 15, 2021
5
1
25
1
After updating BIOS to 3.4 beta version it looks like it's fixed now, running without a crash for 50 minutes already.
I will mark it as solved later if no crash happens for longer time.
 
Reactions: Colif

ASK THE COMMUNITY

TRENDING THREADS