Mcneck

Finally got around to open up my 3090 and repasted it. pictures from before repasting are attached.
And well… somewhere along the way I seem to have fucked up. I no longer get an output from the GPU. Onboard graphics are working but the GPU does not want to show me a picture.
It lights up, fans are spinning but it seems dead. Fuck me.
 
I double checked if I ripped off any of the caps around the GPU (I didnt)
 
Any suggestions what else I could do?

Yeah, I thought so too, but they have listed every Zotac 3080 TI model that is compatible trinity and trinity OC. But for the Zotac 3090 they have only listed the trinity model... that made me think there might me an issue with the OC Model. I will ask Alphacool directly about it.
 
Yay... guess what brand of thermal paste I used 🫠

This is from the Be quiet Wattage calculator:

even with 4 Ram sticks, 4 Fans, 4 SATA-Devices and even a small overclock on the GPU, your PSU should handle it without a problem.
370 Watts from 550 are roughly 70%. So your setup is also efficiency wise pretty good looking.

This is from the Be quiet Wattage calculator:

even with 4 Ram sticks, 4 Fans, 4 SATA-Devices and even a small overclock on the GPU, your PSU should handle it without a problem.
370 Watts from 550 are roughly 70%. So your setup is also efficiency wise pretty good looking.

to your first question: most definitely, yes! (I think what you meant is, will there be a bottleneck between the two components? and I think not...)
to your second question: probably, but I would upgrade to be safe. Also depends kinda on what other Hardware you are planning to put into your rig.
I recommend using one of those: https://seasonic.com/wattage-calculator

So there are basic files that make up your VM. 
VMX = Virtual Machine Configuration file
VMEM = Virtual Memory file
<machine>.VMDK = Virtual Disk characteristics file
<machine>-flat.VMDK = Virtual Disk data file
NVRAM = BIOS/UEFI file
 
These are the basic files you must have for a VM to operate in VMware.
For resolution 1 in your guide, you should have only deleted <machine>-delta.VMDK files which are changes that have been made after the snapshot that have not been commited into the flat file (your base disk). 
 
So back to your question. You should have *only* touched the <machine>-delta.VMDK files, are you saying you're missing all your VMDK's?
Did you create your new VM and copy your existing VMDK's to the new VM's datastore folder, before trying to delete your old VM? If so there should be no reason for the VMDK's to just disappear. 
When you say you can "see" these files, have you tried setting up VM3 by selecting the disk you can see? It's worth noting that in the Datastore "Browser" you cannot see the -flat.vmdk file, you can only see the descriptor .vmdk. So if you still have the -flat.vmdk's this is the sort of behavior you would expect, as they cannot be see in the browser, but can be seen when setting up a new VM. If it is the flat file, then when you select it for your new VM, it will automatically create a new descriptor .vmdk file. 
 
And yes you can easily move your .vmdk files around if need be, but if you re-create the VM, theres no need to move any files. Use the new VM3, and then delete the traces of VM1/VM2 when you've confirmed its working and your vmdk path is to the folder for VM3. 
 

drying the drive with silicagelpads seems to have done the trick, the drive still works and I am copying everything thats important to me to the new drive, in case it fails at a later point in time.