I keep having trouble with my computer going black and restarting, no matter how many parts I swap around to fix it.
I keep having trouble with my computer going black and restarting, no matter how many parts I swap around to fix it.
Hello there. I am at my limits trying to find why my computer is crashing. It's been over a year and I didn't know how to fix it before. All of this started after I decided to upgrade my CPU, but I don't know if that is the real cause or not. Used to get a solid green screen and it would reboot with no Minidump file ever made. Now lately the screen goes black instead of green, I hear that buzzing sound in my headphones, and before I know it it restarts again. On the software side I have tried everything except try Linux just in case it was a Windows 10 problem but it crashed too. Now back at W10. I already swapped out my SSD so if that's bad, maybe the motherboard is also bad. And now the power supply. Still face these issues, I say at least once every week depending on how much I use it. I only use this pc for gaming but it has crashed before on a desktop. Temperature seems fine, RAM is the oldest component I have but I tested it many times with memtest and no errors happened. And unfortunately I do not have any spare parts and I refuse to buy anything else until I figure out the real problem. At this point I can only point at the CPU or GPU but I don't know how to find out which one is bad. Took it to a few shops and none were able to fix the issue either. Are there any programs that can give me more info? For now I am running Burnintest. I tried others like Furmark and nothing has happened yet.
Welcome to our forums! New users are asked to put their computer details in the thread so that other people know what parts they have. If those parts change later, old advice won't work anymore for anyone like you right now. When someone posts about fixing a problem, it's normal to share all of your system specs. Please write them out like this: CPU, cooler, motherboard, RAM, hard drive or SSD, graphics card, power supply, case, operating system, and monitor. Also tell how old the power supply is besides its brand and model number. Tell us about the BIOS version on your board at the exact moment you are using it. You might be swapping parts out sometime in the future. Because of that, please say what your specs were like before and after. Did you reset or reinstall the operating system after changing your motherboard? Did you install all drivers while running the computer with admin privileges instead of just regular user access?
My specs are in my signature, but I'm going to copy them right here. I have an Asus Tuf b550 Wifi II motherboard (which came before a Gigabyte x370). It has 16GB of RAM made by TridentZ. The graphics card is the Radeon 5600XT (before upgrading to a Ryzen 5 1600). For cooling, I used a Cooler Master MWE Gold v2 with 650 watts. Originally, I had an EVGA power supply, but I'm not sure which model it was. Yes, I have fixed Windows 10 many times on my computer. However, because the same thing happened to me when I played games on Linux, I stopped trying to fix all those software problems.
Have you changed all the driver and BIOS files before putting on your new 5500? That way, everything will work well together. Always get the newest drivers for chips and BIOS. Also, make sure to reset Windows every time you swap out a motherboard.
Yeah, I fixed my computer by reinstalling Windows and updating the BIOS many times, even installing all those chipsets. Still got crashes when using Linux too.
The only thing I managed to find is that "RuntimeBroker.exe" was the cause of the shutdown. Not sure if this happens often or not. Reliability History said something about a crash, but it gave no details. I also ran Burnintest a few days ago and the test showed some errors. I already sent the report via email to them, but from what I've seen, it looked like a driver issue which I have already fixed. So far there are no more crashes. I can upload the file if you want
You don't have to send me that file. I guess the new update might have solved it. Just watch the log messages for a couple of days.