Question I keep getting a black screen and reboot even after swapping out several components

Apr 29, 2025
5
0
10
Hello there.

I am at my wit's end trying to figure out what is causing my system to crash. It's been over a year and I was unable to find any solutions. All of this has started once I decided to upgrade my CPU so I don't know for sure if it's connected or not. I used to get a solid green screen and the PC would reboot, and no Minidump file was ever generated.

Now lately the screen turns to black instead of green, I hear the classic buzzing sound inside my headphones and before I know it it's rebooting again. On the software side I have done absolutely everything, until I decided to try out Linux just in case it was a Windows 10 issue but it crashed too. Now I am back at W10. I have already swapped out my SSD just in case, the motherboard and now the power supply. Still face these issues, I would say at least once every week depending on how much I use it. I only use this pc for gaming but it has crashed on desktop before.

Temperature seems fine, RAM is the oldest component I have but I have tested it many times with memtest and I had no errors. And unfortunatey I do not have any spare components and I refuse to buy anything else until I figure out the actual problem. At this point I can only point at the CPU or GPU but I do not know ow to figure it out. Took it to a few shops and none were able to figure out the issue either.

Are there any programs that can give me more information? For now I am running Burnintest. I tried others like Furmark and nothing has happened.
 
Last edited by a moderator:
Welcome to the forums, newcomer!

We ask users to include their system specs int heir thread's body as sig space specs can and will change over time. When that happens this thread and it's relevant suggestions are rendered moot to the end user in the same boat as you're in now.

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

You state upgrading/swapping parts out, at some point. Due to this, please mention a before and after of your specs. To add, did you reinstall the OS after your motherboard swap? Installing the OS in offline mode(and installing all drivers in an elevated command)?
 
Welcome to the forums, newcomer!

We ask users to include their system specs int heir thread's body as sig space specs can and will change over time. When that happens this thread and it's relevant suggestions are rendered moot to the end user in the same boat as you're in now.

When posting a thread of troubleshooting nature, it's customary to include your full system's specs. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

You state upgrading/swapping parts out, at some point. Due to this, please mention a before and after of your specs. To add, did you reinstall the OS after your motherboard swap? Installing the OS in offline mode(and installing all drivers in an elevated command)?
My specs are in my signature. I'll paste them here.
Asus Tuf b550 Wifi II (before Gigabyte x370 Gaming k7)
16GB TridentZ RAM
AMD Radeon 5600XT
Ryzen 5 5500 (before Ryzen 5 1600)
Cooler Master MWE Gold v2 650 (before EVGA 650W Gold, not sure which model)

Yes I reinstalled Windows 10 many times. But considering the same thing happened to me while gaming on Linux I discarded all software related issues.
 
My specs are in my signature. I'll paste them here.
Asus Tuf b550 Wifi II (before Gigabyte x370 Gaming k7)
16GB TridentZ RAM
AMD Radeon 5600XT
Ryzen 5 5500 (before Ryzen 5 1600)
Cooler Master MWE Gold v2 650 (before EVGA 650W Gold, not sure which model)

Yes I reinstalled Windows 10 many times. But considering the same thing happened to me while gaming on Linux I discarded all software related issues.

have you updated all chipset drivers and bios before switching to the 5500

to avoid any compatibility issues always download a install a fresh windows install after a motherboard change.
 
Look in Reliability History/Monitor and Event Viewer.

Any error codes, warnings, or even informational events being captured just before or at the time of the reboots?
All I managed to find out is that "RuntimeBroker.exe" was the one that caused the shutdown. Not sure if that's common or not.
And Reliability History did mark the system crash but doesn't offer much info. I also ran Burnintest a few days ago and the test itself marked some errors. I already sent the report via email to them, but from what I've seen it seemed like a driver issue which I already updated. So far no more crashes for now. I can upload the file if you want
 
Last edited:
There is still a lot that you can do and check. Take your time be methodical.

Learn more about "Runtime Broker" - start here:

https://www.howtogeek.com/268240/what-is-runtime-broker-and-why-is-it-running-on-my-pc/

If necessary look for and read other similar links.

= = = =

For the moment set aside all third party tools, tests, etc.. Disable at least.

= = = =

Regarding "And Reliability History did mark the system crash but doesn't offer much info"

What did it offer? You can click any given entry for more details. It is true that those details may or may not be helpful.

Also open Reliability History/Monitor and select Days view. Expand the window so all can be seen and easily read.

Take a screenshot of the full window and post the screenshot here via imgur (www.imgur.com > green "New post" icon).

If necessary, take a couple of screenshots showing different date ranges starting just before the problem(s) began.

Look in Update History for any failed or problem updates.

= = = =

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

Could be a buggy or corrupted file(s).

Run "dism" and "sfc /scannow"

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
 

TRENDING THREADS