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

[sleepaftertoyle]

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.

 

[Ralston18]

Not sure but it almost appears that the dump file was being put into the Page File space. May or may not be viable and if the dump file was larger than available space that would indeed be a problem.

As for swapping and testing RAM: check the Motherboard's User Guide/Manual first.

Ensure that you are using supported RAM and supported RAM configurations. Including BIOS.

Also be aware that some Motherboards require that the first physically installed RAM be placed in a specific slot. Typically DIMM_A2.

Sometime that requirement is not clearly presented. Read all fine print and check any diagrams carefully.

 

[sleepaftertoyle]

Not sure but it almost appears that the dump file was being put into the Page File space. May or may not be viable and if the dump file was larger than available space that would indeed be a problem.

As for swapping and testing RAM: check the Motherboard's User Guide/Manual first.

Ensure that you are using supported RAM and supported RAM configurations. Including BIOS.

Also be aware that some Motherboards require that the first physically installed RAM be placed in a specific slot. Typically DIMM_A2.

Sometime that requirement is not clearly presented. Read all fine print and check any diagrams carefully.

Right, so any way I can make the page file space bigger? Or would it work if I simply chose a smaller type of memory dump? In that case I'm not sure it would give me enough info.
I already tested both sticks individually. No errors. And yes both were in the correct slots. I realized both were running at stock 2133Mz speeds (the option in the BIOS was set to Auto) I was able to change it to 3200MHz without enabling anything else so I did. Still crashed though.
As for compatibility this is an older model of RAM as I said, so it didn't show up on the motherboard list but everywhere I looked it seemed there shouldn't be a problem.

 

[sleepaftertoyle]

Not sure but it almost appears that the dump file was being put into the Page File space. May or may not be viable and if the dump file was larger than available space that would indeed be a problem.

As for swapping and testing RAM: check the Motherboard's User Guide/Manual first.

Ensure that you are using supported RAM and supported RAM configurations. Including BIOS.

Also be aware that some Motherboards require that the first physically installed RAM be placed in a specific slot. Typically DIMM_A2.

Sometime that requirement is not clearly presented. Read all fine print and check any diagrams carefully.

Okay, found the option to change page file size I believe. Decided to run BurninTest for the millionth time, crashed within 2 minutes. No dump file again. Decided to change the directory back to the default one (System Root- Memory.dmp) and deleted both registry entries I added so now it's back to "stock". No volmgr error in the Event Viewer though.

https://imgur.com/a/gW6jvmH

View: https://imgur.com/a/gW6jvmH

 

[Ralston18]

Just allow Windows to manage paging file size on the C: drive.

 

[sleepaftertoyle]

Just allow Windows to manage paging file size on the C: drive.

Cool, so I check the "Automatically manage paging file size for all drives"? It was unchecked before so hopefully this time...
Managed to make it crash twice now with Burnintest. I noticed it usually reboots before the 5 minute mark. If it goes past that the test will complete like normal. I guess I'll keep running it

 

[Ralston18]

What is the reason for using "Burnintest".

Or any other stress tests of any sort for that matter.

Real stress tests, soon or later, destroy things.

Others, maybe just want to scare you into buying something.

Where are we here?

 

[sleepaftertoyle]

What is the reason for using "Burnintest".

Or any other stress tests of any sort for that matter.

Real stress tests, soon or later, destroy things.

Others, maybe just want to scare you into buying something.

Where are we here?

It's the most reliable way I found to reproduce the crash. Otherwise it could take days before it happens again. I need the crash dump because I cannot afford to buy another component hoping it fixes it. I do have the HWinfo file which was logging things in the background until it crashed. But I don't know how to read it or if it even says anything at all

 

[Ralston18]

Let Windows manage the Pagefile.

No more "burnintest" or other such tests to force the problem.

Use HWinfo to just observe - change nothing so that if something does change you know there is some other reason that that happened.

Run "dism" and "sfc /scannow" to find and fix any corrupted or buggy files.

Check Update History as well for problem or failed updates.

Hopefully the crashes will again stop.

Then, when there is a crash, you can look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or even informational events being logged just before or at the time of the crash.

Check both each day to become familar with each tool and to get a sense of what may be going on within your build. Somethings are perfectly normal. Even errors that Windows detects and simply handles....

Key is to simplify as much as possible to narrow down possible suspects.

Then, be able to readily see what happened if/when there is another crash.

 

[sleepaftertoyle]

Let Windows manage the Pagefile.

No more "burnintest" or other such tests to force the problem.

Use HWinfo to just observe - change nothing so that if something does change you know there is some other reason that that happened.

Run "dism" and "sfc /scannow" to find and fix any corrupted or buggy files.

Check Update History as well for problem or failed updates.

Hopefully the crashes will again stop.

Then, when there is a crash, you can look in Reliability History/Monitor and Event Viewer for any error codes, warnings, or even informational events being logged just before or at the time of the crash.

Check both each day to become familar with each tool and to get a sense of what may be going on within your build. Somethings are perfectly normal. Even errors that Windows detects and simply handles....

Key is to simplify as much as possible to narrow down possible suspects.

