SOLVED
Home

1703->1709 BSOD 0xc00000bb on devices with NVMe SSD's

%3CLINGO-SUB%20id%3D%22lingo-sub-130851%22%20slang%3D%22en-US%22%3E1703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-130851%22%20slang%3D%22en-US%22%3E%3CP%3E1703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20will%20be%20the%20very%20first%20question%20I%20will%20ask%20in%20the%20AMA.%26nbsp%3B%20I%20hope%20you%20have%20a%20better%20answer%20than%20%22we%20are%20working%20on%20it%22%20ready%20for%20the%20thousands%20of%20us%20with%20this%20issue%20and%20waiting%20for%20a%20fix%20since%20September.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F08485ba0-f69f-483b-861e-238f161dabee%2Fproblem-with-upgrade-to-creators-update-on-nvme-disk%3Fforum%3Dwin10itprosetup%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F08485ba0-f69f-483b-861e-238f161dabee%2Fproblem-with-upgrade-to-creators-update-on-nvme-disk%3Fforum%3Dwin10itprosetup%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-204630%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-204630%22%20slang%3D%22en-US%22%3EI%20have%20managed%20to%20update%20my%20PC%2C%20after%20the%20third%20update%20to%201803%20(OS%20Build%2017134.83).%3CBR%20%2F%3EIn%20build%2081%20the%20SSD%20blunder%20was%20fixed.%20Also%2C%20there%20appears%20to%20have%20been%20an%20issue%20with%20Avast%20AV%20that%20is%20now%20fixed.%20I%20did%20a%20regular%20windows%20update%20and%20it%20finally%20worked.%3CBR%20%2F%3EI%20suggest%20to%20anyone%20using%20Win%2010%20Pro%20to%20use%20the%20option%20Semi%20annual%20%2B%20365%20days%20in%20the%20advanced%20options%20of%20Windows%20update%20(Choose%20when%20updates%20are%20installed).%20This%20will%20deffer%20the%20semi%20annual%20feature%20updates%20by%20about%2015%20months.%20Plenty%20of%20time%20for%20MS%20to%20fix%20all%20the%20bugs%20they%20introduce.%20Then%2C%20when%20you%20want%20to%20install%20the%20update%2C%20you%20simply%20change%20it%20to%20Semi%20annual%20Targeted%20%2B%200%20days%2C%20and%20check%20for%20updates.%20When%20it%20comes%20to%20Win%2010%20Semi%20annual%20updates%2C%20don't%20be%20an%20early%20adapter%20.%20Later%20is%20better%20the%20earlier.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-204075%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-204075%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20to%20confirm%2C%20if%20I%20use%20the%20Media%20Creation%20Tool%2C%20get%20an%20ISO%2C%20burn%20a%20DVD%20and%20run%20the%20setup.exe%20(I%20already%20got%20all%20that)%2C%20this%20will%20just%20UPDATE%20my%20windows%2010%3F%20I'm%20not%20going%20to%20have%20to%20reinstall%20software%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20at%20the%20part%20where%20it%20says%20it%20will%20Install%20Windows%2010%20Pro%2C%20and%20to%20%22keep%20files%20and%20apps%22.%20That's%20basically%20going%20to%20painlessly%20update%20me%20without%20the%20destruction%20of%20some%20sort%20of%20fresh%20install%20type%20thing%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20-%20I%20do%20have%20a%20clone%20backup%20just%20in%20case%2C%20I'd%20rather%20not%20use%20that.%20Thanks%20for%20letting%20me%20know%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUPDATE%3A%20I%20went%20ahead%20and%20did%20it.%20To%20let%20everyone%20know%20this%20was%20a%20X99A%20MSI%20Mpower%20MB%2C%20with%20the%20Intel%20750%20SSD%20NVME%20drive.%20Nine%20months%20of%20pain%20with%20failed%20updates%2C%20many%20dozens%20of%20hours%20wasted%2C%20spending%20oodles%20of%20time%20shutting%20off%20the%20noxious%20Update%20Tool%20Virus%20that%20MS%20puts%20out.%20This%20attempt%20took%20me%20most%20of%20the%20day.%20But%20it%20is%20fixed.%20The%20Media%20Creators%20Tool%2C%20creating%20your%20own%20DVD%20or%20USB%20drive%2C%20then%20just%20running%20the%20setup.exe%20from%20inside%20W10%2C%20and%20using%20the%20%22keep%20files%20and%20apps%22%2C%20is%20just%20like%20an%20update%20and%20actually%20worked%20with%20my%20NVME%20drive.%20All%20my%20apps%20and%20everything%20seem%20to%20be%20fine%20so%20far.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20afraid%20of%20what%20the%20next%20Fall%20Creators%20update%20will%20bring.%20Will%20it%20work%20any%20better%3F%20Thanks%20for%20nothing%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197927%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197927%22%20slang%3D%22en-US%22%3E1.%20AHCI%3CBR%20%2F%3E2.%20No%20WHQL%20setting%20in%20my%20BIOS%3CBR%20%2F%3E3.%20960%20is%20first%20and%20primary%20boot%20device.%3CBR%20%2F%3EPlus%2C%20why%20in%20the%20world%20would%20that%20matter%20in%201803%20and%20not%20in%201709%20%3F%3F%3F%3CBR%20%2F%3EThat%20update%20is%20botched.%20I'm%20not%20the%20only%20one.%20Look%20at%20this%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.windowscentral.com%2Fwindows-10-april-2018-update-common-problems-and-fixes%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.windowscentral.com%2Fwindows-10-april-2018-update-common-problems-and-fixes%3C%2FA%3E.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197885%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197885%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Rodriguez%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20are%20you're%20bios%20configs%3F%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3EIs%20you're%20storage%20set%20to%20AHCI%3F%20IDE%20tends%20to%20have%20problems%20with%20recent%20Windows%20Updates%2C%20pretty%20old%20storage%20driver.%3C%2FLI%3E%3CLI%3EIs%20WHQL%20forced%20on%20your%20MoBo%3F%20Could%20also%20be%20a%20issue%2C%20try%20to%20disable%20it%2C%20if%20enabled.%3C%2FLI%3E%3CLI%3EIs%20you%20960%20set%20as%20first%20and%20primary%20boot%20device%3F%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20me%20it%20almost%20look%20like%20you're%20SSD%20is%20not%20getting%20detected%20as%20Boot%20Device.%20Well%20could%20be%20a%20Windows%20Update%20Problem%20%3AP%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-197661%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-197661%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20Asus%26nbsp%3B%20ROG%20Strix%20Z370-H%20Gaming%20board%20with%20a%20Samsung%20NVMe%26nbsp%3B%26nbsp%3B%26nbsp%3B%20SSD%20960.%3CBR%20%2F%3EUp%20to%20v%201709%20I%20had%20no%20problems.%3CBR%20%2F%3EWhen%20I%20tried%20to%20update%20to%201803%20the%20update%20fails%20with%20different%20errors%20which%20are%20vaguely%20related%20to%20a%20driver%20issue%2C%20according%20to%20thing%20I%20found%20on%20MS%20site.%20There%20was%20no%20way%20to%20find%20out%20which%20driver.%20The%20update%20kept%20re-downloading%20and%20installing.%3CBR%20%2F%3EI%20then%20made%20the%20mistake%20to%20try%20the%20update%20through%20Medi%20creation%20tool.%20That%20resulted%20in%20a%20botched%20install%20that%20tried%20to%20roll%20back%20but%20could%20not%2C%20and%20bricked%20my%20PC.%3CBR%20%2F%3ENext%20I%20tried%20a%20clean%20install%20of%201803.%20This%20kept%20failing%20due%20to%20BSODs.%3CBR%20%2F%3EI%20decided%20to%20go%20back%20to%20a%20clean%201709%20install%2C%20and%20put%20windows%20update%20in%20Semi%20Annual%20Channel%20%2B365%20days.%3CBR%20%2F%3ESince%20then%20%2C%20no%20problems.%3CBR%20%2F%3EA%20month%20later%20%2C%20after%20OS%20Build%2017134.48%20came%20out%2C%20I%20tried%20to%20update%20again%20-%20it%20failed%20again.%3CBR%20%2F%3EI%20dare%20not%20try%20with%20OS%20Build%2017134.81.%3CBR%20%2F%3EA%20second%20computer%20I%20tried%20this%20update%20on%20is%20an%20HP%20Probook%20440%20G5%20%2C%20which%20has%20an%20Intel%20Pro%206000p.%20This%20was%20an%20update%20from%201703.%20It%20updated%20without%20a%20problem%2C%20but%20since%20then%20had%20an%20assortment%20of%20BSODs%2C%20mostly%20%22critical%20process%20died%22.%3CBR%20%2F%3ETo%20make%20things%20worse%2C%20the%20OS%20does%20not%20create%20any%20dump%20files%20to%20analyze.%3CBR%20%2F%3EI%20called%20HP%20support%20who%20kindly%20sent%20me%20to%20Microsoft%20to%20work%20it%20out%20with%20them.%20Yeah%2C%20right.%3CBR%20%2F%3EI%20did%20a%20factory%20reset%20to%201703%20(took%20over%202%20hours)%20and%20upgraded%20to%201709.%20So%20far%2C%20no%20BSODs.%3CBR%20%2F%3EThe%20intel%20ssd%20is%20mentioned%20in%20the%20incompatibility%20list%20of%20the%20first%201803%20versions.%20But%20the%20MS%20description%20of%20the%20errors%20is%20quite%20different%20then%20what%20I%20had%3A%3CBR%20%2F%3E%22When%20attempting%20to%20upgrade%20to%20the%20Window%2010%20April%202018%20Update%2C%20select%20devices%20with%20Intel%20SSD%20600p%20Series%20or%20Intel%20SSD%20Pro%206000p%20Series%20may%20repeatedly%20enter%20a%20UEFI%20screen%20after%20restart%20or%20stop%20working.%22%3C%2FP%3E%3CP%3EMy%20conclusion%20is%20that%20MS%20completely%20screwed%20this%20update.%3CBR%20%2F%3EI%20know%20quite%20a%20few%20people%20who's%20PC%20was%20bricked%20by%20the%20automatic%20update.%20Some%20have%20Win%2010%20Home%2C%20so%20they%20cannot%20delay%20this%20update.%3CBR%20%2F%3EI%20would%20not%20be%20surprised%20if%20a%20large%20class%20action%20lawsuit%20is%20opened%20against%20MS.%3CBR%20%2F%3EIn%20my%20business%20we%20have%2020%20PCs%20with%20WIn%2010%201709.%20If%20they%20were%20bricked%20we%20would%20suffer%20significant%20financial%20and%20reputation%20damage.%20Luckily%20all%20our%20PCs%20are%20set%20to%20Semi%20Annual%20Channel%20%2B365%20days.%2C%20and%20I%20hope%20none%20will%20get%20this%20update.%3CBR%20%2F%3EI%20think%20if%20you%20have%20an%20ssd%20machine%2C%20you%20should%20avoid%20this%20update%20for%20now.%20Don't%20trust%20MS%20on%20this%20update.%20You%20might%20suffer%20significant%20damage.%20If%20you%20can%2C%20back%20your%20computer%20with%20an%20imaging%20program%20such%20as%20Acronis%20TI%20.%20This%20is%20the%20fastest%20way%20to%20get%20back%20up%20should%20this%20update%20brick%20your%20PC.%3CBR%20%2F%3EAbsurdly%2C%20if%20you%20have%20an%20old%20PC%20with%20HDD%20you%20are%20probably%20safe%2C%20at%20least%20from%20the%20few%20PCs%20I%20updated.%3CBR%20%2F%3EUnbelievable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-194228%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-194228%22%20slang%3D%22en-US%22%3EI%20also%20have%20sm951%20and%20i've%20been%20having%20issues%20since%20saturday.%20at%20first%20i%20wasn't%20sure%20if%20it%20was%20related%20to%20update%201803%20but%20i'm%20starting%20to%20think%20it%20is.%20looks%20like%20i%20have%20to%20fresh%20install%20%3A(%3CBR%20%2F%3Ei%20hope%20that%20solves%20the%20problem%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-194072%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-194072%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20latest%20version%20of%20Win10%20has%20worked%20perfectly%20for%20me%2C%20but%20clearly%20hasn't%20for%20everyone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20suggest%20telephoning%20MS%20Support%20and%20complaining%20and%20have%20them%20log%20and%20escalate%20the%20issue%20and%20your%20hardware.%26nbsp%3B%20It%20won't%20fixed%20unless%20they%20know%20about%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-193997%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-193997%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFinaly%20I%20had%20some%20spare%20time%20to%20have%20a%20look%20at%20the%201803%20build%2C%20sorry%20for%20delay..........%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20my%20case%20I%20gave%20up%20trying%20to%20upgrade%20to%201709.%20But%20I've%20gone%20from%201703%20to%201803%20by%20doing%20the%20following%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Use%20media%20creation%20tool%20to%20download%20ISO%20of%201803%3C%2FP%3E%3CP%3E2.%20Unpacked%20ISO%20of%201803%20to%20folder%20with%20Winrar%20-%20Yep%20You%20can%20call%20it%20old-fashioned%2C%20but%20I%20works%20%3A)%3C%2FP%3E%3CP%3E3.%20Ran%20setup%3C%2FP%3E%3CP%3E4.%20Follow%20guides%20and%20wait%3C%2FP%3E%3CP%3E5.%20IT%20WORKS!!!!%20Or%20at%20least%20it%20makes%20the%20upgrade.%20Really%20haven't%20testet%20much%20yet%20%3A)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20HW%3A%20Intel%20E5-1630V3%2C%20MSI%20Raider%20X99A%26nbsp%3Band%26nbsp%3BSamsung%20960%20Evo%20NVME.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20reports%20are%20now%2C%20that%20people%20with%20Intel%20and%20Toshiba%20SSDs%20have%20problems%20with%201803.....%20Even%20Microsoft's%20own%20Surface%20has%20problems%20%3A)%20So%20a%20fix%20for%20that%20will%20properly%20be%20out%20much%20faster%2C%20than%20the%201803%20was%20for%20all%20of%20us%20with%20non%20Microsoft%20hardware.......%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWell%20lets%20hope%20Microsoft%20remembers%20what%20they%20did%20in%20build%201803%20to%20get%20the%20NVME%20disks%20to%20work%2C%20and%20implements%20it%20in%20next%20build%2C%20so%20we%20don't%20have%20to%20start%20all%20over%20again.%20Still%2C%20If%20anyone%20stumbles%20on%20info%20what%20the%20exact%20fix%20was%2C%20please%20post.%20I%20wasn't%20able%20to%20find%20fix%20list%20on%201803%20regarding%20this%20problem%20%3A(%20Someone%20know%20how%20Asus%20fixed%20the%20problem%20with%20BIOS%20update%3F%20(Shame%20on%20You%20MSI....)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20Regards%3C%2FP%3E%3CP%3EKim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-193616%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-193616%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20got%20the%20same%20problem.%20I%20have%20a%20Samsung%20960%20Evo%20as%20the%20system%20disk.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20could%20not%20follow%20new%20Technologies%2C%20I%20guess.%20They%20still%20could%20not%20fix%20the%20installation%20problem%20for%20all%20the%20creator%20updates%20on%20NWME%20drives.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20every%20method%20for%201709%20creator%20update.%20I%20only%20managed%20to%20install%201709%20with%20a%20clean%20install.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20really%20fed%20up%20with%20not%20closing%20the%20updates%20properly%20and%20do%20a%20clean%20install%20everytime%20Microsoft%20decides%20to%20release%20a%20new%20creator%20update.%20Last%20time%20I%20had%20to%20install%20every%20software%20again%2C%20it%20was%20really%20annoying%2C%20even%20if%20the%20Windows%20keeps%20the%20old%20files.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToday%20again%2C%20Windows%20tried%20to%20update%20to%20the%20new%20creator%20update%2C%201803%2C%20and%20failed%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20really%20disappointing%20to%20see%20the%20same%20issue%20on%201709%20is%20still%20going%20on%2C%20it's%20been%20more%20than%20a%20year.%20I%20guess%20they%20are%20waiting%20for%20Windows%2011%20to%20fix.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20find%20a%20good%20solution%20except%20than%20clean%20install%2C%20I'd%20really%20like%20to%20hear.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191580%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191580%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20is%20terrible.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMine%20is%3A%3C%2FP%3E%3CP%3EMSI%20X99A%20Godlike%20Gaming%20Carbon%20INTEL%20X99%20Chipset%3C%2FP%3E%3CP%3E512GB%20Samsung%20SM951%20M.2%20PCIe%20NVMe%20SSD%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20ISO%20upgrade%20worked%20flawlessly%2C%20and%20the%20PC%20has%20been%20100%25%20stable%20since%20then.%26nbsp%3B%20Obviously%20no%20updates%20since%20then%2C%20or%20forced%20restarts%20etc.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191399%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191399%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wish%20it%20was%20all%20resolved%20for%20myself...%3C%2FP%3E%3CP%3ERunning%20the%20upgrade%20from%20an%201803%20ISO%20does%20not%20work%20on%20my%20rig.%3C%2FP%3E%3CP%3ETried%20several%20other%20methods%20as%20well%20and%20the%20usual%20simple%20troubleshooting%20steps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMobo%3A%26nbsp%3B%20MSI%20Godlike%20Gaming%20Carbon%20(X99A)%3C%2FP%3E%3CP%3ENVMe%3A%26nbsp%3B%20Samsung%20950%20Pro%20256Gb%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20thread%20%3CA%20href%3D%22https%3A%2F%2Fanswers.microsoft.com%2Fen-us%2Fwindows%2Fforum%2Fwindows_10-update%2Fwindows-10-1709-fails-to-update-to-april-feature%2Fbc637d71-5511-4715-a3ff-339e94fa7055%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20to%20do%20with%20not%20being%20able%20to%20upgrade%20to%201803.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191396%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191396%22%20slang%3D%22en-US%22%3E%3CP%3EI%20used%20the%20online%20installer%20to%20get%20from%201703%20to%201803%20on%20my%20MSI%20X99A%20and%20Samsung%20960%26nbsp%3BEVO%20NVME%20setup%20and%20it%20updated%20(as%20far%20as%20I%20can%20tell)%20OK.%20Hopefully%20there%20will%20be%20no%20repeat%20of%20this%20fiasco%20in%20the%20future%20and%20that%201803%20doesn't%20fall%20over%20in%20the%20next%20couple%20of%20days!!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20luck%20to%20all%20you%20who%20have%20the%20update%20left%20to%20do%2C%20but%20it%20does%20seem%20to%20work.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190163%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190163%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20here%20%3A)%20%26nbsp%3B%20Finally!!!%26nbsp%3B%20MS%20should%20be%20ashamed%20it%20took%20them%20about%209%20months%20to%20fix%20this%20mess.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDownloaded%20the%20ISO%2C%20burned%20to%20disc.%26nbsp%3B%20Then%20installed%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWorked%20flawlessly%20without%20any%20problems.%26nbsp%3B%20Install%20took%20about%2030%20mins.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189878%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189878%22%20slang%3D%22en-US%22%3EJust%20wanted%20to%20add%20that%20the%20update%20worked.%20Downloaded%20the%20iso%20for%201803%20and%20my%20issues%20are%20solved.%20Took%206%20months.%20But%20glad%20to%20be%20back%20to%20normal.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189834%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189834%22%20slang%3D%22en-US%22%3E%3CP%3EI%20didn't%20have%20to%20download%20an%20ISO.%20I%20used%20the%20%22update%20now%22%20button%20on%20this%20link%20instead%20to%20get%20the%201803%20update%20(searching%20for%20updates%20in%20windows%20didnt%20find%20it)%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2Fwindows10%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2Fwindows10%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189713%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189713%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20check%20the%20ISO%20with%20this%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fwww.winhelponline.com%2Fblog%2Fiso-find-windows-build-version-edition-using-dism%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.winhelponline.com%2Fblog%2Fiso-find-windows-build-version-edition-using-dism%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20downloaded%20yesterday%20(danish%20version)%2C%20and%20thats%201803.%20Will%20try%20to%20install%20in%20WE%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKR%3C%2FP%3E%3CP%3EKim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-189685%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-189685%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20no%20luck%20for%20me%2C%20but%20perhaps%20the%20Windows%20Update%20is%20still%20downloading%20the%20old%20version%20for%20me%20perhaps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20whether%20the%20Update%20Tool%2C%20ISO%20download%20is%20now%20the%20latest%20version%3F%26nbsp%3B%20If%20it%20is%2C%20I%20was%20planning%20to%20upgrade%20using%20that.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-188749%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188749%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20finaly%20able%20to%20update%20from%201609%20to%201803%20without%20problems.%20Only%20took%20about%20a%20year%20to%20fix%20and%20last%203%20weeks%20my%20version%20wasn't%20supported%20anymore.%20Fantastic%20customer%20support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-188193%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-188193%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20confirm%20that%20installing%20the%20Windows%20Insider%20version%20helped%20me%20as%20well%20to%20update%20from%201703%20to%201803.%20All%20other%20proposed%20fixes%20did%20not%20help%20to%20escape%20the%20daily%20(!)%20update%20attempt.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20this%20hint%2Fidea!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-186530%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-186530%22%20slang%3D%22en-US%22%3EVersion%201803%20appeared%20in%20Windows%20Update%20yesterday.%20Sadly%20it%20failed%20to%20install%20(with%20three%20attempts).%20I%20will%20stick%20with%201703%20until%20I%20eventually%20find%20a%20spare%20day%20or%20two%20to%20reinstall%20and%20reinstate%20my%20current%20setup.%20Until%20then%20I%20will%20disable%20upgrades%20(as%20per%201709).%3CBR%20%2F%3E%3CBR%20%2F%3EIntel%20Core%20i7-7820X%2C%20Gigabyte%20GA-X299-UD4%20M%2FB%2C%20500GB%20Samsung%20960%20EVO%20M.2%20PCIe%20SSD.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-185684%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-185684%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112406%22%20target%3D%22_blank%22%3E%40Constantino%20Grau%20Turuelo%3C%2FA%3E.%20I%20did%20as%20you%20explained.%20Subscribed%20to%20the%20Windows%20Insider%20Program%2C%20downloaded%2C%20mounted%20and%20launched%20the%20setup%20of%20the%20windows%2017127%20build%20iso%20and%20now%20I'm%20successfully%20running%20on%20windows%201803.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20windows%201709%20perpetual%20update%20fail%20restart%20nightmare%20is%20over!%20I%20don't%20thank%20you%20microsoft%2C%20because%20it%20was%20five%20month%20of%20disastrous%20experience%20with%20your%20OS.%3C%2FP%3E%3CDIV%20class%3D%22post-author-login%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-185351%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-185351%22%20slang%3D%22en-US%22%3EAfter%20doing%20what%20I%20explained%20up%20there%2C%20no%20problems%20so%20far.%3CBR%20%2F%3E%3CBR%20%2F%3EGreetings%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-185346%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-185346%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20should%20have%20been%20launched%20start%20April%2C%20but%20there%20was%20some%20problems%20with%20performance%20%2B%20BSOD%20(according%20to%20MS)%2C%20so%20its%20unfortunately%20delayed%20for%20an%20unknown%20amount%20of%20time%20%3A(%20I%20think%20You%20should%20be%20a%20member%20of%20the%20Windows%20Insider%20program%20to%20get%20the%20build%20as%20it%20is%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20about%20You%20guys%20that%20run%201803%2C%20have%20You%20exp.%20performance%20problems%20or%20BSODs%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKR%3C%2FP%3E%3CP%3EKim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-185266%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-185266%22%20slang%3D%22en-US%22%3E%3CP%3EWhere%20i%20can%20get%201803%20version%3F%20AFAIK%20its%20not%20released%20officially%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183526%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183526%22%20slang%3D%22en-US%22%3EI%20skip%20the%20version%201709.%20I%20have%20upgraded%20my%20system%20from%201703%20to%201803.%20Worked%20for%20me.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183507%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183507%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20reinstalled%20my%20computer%20from%20scratch%2C%20with%20W10%201709%20iso.%20My%20data%20are%20on%20other%20disk%2C%20so%20I%20don't%20waste%20my%20time%20to%20backup%20everything%2C%20i've%20just%20reinstalled%20drivers%20and%20software.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20hope%20the%20next%20update%20won't%20be%20a%20new%20problem%20with%20NVMe%20SSD.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-183052%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-183052%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20the%20same%20problem.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20setup%20%3A%20MSI%20X99A%20GAMING%207%20with%20Samsung%20960%20EVO%20250Gb.%3CBR%20%2F%3E%3CBR%20%2F%3EDo%20you%20think%20I%20could%20upgrade%20windows%2010%20on%20my%20computer%20with%20the%20last%20ISO%20of%20windows%2010%20(with%201709%20update).%3CBR%20%2F%3E%3CBR%20%2F%3EI%20saw%20on%20this%20forum%2C%20people%20has%20cloned%20their%20NVMe%20on%20a%20ssd%20disk%2C%20made%20the%20upgrade%20on%20ssd%20and%20clone%20back%20the%20ssd%20to%20nvme.%20Apparently%2C%20it%20works...%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20is%20the%20best%20method%20to%20correct%20this%20issue%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178725%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178725%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20the%20useful%20info.%20I'll%20be%20waiting%20for%20the%20new%20build%20from%20MS%2C%20and%20when%20its%20there%2C%20I'll%20post%20results%20here.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EKind%20Regards%3C%2FP%3E%0A%3CP%3EKim%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178549%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178549%22%20slang%3D%22en-US%22%3EThank%20you%20very%20much%20for%20the%20clarification%20and%20for%20restoring%20the%20initial%20post%20%3AD.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20was%20really%20wondering%20what%20I%20did%20wrong.%3CBR%20%2F%3E%3CBR%20%2F%3EGreetings%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178545%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178545%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20an%20automated%20spam%20filter%2C%20so%20sometimes%20messages%20get%20marked%20that%20aren't%20actually%20spam.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOur%20team%20manually%20goes%20through%20every%20weekday%20and%20moves%20messages%20out%20of%20the%20spam%20filter%20that%20don't%20belong.%20Sorry%20for%20the%20inconvenience.%20(I%20did%20delete%20the%20duplicate%20message%20since%20it%20was%20a%20re-post%2C%20but%20your%20original%20post%20is%20there.)%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178404%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178404%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Constantino%2C%20thanks%20for%20your%20posts%20%3A).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETried%20it%20out%20with%20the%20Insider%20ISO%20and%20the%20upgrade%20really%20worked.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20first%20time%20I%20tried%20it%20with%20a%20mounted%20USB%20I%20got%20a%20BSOD.%3C%2FP%3E%0A%3CP%3EAfter%20that%20I%20mounted%26nbsp%3Bthe%20Image%20with%20CloneDrive%20directly%20on%20my%20PC%20and%20ran%20the%20Upgrade.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20that%20the%20Upgrade%20worked%20without%20a%20Problem.%20So%20the%20next%20Update%20(1803)%20should%20adress%20the%20X99%20%2B%20NVME%20SSD%20Upgrade%20Problem.%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20anybody%20who%20wants%20to%20download%20the%20Insider%20Image%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.deskmodder.de%2Fblog%2F2018%2F03%2F28%2F17133-iso-esd-deutsch-english%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDeskmodder%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178369%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178369%22%20slang%3D%22en-US%22%3EMy%202%20posts%20with%20the%20solution%20were%20reported%20as%20spam...%3CBR%20%2F%3E%3CBR%20%2F%3EI%20wrote%20it%20also%20on%20the%20msi-forum%2C%20so%20you%20can%20check%20this%20out%20there%20(the%20link%20was%20posted%20by%20another%20mate%20above).%3CBR%20%2F%3E%3CBR%20%2F%3EGreetings%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178359%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178359%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20was%20the%20last%20message%20here%20deleted%3F%26nbsp%3B%20It%20suggested%20a%20fix%20in%20the%20next%20Windows%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft%2C%20you%20really%20are%20beyond%20contempt.%26nbsp%3B%20Look%20up%20the%20word%20%22COMMUNICATION%22.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENo%20wonder%20Apple%20is%20beating%20you%20in%20many%20markets.%26nbsp%3B%20No%20wonder%20Sony%20and%20Nintendo%20have%20beaten%20you%20into%20the%20ground%20in%20the%20console%20market%20(globally).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIncompetent%20company!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178355%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178355%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20guys%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20great%20news.%20It%20looks%20like%20that%20the%20new%20Spring%20Creators%20Update%20will%20solve%20our%20problems.%20I%20am%20right%20now%20with%20that%20distribution%20(updated%20from%20the%20anniversary%20update)%20working%20without%20any%20problems%20and%20after%20avoiding%20the%20BSOD%20while%20updating.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECredits%20to%20the%20user%20%22msi%22%20from%20the%20msi%20forum%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fforum-en.msi.com%2Findex.php%3Ftopic%3D301785.0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fforum-en.msi.com%2Findex.php%3Ftopic%3D301785.0%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20copy%2Fpaste%20from%20his%20thread%20(links%20at%20the%20msi%20forum%20post)%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%22I%20found%20a%20solution%20for%20this%20struggle%20I%20had%20the%20last%208%20month!!%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EI%20just%20tried%20everythind%20but%20a%20clean%20install.%20So%20now%20I%20thought%20about%20not%20installing%201709%2C%20but%201803%20which%20was%20released%20as%20final%20some%20days%20ago.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EWith%20this%20trick%20I%20got%20my%20PC%20on%20WIN%2010%201803%3A%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3E-Download%20ISO%20File%3A%26nbsp%3B%3CA%20class%3D%22bbc_link%22%20href%3D%22https%3A%2F%2Fwww.deskmodder.de%2Fblog%2F2018%2F03%2F28%2F17133-iso-esd-deutsch-english%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDeskmodder%3C%2FA%3E%26nbsp%3BI%20used%20the%20x64%20german%20file%2C%20but%20most%20of%20you%20might%20need%20the%20english%20one.%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E-Download%20ISO%20to%20bootable%20USB%20tool%26nbsp%3B%3CA%20class%3D%22bbc_link%22%20href%3D%22https%3A%2F%2Funetbootin.github.io%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eunetbootin%3C%2FA%3E%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E-Create%20a%20flashdrive%20with%20latest%20ISO%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E-Restart%20PC%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E-Navigate%20in%20explorer%2C%20open%20setup.exe%20on%20USB%20medium%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E-Choose%20install%20and%20keep%20data%2Fsettings%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3EThe%20installation%20process%20starts%20and%20keeps%20up%20-%20no%20error%20after%20reboot!%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EI%20don't%20know%20if%20MS%20did%20any%20changes%20with%20this%20new%20function%20update%2C%20but%20main%20thing%20is%20that%20it%20works%20like%20charm!%22%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EFrom%20my%20side%20I%20have%20also%20a%20small%20contribution.%20You%20should%20install%20the%20package%20which%20has%20your%20language%2C%20otherwise%20you%20will%20not%20be%20able%20to%20upgrade%20without%20losing%20your%20apps%2Fprograms%20due%20to%20language%20incompatibility.%20That%20was%20my%20case.%20I%20could%20not%20find%20.iso%20files%20for%20my%20language%2C%20only%20RU%2C%20EN%2C%20and%20DE.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EMy%20solution%20was%20to%20register%20as%20insider%20and%20to%20download%20the%20last%20iso%20available%20directly%20from%20microsoft%20(%3CU%3Ethe%20page%20only%20works%20with%20edge!!!%3C%2FU%3E)%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2Fwindowsinsiderpreviewiso%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2Fwindowsinsiderpreviewiso%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EProbably%20you%20can%20download%20that%20withouth%20being%20insider%2C%20but%20I%20did%20it%20after%20registering%20so%20I%20do%20not%20know%20if%20that%20is%20a%20prerequisite%20or%20not.%20Right%20now%20the%20most%20updated%20version%20was%20the%20build%2017127.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAfter%20choosing%20the%20last%20build%20and%20my%20language%2C%20the%20iso%20file%20was%20downloaded%2C%20I%20mounted%20it%20(you%20have%20that%20option%20built%20in%20windows)%20and%20then%20I%20did%20the%20install%20directly%20from%20the%20setup.exe%20as%20usual%20(it%20is%20not%20necessary%20to%20use%20an%20usb%20stick).%20Everything%20went%20smoothly%20and%20my%20windows%20was%20updated%20without%20any%20BSOD%20and%20I%20do%20not%20get%20the%20annoying%20forced%20updates%20anymore.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAs%20a%20suggestion%2C%20after%20updating%20to%20the%20build%2017127%2C%20I%20recommend%20to%20look%20for%20updates%20and%20update%20to%20the%20build%2017133%20(Windows%201803)%20as%20that%20will%20be%20the%20final%20public%20version%20for%20the%20Spring%20Creators%20Update.%20I%20did%20that%20and%20then%20I%20left%20the%20windows%20insider%20option%20so%20that%20I%20do%20not%20get%20more%20updates%20from%20that%20source%2C%20only%20from%20public%20releases.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20guess%20that%20it%20will%20be%20possible%20to%20get%20the%20update%20through%20the%20windows%20update%20soon%20(in%2010%20days%20or%20so)%20but%20they%20are%2010%20days%20of%20getting%20again%20the%20annoying%20update%20messages%2C%20reboots%20and%20dealing%20with%20the%20update%20orchestrator.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EPlease%2C%20if%20it%20works%20for%20you%2C%20post%20it%20here%2C%20so%20that%20we%20know%20it%20is%20working.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EGreetings%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178085%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178085%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20to%20BLOCK%20EVERYTHING%20Upgrade%2FUpdate%20-related%20with%20my%20firewall%20(even%20kill%20processes)%2C%20gone%20to%20scheduler%20and%20deactivated%20everything%20there%20is%20related%20to%20the%20update%20mechanisms%20AND%20STILL%20IT%20WILL%20TRY%20TO%20UPGRADE!!!%20i'm%20gettin%20really%20annoyed%20by%20this!%3C%2FP%3E%0A%3CP%3EPLEASE%20MAKE%20IT%20STOP!!!!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMy%20System%3C%2FP%3E%0A%3CP%3EMSI%20x99a%20Gaming%209%20ACK%3C%2FP%3E%0A%3CP%3ESamsung%20960%20Pro%20M.2%202280%20NVMe%20512GB%3C%2FP%3E%0A%3CP%3EOBVIOUSELY%20Windows%2010%20%3A(%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-1815243911%22%20id%3D%22toc-hId-1904971495%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F31297i536BB37028C73549%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Thank%20you%20microsoft.png%22%20title%3D%22Thank%20you%20microsoft.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FH1%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177941%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177941%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%2C%20YOU%20are%20a%20bunch%20of%20incompetent%20half-wits.%26nbsp%3B%20What%20does%20it%20take%20to%20communicate%20with%20your%20CUSTOMERS%20on%20this%20issue%3F%20%26nbsp%3B%20No%20fix%2C%20repeated%20restarts%2C%20lost%20work.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMoronic%20incompetent%20idiots!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20finally%20had%20enough!!!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-177695%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-177695%22%20slang%3D%22en-US%22%3ESame%20problem%20on%20new%20HP%20Omen%20laptop%20with%20PM961%20Samsung%20NVME%20SSD.%3CBR%20%2F%3EI've%20found%20that%20there%20is%20a%20problem%20with%20power%20management%20in%20Win10%20and%20NVME%20SSD.%3CBR%20%2F%3EIf%20the%20PCI%20Express%20option%20Link%20State%20Power%20Management%20in%20powerplan%20is%20selected%20to%20Maximun%20powersafe%20-%20the%20NVME%20SSD%20slept%20and%20laptop%20have%20BSOD%20with%20CRITICAL%20PROCESS%20DIED.%20SSD%20not%20available%20until%20shutdown%20and%20power%20on.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176723%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176723%22%20slang%3D%22en-US%22%3E%3CP%3EAll%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20struggled%20with%20this%20issue%20myself.%20Owning%20an%20MSI%20SLI%20X99%20board%20I%20had%20a%20black%20screen%20after%201709.%20I%20had%20installed%20a%20new%20hard%20drive%20a%20while%20back%20and%20changed%20the%20Sata%20port.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20my%2015th%20attempt%20it%20worked.%20So%20suggest%20unplugging%20all%20hard%20drives%20except%20boot%20to%20see%20if%20that%20resolves%20your%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175566%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175566%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9_UCyiJaH0Q%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D9_UCyiJaH0Q%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20tried%20other%20ways%20to%20disable%20the%20Windows%20Update%20assistant.%26nbsp%3B%20This%20video%20was%20helpful.%26nbsp%3B%20Does%20not%20fix%20the%20issue%2C%20but%20I%20am%20hoping%20will%20keep%20my%20computer%20from%20rebooting%20several%20times%20a%20day.%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20it%20helps%3C%2FBLOCKQUOTE%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175356%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175356%22%20slang%3D%22en-US%22%3E%3CP%3EI%20too%20feel%20EXTREMELY%20ANGRY%20at%20the%20appalling%20support%20from%20MS.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENo%20fix%2C%20no%20temporary%20reprieve%20from%20repeated%20failed%20updates%2C%20and%20no%20communication%20on%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175184%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175184%22%20slang%3D%22en-US%22%3EDude%20WTF%3F%20You%20copied%20my%20Rant%20to%20the%20MSI%20Forum%20xD%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175171%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175171%22%20slang%3D%22en-US%22%3E%3CP%3EI%20started%20a%20thread%20on%20the%20MSI%20Forum%20since%20this%20is%20getting%20pretty%20bad...Windows%20is%20warning%20me%20every%20day%20and%20reboots%20when%20I%20am%20away%20for%20more%20than%2030%20minutes%2C%20so%20i%20lose%20open%20files%20sometimes.%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fforum-en.msi.com%2Findex.php%3Ftopic%3D301785.0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fforum-en.msi.com%2Findex.php%3Ftopic%3D301785.0%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175036%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175036%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wish%20Windows%20was%20Open%20Source.%20Then%20bugs%20like%20this%20could%20be%20fixed%20by%20the%20community%20in%20days%20or%20a%20week.%3CBR%20%2F%3EI%20would%20switched%20since%20long%20to%20Linux%2C%20if%20the%20Driver-%20and%20Apps-Compatibility%20would%20be%20like%20on%26nbsp%3BWindows.%3CBR%20%2F%3E%3CBR%20%2F%3EMSI%20and%20ASUS%20is%20already%20dead%20for%20me.%20Foxconn%20does%20the%20Production%2C%20and%20they%20do%20**bleep**%20all%20the%20times.%3CBR%20%2F%3EOn%20my%20next%20PC%20I%20will%20go%20to%20ASRock%2C%20much%20better%20Support...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft%20please%2C%20fix%20this%20already!%20I%20will%20be%20really%20angry%20if%20it%20was%20just%20a%20Boot%20File%20Size%20limit!%3C%2FP%3E%0A%3CP%3EThat%20would%20be%20a%205%20minute%20job!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-175025%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-175025%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20out.%20Bought%20a%20new%20motherboard%20from%20ASRock%20as%20MSI%20doesn't%20care%20about%20their%20customers.%20Worked%20out%20of%20the%20box%20with%20the%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20sorry%20for%20all%20others%20that%20are%20faced%20with%20this%20problem.%20I'll%20never%20buy%20a%20MSI%20product%20again...%20this%20is%20just%20ridiculous%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174799%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174799%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%20in%20case%20anyone%20is%20listening%3A%3C%2FP%3E%0A%3CP%3E1.%20Microsoft%20is%20giving%20a%20boot%20up%20message%20that%20this%20version%20of%20Windows%2010%20-%201607%20is%20no%20longer%20supported%20in%20April.%3C%2FP%3E%0A%3CP%3E2.%20Still%20can't%20stop%20the%20Windows%20Upgrade%20Assistant-%26nbsp%3B%20I%20have%20modified%20the%20registry%20according%20to%20directions%20multiple%20times.%26nbsp%3B%20If%20I%20uninstall%20it%2C%20it%20comes%20back%20minutes%20later.%26nbsp%3B%20Its%20a%20virus%20that%20can't%20be%20removed.%3C%2FP%3E%0A%3CP%3E3.%20I%20have%20downloaded%20the%20ISO%20on%20the%20new%20Windows%2010%20version%20and%20done%20the%20upgrade%20from%20there.%26nbsp%3B%20It%20goes%20through%20a%20long%20time%20upgrading%2C%20then%20Dies.%26nbsp%3B%20Have%20done%20this%20at%20least%203%20times...probably%20more.%3C%2FP%3E%0A%3CP%3E4.%20About%20every%20other%20failure%20to%20upgrade%20leaves%20my%20machine's%20programs%20unable%20to%20launch%2C%20except%20in%20Administrator%20mode.%26nbsp%3B%20%26nbsp%3BTook%20a%20while%20to%20figure%20that%20out...%20Its%20a%20hassle%2C%20but%20in%20some%20cases%20things%20do%20not%20work.%26nbsp%3B%20Microsoft%20Outlook%20for%20instance%20can%20not%20search%20in%20admin%20mode.%26nbsp%3B%20I%20use%20this%20constantly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThings%20I%20am%20afraid%20to%20try%3A%3C%2FP%3E%0A%3CP%3ESince%20this%20leaves%20my%20machine%20potentially%20unusable%20with%20the%20blue%20screen%20of%20death%2C%20so%20far%20I%20am%20able%20to%20boot%20using%20and%20alternative%20and%20continue.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20Doing%20a%20clean%20install%20is%20worrisome.%26nbsp%3B%20Seems%20like%20a%20good%20possibility%20that%20the%20machine%20will%20not%20recognize%20the%20drives%20and%20never%20boot.%3C%2FP%3E%0A%3CP%3E2.%20Booting%20from%20a%20USB%20drive%20to%20upgrade%20-%20I%20worry%20about%20the%20same%20outcome.%3C%2FP%3E%0A%3CP%3E3.%20Some%20have%20suggested%20using%20a%20non-SSD%20drive%20to%20boot%20from...Clone%20a%20drive%2C%20etc...So%20I%20am%20supposed%20to%20order%20and%20install%20a%20new%20drive%20just%20to%20test%20this%3F%3F%3F%26nbsp%3B%20%26nbsp%3B%20Figure%20out%20how%20to%20clone%20a%20drive%20etc...%26nbsp%3B%20I%20am%20experienced%2C%20but%20its%20not%20something%20I%20am%20set%20up%20to%20do.%3C%2FP%3E%0A%3CP%3E4.%20Reinstalling%20all%20my%20programs%20is%20VERY%20time%20consuming.%26nbsp%3B%20Some%20are%20saying%20hours%2C%20but%20by%20the%20time%20I%20get%20at%20the%20setting%20back%20to%20what%20I%20like%2C%20it%20takes%20me%20days.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20appealing%20to%20MSI%20and%20Mcrosoft%20-%20What's%20the%20answer%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-174161%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-174161%22%20slang%3D%22en-US%22%3E%3CP%3ETruly%20appalling%20communications%2C%20service%20and%20patches%20from%20Microsoft!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173148%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173148%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EMicrosoft%20is%20uninteriseted%26nbsp%3B%20for%20user%20which%20have%20problems%20with%20Windows%2010.%3C%2FP%3E%0A%3CP%3EThis%20is%20the%20%22lesson%20learned%22.%20You%20can%20be%20sure%2C%20I%20do%20not%20make%20any%20kind%20sentence%20about%20MS%20in%20future.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173077%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173077%22%20slang%3D%22en-US%22%3ENothing%20work.%20I%20tried%20a%20new%20bios%20from%20msi.%20Hg3%20bios%20and%20it%20dont%20work.%20%3CBR%20%2F%3E%3CBR%20%2F%3EMS%20you%20have%20no%20fix%20for%20this%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-173023%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-173023%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here.%26nbsp%3B%20Have%20rebooted%20at%20least%203x%20a%20day%20for%20months.%26nbsp%3B%20%26nbsp%3BCan%3Bt%20stop%20reboots.%26nbsp%3B%20Cant%20fix%20it.%26nbsp%3B%20Have%20tried%20everything%20except%20clean%20install.%26nbsp%3B%20Just%20posting%20so%20i%20get%20notified%20if%20and%20when%20a%20fix%20is%20made.%26nbsp%3B%20%26nbsp%3BMSI%20X99a%20Godlike%20Carbon%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-172787%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-172787%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%20here.%20This%20has%20been%20going%20on%20for%20at%20least%20half%20a%20year%20or%20longer%20and%20now%20i%20even%20get%20a%20warning%20that%20my%20current%20win%2010%20version%20(1607)%20will%20not%20be%20supported%20anymore%20come%20april.%20This%20is%20completely%20unacceptable.%20A%20fix%20has%20been%20promised%20for%20months%20and%20months.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMSI%20X99a%20gaming%20pro%20carbon%3C%2FP%3E%0A%3CP%3Esamsung%20evo%20960%20evo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170777%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170777%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20have%20the%20same%20problem.%20The%20Update%20ends%20with%20BS%20and%20EC%200xc00000bb.%3C%2FP%3E%0A%3CP%3EMy%20System%20is%20MSIX99%20Gaming%20pro%20Carbon%207E20%3C%2FP%3E%0A%3CP%3EI7%206800K%20with%2032%20GB%20Ram%3C%2FP%3E%0A%3CP%3EMSI%201070%20Gaming%20and%20Samsung%20NVME%20960%20Evo%20500GB%3C%2FP%3E%0A%3CP%3EWIN%2010%20Pro%2064bit%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-170092%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-170092%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJust%20experienced%20the%20same%20problem%2C%20I'm%20running%201703%2C%20and%20had%20no%20problems.%20Changed%20Updates%20to%20Company%20under%20advanced%20settings%20for%20updates%2C%20and%20set%20that%20function%20updates%20should%20be%20delayed%20for%20365%20days%2C%20hope%20this%20keeps%201709%20from%20trying%20to%20install%20all%20the%20time.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20running%20on%20MSI%20X99A%20Raider%20w%2F%20Samsung%20960%20Evo%20NVME.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20reading%20in%20this%20forum%2C%20it%20unfortunately%20doesn't%20seem%20that%20Microsoft%20cares%20a%20lot%20of%20their%20customers%20%3A(%20If%20engineers%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F41501%22%20target%3D%22_blank%22%3E%40microsoft%3C%2FA%3E%20can't%20seem%20to%20fix%20the%20problem%20in%20in%20half%20a%20year%2C%20can%20we%20be%20sure%20that%20it%20will%20be%20fixed%20ever%3F%3C%2FP%3E%0A%3CP%3EDear%20Microsoft%2C%20When%20You're%20aware%20that%20quite%20a%20bunch%20of%20people%20are%20experiencing%20problems%2C%20then%20at%26nbsp%3Bleast%20make%20a%20tool%20that%20delays%20the%20function%20updates%2C%20until%20a%20fix%20for%20the%26nbsp%3Bproblem(s)%20is%20at%20hand%20(automatic%20check)%20for%20the%20people%20that%20are%20experiencing%20these%20problem(s)%20-%20I%20think%20quite%20a%20lot%20of%20people%20are%20affected%20with%20this%20problem%2C%20so%20that%20would%20%26nbsp%3Bgive%20a%20reason%20for%20the%20development%20of%20such%20a%20tool%20-%20Or%20move%20on%20and%20get%20the%20problem%20fixed.%20Half%20a%20year%20seems%20a%20bit%20out%20of%20proportion%20for%20fixing%20this%20issue!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%3C%2FP%3E%0A%3CP%3EKim%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168824%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168824%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20thanks%20Scott%2C%20that%20worked!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168314%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168314%22%20slang%3D%22en-US%22%3E%3CP%3EUpdate%20to%20BIOS%201102.%26nbsp%3B%20That%20should%20allow%20you%20to%20upgrade%20with%20an%20ASUS%20MOB.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168177%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168177%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EASUS%20Prime%20x299-A%3C%2FP%3E%0A%3CP%3ESamsung%20SSD%20960%20Pro%20512gb%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E0xc00000bb%20error%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThen%20I%26nbsp%3Btried%20updating%20via%20USB%2C%20got%20the%20same%20error%2C%20and%20an%20extra%20error%20shown%20in%20the%20media%20creation%20tool%20dialog%20after%20restarting%3A%3C%2FP%3E%0A%3CP%3E%220xC1900101%20-%200x20017%20The%20installation%20failed%20in%20the%20SAFE_OS%20phase%20with%20an%20error%20during%20BOOT%20operation%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167576%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167576%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%20class%3D%22%22%3EA%20review%20to%20think%20about%3A%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThursday%2C%20October%2026%2C%202017%209%3A17%20PM%3C%2FP%3E%0A%3CP%3E%3CEM%3EJust%20did%20a%20chat%20with%20Microsoft.%26nbsp%3B%20They%20basically%20said%20they%20know%20about%20the%20upgrade%20problems%20with%20the%20NVMe%20Samsung%20SSD%20issue.%26nbsp%3B%20She%20said%20the%20engineers%20are%20working%20on%20the%20problem%2C%20and%20should%20have%20a%20fix%20soon%20on%20their%20support%20site.%26nbsp%3B%20She%20did%20not%20have%20a%20timetable%20or%20know%20if%20it%20will%20be%20a%20fix%20issued%20from%20cumulative%20updates%20through%20windows%20update%20or%20a%20separate%20fix%2C%20but%20she%20said%20they%20are%20working%20on%20it%2C%20and%20a%20fix%20will%20be%20issued%20soon.%26nbsp%3B%20Let's%20hope%20this%20is%20true.%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E---------------------------------------------%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%230000FF%22%3E%3CU%3E%3CEM%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F08485ba0-f69f-483b-861e-238f161dabee%2Fproblem-with-upgrade-to-creators-update-on-nvme-disk%3Fforum%3Dwin10itprosetup%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2F08485ba0-f69f-483b-861e-238f161dabee%2Fproblem-with-upgrade-to-creators-update-on-nvme-disk%3Fforum%3Dwin10itprosetup%3C%2FA%3E%3C%2FEM%3E%3C%2FU%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3F%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%20class%3D%22%22%3ET%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%20class%3D%22%22%3Eoday%20is%20March%204%2C%202018%3C%2FSPAN%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22short_text%22%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22%22%3ENothing%20has%20happened%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167574%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167574%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%20class%3D%22%22%3EA%20new%20installation%20is%20not%20an%20option%20for%20me.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167514%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167514%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%20my%20fault.%20I%20Thought%20a%20clean%20install%20was%20also%20imposible.%20I%20didn't%20tried%20a%20clean%20install.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167473%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167473%22%20slang%3D%22en-US%22%3EA%20clean%20installation%20always%20worked%20(also%20with%20the%20old%20bios).%20But%20nothing%20tells%20you%20that%2C%20in%20the%20next%20update%2C%20you%20will%20have%20the%20same%20problem%20with%20the%20update.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20also%20have%20no%20time%20to%20reinstall%20everything%20again%20and%20make%20copies%20of%20everything%20I%20have.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167472%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167472%22%20slang%3D%22en-US%22%3EIt%20happens%20the%20same%20to%20me.%20When%20MS%20activates%20de%20update%20again%2C%20I%20deactivate%20it%20in%20the%20task%20manager%2FMicrosoft%2FWindows%2FUpdateOrchestrator%20and%20there%20I%20disable%20all%20in%20relation%20to%20the%20UpdateAssistant.%20It%20works%20during%20some%20time%20and%20then%20I%20must%20disable%20it%20again.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167378%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167378%22%20slang%3D%22en-US%22%3E%3CP%3EHey%2C%3C%2FP%3E%0A%3CP%3Ewith%20the%20BIOS%20from%20MSI%20(for%20the%20X99A%20Tomahawk)%20I've%20posted%20before%20i%20was%20able%20to%20get%201709%20running.%20I've%20done%20a%20clean%20installation%20and%20it%20worked%20!%3C%2FP%3E%0A%3CP%3EThe%20guy%20from%20the%20MSI-Support%2C%20said%20this%20BIOS%20will%20be%20available%20in%20a%20final%20version%20in%20the%20future%2C%20but%20at%20least%20they%20try.%3C%2FP%3E%0A%3CP%3EGreetings%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167276%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167276%22%20slang%3D%22en-US%22%3EHello%20Michael%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20there%20any%20update%20on%20this%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%201703%20factory%20installed%2C%20but%20have%20been%20unable%20to%20update%20to%201709%20since%203rd%20November%20(Windows%20update%20has%20tried%2060%2B%20times%20to%20update%20unsuccessfully).%20I%20would%20not%20wish%20to%20go%20through%20this%20with%20every%20six-monthly%20update.%20%3CBR%20%2F%3E%3CBR%20%2F%3EI%20had%20hidden%20the%20update%20using%20wushowhide%20a%20week%20ago%2C%20but%20today%2C%20Microsoft%20appears%20to%20have%20installed%20Windows%2010%20Update%20Assistant%20and%20has%20since%20downloaded%20the%20update%20three%20times%20and%20failed%20to%20install%20three%20times%20-%20all%20this%20in%20one%20afternoon.%20This%20is%20wasting%20time%20and%20resources%20-%20now%20trying%20to%20work%20out%20how%20to%20stop%20this%20download%20process.%3CBR%20%2F%3E%3CBR%20%2F%3EIntel%20Core%20i7-7820X%2C%20Gigabyte%20GA-X299-UD4%20Motherboard%2C%20500GB%20Samsung%20960%20EVO%20M.2%20PCIe%20SSD.%3CBR%20%2F%3E%3CBR%20%2F%3EPaul%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-167125%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-167125%22%20slang%3D%22en-US%22%3E%3CP%3Ei%20do%20this%20for%20many%20times%20at%20both%20-%20MS%20and%20MSI.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebut%20from%20MS%20the%20last%20answer%20was%20a%20few%20weeks%20ago%2C%20and%20the%20only%20tell%20what%20they%20all%20tell.%3C%2FP%3E%0A%3CP%3E%22%20you%20need%20the%20latest%20driver%20for%20motherboard%20and%20chipsetdriver%20and%26nbsp%3B%20nvme%2C%20and%20then%20made%20a%20clean%20install%20from%201709.%22%3C%2FP%3E%0A%3CP%3Ei%20made%20this%20many%20times%2C%20and%20waste%20many%20hours%20for%20this%2C%20but%20still%20the%20same%20BSOD%20after%20all.%3C%2FP%3E%0A%3CP%3Ei%20have%20before%20installing%20all%20newest%20drivers%20and%20beta%20bios%20from%20MSi%2C%20i%20tell%20them%20this%20many%20times.%3C%2FP%3E%0A%3CP%3Ebut%20always%20same%20answer.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eso%20what%20can%20i%20do%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebuy%20a%20new%20motherboard%2C%20or%20another%20SSD.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20think%20this%20is%20not%20the%20wright%20way.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Egreetz%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-166825%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-166825%22%20slang%3D%22en-US%22%3E%3CP%3ELike%20everyone%20else%2C%20I%20am%20extremely%20disappointed%20with%20Microsoft's%20lack%20of%20support%2C%20fix%20and%20communication%20on%20this.%26nbsp%3B%20I%20blame%20the%20motherboard%20manufacturers%20equally.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20complained%20on%20MSI's%20site%2C%20and%20have%20also%20telephoned%20Microsoft%20support%20to%20log%20the%20issue%20and%20request%20a%20fix.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEVERYONE%20here%20should%20please%20do%20at%20least%20these%20two%20things.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165917%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165917%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20received%20also%20a%20BIOS%20Update.%20But%20it%20doesn't%20work%20for%20me....%3C%2FP%3E%0A%3CP%3EMy%20PC%20starts%20the%20Update%20and%20after%20the%20first%20Reboot%2C%20it%20turns%20on%2C%20but%20the%20screen%20is%20black%20until%20it%20goes%20completely%20off.%3C%2FP%3E%0A%3CP%3EI've%20started%20the%20system%20afterwards%2C%20and%20it%20boots%20into%201703%20and%20says%20its%20unable%20to%20install%201709.%3C%2FP%3E%0A%3CP%3EFor%20MSI%20x99a%20Tomahawk%20Users%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3Ddba2f1a780c207bc7a4591a2a0a351b1%26amp%3Brealfilename%3DE7A54IMS_224.7z%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3Ddba2f1a780c207bc7a4591a2a0a351b1%26amp%3Brealfilename%3DE7A54IMS_224.7z%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMaybe%20one%20of%20you%20has%20better%20luck%20with%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165722%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165722%22%20slang%3D%22en-US%22%3E%3CP%3Ehello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20cant%20understand%20why%20MS%20is%20not%20giving%20any%20respond%20of%20our%20problem%20here%3F%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ewe%20are%20many%20user%20with%20the%20same%20problem%2C%20also%20MSI%20is%20not%20able%20to%20bring%20a%20patch%20who%20is%20working.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eplease%20MS%20move%20your%20ass!!!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eor%20give%20an%20answer...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Egreetz%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165690%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165690%22%20slang%3D%22en-US%22%3E%3CP%3EHaving%20same%20issue%20here%2C%20just%20adding%20myself%20to%20the%20list%20of%20troubled%20MSI%20x99s%20users...%26nbsp%3B%20Also%20see%20the%20same%20in%20the%20bios%20regards%20the%20M2%20not%20showing%20up%20on%20the%20storage%20list%2C%20but%20showing%20in%20the%20boot%20order.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165609%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165609%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20my%20X99A%20Raider%2C%20it%20happens%20the%20same%20as%20in%20your%20screenshot.%20No%20detection%20of%20the%20M.2%20drive%20there.%20However%2C%20it%20is%20shown%20in%20the%20UEFI%20Boot%20order%20(so%20it%20is%20detected%20somehow)%20and%20if%20you%20take%20a%20look%20at%20the%20%22Board%20Explorer%22%2C%20it%20is%20detected%20that%20something%20is%20connected%20into%20the%20M.2%20port.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnyway%2C%20I%20think%20this%20is%20a%20software%20issue%20(Bios%20or%20Windows).%20If%20we%20could%2C%20at%20least%2C%20change%20the%20working%20mode%20of%20the%20M.2%20drive%20from%20pci-e%20to%20sata%2C%20so%20that%20it%20goes%20through%20the%20intel%20chipset%20(IRST)%2C%20I%20am%20pretty%20sure%20that%20the%20update%20would%20work%20because%20that%20is%20one%20of%20the%20working%20fixes%20out%20there%2C%20and%20it%20is%20not%20so%20difficult%20to%20let%20it%20upgrade%20with%20sata%20mode%20and%20then%20change%20it%20to%20pci-e.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUnfortunately%2C%20we%20do%20not%20have%20this%20option.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165546%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165546%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20problems%20too.%20Have%20an%20X99A%20Sli%20plus%20board%20and%20tried%20everything%20i%20read%20here%20and%20in%20the%20inet.%20From%20MSI%20is%20a%20beta%20biosupdate%20outside%20but%20it%20doesnt%20work.%20So%20i%20hope%20MS%20will%20find%20a%20way%20to%20bring%20out%20a%20hotfix%20so%20that%20we%20could%20patch.%20What%20i%20didnt%20understand%20is%20that%20every%20KB%20Patch%20could%20patch%20but%20the%20patch%20from%201703%20to%201709%20doesnt%20work.%20So%20for%20me%20the%20Problem%20is%20by%20microsoft%20and%20not%20from%20my%20board%20firm%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165174%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165174%22%20slang%3D%22en-US%22%3E%3CP%3EI%20asked%20to%20all%20MSI%20X99%2FX99a%20users%2C%20because%20I%20think%20it's%20so%20strange%20to%20have%20my%20boot%20disk%20not%20seen%20in%20the%20bios...%20and%20I'd%20like%20to%20understand%20if%20it%20is%20a%20MSI%20bios%20error%20or%20MSI%20choice...%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20I%20can%20see%2C%20a%20lot%20of%20us%2C%20X99a%20users%2C%20have%20this%20kind%20of%20issue...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-164056%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-164056%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20any%20update%20from%20Microsoft%3F%3C%2FP%3E%0A%3CP%3E20th%20unsuccessful%20update%20attempt%20via%20Windows%20update%2C%20eating%20my%20SSD%20life.%20Indeed%20there%20was%20small%20break%20period%20during%20christmas%20%2C%20but%20in%20Jan%20updates%20attempts%20start%20over.%20No%20errors%20or%20blue%20screens%20in%20my%20case%2C%20just%20instant%20rollback%20to%201703%20after%20reboot.%20I%20am%20affraid%20to%20do%20clean%20install%20and%20end%20with%20erased%20reformatted%20OS%20partition%20only.%3C%2FP%3E%0A%3CP%3EOS%20is%20on%20Samsung%20NVME%20SSD%20SM951%2C%20chipset%20C612%20in%20HP%20z840%20workstation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-164021%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-164021%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F29164iA2D79F33431AA2B8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22MSI_SnapShot_01.png%22%20title%3D%22MSI_SnapShot_01.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-163988%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-163988%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EI'm%20using%20an%20MSI%20X99A%20Tomahawk%20with%20an%20960%20EVO%20and%20it's%20not%20visible%20in%20the%20BIOS.%3C%2FP%3E%0A%3CP%3EI've%20got%20the%20same%20Problem%20with%20the%20Bluescreen%20by%20upgrading%20to%201709.%20But%20I've%20upgraded%20previously%20from%201607%20to%201703%20successfully.%3C%2FP%3E%0A%3CP%3EHope%20there%20will%20be%20a%20fix%20in%20near%20future%20!%3C%2FP%3E%0A%3CP%3E%3A)%3C%2FP%3E%0A%3CP%3E%26nbsp%3BEDIT%3A%20But%20it%20was%20always%20the%20case%20that%20my%20960%20EVO%20was%20not%20showing%20up%20in%20the%20BIOS%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-163852%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-163852%22%20slang%3D%22en-US%22%3E%3CP%3E....%3CSPAN%3ENow...%20I%20ask%20to%20%3CSTRONG%3Eall%3C%2FSTRONG%3E%20the%20MSI%20%3CSTRONG%3EX99%3C%2FSTRONG%3E%20users...%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-163209%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-163209%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%20class%3D%22%22%3EThis%20is%20not%20%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMSI%20X99A%20Gaming%20Pro%20Carbon%20!!!!%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-163113%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-163113%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EI%20see%20my%20M.2%20disk%20but%20I've%20migrated%20my%20system%20to%201709.%20Made%20a%20detour%20via%20standard%20disk%20(see%20above).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F29056iCBACAE1612AC7547%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22MSI_SnapShot.jpg%22%20title%3D%22MSI_SnapShot.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-163082%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-163082%22%20slang%3D%22en-US%22%3E%3CP%3EX99A%20Gaming%20Pro%20Carbon%20(MS-7A20%20installed%20version%201.41)%3C%2FP%3E%0A%3CP%3ENVMe%20SSD%20disk%20Samsung%20960%20Pro%20not%20in%20BIOS%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-163054%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-163054%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20MSI%20X99a%20users...%20I%20did%20the%20Fall%20Creators%20Update%20via%20NVMe%20cloning%20(after%204%20months%20of%20troubles%2C%20attempts%20and%20hopes)...%20but%20I'm%20curios%20and%20I%20love%20to%20learn%20every%20time%20I%20have%20the%20possibility%20to%20do%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBefore%20my%20upgrade%20(and%20even%20now)%20I%20noticed%20a%20strange%20thing%20in%20my%20MSI%20X99a%20Workstation%20BIOS%3A%26nbsp%3Binside%20the%20Storage%20Manager%2C%20the%20M.2%20disk%20is%20not%20reported!!!!!%20It's%20like%20the%20M.2%20line%20is%20not%20connected...%20but%20in%20the%20boot%20manager%2C%20the%20960%20Pro%20is%20the%20boot%20disk%20(via%20Intel%20Rapid%20Storage%20Manager).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20see%20it%20in%20the%20attached%20image%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F29053i62CCD187473FB63C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22MSI_SnapShot%20(Copia).jpg%22%20title%3D%22MSI_SnapShot%20(Copia).jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMSI%20said%20to%20me%20that%20if%20the%20NVMe%20disk%20boots%2C%20there%20is%26nbsp%3Bno%20issue...%20but...%20mmm...%20wait...%20your%20bios%2Fmobo%20can't%20see%20my%20disk%2C%20and%20you%20tell%20me%20that%20is%20a%20software%20problem%20and%20I%20need%20to%20format%3F%3F!!!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow...%20I%20ask%20to%20all%20the%20MSI%20X99%20users...%20in%20your%20BIOS%2C%20are%20you%20able%20to%20see%20the%20M.2%20disk%20as%20connected%20into%20the%20M.2%20port%3F%20I%20know%20that%20it%20should%20be%20discussed%20in%20a%20MSI%20related%20forum%2C%20but%20I%20think%20it%20should%20be%20useful%20to%20understand%20if%20the%200xc00000bb%20is%20definitively%20a%20bios%20related%20problem...%20and%20perhaps%20some%20bios%20modder%20can%20understand%20and%20solve%20the%20problem...%20before%20MSI...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHave%20a%20nice%20day!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-162914%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-162914%22%20slang%3D%22en-US%22%3E%3CP%3EX99A%20Gaming%20Pro%20Carbon%20(MS-7A20%20installed%20version%201.30)%3C%2FP%3E%0A%3CP%3ESamsung%20960%20Pro%20M2%20NVMe%20SSD%26nbsp%3B512GB%20firmware%20version%204B6QCXP7%3C%2FP%3E%0A%3CP%3EWindows%2010%20Pro%2064-bit%20version%2010.0.14393%20compilation%2014393%20Version%201607%20(14393.2068)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20swear%2C%20this%20is%20the%20last%20time%20I%20trusted%20MSI.%26nbsp%3BI%20will%20never%20make%20that%20mistake%20again.%26nbsp%3BShame%20of%20you!!!%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-161976%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-161976%22%20slang%3D%22en-US%22%3EThank%20you%20for%20the%20link.%3CBR%20%2F%3E%3CBR%20%2F%3EUnfortunately%2C%20I%20have%20just%20tried%20the%20update%20with%20this%20new%20beta%20bios%20but%20I%20still%20get%20the%20same%20bsod%20%3A(%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-161311%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-161311%22%20slang%3D%22en-US%22%3E%3CP%3Ehello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ehere%20are%20link%20to%20the%20beta%20BIOS%20for%20X99A%20Raider%20%3A%20%3CA%20href%3D%22http%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3D98bce9e21e8f51adb052bcbea36ead96%26amp%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3D98bce9e21e8f51adb052bcbea36ead96%26amp%3B%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eplease%20post%2C%20if%20you%20can%20made%20the%20update%2C%20and%20tell%20how.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Egreetz%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Esilberruecken%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-161274%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-161274%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eis%20absolute%20poor%2C%20what%20MS%20delivers.%20I%20thought%20I%20was%20the%20only%20one%20who%20has%20problems%2C%20but%20I%20see%20a%20lot%20of%20User%20here%20in%20this%20forum%20which%20has%20the%20same%20stupid%20problem.%20What%20kind%20of%20public%20relations%20microsoft%20use%3F!%20Like%20a%20god%3F%20Hurry%20up%20and%20solve%20the%20prob.%20I've%20wasted%20time%20enough%20until%20now%20...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-161074%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-161074%22%20slang%3D%22en-US%22%3EYes%2C%20but%20that%20is%20for%20the%20MSI%20X99S%20Gaming%207%20and%20MSI%20X99A%20Gaming%207%2C%20I%20have%20the%20X99A%20Raider%20like%20silber.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-161023%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-161023%22%20slang%3D%22en-US%22%3E%3CP%3EWolfgang%20posted%20it%20above%3A%20%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3D3b6bfdeeaf140535fc1ffaac86f4916e%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3D3b6bfdeeaf140535fc1ffaac86f4916e%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160960%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160960%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Edo%20you%20have%20a%20weblink%20to%20try%20it%20out%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160952%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160952%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you.%26nbsp%3B%20I%20hadn't%20realised%20this%2C%20and%20it%20is%20good%20to%20know.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20still%20hope%20that%20Microsoft%20will%20fix%20it%20however.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160856%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160856%22%20slang%3D%22en-US%22%3E%3CP%3Ehello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Etoday%20i%20get%20a%20beta%20BIOS%20(E7885IMS.P63)%26nbsp%3B%20from%20MSI%20for%20my%20X99A%20Raider.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBut%20it%20didn%C2%B4t%20fix%20the%20problem.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESame%20like%20before%20(BSOD).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESomeone%20get%20the%20update%20without%20cloning%20to%20a%20other%20ssd%3F%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%C2%B4m%20still%20in%20hope.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Egreetz%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160378%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160378%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20just%20save%20the%20OC%20profile%20then%20flash%20bios%20if%20you%20have%20to%20not%20that%20it%20would%20fix%20anything.%3C%2FP%3E%0A%3CP%3EFlashing%20the%20bios%20will%20still%20keep%20your%20saved%20oc%20profile%20so%20you%20don't%20have%20to%20worry.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160320%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160320%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20that%20they%20are%20working%20on%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20do%20prefer%20that%20Microsoft%20fix%20it%20at%20their%20end%20though.%26nbsp%3B%20Flashing%20BIOS%20would%20mean%20I%20would%20lose%20all%20the%20OC%20settings%20that%20my%20PC%20supplier%20did%20%3A(%26nbsp%3B%20So%20it%20would%20be%20a%20last%20resort%20solution%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160319%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160319%22%20slang%3D%22en-US%22%3E%3CP%3EMartin%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFormat%20c%3A%20is%20unfortunately%20not%20a%20viable%20option%20for%20me.%26nbsp%3B%20It%20would%20mean%20a%20few%20weeks%20of%20work%20rebuilding%20my%20PC%20setup%20and%20software.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160298%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160298%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20good%20to%20know%2C%20that%20i%20didnt%20waste%20even%20more%20time%20with%20that%20H.G3%20Bios%2C%20they%20send%20me%20that%20too.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160294%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160294%22%20slang%3D%22en-US%22%3E%3CP%3EShort%20update%20for%20other%20owners%20of%20MSI%20X99S%20Gaming%207%20and%26nbsp%3BMSI%20X99A%20Gaming%207%20boards%3A%20MSI%20answered%20to%20my%20issue%20I%20addressed%20to%20their%20support.%20They%20sent%20me%20a%20link%20to%20a%20new%20BIOS%20version%20that%20should%20solve%20the%20problem.%20For%20me%20it%20did%20not%20work%2C%20I%20still%20get%20the%20blue%20screen%2C%20but%20maybe%20someone%20else%20wants%20to%20give%20it%20a%20try.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENew%20BIOS%20version%20H.G3%3A%20%3CA%20href%3D%22http%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3D3b6bfdeeaf140535fc1ffaac86f4916e%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fmsi-ftp.de%3A8080%2Fmain.html%3Fdownload%26amp%3Bweblink%3D3b6bfdeeaf140535fc1ffaac86f4916e%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAt%20least%20they%20are%20working%20on%20it!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160289%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160289%22%20slang%3D%22en-US%22%3E%3CP%3EI%20gave%20up%2C%20and%20make%20a%20format%20c%20and%20install%20from%20scratch%2C%20people%20dont%20waste%20your%20time%2C%20like%20i%20did%20and%20try%20to%20avoid%20the%20new%20Win%20setup%20with%20%22workarounds%22%20they%20all%20dont%20help!!!%20Start%20New%2C%20all%20you%20can%20do.%20I%20was%20going%20through%20all%20this%2C%20so%20thats%20the%20poor%20conclusion...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%20regards%3C%2FP%3E%0A%3CP%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159897%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159897%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%3EThe%20same%20problem%20since%20october%202017.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%3EMSI%20X99A%20Gaming%20Pro%20Carbon%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3ESamsung%20960%20Pro%20M2%20SSD%20VNMe%202TB%3C%2FP%3E%0A%3CP%3EWin%2010%3C%2FP%3E%0A%3CP%3EVersionsinfo%3A%201703%20(15063.909)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%3ESee%20also%20german%20Forum..%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMicrosoft!!%20HELP%20HELP%20HELP%20HELP%20HELP%20HELP%20HELP%20HELP%20HELP%20HELP%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%3ER.Freier%2C%26nbsp%3BGermany%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159510%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159510%22%20slang%3D%22en-US%22%3E%3CP%3E%22There%20is%20a%20block%20in%20place%20that%20keeps%20Windows%20Update%20from%20offering%20Windows%201709%20to%20affected%20systems.%22%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3EYour%20block%20is%20NOT%20working%20for%20me.%26nbsp%3B%20Win10%20keeps%20trying%20to%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159496%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159496%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%26nbsp%3BMSI%20Godlike%20Carbon%20X99A%20motherboard%20and%26nbsp%3BSamsung%20SM951%20M.2%20PCIe%20NVMe%20SSD%20boot%20drive%2C%20and%20have%20had%20this%20problem%20ever%20since%20it%20started.%26nbsp%3B%20Very%20annoying%2C%20and%20the%20PC%20keep%20trying%20to%20update%20many%20times%20daily%2C%20and%20failing!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20ridiculous.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159473%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159473%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20problem!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMSI%20Godlike%20Carbon%20X99A%20motherboard%20and%20Samsung%20SM951%20M.2%20PCIe%20NVMe%20SSD%20boot%20drive.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20all%20drivers%20up%20to%20date%2C%20and%20have%20tried%20everything%20(except%20changing%2Fcloning%20my%20boot%20drive%2C%20which%20is%20beyond%20my%20skills).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft%20need%20to%20fix%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-159322%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-159322%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3EI'm%20a%20newbee%20in%20this%20forum%20and%20want%20to%20say%20hello%20to%20everybody!!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20the%20same%20probelm%20with%20the%20Fall-Update%2C%20my%20system%20is%3A%3C%2FP%3E%0A%3CP%3EMSI%20X99A%20SLI%20PLUS%3C%2FP%3E%0A%3CP%3ESamsung%20950%20M2%20SSD%3C%2FP%3E%0A%3CP%3EWin%2010%3C%2FP%3E%0A%3CP%3EVersionsinfo%3A%201703%20(15063.909)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Fall-Update%20fail%20always%20with%20BSOD%20...%3C%2FP%3E%0A%3CP%3EIt's%20very%20poor%20that%20MS%20isn't%20able%20to%20inform%20their%20customers.%204%20Month%20that%20troubble%3F!%3C%2FP%3E%0A%3CP%3ETemporary%20solution%3A%20Disable%20automatic%20updates%2C%20and%20put%20in%20the%20updates%20manualy%2C%20month%20for%20month%20...%3C%2FP%3E%0A%3CP%3EIs%20anybody%20form%20MS-Company%20able%20to%20give%20us%20an%20info%20about%20the%20progress%20of%20the%20debugging%20%3B-)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAll%20the%20best%20for%20You%20all%2C%3C%2FP%3E%0A%3CP%3EUdo%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158551%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158551%22%20slang%3D%22en-US%22%3EHello%20Michael%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20there%20any%20update%20on%20this%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20Windows%2010%20Creators%20Update%20(1703)%20factory%20installed%2C%20but%20have%20been%20unable%20to%20update%20to%201709%20since%203rd%20November%20(Windows%20update%20must%20have%20tried%2060%2B%20times%20to%20update%20unsuccessfully).%20I%20would%20not%20wish%20to%20go%20through%20this%20with%20every%20six-monthly%20update.%3CBR%20%2F%3E%3CBR%20%2F%3EIntel%20Core%20i7-7820X%2C%20Gigabyte%20GA-X299-UD4%20Motherboard%2C%20500GB%20Samsung%20960%20EVO%20M.2%20PCIe%20SSD.%20SSD%20drivers%20updated%20and%20BIOS%20updated%20to%20most%20current%20versions.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%2C%20Paul%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-155098%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-155098%22%20slang%3D%22en-US%22%3E%3CP%3ESo...%20I%20did%20the%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20had%20to%20clone%20the%20system%20disk%20(960%20Pro)%20to%20another%20bootable%20ssd%20(850%20Pro).%3C%2FP%3E%0A%3CP%3ENow%2C%20the%20PC%20is%20doing%20the%20rest%20of%20the%20updates%2C%20then%20I'll%20try%20to%20re-clone%20all%20to%20the%20960%20Pro.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoing%20this%20operation%2C%20I%20noticed%20that%20the%20X99A%20Bios%20has%26nbsp%3Bsome%20problems%3A%20it%20can't%20manage%20correctly%20the%20boot%20disk.%20After%20the%20cloning%20operation%2C%20I%20obviously%20went%20into%20the%20bios%20to%20set%20the%20850%20as%20boot%20disk.%20I%20did%20the%20%22save%20and%20reboot%20option%22%20and%20the%20pc%20started%20again%20with%200xc00000bb%20error.%20After%20some%20bios%20reset%2C%20I%20was%20able%20to%20start%20from%20the%20850%2C%20and%20now%20I%20have%20the%20FCU%20running%20(by%20now%2C%20not%26nbsp%3Bfrom%20the%20NVMe).%26nbsp%3BAd%20maiora...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-154835%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-154835%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can't%20believe%20that%20there%20is%20still%20no%20solution%20to%20this%20problem%20beside%20a%20BIOS%20update%20(which%20is%20mostly%20impossible%20to%20have%20unless%20you%20are%20a%20asus%20user).%20How%20ridiculous.%3C%2FP%3E%0A%3CP%3E%3CAUDIO%20style%3D%22display%3A%20none%3B%22%20controls%3D%22controls%22%3E%3C%2FAUDIO%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-153409%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-153409%22%20slang%3D%22en-US%22%3EI%20100%25%20agree%20with%20you%2C%20I%20will%20be%20waiting%20as%20welll%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-153021%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-153021%22%20slang%3D%22en-US%22%3E%3CP%3ENope%2C%20there%20is%20a%20workaround%20which%20consists%20in%20cloning%20your%20ssd%20into%20another%20drive%2C%20update%20windows%20with%20that%20drive%2C%20and%20then%2C%20after%20having%20the%20system%20up%20and%20running%2C%20cloning%20it%20back%20to%20the%20M.2%20SSD.%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20I%20said%20before%2C%20I%20do%20not%20want%20to%20do%20that%20in%20every%20update%20so%20I%20wait%20for%20the%20fix%20as%20long%20as%20possible.%20Meanwhile%2C%20I%20have%20disabled%20the%20update%20assistant%20in%20the%20task%20manager.%3CBR%20%2F%3E%3CBR%20%2F%3EGreetings%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152873%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152873%22%20slang%3D%22en-US%22%3E%3CP%3EHello.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eany%20news%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ehas%20someone%20make%20the%201709%20update%20with%20following%20parts%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EX99A%20Raider%20-%20Samsung%20Evo%20960%20NVMe%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eif%20someone%2C%20pls%20let%20me%20known%20how%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Egreetz%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152704%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152704%22%20slang%3D%22en-US%22%3E%3CP%3ELast%20weekend%20I%20successfully%20finished%20the%20update%20of%20my%20system%20(MSI%20X99%20%2B%20SSD%20850)%20to%201709.%20It%20took%20me%206%20hours.%20Most%20time%20was%20spent%20waiting%20for%20the%20system.%20No%20clean%20installation.%3C%2FP%3E%0A%3CP%3EI%20was%20tired%20to%20wait%20for%20a%20solution%20by%20MSI%20and%2For%20Microsoft.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMy%20approach%20was%20to%20make%20a%20intermediate%20step%20via%20a%20%22normal%22%20disk.%3C%2FP%3E%0A%3CP%3EShort%20description%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20Image%20Backup%20of%20system%20disk%3C%2FP%3E%0A%3CP%3E2.%20change%20SSD%20to%20%22normal%22%20disk%3C%2FP%3E%0A%3CP%3E3.%20recover%20image%20to%20%22normal%22%20disk%3C%2FP%3E%0A%3CP%3E4.%20Because%20of%20new%20hardware%20set%20product%20key%20again.%20Otherwise%20after%20the%20update%20procedure%20ended%20with%20error%20message%20like%20%22can't%20get%20product%20key%22%3C%2FP%3E%0A%3CP%3E4.%20start%20update%20to%201709%3C%2FP%3E%0A%3CP%3E5.%20clean%20system%20disk%20(delete%20upgrade%20folder%20etc.)%3C%2FP%3E%0A%3CP%3E6.%20make%20image%20backup%20of%20%22normal%22%20disk%3C%2FP%3E%0A%3CP%3E7.%20recover%20image%20to%20ssd%3C%2FP%3E%0A%3CP%3E8.%20O%20gott!%20BSOD%200x00000bb!%3C%2FP%3E%0A%3CP%3E9.%20select%20option%20%22start%20safe%20mode%22%20from%20BSOD.%20system%20starts%20in%20safe%20mode%3C%2FP%3E%0A%3CP%3E10.%20restart%20system%3C%2FP%3E%0A%3CP%3E11.%20everthing%20works%20fine%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegards%3C%2FP%3E%0A%3CP%3EMichael%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152703%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152703%22%20slang%3D%22en-US%22%3ECould%20you%20please%20tell%20me%20what%20fix%20from%20%22Tim%22%20you%20refering%20to%3F%20Is%20the%20post%20deleted%2C%20i%20cant%20find%20it%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152695%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152695%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20method%20also%20worked%20for%20me.%26nbsp%3B%26nbsp%3B%20My%20system%20is%20very%20similar%20to%20yours%20except%20I%20have%20have%2064%20GB%20of%20ram%20and%20the%201TB%20ssd.%26nbsp%3B%20So%20I%20did%20get%20the%201709%20finally%20installed.%26nbsp%3B%20But%20now%20I%20seem%20to%20have%20other%20driver%20problems%20with%20my%20internal%20USB%20hub%20device%20and%20also%20my%20%22Windows%20Update%22%20now%20says%20%22Some%20settings%20are%20managed%20by%20your%20organization%22%20and%20this%20prevents%20me%20from%20checking%20for%20updates%20or%20seeing%20my%20updte%20history.%26nbsp%3B%20I%20wonder%20if%20you%20had%20any%20similar%20problems%20afer%20your%20successful%20upgrade%20to%201709%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152691%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152691%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20fix%20from%20Tim%20definitely%20worked%20for%20me.%26nbsp%3B%20So%20now%20I%20finally%20have%20a%20successful%20update%20to%201709.%26nbsp%3B%20I%20followed%20all%20of%20Tims%20steps%20and%20the%20update%20worked.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152332%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152332%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Tim%20for%20sharing%20your%20fix.%20%26nbsp%3BThat%20gives%20me%20one%20more%20fix%20procedure%20to%20try.%20%26nbsp%3BI%20was%20surprised%20to%20see%20that%20I%20did%20not%20have%20the%20latest%20BIOS%20even%20though%20I%20am%20running%20the%20Asus%20EZ%20%26nbsp%3Btool%20that%20is%20supposed%20to%20check%20daily%20for%20bios%20updates.%20%26nbsp%3BI%20did%20find%20the%201004%20that%20you%20mentioned%20plus%20an%20even%20newer%201102%20version%20from%20Jan%2017%2C%202008.%20%26nbsp%3BSo%20I%20am%20manually%20updating%20the%20bios%20and%20will%20follow%20your%20procedure%20to%20see%20if%20that%20works%20for%20my%20setup.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152314%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152314%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20attempted%20the%20clean%20install%20multiple%20times%20and%20it%20still%20does%20not%20work.%20%26nbsp%3BMy%20brand%20new%20x299%20system%20works%20fine%20with%20windows%207%20pro%20and%20windows%2010%20pro%20fresh%20in%20talls%20%26nbsp%3Bfrom%20usb.%20%26nbsp%3BSo%20there%20must%20be%20good%20drivers.%20%26nbsp%3BI%20have%20removed%20all%20peripherals%20and%20tried%20everything%20I%20can%20think%20of%20plus%20all%20of%20the%20suggested%20fixes%20out%20there%20in%20the%20support%20forumd.%20%26nbsp%3B%20But%20my%20system%20will%20absolutely%20not%20work%20with%20the%201709%20update.%20%26nbsp%3BIt%20does%20not%20matter%20how%20I%20install%20the%20update.%20%26nbsp%3BToday%20I%20again%20downloaded%20the%20new%201709%20ISO%20and%20ran%20through%20the%20installer%20with%20newly%20formatted%20ssd.%20%26nbsp%3B%20It%20all%20seems%20to%20go%20well%20until%20the%20first%20reboot%20which%20leads%20to%20BSOD.%20%26nbsp%3BAll%20my%20drivers%20are%20up%20to%20date%2C%20and%20the%20system%20works%20great%20with%20the%201607%20Win%2010%20version.%20%26nbsp%3BBut%20will%20not%20work%20with%201709%20whether%20it%20being%20updated%20from%20my%201607%20version%20or%20a%20fresh%20ISO%20install.%20%26nbsp%3BCan%20anybody%20at%20Microsoft%20please%20help.%20%26nbsp%3BI%20will%20offer%20one%20million%20of%20my%20own%20TobyNorris%20cryptocoin%20dollars%20to%20anyone%20at%20Microsoft%20who%20can%20either%20fix%20this%20and%20restore%20my%20faith%20in%20your%20company.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152311%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152311%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20brand%20new%20system%20with%20Asus%20prime%20x299%20motherboard%20along%20with%2064%20gb%20ram%20and%20i9-7900x%20cpu%20and%201TB%20samsung%20M.2%20ssd.%20%26nbsp%3BIt%20is%20now%20Feb%204%202018.%20%26nbsp%3BI%20have%20installed%20and%20reinstalled%20my%20brand%20new%20windows%2010%20pro%20multiple%20times%20from%20the%20%24200%20usb%20stick.%20%26nbsp%3BI%20also%20have%20dvd%20and%20even%20dowloaded%20the%20latest%20from%20internet.%20%26nbsp%3BEverything%20works%20great%20until%20the%20update%20service%20starts%20forcing%20the%201709%20defective%20update%20on%20me.%20%26nbsp%3BThen%20the%20problems%20and%20harm%20begins.%20%26nbsp%3BI%20have%20tried%20every%20so-called%20fix%20on%20the%20internet.%20%26nbsp%3BThe%20update%20process%20always%20leads%20to%20BSOD%20with%200xc00000bb.%20%26nbsp%3BI%20am%20a%20software%20engineer%20with%20over%2030%20years%20experience.%20%26nbsp%3BNothing%20works.%20%26nbsp%3BNot%20the%20trouleshooter%2C%20nor%20any%20of%20the%20other%20many%20fixes%20offered%20by%20MS%20support%20fotums.%20%26nbsp%3BNot%20even%20the%20brand%20new%20ISO%20download%20with%201709.%20%26nbsp%3BSo%20there%20is%20apparently%20still%20no%20solution%20for%20this%20problem%20after%20many%20months.%20%26nbsp%3B%20I%20see%20that%20I%20am%20not%20alone.%20%26nbsp%3BThere%20is%20no%20excuse%20for%20this.%20%26nbsp%3BThis%20motherboard%20is%20popular%20and%20one%20of%20the%20newest%20out%20there.%20%26nbsp%3BThe%201709%20update%20was%20not%20adequately%20tested%20and%20is%20defective%20and%20is%20causing%20harm%20to%20many%20people%20like%20me%20who%20have%20wasted%20many%20many%20hours%20trying%20to%20get%20it%20to%20work.%20%26nbsp%3BWho%20is%20responsible%20and%20accountable%20for%20this%20blunder%20at%20microsoft%3F%20%26nbsp%3BWe%20will%20never%20know.%20%26nbsp%3BFor%20now%20I%20can%20only%20disable%20the%20windows%20update%20service%20and%20pray%20that%20someday%20someone%20at%20Microsoft%20will%20fix%20this%20terrible%20and%20embarrassng%20defective%20product.%20%26nbsp%3BThis%20is%20no%20different%20than%20going%20to%20car%20dealer%20and%20buying%20a%20new%20car%20and%20then%20the%20car%20won%20even%20start.%20%26nbsp%3BThe%20dealer%20is%20happy%20to%20take%20all%20your%20money%20and%20apologizes%20for%20the%20defective%20product%20and%20promises%20to%20get%20it%20fixed%20someday.%20%26nbsp%3BMeanwhile%20you%20have%20nothing%20for%20your%20money%20and%20dealer%20has%20no%20incentive%20to%20fix%20their%20defect%20because%20they%20already%20have%20all%20your%20money.%20%26nbsp%3BSomewhere%20there%20might%20be%20a%20smart%20lawyer%20or%20consumer%20organization%20who%20will%20get%20dealer%20attention%20by%20class%20action%20lawsuit%20representing%20all%20the%20injured%20customers.%20%26nbsp%3BMaybe%20then%20the%20product%20will%20get%20fixed%20or%20recalled%20and%20the%20customers%20will%20get%20their%20money%20back.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152105%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152105%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eyes%20i%20do%20this%2C%20but%20first%20they%20answer%2C%20that%20they%20never%20heard%20from%20this%20problem.%26nbsp%3B%20lol%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eand%20second%20they%20told%20me%2C%20i%20have%20to%20make%20a%20clean%20install%20from%20win10%201709%20creators%20update%20with%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUEFI%20mode%20on.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20send%20them%20all%20emails%20and%20links%20from%20all%20forums%20i%20posted%2C%20MS%2CMSI%2C%20Samsung%20and%20and%20and.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebut%20i%20think%20they%20didn%C2%B4t%20read%20it.%20i%20also%20ask%20why%20can%20Asus%20fix%20it.%20but%20no%20answere.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20dont%C2%B4make%20a%20clean%20new%20install%2C%20before%20no%20one%20posted%20that%20the%20problem%20is%20fixed%20now.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Elet%20me%20hear%20if%20someone%20made%20it%2C%20and%20it%20works%2C%20please%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151934%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151934%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20thinking%20exactly%20the%20same.%20I%20do%20not%20want%20to%20perform%20a%20clean%20install%20when%20there%20is%20no%20guarantee%20that%2C%20in%20the%20next%20update%2C%20this%20issue%20persists%20(I%20am%20with%20the%20Anniversary%20version%20because%20the%20first%20Creators%20Update%20was%20already%20giving%20me%20this%20BSOD).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20is%20funny%20to%20see%20that%20Asus%20customers%20are%20receiving%20a%20fix%20via%20BIOS%20update%2C%20while%20we%2C%20MSI%20users%2C%20are%20left%20in%20the%20dark.%20It%20is%20funny%20to%20read%20that%20they%20recommend%20to%20do%20the%20installation%20in%20UEFI%20mode%2C%20when%20there%20is%20no%20other%20way%20to%20have%20the%20M.2%20drive%20as%20the%20boot%20device...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECould%20any%20of%20you%2C%20who%20contacted%20MSI%20support%2C%20give%20them%20the%20link%20to%20this%20thread%3F%20It%20could%20be%20helpful%20for%20them%20to%20find%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151912%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151912%22%20slang%3D%22en-US%22%3E%3CP%3EI%20think%20that%20MSI%20will%20never%20release%20new%20bioses%20for%20old%20X99%20clients...%20pheraps%20they%20want%20us%20to%20buy%20a%20new%20motherboard...%20but%20I%20am%20very%20disappointed%20with%20them...%26nbsp%3B%20very%20disappointed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20asked%20suppord%2C%20and%20they%20said%20%22We%20tried%20to%20install%20W10%201703%20on%20X99A%20Workstation%20with%20960%20Pro%2C%20then%20we%20made%20the%20FCU...%20It%20worked%20without%20problems%22...%20ok%2C%20but%20our%20systems%3F%20We%20all%20have%20garbage%20on%20our%20pcs%3F%20We%20are%20all%20incompetent%3F%20Sorry%20for%26nbsp%3Bthe%20outburst...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151904%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151904%22%20slang%3D%22en-US%22%3E%3CP%3EI%20doubt%20a%20new%20installation%20of%20Windows%20will%20help%20to%20solve%20the%20problem%20in%20long%20term%20perspective.%20The%20next%20big%20update%20of%20Windows%2010%20will%20come%20sooner%20or%20later%20and%20if%20this%20problem%20is%20not%20solved%20until%20then%2C%20you%20will%20have%20to%20face%20with%20the%20same%20error%20again...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151823%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151823%22%20slang%3D%22en-US%22%3E%3CP%3EAnybody%20here%2C%20who%20did%20a%20clean%20new%20Win10-1709%20Installation%3F%20%3CBR%20%2F%3EDoes%201709%20run%20at%20all%20at%20the%20MSI%20X99%2FSSD%20960%20combination%3F%3CBR%20%2F%3E%3CBR%20%2F%3EBevor%20i%20have%20to%20completely%20rebuild%20my%20system%2C%20which%20will%20take%20hours%2C%20it%20would%20be%20nice%20to%20know%2C%3C%2FP%3E%0A%3CP%3Eit%20the%20toxic%20combination%20of%20X99%20%2B%20SSD%20960%20works%20anyhow...%3CBR%20%2F%3E%3CBR%20%2F%3EMartin%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151806%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151806%22%20slang%3D%22en-US%22%3E%3CP%3EI%20really%20feel%20for%20these%20people%20with%20MSI%20motherboards.%26nbsp%3B%20Apparently%20Microsoft%20is%20never%20going%20to%20issue%20a%20fix.%26nbsp%3B%20You%20have%20to%20keep%20leaning%20on%20MSI%20to%20issue%20a%20BIOS%20fix.%26nbsp%3B%20As%20has%20been%20reported%20here%2C%20ASUS%20released%20a%20fix%20for%20this%20with%20their%201102%20BIOS%20update.%26nbsp%3B%20Good%20luck%20to%20everyone.%26nbsp%3B%20You%20must%20keep%20at%20your%20MOB%20manufacturer.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151784%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151784%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Everyone%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20the%20original%20poster%20of%20this%20thread%2C%20I%20would%20like%20to%20let%20everyone%20know%20that%20the%20latest%201102%20BIOS%20update%20from%20ASUS%20for%20the%20X299%20Prime%20Deluxe%20resolved%20the%20issue.%26nbsp%3B%20I%20was%20able%20to%20install%20the%20Fall%20Creators%20Update%20using%20the%20Windows%20Update%20assistant.%26nbsp%3B%20I%20did%20delete%20the%20SoftwareDistribution%20prior%20to%20the%20update%26nbsp%3Bto%20ensure%20that%20there%20was%20no%20old%20update%20media%20still%20on%20the%20drive%2C%20however%20this%20may%20or%20may%20not%20have%20been%20necessary.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151781%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151781%22%20slang%3D%22en-US%22%3E%22you%20have%20to%20make%22...%20Thank%20you%2C%20MSI...%20%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20issue%20is%20not%20our%20fault.%20We%20bought%20Great%20components%20for%20our%20PC...%20This%20is%20our%20only%20fault...%20So%2C%20do%20they%20pay%20us%20for%20the%20time%20we%20Will%20spend%20for%20the%20complete%20reconfiguration%20of%20our%20workstations%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151752%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151752%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3Ehere%20are%20the%20last%20answer%20today%20from%20MSI%20support%3A%3C%2FP%3E%0A%3CP%3E%22You%20have%20to%20make%20a%20clean%20Windows%2010%20installation%20with%20UEFI%20mode%20on%20in%20BIOS%2C%20and%20with%20included%201709%20and%20WHQL%20Support%20on%22.%3C%2FP%3E%0A%3CP%3EBut%20there%20are%20no%20guarantee.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESomeone%20an%20other%20issue%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151504%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151504%22%20slang%3D%22en-US%22%3E%3CP%3EAnd%20today%20Microsoft%20released%20a%20new%20update%20for%201709%20(and%20some%20other%20updates%20for%20older%20versions)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20tried%20another%20time%20to%20update%20the%20old%201703.%20Same%20result%3A%200xc00000bb.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%2C%20I've%20just%20finished%20to%20clean%20the%20960%20pro%20from%20the%20update%20data%20and%20Windows%20starts%20to%20download%20again%20the%20faulty%20update...%20I%20think%20that%20FCU-X99-960Pro%20issue%20is%20killing%20my%20precoius%20ssd...%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151502%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151502%22%20slang%3D%22en-US%22%3EI%20get%20the%20new%20one%20via%20Magician...%20it%20asked%20me%20to%20upgrade...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-151337%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151337%22%20slang%3D%22en-US%22%3E%3CP%3EExactly%20same%20problem%20for%20me%20with%20MSI%20%22X99A%22%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIts%20like%20madness%20that%20he%20forces%20the%20user%20to%20upgrade%20to%20a%20version%20every%26nbsp%3Bother%20day%20and%20then%20crashes%20with%20blue%20screen%20%3CSPAN%3E0xc00000bb%26nbsp%3B%3C%2FSPAN%3Eand%20then%20downgrades%20to%20make%20it%20work%20again.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20might%20even%20mess%20up%20the%20SSD%20lifetime...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150910%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150910%22%20slang%3D%22en-US%22%3EExactly%20the%20same%20for%20me.%20Everyday%2C%202-3%20failed%20updates%20when%20my%20pc%20is%20idle%20or%20I%20am%20not%20there%20to%20prevent%20the%20installation.%20It%20cannot%20be%20stopped%20anywhere.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20really%20tired%20of%20this%20situation.%20At%20least%2C%20one%20month%20ago%2C%20the%20update%20was%20not%20appearing%20every%20day%20at%20any%20time.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150746%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150746%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Esame%20for%20me%2C%20everyday%202%20or%203%20times%2C%20downloading%20the%20hole%20updates.%20but%20installation%20failed.%3C%2FP%3E%0A%3CP%3Ethe%20problem%20is%2C%20that%20i%20can%20not%20stop%20the%20download.%20or%20the%20update%20process.%20so%20i%20loose%20everyday%20many%20GB%20datatranfer%20for%20nothing%2C%3C%2FP%3E%0A%3CP%3Eand%20it%20kill%C2%B4s%20my%20monthly%20volume.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ewhy%20they%20don%C2%B4t%20answer%3F%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMSI%3A%20no%20Answer%3C%2FP%3E%0A%3CP%3EMS%3A%20no%20Answer%2C%20or%20response%2C%20or%20help%3C%2FP%3E%0A%3CP%3ESamsung%3A%20ask%20MS%20or%20MSI%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Estupid%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150735%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150735%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20also%20the%20same%20problem%20since%20the%20Creators%20Update%20(some%20years%20already)%20which%20was%20never%20solved.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20most%20of%20you%2C%20I%20have%20a%20MSI%20X99A%20Raider%20mobo%20with%20an%20i7%206800K.%20(960EVO)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20hope%20it%20will%20be%20soon%20fixed%2C%20because%20the%20FCU%20is%20trying%20to%20update%20twice%20per%20day%20with%20the%20corresponding%20bsod%20after%20updating.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150649%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150649%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20use%20samsung%20magican%2C%20but%20for%20me%2C%20there%20is%20no%20new%20firmware%20for%20the%20samsung%20NVMe%20960%20SSD.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eis%20still%20the%20same%20old%20one%203B7QCXE7.%20how%20do%20you%20get%20the%20new%20one%3F%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eand%20today%20is%20the%20last%20day%20of%20january%2C%20and%20MS%20told%20all%20the%20time%2C%20end%20of%20january%20you%20get%20a%20patch.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20think%20we%20never%20get%20help%20from%20MS%2C%20MSI%20or%20Samsung.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ewhat%20a%20story....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150588%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150588%22%20slang%3D%22en-US%22%3E%3CP%3ESo...%20today%20Samsung%20released%20a%20new%20firmware%20for%20960%20Pro%20(4B6QCXP7).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EObviously%2C%20on%20my%20MSI%20X99A%20Workstation%2C%20no%20way%20to%20install%20the%20FCU.%20Same%20error%2C%20again%20and%20again.%20I%20can%20write%20a%20film%20or%20a%20tv%20serie%20about%20this...%20and%20MSI%20doesn't%20have%20a%20new%20bios%2Fbeta%20bios%20for%20my%20mobo.%20Thank%20you...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150573%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150573%22%20slang%3D%22en-US%22%3E%3CP%3EMSI%20x99%20board%20here%20too%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150308%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150308%22%20slang%3D%22en-US%22%3EHi%2C%20Same%20thing%20(error%200XC00000bb)%20with%3A%20MSI%20X99S%20Sli%20Plus%20and%20Intel%20SSDPEKKW256G7%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150230%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150230%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3Efor%20my%20understanding.%20Is%20it%20an%20issue%20for%20Microsoft%20or%20for%20the%20Motherboard%20Dealer%3F%20Don't%20get%20me%20wrong%20but%20I%20do%20not%20see%20any%20activities%20on%20MSI%20side.%20I%20do%20not%20see%20any%20intensive%20discussions%20concerning%20MS%20update%20with%20MSI%20x99%20on%20MSI%20boards.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ERegards%3C%2FP%3E%0A%3CP%3EMichael%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150221%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150221%22%20slang%3D%22en-US%22%3EHi%2C%20Any%20news%20about%20this%20issue%3F%20This%20doesn't%20only%20appear%20on%20Asus%20machines.%20I%20Have%20an%20MSI%20X99%20Mainboard%20and%20have%20the%20same%20isssue%20and%20according%20to%20what%20I've%20found%20on%20the%20internet%2C%20pretty%20much%20all%20X99%20are%20impacted.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-149772%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-149772%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%2010%20hours%26nbsp%3Battempts%20I%26nbsp%3Bfind%20the%20way%20to%20resolve%20this%20problem.%20This%20is%20what%20I%20did%3A%3CBR%20%2F%3E1)%20Update%20BIOS%20to%201102%20from%20asus.com%20and%20reset%20BIOS%20to%20default%20settings(Disabled%20XMPP%20and%20reset%20my%20overclock)%3CBR%20%2F%3E2)%26nbsp%3BMake%20USB%20flash%20with%20MediaCreationTool%3CBR%20%2F%3E3)%20Make%20this%20action%20from%20Tim%20Gall%20poste%3A%3CBR%20%2F%3E%22%3C%2FP%3E%0A%3CP%3EFor%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EPCH%20Storage%20Cofiguration%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EI%20set%3A%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESATA%20Controllers%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eto%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3E%3CSTRONG%3Edisabled%3C%2FSTRONG%3E%3C%2FEM%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E(the%20topmost%20option).%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3EI%20enabled%20it%20again%20once%20the%20upgrade%20was%20complete.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EBoot%20-%26gt%3BCSM%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EI%20set%20it%20to%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E%3CEM%3Eenabled%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBoot%20Devices%20Control%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eset%20to%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3E%3CSTRONG%3EUEFI%20only%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBoot%20Network%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EBoot%20Storage%20Devices%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eset%20to%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3E%3CSTRONG%3Eignore%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBoot%20from%20PCIE%20expansion%20devices%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eto%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEM%3E%3CSTRONG%3EUEFI%20first%22%3CBR%20%2F%3E%3C%2FSTRONG%3E4)%20I%20open%20BIOS%20menu%20after%20all%20system's%20restarts%20before%20update%20continue.%20Update%20was%20loading%2C%20then%20restart%2C%20I%20click%20DEL%20to%20open%20menu%2C%20quit%20without%20change%2C%20update%20continue%20install.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EI%20don't%20sure%20that%203)%20and%204)%20is%20important%2C%20but%20I%20did%20and%20now%20I%20have%201709%20windows%2010%20build.%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%20my%20config%20is%20Motherboard%20Asus%20x299%20Prime%20Deluxe%2BSamsung%20960%20PRO%20512gb%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-149638%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-149638%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Michael%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20you're%20doing%20well.%20Currently%20we%20have%20almost%20end%20of%20January.%20Do%20you%20have%20any%20information%20about%20the%20patch%20for%20the%200XC00000bb%20FCU%20Update%20Error%20on%20X99%20Mainboards%20with%20Intel%20NVMe%20SSD%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-149435%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-149435%22%20slang%3D%22en-US%22%3E%3CP%3EFYI%20I%20updated%20to%201102%20as%20Scott%20G%20mentioned%20and%20was%20FINALLY%20able%20to%20install%201709.%20If%20you%20have%20a%26nbsp%3B%3CSPAN%3EASUS%20X299%20mobo%2C%20update%20the%20BIOS%20to%201102%2C%20it%20worked%20for%20me%20as%20well.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-149171%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-149171%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20problem%201703-%26gt%3B1709%20and%20Samsung%20SSD%20960%20with%20MSI%20X99%20Gaming%207%2C%20latest%20BIOS%20is%20HF%20from%202016.%20BSOD%26nbsp%3B%3CSPAN%3E0xc00000bb%20with%20%22normal%22%20Update%20procedure%26nbsp%3B%26nbsp%3B%2C%20with%20manual%20Update%20via%20Update%20Assistant%20and%20also%20with%20an%20downloadet%20bootable%20Update%20DVD%2C%20makes%20no%20difference%20at%20all%20in%20any%20way%20you%20are%20trying%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20would%20be%20very%20kind%2C%20if%20anybody%20find%20a%20solution%2C%20please%20let%20us%20know%20here%2C%20so%20that%20we%20share%20a%20solution%2C%20so%20that%20we%20not%20have%20to%20search%20in%2010%20different%20places%20in%20the%20net%20%3A)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148928%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148928%22%20slang%3D%22en-US%22%3E%3CP%3EBIOS%20version%201102%20seems%20to%20have%20solved%20the%20upgrade%20to%201709%20problems%20for%20people%20with%20ASUS%20X299%20MOB's.%26nbsp%3B%20If%20you%20have%20an%20ASUS%20MOB%20upgrade%20the%20BIOS%20to%201102%20and%20you%20should%20be%20able%20to%20upgrade.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148851%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148851%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all.%20I%20have%20had%20the%20same%20issue%20with%20the%20BSOD.%20I%20wanted%20to%20just%20let%20anyone%20who%20might%20have%20the%20same%20hardware%20I%20have%20know%20what%20I%20did%20to%20get%20this%20update%20working.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHardware%3A%3C%2FP%3E%0A%3CP%3EASUSTeK%20X299%20MARK%202%3CBR%20%2F%3ESambsung%20SSD%20960%20EVO%201TB%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20I%20did%3A%3C%2FP%3E%0A%3CP%3EI%20read%20on%20here%20about%20updating%20the%20motherboard%20so%20I%20updated%20my%20ASUS%20BIOS%20version%20to%201102%20(most%20recent)%20just%20last%20night.%20I%20then%20used%20the%201709%20update%20assistant%20one%20more%20time%20and%20it%20worked%20flawlessly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEdit%3A%3C%2FP%3E%0A%3CP%3EAnother%20thing%20to%20note%20that%20I%20did%20that%20may%20or%20may%20not%20have%20made%20a%20difference%20was%3A%3C%2FP%3E%0A%3CP%3EI%20deleted%20anything%20in%20the%20C%3A%5CWindows%5CSoftwareDistribution%5CDownload%20folder%3C%2FP%3E%0A%3CP%3EDeleted%20the%20few%20folders%20off%20the%20C%3A%20drive%20the%20failed%20installations%20added%3C%2FP%3E%0A%3CP%3ERenamed%20the%20windows%20update%20database%20files%20(.edb%20and%20.jfm%20files)%20located%20in%20C%3A%5CWindows%5CSoftwareDistribution%5CDataStore%3C%2FP%3E%0A%3CP%3ERenamed%20the%20Windows%20Update%20Log%20folder%20located%20in%20C%3A%5CWindows%5CSoftwareDistribution%5CDataStore%20as%20well.%3C%2FP%3E%0A%3CP%3ERenamed%20the%20SLS%20folder%20in%20C%3A%5CWindows%5CSoftwareDistribution%3C%2FP%3E%0A%3CP%3ERenamed%20the%20ReportingEvents.log%20in%20C%3A%5CWindows%5CSoftwareDistribution%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148790%22%20slang%3D%22en-US%22%3EHi%20all%2C%20%26nbsp%3B%20i%20have%20the%20same%20problem%2C%20MS%20phone%20and%20chat%20supp...%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148790%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ei%20have%20the%20same%20problem%2C%20MS%20phone%20and%20chat%20support%20cant%20help.%20If%20you%20try%20to%20contact%20the%20german%20MS%20support...%20let%20it%20be.%20horrible...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Emy%20hardware%3A%20msi%20x99a%20gaming%207%2C%20intel%206850k%2C%20nvidia%20gtx%201080%2C%20m2%20ssd%20samsung%2C%2032gb%20DDR4-2400%20ram.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBluescreen%20with%20%3CA%20id%3D%22link_cbc497504bc94d_2%22%20class%3D%22lia-link-navigation%20child-thread%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-10%2F1703-gt-1709-BSOD-0xc00000bb-on-devices-with-NVMe-SSD-s%2Fm-p%2F148240%23M763%22%20target%3D%22_blank%22%3E0xc00000bb%3C%2FA%3E%20or%20if%20windows%20can%20start%2C%20%3CSPAN%20class%3D%22short_text%22%3E%3CSPAN%20class%3D%22%22%3Enote%20appears%3C%2FSPAN%3E%3C%2FSPAN%3E%20%22update%201709%20failed%22...%20can%20do%20nothing%20to%20fix%20this%20issue%2C%20no%20workarround%20helps%2C%20new%20windows%20installation%20doenst%20help%20too.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20Microsoft%2C%20when%20we%20can%20expect%20the%20fix%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-148240%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-148240%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ehe%20MS%2C%20not%20possible%20to%20answer%3F%3F%20You%20all%20sleeping%20or%20what%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147392%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147392%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Michael%2C%3C%2FP%3E%0A%3CP%3Ei%C2%B4m%20still%20hanging%20on%20windows%2010%20version%2010586%2C%20it%C2%B4s%20not%20possible%20to%20use%20update%201703%20and%201709%2C%20since%20oktober%20i%C2%B4m%20still%20in%20a%20updateloop.%20how%20can%20i%20make%20my%20updates%3F%3F%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3EWin%2010%20pro%2064bit%3C%2FP%3E%0A%3CP%3EMSI%20X99%20Board%3C%2FP%3E%0A%3CP%3Eintel%20I7-6800k%3C%2FP%3E%0A%3CP%3E32%20Gb%20RAM%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3ENVMe%20SSD%20960%20as%20bootmedium%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Ethe%20main%20problem%20is%2C%20i%20use%20my%20pc%20for%20work%2C%20and%20every%20day%20pc%20downloads%20the%20latest%20updates.%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Ebut%20it%20failed%20everytime.%20because%20of%20missing%20os%20driver%20for%20the%20ssd.%20(0xc00000bb)%2C%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Eso%20restart%20and%20windows%20get%20back%20to%20the%20old%2010586%20windows.%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Ebut%20everyday%20this%20updates%20starts%20from%20beginning%2C%20i%20cannot%20stop%20it.%20and%20it%20kill%C2%B4s%20my%20datatransfer%20volume%20for%20nothing.%20how%20can%20i%20stop%20it%3F%3F%3F%20and%20is%20it%20sure%20that%20the%20problem%20is%20fixed%20and%20of%20january%3F%3F%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Eor%2C%20how%20can%20i%20stop%20the%20windows%20from%20updating%3F%20only%20for%20the%20time%20MS%20need%C2%B4s%20for%20fixing%20the%20problem.%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Ei%20read%20in%20many%20forums%2C%20that%20many%20people%20with%20samsung%20ssd%20nvm%20has%20the%20same%20problem%2C%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Enot%20only%20a%20few.%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Ei%20write%20to%20samsung%20many%20emails%2C%20but%20the%20only%20thing%20they%20told%20me%2C%20that%20it%20is%20not%20a%20problem%20from%20samsung%2C%20it%20was%20a%20problem%20from%20ms%2C%20they%20have%20to%20fix%20it.%20for%20my%20opinion%20they%20have%20to%20make%20i%20big%20red%20sticker%20on%20there%20ssd%20medims%3A%20DONT%20USE%20IT%20AS%20BOOTMEDIUM%20WITH%20WIN10.%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Eso%20what%20can%20i%20do%3F%3F%20someone%20any%20help%2C%20or%20tips%20for%20me%3F%3F%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Ei%20will%20not%20going%20to%20back%20win%207.%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Eplesase%20MS%20help%2C%20let%20your%20user%20not%20standing%20in%20the%20rain%20like%20samsung!%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Emeikel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147086%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147086%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20ASUS%20X299-A%20Prime%20MOB%20and%20a%20Samsung%20960%20Pro%20NVMe%20SSD.%26nbsp%3B%20I%20have%20been%20waiting%20since%20October%20for%20a%20fix%20to%20upgrade%20to%201709.%26nbsp%3B%20Nothing%20yet.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147076%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147076%22%20slang%3D%22en-US%22%3ESorry%20to%20Say%20that%20i%20tried%20to%20inject%20the%20Fix%2C%20but%20It%20didn't%20solve%20the%20problem%2C%20for%20me.%20Pheraphs%20because%20my%20issue%20is%20due%20to%20Samsung%20NVMe%20and%20not%20Intel%20NVMe%20drive.%20Hope%20that%20the%20upcoming%20patches%20Will%20solve%20this%20problem%20even%20forum%20x99%20non%20Asus%20motherboards...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147075%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147075%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20heard%20from%20various%20Microsoft%20reps%20for%20weeks%20and%20weeks%20and%20weeks%20that%20the%20fix%20is%20coming.%26nbsp%3B%20Yet%20it%20never%20comes.%26nbsp%3B%20I%20will%20believe%20it%20when%20I%20see%20it.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147074%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147074%22%20slang%3D%22en-US%22%3E%3CP%3E%22%3CSPAN%3ENext%20week's%20cumulative%20update%20is%20expected%20to%20address%20the%20second%20problem%2C%20which%20occurs%20with%20x299%20chipsets%2C%20mostly%20from%20ASUS.%22%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThank%20you%20for%20replying%20Michael%20and%20letting%20us%20know%2C%20the%20above%20is%20what%20I%20have%20been%20waiting%20for!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147068%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147068%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20update%2C%20Michael.%26nbsp%3B%20It's%20nice%20to%20know%20that%20this%20problem%20hasn't%20been%20ignored!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147067%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147067%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20mentioned%20before%2C%20there%20were%20two%20different%20issues%20being%20worked%20on.%26nbsp%3B%20The%20first%20one%2C%20which%20affected%20only%20certain%20Intel%20NVMe%20devices%2C%20is%20already%20fixed%20in%20the%20latest%20cumulative%20update.%26nbsp%3B%20Next%20week's%20cumulative%20update%20is%20expected%20to%20address%20the%20second%20problem%2C%20which%20occurs%20with%20x299%20chipsets%2C%20mostly%20from%20ASUS.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'm%20still%20checking%20to%20confirm%20that%20these%20will%20be%20published%20as%20dynamic%20updates%20so%20that%20they%20are%20automatically%20installed%20as%20you%20are%20upgrading%20to%20Windows%2010%201709.%26nbsp%3B%20(Until%20that%20happens%2C%20you'll%20still%20have%20the%20problem%20unless%20you%20manually%20inject%20the%20update%20yourself%2C%20which%20is%20not%20a%20simple%20task.)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147053%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147053%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20is%20clear%20now%20that%20Microsoft%20is%20never%20going%20to%20fix%20this%20issue.%26nbsp%3B%20If%20you%20keep%20getting%20the%20error%20when%20trying%20to%20reboot%20you%20have%20two%20choices%20%3A%20Either%20clean%20install%20or%20stay%20on%201703.%26nbsp%3B%20I%20think%20it%20is%20very%20unlikely%20Microsoft%20will%20ever%20bother%20to%20issue%20a%20fix%20for%20the%20issue.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147052%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147052%22%20slang%3D%22en-US%22%3E%3CP%3EWell...%20no%20good%20news%2C%20till%20now.%200xc00000bb%20is%20still%20a%20big%20black%20hole...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESome%20times%20ago%2C%20I%20tried%20to%20contact%20MSI.%20They%20excluded%20that%20the%20issue%20is%20%22mobo%20or%20bios%22%20related%2C%20and%20suggested%20me%20to%20format%20and%20do%20a%20clean%20install.%20Oh%2C%20well...%20and%20my%20work%3F%20My%20customised%20production%20software%3F%20I%20use%20the%20workstation%20as%20work%20station...%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESamsung%20released%20the%205.2%20version%20of%20Magician%20software%2C%20but%20not%20new%20driver%20or%20new%20firmware%20(I%20have%20the%20buggy%203b6qcxp7...%20%3A(%20).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20updated%20the%20Intel%20Rapid%20Storage%20Engine%20to%20the%20last%20version.%200xc00000bb%20and%20update%20failed.%20And%20it%20is%20able%20to%20see%20only%204%20disks%20of%20the%207%20installed%20on%20my%20system.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft%20said%20that%20the%20fix%20will%20come%20in%20late%20January%2C%20but%20now%20the%20world%20fights%20versus%20Meltdown%2C%20Spektre%20and%20the%20other%20CPU%20vulnerabilities...%20I%20don't%20think%20that%20they%20are%20working%20on%20a%20problem%20that%20affects%20a%20little%20number%20of%20machines...%20I%20hope%20I'm%20wrong%2C%20but...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ELet's%20see...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-147035%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-147035%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20is%20the%20status%20of%20this%20fix%3F%20Been%20Pausing%20updates%20for%20months%20on%20Win%2010%20pro%20because%20of%20this...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-146111%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-146111%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%20for%20me.%20MSI%20X99a%20gaming%20pro%20carbon.%20Samsung%20evo%20960%20m2.%3C%2FP%3E%0A%3CP%3EThis%20is%20going%20on%20for%20months.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20really%20annoys%20me%20is%20that%20the%20update%20prompts%20become%20more%20and%20more%20obnoxious.%20Please%20Microsoft%20stop%20trying%20to%20force%20an%20update%20on%20me%20that%20is%20broken!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143886%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143886%22%20slang%3D%22en-US%22%3Ehello%2C%3CBR%20%2F%3Ethanks%20for%20response.%20my%20pc%20is%20still%20hanging%20on%20update%201607%20and%201703%20no%20one%20is%20possible.%3CBR%20%2F%3Eso%20i%20have%20to%20wait%20for%20the%20fix%20in%20end%20of%20january.%20when%20nothing%20comes%20i%20will%20make%20a%20new%20fresh%20installing.%20but%20i%20don%C2%B4t%20like%20to%20do%20this%2C%20because%20my%20sytem%20is%20very%20full%20and%20i%20have%20to%20install%20everything%20new%2C%20this%20boring.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143646%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143646%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Microsoft%20guy%20said%20there%20would%20be%20a%20fix%20end%20of%20January.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20still%20doubt%20that%20with%20all%20the%20updates%20their%20currently%20doing%20regarding%20meltdown%20and%20spectre.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20waited%20since%20October%20for%20a%20fix%20and%20just%20cba%20anymore%20and%20went%20for%20a%20fresh%20install%20today.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECurrently%20running%20v1709%20on%20my%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMotherboard%3A%20X299%20MSI%20GAMING%20M7%20ACK%3C%2FP%3E%0A%3CP%3ESSD%3A%20Samsung%20960%20Pro.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOnly%20because%20I%20use%20this%20drive%20for%20OS%20only%20I%20could%20afford%20to%20do%20a%20fresh%20install%20without%20fear%20of%20deleting%20anything%20important%20and%20starting%20again.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt's%20just%20the%20v1703%20updating%20to%20v1709%20that%20bricks%20the%20pc%20basically.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDoing%20a%20fresh%20install%20then%20search%20for%20updates%20gives%20you%20the%20v1709%20without%20ever%20being%20on%20v1703%20so%20it%20works%20and%20if%20their%20isn't%20a%20fix%20by%20the%20end%20of%20this%20month%20then%20just%20go%20ahead%20and%20do%20this.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143628%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143628%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eno%20one%20can%20help%3F%3F%3F%20no%20idea%3F%20nothing.%20this%20sucks.%20every%20day%20my%20pc%20is%20still%20in%20a%20updateloop.%3C%2FP%3E%0A%3CP%3Ei%20waste%20so%20much%20time%20for%20this%20and%20ms%20is%20not%20able%20to%20fix%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-142175%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-142175%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20same%20problems%20here%20since%20Sept.%202017%20no%20update%20possible.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3EWIN%2010%2064%20Bit%3C%2FP%3E%0A%3CP%3EMSI%20X99A%20Raider%20(%20MS-7885)%20BIOs%20P.50%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3ESamsung%20SSD%20NVMe%20960%20Treiberversion%2010.0.10586.0%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3Eplease%20MS%20can%20you%20help!!!%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F26441i599E1743F848B742%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22large.jpg%22%20title%3D%22large.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-141359%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-141359%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Update%20from%201703%20to%201709%20dont%20work!%3C%2FP%3E%0A%3CP%3EError%200xc00000bb%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMotherboard%20MSI%20MS-7885%20Bios%20H.C0%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140834%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140834%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20a%26nbsp%3BMSI%20X99A%20Godlike%20Gaming%20Carbon%20and%26nbsp%3BSamsung%20SSD%20960%26nbsp%3BEvo%20nVME%20combination%20and%20suffering%20the%20same%20failure%20during%201703-%26gt%3B1709%20update%20so%20your%20bug%20is%20not%20just%20confined%20to%20X299%20and%2For%20ASUS.%20Maybe%20your%20MS%20engineers%20could%20inform%20MSI%20to%26nbsp%3Bget%20them%26nbsp%3Bto%20provide%20a%20BIOS%20fix%20for%20my%20board%20(if%20needed)%20as%20I%20very%20much%20doubt%20they%20would%20listen%20to%20me.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere's%20hoping%20you%20get%20a%20suitable%20solution%20to%20all%20our%20bugs%20when%20installing%201709%20before%20you%20remove%20support%20for%201703.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-140052%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-140052%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here%20with%20MSI%20X99S%20Gaming%207%20(MS-7885)%20Motherboard%20and%20Samsung%20SSD%20960%20PRO%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWindows%2010%20tried%2022%20times%20to%20install%20the%20update%20and%20failed.%20The%20update%20routine%20is%20totaly%20dumb%20and%20does%20not%20recognize%20that%20the%20update%20does%20not%20work%20on%20my%20system%2C%20instead%20it%20ended%20me%20being%20in%20an%20update%20loop%20forever.%20To%20make%20matters%20worse%20I%20was%20not%20always%20allowed%20to%20stop%20the%20update%20process.%20Seriously%20Microsoft%20if%20you%20force%20me%20to%20an%20update%20make%20sure%20it%20works!%20We%20are%20in%202017%20and%20not%201997...%20never%20heard%20of%20user%20experience%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere%20the%20nice%20list%20of%20update%20fails%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20388px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F26156i0A17BB24672AB513%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22winup.PNG%22%20title%3D%22winup.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139987%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139987%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BI%20have%20the%20same%20issue%20I%20have%20the%20MSI%20X99A%20Gaming%20Pro%20Carbon%20(MS-7A20)%20Mother%20Board%20with%20a%20Intel%20i7-5820K%20CPU%203.30GHz%20and%20a%20Samsung%20SSD%20960%20Pro%20M.2%201TB%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20and%20I%20cannot%20update%20to%20the%20latest%20build%20of%20windows%2010%20this%20is%20a%20major%20failing%20from%20microsoft.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-139565%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-139565%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20what%20it's%20worth.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMSI%20X99A%20XPOWER%20GAMING%20TITANIUM%20LGA%202011-v3%20Intel%20X99%20SATA%206Gb%2Fs%20USB%203.1%20Extended%20ATX%20Motherboards%20-%20Intel%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIntel%20750%20Series%20AIC%201.2TB%20PCI-Express%203.0%20x4%20MLC%20Internal%20Solid%20State%20Drive%20(SSD)%20SSDPEDMW012T4X1%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGetting%26nbsp%3B0xc00000bb%20error%20after%20reboot.%26nbsp%3B%20Have%20to%20go%20back%20through%20UEFI%20boot%20menu%20and%20reselect%20above%20drive%20in%20order%20to%20boot%20back%20in%20to%20windows.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138935%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138935%22%20slang%3D%22en-US%22%3E%3CP%3EDo%20not%20waste%20your%20time.%20It's%20not%20our%20fault%20and%20I%20personally%20do%20not%20miss%20the%20creator%20update.%20Switch%20of%20the%20Windows%20Update%20service%20and%20wait%20for%20the%20bug%20fix.%20Shame%20on%20Microsoft%20that%20they%20forgot%20to%20consider%20these%20%22technical%20state%20of%20the%20art%20configurations%22%20and%20finally%20not%20be%20able%20to%20provide%20a%20solution%20in%20acceptable%20time%20frame.%20Furthermore%20although%20they%20collect%20so%20much%20informations%20from%20every%20installation%20they%20do%20not%20stop%20updating%20those%20systems!%20Obviously%20they%20collect%20the%20wrong%20information%20%3B-)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138524%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138524%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20way%20for%20my%20system.%20When%20BSOD%20occurs%2C%20every%20button%20(F1%20for%20the%20recovery%2C%20F8%20for%20boot%20options...)%20results%20in%20nothing.%20I'm%20able%20only%20to%20enter%20the%20UEFI%20or%20to%20%22load%20another%20OS%22%20with%20F9.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20I%20tried%20to%20disable%20the%20driver%20signature%20in%20Command%20Prompt%2C%20with%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebcdedit%20%2Fset%20testsigning%20off%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20did%20reboot%20the%20pc%2C%20then%20I%20tried%20to%20update.%20And%20I%20received%20the%20same%20error%3A%20BSOD%20with%200xc00000bb.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138228%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138228%22%20slang%3D%22en-US%22%3EA%20temporary%20workaround%20is%20reboot%20untill%20you%20get%20the%20blue%20screen%2C%20press%20F8%20for%20startup%20settings.%3CBR%20%2F%3EThen%20select%20(7%20Disable%20Driver%20Signature%20Enforcement.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20boots%20the%20PC.%20Sometimes%20it%20boots%20after%20the%20first%20reset%2C%20sometimes%20it%20comes%20up%20with%20the%20BSOD.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138077%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138077%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20the%20same%20board%20and%20ssd%20I%20have%20and%20I%20also%20meet%20this%20issue%20during%20updating%20from%201703%20to%201709%2C%20this%20is%20annoying%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137771%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137771%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%0A%3CP%3EI%20have%20the%20save%20issue%20during%20Update%20from%201607-%26gt%3B1709%20several%20times.%20My%20configuration%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBoard%3A%20MSI%20X99A%20XPoWER%20GAMING%20TITATIUM%3C%2FP%3E%0A%3CP%3EBIOS%3A%20Latested%20(MS-7A21)%3C%2FP%3E%0A%3CP%3ESystem%20Disk%3A%20SAMSUNG%20MZVPW128HEGM%20(SSD%20SM961-NVMe%20128GB%20M.S%20PCIe)%3C%2FP%3E%0A%3CP%3EI%20would%20strongly%20appreciate%20if%20Microsoft%20stop%20updating%20my%20system%20to%201709%20until%20the%20issue%20was%20fixed!%3C%2FP%3E%0A%3CP%3ESecurity%20updates%20are%20welcome.%20This%20must%20be%20possible.%20In%20this%20case%20waiting%20for%20the%20fix%20is%20tolerable.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137573%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137573%22%20slang%3D%22en-US%22%3E%3CP%3Ehey%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo%20when%20i%20used%20windows%20upgrade%20assistant%20it%20basically%20messed%20up%20my%20pc%20and%20turned%20from%20the%20initial%20error%20code%26nbsp%3B0xc00000bb%20to%20error%20code%26nbsp%3B%26nbsp%3B0x80242006.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAny%20idea%20how%20to%20fix%20this%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI've%20looked%20online%20and%20tried%20a%20few%20things%20and%20none%20seemed%20to%20have%20worked.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EObviously%20once%20this%20has%20been%20fixed%20i'd%20still%20have%20the%20error%20code%26nbsp%3B%3CSPAN%3E0xc00000bb%20waiting%20for%20me%20but%20at%20least%26nbsp%3BI've%26nbsp%3Bticked%20off%20one%20in%20the%20process.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAlso%20I%20know%20Asus%20is%20probably%20the%20most%20popular%20brand%20of%20motherboards%20but%20have%20you%20guys%20been%20in%20contact%20with%20MSI%3F%20or%20even%20gigabyte%20about%20the%20problem%3F%20Neither%20have%20a%20fix%20and%20it%20seems%20no%20one%20even%20talks%20about%20brands%20other%20than%20Asus.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137073%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137073%22%20slang%3D%22en-US%22%3E%3CP%3EHello!%20My%20name%20is%20Michele%2C%20from%20Italy.%20I've%20a%20Samsung%20960%20Pro%20on%20MSI%20X99A%20Workstation%20(beta%20bios%20v.%201.15)%2C%20and%20even%20my%20system%20suffers%20of%20this%20issue.%20Error%200xc00000bb%2C%20if%20I%20update%20via%20Windows%20Update%20or%20Windows%20Update%20Assistant%3B%20error%26nbsp%3B%3CSPAN%3E0xc1900101%20-%200x20017%20if%20I%20try%20to%20update%20via%20Media%20Creation%20Tool.%26nbsp%3BMy%20PC%20is%20a%20custom%20built%20Xeon%20based%20workstation%2C%20and%20I%20use%20it%20for%20my%20work%2C%20so%20I%20can't%20have%20a%20clean%20install...%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20tried%20to%20open%20a%20ticket%20with%20MSI.%20MSI%20tried%20to%20install%20the%20update%20on%20a%20system%20like%20the%20one%20I%20have%2C%20and%20they%20said%26nbsp%3B%22no%20problems%20here!%22%20and%20closed%20the%20ticket.%20The%20official%20bios%20release%20is%20locked%20at%201.0%20(2016).%20They%20sent%20me%20a%20beta%20bios%20(1.15)%20but%20I%20still%20have%20the%20issue.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ENow%20Windows%20Update%20did%20another%20download...%20I%20hope%20to%20have%20my%20troubles%20fixed%2C%20but%20I%20don't%20think%20so.%20I'll%20wait%20for%20the%20next%20release...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137019%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137019%22%20slang%3D%22en-US%22%3E%3CP%3EI%20tried%20upgrading%20to%201709%20after%20the%20ASUS%20BIOS%20upgrade%20to%201004%20and%20still%20a%20no%20go.%26nbsp%3B%20I%20still%20get%20error%200XC00000bb.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137000%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137000%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20basic%20problem%3A%26nbsp%3B%20Memory%20fragmentation%20during%20system%20initialization%20forces%20IO%20buffers%20into%20high%20memory.%26nbsp%3B%20So%20yes%2C%20the%20hardware%20in%20the%20system%20has%20a%20definite%20impact%20on%20that%20fragmentation%20(each%20device%20reserves%20an%20address%20range).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhile%20we%20have%20provided%20details%20about%20the%20issue%20to%20ASUS%2C%20we%20are%20not%20aware%20of%20what%20they%20changed%20in%20the%201004%20firmware.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3E-Michael%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136998%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136998%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20update%20Michael%2C%20really%20appreciate%20it!%3CBR%20%2F%3E%3CBR%20%2F%3EWill%20wait%20till%20end%20of%20January%20and%20check%20back%20then%20%3A)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136996%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136996%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20update%20Michael.%3C%2FP%3E%0A%3CP%3EIs%20there%20any%20indication%20as%20to%20why%20the%201004%20update%20did%20not%20resolve%20it%20for%20everyone%3F%3C%2FP%3E%0A%3CP%3EDid%20MS%20work%20together%20with%20ASUS%20on%20this%20update%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20there%20something%20those%20of%20us%20whom%201004%20did%20not%20resolve%20the%20issue%20could%20try%3F%3C%2FP%3E%0A%3CP%3EAre%20there%20other%20factors%20which%20could%20interfere%3F%26nbsp%3B%20Installed%20Memory%20size%2C%20video%20card%2C%20etc%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20my%20case%2C%20another%20member%20with%20the%20same%20motherboard%2C%20m.2%20drive%20and%20using%20the%20ms%20nvme%20driver%20was%20able%20to%20perform%20the%20upgrade.%26nbsp%3B%20I%20replicated%20that%20configuration%20and%20mine%20was%20not%20successful.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136990%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136990%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20continuing%20to%20work%20on%20it.%26nbsp%3B%20A%20few%20points%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20December%20update%20does%20not%20include%20a%20fix%20for%20this%20problem.%26nbsp%3B%20We%20are%20hoping%20to%20have%20a%20fix%20in%20place%20by%20the%20end%20of%20January.%3C%2FLI%3E%0A%3CLI%3EThe%20updated%20Asus%20firmware%20(1004)%20has%20addressed%20the%20issue%20for%20many%20people.%3C%2FLI%3E%0A%3CLI%3EThere%20is%20a%20block%20in%20place%20that%20keeps%20Windows%20Update%20from%20offering%20Windows%2010%201709%20to%20affected%20systems.%26nbsp%3B%20But%20if%20you%20go%20into%20Settings%20and%20manually%20check%20for%20updates%2C%20this%20bypasses%20the%20block%20because%20you%20are%20%22seeking%22%20the%20update.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3E-Michael%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136985%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136985%22%20slang%3D%22en-US%22%3E%3CP%3ENope%20%3CSPAN%3EKB4054517%20(12.12.2017)%20also%20didn't%20work.%20Got%20still%20the%20Error%26nbsp%3B0xc00000bb.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20did%20try%20it%20with%20the%20normal%20Win%20Updater%20and%20with%20the%20Upgrade%20Assistent%2C%20both%20got%20the%20error.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIt%20really%20feels%20like%20a%20joke%20that%20Microsoft%20and%20the%20Manufacturers%20didnt%20patch%20it%20already.%201709%20was%20released%20end%20of%26nbsp%3BOctober.%26nbsp%3BNow%20we%20have%20mid%20December%20and%20it's%20still%20not%20fixed...%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F25569i89B6CFB19DCCDD1C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%2220171213_203337.jpg%22%20title%3D%2220171213_203337.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136949%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136949%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F101089%22%20target%3D%22_blank%22%3E%40Erkan%20Isik%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EMicrosoft%20released%20yesterday%20a%20new%20Update%20called%20KB4054517.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4054517%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4054517%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWill%20try%20this%20update%2C%20hope%20it%20will%20fix%20the%26nbsp%3B%3CSPAN%3E0xc00000bb%20error%20for%20nVME%20drives.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%0A%3CP%3EPlease%20let%20us%20know%20if%20this%20works.%26nbsp%3B%20Thanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136905%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136905%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20released%20yesterday%20a%20new%20Update%20called%20KB4054517.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4054517%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4054517%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWill%20try%20this%20update%2C%20hope%20it%20will%20fix%20the%26nbsp%3B%3CSPAN%3E0xc00000bb%20error%20for%20nVME%20drives.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136657%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136657%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20Asus%201004%20bios%20fixed%20it%20for%20me.%20I%20didn't%20have%20to%20do%20any%20bios%20tweaks%20that%20Tim%20Gall%20did.%20I%20just%20updated%20the%20bios%2C%20re-ran%20the%20Windows%2010%20Update%20Assistant%20(didn't%20create%20USB%20media)%2C%20and%20then%20the%20update%20went%20through%20smoothly.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMy%20config%3A%3C%2FP%3E%0A%3CP%3EASUS%20Prime%20X299-Deluxe%3C%2FP%3E%0A%3CP%3ESamsung%20960%20Pro%20(Samsung%20NVME%20driver)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136520%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136520%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20it%20looks%20like%20there%20was%20nothing%20in%20the%20patch%20Tuesday%20cumulative%20update%20for%20December.%26nbsp%3B%20So%20no%20fix%20for%20us%20trying%20to%20upgrade%20to%201709%20goes%20on%20and%20on%20from%20Microsoft.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136237%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136237%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%202%20hours%20wasted%20making%20the%20attempt.%26nbsp%3B%20I%20uninstalled%20the%20Samsung%20NVME%20driver%2C%20rebooted%2C%20ensured%20the%20MS%20NVME%20drive%20was%20in%20use%2C%20performed%20the%20upgrade%20attempt%20using%20the%20Windows%2010%20upgrade%20assistant%20and%20same%20BSOD%20result.%26nbsp%3B%20This%20is%20getting%20very%20tiresome.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136149%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136149%22%20slang%3D%22en-US%22%3E%3CP%3EI%20know%20that%20the%20bios%20update%20fixed%20it%20for%20me%20.%20I%20want%20to%20add%20for%20those%20who%20might%20still%20have%20the%20issue%20after%20updating%20to%20the%20new%20bios%20from%20asus%20that%20I%20was%20on%20the%20microsoft%20nvme%20driver%20when%20I%20did%20the%20update.%20I've%20done%20this%20because%20of%20the%20current%20firmware%20issue%20with%20the%20960%20pro.%20This%20might%20help%20or%20not%20I%20don't%20know.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135844%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135844%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue%20with%20the%201709%20windows%20update%20with%20an%20x299%20motherboard%20and%20a%20samsung%20960%20ssd%20NVME...please%20fix%20it%20ASAP!!!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135836%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135836%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20is%20not%20a%20fix%20for%20the%20layman%20PC%20user%20out%20there.%26nbsp%3B%20These%20are%20BIOS%20tweaks%20for%20a%20very%20experienced%20user.%26nbsp%3B%20The%20bottom%20line%20is%20the%20new%20BIOS%201004%20from%20ASUS%20does%20not%20fix%20the%201709%20upgrade%20problem%20for%20people%2C%20and%20still%20nothing%20from%20Microsoft.%26nbsp%3B%20Microsoft%20nor%20ASUS%20has%20done%20a%20thing%20to%20help%20people%20upgrade%20from%201709%20if%20they%20have%20a%20NVMe%20M.2%20SSD%20drive.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135827%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135827%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Steven%2C%3C%2FP%3E%0A%3CP%3EI'll%20put%20in%20some%20more%20detail%20about%20how%20I%20got%20my%20system%20to%20update%20in%20the%20hope%20its%20of%20some%20help%20to%20anyone.%3C%2FP%3E%0A%3CP%3EAfter%20updating%20bios%20to%201004%20I%20made%20some%20adjustments%20to%20bios%20%3CSTRONG%3EPCH%20Storage%20Configuration%3C%2FSTRONG%3E%20and%20%3CSTRONG%3EBoot%20-%26gt%3B%20CSM%20%3C%2FSTRONG%3Ebefore%20upgrading%20to%20FCU1709.%3C%2FP%3E%0A%3CP%3EFor%20%3CSTRONG%3EPCH%20Storage%20Cofiguration%3C%2FSTRONG%3E%20I%20set%3A%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ESATA%20Controllers%3C%2FSTRONG%3E%20to%20%3CEM%3E%3CSTRONG%3Edisabled%3C%2FSTRONG%3E%3C%2FEM%3E%20(the%20topmost%20option).%20%3CEM%3EI%20enabled%20it%20again%20once%20the%20upgrade%20was%20complete.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20%3CSTRONG%3EBoot%20-%26gt%3BCSM%3C%2FSTRONG%3E%20I%20set%20it%20to%20%3CSTRONG%3E%3CEM%3Eenabled%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBoot%20Devices%20Control%3C%2FSTRONG%3E%20set%20to%20%3CEM%3E%3CSTRONG%3EUEFI%20only%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBoot%20Network%3C%2FSTRONG%3E%20and%20%3CSTRONG%3EBoot%20Storage%20Devices%3C%2FSTRONG%3E%20set%20to%20%3CEM%3E%3CSTRONG%3Eignore%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBoot%20from%20PCIE%20expansion%20devices%3C%2FSTRONG%3E%20to%20%3CEM%3E%3CSTRONG%3EUEFI%20first%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20updated%20from%20USB%20using%20a%20fresh%20copy%20built%20with%20the%20Media%20Creation%20Tool%20(FCU%201709).%3C%2FP%3E%0A%3CP%3EI%20started%20the%20update%20from%20windows.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EUpdate%20went%20through%20smoothly.%20After%20the%20update%20I%20had%20to%20reinstall%20my%20antivirus%20and%20a%20few%20drivers%20but%20nothing%20drastic.%20Ive%20read%20about%20other%20experiencing%20that%20from%20the%201709%20update%20but%20it%20wasnt%20a%20drama%20to%20fix.%20I%20only%20noticed%20something%20off%20with%20a%20few%20drivers%20when%20stressing%20my%20machine%20with%20an%20intensive%20game%20after%20the%20update.%3C%2FP%3E%0A%3CP%3ESeems%20spot%20on%20now.%20Hope%20this%20info%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135823%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135823%22%20slang%3D%22en-US%22%3E%3CP%3EThe%201004%20BIOS%20Update%20%3CSTRONG%3EDID%20NOT%26nbsp%3B%3C%2FSTRONG%3Efix%20the%20problem%20for%20me.%26nbsp%3B%20I%20just%20wasted%20an%20hour%20attempting%20the%20upgrade%20using%20the%20Windows%2010%20Update%20Assistant%20and%20it%20failed%20with%20the%20same%20BSOD.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EASUS%20Prime%20X299-Deluxe%3C%2FP%3E%0A%3CP%3ESamsung%20960%20Pro%20NVME%20M.2%20SSD%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135809%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135809%22%20slang%3D%22en-US%22%3E%3CP%3ENever%20mind%20I%20just%20found%20it%20under%20others%20in%20the%20os%20selection.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20can%20confirm%20that%20this%20fixes%20the%20issue%20for%20those%20with%20the%20Asus%20X299%20Deluxe%20board.%20I'm%20now%20on%20the%201709%20version.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135808%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135808%22%20slang%3D%22en-US%22%3E%3CP%3EWhere%20do%20you%20see%20that%20bios%20revision%20%3F%20I'm%20on%20the%20asus%20support%20website%20for%20the%20X299%20deluxe%20and%20I'm%20still%20seeing%20the%20802.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135807%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135807%22%20slang%3D%22en-US%22%3E%3CP%3EASUS%20released%20an%20%3CSTRONG%3Eupdated%20bios%20(1004)%20for%20the%20Prime-X299-deluxe%3C%2FSTRONG%3E%20today%20that%20fixed%20the%20issue%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135742%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135742%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20problem%20as%20well%2C%20and%20have%20not%20noticed%20any%20block.%3C%2FP%3E%0A%3CP%3ENow%20I%20turned%20the%20automatic%20update%20off%2C%20since%20my%20PC%20tried%20to%20update%20at%20least%2010%20times%2C%20consuming%20all%20network%20bandwidth.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20my%20config%3A%3C%2FP%3E%0A%3CP%3ESamsung%20960%20EVO%20SSD%20M.2%202280%20-%20500GB%20%3CBR%20%2F%3EASUS%20PRIME%20X299-DELUXE%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135595%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135595%22%20slang%3D%22en-US%22%3E%3CP%3EI%20to%20have%20been%20having%20this%20issue%20with%20an%20X99-A%20MSI%20board%20built%20by%20Origin%20with%3A%3C%2FP%3E%0A%3CP%3EMSI%20Godlike%20Gaming%20Carbon%3C%2FP%3E%0A%3CP%3Ew%2F%20Samsung%20960%20Evo%20NVMe%20and%20a%20Samsung%20850%20SSD%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20update%20appeared%20to%20have%20issues%20and%20recently%20seemed%20to%20try%20to%20auto%20update%20itself%20hosing%20my%20install%20to%20be%20stuck%20on%20a%20blank%20boot%20screen%2C%20no%20amount%20of%20repairing%20startup%20fixed%20it%20so%20I%20went%20back%20to%20a%20recovery%20USB%20from%20Origin.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20seem%20to%20agree%20with%20the%20group%20here%20that%20the%20common%20denominator%20seems%20to%20be%20the%20960%20NVMe%20but%20that%20could%20just%20be%20that%20its%20a%20common%20NVMe%20drive.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EConsidering%20its%20already%20hosed%20my%20install%20and%20I've%20gone%20back%20to%20a%20blank%201703%20install%20I%20may%20try%20some%20of%20the%20workarounds%20to%20get%20to%201709.%20What's%20frustrating%20to%20me%20right%20now%20is%20that%20the%20Windows%20Update%20is%20stuck%20wanting%20to%20install%201709%20so%20bad%20that%20because%20its%20failed%20on%20restart%20theres%20no%20way%20I%20can%20see%20to%20force%20it%20to%20redownload%20updates%20or%20check%20for%20new%20ones.%20I've%20gone%20so%20far%20as%20delete%20the%20download%20files%20expecting%20it%20to%20check%20and%20attempt%20redownload.%20Nope%2C%20still%20thinks%20its%20there%20and%20still%20thinks%20it%20wants%20me%20to%20restart%20thinking%20it%20will%20install.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20attempted%20to%20use%20the%20Microsoft%20tool%20again%20to%20download%20the%20update%20on%20Wednesday%20and%20it%20didn't%20seem%20to%20pull%20any%20new%20updates%20as%20it%20ended%20in%20the%20same%20error%20on%20install.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnother%20odd%20thing%20is%20that%20for%20the%20first%20time%20I've%20had%20my%20overclocking%20profile%20fail%20twice%20after%20shutting%20down%20the%20PC%20and%20on%20the%20next%20boot%20up%20the%20next%20day%20it%20fails%2C%20I%20reload%20the%20config%20and%20it's%20fine.%20All%20hardware%20checks%20out.%20Just%20odd.%20No%20issues%20until%20this%201709%20stuff%20started.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135579%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135579%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20also%20heard%20of%20countless%20people%20with%20different%20model%20Motherboards%20that%20have%20this%20problem.%26nbsp%3B%20It%20is%20not%20just%20ASUS.%26nbsp%3B%20Gigabyte%20and%20MSI%20Motherboards%20all%20have%20this%20problem.%26nbsp%3B%20The%20common%20thing%20all%20of%20us%20seem%20to%20have%20that%20have%20this%20problem%20is%20the%20Samsung%20M.2%20NVMe%20SSD.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135575%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135575%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20tried%20everything%20possible%20but%20a%20clone%20%26amp%3B%20fresh%20install%20because%20i%20don't%20see%20why%20i'd%20have%20to%20resort%20to%20that.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWindows%20upgrade%20assistant%20seems%20to%20have%20messed%20up%20my%20pc%20even%20more.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFrom%20%3CSPAN%3E%26nbsp%3BBSOD%200xc00000bb%26nbsp%3B%20update%20failing%20to%26nbsp%3B%3C%2FSPAN%3EError%200x80242006%20every%20time%20my%20pc%20tries%20to%20automatically%20update%20itself.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMotherboard%3A%20MSI%20GAMING%20M7%20ACK%3C%2FP%3E%0A%3CP%3ESSD%3A%20Samsung%20960%20evo%20%2B%20Samsung%20960%20pro%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%20a%20friend%20of%20mine%20has%20the%20same%20SSD's%20as%20myself%20but%20with%20a%26nbsp%3BGigabyte%20X299%20AORUS%20Gaming%209%20%26amp%3B%20has%20the%20same%20problems.%3C%2FP%3E%0A%3CH3%20class%3D%22r%22%20id%3D%22toc-hId-1422216901%22%20id%3D%22toc-hId--1040212476%22%3E%26nbsp%3B%3C%2FH3%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135337%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135337%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ESigned%20up%20to%20add%20my%20similar%20experience%2C%20have%20several%20friends%20with%20largely%20same%20spec.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ESame%20issue%20with%201709%2C%20same%20spec%20%3A%20Asus%20Prime%20X299%20Deluxe.%20Samsung%20960%20Pro%202TB%20m.2.%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAlso%2C%20the%201709%20update%20is%20also%20not%20blocked%20for%20me%20(%20has%20failed%209%20times%2C%20and%20is%20currently%20waiting%20for%20a%20reboot%20which%20I%20guess%20would%20fail).%20My%20machine%20is%20a%20standard%20build%20by%20%3CA%20href%3D%22http%3A%2F%2Fwww.scan.co.uk%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ewww.scan.co.uk%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EIt's%20odd%20that%20a%20clean%20install%20reported%20to%20be%20be%20OK%2C%20and%20yet%20an%20upgrade%20is%20not.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThanks%20in%20advance%20for%20any%20help.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135245%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135245%22%20slang%3D%22en-US%22%3E%3CP%3EAlso%20having%20this%20issue.%20System%20specs%3A%3C%2FP%3E%0A%3CP%3EMOB%3A%20Asus%20prime%20X299-deluxe%20(FW%3A%20802%3B%20running%2028%20lanes%20with%20i7-7800x%20%26amp%3B%20quad%20memory)%3C%2FP%3E%0A%3CP%3ESSD%3A%20Samsung%20960%20evo%20M.2%20500GB%20(NVMe%2C%20FW%3A%203B7QCXE7)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135218%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135218%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20seems%20to%20be%20the%20magic%20combination%20with%20this%20problem%3A%20An%20ASUS%20X299%20MOB%20with%20a%20Samsung%20960%20Pro%20SSD%26nbsp%3BM.2%20using%20NVMe%20.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135214%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135214%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20also%20having%20this%20issue.%20I%20have%20a%20Samsung%20960%20pro%20and%20asus%20prime%20x299%20deluxe%20board.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135189%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135189%22%20slang%3D%22en-US%22%3E%3CP%3ECould%20it%20be%20that%20ASUS%20is%20just%20the%20most%20popular%20motherboard%20%3F%26nbsp%3B%20I%20have%20seen%20people%20with%20MOB's%20like%20MSI%20and%20Gigabyte%20with%20the%20same%20problem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135185%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135185%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20may%20also%20affect%20other%20motherboards.%26nbsp%3B%20The%20Asus%20one%20is%20the%20one%20that%20we%20have%20seen%20most.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135166%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135166%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BHi%20Michael%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20tried%20the%2030%20November%20update%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fde-ch%2Fhelp%2F4051963%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EKB4051963%3C%2FA%3E)%20right%20now%2C%20but%20my%20pc%20still%20crashes%20after%20the%20installation%20reboot.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20I%20tried%20the%20Upgrade%20my%20PC%20restarts%2C%20the%20screen%20stays%20black%20for%20around%202%20minutes%20and%20then%20the%20PC%20does%20power%20off.%20When%20I%20start%20the%20PC%20again%2C%20it%20immediatly%20boots%20with%20Build%201703.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMachine%3A%20Selfbuild%3C%2FP%3E%0A%3CP%3EMB%20Modell%3A%20MSI%20X99A%20Gaming%20Pro%20Carbon%20(%3CA%20href%3D%22https%3A%2F%2Fwww.msi.com%2FMotherboard%2FX99A-GAMING-PRO-CARBON%2FSpecification%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ELINK%3C%2FA%3E)%3C%2FP%3E%0A%3CP%3ESSD%3A%20Samsung%20SSD%20960%20Pro%20nVME%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20the%20X99A%20also%20affected%20with%20the%20same%20problem%20as%20X299%3F%20Or%20is%20the%20Samsung%20960%20Pro%20still%20not%20patched%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135157%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135157%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20is%20amazing%20I%20have%20almost%20the%20identical%20system%20except%20an%20ASUS%20Prime%20X299-A%20MOB%2C%20and%20I%20have%20the%20identical%20problems%20as%20you%20do.%26nbsp%3B%20I%20also%20have%20had%20Windows%20Update%20trying%20to%20update%20me%20for%20weeks.%26nbsp%3B%20I%20had%20to%20change%20my%20connection%20to%20metered%20to%20prevent%20Windows%20Update%20from%20downloading%20the%20update.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135156%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135156%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20an%20ASUS%20Prime%20X299-A%20motherboard%20with%20a%20512GB%20Samsung%20960%20Pro%20SSD%20and%20two%20SATA%20drives%2C%20as%20well.%26nbsp%3B%20%26nbsp%3BRight%20now%20Windows%20Update%20has%20been%20trying%20to%20upgrade%20me%20to%201709%20for%20about%20a%20month%20now.%26nbsp%3B%20I%20have%20my%20ethernet%20connection%20set%20to%20metered%20so%20it%20does%20not%20download%20the%20update.%26nbsp%3B%20I%20have%20kept%20my%201703%20system%20updated%20with%20manual%20updates%20I%20downloaded%20and%20installed%20myself.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20tried%20with%20an%20ISO%20flash%20drive%2C%20Windows%20Upgrade%20Assistant%2C%20etc.%20to%20upgrade%20about%20a%20dozen%20times%20and%20every%20time%20I%20try%20to%20reboot%20I%20get%20the%20BSOD%20with%20error%200xc00000bb.%26nbsp%3B%20If%20you%20need%20any%20other%20information%20I%20will%20be%20happy%20to%20give%20it%20to%20you.%26nbsp%3B%20Thanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135140%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135140%22%20slang%3D%22en-US%22%3E%3CP%3EInteresting%2C%20thank%20you%20for%20explaining%20the%20detail%20of%20the%20problem.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20remain%20hopeful%20for%20a%20fix%20soon.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135139%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135139%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20the%20Asus%20board%20is%20the%20most%20common%20one.%26nbsp%3B%20It's%20a%20pretty%20subtle%20issue%2C%20only%20exposed%20by%201709%20due%20to%20a%20slight%20increase%20in%20the%20boot%20image%20size%20(which%20is%20why%20previous%20versions%20worked%20fine)%20that%20results%20in%20the%20boot%20image%20being%20loaded%20into%20higher%20memory%20due%20to%20memory%20fragmentation%20on%20that%20specific%20motherboard%20with%20that%20specific%20firmware.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI'll%20check%20to%20make%20sure%20the%20block%20is%20correct.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135133%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135133%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Michael%2C%20first%20thank%20you%20for%20following%20up%20and%20not%20leaving%20us%20hanging.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESecond%2C%20Yes%2C%20mine%20is%20a%20custom%20built%20X299%20based%20system.%26nbsp%3B%20The%20motherboard%20is%20the%20ASUS%20Prime%20X299-Deluxe%20and%20the%20SSD%20is%20the%20NVME%20Samsung%20960%20Pro%20M.2%20512GB.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20checked%20with%20both%20ASUS%20and%20Samsung%20and%20neither%20have%20posted%20a%20recent%20firmware%20update%20to%20address%20this%20issue.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPS%3A%26nbsp%3B%20You%20mentioned%20a%20block%20in%20place%20to%20prevent%20the%20installation.%26nbsp%3B%20I%20can%20tell%20you%2C%20if%20it%20is%20designed%20to%20block%20the%201709%20installation%20via%20Windows%20Update%2C%20it%20is%20not%20working%20for%20me.%26nbsp%3B%20Every%20time%20I%20check%20for%20updates%20it%20tries%20to%20download%20and%20installed%20the%20%22Windows%20Feature%20Update%20to%201709%22.%26nbsp%3B%20I've%20had%20to%20temporarily%20disabled%20the%20Windows%20Update%20service%20to%20prevent%20this%20from%20happening%20every%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-135132%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-135132%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20reviewing%20this%20with%20support%20engineers.%26nbsp%3B%20It%20appears%20that%20there%20are%20two%20separate%20problems%2C%20one%20that%20was%20fixed%20with%20the%20update%20released%20on%20November%2030th%20(affecting%20a%20small%20number%20of%20devices%20with%20Intel%20%3CSPAN%3EP4500%2F4600%3C%2FSPAN%3E%20drives)%2C%20and%20a%20second%20one%20that%20is%20still%20being%20worked%20on%20(affecting%20certain%20X299%20motherboards).%26nbsp%3B%20We%20still%20have%20a%20block%20in%20place%20for%20the%20affected%20devices%20so%20that%20Windows%20Update%20doesn't%20try%20to%20upgrade%20them.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20the%20machines%20where%20you%20are%20seeing%20this%20issue%2C%20can%20you%20provide%20the%20make%20and%20model%20of%20the%20machine%2C%20or%20if%20it%20is%20a%20%22build-your-own%22%20device%2C%20what%20model%20of%20motherboard%20is%20being%20used%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20second%20issue%20(X299%20motherboards)%20can%20also%20be%20fixed%20with%20a%20firmware%20update%3B%20the%20fix%20we%20are%20working%20on%20just%20tries%20to%20work%20around%20the%20firmware%20issue.%26nbsp%3B%20We%20are%20trying%20to%20work%20with%20the%20motherboard%20makers%20to%26nbsp%3Bhave%20them%20create%20a%20firmware%20update.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134930%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134930%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20see.%26nbsp%3B%20You%20are%20already%20coming%20up%20with%20a%20possible%20problem.%26nbsp%3B%20I%20cannot%20believe%20all%20this%20time%2C%20and%20not%20one%20engineer%20at%20a%20place%20like%20Microsoft%20can%20actually%20come%20up%20with%20a%20fix%20for%20this.%26nbsp%3B%20Just%20unbelievable.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134927%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134927%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20copy%2C%20clone.%26nbsp%3B%20As%20in%20using%20a%203rd%20party%20tool%20like%20Acronis%20or%20something%20else.%26nbsp%3B%20The%20only%20downside%20I%20could%20see%20if%20the%20hardware%20change%20from%20NVME-%26gt%3BSATA-%26gt%3BNVME%20would%20trigger%20a%20hardware%20ID%20change%20and%20make%20all%20installed%20software%20unregistered%20and%20ask%20for%20re-activation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134925%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134925%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20mean%20you%20can%20simply%20copy%201709%20from%20your%20SATA%20to%20your%20SSD%20after%20upgrading%20and%20everything%20works%20fine.%26nbsp%3B%20Sounds%20like%20a%20lot%20of%20work%2C%20and%20it%20will%20open%20up%20the%20possibility%20of%20many%20errors.%26nbsp%3B%20I%20just%20cannot%20understand%20why%20this%20is%20such%20a%20big%20fix%20for%20Microsoft.%26nbsp%3B%20Lots%20of%20people%20a%20lot%20less%20computer%20efficient%20than%20us%20are%20having%20this%20problem.%26nbsp%3B%20I%20wish%20they%20would%20just%20issue%20a%20fix%20already.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134924%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134924%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can%20also%20do%20the%20workaround%2C%20which%20is%20to%20clone%20the%20NVME%20drive%20to%20a%20SATA%20drive%2C%20then%20boot%20from%20SATA%2C%20do%20the%201709%20upgrade%2C%20then%20clone%20back%20to%20the%20NVME.%26nbsp%3B%20Many%20have%20done%20this%20successfully%2C%20I%20just%20can't%20be%20bothered.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134923%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134923%22%20slang%3D%22en-US%22%3E%3CP%3EMicrosoft%20seems%20to%20treat%20this%20like%20there%20is%20a%20couple%20of%20hundred%20of%20us%20here%20complaining%2Cand%20no%20one%20else%20has%20this%20problem.%26nbsp%3B%20Well%2C%20in%20reality%20I%20cannot%20tell%20you%20how%20many%20people%20have%20this%20problem.%20I%20have%20heard%20from%20countless%20other%20people%20that%20cannot%20upgrade%20to%201709.%20Why%20in%20the%20world%20is%20it%20so%20difficult%20to%20put%20out%20a%20fix%20after%20about%20six%20weeks%20of%20this.%26nbsp%3B%20All%20we%20are%20asking%20is%20to%20be%20able%20to%20upgrade%20to%201709.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20at%20my%20end%20with%20this.%26nbsp%3B%20I%20have%20tried%20every%20method%20of%20upgrading.%26nbsp%3B%20Other%20than%20doing%20a%20clean%20install%2C%20which%20I%20refuse%20to%20do%2C%20it%20is%20impossible%20for%20people%20with%20SSD%20drives%20with%20NVMe%20to%20upgrade.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134920%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134920%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E%26nbsp%3BA%20lot%20of%20very%20angry%20people%2C%20Michael.%26nbsp%3B%20Can%20you%20please%20bring%20this%20to%20the%20attention%20of%20whomever%20can%20provide%20a%20solution.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134915%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134915%22%20slang%3D%22en-US%22%3E%3CP%3EThese%20constant%20promises%20from%20Microsoft%20without%20a%20fix%20is%20just%20getting%20ridiculous%20already.%26nbsp%3B%20I%20have%20tried%20updating%20to%201709%20in%20every%20possible%20way.%26nbsp%3B%20From%20Windows%20Update%2C%20to%20ISO%2C%20Upgrade%20Assistant%2C%20etc.%2CI%20have%20tried%20them%20all%20and%20nothing%20works.%26nbsp%3B%20Every%20time%20you%20try%20to%20reboot%20you%20get%20error%200xc00000bb.%26nbsp%3B%20There%20is%20no%20fix%20from%20Microsoft%20out%20there%2C%20and%20it%20does%20not%20look%20like%20there%20is%20going%20to%20be%20a%20fix.%3C%2FP%3E%0A%3CP%3EDoes%20Microsoft%20really%20want%20me%20to%20go%20and%20buy%20an%20Apple%20and%20be%20done%20with%20this.%26nbsp%3B%20I%20am%20sick%20of%20waiting%20for%20a%20fix%20for%20something%20that%20is%20a%20common%20problem%20for%20people%20trying%20to%20upgrade%20with%20a%20SSD%20drive.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20someone%20from%20Microsoft%20please%20tell%20us%20if%20there%20is%20going%20to%20be%20a%20fix%20or%20not%2C%20and%20what%20is%20the%20timetable%20%3F%26nbsp%3B%20I%20really%20would%20like%20to%20know%20a%20fix%20is%20really%20coming%20or%20not.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134809%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134809%22%20slang%3D%22en-US%22%3E%3CP%3ESeems%20to%20me%2C%20what%20hes%20basically%20saying%20is%20that%20the%20fix%20that%20should%20have%20came%20out%20on%20the%2030th%20which%20never%20did%2C%20then%20the%20update%20for%20the%2030th%20came%20out%20on%20the%205th%20on%20Tuesday%20which%20still%20does%20not%20contain%20the%20fix%20%26amp%3B%20now%20we'd%20have%20to%20wait%20till%20January%20for%20the%20%22fix%22%20which%20probably%20won't%20come%20again.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESeriously%20it's%20very%20disappointing%2C%20everyone%20out%20their%20is%20complaining%20and%20nothing%20is%20being%20done.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20built%20a%20new%20pc%20just%203%20months%20ago%20and%20knew%20win10%20would%20be%20very%20troublesome%2C%20that%20i%20literally%20bought%20an%20ssd%20just%20for%20the%20OS%20to%20to%20prevent%20deletion%20of%20important%20files%20because%20fresh%20installs%20are%20the%20only%20thing%20that%20temporarily%20fix%20things%20like%20this.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20also%20stopped%20my%20antivirus%20%26amp%3B%20nvidia%20drivers%20from%20working%20that%20i%20had%20to%20delete%20both%20apps%20and%20reinstall%20to%20my%20other%20ssd.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134558%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134558%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E%26nbsp%3BI%20am%20not%20sure%20what%20you%20mean%20by%20a%20%22dynamic%22%20update%20but%20I%20am%20assuming%20you%20mean%20through%20an%20automatic%20mechanism.%26nbsp%3B%20I%20tried%20the%20upgrade%20again%20using%20Windows%20Update%2C%20and%20I%20get%20the%20same%20BSOD%20after%20it%20tries%20and%20fails%20to%20update%20with%20the%20%22Feature%20Update%20to%201709%22%20update.%26nbsp%3B%20I%20also%20tried%20the%20Windows%2010%20Update%20Assistant%20application%20which%20re-downloaded%20the%20media%20and%20also%20failed%20with%20the%20same%20BSOD%20on%20the%20first%20reboot.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEither%20I%20am%20doing%20something%20wrong%2C%20or%20the%20patch%20was%20not%20issued%20by%20Microsoft.%26nbsp%3B%20I%20have%20to%20say%20this%20is%20extremely%20disappointing.%26nbsp%3B%20A%20solution%20was%20implied%2C%20and%20none%20was%20given.%26nbsp%3B%20Please%20Help.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134400%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134400%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20fix%20is%20needed%20to%20the%20Windows%2010%201709%20installation%20files%2C%20not%20to%20Windows%2010%201703.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20are%20using%20dynamic%20update%2C%20the%20fix%20should%20automatically%20be%20injected%20during%20the%20process.%26nbsp%3B%20Otherwise%2C%20you%20might%20need%20to%20manually%20mount%20the%20install.wim%20and%20inject%20the%20update%20into%20it%2C%20at%20least%20until%20January%20when%20we'll%20be%20releasing%20updated%20media%20that%20will%20contain%20the%20fix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134342%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134342%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20think%20so%2C%20the%20KB%20applies%20to%201709%2C%20the%20patch%20we%20are%20looking%20for%20should%20be%20applicable%20to%201703%20as%20we%20can't%20update%20to%201709%20because%20of%20the%20NVME%20SSD%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134339%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134339%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20should%20be%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4051963%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4051963%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-134268%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-134268%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20tell%20me%20what%20the%20KB%20number%20is%20for%20this%20patch%20please%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-133022%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-133022%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F21544%22%20target%3D%22_blank%22%3E%40Michael%20Niehaus%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI've%20been%20watching%20the%20Windows%20Update%20Catalog%20website%20all%20day%2C%20as%20of%20this%20writing%20(4%3A43PM)%20I%20don't%20see%20it.%26nbsp%3B%20I'm%20using%20the%20search%20term%20%22windows%2010%20cumulative%20update%22%20and%20the%20most%20recent%20results%20are%20dated%20as%20Nov%2029th%2C%20but%20they%20show%20as%20being%20for%20Build%201709.%26nbsp%3B%20I%20would%20assume%20by%20what%20you%20suggested%20we%20would%20be%20seeing%20a%20Cumulative%20Update%20dated%20for%20today%2C%20Nov%2030th%20with%20Build%201703%20in%20the%20description.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132835%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132835%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20You%20very%20much%20for%20addressing%20my%20question.%26nbsp%3B%20I%20am%20happy%20that%20this%20was%20resolved%20and%20am%20excited%20to%20finally%20be%20able%20to%20try%20FCU.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132832%22%20slang%3D%22en-US%22%3ERE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132832%22%20slang%3D%22en-US%22%3EThe%20suggestion%20I%20received%20from%20many%20employed%20by%20MS%20was%20to%20simply%20format%20and%20re-install%20Windows.%20This%20isn't%20an%20option%2C%20I%20run%20a%20highly%20customized%20system%20with%20many%20apps.%20A%20full%20reinstall%20would%20be%20a%20tremendous%20effort%2C%20the%20in%20place%20update%20really%20needs%20to%20work.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132830%22%20slang%3D%22en-US%22%3ERE%3A%201703-%26amp%3Bgt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132830%22%20slang%3D%22en-US%22%3EThis%20is%20a%20known%20issue.%20The%20fix%20for%20this%20will%20be%20included%20in%20the%20cumulative%20update%20that%20will%20be%20released%20today%20at%2010am%20via%20%3CA%20href%3D%22http%3A%2F%2Fcatalog.update.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fcatalog.update.microsoft.com%3C%2FA%3E%20(manually%20downloaded).%20It%20will%20also%20be%20included%20in%20the%20next%20Patch%20Tuesday%20cumulative%20update.%20(Ref%20OS%20%2314207031%2C%2011D)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-132812%22%20slang%3D%22en-US%22%3ERe%3A%201703-%26gt%3B1709%20BSOD%200xc00000bb%20on%20devices%20with%20NVMe%20SSD's%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-132812%22%20slang%3D%22en-US%22%3E%3CP%3EHere%20are%20links%20to%20just%20a%20few%20of%20the%20dicussions%20regarding%20this%20issue.%26nbsp%3B%20This%20is%20widespread%20and%20a%20solution%20is%20required.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.google.ca%2Furl%3Fsa%3Dt%26amp%3Brct%3Dj%26amp%3Bq%3D%26amp%3Besrc%3Ds%26amp%3Bsource%3Dweb%26amp%3Bcd%3D1%26amp%3Bcad%3Drja%26amp%3Buact%3D8%26amp%3Bved%3D0ahUKEwiA4fTf4ebXAhVq0oMKHV_HATIQFggtMAA%26amp%3Burl%3Dhttps%253A%252F%252Fsocial.technet.microsoft.com%252FForums%252Fen-US%252F08485ba0-f69f-483b-861e-238f161dabee%252Fproblem-with-upgrade-to-creators-update-on-nvme-disk%253Fforum%253Dwin10itprosetup%26amp%3Busg%3DAOvVaw2zXfJgTM6FJaq_nGgja4Rf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.google.ca%2Furl%3Fsa%3Dt%26amp%3Brct%3Dj%26amp%3Bq%3D%26amp%3Besrc%3Ds%26amp%3Bsource%3Dweb%26amp%3Bcd%3D1%26amp%3Bcad%3Drja%26amp%3Buact%3D8%26amp%3Bved%3D0ahUKEwiA4fTf4ebXAhVq0oMKHV_HATIQFggtMAA%26amp%3Burl%3Dhttps%253A%252F%252Fsocial.technet.microsoft.com%252FForums%252Fen-US%252F08485ba0-f69f-483b-861e-238f161dabee%252Fproblem-with-upgrade-to-creators-update-on-nvme-disk%253Fforum%253Dwin10itprosetup%26amp%3Busg%3DAOvVaw2zXfJgTM6FJaq_nGgja4Rf%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.google.ca%2Furl%3Fsa%3Dt%26amp%3Brct%3Dj%26amp%3Bq%3D%26amp%3Besrc%3Ds%26amp%3Bsource%3Dweb%26amp%3Bcd%3D3%26amp%3Bcad%3Drja%26amp%3Buact%3D8%26amp%3Bved%3D0ahUKEwiA4fTf4ebXAhVq0oMKHV_HATIQFghBMAI%26amp%3Burl%3Dhttps%253A%252F%252Frog.asus.com%252Fforum%252Fshowthread.php%253F96864-Beware-of-Fall-Creators-Update-with-a-ASUS-x299-MOB-amp-Samsung-NVMe-SSD%26amp%3Busg%3DAOvVaw1uS12FMzgE7edDudsQmrnR%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.google.ca%2Furl%3Fsa%3Dt%26amp%3Brct%3Dj%26amp%3Bq%3D%26amp%3Besrc%3Ds%26amp%3Bsource%3Dweb%26amp%3Bcd%3D3%26amp%3Bcad%3Drja%26amp%3Buact%3D8%26amp%3Bved%3D0ahUKEwiA4fTf4ebXAhVq0oMKHV_HATIQFghBMAI%26amp%3Burl%3Dhttps%253A%252F%252Frog.asus.com%252Fforum%252Fshowthread.php%253F96864-Beware-of-Fall-Creators-Update-with-a-ASUS-x299-MOB-amp-Samsung-NVMe-SSD%26amp%3Busg%3DAOvVaw1uS12FMzgE7edDudsQmrnR%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.reddit.com%2Fr%2FWindows10TechSupport%2Fcomments%2F7729kq%2Fwindows_10_update_1709_fails_to_install_0xc00000bb%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.reddit.com%2Fr%2FWindows10TechSupport%2Fcomments%2F7729kq%2Fwindows_10_update_1709_fails_to_install_0xc00000bb%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.cnet.com%2Fnews%2Fwindows-10-fall-creators-update-hits-install-snag-for-some%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.cnet.com%2Fnews%2Fwindows-10-fall-creators-update-hits-install-snag-for-some%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
I get the new one via Magician... it asked me to upgrade...

And today Microsoft released a new update for 1709 (and some other updates for older versions)

 

I tried another time to update the old 1703. Same result: 0xc00000bb. 

 

Now, I've just finished to clean the 960 pro from the update data and Windows starts to download again the faulty update... I think that FCU-X99-960Pro issue is killing my precoius ssd... 

Hi,

here are the last answer today from MSI support:

"You have to make a clean Windows 10 installation with UEFI mode on in BIOS, and with included 1709 and WHQL Support on".

But there are no guarantee.

 

Someone an other issue??

"you have to make"... Thank you, MSI...

This issue is not our fault. We bought Great components for our PC... This is our only fault... So, do they pay us for the time we Will spend for the complete reconfiguration of our workstations?

Hello Everyone,

 

As the original poster of this thread, I would like to let everyone know that the latest 1102 BIOS update from ASUS for the X299 Prime Deluxe resolved the issue.  I was able to install the Fall Creators Update using the Windows Update assistant.  I did delete the SoftwareDistribution prior to the update to ensure that there was no old update media still on the drive, however this may or may not have been necessary.

I really feel for these people with MSI motherboards.  Apparently Microsoft is never going to issue a fix.  You have to keep leaning on MSI to issue a BIOS fix.  As has been reported here, ASUS released a fix for this with their 1102 BIOS update.  Good luck to everyone.  You must keep at your MOB manufacturer.  

Highlighted

Anybody here, who did a clean new Win10-1709 Installation?
Does 1709 run at all at the MSI X99/SSD 960 combination?

Bevor i have to completely rebuild my system, which will take hours, it would be nice to know,

it the toxic combination of X99 + SSD 960 works anyhow...

Martin

 

 

I doubt a new installation of Windows will help to solve the problem in long term perspective. The next big update of Windows 10 will come sooner or later and if this problem is not solved until then, you will have to face with the same error again...

I think that MSI will never release new bioses for old X99 clients... pheraps they want us to buy a new motherboard... but I am very disappointed with them...  very disappointed.

 

I asked suppord, and they said "We tried to install W10 1703 on X99A Workstation with 960 Pro, then we made the FCU... It worked without problems"... ok, but our systems? We all have garbage on our pcs? We are all incompetent? Sorry for the outburst...

I am thinking exactly the same. I do not want to perform a clean install when there is no guarantee that, in the next update, this issue persists (I am with the Anniversary version because the first Creators Update was already giving me this BSOD).

 

It is funny to see that Asus customers are receiving a fix via BIOS update, while we, MSI users, are left in the dark. It is funny to read that they recommend to do the installation in UEFI mode, when there is no other way to have the M.2 drive as the boot device...

 

Could any of you, who contacted MSI support, give them the link to this thread? It could be helpful for them to find the issue.

Hello,

 

yes i do this, but first they answer, that they never heard from this problem.  lol

 

and second they told me, i have to make a clean install from win10 1709 creators update with

 

UEFI mode on.

 

i send them all emails and links from all forums i posted, MS,MSI, Samsung and and and.

 

but i think they didn´t read it. i also ask why can Asus fix it. but no answere.

 

i dont´make a clean new install, before no one posted that the problem is fixed now.

 

let me hear if someone made it, and it works, please

I have a brand new system with Asus prime x299 motherboard along with 64 gb ram and i9-7900x cpu and 1TB samsung M.2 ssd.  It is now Feb 4 2018.  I have installed and reinstalled my brand new windows 10 pro multiple times from the $200 usb stick.  I also have dvd and even dowloaded the latest from internet.  Everything works great until the update service starts forcing the 1709 defective update on me.  Then the problems and harm begins.  I have tried every so-called fix on the internet.  The update process always leads to BSOD with 0xc00000bb.  I am a software engineer with over 30 years experience.  Nothing works.  Not the trouleshooter, nor any of the other many fixes offered by MS support fotums.  Not even the brand new ISO download with 1709.  So there is apparently still no solution for this problem after many months.   I see that I am not alone.  There is no excuse for this.  This motherboard is popular and one of the newest out there.  The 1709 update was not adequately tested and is defective and is causing harm to many people like me who have wasted many many hours trying to get it to work.  Who is responsible and accountable for this blunder at microsoft?  We will never know.  For now I can only disable the windows update service and pray that someday someone at Microsoft will fix this terrible and embarrassng defective product.  This is no different than going to car dealer and buying a new car and then the car won even start.  The dealer is happy to take all your money and apologizes for the defective product and promises to get it fixed someday.  Meanwhile you have nothing for your money and dealer has no incentive to fix their defect because they already have all your money.  Somewhere there might be a smart lawyer or consumer organization who will get dealer attention by class action lawsuit representing all the injured customers.  Maybe then the product will get fixed or recalled and the customers will get their money back.

I have attempted the clean install multiple times and it still does not work.  My brand new x299 system works fine with windows 7 pro and windows 10 pro fresh in talls  from usb.  So there must be good drivers.  I have removed all peripherals and tried everything I can think of plus all of the suggested fixes out there in the support forumd.   But my system will absolutely not work with the 1709 update.  It does not matter how I install the update.  Today I again downloaded the new 1709 ISO and ran through the installer with newly formatted ssd.   It all seems to go well until the first reboot which leads to BSOD.  All my drivers are up to date, and the system works great with the 1607 Win 10 version.  But will not work with 1709 whether it being updated from my 1607 version or a fresh ISO install.  Can anybody at Microsoft please help.  I will offer one million of my own TobyNorris cryptocoin dollars to anyone at Microsoft who can either fix this and restore my faith in your company.

 

Thanks Tim for sharing your fix.  That gives me one more fix procedure to try.  I was surprised to see that I did not have the latest BIOS even though I am running the Asus EZ  tool that is supposed to check daily for bios updates.  I did find the 1004 that you mentioned plus an even newer 1102 version from Jan 17, 2008.  So I am manually updating the bios and will follow your procedure to see if that works for my setup.

That fix from Tim definitely worked for me.  So now I finally have a successful update to 1709.  I followed all of Tims steps and the update worked. 

That method also worked for me.   My system is very similar to yours except I have have 64 GB of ram and the 1TB ssd.  So I did get the 1709 finally installed.  But now I seem to have other driver problems with my internal USB hub device and also my "Windows Update" now says "Some settings are managed by your organization" and this prevents me from checking for updates or seeing my updte history.  I wonder if you had any similar problems afer your successful upgrade to 1709?

Could you please tell me what fix from "Tim" you refering to? Is the post deleted, i cant find it?

Last weekend I successfully finished the update of my system (MSI X99 + SSD 850) to 1709. It took me 6 hours. Most time was spent waiting for the system. No clean installation.

I was tired to wait for a solution by MSI and/or Microsoft. 

My approach was to make a intermediate step via a "normal" disk.

Short description:

 

1. Image Backup of system disk

2. change SSD to "normal" disk

3. recover image to "normal" disk

4. Because of new hardware set product key again. Otherwise after the update procedure ended with error message like "can't get product key"

4. start update to 1709

5. clean system disk (delete upgrade folder etc.)

6. make image backup of "normal" disk

7. recover image to ssd

8. O gott! BSOD 0x00000bb!

9. select option "start safe mode" from BSOD. system starts in safe mode

10. restart system

11. everthing works fine

 

 

Regards

Michael

Hello.

 

any news?

 

has someone make the 1709 update with following parts?

 

X99A Raider - Samsung Evo 960 NVMe

 

if someone, pls let me known how?

 

greetz

Nope, there is a workaround which consists in cloning your ssd into another drive, update windows with that drive, and then, after having the system up and running, cloning it back to the M.2 SSD.

As I said before, I do not want to do that in every update so I wait for the fix as long as possible. Meanwhile, I have disabled the update assistant in the task manager.

Greetings

I 100% agree with you, I will be waiting as welll

I can't believe that there is still no solution to this problem beside a BIOS update (which is mostly impossible to have unless you are a asus user). How ridiculous.

So... I did the update.

 

I had to clone the system disk (960 Pro) to another bootable ssd (850 Pro).

Now, the PC is doing the rest of the updates, then I'll try to re-clone all to the 960 Pro.

 

Doing this operation, I noticed that the X99A Bios has some problems: it can't manage correctly the boot disk. After the cloning operation, I obviously went into the bios to set the 850 as boot disk. I did the "save and reboot option" and the pc started again with 0xc00000bb error. After some bios reset, I was able to start from the 850, and now I have the FCU running (by now, not from the NVMe). Ad maiora...

Hello Michael,

Is there any update on this?

I have Windows 10 Creators Update (1703) factory installed, but have been unable to update to 1709 since 3rd November (Windows update must have tried 60+ times to update unsuccessfully). I would not wish to go through this with every six-monthly update.

Intel Core i7-7820X, Gigabyte GA-X299-UD4 Motherboard, 500GB Samsung 960 EVO M.2 PCIe SSD. SSD drivers updated and BIOS updated to most current versions.

Thanks, Paul

Hi all,

I'm a newbee in this forum and want to say hello to everybody!!

 

I have the same probelm with the Fall-Update, my system is:

MSI X99A SLI PLUS

Samsung 950 M2 SSD

Win 10

Versionsinfo: 1703 (15063.909)

 

The Fall-Update fail always with BSOD ...

It's very poor that MS isn't able to inform their customers. 4 Month that troubble?!

Temporary solution: Disable automatic updates, and put in the updates manualy, month for month ...

Is anybody form MS-Company able to give us an info about the progress of the debugging ;-)

 

All the best for You all,

Udo

I have the same problem!

 

MSI Godlike Carbon X99A motherboard and Samsung SM951 M.2 PCIe NVMe SSD boot drive.

 

I have all drivers up to date, and have tried everything (except changing/cloning my boot drive, which is beyond my skills).

 

Microsoft need to fix this.

I have MSI Godlike Carbon X99A motherboard and Samsung SM951 M.2 PCIe NVMe SSD boot drive, and have had this problem ever since it started.  Very annoying, and the PC keep trying to update many times daily, and failing!

 

This is ridiculous.

"There is a block in place that keeps Windows Update from offering Windows 1709 to affected systems."
  
 
Your block is NOT working for me.  Win10 keeps trying to update.

The same problem since october 2017.

 

MSI X99A Gaming Pro Carbon

Samsung 960 Pro M2 SSD VNMe 2TB

Win 10

Versionsinfo: 1703 (15063.909)

 

See also german Forum..

Microsoft!! HELP HELP HELP HELP HELP HELP HELP HELP HELP HELP

 

R.Freier, Germany

 

I gave up, and make a format c and install from scratch, people dont waste your time, like i did and try to avoid the new Win setup with "workarounds" they all dont help!!! Start New, all you can do. I was going through all this, so thats the poor conclusion...

 

Best regards

Martin

Short update for other owners of MSI X99S Gaming 7 and MSI X99A Gaming 7 boards: MSI answered to my issue I addressed to their support. They sent me a link to a new BIOS version that should solve the problem. For me it did not work, I still get the blue screen, but maybe someone else wants to give it a try.

 

New BIOS version H.G3: http://msi-ftp.de:8080/main.html?download&weblink=3b6bfdeeaf140535fc1ffaac86f4916e

 

At least they are working on it!

Ok, good to know, that i didnt waste even more time with that H.G3 Bios, they send me that too.

Martin,

 

Format c: is unfortunately not a viable option for me.  It would mean a few weeks of work rebuilding my PC setup and software.

Good that they are working on it.

 

I do prefer that Microsoft fix it at their end though.  Flashing BIOS would mean I would lose all the OC settings that my PC supplier did :(  So it would be a last resort solution for me.

You can just save the OC profile then flash bios if you have to not that it would fix anything.

Flashing the bios will still keep your saved oc profile so you don't have to worry.

hello,

 

today i get a beta BIOS (E7885IMS.P63)  from MSI for my X99A Raider.

 

But it didn´t fix the problem.

 

Same like before (BSOD).

 

Someone get the update without cloning to a other ssd??

 

I´m still in hope.

 

greetz

Thank you.  I hadn't realised this, and it is good to know.

 

I still hope that Microsoft will fix it however.

Hi,

 

do you have a weblink to try it out?

 

Thanks

Yes, but that is for the MSI X99S Gaming 7 and MSI X99A Gaming 7, I have the X99A Raider like silber.

Hi,

 

is absolute poor, what MS delivers. I thought I was the only one who has problems, but I see a lot of User here in this forum which has the same stupid problem. What kind of public relations microsoft use?! Like a god? Hurry up and solve the prob. I've wasted time enough until now ...

hello,

 

here are link to the beta BIOS for X99A Raider : http://msi-ftp.de:8080/main.html?download&weblink=98bce9e21e8f51adb052bcbea36ead96&

 

please post, if you can made the update, and tell how.

 

greetz

 

silberruecken

Thank you for the link.

Unfortunately, I have just tried the update with this new beta bios but I still get the same bsod :(

X99A Gaming Pro Carbon (MS-7A20 installed version 1.30)

Samsung 960 Pro M2 NVMe SSD 512GB firmware version 4B6QCXP7

Windows 10 Pro 64-bit version 10.0.14393 compilation 14393 Version 1607 (14393.2068)

 

I swear, this is the last time I trusted MSI. I will never make that mistake again. Shame of you!!!

 

 

Dear MSI X99a users... I did the Fall Creators Update via NVMe cloning (after 4 months of troubles, attempts and hopes)... but I'm curios and I love to learn every time I have the possibility to do it.

 

Before my upgrade (and even now) I noticed a strange thing in my MSI X99a Workstation BIOS: inside the Storage Manager, the M.2 disk is not reported!!!!! It's like the M.2 line is not connected... but in the boot manager, the 960 Pro is the boot disk (via Intel Rapid Storage Manager).

 

You can see it in the attached imageMSI_SnapShot (Copia).jpg

 

MSI said to me that if the NVMe disk boots, there is no issue... but... mmm... wait... your bios/mobo can't see my disk, and you tell me that is a software problem and I need to format??!!!

 

Now... I ask to all the MSI X99 users... in your BIOS, are you able to see the M.2 disk as connected into the M.2 port? I know that it should be discussed in a MSI related forum, but I think it should be useful to understand if the 0xc00000bb is definitively a bios related problem... and perhaps some bios modder can understand and solve the problem... before MSI...

 

Have a nice day!

 

 

 

X99A Gaming Pro Carbon (MS-7A20 installed version 1.41)

NVMe SSD disk Samsung 960 Pro not in BIOS

Hi,

I see my M.2 disk but I've migrated my system to 1709. Made a detour via standard disk (see above).

 

MSI_SnapShot.jpg

This is not

MSI X99A Gaming Pro Carbon !!!!

....Now... I ask to all the MSI X99 users...

Hi,

I'm using an MSI X99A Tomahawk with an 960 EVO and it's not visible in the BIOS.

I've got the same Problem with the Bluescreen by upgrading to 1709. But I've upgraded previously from 1607 to 1703 successfully.

Hope there will be a fix in near future !

:)

 EDIT: But it was always the case that my 960 EVO was not showing up in the BIOS

 

Related Conversations