Jump to content

MarkoARH

Member
  • Posts

    2
  • Joined

  • Last visited

Awards

This user doesn't have any awards

  1. Ok, so the way to go was to detach all other drives, totally reset the bios and to circle the system from booting, shutting down, power off the power supply, emptying the capacitors and power up again until the boot device "Predator ssd" registered as a "Windows boot". For all that have read thak you for the time spent !
  2. So, this is gonna be lengthy post. Be it because of lack of googling skills or just reoccurring bad luck with this particular problem I was unable to find a solution online. Let me share my problem that has bugged me for years now on this build from 2016: MB: Asus X99 -a CPU: 6800k RAM: 16Gb DDR4 Kingstone Savage 4X4Gb GPU: Asus Strix 1080Ti OS boot device: Kingstone HyperX Predator 240Gb on a PCI-e board SATA: 5 drives total 2x2driver running on Intel Raid1 First encounter: At some point in time around 6 month's after I had this PC I had to move my OS device from it's PCI-e x4 board that was located on the bottom PCI-e x16 socket to the m.2 socket of the motherboard so I could fit another identical GPU ( Asus strix 1080ti ). Everything worked just fine no issues whatsoever. Until, due to overheating of the SSD drive, I had to move the GPU to another rig and go back to the original setup where the SSD would sit in it's dedicated PCI-e card on the bottom x16 socket. When I tried to boot I got a " no operating system detected" promt. After failing to resolve the issue I had endure the painstakingly tedious task of reinstalling the OS and a plethora of programs I use for work and whipping the drive in the process. Second encounter: A year or so later pretty much the same thing happened almost in the same order cannot recall why it was swapped but It had to do something with the GPU's. Again so many hours of reinstaling the OS and programs and plugins and scripts and importing settings etc. Third encounter: Now, after stupidity not adhering to a promise I made to my self that I will not fiddle with the drive until it died I wanted to expend the storage for my libraries that have bulky files that I work on so i tough an 240Gb Kingstone a2000 nvme drive would be quite nice to have for storing current project files before storing on the aforementioned RAID HDD's. I had one nvme drive laying around from a never made build so I put in ( in the MB m.2 socket ) figured it be straight forward. I turn on the pc and voila, there was an OS on the drive ( unused just installed ). Figured boot priority was scrambled so I head to the boot menu select my never so trusty Predator and there comes the " no operating system detected"..... A2000 runs the OS it had just fine Predator reads in BIOS but does not show in the partition manager in the OS the A2000 holds Thanks for reading this lengthy post and I hope there is a fundamental lack in my knowledge and that the issue is far simpler to solve cause this always happens when I have some deadlines breathing down my neck. Ohhh, almost forgot CMS was on by default I figure that might have some relevance. Thanks in advance !!!! P.S. the overheating of the SSD when installed on the MB m.2 slot is caused by 2 main factors. 1. The gpu is blowing hot air or when unused blocking the air to run over the ssd 2. On this particular MB the TPU chip,or what asus calls it, that is their "power management engine" runs extremely when under load and it sits just under the ssd Just a rant And sorry for any grammar issues you may stumble upon English is not my native language so if my post has some inconsistencies please bear that in mind.
×