BSOD event id 41 bugcheck code 159

Question

BSOD event id 41 bugcheck code 159

James Stennett 20

I've recently built a new computer and within minutes of finishing I installed windows 11 home onto the it, this was the 26/06/25. within 3 days of this, I'd unknowingly received my first Kernel-power critical event event ID 41. As I had my first BSOD today at 12:00;59 I checked event viewer as per a few people recommendations and found the exact same event had occurred several times over the past 3-4 weeks. I've had some stuttering in games but today before the crash was unplayable, my keyboard and mouse lagged in directions I had inputted for mere milliseconds and as per another post (https://learn.microsoft.com/en-us/answers/questions/3184538/bsod-event-id-41-bugcheck-code-159) I'm left wondering if my BeQuiet! IO centre for my keyboard is the cause as I've noticed it using nearly 50% of my CPU at points, something I assume is bad given I have a 7950X3D. anyway, If anyone could help I'll have the XML view of the error code copied below:

<Channel>System</Channel>

<Computer>My-Puper</Computer>

</System>

<EventData>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="BugcheckInfoFromEFI">false</Data>

<Data Name="LongPowerButtonPressDetected">false</Data>

<Data Name="LidReliability">false</Data>

</EventData>

</Event>

I can't figure out how to save the minidump file so I hope a copy/paste of it here will suffice:

23: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................................
Loading User Symbols

Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        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: ffffe68e4db0c060, Physical Device Object of the stack
Arg3: ffffaa8999b0f000, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe68e5f9c7010, The blocked IRP

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1375

    Key  : Analysis.Elapsed.mSec
    Value: 6982

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    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_qcwlan64_IMAGE_pci.sys

    Key  : Failure.Hash
    Value: {9ca15696-4306-2f47-216c-2b9592843f7a}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    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: 0x24a10ef

    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: 0x3f7


BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffe68e4db0c060

BUGCHECK_P3: ffffaa8999b0f000

BUGCHECK_P4: ffffe68e5f9c7010

FILE_IN_CAB:  072325-17937-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe68e4a78a280

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff8047eac0000 pci

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffaa89`99b0efa8 fffff804`ec9cf3ed     : 00000000`0000009f 00000000`00000003 ffffe68e`4db0c060 ffffaa89`99b0f000 : nt!KeBugCheckEx
ffffaa89`99b0efb0 fffff804`ec9cf1ec     : ffffe68e`4a78a280 ffffaa89`99b0f3e0 ffffe68e`5f1af2d0 ffffaa89`99b0f189 : nt!PopIrpWatchdogBugcheck+0x1f5
ffffaa89`99b0f090 fffff804`ec751b12     : ffffc401`00000016 fffff804`00000001 ffffaa89`00000000 fffff804`00000002 : nt!PopIrpWatchdog+0xc
ffffaa89`99b0f0c0 fffff804`ec7523f5     : 00000247`bca5febd 00000000`0000000f 00000107`1133efdb ffffc401`ccdce180 : nt!KiProcessExpiredTimerList+0x502
ffffaa89`99b0f1f0 fffff804`ec6c8235     : 00000000`00000000 00000000`00000000 ffffc401`ccdce180 ffffe68e`4a78a280 : nt!KiTimerExpiration+0x2b5
ffffaa89`99b0f330 fffff804`ecaa66be     : ffffc401`ccdce180 ffffc401`ccdce180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0xc45
ffffaa89`99b0f5c0 00000000`00000000     : ffffaa89`99b10000 ffffaa89`99b09000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION:  10.0.26100.4484

STACK_COMMAND: .process /r /p 0xfffff804ed3cef80; .thread 0xffffe68e4a78a280 ; kb

FAILURE_BUCKET_ID:  0x9F_3_qcwlan64_IMAGE_pci.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9ca15696-4306-2f47-216c-2b9592843f7a}

Followup:     MachineOwner

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

DaveM121 878.9K Independent Advisor

Go to the support page for your PC on the manufacturers website, then from there, download and re-install (not update) the version of Qualcomm WiFi drivers they provide, that is indicated as the cause of the system crash in your data.

With regards to the other problems you have been experiencing, I suggest completely removing the BeQuiet! IO Centre utility, then restart (not shut down) your PC and wait to test if your system is stable.

James Stennett 20 Reputation points

2025-07-23T18:28:55.52+00:00

Hi Dave,

Thank you! I had actually copied the dump into chatgpt who told me the same thing, turns out I hadn't installed that driver and I remember choosing not to as I've used ethernet from the beginning and wasn't aware of the implications. While I was at it, I installed all the other drivers and you'll never guess how many of them I'd installed, two. I had the audio driver, as well as the AMD chipset driver.

I'm now only concerned with a kernel-event trace error as the IO seems to have fixed itself with the latest patch, which I had also taken the liberty of not installing as the software is set to check updates once a fortnight and I hadn't checked. you can tell I'm great at this. I've set that to daily now along with every other piece of software on my device!

Thank you so much for the help, my computer is functioning far better than it had been. my CPU is down 5 degrees Celsius both idle and in games, I'm using 25% less of my L3 cached CCD, my fans are quieter, and my ram usage is down 4 gigs too. drivers do wonders.

Share via

BSOD event id 41 bugcheck code 159

0 additional answers

Your answer