Solved Driver power state failure BSOD, some help please.

G47 · Feb 4, 2024

Hello to all,
George here, posting for the first time regarding a BSOD I get only when I'm starting the pc when it was previously shut off. If I restart for any reason, I don't get any BSOD. After the BSOD and the necessary restart, then the system is fine for the rest of day.
The BSOD mentions "Driver power state failure".
I have removed overclocking.
All drivers are up to date.
I'm using the latest bios version 1904.
No pending Windows updates.
No unknown devices in device manager.
Windows install is two days old because of an Armory Crate problem I was trying to solve and I ended up resetting my windows installation.
I have attached the V2 Log collector file as required.

WinDbg shows the following:

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: ffff870114ee0dd0, Physical Device Object of the stack
Arg3: fffffc0ddcaef178, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff87011d187820, The blocked IRP

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

Implicit thread is now ffff8701`2b615040

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1061

Key : Analysis.Elapsed.mSec
Value: 6063

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key : Dump.Attributes.AsUlong
Value: 1808

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_SpbCx!CScxController::_OnIrpPreprocess

Key : Failure.Hash
Value: {d73aa0aa-6a67-746c-735c-4a037283fe15}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

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: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

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

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff870114ee0dd0

BUGCHECK_P3: fffffc0ddcaef178

BUGCHECK_P4: ffff87011d187820

FILE_IN_CAB: 020424-13468-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffff87012b615040

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffffc0d`e6366ce0 fffff805`0ea6c9d5 : ffffe381`68191180 00000000`00000000 ffff8701`14b40040 00000000`00000000 : nt!KiSwapContext+0x76
fffffc0d`e6366e20 fffff805`0ea6ebb7 : 00000000`00000000 ffff8701`14dfc0cc ffff8701`161fa000 00000000`00000000 : nt!KiSwapThread+0xab5
fffffc0d`e6366f70 fffff805`0ea70ad6 : ffff8701`00000000 ffff8701`00000001 ffff8701`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x137
fffffc0d`e6367020 fffff805`6e1b509c : 00000000`00000001 ffff8701`1d187820 ffff8701`1e370a60 fffff805`0eb2e607 : nt!KeWaitForSingleObject+0x256
fffffc0d`e63673c0 fffff805`136fe7c2 : 00000000`00000000 fffff805`0eb2e458 ffffe381`67e60000 ffff8701`1d187820 : SpbCx!CScxController::_OnIrpPreprocess+0x13c
fffffc0d`e6367440 fffff805`136cb964 : ffff8701`1d187820 fffffc0d`e6367540 00000000`00000000 ffff8701`1e2cec90 : Wdf01000!PreprocessIrp+0x62 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1521]
fffffc0d`e6367470 fffff805`0eb2de8a : ffff8701`2b615040 ffff8701`2b615040 fffffc0d`e6367540 ffff8701`1dddc000 : Wdf01000!FxDevice:

ispatchWithLock+0x3ea4 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1445]
fffffc0d`e63674c0 fffff805`0eb07317 : ffff8701`00000000 ffffffff`fa0a1f00 fffff805`0eb2da20 ffff8701`2daf8290 : nt!PopIrpWorker+0x46a
fffffc0d`e6367570 fffff805`0ec1bc54 : ffffe381`67e51180 ffff8701`2b615040 fffff805`0eb072c0 00000000`00000246 : nt!PspSystemThreadStartup+0x57
fffffc0d`e63675c0 00000000`00000000 : fffffc0d`e6368000 fffffc0d`e6361000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: SpbCx!CScxController::_OnIrpPreprocess+13c

MODULE_NAME: SpbCx

IMAGE_NAME: SpbCx.sys

IMAGE_VERSION: 10.0.22621.3139

STACK_COMMAND: .process /r /p 0xffff870114bc3040; .thread 0xffff87012b615040 ; kb

BUCKET_ID_FUNC_OFFSET: 13c

FAILURE_BUCKET_ID: 0x9F_3_SpbCx!CScxController::_OnIrpPreprocess

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d73aa0aa-6a67-746c-735c-4a037283fe15}

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

Then I run kd> !ffff87011d187820 and I got:

Irp is active with 6 stacks 5 is current (= 0xffff87011d187a10)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffff87011e2cec90 00000000 fffff8050eb2d130-ffff87011e370208 Success Error Cancel pending
Unable to load image amdi2c.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdi2c.sys
\Driver\amdi2c nt!PopRequestCompletion
Args: 00000000 00000001 00000004 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffff87011e370208

Args: 00000000 00000000 00000000 00000000

BlueSceen View mentions ntoskrnl.exe+416bc0 as the crash address (please see attached screenshot).

Any help by the experts will be greatly appreciated because I can't find the cause myself.
Please let me know if I forgot anything, I read the posting instructions and I think that's everything.
Thank you.

