Possible (not proven) Physical damage of SSD caused by OBS

BroPikapi

New Member
(English isn't my first language, sorry for my poor grammar.)
Hello, this is my first, and probably only time posting on this forum, i come to tell my situation, that happened just a few hours ago, I don't know if this was caused by OBS, but certainly it was the last program that i willingly wrote on my hard drive.
So, a few months back i changed from HDD to SSD, both 2TB, i didn't format the HDD since i wanted a smooth transition, moving and pasting files to the SSD as i needed, so, effectively i had 2 bootable instances of windows, this will be important in a moment.
So today i wanted to export my OBS configs to the SSD, my friend told me that there was a button for that, so i logged out of my SSD and booted on the HDD, then i loaded windows and opened OBS, i clicked on the "export" button on "profile" and named a folder "OBSConfig" under the root of the SSD, after that, i logged back to the SSD, saying there was something wrong with the SSD information and it needed to restart, i had the option of restarting later, so before i restarted, i tried importing the settings to the newly downloaded OBS, it requested access but didn't do anything, then said i didn't have access to the files when i tried to open it myself (I have administrator rights on my PC), so , i tried adding myself manually as owner of the folder, clicked apply and a window popped up saying that the data was corrupted, so the operation couldn't be performed.
After all that, i clicked restart, and it booted on the windows recovery mode, it had the option to boot back like normal, so i tried that, didn't work, then tried reinstalling windows saving all the files from a local windows installation, didn't work, then tried reinstalling from the web, didn't work, after disabling CSM on the BIOS the SSD booted one last time, a lot of files were missing, discord booted half, tried reinstalling it fast, but it gave an error and, when i checked, the discord installation folder was gone (at least not found using the file explorer), same with firefox, but the folder still could be found with only some DLLs, so after all that, i decided to hop back into my HDD, it gave the same error message about something wrong with the information, requesting to reboot, so, in fear of my PC not booting and running out of any bootable devices i used that session only to install a fresh 16gb Adata USB drive (its not the best, but it's what i had) and copying an important project i had (5gb or so, I don't know if it was still complete), so after that, i booted from the USB drive, but my stupid self did format the HDD instead of the SSD, leaving me without info on the HDD ,sadly i cannot give the OBS version where i exported my configs from due to that mistake of mine, to avoid that again, i just unplugged the HDD from the SATA panel between boots (with the power OFF), so i could only format the SSD (windows doesn't tell which drive is which and since they are both 2TB they were very hard to check which one i was selecting).
I formatted the SSD, only for it to get an error 0x80300024 from the installer, after that, i did clean the SSD myself by using the following commands on the installer CMD:

$ diskpart
$ list disk
$ sel disk *id of the SSD*
$ clean
after that, the SSD was gone for real too, it seemed that the trick worked and tried installing but it only sent me back to the installer.

So, here i am, after almost 5 hours of pain and misery with a 3 month SSD (requesting warranty), i am writing this from the newly installed HHD installation that i made, the last week of work on my project is sadly lost forever, so now i can only tell my story of how i managed to fuck up so badly, i don't know if this is replicable, but if it is, i can request any extra info on this post or via private message (depends what kind of info).

I am still gonna use OBS btw
 

rockbottom

Active Member
avatar3629cl1.gif


Thx for the laugh!!
 

koala

Active Member
You cannot blame OBS for you being unable to manage hard disks and multiple bootable Windows installations on your PC.

There is one golden rule for installing Windows fresh onto a new hard disk/ssd while keeping the old disk that includes the old Windows installation as data disk: temporarily disconnect the old hard disk while installing a fresh Windows version on the new device. That's vital, otherwise you could get unwanted dependencies between the two disks and wrong drive letters, so you confuse old and new drives.

If the new install boots fine and works, reconnect the old hdd and assign new disk drive letters to the old partitions. To make sure to never ever boot this disk again, not even once, (that's vital for the health of the new system) delete the small non data partitions and only keep the partitions where you stored your data. Get rid of the \Windows directory and of all the \Program Files directories on the old drive as soon as possible to avoid confusion. The best is to backup all data you want to keep from that drive to the new boot drive or to some USB HDD, then format the old hdd to get a really clean start for the new system.

OBS has nothing to do with that. You could have migrated its settings by just copying the directory \users\<username>\appdata\roaming\obs-studio from the old drive to the same location on the new drive.
 

Lawrence_SoCal

Active Member
what @KAOLA said
Though, as an advanced user, my approach has been on occasion to use Partition tools (was Partition Magic, then Partition Wizard, iirc) to hide OS and boot partitions (vs deleting). But that only works if you REALLY know what you are doing. And I created (free tools) a bootable USB drive with WinPE and right drivers for every computer I (and family) have, and boot from the USB drive, NOT installed HDD or SSD
- why hide vs delete? so I have an emergency backup boot option to a known good state... done only when I have plenty of spare disk space... and knowing EXACTLY how to track which drive and partitions are which.. I usually create a unique Display Background setting on the old backup boot image to make it that much more obvious if somehow I end up booting into unexpected version of OS

The safe approach I use is to boot from my USB drive, make an entire drive backup image either to locally attached large archive HDD (current one is 18TB) or over the network [depending on situation] before even starting partition work... just in case. From that USB, I duplicate drive/partitions, resize partitions as necessary, etc. Then hide partitions that will eventually be removed, test, repeat until good. Then delete old boot and OS partitions, as Koala mentioned if you need that space, and re-partition remainder as appropriate. *IF* partition to resize is data only, and you've made all the non-partitioned free space contiguous, then I prefer to boot into the OS, and let Windows expand the partition itself (I do this as I know the caveats and implications of this choice... I've had better results this way.. ymmv {your mileage may vary}, so to speak)
 

BroPikapi

New Member
You cannot blame OBS for you being unable to manage hard disks and multiple bootable Windows installations on your PC.

There is one golden rule for installing Windows fresh onto a new hard disk/ssd while keeping the old disk that includes the old Windows installation as data disk: temporarily disconnect the old hard disk while installing a fresh Windows version on the new device. That's vital, otherwise you could get unwanted dependencies between the two disks and wrong drive letters, so you confuse old and new drives.

If the new install boots fine and works, reconnect the old hdd and assign new disk drive letters to the old partitions. To make sure to never ever boot this disk again, not even once, (that's vital for the health of the new system) delete the small non data partitions and only keep the partitions where you stored your data. Get rid of the \Windows directory and of all the \Program Files directories on the old drive as soon as possible to avoid confusion. The best is to backup all data you want to keep from that drive to the new boot drive or to some USB HDD, then format the old hdd to get a really clean start for the new system.

OBS has nothing to do with that. You could have migrated its settings by just copying the directory \users\<username>\appdata\roaming\obs-studio from the old drive to the same location on the new drive.
I'm not blaming OBS, but i tought it was a possible cause (very unlikely, but very severe if true, that's why i posted here, i'm no windows expert nor i know how OBS works internally).
Thanks for the tips, i will take them in account, didn't know booting another windows would be that fatal for my system.
the SSD didn't boot back up, installled windows on it but it just didn't install and didn't boot.
Maybe i just witnessed my SSD die and OBS was the detonant, or just the last app that launched properly before it all went to trash.
 

PaiSand

Active Member
Don't think OBS has anything to do with the boot sector of a disc, HDD or SSD, or any kind of discs.
 
Top