Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
It started these random shutdowns in 2012 and i lived with it until January 1st 2015, which it has never started again. I tried even more than what you did above, even some ludicrous things but they didn't work for 3 years, until it finally gave up altogether.
It is the aging PSU brother. In my case, i didn't just buy a new PSU for my 12 year old Pentium 4 machine but i bought an all new one as it would have been pointless to run a P4 Machine in 2015.
If those shutdowns are totally random, like it can work during heated gaming sessions but can shutdown while it is idle, on desktop, with no browser nor game nor heavy software is at work (some other time browsing the web, some other time in game menu... etc), then it is PSU.
Anyways, I had an issue where the Windows Update changed the "Turn HDD Off" after 5 minutes issue which would randomly shut the PC down when watching movies, in idle, pausing a game, or listening to music.
If you can get it to work, run SFC Scan and DISM CheckHealth.
If you updated the BIOS, I hope you saved the revision. Re-flash the BIOS. And stay clear of any Beta BIOS revisions.
I was really hoping it would've been the missing memory
The PSU that's in their PC is like 5+ years old, the Corsair TX550M. And you would be correct that the shutdowns/resets are totally random, while the PC is idle or doing non-demanding processes.
Will do! While at it, I have another PSU to try and see if the PC doesn't reset.
The OS is installed on the SSD, while there are two extra HDDs I set in RAID 0. So I can try some of them scanning options and see if anything unusual comes up, but I can't re-flash the BIOS; too late for that. But I made sure I wasn't updating to a beta version.
idk just possibility
I'm not sure how much or if it leaked at all. There was residue around and within the slot. And don't worry, they brought the PC back inside
Sounds plausible. It was pretty hefty inside there when I opened the case.
I'll take a closer inspection at the rest of the PCB.
may need new pc
disable auto reboot on bsod
many times it reboots before showing the bsod
In this case, I can access the BIOS quickly. Nothing had spilled into the PC, though.
You also didn't provide the hardware itself (CPU-Z validation link would be good but you'd need access to the PC for that).
Your first course of action should be to check event viewer. If it's a BSOD, it will tell you. And if it is a BSOD, this is where you'll get any information that may help you troubleshoot it. If it's not a BSOD, you've narrowed that out and know you're actually dealing with a true "random restart" which is nine times out of ten an electrical issue, if not a thermal one (random number, and it's probably higher than this if anything).
I'm not going to question why the PC was outside, but did it stay out there? If so, again... won't even question why, but knowing both that, and that you describe the battery as having leaked and it being "hefty" inside (this means what?), then I'd honestly be starting with a new PSU and motherboard and seeing what else can be salvaged (CPU, GPU, and storage might have a decent chance of being good). Before jumping to those, if you other RAM you can test, you can do so.
No, one DIMM of RAM won't cause random restarts. As long as the remaining DIMM is indeed good, then that's not the issue.
Oh. I thought by narrowing down all the solutions I tried in order to eliminate this problem with the random restarts that was the elaboration, since I still don't know what's the reason for these random restarts to occur, all of a sudden.
True, I just mentioned the motherboard. As follow:
CPU: Ryzen 3600
CPU cooler: ARCTIC Freezer 34 eSports
Motherboard: Gigabyte B550M DS3H, updated to BIOS version F17
Memory: Kingston HyperX 16 GB 3200 MHz CL16 DDR4
GPU: ASUS ROG Strix GTX 1070 OC
SSD: Samsung PM961 256 GB
x2 WD HDDs 500 GB
PSU: Corsair TX550m
None of these parts have warranties anymore. The first four components are from 3 years ago, while everything else except the HDDs are from my old PC from 5-6 years ago.
I can confirm it's not a BSOD.
I could try testing the memory slots with a different kit. I also have another PSU around to test the PC with.
After getting a closer inspection, most of the motherboard is clean from residue. However, I've noticed a small amount of residue on the PCB around the CMOS slot area, as well as a little bit between the 24-pin connector to the CMOS slot. Oh and by hefty I meant the amount of dirt and dust the PC collected throughout the spring, being left outside like that.
Good!
If you can get into bios and stay in there for a while and also get into Windows but it crashes have you tried a bootable Linux iso?
I would kind of assume it is hardware regardless, but knowing the answers to these questions would be helpful. Not sure if I missed them and they're already answered.
It boots into Windows/restarts every couple of minutes to a couple of hours. It doesn't fail to boot.
I can try to just remain within the BIOS and see if anything changes... I don't have Linux, though.
The main issue hasn't exactly been determined yet, but most of the comments suggest it's a PSU/hardware/power issue, given that I've done probably everything one can on the software end of the spectrum, up to reinstalling Windows itself, and nothing was resolved. So I'm left with trying a different PSU, as well as a different memory kit.
As far as Linux, you can quickly make a bootable iso so you don't have to go through the hassle of like installing/wiping a drive/partition. Just boot off the usb/cd or whichever and you're basically on it and use it for a little while and check for stability. If it crashes/reboots/freezes there then it's almost definitely hardware. If you could use that Linux os for a long time and you pretty much never get a reboot, then there's a chance it has something to do with Windows being corrupted or just something with Windows not working well with a newly introduced hardware issue that Linux can handle.
So we know it's not a BSOD, but does event viewer show anything? I would expect Event ID 41 in this case and that's expected so don't pay it much mind (it just means "Windows detected the prior shutdown was not expected"). What I'm interested in is if these are alone though, or if there's other (perhaps consistent) major logs before/during the time of the restarts. It it's alone, it points more to "nothing is going south" software-wise, and there really is just some really bad electrical issue somewhere.
(Do note that Event ID 41 itself gets logged on the next startup after an improper shutdown and not during the restart itself [Windows has no time], so if these following startup happens well after the prior shutdown, take that into account when looking at times to try and reference a time frame.)
I'd expect the CPU to be good but that's purely a guess. They seem pretty robust in my experience.
I'd expect the same of the GPU and storage but with less confidence than of the CPU.
The PSU and motherboard are the likeliest I would think given the symptoms.
Very helpful! Do both of those. Perhaps individually first.
RAM is probably easier to try first but if your prior troubleshooting is correct that the existing RAM (at least one of them) is good then your RAM might not change anything. But worth a try due to how easy and fast it is (expect it to possibly need to retrain/restart a few times with the new RAM and that is normal).
Be sure to test in multiple DIMM slots if needed. Some RAM slots themselves could be bad and make it appear like RAM is bad.
I'd try your known working RAM and if that fails change the PSU.
If it still is bad, and you can't rule out the CPU or storage or GPU without buying new ones, I'd honestly go straight to the motherboard. But if you have a different GPU or storage to test it rules them out too. I'd honestly skip suspecting the CPU and while it's not impossible I'd be surprised if it was bad (watch it be this and nothing else now).