Windows 10 ver.2004/ver.21H1 kernel crashes

Question

Windows 10 ver.2004/ver.21H1 kernel crashes

Anonymous

Overview:

My PC infrequently (once a week or more) restarts unexpectedly, without notice.

This issue lasts over 6 month among ver.2004 and ver.21H1.

Description:

This unexpected restart does not recognized by Windows kernel and no error information is recorded, of course no minidump or no MEMORY.DMP. Critical error is recorded after unexpected restart, but the reason is unknown.

CRITICAL: Event ID 41: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Some curious events happen before every restart.

CRITICAL: Event ID:6008 : The previous system shutdown at 8:56:44 on ‎2021/‎09/‎20 was unexpected.

This event is puzzling, because I never shutdown PC at that time and PC never booted at that time. My PC is laptop so even if AC power is off, PC still works (I always use PC connected to AC adapter).

Another event happens before the event 6008.

INFORMATION: Source HAL: Event ID:16: The iommu fault reporting has been initialized.

IOMMU (I/O virtualization unit of AMD Ryzen) driver seemed to report some kind of errors, but no error related to I/O recorded in the event log.

Today, I got a rare event log (so I decided to post the issue here). The crash happened during WindowsUpdate. Therefore Windows created memory.dmp and recorded some events related to the crash.

09/20/2021 9:18:43 ID:7034 The System Update service terminated unexpectedly. It has done this 1 time(s).

...

09/20/2021 9:07:28 ID:1001

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000a0 ( 0x0000000000000608, 0xffff9a83ec228528, 0x0000000000000000, 0x0000000000000000 ). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9a29436c-7156-45ee-9847-2ca5cfbf269f.

After analyzing memory.dmp, I've got the information below.

******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************INTERNAL_POWER_ERROR (a0)The power policy manager experienced a fatal error.Arguments:Arg1: 0000000000000608, A driver has attempted to transition a component to idle without a preceding active request.Arg2: ffff9a83ec228528, POP_FX_COMPONENT componentArg3: 0000000000000000, POP_FX_COMPONENT_FLAGS component conditionArg4: 0000000000000000Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3093 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 3116 Key : Analysis.Init.CPU.mSec Value: 390 Key : Analysis.Init.Elapsed.mSec Value: 43893 Key : Analysis.Memory.CommitPeak.Mb Value: 76 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.1BUGCHECK_CODE: a0BUGCHECK_P1: 608BUGCHECK_P2: ffff9a83ec228528BUGCHECK_P3: 0BUGCHECK_P4: 0BLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1PROCESS_NAME: SystemSTACK_TEXT: ffff828afe2534f8 fffff803113640a8 : 00000000000000a0 0000000000000608 ffff9a83ec228528 0000000000000000 : nt!KeBugCheckExffff828afe253500 fffff803112510a6 : ffff828afe2535f0 ffff9a83ec1e41a0 0000000000000000 ffff9a83ec5d4020 : nt!PopFxBugCheck+0x1cffff828afe253540 fffff803110c9ed9 : 00000168109b7ec3 0000000000000000 0000000000000000 ffff9a83eca618a0 : nt!PopFxIdleComponent+0x1871b6ffff828afe2535a0 fffff8031522c647 : ffff9a83ec1e41a0 ffff9a83ec22a1a0 0000000000000000 0000000000000000 : nt!PoFxIdleComponent+0x39ffff828afe253610 fffff80315208fc0 : 0000000000000003 ffff9a83ec22a1a0 ffff9a83ec22a1a0 ffff9a84048a1e00 : storport!RaidAdapterPoFxIdleComponent+0x1fffff828afe253640 fffff8031521ad8b : ffff828afe253820 0000000000000000 fffff78000000320 ffff9a83ec5d4020 : storport!RaidUnitCompleteRequest+0x5e0ffff828afe2537c0 fffff8031109a3be : ffff828afe253b30 ffff9a83ea414000 0000000000000400 ffff9a8400000002 : storport!RaidpAdapterRedirectDpcRoutine+0x8bffff828afe253860 fffff803110996a4 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30effff828afe2539d0 fffff803111fad2e : ffffffff00000000 ffffae00c5791180 ffffae00c579c240 ffff9a8402535040 : nt!KiRetireDpcList+0x1f4ffff828afe253c60 0000000000000000 : ffff828afe254000 ffff828afe24e000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9eSYMBOL_NAME: storport!RaidAdapterPoFxIdleComponent+1fMODULE_NAME: storportIMAGE_NAME: storport.sysSTACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 1fFAILURE_BUCKET_ID: 0xa0_608_stornvme_storport!RaidAdapterPoFxIdleComponentOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {bf5ae663-b710-adc0-5c18-f8ecaafd9387}Followup: MachineOwner---------4: kd> .f+01 ffff828afe253500 fffff803112510a6 nt!PopFxBugCheck+0x1c

