Dong Kollector Jax
INTL Dick Twisters
 [CEMETARY MAN (1994) SPOILERS]
Ballkicks: (+136 / -33)
Posts: 1045 (0.239)
Reg. Date: Feb 2009
Location:
Gender: Male |
(Originally posted on: 09-12-15 05:34:15 PM)
Edit Post
| Edit History
| Send PM
| Change Title
| Reply w/Quote
| Report Post
| Ignore
| Show All Posts
I'm posting this in case anyone (1) feels like reading it and (2) is unusually proficient with computers. I'm not 100% sure (2) is the case...



...Just 99% sure.
As for (1), I'll just copy and paste this to a tech support site if needed. However, I trust you people more than the randos out there. If you have the expertise and want to read this little story, I'd be very thankful.
Very thankful. 
As of about a month ago, I sometimes stayed on my desktop PC during electrical storms. For the most part, things went totally well. Occasionally, there would be some sort of power surge that forced my PC to restart, but other than that, there were no repercussions. I also had the bad habit of leaving my PC on all night sometimes because Sleep Mode had a chance of straight-up shutting down the PC without suspending my work, so I said "fuck it."
Here's what I remember about the night when it all changed. I was sleeping on the carpet floor of my apartment, but stirred as the room lit up with lightning. I decided it was best to save all my shit and put my PC into Sleep Mode, so I did so, lied back down, and woke up some time later as the thunder boomed even louder.
Suddenly, my PC kicked on without my permission when I wasn't in arm's reach of any wires, peripherals or connected parts. "Oh fuck," I thought, but I think I just turned it off and went back to sleep.
In a matter of days, things got more bizarre. I walked back into my room and saw my PC randomly restarting without my permission. (There were no Windows Update notifications I saw at all earlier that day.) It continued to work fine for a while, then I got Windows 10's casually-worded pastel-blue screen of death a couple of times. At one point, the screen was black for like a whole hour while the hard drive light kept flashing; I assumed it had locked up and cut it off in a rage. Then, eventually, the BIOS failed to detect my hard drive.
I was frustrated and distraught and tried restarting several times to no avail. Eventually, seemingly by accident, Windows 10 started loading again, and the PC worked. Cue another cyan screen of death, then another period of hard drive non-detection. Eventually, it seemed to detect the hard drive a few times, launching Windows Repair Utility (which always failed; don't have the logs). That quickly faded to another spiel of total non-detection that persisted for over a week.
While the hard drive seemed effectively dead, as far as my BIOS was concerned, starting the PC would sometimes cause the hard drive indicator at the top to light up several times as the hard drive clicked back and forth rapidly, then it would just give up. I researched the "click of death," and assumed this meant the drive was dead. Oh well.
"Okay," I thought, "I'll just run my PC from a flash drive, work to purchase a new SSD, then run my computer from that when it arrives."
(Over the course of that week, it seemed Ubuntu detected a 1 TB hard drive in File Manger precisely 1 time, but couldn't access it, probably because it was formatted for Windows. After a brief period, it was gone.)
After like 6 days of setbacks and multitudinous flash drive issues I won't get into, the SSD arrived today. Much like my old HDD, however, it doesn't seem to exist as far as my motherboard is concerned, even though everything else on the MB seems to run fine. Updating my BIOS to the latest version from 2012 did not change this.
This raises an interesting question: is the problem, in fact, that my motherboard has lost the ability to read hard drives from the SATA ports? Does that mean I need to repair/replace my MB, or could this be a power supply issue?
Long before this debacle, I had an issue where it seemed to take a random number of power-button presses to start my PC, ranging from 1-2 to about 10 (usually) to (occasionally) about 50. This didn't really bother me all that much, because I knew it would at least start, but I wonder if that issue is connected with this one.
Things I've already tried:
Reseating SATA and power cables.
Switching out SATA cables.
Switching out SATA ports.
Making sure each SATA port is set to AHCI and is enabled in BIOS.
Checking every boot list available in BIOS and making sure the HDs are not detected.
Resetting BIOS to defaults.
Updating BIOS.
OLD OPERATING SYSTEM: WINDOWS 10
OLD HARD DRIVE: SEAGATE BARRACUDA 7200.12 (1 TB)
NEW HARD DRIVE: KINGSTON SSDNOW 300 SOLID STATE DRIVE (120 GB)
MOTHERBOARD: ASUS SABERTOOTH 990FX
CPU: AMD FX-6100 SIX-CORE PROCESSOR X 6
GRAPHICS CARD: ATI XFX RADEON HD 6950
POWER SUPPLY: CORSAIR TX650 (650 watts)
RAM: Two big black bars that say "CORSAIR" on them.
There's the info, gentlemen. Have any leads?
|