Question Bsod every 10 minutes win 11

[Funti]

Hey , can some smart a$$ look to my dumping file and tell me why i am bsoding ?

Cant find this phisical device, hdd checked - no errors
Ram checked - no errors
Gpu removed ....
Thanks for your time Friends

Cpu Ryzen 7 7800x3d
Moba
PSU be quiet! Straight Power 10-CM 600W 8yold
x670 Gaming X AX V2
Ram Pamięć G.Skill Trident Z5 Neo, DDR5, 32 GB, 6000MHz
Disk New Lexar NM790 1TB 70% full
GPU gigabyte rtx 4070 super ( removed )


************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27704.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\GetLoft\Downloads\122124-5718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 26100 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff803`77a00000 PsLoadedModuleList = 0xfffff803`788f4790
Debug session time: Sat Dec 21 19:40:26.730 2024 (UTC + 1:00)
System Uptime: 0 days 0:03:40.391
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols

Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`77eb87e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff803`09ce0fc0=000000000000009f
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffff8d083cbed060, Physical Device Object of the stack
Arg3: fffff80309ce1010, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8d083cc04a60, The blocked IRP

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2015

Key : Analysis.Elapsed.mSec
Value: 2241

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27704.1001

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key : Bugcheck.Code.TargetModel
Value: 0x9f

Key : Dump.Attributes.AsUlong
Value: 21808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x9F_3_ACPI_IMAGE_pci.sys

Key : Failure.Hash
Value: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

Key : Hypervisor.Enlightenments.ValueHex
Value: 7497cf94

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 1

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 38408431

Key : Hypervisor.Flags.ValueHex
Value: 24a10ef

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : Stack.Pointer
Value: NMI


BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff8d083cbed060

BUGCHECK_P3: fffff80309ce1010

BUGCHECK_P4: ffff8d083cc04a60

FILE_IN_CAB: 122124-5718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: fffff803789d0640

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff80309ac0000 pci

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

DPC_STACK_BASE: FFFFF80309CE9FB0

STACK_TEXT:
fffff803`09ce0fb8 fffff803`77f8c7ed : 00000000`0000009f 00000000`00000003 ffff8d08`3cbed060 fffff803`09ce1010 : nt!KeBugCheckEx
fffff803`09ce0fc0 fffff803`77f8c5ec : fffff803`789d0640 fffff803`09ce13e0 00000000`00000000 fffff803`09ce1199 : nt!PopIrpWatchdogBugcheck+0x1f5
fffff803`09ce10a0 fffff803`77d59c0a : fffff803`057c5180 fffff803`77e9a7ff fffff803`09ce13e8 fffff803`09ce1308 : nt!PopIrpWatchdog+0xc
fffff803`09ce10d0 fffff803`77d591e3 : fffff803`057c9280 fffff803`77e9a4f7 00000000`8e592f55 fffff803`057cd260 : nt!KiProcessExpiredTimerList+0x26a
fffff803`09ce1200 fffff803`77cf96e1 : fffff803`057c5180 00000000`00000020 fffff803`057c5180 00000000`00000002 : nt!KiTimerExpiration+0x2e3
fffff803`09ce1330 fffff803`78077bfe : fffff803`057c5180 fffff803`057c5180 00000000`001a7550 00000000`00000000 : nt!KiRetireDpcList+0xaf1
fffff803`09ce15c0 00000000`00000000 : fffff803`09ce2000 fffff803`09cdb000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION: 10.0.26100.2161

STACK_COMMAND: .process /r /p 0xfffff803789cdf80; .thread 0xfffff803789d0640 ; kb

FAILURE_BUCKET_ID: 0x9F_3_ACPI_IMAGE_pci.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

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

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

Look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or even informational events being captured just before or at the time of the BSODs.

Try running "dism" and "sfc /scannow" to find and fix corrupted files.

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

m/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Dump files can be helpful but much more needs to be known.