This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Good morning, I am having an issue on some PCs recently after some PCs received the Windows 10 2004 build update. After receiving said update, the machines will BSOD with a 0x027 error code when logging into a domain profile while connected to the network.
If I remove the network cable from the PC and log into a domain account that was cached on the machine before the update, it will log in without issues and then I can connect it to the network and it seems to resume function. I can also sign into a local account on the machine, with and without network connectivity.
I used Bluescreen View to look at the dumps which seem to be showing rdbss.sys and mrxsmb20.sys as drivers that are causing the issue. I have tried updating network drivers etc from the vendors websites and not relying on Windows to, but am still having the issue.
The other bizarre thing is if the PC crashes 3 times, boots into the recovery mode to try and repair your PC and I restart it, it will then log in once to a domain account and seem to be functioning, however if the PC is restarted it will BSOD on log in.
Has anyone seen or heard of any issues like this since this update? Could it be something out dated on the server that is causing the issue to happen to the machines on the newer OS? I can't help but feel like it has something to do with folder redirection and that is why cached accounts will work with no network connection however I am stumped how to get around this other than not updating every other machine, and rolling back if possible (I had a PC that was upgraded from Windows 7 to 10 and went straight to the 2004 build and BSOD'd, I tried to roll back to Win7 and system will not boot at the moment saying it is missing system files etc.).
I have some mini dumps I can share if that would help as I would like to get to the bottom of this if possible.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I confirmed this is the case, a group of users with a Group Policy mapping their home drives to a drive letter, when logging into a 2004 windows 10 install bluescreened on login. When logging into 1909 installs, they could log in without an issue.
We removed their home drive from the group policy, instead mapping this via their AD account in the profile tab.
Users could then log in without issue.
I can confirm that BSOD happened if we have one redirected folder (Documents in my case) and the same folder also mapped to the network drive, even if network connection to the domain network is fine (both PC and DC are in same L2).
Just disabled the drive mapping for this share - and no BSODs on logon anymore.
If what we're told in this thread is correct, (1) a patch will be released 3rd week in November unless they have problems during internal testing, in which case it will be pushed out to January, and (2) 20H2 does not include the fix either.
I hope they release the patch to fix this soon. It is really difficult when it occurs for a remote user.
Did the update on two computers. one keeps crashing the other I have not take much time to review due to the first one. The second computer didnt crash as much as the other. One is a new Surface crashes often, and the other is a HP a new HP Zbook that randomly crashes. Both get the same blue screen error and do not blue screen when logging on local.
