Question "Unexpected Shutdown" multiple days in a row according to Bugcheck ?

[sanman98]

Laptop model: Lenovo Yoga 7i (Type 82BH)

12GB RAM
11th gen Intel i5-1135G7
Windows 11 pro

the device has been plugged into usb-c power attached to a monitor screen
the cord sometimes is a bit finnicky
the cord charges the device and also outputs to the screen


i've recently reinstalled Windows and even had the device in warranty repair, which they only reinstalled OS but seemed to fix a network issue

other odd thing is my Alt and Windows keys got swapped software-wise
on external keyboard

yesterday computer shut down two separate times, today happened again
got Reliability History copied inline message, and copied Event viewer for today between those 2 minutes to a Pastebin in plaintext

is minidump safe to post?
4 files
https://mega.nz/folder/xk5zFbSY#Py5UdbTyEmST6U8oHtmZkw



7:33pm

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff8807a3a2e360, 0xffff98074b4d70f8, 0xffff8807a7819920). A dump was saved in: C:\Windows\Minidump\121823-17515-01.dmp. Report Id: 51268f53-7548-4556-a7b5-533f9ba7823b.

7:33
The previous system shutdown at 7:13:54 PM on ‎12/‎18/‎2023 was unexpected.








7:35

Problem signature
Problem Event Name: BlueScreen
Code: 9f
Parameter 1: 3
Parameter 2: ffff8807a3a2e360
Parameter 3: ffff98074b4d70f8
Parameter 4: ffff8807a7819920
OS version: 10_0_22631
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.22631.2.0.0.256.48
Locale ID: 1033





Event viewer log from 7:33 to 7:35
https://pastebin.com/F6dW5P8H







same thing happened two times yesterday



The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe309a85bc360, 0xffff8083f0c8f0f8, 0xffffe309ab4028f0). A dump was saved in: C:\Windows\Minidump\121723-25890-01.dmp. Report Id: e07a00a5-d906-4719-a8c6-393fdb694697.


The previous system shutdown at 7:44:32 PM on ‎12/‎17/‎2023 was unexpected.


Problem signature
Problem Event Name: BlueScreen
Code: 9f
Parameter 1: 3
Parameter 2: ffffe309a85bc360
Parameter 3: ffff8083f0c8f0f8
Parameter 4: ffffe309ab4028f0
OS version: 10_0_22631
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.22631.2.0.0.256.48
Locale ID: 1033




Description
Faulting Application Path: C:\Windows\System32\svchost.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: svchost.exe_FrameServer
Application Version: 10.0.22621.1
Application Timestamp: 6dc5c2a5
Fault Module Name: frameserver.dll
Fault Module Version: 10.0.22621.2792
Fault Module Timestamp: 238c48bc
Exception Code: c00d4e24
Exception Offset: 000000000008a16a
OS Version: 10.0.22631.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 4008
Additional Information 2: 40082707a182b8937848a7459deb2b6f
Additional Information 3: cc64
Additional Information 4: cc64b42f3e2330ab5583a79bc3b25b4b

Extra information about the problem
Bucket ID: 4d48f1d7ea692000c3fe597ac561ea74 (1440687314637548148)




Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffdf8d76c70360, 0xfffff804371010f8, 0xffffdf8d7ae22010). A dump was saved in: C:\Windows\Minidump\121723-17625-01.dmp. Report Id: 66e02da1-7e2b-4161-a090-63dd0f18ef32.




Description
The previous system shutdown at 9:11:58 PM on ‎12/‎17/‎2023 was unexpected.



Problem signature
Problem Event Name: BlueScreen
Code: 9f
Parameter 1: 3
Parameter 2: ffffdf8d76c70360
Parameter 3: fffff804371010f8
Parameter 4: ffffdf8d7ae22010
OS version: 10_0_22631
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.22631.2.0.0.256.48
Locale ID: 1033

 

[Ralston18]

Quick shot to fix things:

Run the built in Windows troubleshooters. The troubleshooters may find and fix something.

Corrupted files: run "dism" and "sfc /scannow".

FYI:

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

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

 

[sanman98]

did troubleshooter for
windows update
Windows update issues detected
i didn;t copy the full details. didn't see exactly what it found.

tried a few other troubleshooters for misc stuff

DISM ran fine, no problem detected on checkhealth
scanhealth says The component store is repairable.
restore lagged a long time on some percent but i clicked it and it went to 100% immediately
The restore operation completed successfully.

