[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/wsr/ - Worksafe Requests

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: 1694119063797728.jpg (273 KB, 1600x1200)
273 KB
273 KB JPG
Please someone help me through this nightmare tech issue
I removed and installed some new fans on my PC.
Then my PC got stuck in an infinite boot loop until it finally got to a black screen with the mouse still visible. I couldn't do anything on that screen like ctrl alt del and stuff.
I left it like that for about an hour and it went to a "diagnosing your PC" screen that lasted for 30 minutes before I shutdown the PC.
I reseated the RAM and cleared the CMOS battery just to be safe then rebooted.

Same issue. Seems like my OS drive got corrupted. So I removed it and installed a backup version SSD that I made a week ago thinking it would be solved. Same issue happened and that drive also got corrupted.
I reseated and replugged every component in my PC to be safe and put in a second back up of my OS drive (3 SSD's total at this point)

Same issue with infinite black screens and mutliple failed automatic repairs and diagnosing your PC screen. I used external SSD drives to see if my data was still intact on each drive and luckily they were. They just won't boot for some reason.
At this point I have no fucking clue what to do. Is my mobo just bricked somehow for no fucking reason?
>>
If it's bricked it's not for no reason. You messed around with the internals, even just a fan, that could be it.
>but I was careful
Maybe there was a manufacturing error and the a trace shorted when the fan circuit was energised
>but I wasn't powering the fan from the board
Not trying diagnose a board I've never seen, just making the point it wasn't nothing, like why you reseated the ram just in case.

If you can access the drive without a stream of errors and without having to leave it at a data recovery shop then your drive isn't corrupted. Buying a new motherboard sucks, especially if it's old and you'll need new memory modules to fit the new one, but the data are usually harder to replace.

Put your drive in an enclosure, boot from it on the same or different hardware. Being Windows it might complain about new hardware but at least you're bypassing the onboard controllers in case that's a problem and you know the drives work on different harfware. Or is that what you meant by
>I used external SSD drives to see if my data was still intact

If it boots from USB but not internal drives then that points towards a controller, cable, or power supply issue.

Remove all the ram sticks, power up and wait for the proper error signal. Replace only one. If you have onboard graphics remove the graphics card. See if it boots.

Try booting from your rescue drive. The one you made on a USB drive. You're smart enough to have backed up your drive twice sort of recently so you'll have a couple of those.

Try booting with a non windows OS. A live linux distro is extremely useful for fixing a lot of windows problems. You can make one with an old android phone, EtchDroid, and an OTG connector if you don't have better hardware.

If either of those two boots are successful with all the hardware connected then you've at least eliminated it being a mobo, video card, memory issue.
>>
>>1554085
Thanks, haven't read all of it yet just posting an update on my end
I unplugged all of my drives except the original C drive I thought was corrupted and it worked with no issues. I did an sfc scan now and chkdsk and got zero errors
It might be an issue that happens when I use more than one drive on the system. I'm going to try replugging each drive alongside the original one by one to see what happens
>>
>>1554085
>>1554087
Welp seems like the culprit was a dead sata ssd. It's the only one that results in boot looping when I plug it in. All others boot up fine Guess it either just chose the perfect time to die or my fan fiddling somehow killed it


Is there a way to service it or at least figure out how old it was? I'm fairly certain it was from 2018 ish. It's a Samsung evo 1tb
>>
>>1554088
For anyone else with a samsung evo sata ssd, it seems like this is a very common issue in that the drive can suddenly cause your entire system to hang until it's unplugged. All my other drives were fine and there was no corruption. Thankfully I backed up the evo ssd contents too but I'd be wary of buying samsung satas again



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.