PC has gone berserk and can't work anymore (solved)

Perene

Distinguished
Oct 12, 2014
143
3
18,695
My PC has gone berserk after this happened another time:
http://www.tomshardware.com/forum/id-3214510/computer-turns-opening-app-ipad.html

https://m.youtube.com/watch?ebc=ANyPxKpm2LXnTxPJGc3PVvG6EwvjQS6mqBcPjhdMCw_6d6hTsv1ZRF88EqhkCVQdDwxI9KXvEPo-&v=jAuKjiLyXqI

https://m.youtube.com/watch?v=ZSlzpX9gHkw&ebc=ANyPxKpm2LXnTxPJGc3PVvG6EwvjQS6mqBcPjhdMCw_6d6hTsv1ZRF88EqhkCVQdDwxI9KXvEPo-

Even after I turned off all components, and tried to restart, it's not working anymore. Hdtune said all discs are fine (right before this happened I checked my discs). It happened once, but the PC became normal hours later. Not this time.

Who is the culprit? Oh, BTW, the only odd thing I noticed in windows 10 64 was a BSOD saying critical corruption. Then again, this happened when I was using virtual box. And happened once more after I uninstalled. Not sure if this info is relevant somehow...

******** Update ********

I managed to update the BIOS, following to the letter the instructions.

http://www.gigabyte.us/MicroSite/121/tech_a_bios.htm
http://br.gigabyte.com/products/product-page.aspx?pid=4962#manual

However, right after I did it, the problem happened. And for the 1st time after a reset. In the other scenarios, it was after it turned on by itself.

Then I turned everything off. Waited for 10 minutes (if I wait 1 or 2, it will continue to present the same problems from the Youtube videos).

It worked just fine after I waited. Windows 10 is OK, the system booted. Meaning the BIOS was updated successfully. And also meaning the BIOS wasn't the culprit.

- Something inside the case is causing this. And I don't think it's hardware related. I mean, not a defect, perhaps something needs to be cleaned, or maybe it's the PSU that is defective? The memory?

Or maybe it's a cooler that needs to be replaced or bought?

It's been a while this case isn't cleaned/opened.

What I can tell is that is very unlikely one the Hard-Drives (or the SSD) is causing this. Their health is OK according to HDTune, and I haven't noticed anything wrong while using Windows.

Now I would like for you to look into these pictures, taken from the BIOS. Specially the CPU temperature. Is everything OK?

https://goo.gl/GfBL2C

To sum things up:

- Computer works OK if already on. It works 24/7. However, once it's turned off and you try to turn on, this happens in random moments. It isn't happening everytime I reset the machine or turn it on. In fact, it wasn't happening until a week ago.

Please also note that the PC tries to turn on, then turns off, then ON-OFF-ON-OFF until you unplug from electric current.
 
Solution
Actually not a single piece of hardware was found to be defective in any way. This was perhaps caused by some "bad contact" (I think that's what is called in english), meaning that removing the RAM and reinserting again in the motherboard, for example, would solve the problem.

The only thing that I noticed (and this wasn't what caused the beeps, I guess) was an increase in the HDTune Interface CRC Error Count from 0 to 202 in "Data" after I sent the Western Digital 1 TB SATA perfect Hard Drive (perfect = never had any issues and all other specs are 100% fine) for them, however once I asked them to replace the SATA cable, the HDD was recognized again (after I sent for them to clean the case, Windows and the motherboard kept saying the...

Lutfij

Titan
Moderator
1| When posting a thread of troubleshooting nature, it's customary to include your full system's specs. It almost looks like the system was prebuilt. I could be wrong though. How old is it?
2| Have you tried running your system with everything set to factory default/auto?
3| It's quite possible that you're going to have to reinstall your OS and the issue will be resolved. I would like to stress though any underlying issue might come to light after learning of your system's specs.
 

Perene

Distinguished
Oct 12, 2014
143
3
18,695
This issue was solved after I send to technicians to clean the case and replace the SATA cable for one of the Hard Drives. I also installed a new HDD.

I don't know what caused all this, but it stopped doing these beeps for good.

This is my system:
Core i7 4770, and MB: Gigabyte H97M-D3H, plus Win10-64 bit and one RAM 8 GB (Corsair DDR-3 1600mhz Vengeance - CMZ8GX3M1A1600C10).

Video: AMD Radeon R7 200 Series (R7-265)

HDD WD Blue 1 TB
2nd HDD: the Samsung 750 GB (753LJ - old, 6-7 years old, but still works)
SSD Samsung EVO 840 120 GB (where the OS is installed)

CPU Cooler: Hyper 212X
PSU: Seasonic ATX 520W S12II-520 Bronze

This is the case I am using ("Gamer PCYES Rhino Preto 3 Fans 120mm Led Azul Lateral em Acrílico"):
https://www.youtube.com/watch?v=CevFGtwwTqY

And if I am not mistaken, a 2nd cooler was bought later.

The age of these components? 2.5-3 years.

I have removed the Samsung 750 GB from the case and I am now selling.
 

Lutfij

Titan
Moderator
^Thank you for a followup. It's good to know that you found a resolution to the issue.

When posting your full system's specs, pass them on as:
CPU:
Motherboard:
Ram:
GPU:
SSD/HDD:
PSU:
Chassis:
OS:

Quite possible the HDD was at fault. By cooler do you mean a cooling fan or an actual CPU cooler? By second you mean the first one failed/got damaged?
 

Perene

Distinguished
Oct 12, 2014
143
3
18,695
Actually not a single piece of hardware was found to be defective in any way. This was perhaps caused by some "bad contact" (I think that's what is called in english), meaning that removing the RAM and reinserting again in the motherboard, for example, would solve the problem.

The only thing that I noticed (and this wasn't what caused the beeps, I guess) was an increase in the HDTune Interface CRC Error Count from 0 to 202 in "Data" after I sent the Western Digital 1 TB SATA perfect Hard Drive (perfect = never had any issues and all other specs are 100% fine) for them, however once I asked them to replace the SATA cable, the HDD was recognized again (after I sent for them to clean the case, Windows and the motherboard kept saying the drive wasn't there), and this status hasn't changed since that day. Meaning that replacing the cable solved this other issue, too, and I am using this drive for several days without any problem.

The coolers are OK, the 2nd was a cooling fan.
 
Solution