Server 2016 + BSOD + Bugcheck

[Tefters]

Afternoon all,

 

7 RDS session host servers, 5 for students and 2 for staff. EG. RDSH01 through to RDSH05 and then RDSH-T01 and RDSH-T02.

The 5 student servers in a collection use UPD while the 2 staff servers use local profiles.

It use to be just 1 staff server but I have implemented a second due to the issue i'm about to detail in the hope it was an isolated incident on the first staff server but both exhibit the same issue.

 

Same base WIM custom image across all machines, only difference is the teacher servers have about 3 or 4 extra applications over the student servers (SIMS being a good example).

 

Recently I have noticed that the teacher servers are rebooting randomly which I've tracked down to BSOD. Event viewer is showing an Error BugCheck of "The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027 (0x00000000fcb0027c .........bla bla bla).

And is dumping a nice sized DMP file to the root of Windows.

 

I've yet to open the log however looking up the error code indicates back to a common error back in Win7/2008 R2 era which resulted in a MS KB patch fix.

 

I have managed to stumble across only 1 other person so far experiencing this issue out there https://developercommunity.visualstudio.com/content/problem/3146/debugging-managed-code-system-services-cause-rando.html#reply-form, he is having the exact same error while using Visual Studio on 2016 over Remote Desktop.

 

Anyone else encountering this? I'm about to start removing apps 1 by 1 from a staff server and monitor however I have yet to find the specific trigger to the BSOD so this could take a good while to test, monitor and report back.

Edited November 30, 2016 by Tefters

[Tefters]

Having thought about this a little more now I have just realised that I also have drive map through enabled for staff servers which would also relate to \\tsclient which was also noted by the other person on the visual studio MSDN forum.

 

Now I know a few of our teachers love to use portable HDD's and pen sticks and am wondering if something around this is causing the BSOD.

[Tefters]

Well ladies and gentleman after a whole week of having local drive re-direction turned off on my staff servers they have been 100% stable so here lies the issue, something to do with a call on the \\tsclient share is causing blue screen bug checks in Server 2016.

 

I have reported this to Microsoft in the hope we will see a KB patch for this, in the meantime I'm leaving this off so no-one can use USB drives/sticks through RD.

[Tefters]

Confirmed issue by Microsoft - https://social.technet.microsoft.com/Forums/exchange/en-US/cf843781-195e-418f-a124-5e40dee0d901/windows-server-2016-crashes-with-error-in-rdbsssys?forum=ws2016

 

Awaiting a fix.

[Ephelyon]

We're experiencing this too.

[AzureCloudMan]

We are getting the same thing, this is veryvery frustrating, i have an azure cloud network, where i have built an RDP server using server 2016, i have 25 live users working in it, it was fine for the first few days but then randomly started kicking us out and rebooting with no error, i assumed that it an azure infrastructure issue (we are on UK south) but now im not sure, i think its an issue with 2016 being unstable, The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027 (0x00000000fcb0027c, 0xffff9788a32cf488, 0xffff9788a32cf0c0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fa0e7a67-35a6-4146-966f-7445208f70c8.

This is the error we get after it kicks us out and reboots in the event logs. Need help ASAP!!!!

[AzureCloudMan]

We are getting the same thing, this is veryvery frustrating, i have an azure cloud network, where i have built an RDP server using server 2016, i have 25 live users working in it, it was fine for the first few days but then randomly started kicking us out and rebooting with no error, i assumed that it an azure infrastructure issue (we are on UK south) but now im not sure, i think its an issue with 2016 being unstable, The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027 (0x00000000fcb0027c, 0xffff9788a32cf488, 0xffff9788a32cf0c0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fa0e7a67-35a6-4146-966f-7445208f70c8.

This is the error we get after it kicks us out and reboots in the event logs. Need help ASAP!!!!

[Tefters]

We are getting the same thing, this is veryvery frustrating, i have an azure cloud network, where i have built an RDP server using server 2016, i have 25 live users working in it, it was fine for the first few days but then randomly started kicking us out and rebooting with no error, i assumed that it an azure infrastructure issue (we are on UK south) but now im not sure, i think its an issue with 2016 being unstable, The computer has rebooted from a bugcheck. The bugcheck was: 0x00000027 (0x00000000fcb0027c, 0xffff9788a32cf488, 0xffff9788a32cf0c0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: fa0e7a67-35a6-4146-966f-7445208f70c8.

This is the error we get after it kicks us out and reboots in the event logs. Need help ASAP!!!!

 

On your RDS Server Collection turn off USB passthrough, this is the only fix at present and has been since I first discovered it late November.

 

Microsoft have a patch coming out this month to fix it (should of been last month but February patching got canned).

[AzureCloudMan]

Ok thanks mate, so in the collection settings will unticking the plug and play devices do the trick?

[Tefters]

Ok thanks mate, so in the collection settings will unticking the plug and play devices do the trick?

 

Sorry should of been more specific, Drive passthrough.

[AzureCloudMan]

thanks, some of the users have usb printers, i hope these carry on working through, thanks for you help mate, keep us updated on that patch

[AzureCloudMan]

Hi all, i had a case open with microsoft as we have a support contract with them and they have provided the following update:

 

Hope this email finds you well.

The fix has been delayed to March 14, 2017.

 

Meanwhile the resolution will be:

 

• Try using direct FQDN links to the server shares instead of mapped drives.
  
• Disable any drive, folder, printer redirection on the RDP client.
  
• If you are encountering this stop code when plugging removable storage into a client RDPed into a host server, then disable USB redirection in RDS to circumvent the issue in this scenario.
  
• Install the March 14, 2017 patch Tuesday update on the affected WS 2016 server.
  

 

 

Hope this information is useful for you.

 

Kind regards,

 

 

 

Visit the Windows Azure Support page regarding available support plans: Support Plans

For the latest news regarding Windows Azure, visit the site: Microsoft Azure

 

Azure Status | Create a Case

[Arthur]

Awaiting a fix.

I think it's fixed. The changelog mentions remote desktop.

 

https://support.microsoft.com/en-us/help/4013429/windows-10-update-kb4013429

[Tefters]

Yup that's the fix, good old patch Tuesday