sfc
Windows Resource Protection found corrupt files and successfully repaired them.


hopefully this is solved for now
thanks

 

[Ralston18]

 

[sanman98]

still happening

reliability history and event viewer
7:58pm
The previous system shutdown at 7:53:40 PM on ‎12/‎22/‎2023 was unexpected.

event viewer
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
date&time: 7:58pm
source: kernel-power

 

[Ralston18]

Continue watching Reliability History/Monitor and Event Viewer. Objective to find more specific information and error codes.

Reliability History may show some pattern of envents that led to the problem re-occurring. Look at the timeline as far back as you can.

Also look in Update History for any failed or problem updates that preceded the crashes re-appearence.

No problem with posting the mini-dump. There are some members herein who are well versed in reading the provided information and identifying potential culprits.

 

[Colif]

Report - mostly for me


File: 121823-17515-01.dmp (Dec 19 2023 - 11:33:17)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 22 Hour(s), 00 Min(s), and 53 Sec(s)

File: 121723-25890-01.dmp (Dec 18 2023 - 11:59:48)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 12 Hour(s), 45 Min(s), and 37 Sec(s)

File: 121723-17625-01.dmp (Dec 18 2023 - 13:32:07)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 32 Min(s), and 01 Sec(s)

File: 121323-17484-01.dmp (Dec 14 2023 - 09:51:49)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 38 Min(s), and 48 Sec(s)

Comment: 2 or more types of RAM are installed. << normal for laptops, or did you install one of them?
pci.sys is part of windows... updating chipset drivers might help

have you run automatic update? https://pcsupport.lenovo.com/us/en/...ooks/yoga-series/yoga-7-14itl5/82bh/downloads

 

[sanman98]

Report - mostly for me


File: 121823-17515-01.dmp (Dec 19 2023 - 11:33:17)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 22 Hour(s), 00 Min(s), and 53 Sec(s)

File: 121723-25890-01.dmp (Dec 18 2023 - 11:59:48)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 12 Hour(s), 45 Min(s), and 37 Sec(s)

File: 121723-17625-01.dmp (Dec 18 2023 - 13:32:07)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 32 Min(s), and 01 Sec(s)

File: 121323-17484-01.dmp (Dec 14 2023 - 09:51:49)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: pci.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 38 Min(s), and 48 Sec(s)

Comment: 2 or more types of RAM are installed. << normal for laptops, or did you install one of them?
pci.sys is part of windows... updating chipset drivers might help

have you run automatic update? https://pcsupport.lenovo.com/us/en/...ooks/yoga-series/yoga-7-14itl5/82bh/downloads

updates on this
the problem still happening

Lenovo Service Bridge for drivers updates won't load
i'm manually updating any drivers that seem new
there's a BIOS update
maybe an intel graphics also

i'll edit this post soon
do i need to update some RAM thing? it's stock unless it was Open Box or i think it's just stock.

i can get some more Event Viewer and Reliability History reports and whatever else
i gotta reboot
updated all the Windows 11 chipset stuff from Lenovo website


here's the export from Event Viewer
of Windows Logs > System
https://mega.nz/file/u41TzBgQ#gwAFQtNpudW4MNgDd4n1bliQ-FSi_gyqgEV3KvIWCRk
is that ok to post?
what else was i supposed to export?
found it

crashdumps
https://mega.nz/folder/D0UBkDBY#1DOW22yKsw9RPgz3w0H8Pg

 

[Ralston18]

Well things became worse after the May 10 failed Windows update. However, the update failure may have been caused by something else that failed.

Take a close look at all of those critical Application failure prior to May 10. What apps and error codes are listed - check the technical details

Then do the same for all of the critical failures starting May 10 and onward.

Afterthat, the next step is to disable all unnecessary app etc.. If the shutdowns stop, then begin adding back apps one at a time allowing time between additions. If/when the shutdows begin again then that app is suspect.

 

[sanman98]

Well things became worse after the May 10 failed Windows update. However, the update failure may have been caused by something else that failed.

Take a close look at all of those critical Application failure prior to May 10. What apps and error codes are listed - check the technical details

Then do the same for all of the critical failures starting May 10 and onward.

Afterthat, the next step is to disable all unnecessary app etc.. If the shutdowns stop, then begin adding back apps one at a time allowing time between additions. If/when the shutdows begin again then that app is suspect.

