Windows 10: Recent Intermittent BSODs After KB4576478 & KB4571756

Hey Win10 Crew,

Since the most recent Windows updates: KB4576478 & KB4571756 I've been having intermittent BSODs at odd times with the most recent one at 4:20AM ish (Eastern Timezone) today Sept 19 2020. I'm not a super Windows admin but I knew enough to be able to take the minidump and run it against the WindowsDebugger WinDbg which is below.

I installed KB4576478 & KB4571756 on Sept 14 2020 and it's been a nightmare since then.

Do you have any idea what's happening here? What would you suggest that I do as the next steps?

Also, if this forum is not the right place, please tell me. I'm new to this subreddit.

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\myuserfolder\Desktop\091920-8375-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff805`18200000 PsLoadedModuleList = 0xfffff805`18e2a310 Debug session time: Sat Sep 19 04:23:28.376 2020 (UTC - 4:00) System Uptime: 1 days 13:42:59.968 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................................... Loading User Symbols Loading unloaded module list ................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805`185f3ea0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb08d`7ecd6000=000000000000000a 7: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000068, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff80518489c5c, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1406 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on KRONOS Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 1828 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: a BUGCHECK_P1: 68 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff80518489c5c READ_ADDRESS: fffff80518efa390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff80518e0f2e0: Unable to get Flags value from nt!KdVersionBlock fffff80518e0f2e0: Unable to get Flags value from nt!KdVersionBlock unable to get nt!MmSpecialPagesInUse 0000000000000068 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: csrss.exe TRAP_FRAME: ffffb08d7ecd6140 -- (.trap 0xffffb08d7ecd6140) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffe4810f300180 rbx=0000000000000000 rcx=ffffe4810f300180 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80518489c5c rsp=ffffb08d7ecd62d0 rbp=ffff9986ed3870c0 r8=ffff9986ed3870c0 r9=ffffb08d7ecd6301 r10=ffffe4810f300180 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiEvaluateGroupSchedulingPreemption+0x3c: fffff805`18489c5c 488b7268 mov rsi,qword ptr [rdx+68h] ds:00000000`00000068=???????????????? Resetting default scope STACK_TEXT: ffffb08d`7ecd5ff8 fffff805`18605e69 : 00000000`0000000a 00000000`00000068 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffb08d`7ecd6000 fffff805`18602169 : 00000000`00000000 fffff805`18200000 00000048`041002f5 00000000`00000004 : nt!KiBugCheckDispatch+0x69 ffffb08d`7ecd6140 fffff805`18489c5c : ffffb150`9819b5c1 55555555`55555555 ffffe481`0f6c0100 00000000`00000000 : nt!KiPageFault+0x469 ffffb08d`7ecd62d0 fffff805`184ca642 : ffff9986`ed3870c0 0000013c`00000000 ffff9986`ed3870c0 00000000`00000000 : nt!KiEvaluateGroupSchedulingPreemption+0x3c ffffb08d`7ecd6330 fffff805`184c9861 : 00000000`00000000 ffff9986`00000002 ffff9986`ed387001 fffff805`184c5360 : nt!KiDeferredReadySingleThread+0xb22 ffffb08d`7ecd6520 fffff805`184c92ea : 00000000`00000000 ffff801d`00000000 ffff9986`ed7457e0 ffffe481`0f8c0180 : nt!KiExitDispatcher+0x141 ffffb08d`7ecd6590 ffff8053`8c8b99f9 : ffff9986`ed074b00 ffff801d`428b4b48 00000000`00000001 ffff9986`ed52f3d0 : nt!KeSetEvent+0xea ffffb08d`7ecd6620 ffff8053`8c8b9346 : 00000000`0000000f 00000000`0817d680 00000000`00000001 00000000`00000004 : win32kfull!TimersProc+0x399 ffffb08d`7ecd66b0 ffff8053`8be81eb4 : ffff9986`e84d7080 ffff9986`e84d7080 00000000`00000000 00000000`00000005 : win32kfull!RawInputThread+0x7f6 ffffb08d`7ecd6870 ffff8053`8c858961 : ffff9986`e84d7080 00000000`00000000 00000000`00000005 00000000`00000005 : win32kbase!xxxCreateSystemThreads+0xc4 ffffb08d`7ecd69a0 ffff8053`8c3e474e : ffff9986`e84d7080 00000281`2d005180 00000000`000004ac 00007ff8`c4de3740 : win32kfull!NtUserCallNoParam+0x71 ffffb08d`7ecd69d0 fffff805`18605dee : ffff9986`00000005 00000000`00000005 00000281`2d005180 00000000`000004ac : win32k!NtUserCallNoParam+0x16 ffffb08d`7ecd6a00 00007ff8`c56e10e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2b9 00000092`e5f7f7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`c56e10e4 SYMBOL_NAME: win32kfull!TimersProc+399 MODULE_NAME: win32kfull IMAGE_NAME: win32kfull.sys IMAGE_VERSION: 10.0.19041.508 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 399 FAILURE_BUCKET_ID: AV_win32kfull!TimersProc OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {4204da86-0e34-a6fb-28f3-793ac186b089} Followup: MachineOwner ---------
submitted by /u/lemateogunner
[link] [comments]

:)

 

2 bsod after update win10 v1903 to 2004 - and 1 bsod from windows updates: KB4571756 / KB4577266 / KB4576478

Hi Igor

My pc is about 2 years ago:

Asus Prime Z370-P - i7 8700@4,3 - G.Skill F4-3200C14D-16GTZSW 2x8 Gb - EVGA GTX 1080 SC 8Gb ddr5x

SSD SAMSUNG evo 850 1 Tb

Be Quiet! Straight Power 10 700W 80 Plus Gold

I update audio drivers after first bsod when I update from v1903 to v2004

Now all drivers are up to date and bios too

The third bsod after windows updates KB4571756 / KB4577266 / KB4576478

I could check another person with same promble with these updates :

BSOD after update - any help for Ideapad-700?-English Community

 

BSOD when computer idle

my computer has BSOD 5 times today (12th September). I'm suspecting this problem is caused by installing the windows update KB4571756 and KB4576478 on the 11th September.

 

KB4571756 Fails, error code: 0x8007000d

Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x8007000d)

I tried the steps found in

KB4571756 doesn't install

for problem:

KB4571756 doesn't install error code 0x800F0984
None of those steps helped.

0x800F0984