Windows 10: Getting IRQL_NOT_LESS_OR_EQUAL after updating KB4512508

It happens after updating KB4512508(Build 18362.295) and I am using Korean as windows.

I've tried to reinstall and fresh-reinstall windows, it is same. Same crash(bluescreen) happens.

It happens at random time, I could roll-back the update so just for now I could use it normally.

Is there a way to fix it or can I(or someone) report to Microsoft?



Bugcheck code: 0xA (0xFFFF8086, 0x2, 0x0, 0xFFFFF80615442454)

Error: IRQL_NOT_LESS_OR_EQUAL


System info
Hardware: ASUSTeK COMPUTER INC., TUF B450M-PRO GAMING
CPU: AuthenticAMD AMD Ryzen 7 3700X 8-Core Processor AMD8664, level: 23
16 logical processors, active mask: 65535
RAM: 34292961280 bytes (31.9GB)


At the memory dump file(2 logs, checked by whocrashed) :


This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x11E8)
Bugcheck code: 0xA (0xFFFF8086, 0x2, 0x0, 0xFFFFF80615442454)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft 파일 시스템 필터 관리자
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 a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.


This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0xA (0xFFFF8086, 0x2, 0x0, 0xFFFFF80615442454)
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.

:)

 

Irql_not_less_or_equal

So I have this clients PC that blue screens and gives a IRQL_NOT_LESS_OR_EQUAL STOP 0x0000000A error message. Error Goblin (link in sig) says the following:

And I have NO IDEA what the hell that means. It has wrapped around my head 5 times and caused it to explode. Ive ran memtest for 7 and a half hours and it didnt find any errors. I will probably run it again overnight just to be safe. Ive also cleaned out the computer with an air compressor and checked the hard drive for bad sectors are none are to be found.

Im trying like hell to avoid reinstalling Windows but it seems unlikely.

Im going to try updating some drivers and see what happens. Some of the drivers on this computer date back to 2007.

Suggestions are greatly appreciated.

Thanks guys.

EDIT:

Alright so it doesnt look like ill be able to get onto the internet to do anything because nearly every time i try, i get the BSOD. Format seems imminent.

 

KB4512508

Hello --- I followed this directions and was able to get the update installed, but you said it was non-destructive, which is not exactly true --- it wiped out the update history and the only update in the history is KB4512508

How do I restore the history????

 

Intel E5200 Gets Updated, R0 Stepping Coming Up

Intel's Pentium Dual-Core E5200 processor is getting on course for a specifications update. The chip will feature in a new, improved Wolfdale-2M core, spec'd out as the R0 stepping, from its current M0 stepping. The new stepping is intended to add new instructions, power-management features, and bring about changes in the chip-package. A short list of known changes is as follows:

• CPUID changed from 10677 to 1067A
• Power State Indicator (PSI) support with Intel 4 series chipsets
• New instructions - XSAVE and XRSTOR
• New S-spec and MM numbers
• New halide-free chip package

Due to the changed CPUID, users may require BIOS updates to detect the CPU. According to the company, E5200 R0 should be out by April 13.

Source: TechConnect Magazine