Then, be able to readily see what happened if/when there is another crash.

Ran both DISM and scannow. No errors were detected this time. I remember months ago scannow did detect some errors and fixed them, but that didn't help. It was a brand new install and I ended up reinstalling Windows yet again. Event viewer seems to give even less info that before, and there are no failed updates.
What do I look for in HWinfo? I don't understand anything. I have a few log files that were running while the system crashed. Is there a way I can upload them here? Not sure if they logged anything.

 

[Ralston18]

Log files: source, names, extension? HWinfo?

 

[sleepaftertoyle]

Log files: source, names, extension? HWinfo?

It's a CSV file. It logged all the 'sensors' info in HWInfo, up until when it crashed. Again, not sure if it even recorded anything. What's the best site to upload it? I don't believe I can do that directly on this site.

 

[Ralston18]

Try imgur.

https://imgur.com/hc

View: https://help.imgur.com/hc/en-us/articles/26511665959579-What-files-can-I-upload-Is-there-a-size-limit


Generally used for images but try the file.

There may be other comments and suggestions.

 

[sleepaftertoyle]

Try imgur.

https://imgur.com/hc

View: https://help.imgur.com/hc/en-us/articles/26511665959579-What-files-can-I-upload-Is-there-a-size-limit


Generally used for images but try the file.

There may be other comments and suggestions.

Does this link work? https://limewire.com/d/pfNnD#Ng1mB36QYi

 

[Ralston18]

Yes, I can view the .CSV file contents.

However, as a matter of practice I do not download files.

Do you have a spreadsheet app and know how to import the .csv (comma separated values) file into the spreadsheet?

If you put the data into a spreadsheet with readily readible columns you should be able to get a better sense of what is being shown.

Look at the memory related columns: values and %'s.

 

[sleepaftertoyle]

Yes, I can view the .CSV file contents.

However, as a matter of practice I do not download files.

Do you have a spreadsheet app and know how to import the .csv (comma separated values) file into the spreadsheet?

If you put the data into a spreadsheet with readily readible columns you should be able to get a better sense of what is being shown.

Look at the memory related columns: values and %'s.

These are a few columns I found with certain difference in numbers. Again, no clue what any of this means or if it's normal or not. Let me know if you need other specific values.

https://imgur.com/a/E1tgHwI

View: https://imgur.com/a/E1tgHwI

 

[Ralston18]

Nicely done.

The changes that you noted with blue boxes may be related to some power loss(es) to the CPU.

Because you have switched CPUs and made other changes (provided that I have correctly followed the history thus far) I think the PSU may be suspect.

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

(It appears that you may have swapped PSUs - if so, provide specs for both.)

Disk drive(s): make, model, capacity, how full?

List of all connected peripherals.

= = = =

Also FYI:

VID voltage

Read the link and search for other similar links.

Purpose simply to learn more and perhaps find other explanations and information that will help you recognize other relevant symptoms.

I am not a member of the overclocking community (full disclosure) but there are members here that very much can intrepret the results from the spreadsheet.

Or provide further suggestions and ideas.

 

[sleepaftertoyle]

Nicely done.

The changes that you noted with blue boxes may be related to some power loss(es) to the CPU.

Because you have switched CPUs and made other changes (provided that I have correctly followed the history thus far) I think the PSU may be suspect.

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

(It appears that you may have swapped PSUs - if so, provide specs for both.)

Disk drive(s): make, model, capacity, how full?

List of all connected peripherals.

= = = =

Also FYI:

VID voltage

Read the link and search for other similar links.

Purpose simply to learn more and perhaps find other explanations and information that will help you recognize other relevant symptoms.

I am not a member of the overclocking community (full disclosure) but there are members here that very much can intrepret the results from the spreadsheet.

Or provide further suggestions and ideas.

These are my current specs: Asus Tuf b550 Wifi II (used to be Gigabyte x370 Gaming k7)
16GB G SKill TridentZ RAM
AMD Radeon 5600XT
Ryzen 5 5500 (used to be Ryzen 5 1600)
Cooler Master MWE Gold v2 650w (used to be an EVGA Gold rated, not sure which model but it was also 650W)
Both drives are Kingston, one is a SATA one and the other is an NVME. Neither is running out of space. Both are 500gb. They are about 4 months old I believe. I used to have a Crucial mx500 and I took that one out. The PSU I swapped about a month or so ago. Motherboard maybe a year ago but I barely used the PC because of the constant crashes. As for peripherals I have nothing out of the ordinary. One 1080p, 144Hz monitor, one Logitech mouse, a generic gaming keyboard and a pair of Audio Technica m50x headphones plugged directly to the back, no DAC. Both the monitor and the PC are plugged into a UPS which hasn't really been used much and is always fully unplugged once the PC is off. I could try plugging everything directly to the wall? It hasn't beeped or anything indicating an error but maybe I'll try it.
So what else could cause the CPU to lose some power beside it possibly being faulty? This happened with two motherboards, new drives and two different power supplies.

EDIT: Also curious about the CPU possibly having some physical damage? I did not trust myself to install it so I took it to a shop so they could do it. May be worth taking it out to inspect it, idk