Whatsapp or something
and some web browsers mentioned in Reliability History


i used Autoruns to disable some stuff from startup
and i could just not open some software
maybe try uninstalling, after a backup

i'm scrolling through event viewer a little
4/29
The driver detected a controller error on \Device\Harddisk1\DR1.

Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {b5cfc211-8c30-4796-883d-91002b95042f}, had event Fatal error: The miniport has failed a power transition to operational power

4/27
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NKSQGP7F2NH-5319275A.WhatsAppDesktop.



Maybe i update Wifi drivers also now

 

[ubuysa]

Sorry, I'm a bit late to this one. All these dumps are 0x9F bugchecks, indicating that a device failed to complete a power transition in time. The dump parameters give us both the address of the IRP managing the power transition request and the address of the device object for the failing device.

The IRP managing the power transition shows that the driver that's failing is Netwtw10.sys, the Intel WiFi driver...

4: kd> !irp ffffe309ab4028f0
Irp is active with 7 stacks 5 is current (= 0xffffe309ab402ae0)
 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   
.....

>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  0 ffffe309abe18050 00000000 00000000-00000000   
          Unable to load image Netwtw10.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Netwtw10.sys
 \Driver\Netwtw10
            Args: 00000000 00000001 00000004 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe309ac062700 00000000 fffff8020ed2cf80-ffffe309b1085248 Success Error Cancel pending
           \Driver\vwifibus    nt!PopRequestCompletion
            Args: 00000000 00000001 00000004 00000000

That indicates that the problem device is a wireless adapter. The device object address leads us (via the device node address) to the identity of the failing device...

4: kd> !devnode ffffe309a86cea20
DevNode 0xffffe309a86cea20 for PDO 0xffffe309a85bc360
  Parent 0xffffe309a858dc40   Sibling 0xffffe309a85c3a20   Child 0xffffe309b4f97b20  
  InstancePath is "PCI\VEN_8086&DEV_A0F0&SUBSYS_00748086&REV_20\3&11583659&0&A3"
  ServiceName is "Netwtw10"
  State = DeviceNodeStarted (0x30a) @ 2023 Dec 17 12:16:21.688
  Previous State = DeviceNodeEnumerateCompletion (0x30f) @ 2023 Dec 17 12:16:21.688

....

  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  Flags (0x4c0000f0)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
                      DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
                      DNF_NO_UPPER_CLASS_FILTERS
  CapabilityFlags (0x00002000)  WakeFromD3

The hardware identifiers of VEN_8086&DEV_A0F0 in the InstancePath indicate that this device is an Intel AX201 wireless adapter.

The first thing to check is the driver, and the version of Netwtw10.sys that you have loaded is 9 months old...

4: kd> lmvmnetwtw10
Browse full module list
start             end                 module name
fffff802`20330000 fffff802`20894000   Netwtw10 T (no symbols)          
    Loaded symbol image file: Netwtw10.sys
    Image path: Netwtw10.sys
 Image name: Netwtw10.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Aug  6 17:51:52 2023 (64CFB388)
    CheckSum:         004F843E
    ImageSize:        00564000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I'd suggest looking for an update for that driver, either from the Lenovo website for your model of laptop or from Intel. If an updated driver doesn't stop the BSODs then you'll need to investigate the card. Laptop wireless cards are generally replaceable, although it's a bit fiddly, and they do occasionally fail.

 

[sanman98]

Sorry, I'm a bit late to this one. All these dumps are 0x9F bugchecks, indicating that a device failed to complete a power transition in time. The dump parameters give us both the address of the IRP managing the power transition request and the address of the device object for the failing device.

The IRP managing the power transition shows that the driver that's failing is Netwtw10.sys, the Intel WiFi driver...

4: kd> !irp ffffe309ab4028f0
Irp is active with 7 stacks 5 is current (= 0xffffe309ab402ae0)
 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  
.....

>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  0 ffffe309abe18050 00000000 00000000-00000000  
          Unable to load image Netwtw10.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Netwtw10.sys
 \Driver\Netwtw10
            Args: 00000000 00000001 00000004 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffe309ac062700 00000000 fffff8020ed2cf80-ffffe309b1085248 Success Error Cancel pending
           \Driver\vwifibus    nt!PopRequestCompletion
            Args: 00000000 00000001 00000004 00000000

