Computer shuts down after hours of running and then it wont turn on until hours later.

pin-ice

Prominent
Jan 1, 2018
9
0
510
Hello everyone, i have a "little" actually a huge problem and im desperated enough to ask for support here before going to visit a technician who will charge me a bunch of $$ lol, ok so an engineer built this pc for me january 2018, i bought every piece via online, so one month later the computer fell off from 3.5 feet height and it had apparently no damage inside, the frontal-removable panel got a little broken but i "repaired" it with some special "glue" the fans inside and the rest still worked properly since i have used the computer for 2 months after this accident without an issue, but now it shuts down randomly after 2-10 hours of use, without any warning, and then when i try to turn it on it will turn on for 1-3 seconds and shut down again, and then it will automatically retry to turn on once or twice and then it will stay turned off, i must add that the LED in the MOBO is still bright even when it shuts down, though someone told me that the PSU can be damaged and still give enough energy to LED on MOBO, anyway if i turn off the power button behind the PSU for 3-4 hours and retry to turn it on it will start normally an then shut down some hours later just to repeat the cycle right now im writting from this computer, this is my build:

samsung ram 8GB 2133 Mhz
HDD 250GB (planning to add an SSD so this is temporal)
Intel Pentium G4560 7th gen (2 cores and 4 hyperthreading first pentium to have such function)
Chasis eagle warrior robot Q green (you can google it, is a mexican brand)
EVGA 430W PSU
Asus Prime B250M-A

So yeah maybe sometimes the psu gives the wrong power and either the psu or the board has a protection for it so it shut downs and orders the computer to not turn on anymore until faulty piece is changed but the instruction gets lost after some hours of being disconnected (PSU turned off)
The question what could be causing this issue? thermal paste damaged due to fall? or PSU ... or maybe the MOBO is damaged

Important note: The very first days that my computer was built cpu fan used to go to 100% speed rate just to few seconds later shut down with an over heating message (this is not the case anymore right now my PC is not turning off from high temperatures i been checking HW monitor all the time) so first of all i disabled C states and then opened the case and i made sure that the CPU cooler locks were well placed, and after that it didn't repeat anymore so 1 month later i enabled C states again and it never did shut down again, until last friday it started to shut down as i explained on the beginning of this post, today i disabled C states again i think my psu can handle them but not all the time, so it could be the issue too, if it shuts down again today or tomorrow, i will post to update everyone, but if that doesn't happen anymore it just means that the PSU + C states was the problem.

https://i.imgur.com/Wgnldal.png

I added a picture from HW monitor i took the screenshot after having it running for about 3,5 hours but sometimes it takes up to 10 hours to shut down so i can't tell yet if disabling C-States was any help, any suggestions are welcomed, im not a technician so don't ask me to open it and do stuff but i sure will advice it to my engineer

Update: Nope the C states were not the problem, still dont know what the problem is, will take it to the engineer until i have enough money to replace the most expensive part that i have just in case...
 
Solution
You may want to take your CPU heatsink off, clean any thermal paste from both cpu and heatsink.
Then apply one drop to CPU and then replace the heatsink.

It is possible that you may have disturbed the seal between HS and cpu when you dropped it.

That is the first thing that I would check.
You may want to take your CPU heatsink off, clean any thermal paste from both cpu and heatsink.
Then apply one drop to CPU and then replace the heatsink.

It is possible that you may have disturbed the seal between HS and cpu when you dropped it.

That is the first thing that I would check.
 
Solution