IRQL_not_less_or_equal bios update

[Capaa]

When I update the bios the blue screen started to appear and now I do not know what to do

the dmp - https://pastebin.com/q7BLw8E1

I already checked the ram with memtest and it's okay Also updated all the drivers

thanks for help 😀

 

[paulewills1]

When I update the bios the blue screen started to appear and now I do not know what to do

the dmp - https://pastebin.com/q7BLw8E1

I already checked the ram with memtest and it's okay Also updated all the drivers

thanks for help 😀

 

[Colif]

I can't read dumps but this will, can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do
Its worth a try while you wait for someone to read dmp file

 

[paulewills1]

I have had this happen to me on early preview builds. This can be caused by your network adapter drivers.
Try disconnecting your internet connection & try again. You may have to update your network drivers.

 

[Capaa]

I can't read dumps but this will, can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do
Its worth a try while you wait for someone to read dmp file

crash dump file: C:\WINDOWS\Minidump\072117-29781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142480)
Bugcheck code: 0xA (0x1E4, 0x2, 0x0, 0xFFFFF802820E43EC)
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.
-------------------------------

crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x1E4, 0x2, 0x0, 0xFFFFF802820E43EC)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

 

[androbourne]

Also if that doesn't work. Try going into the BIOS and setting all back to defaults.

 

[Capaa]

Also if that doesn't work. Try going into the BIOS and setting all back to defaults.

I already did it and it keeps showing up

 

[Colif]

both files mentioned are part of windows kernel, and IRQ errors can be caused by any driver so best bet is wait for someone to read dump files and they will show you more.

 

[Capaa]

this is another blue screen now DRIVER_IRQL_NOT_LESS_OR_EQUAL https://pastebin.com/7fmX49cU

 

[gardenman]

What you've uploaded so far is the debugger results, not the actual dump files. Upload the actual dump files to somewhere like a google drive. If you get lucky, johnbl will see them and he can get more information from them. He likes both types, minidump and kernal dump. The kernal dump is the big memory.dmp file in C:\Windows.

 

[Capaa]

memory.dmp https://pastebin.com/eqAvHN6k

 

[Capaa]

i formatted the pc and now the screen remains frozen and I have to restart, check hdd,ram,gpu i think the problem is the bios