GSync IPS 75HZ -=-=- Chi Mei 60Hz (Overclocked to 85Hz) Realtek High Definition Audio / NVIDIA High Definition Audio G752VS (U3E1) -=-=- ASUSTeK COMPUTER INC. Join Date Apr 2017 Reputation 48 Posts 1,125Īrray Darnassus PC Specs Darnassus PC SpecsĪSUSTeK COMPUTER INC. (3) HDD's - Western Digital Caviar Black 2TB 3.5-in SATA III 64MB CacheĬorsair Obsidian Series 650D Black, ATX, Mid TowerĬorsair Digital AXi-Series AX1200i (1200W) 80+ Platinum Rating (2) Dell UltraSharp U2515H 25-inch monitors Sapphire Nitro Radeon R9 Fury 4GB HBM Backplate Intel Core i7-6950X Extreme 10-core 25MB Cache 3.0 GHzĬorsair Vengeance LPX Red DDR4 DRAM 64GB-4x16 3333 (CMK64GX4M4B3333C16R) And i've read whole 30 pages of this thread.Īrray davemon50 PC Specs davemon50 PC SpecsĪsus G752VY-DH72 (17") and Asus G752VT-DH74 (17")Īsus ROG LGA2011-v3 Rampage V Edition 10, x99 EATX My OS installed in the Samsung 950 PRO SSD that came with the laptop.
Is there any working solution at all to this long running problem? please? Why do i have to clone my disk and update on spare SATA, am i cursed? G752 BIOS doesn't even read the Samsung 950 PRO NVMe and only list it as 'Windows Boot Manager' in 'Boot'Įdit: My laptop is G752VY. Had my Windows upgraded to PRO version so i can refuse updates bcs it eat to my SSD lifespan and network usage unnecessarily. The so called new NVMe driver from ASUS, the disabling of S.M.A.R.T, Raid mode whatever nothing works AGAIN. Well NOW it's happening again, feature update, winload.efi problem, the whole thing.
In the end, i managed to update 1607 to 1709 by cloning the OS to a SATADrive, remove the NVMe SSD and then updating on the SATA Drive, i had thought that's it, no such problem will arise anymore. I sent a complaint and they ask me to RMA, which also not an option because it will simply take too long and i don't have spare laptop/computer to use. I'm aware that clean format works, but that's not an option for me. I tried all the solutions about disabling S.M.A.R.T and the likes to no avail. Previously i dealt with this problem on 1607 update, referring to the 30 page long thread here about similar update failure on NVMe.
0 kommentar(er)