Ghot · Feb 4, 2024

Hello @G47 and welcome to ElevenForum.

The general consensus regarding Armory Crate is... get rid of it ASAP.
It causes a LOT of problems.

As for the BSODs one of the BSOD analyzers will be here sooner or later.
There's not many of them, so be patient.

@zbook

G47 · Feb 4, 2024

Hello and thank you!
Regarding Armory Crate, I know....I found out after the problem I faced while I was googling.
Unfortunately it's the only way to control my aio's screen. In any way, I think it's solved now (fingers crossed) after the reset, but the blue screen emerged.
Will be patient, thank you!

Ghot · Feb 4, 2024

I

G47 said:
Unfortunately it's the only way to control my aio's screen

Maybe you could just glue a picture on the screen, and then remove Armory Crate.

That's one seriously nice AIO cooler you have there. ^^

zbook · Feb 4, 2024

Please perform the following steps: (in sequence)

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Uninstall Bitdefender using the applicable uninstall tool:

Uninstall Bitdefender

www.bitdefender.com

Uninstall Bitdefender

www.bitdefender.com

Using the Uninstall Tool to remove Bitdefender Endpoint Security Tools

www.bitdefender.com

3) Make a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

4) Read this link on WDV:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

5) Start WDV with these settings:

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers
c) Start the tool with the 3 customized tests displayed in the Ten Forums tutorial

6) Plan to run the WDV tool with various customized tests for approximately 48 hrs

Make sure that the WDV tool is started with these 3 customized tests:

[ ] 0x00000010 I/O verification.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.

7) If there is no immediate BSOD after starting WDV then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

8) For any BSOD post a new V2 share link into the newest post

G47 · Feb 4, 2024

Thank you for your reply, will do and come back with results.

x BlueRobot · Feb 4, 2024

G47 said:
Any help by the experts will be greatly appreciated because I can't find the cause myself.

You already did though in your own dump file analysis?

Just update your AMD I2C Controller driver which you should be able to do using the AMD update tool: https://www.amd.com/en/support, you can use the auto-detect tool.

There is no need to remove BitDefender and certainly no need to run Driver Verifier on a Stop 0x9F bugcheck.

G47 · Feb 4, 2024

x BlueRobot said:
You already did though in your own dump file analysis?

Just update your AMD I2C Controller driver which you should be able to do using the AMD update tool: https://www.amd.com/en/support, you can use the auto-detect tool.

There is no need to remove BitDefender and certainly no need to run Driver Verifier on a Stop 0x9F bugcheck.

Well, I kind of did as I just replicated the kd> !ffff87011d187820 that I found on a random forum while trying to find something that I could interpret myself, but I couldn't.
So what I did is to install the AMD I2C Controller driver again from this link:

https://www.amd.com/en/support/apu/amd-ryzen-processors/amd-ryzen-7-processors/amd-ryzen-7-7800x3d

The driver was up to date but I did it anyway. Unfortunately no luck as I get the same blue screen.

The autodetect tool just reinstalled Adrenalin.

The summary after the installation:

AMD Chipset Software Install Summary

Name : AMD I2C Driver
Version : 1.2.0.124
Install : Success

Name : AMD GPIO Driver
Version : 2.2.0.130
Install : Success

Name : AMD GPIO Driver (for Promontory)
Version : 3.0.0.0
Install : Fail

Name : AMD PSP Driver
Version : 5.26.0.0
Install : Success

Name : AMD SMBus Driver
Version : 5.12.0.38
Install : Success

Name : AMD PPM Provisioning File Driver
Version : 8.0.0.27
Install : Success

Name : AMD 3D V-Cache Performance Optimizer Driver
Version : 1.0.0.7
Install : Success

zbook · Feb 4, 2024

Please follow the instructions in post #5.

x BlueRobot · Feb 4, 2024

G47 said:
Well, I kind of did as I just replicated the kd> !ffff87011d187820 that I found on a random forum while trying to find something that I could interpret myself, but I couldn't.

Do you mean !irp ffff87011d187820? If you had additional crashes, then please upload the dump files from the following directory:

Code:

%systemroot%\Minidump

G47 · Feb 4, 2024

zbook said:
Please follow the instructions in post #5.

Ok. Should I report after every step or after I complete all of them?
I will be coming back with questions most probably as I'm really new to this.

x BlueRobot said:
Do you mean !irp ffff87011d187820? If you had additional crashes, then please upload the dump files from the following directory:

Code:

%systemroot%\Minidump

Yes, my bad, that's what I mean.
I uploaded the dump that I got right after updating the I2C driver.
I can't see any difference to be honest.

WinDbg gets me the following:

9: 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: ffff818f6a5e5de0, Physical Device Object of the stack
Arg3: ffffaa0420b07178, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff818f72a58420, The blocked IRP

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

