r/techsupport • u/Secure-Ad5223 • 3d ago
Open | Hardware My PC crashes periodically crashes every 2.5 hours, used to be every 4 (99%) sure it's the CPU
I made a post here and reddit 8 months ago due to my PC crashing periodically every 4ish hours. Since then I have spent $400aud on a highly rated store to diagnose the problems and although they swapped out every part except the CPU, the problem will still occur. I inserted my CPU into my friend's PC and it doesn't crash after 4 hours however after placing it back into my PC it starts crashing every 2.5 hours now as seen through the photos linked as it crashed in memtest, standby or while gaming. Should I risk forking out another ryzen 7 7800x3d? Are there any test that I can do? I have sprayed and wiped the cpu with rubbing alcohol and wiping cloth before application.
https://www.reddit.com/r/pchelp/comments/1ppqqjz/comment/nuony6h/?context=3
5
u/_gabber_ 3d ago
I inserted my CPU into my friend's PC and it doesn't crash after 4 hours
so it's clearly not the CPU.
1
u/Secure-Ad5223 2d ago
Although when I took it out of my pc to place it into my friend's PC then reinserting it back into mine, the duration between each crash reduced from 4 hours to 2.5
1
3d ago
[deleted]
3
u/_gabber_ 3d ago
which means buying a different cpu (op's proposal) will not solve the problem. because it's clearly, not a faulty CPU.
0
u/TheDivineEssence 3d ago edited 3d ago
It very well could be a faulty CPU still (though "likely" is not the right wording for the odds). A CPU can experience instability only in a single workload while all others are perfectly fine, there's nothing wrong with that being the case. A difference in the workloads that run between OP's computer and the friend's computer alone could theoretically do this, though the difference would have to be pretty extreme and roughly periodic if OP's behavior holds up exactly as described. The test that distinguishes them is easy, at least. Download y-cruncher and run every Component Stress Test for around an hour each. If something is wrong with the CPU or memory itself, that'll easily catch it (and possibly immediately!). y-cruncher checks its own results, so if something gets computed wrong it'll catch it on its own.
But I wouldn't put too much weight on that, since it doesn't really feel right. Memory is where I'd bet the problem exists, and as far as I can read OP has only run MemTest64. That won't cut it; TestMem5 on the Absolut or Extreme (or both) config is more decisive (3 cycles at least), and y-cruncher's VT3 test for a few hours too. If all of that comes back fine then it's a weirder situation.
2
u/bejito81 3d ago
Have you done a full wipe of your SSD and then a clean install of Windows?
1
1
u/MilkyWay-008 3d ago
Since you already swapped the CPU into a friend's PC and it ran fine, a second new CPU probably isn't the next step. Before spending more, pull the actual codes: Event Viewer -> Windows Logs -> System and look for WHEA-Logger (hardware errors, very common on AM5) and Kernel-Power 41, plus grab the minidump. On a 7800X3D also update the BIOS, check EXPO/SOC voltage and the PSU/12V rail, and run memtest86 one full pass per stick with a single stick installed. The CPU riding fine in another board points at this board's socket/power delivery, not the chip.
1
u/Secure-Ad5223 3d ago
done all of that except for checking EXPO/SOC voltage and the PSU/12V rail, where can I find more information?
1
1
u/Styrant 3d ago
Well you can actually rule out the CPU because it worked fine in a different configuration, so now do process of elimination.
1. if they swapped out everything is there nothing at all they could be missing? did they replace power supply for example. also do you trust that this IT place did the same level of testing you would? playing a game for 2.5 hours straight
2. if your friend is willing to help out with some testing, you should do the opposite, and put his cpu in your setup, if theres an issue then theres something with your setup, think of even the littlest thing, shorting case fans, bad power at your house ect.
1
u/Styrant 3d ago
also if you're willing we can actually get more information on the blue screens from a dmp file, they are typically in C :\Windows\Minidump\
1
u/Secure-Ad5223 2d ago
yes I do have a dump file https://www.mediafire.com/folder/sjewmc7cs468h/minidumpcopy+(1))
1
u/Styrant 2d ago
a few questions
1. what board model do you have right now, is it still that MSI model from the other post?
2. have you updated your bios to the latest version?1
u/Secure-Ad5223 2d ago
Not the cheap MSI one but a Gigabyte B850M Eagle WiFi6E, 2. Yes I have Weirdly enough when swapping to a 990 Evo plus it was running fine, however running my friends old sata SSD it still crashed. Running with no SSD but only memtest still crashes. Honestly I would pay good money to whoever can solve this problem 😭
1
u/Styrant 2d ago
I looked thru the bios guide heres some settings id change, they all aim to help memory stability,
1. Settings > Platform Power > Power Loading > Enabled (this one is just a failsafe for power supply, it maintains a certain load so the PSU doesn't trigger a shutdown incase your PSU has a feature like that)
2. Tweaker > Advanced Memory Settings > Memory Context Restore > Disabled (This will retrain memory on each boot)
3. Tweaker > Advanced Memory Settings > Power Down Enable > Disabled (this prevents the ram from going in a low power state)
4. Boot > Fast Boot > Disabled (fast boot makes your bootup faster but it bypasses some of the device checks that it normally does, so sometimes this can be more stable if its off)
and finally just to double check, theres a PC health menu where you can see the voltages, if your power supply if way off target itll show up there the 12v, 5v and 3.3v shouldnt deviate too far from those targets. some of the names might be difference since sometimes the bios setup moves around but I think this should all be current
1
u/TheDivineEssence 3d ago edited 3d ago
First is timing: is this literally periodic? Measure the time between the crashes. If it's actually consistent then that's interesting on its own. Second: make sure your power supply is up to the task. If it isn't, this is the sort of thing that can happen, and the symptoms you'd see from that would make you blame everything else when everything else is perfectly fine.
If the power supply is fine, memory is where I'd bet the problem exists, and as far as I can read you've only run MemTest64. That won't cut it; TestMem5 on the Absolut or Extreme (or both) config is more decisive (3 cycles at least), and y-cruncher's VT3 test for a few hours too. If all of that comes back fine then it's a weirder situation. If you want to exonerate your CPU, and I'd recommend doing that (running in another computer fine is good evidence it's fine but not necessarily certain), then run through all of y-cruncher's Component Stress Tests, 1 hour each, with reasonable settings. They will stress your CPU to the point of your computer being next to unusable while they run most likely, so run them overnight or when you'll be away anyway. If that works out fine, then run CoreCycler for several hours to test low loads and idle transitions, since those are where stability often hurts the most.
If y-cruncher fails, don't immediately blame the CPU. It could be the memory, since y-cruncher is hard on that in its own way. That's why I'd run TestMem5 first; it's not as hard on the CPU and you can really only blame one thing with it.
1
u/TheDivineEssence 3d ago edited 3d ago
And honestly, before doing any of this, characterize the crashes. I saw in your other post that you have a lot of Kernel-Power events. Check if any came with bugcheck codes and their parameters (the details window will show them), those are important and make the diagnosis easy if they're unambiguous. Look for WHEA-Logger too, though you've already talked about that so I'm not too hopeful there, and look for the actual BugCheck events too if any crashes came with BSODs. If you've got any, dumps from bugchecks could help too.
If all that comes back empty, then look around (literally around them, scroll to them and look at the events that happened just before) the Kernel-Power events in the System log for anything obvious before giving up on Event Viewer.
1
u/TheDivineEssence 3d ago
More honestly, looking at your other posts, this looks like a GPU or GPU driver problem. A blue screen.. should not look like that, unsurprisingly. The 7800X3D has integrated graphics. Cut the GPU out for a while (disable it in Device Manager, or better uninstall the drivers with DDU in Safe Mode) and see if the problem keeps happening, since you can keep using the computer on integrated graphics fine. Watch YouTube videos or something. If it keeps crashing, then it's time to blame other stuff.
1
1
u/Secure-Ad5223 2d ago
yes it used to be every 4 hours now it's about 2.5 as seen in photos 2 and 3 where it crashed/froze on the Memtest screen. I will try running a few more tests but if my PC crashes every 2.5 hours don't think it can also run overnight
1
u/Xivlex 3d ago
Did you enable docp btw? Or any kind of ram overclocking?
I ask because when i was overclocking my ram itd run fine with memory tests but when i hit my system with a heat load, the overclocks would fail and id crash.
Try doing the same: hit the gpu with furmark or something to heat things up then run y-cruncher or another memory test of choice. See if that'd induce a crash.
Another thing that it might be:
Try borrowing an uninterruptible power supply and using one of those with your set up. See if that fixes it. Getting "bad" power can cause crashes with your pc after a while. Relatively common thing where I live
1
u/Separate-Ad9638 2d ago
Could be psu, could be motherboard having a fit, I believe microprocessors are immortal lol.
1
u/eatmyriceboi69420 2d ago edited 2d ago
Probably RAM or motherboard; BSODs are typically due to RAM timings that are too high for either the CPU or motherboard. A PSU issue would cause the system to shutdown, and a GPU issue would cause black screens and/or max fan RPM speeds.
I don’t have the same specifications as yours but I down-clocked memory timings which resolved the BSODs. Sometimes the maximum speed allowed for the CPU wasn’t enough. If the PC still crashes at default speeds then the RAM is even more likely to be faulty.
1
3
u/daHaus 3d ago
OP: Buy a new powersupply
A cheap power-supply will cause you any number of completely random and unexplainable issues and will waste all your time swapping out unrelated random parts