[SOLVED] random reboots in my pc

[tallyneedshelp]

I’ve been dealing with an issue where my pc would randomly reboot. Their is no BSOD and nothing happens. These reboots are just completely random. At first I thought it could be a psu issue because it stopped turning on after some time, so i tested this and bought a new psu. It was working fine for about 2 weeks or so, then it just started to crash again. I don’t know what the cause is and have no idea anymore.

 

[LinuxDevice]

I’ve been dealing with an issue where my pc would randomly reboot. Their is no BSOD and nothing happens. These reboots are just completely random. At first I thought it could be a psu issue because it stopped turning on after some time, so i tested this and bought a new psu. It was working fine for about 2 weeks or so, then it just started to crash again. I don’t know what the cause is and have no idea anymore.

How old is the motherboard? I ask because if the CMOS battery is running low, then the BIOS itself can make the system unreliable. In that case a new battery and BIOS set to sane defaults would solve this.

Similar for heat issues. If the heat sink compound is one which solidifies and loses effectiveness over several years, then you might solve a heat issue just by using new heat sink compound on the CPU.

It isn't likely to be a big help, but sometimes reseating any PCIe cards or connectors to the motherboard and other peripherals can help. Connectors which stay in place for many years can suffer from thermal creep (heating and cooling cycles over many years can cause the connector to actually move slightly and cause connectors to fail just like when not fully seated).

You could also test with memtest86+ for a day or so. Typically memtext86 can verify basic function. If memtest86 does not fail, then you at least know basic RAM and CPU function is in good shape (without hardware for that part of the system being at fault).

 

[tallyneedshelp]

How old is the motherboard? I ask because if the CMOS battery is running low, then the BIOS itself can make the system unreliable. In that case a new battery and BIOS set to sane defaults would solve this.

Similar for heat issues. If the heat sink compound is one which solidifies and loses effectiveness over several years, then you might solve a heat issue just by using new heat sink compound on the CPU.

It isn't likely to be a big help, but sometimes reseating any PCIe cards or connectors to the motherboard and other peripherals can help. Connectors which stay in place for many years can suffer from thermal creep (heating and cooling cycles over many years can cause the connector to actually move slightly and cause connectors to fail just like when not fully seated).

You could also test with memtest86+ for a day or so. Typically memtext86 can verify basic function. If memtest86 does not fail, then you at least know basic RAM and CPU function is in good shape (without hardware for that part of the system being at fault).

The motherboard isn’t near old. I have a b450 tomahawk max and I built this pc about a few months ago in august, so it’s only about 4 months old. If I tried to run memtest86+ I’m scared it’s just reboot in the process. It’s currently rebooting, disk checking, then starting up and repeating about a minute into the computer just going into desktop.

 

[LinuxDevice]

The motherboard isn’t near old. I have a b450 tomahawk max and I built this pc about a few months ago in august, so it’s only about 4 months old. If I tried to run memtest86+ I’m scared it’s just reboot in the process. It’s currently rebooting, disk checking, then starting up and repeating about a minute into the computer just going into desktop.

You really should run memtest86+. Knowing if it reboots would be a very valuable bit of data. That is the whole point: Find out if basics are correct, and it is quite possible this is only a software issue.

Even though the system is not old, perhaps you could go into the BIOS and tell it to reset to default values. If memtest86+ fails, then you could try running with a single stick of RAM. Booting into Windows, failing and corrupting the disk, and then repeating won't help.