Implicit thread is now ffff818f`7f781040

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1031

Key : Analysis.Elapsed.mSec
Value: 13397

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x9f

Key : Dump.Attributes.AsUlong
Value: 1808

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_SpbCx!CScxController::_OnIrpPreprocess

Key : Failure.Hash
Value: {d73aa0aa-6a67-746c-735c-4a037283fe15}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

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: 4853999

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

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

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffff818f6a5e5de0

BUGCHECK_P3: ffffaa0420b07178

BUGCHECK_P4: ffff818f72a58420

FILE_IN_CAB: 020424-15078-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE: 3

FAULTING_THREAD: ffff818f7f781040

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffaa04`23ffece0 fffff805`6e86c9d5 : ffff9501`c1798180 00000000`00000000 ffff818f`6a23a040 00000000`00000000 : nt!KiSwapContext+0x76
ffffaa04`23ffee20 fffff805`6e86ebb7 : 00000000`00000000 ffff818f`6a3fa39c ffff818f`6a4e9000 00000000`00000000 : nt!KiSwapThread+0xab5
ffffaa04`23ffef70 fffff805`6e870ad6 : ffff818f`00000000 ffff818f`00000001 ffff818f`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x137
ffffaa04`23fff020 fffff805`ea59509c : 00000000`00000001 ffff818f`72a58420 ffff818f`72a68a60 fffff805`6e92e607 : nt!KeWaitForSingleObject+0x256
ffffaa04`23fff3c0 fffff805`719fe7c2 : 00000000`00000000 fffff805`6e92e458 ffff9501`c1060000 ffff818f`72a58420 : SpbCx!CScxController::_OnIrpPreprocess+0x13c
ffffaa04`23fff440 fffff805`719cb964 : ffff818f`72a58420 ffffaa04`23fff540 00000000`00000000 ffff818f`72889c90 : Wdf01000!PreprocessIrp+0x62 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1521]
ffffaa04`23fff470 fffff805`6e92de8a : ffff818f`7f781040 ffff818f`7f781040 ffffaa04`23fff540 ffff818f`723a8000 : Wdf01000!FxDevice:

ispatchWithLock+0x3ea4 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1445]
ffffaa04`23fff4c0 fffff805`6e907317 : ffff818f`00000006 ffffffff`fa0a1f00 fffff805`6e92da20 ffff818f`77fffa30 : nt!PopIrpWorker+0x46a
ffffaa04`23fff570 fffff805`6ea1bc54 : ffff9501`c1051180 ffff818f`7f781040 fffff805`6e9072c0 00000000`00000246 : nt!PspSystemThreadStartup+0x57
ffffaa04`23fff5c0 00000000`00000000 : ffffaa04`24000000 ffffaa04`23ff9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: SpbCx!CScxController::_OnIrpPreprocess+13c

MODULE_NAME: SpbCx

IMAGE_NAME: SpbCx.sys

IMAGE_VERSION: 10.0.22621.3139

STACK_COMMAND: .process /r /p 0xffff818f6a1d3040; .thread 0xffff818f7f781040 ; kb

BUCKET_ID_FUNC_OFFSET: 13c

FAILURE_BUCKET_ID: 0x9F_3_SpbCx!CScxController::_OnIrpPreprocess

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d73aa0aa-6a67-746c-735c-4a037283fe15}

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

9: kd> !irp ffff818f72a58420
Irp is active with 6 stacks 5 is current (= 0xffff818f72a58610)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffff818f72889c90 00000000 fffff8056e92d130-ffff818f72a68208 Success Error Cancel pending
Unable to load image amdi2c.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdi2c.sys
\Driver\amdi2c nt!PopRequestCompletion
Args: 00000000 00000001 00000004 00000000
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffff818f72a68208

Args: 00000000 00000000 00000000 00000000

zbook · Feb 4, 2024

For each group of customized tests post one of these share links:

V2

or

verifier /querysettings

zbook · Feb 4, 2024

Please uninstall Bitdefender.

Make sure that Microsoft defender is on.

zbook · Feb 4, 2024

When available update the progress with post #5.

G47 · Feb 4, 2024

zbook said:
Please perform the following steps: (in sequence)

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Uninstall Bitdefender using the applicable uninstall tool:

Uninstall Bitdefender

Uninstall Bitdefender

www.bitdefender.com

Uninstall Bitdefender

Uninstall Bitdefender

www.bitdefender.com

Using the Uninstall Tool to remove Bitdefender Endpoint Security Tools

www.bitdefender.com

3) Make a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

4) Read this link on WDV:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

5) Start WDV with these settings:

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers
c) Start the tool with the 3 customized tests displayed in the Ten Forums tutorial

6) Plan to run the WDV tool with various customized tests for approximately 48 hrs

Make sure that the WDV tool is started with these 3 customized tests:

[ ] 0x00000010 I/O verification.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.

