Question Waking up from sleep/shut down sometimes results in a black screen ?

[Draggs]

Waking up from sleep/shut down results in a black screen until I force shut down the PC by holding the power button, which I don't think is a good thing to do regularly. But regularly doesn't even cut it. I can't even recreate the problem. Sometimes when I shutdown/sleep it would work just fine, but then at other times the screen just wouldn't show anything. Fan's still running, RGB lights are on.

Tried to troubleshoot it by myself by doing:

• Updating Windows
• Repair Windows
• Resolve Start Up problems (which doesn't result in anything)
• Turned Secure Boot On/Off
• Turned Fast Boot On/Off
• Turned Fast Startup Off
• Changed to CSM/UEFI
• Swapped cables & ports (HDMI & DP)
• Swapped monitor
• Ctrl + Shift + Win + B
• Allow keyboard and mouse to wake up PC on devmgmt.msc
• Unchecked allow Intel Management Engine to turn off computer
• Updating drivers (most notably Intel Chipset Driver, Realtek HD Universal Driver Audio, Realtek PCI-E Ethernet Drivers, & Intel Management Engine Driver)
• Set Allow Wake up Timers to both Enabled/Disabled
• Set Link State Power Management to On/Off
• Set Turn Off Hard Disk to Never
• Reinstall Display Driver (using DDU)
• "powercfg -h off" in cmd
  and probably more that I missed because I did try a lot of things.

Specs
Motherboard: MSI H310I PRO (bios 7B80v1A)
CPU: i5-9400F
CPU cooler: stock
GPU: RTX 2080
RAM: Klevv 2 x 8GB DDR4 2666
SSD/HDD: Ballista ADV 2280 512GB / Seagate Barracuda 1TB
PSU: Seasonic Focus Plus Gold 550w (5yo)
Chassis: Cougar QBX
OS: Win 11
Monitor: Xiaomi A27i

 

[Ralston18]

Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some related error code, warning, or informational event that precedes the black screens.

Overall, my first suspect would be that 5 year old ("5yo" ? ) PSU.

 

[Draggs]

Look in Reliability History/Monitor and Event Viewer.

Either one or both tools may be capturing some related error code, warning, or informational event that precedes the black screens.

Overall, my first suspect would be that 5 year old ("5yo" ? ) PSU.

I saw both, but I don't know where to start tbh. There's this:

Source
Windows

Summary
Hardware error

Date
‎1/‎3/‎2025 7:46 PM

Status
Not reported

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 141
Parameter 1: ffffcd07c6144010
Parameter 2: fffff802541916a0
Parameter 3: 0
Parameter 4: ffffcd07b2f0c080
OS version: 10_0_26100
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26100.2.0.0.256.48
Locale ID: 1033

Files that help describe the problem
WATCHDOG-20250103-1946.dmp
sysdata.xml
WERInternalMetadata.xml
memory.csv
sysinfo.txt
WERInternalRequest.xml

On Reliability History, but I personally can't really make anything out of this. Anything I should look out for?

 

[Ralston18]

Reliability History/Monitor:

What to look for are yellow and red icons wherever they appear. Note the "failures" groups by line at the right edge of the table.

Open the tool and expand the window so all can be seen. Chose "View by" as Days and then select a date that has multiple error codes and warnings. Take a a full screen shot and post the screenshot here via imgur (www.imgur.com).

Then change "View by" to Weeks, take and post that screen shot.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

As in Reliability History/Monitor you are looking for error codes and warnings.

In both tools, clicking any given entry will provide more details about the entry. The details may or may not be helpful. However, at least make note of any error codes.

Overall, varying errors and increasing numbers of errors over time are a sign of a faltering/failing PSU.

Take you time looking and reading. Watch for patterns: e.g., If "X "happens then "Y" follows.

Post accordingly:

= = = =

Also - could be related to some buggy or corrupted files.

Reading back I did not note that you tried "dism" and "sfc /scannow" unless that was part of " a lot of things".

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

 

[johnbl]

enable verbose logging:
https://learn.microsoft.com/en-us/t...startup-shutdown-logon-logoff-status-messages

to find out what is going on during the shutdown. for example shutdown will refuse to finish if data will be lost. (ie flush disk command does not complete)
also, media players are allowed to block shutdown so you could have something like a xbox on the same network blocking your shutdown.
(disconnect network before shutdown for a test)

also run crystaldiskinfo.exe to check the health of your drives ( and see if the drive needs a firmware update)

I have seen cases where a bug in a network driver or router causes packet corruption that leads to a blocked shutdown. (update driver and firmware of router)