BSOD IRQL_NOT_LESS_NOT_EQUAL error

[kidd0130]

Constant BSOD IRQL_NOT_LESS_NOT_EQUAL error when every i try to play a game, windows 10 and tried so many things to fix, if need me to add anything to help fix let me know.

 

[Colif]

Can you download and run who crashed - it will create a summary of the BSOD and might show us the cause

Copy/paste the summary into here and I see what I can do

 

[kidd0130]

Can you download and run who crashed - it will create a summary of the BSOD and might show us the cause

Copy/paste the summary into here and I see what I can do

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 2/9/2017 1:30:20 PM your computer crashed
crash dump file: C:\Windows\Minidump\020917-19093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x40070, 0x2, 0x1, 0xFFFFF8021886A672)
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 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 Thu 2/9/2017 1:30:20 PM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: afd.sys (afd+0x518D6)
Bugcheck code: 0xA (0x40070, 0x2, 0x1, 0xFFFFF8021886A672)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 standard 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 Thu 2/9/2017 1:18:10 PM your computer crashed
crash dump file: C:\Windows\Minidump\020917-20125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8028B76309B, 0xFFFF9881EDE2BD60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 2/9/2017 8:18:20 AM your computer crashed
crash dump file: C:\Windows\Minidump\020917-20265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x80D46E, 0x2, 0x0, 0xFFFFF8013E4F0725)
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 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 Thu 2/9/2017 6:25:14 AM your computer crashed
crash dump file: C:\Windows\Minidump\020917-19484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x703292402, 0x2, 0x0, 0xFFFFF8011474C77D)
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 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.

 

[kidd0130]

Windows customer support is stating its most likely a hardware issue to this info i gave them do you also think so?

 

[Colif]

If this is a laptop or a brand name PC, go to makers web site for model and update your lan drivers
If this is a custom built PC, go to motherboard makers web site and make sure you have latest lan drivers

Afd.sys file information
The process known as Ancillary Function Driver for WinSock or AFD belongs to software Microsoft Windows Operating System or Ancillary Function Driver for Winsock or Ancilliary Function Driver for Winsock or AFD Networking Support Environment by Microsoft (www.microsoft.com).

It's a system kernel driver, aka "AFD Networking Support Environment" and is part of the Windows TCP/IP stack, supporting socket operations.

Updating network drivers is likely to fix all the irq errors

 

[kidd0130]

If this is a laptop or a brand name PC, go to makers web site for model and update your lan drivers
If this is a custom built PC, go to motherboard makers web site and make sure you have latest lan drivers

Afd.sys file information
The process known as Ancillary Function Driver for WinSock or AFD belongs to software Microsoft Windows Operating System or Ancillary Function Driver for Winsock or Ancilliary Function Driver for Winsock or AFD Networking Support Environment by Microsoft (www.microsoft.com).

It's a system kernel driver, aka "AFD Networking Support Environment" and is part of the Windows TCP/IP stack, supporting socket operations.

Updating network drivers is likely to fix all the irq errors

I did network drivers like 5 different ways and times and non worked, the mother board i did different times installing off the website, i think im just gonna send it back