7) If there is no immediate BSOD after starting WDV then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

8) For any BSOD post a new V2 share link into the newest post

1) Please see attached file.
I'm copy pasting as a spoiler below if that's convenient:

Microsoft Windows 11 Pro Version 23H2 (OS Build 22631.3085)

==================================================================

Started on ??? 04/02/2024 at 21:49:53,28

[SFC /ScanNow]

Beginning system scan. This process will take some time.

Results:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on ??? 04/02/2024 at 21:50:58,35

[DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3085

No component store corruption detected.

The operation completed successfully.

==================================================================

Started on ??? 04/02/2024 at 21:51:43,05

[DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.2792

Image Version: 10.0.22631.3085

The restore operation completed successfully.

The operation completed successfully.

==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.

==================================================================

Started on ??? 04/02/2024 at 21:52:23,74

[ChkDsk /Scan]

The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
509184 file records processed.
File verification completed.
Phase duration (File record verification): 3.15 seconds.
23334 large file records processed.
Phase duration (Orphan file record recovery): 9.29 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.02 milliseconds.

Stage 2: Examining file name linkage ...
224 reparse records processed.
628020 index entries processed.
Index verification completed.
Phase duration (Index verification): 3.25 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 284.90 milliseconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.05 milliseconds.
224 reparse records processed.
Phase duration (Reparse point and Object ID verification): 1.41 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 52.11 milliseconds.
59419 data files processed.
Phase duration (Data attribute verification): 0.04 milliseconds.
CHKDSK is verifying Usn Journal...
33870256 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 50.97 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.

975950847 KB total disk space.
77055820 KB in 212951 files.
131484 KB in 59420 indexes.
0 KB in bad sectors.
653447 KB in use by the system.
65536 KB occupied by the log file.
898110096 KB available on disk.

4096 bytes in each allocation unit.
243987711 total allocation units on disk.
224527524 allocation units available on disk.
Total duration: 6.81 seconds (6814 ms).

==================================================================

Started on ??? 04/02/2024 at 21:52:37,35

AutoReboot

TRUE

==================================================================

[Set AutoReboot = False]

Updating property(s) of '\\OPTIMUS2\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================

AutoReboot

FALSE

==================================================================

DebugInfoType

3

==================================================================

[Set DebugInfoType = 7]

Updating property(s) of '\\OPTIMUS2\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================

DebugInfoType

7

==================================================================

[WMIC PageFile list]

AllocatedBaseSize=5120
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20230917145728.829145+180
Name=C:\pagefile.sys
PeakUsage=0
Status=
TempPageFile=FALSE

==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[Set AutomaticManagedPagefile = True]

Updating property(s) of '\\OPTIMUS2\ROOT\CIMV2:Win32_ComputerSystem.Name="OPTIMUS2"'
Property(s) update successful.
==================================================================

AutomaticManagedPagefile

TRUE

==================================================================

[BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier {badmemory}

==================================================================

Finished on ??? 04/02/2024 at 21:52:38,16
It took minutes and seconds to complete the operations.

2)Done even before step one just in case that changed anything. It didn't, upon powering on the pc I had the same BSOD.

3) Done.

I now have to educate myself about WDV and I will come back with what I found or questions.

Thank you all again.

zbook · Feb 4, 2024

Bitdefender was uninstalled as it sometimes interferes with V2.

When available post either V2 or querysettings for each run of WDV.

G47 · Feb 4, 2024

zbook said:
Please perform the following steps: (in sequence)

1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Uninstall Bitdefender using the applicable uninstall tool:

Uninstall Bitdefender

Uninstall Bitdefender

www.bitdefender.com

Uninstall Bitdefender

Uninstall Bitdefender

www.bitdefender.com

Using the Uninstall Tool to remove Bitdefender Endpoint Security Tools

www.bitdefender.com

3) Make a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

4) Read this link on WDV:

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

5) Start WDV with these settings:

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers
c) Start the tool with the 3 customized tests displayed in the Ten Forums tutorial

6) Plan to run the WDV tool with various customized tests for approximately 48 hrs

Make sure that the WDV tool is started with these 3 customized tests:

[ ] 0x00000010 I/O verification.
[ ] 0x00000200 Force pending I/O requests.
[ ] 0x00000400 IRP logging.

7) If there is no immediate BSOD after starting WDV then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

8) For any BSOD post a new V2 share link into the newest post

5)
I couldn't even complete 10 seconds of the verifier and there was a blue screen (HID Class Driver).
I had to use the restore point as command prompt didn't work.
I'm posting a V2 again.
Does that lead us anywhere?

zbook · Feb 4, 2024

1) Please restart WDV with only:

[ ] 0x00000010 I/O verification.

2) If there is no immediate BSOD after starting WDV then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.

3) For any BSOD post a new V2 share link into the newest post