[SOLVED] BSOD Kernel, IRQL, etc

Dec 6, 2021
2
0
10
0
So I did a fresh clean install of Windows 10 and have been getting these bluescreens (usually when PC is in idle, not playing)

Config:

Ryzen 5 3600
ASUS EX-A320M-Gaming, AMD AM4, mATX, DDR4
Crucial Ballistix Sport LT, 16 GB (2X8),2666MHz, DDR4, CL16
Gigabyte AMD Radeon RX 5600 XT Windforce OC 6G, 6GB, DDR6, Rev 2.0
EVGA 650W 100-N1-0650-L


On Mon 06/12/2021 13:58:35 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120621-4343-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF80175DB10C6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80175DB10C6, 0xFFFF86808B6ECC60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 06/12/2021 13:50:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120621-4031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0xA (0xCF2F7320, 0xFF, 0x0, 0xFFFFF8036C111697)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 06/12/2021 12:20:25 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120621-5406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x157 (0xFFFF8B8D0196C080, 0x5, 0x2, 0x0)
Error: KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an illegal operation was attempted on the priority floor of a particular thread.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 05/12/2021 20:56:18 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\120521-4593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0xFC (0xFFFFDE08D72517D8, 0x8400000217F4F963, 0xFFFFF8844AF5D5E0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This may be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. Memory corruption can also occur because of overheating (thermal issue). There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

already tried scannow, dism, etc. None of that worked

minidumps: https://1drv.ms/u/s!AmT3GWMxJQ19k1B5tA60bmhq3pYU?e=pb9c3j
 

Colif

Win 11 Master
Moderator
Ancillary Function Driver for WinSock
this is used by windows to talk to Network drivers, so try updating ethernet or wifi, whichever you use

is an unusual error. IN that, its not common.

my 1st reaction to unusual errors is run memtest
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
 

Lutfij

Titan
Moderator
Welcome to the forums, newcomer!

How old is the PSU in your build? Can you check and see what your BIOS version is at the time of writing? As for your platform, are the rams running on X.M.P or are the manually input in BIOS? As for your OS, did you recreate your bootable USB installer using Windows Media Creation Tools to rule out a corrupt installer? Storage drive that has the OS on it?
 
Last edited:
Dec 6, 2021
2
0
10
0
PSU is one and a half year old, bought new

My BIOS version if from 10/21/2021

Can you tell me how to check the RAM? I dont know the answer to your question

Yes, I did use Windows media creation tool, it reduced the frequency of blue screens

OS is installed in the SSD
 

Colif

Win 11 Master
Moderator
Ancillary Function Driver for WinSock
this is used by windows to talk to Network drivers, so try updating ethernet or wifi, whichever you use

is an unusual error. IN that, its not common.

my 1st reaction to unusual errors is run memtest
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