TwixOps

Well, for better or worse I have progress... When I came back into the room, the BIOS was frozen. After force restarting the computer, it didn't make POST, and upon further investigation the MB is reading code 00. Now, It doesn't make sense that these issues could even be related... Maybe all the hard resets cooked something important because something somewhere is well and truly fried. In any case, this is a problem for tomorrow's me. I'll probably start by pulling off the clc, and if that doesn't end any insights, I'll try buying a new PSU. EDIT: Could I have somehow killed the BIOS? Would that cause a post code 00?

I did both before and just for the hell of it but both again just now. I'm beginning to think that either this board is haunted or I experienced 4 simultaneous drive failures

Here you are Options, note m.2/SATA switch I referenced earlier (highlighted) Further down, connected devices. Also, in case you want it, here is the boot settings window, note the CSM I referenced in OP at the bottom. Kingston m.2 drive is the only one that appears in boot option drop-down list

Physically moved two SATA cables from SATA3_A0 and A1 (ASmedia controller) to SATA3_4 and _5 (Intel controller)

Clearing CMOS had no effect.

Issue: none of my HDDs/SSDs show as bootable in BIOS, only an M.2 without an OS appears in that list. What I was doing when it broke: switching the physical SATA ports in my MB to which the drives were connected (moved two HDDs from the ASmedia controller to the Intel controller so I could use Intel RAPID to create a RAID array) Symptoms: Attached picture shows the issue - connected drives are visible in "storage configuration" in bottom left but not in "boot priority" on right. What I've tried so far:. Moved boot ssd back to ASmedia controller (SATA3_A1) Result: no improvement Disabled M.2 drive by forcing its SATA lanes to go to SATA3_0 and _1 in BIOS (they share lanes, to use that m.2 slot, you lose 2 SATA ports) Result: m.2 drive disappeared from bios Disabled compatibility support middle in BIOS. Result: m.2 drive disappeared from boot priority list Disabled fast boot Result: no improvement Moved boot SSD to SATA3_0 and forced the SATA/m.2 switch to SATA in BIOS. Result: m.2 drive disappeared from bios, boot ssd appeared on SATA3_0 but not in boot priority list Disabled RAID and XMP for the hell of it Result: no improvement EDIT: cleared CMOS Result: no effect Hardware MB - ASrock z370 gaming k6 CPU - i7 8700k Storage -120gb SSD (boot) Samsung 840 Evo -2x WD 2TB drives -WD 500GB drive -480GB Kingston m.2 drive System was fully functional before I moved SATA ports

I'm currently using an older fairly high end 1080p 120hz monitor as the main display in my setup. In the near future, however, I'm going to be picking up a 4k monitor for easier CAD work when I'm home. I'm a little on the fence about which of the two should I use when I'm gaming, as the better response time and refresh rate of my current monitor set balanced against the higher resolution and larger physical size of my soon to be. I've got the horsepower to push the frames either way now that I'm getting rid of the old 660ti (1080 arrives Monday!!!)

Did you mean to say 2018 there? If so, that is surprising to me.

My GTX 660ti PE is starting to get a bit old, so I'm looking to upgrade in the near to mid future. I figure that it is probably worth it to upgrade to whatever their next generation chips are. What kind of timeframe are we looking at for them? Q4 2017? Q2 2018? I honestly don't follow the release schedule closely at all so I'm not sure what the interval between generations usually is.

Consider installing your system drive in another computer and seeing if it will boot to desktop there.

My brother suffered an apparent OS corruption recently, so I am working on installing a clean copy of Win7 Ultimate for him. I installed the OS onto his 1TB SSD while it was connected to my computer, and the new OS booted to desktop just fine. When I went to connect it to his system to install drivers however, the computer does not detect the OS on the drive. When I plug my C:\ drive (120Gig SSD) into his system, it boots to desktop just fine. I have already: Uninstalled all other drives from the system and made sure it is booting from the correct one in BIOS Tried different SATA ports/power cables with both SSDs, (mine works every time, his doesn't detect an OS) Gone back to my system and booted to desktop with the his new install (it is completely fresh, nothing installed on it yet) Any advice/suggestions would be appreciated.

I'm setting up system restore on my Win 10 pro PC, and I'm confused about whether I need to allocate space on each hard drive for the restore points. My system has: 120 GB SSD for the boot drive, a pair of 2 TB HDD in RAID 1 for program installation 1 500 gig for media. Do I need to allocate space on each drive for the restore points? How much?