Question Constantly getting BSOD while playing games because of ntoskrnl.exe

ADHttv

Reputable
Oct 18, 2019
7
0
4,510
Hi, my windows 11 computer keeps BSODing most of the time while playing intensive games for my rig like Star Citizen or The Finals.

Rarely it BSODS while idle-ing but again, most of the time while playing a game and listening to a youtube video in the background and I'm at a loss as to what might be causing this problem.
FYI: no BSODS were encountered while heavy rendering a video file multiple times for hours and hours in premiere pro.

I ran the Bluescreen view app and see that the culprit is ntoskrnl.exe

Could someone please assist me in resolving this issue? I would greatly appreciate any guidance or suggestions you can provide.

BSOD dump files and screenshot of the bluescreen viewer https://drive.google.com/drive/folders/1QCPIJWHDFvaY5rF8tF2ZEQQ5bOt19CVm?usp=sharing


System:

Processor 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz

Installed RAM 64.0 GB (63.8 GB usable)

System type 64-bit operating system, x64-based processor

Video Card 2080TI with the latest drivers (this has been happening for more than a month now on multiple different drivers)




I've tried memory check and no issues appeared during the scan.

also tried Dism /online /cleanup-image /restorehealth and SFC /scannow with no issues found during the scans

any ideas would be super appreciated.

Thank you!
 
Last edited:
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.
 
When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.
Entire system is from Jan 2023

Case HYTE Y60 MID-TOWER PANORAMIC CASE
Processor (CPU) Intel® CoreTM i9 24-Core Processor i9-13900K (3.0GHz) 36MB Cache
Motherboard GIGABYTE Z690 AORUS ULTRA WIFI (LGA1700, USB 3.2, PCIe 5.0) - ARGB
Memory (RAM) 64GB Corsair DOMINATOR PLATINUM RGB DDR5 6000MHz (4 x 16GB)
1st (System drive) M.2 SSD Drive 500GB SAMSUNG 980 PRO M.2, PCIe NVMe (up to 6900MB/R, 5000MB/W)
2nd M.2 SSD Drive 2TB SEAGATE FIRECUDA 530 GEN 4 PCIe NVMe (up to 7300MB/R,6900MB/W)
3rd Baracuda SSD 1TB ZA1000cm10002
Power Supply CORSAIR 1000W RMx SERIESTM - MODULAR 80 PLUS GOLD, ULTRA QUIET
Power Cable 1 x 1.5 Metre UK Power Cable (Kettle Lead, 1.0mm Core)
Processor Cooling Corsair iCUE H150i ELITE CAPELLIX RGB Hydro Series High Performance CPU Cooler
Thermal Paste STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Sound Card ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card 10/100/1000 GIGABIT LAN PORT

1st monitor Dell S2719DGF 2560x1440 144hz
2nd monitor LG ultrawide 2560x1080 60hz
3rd monitor PHL 234E5 1080p 60hz
 
The dumps are pointing me in two directions; on the one hand this looks like a possible RAM problem, one dump in particular is pointing directly at bad RAM...
Code:
FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram
However, another dump apparently fails due to an Avast driver...
Code:
FAILURE_BUCKET_ID:  AV_aswbidsdriver!unknown_function
Third-party anti-malware products cause lots and lots of BSODs (which is why I never use them) and when we see an Avast! (or similar anti-malware) driver in a dump it's always tempting to blame the anti-malware product. Clearly, you'd much prefer this to be an Avast problem rather than a RAM problem so I'm going to ask you to do two things. Firstly test your RAM with Memtest86....
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
If that finds no errors then I strongly suggest that you uninstall Avast completely using the specialised uninstall tool from Avast. Then see how things go. If you still get BSODs afterwards then please run the SysnativeFileCollectionApp again and upload a new data file.
 
  • Like
Reactions: ADHttv
The dumps are pointing me in two directions; on the one hand this looks like a possible RAM problem, one dump in particular is pointing directly at bad RAM...
Code:
FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram
However, another dump apparently fails due to an Avast driver...
Code:
FAILURE_BUCKET_ID:  AV_aswbidsdriver!unknown_function
Third-party anti-malware products cause lots and lots of BSODs (which is why I never use them) and when we see an Avast! (or similar anti-malware) driver in a dump it's always tempting to blame the anti-malware product. Clearly, you'd much prefer this to be an Avast problem rather than a RAM problem so I'm going to ask you to do two things. Firstly test your RAM with Memtest86....
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
If that finds no errors then I strongly suggest that you uninstall Avast completely using the specialised uninstall tool from Avast. Then see how things go. If you still get BSODs afterwards then please run the SysnativeFileCollectionApp again and upload a new data file.
Thanks for the advice, I already uninstalled avast and continue to get bsod regarding ntoskrnl. Now, the PC is moving with lag-ish (if I constantly move a window it's not showing a cursive image, adding or removing a a display takes way longer than before, games (if the dont bsod) even though they show 100+ fps feel they have microstutters a LOT).

I'll try the ram test even though I've done a memory test with windows and everything turned out right. I'm one step away in doing a windows reset and see if this was caused by the RGB software that I have and that I know it can conflict ( RGB fusion with Icue corsair). it's annoying that there are so many possible situations but I'll do the ram stuff first.