Jump to content

Hey all, about 5-6 months ago my old PSU stopped working and I replaced it with a new one with identical wattage and all, about a month afterwards, my PC has been black screening and restarting whenever I run particular games like Overwatch 2, Darktide, Total Warhammer 3, Doom Eternal, Battlefield 2042, etc.

I swear I have tried everything I can think of at this point, I've reinstalled my GPU drivers, checked my cable and part connections, swapped out HDMI and DP cables, reinstalled the above games, reset my RAM speeds to default, added new thermal paste to my CPU, de-dusted my pc, reset my monitor settings, disabled hardware acceleration on apps like Discord and Spotify, put my CPU and GPU on full strain to see if they were struggling/faulty (they weren't) and then I tried connecting my monitors one at a time.

If anyone has any idea of what could be going wrong on my PC, it'd be greatly appreciated.

My build:
NVIDIA GeForce RTX 3060Ti (Driver ver. 528.49)
AMD Ryzen 5 3600X (6-Core)
2x8GB DDR4 RAM (3200Mhz)
Corsair RM650 PSU
 

Monitor 1: 3440x1440 (75Hz)
Monitor 2: 1680x1050 (60hz)

 


 

Link to comment
https://linustechtips.com/topic/1488964-pc-blackscreening-then-restarting/
Share on other sites

Link to post
Share on other sites

1 hour ago, Gokul_P said:

Check event viewer and What is the last Critical event

 

Update The Bios

Update Chipset drivers

Use DDU to remove your driver and reinstall it 

 

I received 80 instances of the same error that occurred while playing OW2: The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

I assume this error has something to do with the graphics driver?

Link to post
Share on other sites

22 minutes ago, gluglug said:

I received 80 instances of the same error that occurred while playing OW2: The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

I assume this error has something to do with the graphics driver?

This looks like a Gpu driver issue USE DDU and wipe the driver and reinstall it 

Link to post
Share on other sites

Okay, I wiped the driver and did a clean re-install, still getting a black screen then crash.

Very few errors showing in event viewer now, only potentially relevant error message I can find is a warning: The driver \Driver\WudfRd failed to load for the device ROOT\SYSTEM\0006.

Link to post
Share on other sites

Just played some Risk of Rain 2, and I've noticed that every time I black screen I get a series of information events:

- The operating system started at system time ‎2023‎-‎02‎-‎18T12:50:58.500000000Z.

- Virtualization-based security (policies: 0) is disabled.
- There are 0x1 boot options on this system.
- The bootmgr spent 0 ms waiting for user input.

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

- EFI time zone bias: 2047. Daylight flags: 0

- The boot menu policy was 0x1.

- The boot type was 0x0.

- The firmware reported boot metrics.

- The leap second configuration has been updated.
Reason: Leap second data initialized from registry during boot
Leap seconds enabled: true
New leap second count: 0
Old leap second count: 0

 

Then followed by an error - The previous system shutdown at 11:14:12 PM on ‎2/‎18/‎2023 was unexpected.

 

Then followed by more information events:
- Microsoft (R) Windows (R) 10.00. 19045  Multiprocessor Free.

- The Event log service was started.

- The system uptime is 9 seconds.

- The iommu fault reporting has been initialized.

- File System Filter 'FileInfo' (10.0, ‎2062‎-‎12‎-‎23T16:21:06.000000000Z) has successfully loaded and registered with Filter Manager.

- File System Filter 'Wof' (10.0, ‎2023‎-‎04‎-‎23T13:17:53.000000000Z) has successfully loaded and registered with Filter Manager.

- File System Filter 'WdFilter' (10.0, ‎2101‎-‎02‎-‎28T22:30:25.000000000Z) has successfully loaded and registered with Filter Manager.

- Volume C: (\Device\HarddiskVolume7) is healthy.  No action is needed.

- File System Filter 'FileCrypt' (10.0, ‎2002‎-‎03‎-‎01T22:12:42.000000000Z) has successfully loaded and registered with Filter Manager.

- File System Filter 'npsvctrig' (10.0, ‎2025‎-‎01‎-‎06T13:41:12.000000000Z) has successfully loaded and registered with Filter Manager.

 

I'm not sure if any of this has any relevance to my situation, though I do want to reiterate that this series of events is almost always present in the event log at the time of a crash.

 

 

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×