As you see, storport.sys seemed to get a fatal error, but the reason is unknown. (and I don't use RAID)

Other events related to the crash is exactly the same as before (same as the other unexpected restarts).

I don't expect that this issue will be solved easily. rather, expect that some engineer notices the existence of a kind of design error.

PC specification:

AMD Ryzen 7 4700U

16GB memory

512GB SSD

chkdsk, sfc and dism reported no error. PC diagnostics tool reported no error. Windows and device drivers are up-to-date.

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

4 answers

Answer 1

Hi, same bug, same behaviour (frozen screen and all controls - keyboard, mouse) few seconds before crash. I can provide dump file, just let me know.

I installed every driver directly from Lenovo websites around 5/2021. No new/updated drivers installed recently. This is the first time when this occurs.

Lenovo T14s, AMD Ryzen 7 PRO 4750U, 32 GB RAM, 1TB WDC PC SN730 SDBQNTY-1T00-1001

Windows 10 Pro, 21H1, Build 19043.1288

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000608, A driver has attempted to transition a component to idle without
a preceding active request.
Arg2: ffffc70295fe2058, POP_FX_COMPONENT component
Arg3: 0000000000000000, POP_FX_COMPONENT_FLAGS component condition
Arg4: 0000000000000000

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4390

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11116

    Key  : Analysis.Init.CPU.mSec
    Value: 1171

    Key  : Analysis.Init.Elapsed.mSec
    Value: 54241

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 81

    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

FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  a0

BUGCHECK_P1: 608

BUGCHECK_P2: ffffc70295fe2058

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
ffff8c0d`cf2374f8 fffff805`64b640a8     : 00000000`000000a0 00000000`00000608 ffffc702`95fe2058 00000000`00000000 : nt!KeBugCheckEx
ffff8c0d`cf237500 fffff805`64a510a6     : ffff8c0d`cf2375f0 ffffc702`95e381a0 00000000`00000000 ffffc702`99c11020 : nt!PopFxBugCheck+0x1c
ffff8c0d`cf237540 fffff805`648c9ed9     : 000000d0`ea39cf52 00000000`00000000 00000000`00000000 ffffc702`99d948a0 : nt!PopFxIdleComponent+0x1871b6
ffff8c0d`cf2375a0 fffff805`6283c647     : ffffc702`95e381a0 ffffc702`95fe31a0 00000000`00000000 00000000`00000000 : nt!PoFxIdleComponent+0x39
ffff8c0d`cf237610 fffff805`62818fc0     : 00000000`00000003 ffffc702`95fe31a0 ffffc702`95fe31a0 ffffc702`9aa4fa00 : storport!RaidAdapterPoFxIdleComponent+0x1f
ffff8c0d`cf237640 fffff805`6282ad8b     : ffff8c0d`cf237820 00000000`00000000 fffff780`00000320 ffffc702`99c11020 : storport!RaidUnitCompleteRequest+0x5e0
ffff8c0d`cf2377c0 fffff805`6489a24e     : ffff8c0d`cf237b30 ffffc702`929e0000 00000000`00000400 00000000`00000002 : storport!RaidpAdapterRedirectDpcRoutine+0x8b
ffff8c0d`cf237860 fffff805`64899534     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffff8c0d`cf2379d0 fffff805`649fad1e     : ffffffff`00000000 ffffb681`3f7c0180 ffffb681`3f7cb440 ffffc702`ac0df040 : nt!KiRetireDpcList+0x1f4
ffff8c0d`cf237c60 00000000`00000000     : ffff8c0d`cf238000 ffff8c0d`cf232000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME:  storport!RaidAdapterPoFxIdleComponent+1f

MODULE_NAME: storport

IMAGE_NAME:  storport.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f

FAILURE_BUCKET_ID:  0xa0_608_stornvme_storport!RaidAdapterPoFxIdleComponent

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {bf5ae663-b710-adc0-5c18-f8ecaafd9387}

Followup:     MachineOwner
---------

Answer 2

Same bug, same OS version, same FAILURE_ID_HASH. Computer is 10400F i5 with GTX 1660 Super, 16GB DDR4 3000Mhz RAM, 2x8GB, with 512GB NVMe SSD. Motherboard is gigabyte b460m ds3h ac v2:

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff80150a00000 PsLoadedModuleList = 0xfffff8015162a230

Debug session time: Thu Oct 7 15:01:36.900 2021 (UTC - 7:00)

System Uptime: 0 days 3:22:43.577

Loading Kernel Symbols

...............................................................

................................................................

........

Loading User Symbols

Loading unloaded module list

............

For analysis of this file, run !analyze -v

9: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

INTERNAL_POWER_ERROR (a0)

The power policy manager experienced a fatal error.

Arguments:

Arg1: 0000000000000608, A driver has attempted to transition a component to idle without

a preceeding active request.

Arg2: ffffe08cad317058, POP_FX_COMPONENT component

Arg3: 0000000000000000, POP_FX_COMPONENT_FLAGS component condition

Arg4: 0000000000000000

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 2203 

Key  : Analysis.DebugAnalysisManager 

Value: Create 

Key  : Analysis.Elapsed.mSec 

Value: 5069 

Key  : Analysis.Init.CPU.mSec 

Value: 4093 

Key  : Analysis.Init.Elapsed.mSec 

Value: 41520 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 89 

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

BUGCHECK_CODE: a0

BUGCHECK_P1: 608

BUGCHECK_P2: ffffe08cad317058

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:

ffff9b88816af3f8 fffff80150f640e8 : 00000000000000a0 0000000000000608 ffffe08cad317058 0000000000000000 : nt!KeBugCheckEx

ffff9b88816af400 fffff80150e510e0 : ffff9b88816af4f0 ffffe08cad28d1a0 0000000000000000 ffffe08cad87d020 : nt!PopFxBugCheck+0x1c

ffff9b88816af440 fffff80150cc9ec9 : 0000001c520eb507 0000000000000000 0000000000000000 ffffe08cada408a0 : nt!PopFxIdleComponent+0x187200

ffff9b88816af4a0 fffff801529fc647 : ffffe08cad28d1a0 ffffe08cad3181a0 0000000000000000 0000000000000000 : nt!PoFxIdleComponent+0x39

ffff9b88816af510 fffff801529d8fc0 : 0000000000000003 ffffe08cad3181a0 ffffe08cad3181a0 ffffe08ccb981800 : storport!RaidAdapterPoFxIdleComponent+0x1f

ffff9b88816af540 fffff801529ead8c : 0000000000000000 0000000000000000 fffff78000000320 ffffe08cad87d020 : storport!RaidUnitCompleteRequest+0x5e0

ffff9b88816af6c0 fffff80150c9a3ae : ffff9b88816afa20 0000000000000000 0000000000000004 ffffa100f06d2180 : storport!RaidpAdapterRedirectDpcRoutine+0x8c

ffff9b88816af760 fffff80150c99694 : 0000000000000000 0000000000000000 0000000000140001 0000000000000000 : nt!KiExecuteAllDpcs+0x30e

ffff9b88816af8d0 fffff80150dfad1e : ffffffff00000000 ffffa100f06d2180 ffffa100f06dd340 ffffe08cc3bc9040 : nt!KiRetireDpcList+0x1f4

ffff9b88816afb60 0000000000000000 : ffff9b88816b0000 ffff9b88816a9000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: storport!RaidAdapterPoFxIdleComponent+1f

MODULE_NAME: storport

IMAGE_NAME: storport.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1f

FAILURE_BUCKET_ID: 0xa0_608_stornvme_storport!RaidAdapterPoFxIdleComponent

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {bf5ae663-b710-adc0-5c18-f8ecaafd9387}

Followup: MachineOwner

Answer 3

Thank you for the reply.

In the past I did safe-mode a few times and sadly got no result.

I noticed two things from the past experience.

1). PC does not respond to any input, screen is frozen immediately before unexpected restart.

