F5F Stay Refreshed Hardware Desktop Computer appears black after a short period of use.

Computer appears black after a short period of use.

Computer appears black after a short period of use.

D
DryWay
Junior Member
Find
17
06-06-2023, 01:59 AM
#1
As mentioned in the title, I’m experiencing frequent black screens shortly after powering on my PC. My most likely explanation is a video driver issue, which I’ve attempted to resolve by reinstalling it and checking for other errors in various applications. Even when switching to safe mode, I still encounter these black screens, though they can persist for several hours.

I’m starting to lose my composure. Any assistance would be greatly appreciated!

Updated details:
Device name: DESKTOP-S2E323T
Processor: AMD Ryzen 7 5700X 8-Core Processor (3.40 GHz)
Installed RAM: 32,0 GB
Device ID: EF6426DC-6A51-421F-BA4B-2C9182750091
Product ID: 00331-10000-00001-AA685
System type: 64-bit OS, x64 architecture
Pen and touch: Supported
GPU: ASUS RTX 4070 TI 12GB
Power supply: 750W GIGABYTE UD750GM (18 months old, new to build)
Storage: crucial-p3-ssd-disk-1tb-m2-80mm-pci-e-30-x4-nvme-3d-nand-ct1000p3ssd8 73.5GB TO FULL / 874GB
HDD: 1TB Barracuda 200GB Free
Connected peripherals: Logitech G Pro Wireless, Razer BlackWidow v3
Network: Wired connection
Additional warning codes from Event Viewer:
-LSA package isn’t signed as expected. This may lead to unexpected behavior with Credential Guard.
PackageName references: msv1_0, sfapm, schannel, wdigest, cloudap, pku2u, tspkg, msv1_0, kerberos, negoexts
Security notes: Credential Guard and/or VBS Key Isolation are set up but the secure kernel isn’t running. Continuing without them.
-Detected unrecognized USB driver (Driver\USBPcap).
-Permission settings: Machine defaults don’t allow Local Activation for COM Server with CLSID {0868DC9B-D9A2-4F64-9362-133CEA201299} to NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from LocalHost via LRPC.
-Application-specific settings: Also block Local Activation for COM Server with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to DESKTOP-S2E323T\goraz SID (S-1-5-21-502743978-2129976413-751155887-1001}.
-Security permissions can be adjusted using the Component Services admin tool.
-The machine defaults don’t allow Local Activation for COM Server with CLSID {0868DC9B-D9A2-4F64-9362-133CEA201299} and APPID {0868DC9B-D9A2-4F64-9362-133CEA201299}.
This security setting can be changed via the Component Services tool.
Reply
Reply
D
DryWay
06-06-2023, 01:59 AM #1

As mentioned in the title, I’m experiencing frequent black screens shortly after powering on my PC. My most likely explanation is a video driver issue, which I’ve attempted to resolve by reinstalling it and checking for other errors in various applications. Even when switching to safe mode, I still encounter these black screens, though they can persist for several hours.

I’m starting to lose my composure. Any assistance would be greatly appreciated!

Updated details:
Device name: DESKTOP-S2E323T
Processor: AMD Ryzen 7 5700X 8-Core Processor (3.40 GHz)
Installed RAM: 32,0 GB
Device ID: EF6426DC-6A51-421F-BA4B-2C9182750091
Product ID: 00331-10000-00001-AA685
System type: 64-bit OS, x64 architecture
Pen and touch: Supported
GPU: ASUS RTX 4070 TI 12GB
Power supply: 750W GIGABYTE UD750GM (18 months old, new to build)
Storage: crucial-p3-ssd-disk-1tb-m2-80mm-pci-e-30-x4-nvme-3d-nand-ct1000p3ssd8 73.5GB TO FULL / 874GB
HDD: 1TB Barracuda 200GB Free
Connected peripherals: Logitech G Pro Wireless, Razer BlackWidow v3
Network: Wired connection
Additional warning codes from Event Viewer:
-LSA package isn’t signed as expected. This may lead to unexpected behavior with Credential Guard.
PackageName references: msv1_0, sfapm, schannel, wdigest, cloudap, pku2u, tspkg, msv1_0, kerberos, negoexts
Security notes: Credential Guard and/or VBS Key Isolation are set up but the secure kernel isn’t running. Continuing without them.
-Detected unrecognized USB driver (Driver\USBPcap).
-Permission settings: Machine defaults don’t allow Local Activation for COM Server with CLSID {0868DC9B-D9A2-4F64-9362-133CEA201299} to NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from LocalHost via LRPC.
-Application-specific settings: Also block Local Activation for COM Server with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to DESKTOP-S2E323T\goraz SID (S-1-5-21-502743978-2129976413-751155887-1001}.
-Security permissions can be adjusted using the Component Services admin tool.
-The machine defaults don’t allow Local Activation for COM Server with CLSID {0868DC9B-D9A2-4F64-9362-133CEA201299} and APPID {0868DC9B-D9A2-4F64-9362-133CEA201299}.
This security setting can be changed via the Component Services tool.

Reply
Reply
M
MonochromeLG
Member
Find
74
06-06-2023, 02:24 AM
#2
Update your update with complete hardware details and operating system specifics. Provide PSU specifications, model, wattage, age, and condition of the original build versus the new setup. List all connected peripherals. Indicate whether the network is wired or wireless. Report any error codes found in the Reliability History, Monitor, or Event Viewer.
Reply
Reply
M
MonochromeLG
06-06-2023, 02:24 AM #2

Update your update with complete hardware details and operating system specifics. Provide PSU specifications, model, wattage, age, and condition of the original build versus the new setup. List all connected peripherals. Indicate whether the network is wired or wireless. Report any error codes found in the Reliability History, Monitor, or Event Viewer.

Reply
Reply