Share via

BSOD ERROR: DRIVER IRQL NOT LESS OR EQUAL - AFD.SYS WINDOWS 10

Anonymous
2020-03-25T09:48:25+00:00

Hi Guys,

I have been struggling with this for a couple of days now, i am aware that this question has been asked before, and i have read through all the related articles as well.

Unfortunately in my case none of the already mentioned methods lead to a fix.

First BSOD happened 03/22 while playing Wow.

Windows version: Windows 10 , 10.0, build: 18363

Windows dir: C:\WINDOWS

Hardware: ASUSTeK COMPUTER INC., PRIME B350-PLUS

CPU: AuthenticAMD AMD Ryzen 7 1700 Eight-Core Processor AMD8664, level: 23

16 logical processors, active mask: 65535

RAM: 17111769088 bytes (15.9GB)

Last Minidump -  032520-11171-01.zip https://drive.google.com/file/d/19XEd8rDJ2prwjHURDobHFoPczhVusqCY/view?usp=sharing

crash dump file: C:\WINDOWS\Minidump\032520-11171-01.dmp

This was probably caused by the following module: afd.sys (0xFFFFF803CB270DE0)

Bugcheck code: 0xD1 (0xFFFFD00788ECC188, 0x2, 0x0, 0xFFFFF803CB270DE0)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\WINDOWS\system32\drivers\afd.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Ancillary Function Driver for WinSock

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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 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.

Since the problem first occurred I have checked Memory, HDDs, Updated all my Motherboard, LAN drivers, GPU Drivers.

All are up to date, no Hardware changes were made...

I am out of ideas, Can someone help?

Windows for home | Windows 10 | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
  1. Anonymous
    2020-03-25T14:35:35+00:00

    You're welcome for the help.

    Most of the crashes appear to have been initiated by the Driver Verifier.

    Did you "turn on" the Driver Verifier and , if so, when and why?

    Can you ensure the Driver Verifier has been "turned off';

    Windows Key + R > type verifier.exe in the "Open" box > OK > Delete existing settings > Finish

    10+ people found this answer helpful.
    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Anonymous
    2020-03-25T15:54:31+00:00

    Hello,

    Hmm interesting, no I have not turned it On...

    I did as you said and turned it Off now. Lets see if this Helps, I will report back if any more crashes occur!

    Thanks :)

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-03-25T12:18:36+00:00

    Hi,

    The minidump file was inconclusive.

    Can you provide all the minidump files that are available to see if the error is consistent.

    Also, can you also provide the following file which has more information on the crash:

    C:\Windows\MEMORY.DMP

    The memory.dmp file will be quite large, you could zip and compress the memory.dmp file with a third party application such as 7-Zip.

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-03-25T16:01:36+00:00

    You're welcome. Post back if a BSOD re-occurs.

    0 comments No comments
  4. Anonymous
    2020-03-25T13:05:08+00:00

    Hello!

    Thanks for taking the time to check this out :)

    Minidumps: Minidumps.zip

    Memory dump: memory.zip

    0 comments No comments