That indicates that the problem device is a wireless adapter. The device object address leads us (via the device node address) to the identity of the failing device...

4: kd> !devnode ffffe309a86cea20
DevNode 0xffffe309a86cea20 for PDO 0xffffe309a85bc360
  Parent 0xffffe309a858dc40   Sibling 0xffffe309a85c3a20   Child 0xffffe309b4f97b20 
  InstancePath is "PCI\VEN_8086&DEV_A0F0&SUBSYS_00748086&REV_20\3&11583659&0&A3"
  ServiceName is "Netwtw10"
  State = DeviceNodeStarted (0x30a) @ 2023 Dec 17 12:16:21.688
  Previous State = DeviceNodeEnumerateCompletion (0x30f) @ 2023 Dec 17 12:16:21.688

....

  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  Flags (0x4c0000f0)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
                      DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
                      DNF_NO_UPPER_CLASS_FILTERS
  CapabilityFlags (0x00002000)  WakeFromD3

The hardware identifiers of VEN_8086&DEV_A0F0 in the InstancePath indicate that this device is an Intel AX201 wireless adapter.

The first thing to check is the driver, and the version of Netwtw10.sys that you have loaded is 9 months old...

4: kd> lmvmnetwtw10
Browse full module list
start             end                 module name
fffff802`20330000 fffff802`20894000   Netwtw10 T (no symbols)         
    Loaded symbol image file: Netwtw10.sys
    Image path: Netwtw10.sys
 Image name: Netwtw10.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Aug  6 17:51:52 2023 (64CFB388)
    CheckSum:         004F843E
    ImageSize:        00564000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

I'd suggest looking for an update for that driver, either from the Lenovo website for your model of laptop or from Intel. If an updated driver doesn't stop the BSODs then you'll need to investigate the card. Laptop wireless cards are generally replaceable, although it's a bit fiddly, and they do occasionally fail.

thanks i updated the driver and rebooted
then a little later picked up the laptop again was rebooted



Event Viewer
exported Windows>System again
12:01pm and 12:09 has the errors
https://mega.nz/file/oxAwDDZT#zqM-nI1fTg9dSMdVytdkIP6r8YHNVn6e2t_SArMQfIU


new minidump file
https://mega.nz/file/UpglWAAI#LBoBCpQxeTjIVHoErxrBS-VKOkaOrTeEZV02Rmljxig

event viewer
Name resolution for the name client.wns.windows.com timed out after none of the configured DNS servers responded. Client PID 6440.


The driver entered RTD3.
All the connected devices will be removed from driver's internal state, so it is expected that DeviceDisconnected events will happen.


Driver exit RTD3.
All the connected devices will now cause DeviceConnected events.





The previous system shutdown at 11:54:24 AM on ‎5/‎12/‎2024 was unexpected.

