Forum Discussion
Solved
1703->1709 BSOD 0xc00000bb on devices with NVMe SSD's
1703->1709 BSOD 0xc00000bb on devices with NVMe SSD's
This will be the very first question I will ask in the AMA. I hope you have a better answer than "we are working on it" ready for the thousands of us with this issue and waiting for a fix since September.
- This is a known issue. The fix for this will be included in the cumulative update that will be released today at 10am via http://catalog.update.microsoft.com (manually downloaded). It will also be included in the next Patch Tuesday cumulative update. (Ref OS #14207031, 11D)
The error 0xc00000bb is the most rare blue screen of death. It is also similar to the 0xc0000034 which may cause a driver to overrun a Stacked-Based-Buffer. This can allaw a malicious user to gain control of the machine and cause an Unknown Hard Error (0xc0000218).
You'll need to restart your computer and set the /CRASHDEBUG system start option or check with your hardware device vendor for BIOS updates. If the Stop Error Screen appears again, do not press the POWER button or unplug the power cord. Instead, CONTACT your system administrator or your support team.
If you're interested in this comment, reply to ourselves for more information about troubleshooting Stop errors or contact us via private message in the Tech Community for troubleshooting.I have an Asus ROG Strix Z370-H Gaming board with a Samsung NVMe SSD 960.
Up to v 1709 I had no problems.
When I tried to update to 1803 the update fails with different errors which are vaguely related to a driver issue, according to thing I found on MS site. There was no way to find out which driver. The update kept re-downloading and installing.
I then made the mistake to try the update through Medi creation tool. That resulted in a botched install that tried to roll back but could not, and bricked my PC.
Next I tried a clean install of 1803. This kept failing due to BSODs.
I decided to go back to a clean 1709 install, and put windows update in Semi Annual Channel +365 days.
Since then , no problems.
A month later , after OS Build 17134.48 came out, I tried to update again - it failed again.
I dare not try with OS Build 17134.81.
A second computer I tried this update on is an HP Probook 440 G5 , which has an Intel Pro 6000p. This was an update from 1703. It updated without a problem, but since then had an assortment of BSODs, mostly "critical process died".
To make things worse, the OS does not create any dump files to analyze.
I called HP support who kindly sent me to Microsoft to work it out with them. Yeah, right.
I did a factory reset to 1703 (took over 2 hours) and upgraded to 1709. So far, no BSODs.
The intel ssd is mentioned in the incompatibility list of the first 1803 versions. But the MS description of the errors is quite different then what I had:
"When attempting to upgrade to the Window 10 April 2018 Update, select devices with Intel SSD 600p Series or Intel SSD Pro 6000p Series may repeatedly enter a UEFI screen after restart or stop working."My conclusion is that MS completely screwed this update.
I know quite a few people who's PC was bricked by the automatic update. Some have Win 10 Home, so they cannot delay this update.
I would not be surprised if a large class action lawsuit is opened against MS.
In my business we have 20 PCs with WIn 10 1709. If they were bricked we would suffer significant financial and reputation damage. Luckily all our PCs are set to Semi Annual Channel +365 days., and I hope none will get this update.
I think if you have an ssd machine, you should avoid this update for now. Don't trust MS on this update. You might suffer significant damage. If you can, back your computer with an imaging program such as Acronis TI . This is the fastest way to get back up should this update brick your PC.
Absurdly, if you have an old PC with HDD you are probably safe, at least from the few PCs I updated.
Unbelievable.Hi Rodriguez
What are you're bios configs?:
- Is you're storage set to AHCI? IDE tends to have problems with recent Windows Updates, pretty old storage driver.
- Is WHQL forced on your MoBo? Could also be a issue, try to disable it, if enabled.
- Is you 960 set as first and primary boot device?
For me it almost look like you're SSD is not getting detected as Boot Device. Well could be a Windows Update Problem :P
- 1. AHCI
2. No WHQL setting in my BIOS
3. 960 is first and primary boot device.
Plus, why in the world would that matter in 1803 and not in 1709 ???
That update is botched. I'm not the only one. Look at this:
https://www.windowscentral.com/windows-10-april-2018-update-common-problems-and-fixes.
Hi all
Finaly I had some spare time to have a look at the 1803 build, sorry for delay..........
In my case I gave up trying to upgrade to 1709. But I've gone from 1703 to 1803 by doing the following:
1. Use media creation tool to download ISO of 1803
2. Unpacked ISO of 1803 to folder with Winrar - Yep You can call it old-fashioned, but I works :)
3. Ran setup
4. Follow guides and wait
5. IT WORKS!!!! Or at least it makes the upgrade. Really haven't testet much yet :)
My HW: Intel E5-1630V3, MSI Raider X99A and Samsung 960 Evo NVME.
But reports are now, that people with Intel and Toshiba SSDs have problems with 1803..... Even Microsoft's own Surface has problems :) So a fix for that will properly be out much faster, than the 1803 was for all of us with non Microsoft hardware.......
Well lets hope Microsoft remembers what they did in build 1803 to get the NVME disks to work, and implements it in next build, so we don't have to start all over again. Still, If anyone stumbles on info what the exact fix was, please post. I wasn't able to find fix list on 1803 regarding this problem :( Someone know how Asus fixed the problem with BIOS update? (Shame on You MSI....)
Best Regards
Kim
Just to confirm, if I use the Media Creation Tool, get an ISO, burn a DVD and run the setup.exe (I already got all that), this will just UPDATE my windows 10? I'm not going to have to reinstall software?
I'm at the part where it says it will Install Windows 10 Pro, and to "keep files and apps". That's basically going to painlessly update me without the destruction of some sort of fresh install type thing?
Yes - I do have a clone backup just in case, I'd rather not use that. Thanks for letting me know
UPDATE: I went ahead and did it. To let everyone know this was a X99A MSI Mpower MB, with the Intel 750 SSD NVME drive. Nine months of pain with failed updates, many dozens of hours wasted, spending oodles of time shutting off the noxious Update Tool Virus that MS puts out. This attempt took me most of the day. But it is fixed. The Media Creators Tool, creating your own DVD or USB drive, then just running the setup.exe from inside W10, and using the "keep files and apps", is just like an update and actually worked with my NVME drive. All my apps and everything seem to be fine so far.
I'm afraid of what the next Fall Creators update will bring. Will it work any better? Thanks for nothing Microsoft.
I've got the same problem. I have a Samsung 960 Evo as the system disk.
Microsoft could not follow new Technologies, I guess. They still could not fix the installation problem for all the creator updates on NWME drives.
I tried every method for 1709 creator update. I only managed to install 1709 with a clean install.
I am really fed up with not closing the updates properly and do a clean install everytime Microsoft decides to release a new creator update. Last time I had to install every software again, it was really annoying, even if the Windows keeps the old files.
Today again, Windows tried to update to the new creator update, 1803, and failed again.
It is really disappointing to see the same issue on 1709 is still going on, it's been more than a year. I guess they are waiting for Windows 11 to fix.
If you find a good solution except than clean install, I'd really like to hear.
Thanks.
The latest version of Win10 has worked perfectly for me, but clearly hasn't for everyone.
I suggest telephoning MS Support and complaining and have them log and escalate the issue and your hardware. It won't fixed unless they know about it.
Hi all,
I have the same problem.
My setup : MSI X99A GAMING 7 with Samsung 960 EVO 250Gb.
Do you think I could upgrade windows 10 on my computer with the last ISO of windows 10 (with 1709 update).
I saw on this forum, people has cloned their NVMe on a ssd disk, made the upgrade on ssd and clone back the ssd to nvme. Apparently, it works...
What is the best method to correct this issue ?Hi all,
I've reinstalled my computer from scratch, with W10 1709 iso. My data are on other disk, so I don't waste my time to backup everything, i've just reinstalled drivers and software.
I hope the next update won't be a new problem with NVMe SSD.- I skip the version 1709. I have upgraded my system from 1703 to 1803. Worked for me.
I tried to BLOCK EVERYTHING Upgrade/Update -related with my firewall (even kill processes), gone to scheduler and deactivated everything there is related to the update mechanisms AND STILL IT WILL TRY TO UPGRADE!!! i'm gettin really annoyed by this!
PLEASE MAKE IT STOP!!!!
My System
MSI x99a Gaming 9 ACK
Samsung 960 Pro M.2 2280 NVMe 512GB
OBVIOUSELY Windows 10 :(
Why was the last message here deleted? It suggested a fix in the next Windows update.
Microsoft, you really are beyond contempt. Look up the word "COMMUNICATION".
No wonder Apple is beating you in many markets. No wonder Sony and Nintendo have beaten you into the ground in the console market (globally).
Incompetent company!
- My 2 posts with the solution were reported as spam...
I wrote it also on the msi-forum, so you can check this out there (the link was posted by another mate above).
Greetings
Hi guys,
I have great news. It looks like that the new Spring Creators Update will solve our problems. I am right now with that distribution (updated from the anniversary update) working without any problems and after avoiding the BSOD while updating.
Credits to the user "msi" from the msi forum:
https://forum-en.msi.com/index.php?topic=301785.0
I copy/paste from his thread (links at the msi forum post):
"I found a solution for this struggle I had the last 8 month!!
I just tried everythind but a clean install. So now I thought about not installing 1709, but 1803 which was released as final some days ago.
With this trick I got my PC on WIN 10 1803:
-Download ISO File: Deskmodder I used the x64 german file, but most of you might need the english one.
-Download ISO to bootable USB tool unetbootin
-Create a flashdrive with latest ISO
-Restart PC
-Navigate in explorer, open setup.exe on USB medium
-Choose install and keep data/settings
The installation process starts and keeps up - no error after reboot!
I don't know if MS did any changes with this new function update, but main thing is that it works like charm!"From my side I have also a small contribution. You should install the package which has your language, otherwise you will not be able to upgrade without losing your apps/programs due to language incompatibility. That was my case. I could not find .iso files for my language, only RU, EN, and DE.
My solution was to register as insider and to download the last iso available directly from microsoft (the page only works with edge!!!):
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso
Probably you can download that withouth being insider, but I did it after registering so I do not know if that is a prerequisite or not. Right now the most updated version was the build 17127.
After choosing the last build and my language, the iso file was downloaded, I mounted it (you have that option built in windows) and then I did the install directly from the setup.exe as usual (it is not necessary to use an usb stick). Everything went smoothly and my windows was updated without any BSOD and I do not get the annoying forced updates anymore.
As a suggestion, after updating to the build 17127, I recommend to look for updates and update to the build 17133 (Windows 1803) as that will be the final public version for the Spring Creators Update. I did that and then I left the windows insider option so that I do not get more updates from that source, only from public releases.
I guess that it will be possible to get the update through the windows update soon (in 10 days or so) but they are 10 days of getting again the annoying update messages, reboots and dealing with the update orchestrator.
Please, if it works for you, post it here, so that we know it is working.
Greetings
Thank you Constantino Grau Turuelo. I did as you explained. Subscribed to the Windows Insider Program, downloaded, mounted and launched the setup of the windows 17127 build iso and now I'm successfully running on windows 1803.
The windows 1709 perpetual update fail restart nightmare is over! I don't thank you microsoft, because it was five month of disastrous experience with your OS.
Same problem here. This has been going on for at least half a year or longer and now i even get a warning that my current win 10 version (1607) will not be supported anymore come april. This is completely unacceptable. A fix has been promised for months and months.
MSI X99a gaming pro carbon
samsung evo 960 evo
Hi
Just experienced the same problem, I'm running 1703, and had no problems. Changed Updates to Company under advanced settings for updates, and set that function updates should be delayed for 365 days, hope this keeps 1709 from trying to install all the time.
I'm running on MSI X99A Raider w/ Samsung 960 Evo NVME.
From reading in this forum, it unfortunately doesn't seem that Microsoft cares a lot of their customers :( If engineers Pernille-Eskebo can't seem to fix the problem in in half a year, can we be sure that it will be fixed ever?
Dear Microsoft, When You're aware that quite a bunch of people are experiencing problems, then at least make a tool that delays the function updates, until a fix for the problem(s) is at hand (automatic check) for the people that are experiencing these problem(s) - I think quite a lot of people are affected with this problem, so that would give a reason for the development of such a tool - Or move on and get the problem fixed. Half a year seems a bit out of proportion for fixing this issue!
Best regards
Kim
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 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.
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...
