----------------------------
Requested Specs
SAMSUNG 950 PRO M.2 2280 256GB PCI-Express 3.0 x4 Internal Solid State Drive (SSD) MZ-V5P256BW
ASUS TUF SABERTOOTH Z170 MARK 1 LGA 1151 Intel Z170 HDMI SATA 6Gb/s USB 3.1 USB 3.0 ATX Intel Motherboard
Hyper M.2X4 Mini Card
-------------------------------
My full system specs are on another post. (I also had RAM issues that have been resolved)
That's great advice that you gave me on the PCI E slot sharing certain SATA ports. However, I don't think that sharing resources would lead to a totally non-recognizable device. You indicated that there might be appropriate BIOS settings for the onboard slot? That is what I am really interested in because I plan on using that PCI slot for a GPU SLI once the price drops on my card. In the meantime, I will try and use the expansion card and set the BIOS to PCI-E just to see if it will recognize. Bottom line is that I want the drive back on the MOBO "compartment" . I guess that the information on the drive will be lost and that it is corrupted. How it got corrupted, I have no idea considering that I keep Defender running and updated. I was in the middle of using Photoshop when it happened. Currently I have two separate drives using the Sata ports E1 and E2. I will move those to the Sata G ports. This is the block containing 6. Therefore leaving E1 and E2 open. I will look in the bios for a M.2 motherboard "mode" as you suggested. This is so frustrating. I spend hours upon hours setting that drive up then BAM! I will be monitoring updates to the post all day.
Thanks for your help,
Red
You know, given how sparse the information in ALL motherboard manuals -- ASUS neither worse nor better -- it's interesting if they included that caution about setting the BIOS appropriately, especially when intending to add an M.2 NMVe to the motherboard slot for it. And more interesting -- they embedded that warning or instruction in the BIOS instruction-pane when that M.2/PCI-Express-mode has focus.
It could insinuate the possibility that just the wrong BIOS setting could damage hardware or even firmware.
That wasn't my own unpleasant experience. I am addicted to a popular Steam game which may work well on a certain generation of NVidia card, but not only later models, despite Experience's recognition, management and update. Occasional freezes occur and recover, so the user may have varied experiences keeping the airplane in trim or in the air, the stock car from hitting the rock wall, the shooter who misses an occasional DOOM-demon of critical importance for that moment.
At one point, this happened as I was "tuning" dual-OS separate NVMe caches for SATA devices on the 960 EVO. [You cannot mix the caches -- whichever proprietary or agnostic caching software you use. It requires for me creating separate logical volumes of initially equal size, in addition to "C :" drive boot-volumes in other logical volumes on a large NVMe. For the moment, the boot-volumes are on an ADATA SATA SP550 480GB -- more or less up-to-snuff for what you pay.] the 250GB NVMe EVO is split into two 100GB volumes -- one for Win 7 boot-time, the other for Win 10 boot-time.
Enter my fingers -- there is possibility that I hit a peculiar combination or sequence of keys to make a panic exit from the game when I might only have waited. Now of course, the graphics card is on the PCIE bus with an NVMe expansion card -- that's just a fact.
I think it then threw a message with the word "Samsung" and the word "reset" in the text I barely had time to read. But it recovered to Windows -- no freeze there, no BSOD or hard reset.
It disappeared from "Storage Controllers" in Device Manager. Rebooting -- it remained missing in action. So of course, if you think it was a bad NVMe, a bad PCIE slot -- RAM? CPU? less likely -- you'd unplug everything, pop the case open, remove the NVMe. Oh -- and there was especially the possibility that the expansion card failed, when we point out that it seems like nothing but circuit-traces to the PCIE edge-connector. So that became first priority, and I replaced the card.
Replacement was ASUS Hyper M.2 X4 Mini, which also optionally works with an ASUS hyper-kit device.
At system boot, the drive was again recognized, the partition and volume intact -- (but I chose to replace those anyway). Nothing more to it. No more hiccups. My LACK of knowledge tells me to stick with the ASUS Mini just for the CHANCE that I'd avoid any future problems, but I always recognize multi-causation and things like "mutual-independence" or other probability scenarios.
But I suppose if I report the detailed symptoms I had here, because many of us are all just learning about NVMe, PCI-Express, SATA-Express, M and B key devices (or both). I discovered an outfit with "cable" in their name featuring a vast number of devices and adapters for NVMe and M.2. the problem is finding the one you need the first time.