(((I'm not seeing the shutdown in event viewer...***




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

12:09pm
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffc70c514c8360, 0xfffff8056a7010f8, 0xffffc70c539ed8e0). A dump was saved in: C:\Windows\Minidump\051224-18187-01.dmp. Report Id: 44c83df4-28d6-4620-a70b-8cd83bec28c8.


12:09pm
The operating system started at system time ‎2024‎-‎05‎-‎12T16:09:21.500000000Z.

The last shutdown's success status was false. The last boot's success status was true.

EFI time zone bias: 2047. Daylight flags: 0. Firmware time: ‎2024‎-‎05‎-‎12T12:09:20.000000000Z.

 

[ubuysa]

That recent dump is exactly the same as the others. It's a 0x9F and the device failing the power transition is the Intel AX201 wireless adapter. Since updating the driver hasn't helped one must now suspect the card. Intel laptop wireless cards do fail, I had one fail in a laptop of mine some years ago and I've seen several others fail since then.

Go into Device Manager, right-click on your AX201 and select Properties. In there click the Power Management tab and ensure that the 'Allow the computer to turn off this device' is NOT checked.

I also note that the version of netwtw10.sys that you're running is dated 22nd Feb 2024, but the latest driver available from the Lenovo website for your model is dated 17th Aug 2021. Where did the new version come from? If it was Windows Update then that should be fine. The thing with laptops is that drivers are often customised for the laptop to aid with interoperability and power-saving reasons. A generic AX201 driver from Intel will not contain those customisations and may cause problems. One thing you might try then, is to download the driver from the Lenovo website, then uninstall the current AX201 driver (uninstall the device in Device Manager and check the box to also uninstall the driver), and then install the Lenovo driver.

We know that the Lenovo driver will be fully compatible with your laptop, so if that BSODs with a 0x9F bugcheck code then it's almost certainly the AX201 card.

A new AX201 can be found online for around $20 and they're not that difficult to change.

 

[sanman98]

Last time with GPU problems, someone recommended install from Intel
and i got one or two of those software and drivers

if i recall correctly, i might have used the "newer" intel drivers for network and whatnot
it seems Windows update is working properly after reverting to Lenovo 2022 win11 driver
but i'll see if this fixes it

thanks

 

[sanman98]

That recent dump is exactly the same as the others. It's a 0x9F and the device failing the power transition is the Intel AX201 wireless adapter. Since updating the driver hasn't helped one must now suspect the card. Intel laptop wireless cards do fail, I had one fail in a laptop of mine some years ago and I've seen several others fail since then.

Go into Device Manager, right-click on your AX201 and select Properties. In there click the Power Management tab and ensure that the 'Allow the computer to turn off this device' is NOT checked.

I also note that the version of netwtw10.sys that you're running is dated 22nd Feb 2024, but the latest driver available from the Lenovo website for your model is dated 17th Aug 2021. Where did the new version come from? If it was Windows Update then that should be fine. The thing with laptops is that drivers are often customised for the laptop to aid with interoperability and power-saving reasons. A generic AX201 driver from Intel will not contain those customisations and may cause problems. One thing you might try then, is to download the driver from the Lenovo website, then uninstall the current AX201 driver (uninstall the device in Device Manager and check the box to also uninstall the driver), and then install the Lenovo driver.

We know that the Lenovo driver will be fully compatible with your laptop, so if that BSODs with a 0x9F bugcheck code then it's almost certainly the AX201 card.

A new AX201 can be found online for around $20 and they're not that difficult to change.

Still happening

https://mega.nz/folder/MpATmL4L#3RV4W2_yX4I8UcQpV_vOoA

so still seems to be the wifi adaptor, or no? should i view the minidump...i only filtered event viewer
minidump says caused by ntoskrnl.exe



Reset and/or resume count do not match expected values after hibernate/resume.

Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {a6bc66bc-6d1a-476a-a7aa-5e602015543e}, had event Fatal error: The miniport has failed a power transition to operational power

6062 - Lso was triggered

The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931

Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {a6bc66bc-6d1a-476a-a7aa-5e602015543e}, had event Fatal error: The miniport has failed a power transition to operational power

6062 - Lso was triggered

Name resolution for the name go.microsoft.com timed out after none of the configured DNS servers responded. Client PID 2644.



TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.


Power Manager has requested suppression of all input (INPUT_SUPPRESS_REQUEST=1)

Power Manager has requested suppression of all input (INPUT_SUPPRESS_REQUEST=1)


Name resolution for the name client.wns.windows.com timed out after none of the configured DNS servers responded. Client PID 6612.


The previous system shutdown at 12:30:56 PM on ‎5/‎31/‎2024 was unexpected.Dump file creation failed due to error during dump creation.


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

The driver \Driver\WUDFRd failed to load for the device PCI\VEN_8086&DEV_9A03&SUBSYS_380517AA&REV_01\3&11583659&0&20.


The driver \Driver\WudfRd failed to load for the device HID\Vid_8087&Pid_0AC2\6&1bba3d2d&0&0000.


The driver \Driver\WudfRd failed to load for the device HID\Vid_8087&Pid_0AC2\6&9008c88&0&0000.The driver \Driver\WUDFRd failed to load for the device {DD8E82AE-334B-49A2-AEAE-AEB0FD5C40DD}\DetectionVerification\5&ed8e0ec&0&0.The driver \Driver\WUDFRd failed to load for the device USB\VID_1C7A&PID_0576\16D807E3.

File System Filter 'Mrvdp' (Version 6.2, ‎2021‎-‎10‎-‎13T09:39:11.000000000Z) does not support bypass IO.
Supported features: 0x4.

The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931



The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

An error was detected.
Error message: Error code: 0x145, Sub error code: 0xA9



An error was detected.
Error message: Error code: 0x145, Sub error code: 0x1CA





Reset and/or resume count do not match expected values after hibernate/resume.



edit: today again i updated the download folder
happened right when i set the computer down and when i came back crashed again

 

[sanman98]

ok ordering ax201 card