2). Limiting audio device function improves this issue significantly.

From (1), I suspect DPC timeout error. In the memory dump shown in the 1st post, "storport.sys" got the error through DPC. This means that some software (ISR. DPC, or some kind of atomic transaction) inhibits IRQ too long.

ffff828afe2537c0 fffff8031109a3be : ffff828afe253b30 ffff9a83ea414000 0000000000000400 ffff9a8400000002 : storport!RaidpAdapterRedirectDpcRoutine+0x8b

(Another cause is recursive entering into ISR, but it must be prohibited in software design.)

Longest ISR execution time are mainly recorded by wdf0100.sys (about 400us) or HDAudioBus.sys(about 300us). Longest DPC exec. time is mainly recorded by ntoskrnl.exe (about 700us) or ndis.sys(about 500us). (measured with LatencyMon)

So I tested disabling audio device and almost no unexpected restart (but this method broke the integrity of the registry entries finally.)

I expect the improvement of the issue in the future.

Answer 4

Hi,

Thank you for writing to Microsoft Community Forums.

I understand that you are facing Blue Screens on your PC, and I certainly appreciate your efforts in trying to resolve the issue.

We will certainly look into this for you.

Based on the information you have shared, I see that the file storport.sys is causing the Blue Screens on the PC.

One of the things that you can try is booting the PC into Safe Mode and check if you still receive BSOD. Refer the article Start your PC in safe mode in Windows 10

In case the PC is crashing in Safe Mode, then the issue could be due to a hardware fault. However, if the PC boots normally then you can try performing Clean Boot and see if the crash appears. Refer the article How to perform a clean boot in Windows

Performing a clean boot will start the computer with minimal set of drivers and programs, to determine whether a background program is causing the issue. Some of the Startup programs will not load after performing a clean boot on the computer. However, that functionality will return when you reset the computer to start normally after finishing the troubleshooting.

If the PC is not crashing in Clean Boot, then you can refer the section How to determine what is causing the problem after you do a clean boot from the Clean Boot article.

Note: Please refer the sectionReset the computer to start normally after clean boot troubleshootingto boot the computer in to normal mode after troubleshooting.

In addition, you may want to run a hardware diagnostic on the PC to see if there is any hardware fault.

Let us know if you need any further assistance, we will be glad to assist you.

Regards,

Prakhar Khare

Microsoft Community – Moderator

Share via

Windows 10 ver.2004/ver.21H1 kernel crashes

4 answers