Hello, and welcome to the forum!
From the dumps, both BSODs failed for the same reason. They're both a 0x9F stopcode (DRIVER_POWER_STATE_FAILURE) which happens when a device, or its driver, fails to complete a power transition (from idle low power to running high power) in a reasonable time. The dump provides us with both the address of the IRP handling the power transition and the address of the Device Object which represent the device involved.
The IRP reveals that the driver that was managing the transitioning device was WdmCompanionFilter.sys, a Windows Driver Model driver, which means this could be any device or driver using the WDM libraries.
Code:
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 1 ffff900a6aae0de0 00000000 00000000-00000000 pending
\Driver\WdmCompanionFilter
Args: 00000000 00000001 00000004 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffff900a6414de00 00000000 fffff80473e76120-ffff900a5c713340 Success Error Cancel pending
\Driver\ksthunk nt!PopRequestCompletion
Args: 00000000 00000001 00000004 00000000
The Device Object address shows us information about the device, in particular the address of the Device Node...
Code:
3: kd> !devobj ffff900a6ad180a0
Device object (ffff900a6ad180a0) is for:
Cannot read info offset from nt!ObpInfoMaskToOffset
\Driver\usbccgp DriverObject ffff900a5f083e10
Current Irp 00000000 RefCount 0 Type 00000022 Flags 00003040
SecurityDescriptor ffffb300cc0440e0 DevExt ffff900a6ad181f0 DevObjExt ffff900a6ad18760 DevNode ffff900a7715da00
ExtensionFlags (0000000000)
Characteristics (0x00000180) FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffff900a66711e10 \Driver\ACPI
Device queue is not busy.
The Device Node describes the actual device and its capabilities...
Code:
3: kd> !devnode ffff900a7715da00
DevNode 0xffff900a7715da00 for PDO 0xffff900a6ad180a0
Parent 0xffff900a6003a940 Sibling 0xffff900a69d317a0 Child 0000000000
InstancePath is "USB\VID_3277&PID_0018&MI_00\7&ae5a96&0&0000"
ServiceName is "usbvideo"
State = DeviceNodeStarted (0x30a) @ 2024 Mar 30 18:14:59.079
Previous State = DeviceNodeStarted (0x30a) @ 2024 Mar 30 18:14:59.068
StateHistory[11] = DeviceNodeAwaitingQueuedDeletion (0x310)
StateHistory[10] = DeviceNodeStarted (0x30a)
StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f)
StateHistory[08] = DeviceNodeEnumeratePending (0x30e)
StateHistory[07] = DeviceNodeStarted (0x30a)
StateHistory[06] = DeviceNodeStartPostWork (0x309)
StateHistory[05] = DeviceNodeStartCompletion (0x308)
StateHistory[04] = DeviceNodeStartPending (0x307)
StateHistory[03] = DeviceNodeResourcesAssigned (0x306)
StateHistory[02] = DeviceNodeDriversAdded (0x305)
StateHistory[01] = DeviceNodeInitialized (0x304)
StateHistory[00] = DeviceNodeUninitialized (0x301)
StateHistory[19] = Unknown State (0x0)
StateHistory[18] = Unknown State (0x0)
StateHistory[17] = Unknown State (0x0)
StateHistory[16] = Unknown State (0x0)
StateHistory[15] = Unknown State (0x0)
StateHistory[14] = Unknown State (0x0)
StateHistory[13] = Unknown State (0x0)
StateHistory[12] = Unknown State (0x0)
Flags (0x28000138) DNF_REENUMERATE, DNF_ENUMERATED,
DNF_IDS_QUERIED, DNF_NO_RESOURCE_REQUIRED,
DNF_NO_LOWER_CLASS_FILTERS, DNF_NO_UPPER_DEVICE_FILTERS
CapabilityFlags (0x00100690) Removable, SilentInstall,
SurpriseRemovalOK, WakeFromD0,
SecureDevice
It's the hardware identifiers in the "InstancePath" above that describes the actual device. The USB\VID_3277&PID_0018 identifiers would appear to be your built-in webcam. You can see at the bottom of the above that the camera is capable of "WakeFromD0", which means it's capable of entering the D0 low power state and being woken from that when accessed. The 0x9F bugcheck would suggest that the camera (or the driver) has had problems waking from D0.
There isn't a specific driver for your webcam listed on the
Asus driver website for your laptop model and no recent driver updates there either. If you have the
Windows Fast Startup feature enabled (it's enabled by default) I would disable that. Windows Fast Startup hibernates the kernel on a shutdown and restores it on a reboot. Some third-party drivers don't play well with that. Fast Startup is a performance aid for HDDs and if your system drive is an SSD then Fast Startup is not needed.
If there is a Windows camera troubleshooter then run that. There is also an Asus help page with details on
how to fix common webcam issues so I would suggest you take a look at those.
It may also be a problem caused by an app that uses the webcam, so check what webcam apps are running, especially any that run in the background.
