- Joined
- Jul 30, 2019
- Messages
- 3,276 (1.69/day)
System Name | Still not a thread ripper but pretty good. |
---|---|
Processor | Ryzen 9 7950x, Thermal Grizzly AM5 Offset Mounting Kit, Thermal Grizzly Extreme Paste |
Motherboard | ASRock B650 LiveMixer (BIOS/UEFI version P3.08, AGESA 1.2.0.2) |
Cooling | EK-Quantum Velocity, EK-Quantum Reflection PC-O11, D5 PWM, EK-CoolStream PE 360, XSPC TX360 |
Memory | Micron DDR5-5600 ECC Unbuffered Memory (2 sticks, 64GB, MTC20C2085S1EC56BD1) + JONSBO NF-1 |
Video Card(s) | XFX Radeon RX 5700 & EK-Quantum Vector Radeon RX 5700 +XT & Backplate |
Storage | Samsung 4TB 980 PRO, 2 x Optane 905p 1.5TB (striped), AMD Radeon RAMDisk |
Display(s) | 2 x 4K LG 27UL600-W (and HUANUO Dual Monitor Mount) |
Case | Lian Li PC-O11 Dynamic Black (original model) |
Audio Device(s) | Corsair Commander Pro for Fans, RGB, & Temp Sensors (x4) |
Power Supply | Corsair RM750x |
Mouse | Logitech M575 |
Keyboard | Corsair Strafe RGB MK.2 |
Software | Windows 10 Professional (64bit) |
Benchmark Scores | RIP Ryzen 9 5950x, ASRock X570 Taichi (v1.06), 128GB Micron DDR4-3200 ECC UDIMM (18ASF4G72AZ-3G2F1) |
Something to keep in mind which I found the hard way is if you installed AMD RAID drivers it sometimes likes to install a driver for the NVMe that shows up something like "AMD bottom device" whatever that means I don't know. So for example in my case I soft-raid (with Windows Disk Management) my 2 Optanes what would happen is one of those drives might get tagged for that device driver instead of the Standard NVMe driver. This causes the Windows Disk Management import to fail to see the 2nd drive of a 2 drive set. You need to cancel the import so you don't loose your data on the disk it did recognize. Then look for the "AMD bottom device" in device manager and replace the driver with the Standard NVMe driver. Then reboot and go back and try to reimport your raid set. At that point it should see both drives and you should be able to import your soft array.NVME as a platform can be very fickle on X670E. I mentioned on another thread that I had to replace my WD AN 1500. I ordered a cheap 4TB 4.0 drive to replace it. When I took the AN 1500 apart I took the first drive and Windows recognized it as raw data (Using a USB C NVME external). I put the 2nd drive in and it registered as my G drive (NVME RAID 0). When I looked in Disk Manager I noticed that my actual NVME RAID drive was now unavailable. I unplugged it restarted and now only my SATA drives are showing. I had to go into the BIOS and change the ON board Device setting from PCIe RAID to Auto. That gave me my NVME drives back. I am using a PCIe adapter for the new NVME drive. I have one of those Supermicro RAID cards from 3.0 days so while I was waiting I plugged it into that and put it into the PC. Well now my NVME RAID drive is broken. I had to format them to get them back but no report of the new drive in Windows. Did a restart and once again no access to NVME. Not even in the BIOS. The only NVME I know in the BIOS is my boot drive. The adapter arrives. It is a 4.0 x4 adapter. I take the Supermicro card out. Install the NVME in the new adapter, plug it into the PC, turn it on and I get the pop up when I go into Disk Magmt that lets me know my drive is recognized. I have even seen issues when you change what slot a drive is in. F me I formatted a NV2 using USB C and no computer can recognize the drive. I actully had to plug that into an M2 slot on the MB to get it back. I even had an issue with the MP700 where if I put in one particular 5.0 slot the writes would be like what this post is describing. I know I am not the average user but for me it comes down to PCIe 5.0 being rushed to the desktop. As an example the drive I bought yesterday is as fast as my MP 700 in Crystal DIsk Mark even though it is a 4.0 drive.