Question Random BSOD when gaming | IRQL NOT LESS OR EQUAL

Jun 24, 2020
4
0
10
0
Hi guys,

i am getting BSOD when playing games in a weird regularity. sometimes it works for 2-3 days and then it happens every hour for a couple of days. which doesn't really make sense to me.
anyway i have no idea what or why this is happening and was hoping maybe someone here can help me.

my specs:
Mainboard: ASRock z170 PRO4S
CPU: i5-6600k (not overclocked)
GPU: GTX 1660 Super
RAM: 2x8 HyperX 3000mhz DDR4
PSU: CoolerMaster 450W

MemoryDump: https://1drv.ms/u/s!AvNHaB2nRMfMggRXVT6k109cnI6Z?e=OraoSX
MiniDump: https://1drv.ms/u/s!AvNHaB2nRMfMggN7gqevjvsiix0o?e=WDJJ3o

RAM is 3 months old and GPU is 1 month old. Rest is 5 years old.

thanks
heinz

edit: going through the last 10 minidumps i just realized it's always the same crash adress : ntoskrnl.exe+1c23a0 . my ram is fairly new, so i guess it shouldnt be the ram itself. could it be that my 5 year old 256gb ssd is nearing the end of its life?
 
Last edited:

Colif

Win 10 Master
Moderator
ntoskrnl is blamed for almost all BSOD I see... but windows isn't that bad.
NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

I will send link to a friend and he will convert dumps for us.
 

gardenman

Admirable
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://pastebin.com/MehiAPFa

File information:062420-10578-01.dmp (Jun 24 2020 - 08:44:22)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 15 Hour(s), 47 Min(s), and 29 Sec(s)

Possible Motherboard page: https://www.asrock.com/mb/Intel/Z170 Pro4S/index.us.asp
You have the latest BIOS already 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.
 

Colif

Win 10 Master
Moderator
possibly the asrock app charger driver since its dated 2011

Can you give us the other 9 minidumps? more info the better.

Who makes ssd? If its from Samsung, have you run Samsung Magician on it and checked its SMART scores? (only guessing based on ssd size)
 
Jun 24, 2020
4
0
10
0
hi,

thanks for helping me.
here are all minidumps from the folder, but i realized those are slightly older then the ones above.
i did one system reset which helped with the bluescreen for 2 days, but the current minidumps are gone.
https://1drv.ms/u/s!AvNHaB2nRMfMggX5CpxUyx1AxoOD?e=oIDqnY

the ssd is a crucial 250 bx. i've got a new nvme ssd from samsung yesterday. will reinstall windows on the new one over the weekend.

to add some history to the problem which really keeps confusing me. the bluescreens started in february 2020. once they started appearing they got more frequent. i reinstalled windows back then and the bluescreens stoped for like 2 months. then it started again. so i kinda think it should be a driver problem, but on the other side, they just start appearing without me changing any drivers or something. but over the time my ssd has less free space. (i dont know if this changes anything).
 

gardenman

Admirable
Moderator
I ran the older dump files through the debugger and got the following information: https://pastebin.com/4iuv1hbG
File information:062120-7921-01.dmp (Jun 21 2020 - 11:37:12)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 28 Min(s), and 15 Sec(s)

File information:062120-7906-01.dmp (Jun 21 2020 - 11:07:13)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:5 Day(s), 4 Hour(s), 19 Min(s), and 49 Sec(s)

File information:061620-8656-01.dmp (Jun 16 2020 - 06:46:59)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 0 Hour(s), 00 Min(s), and 24 Sec(s)

File information:061620-11218-01.dmp (Jun 16 2020 - 06:45:59)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:4 Day(s), 10 Hour(s), 42 Min(s), and 11 Sec(s)

File information:061220-8281-01.dmp (Jun 11 2020 - 20:03:17)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:1 Day(s), 4 Hour(s), 21 Min(s), and 38 Sec(s)

File information:060920-10625-01.dmp (Jun 8 2020 - 21:00:35)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:0 Day(s), 4 Hour(s), 35 Min(s), and 23 Sec(s)

File information:060520-8250-01.dmp (Jun 4 2020 - 18:21:55)
Bugcheck:IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:memory_corruption (Process: System)
Uptime:3 Day(s), 1 Hour(s), 07 Min(s), and 30 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 10 Master
Moderator
I had thought I would get something out of that many... they all the same, perhaps it is a driver still.

It could be any of these as they made before win 10 was released
  1. May 10 2011 - AsrAppCharger.sys - ASRock App Charger driver
  2. Jun 03 2015 - iaStorA.sys - Intel SATA Storage Device RAID Controller
  3. Jun 23 2015 - RTKVHD64.sys - Realtek Audio System driver https://www.realtek.com/en/
Could be nvidia drivers too.

it shouldn't be the ram but - Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it
 

ASK THE COMMUNITY

TRENDING THREADS