M
Matthew J Hibberd
Hi
Wondering if somebody could assist.
We may have identified a genuine bug here in the SMB Bandwidth Limits feature in Server 2016. I cannot find any evidence online that anyone else has experienced this, however it is 100% repeatable every time, regardless of whether Server 2016 is running on physical hardware or in a VM.
We have also tested this on various patching levels, from completely unpatched to fully patched with no difference in results.
In good old KB Article speak, consider the following:
The machine will then immediately blue screen with Bugcheck 0x0000003b. Analyising the memory dump that is generated presents the following:
PRIMARY_PROBLEM_CLASS: 0x3B_SmbBandwidthLimitFilter!SchedDispatchDeviceControl
Can Microsoft support test and investigate if possible? We initially disovered this in a production S2D cluster, however after much testing, it doesn't matter where this is demonstrated, it will happen every time.
If anybody dares reply with "Please try running SFC /ScanNow", there will be a reckoning
Thanks
Matthew
Continue reading...
Wondering if somebody could assist.
We may have identified a genuine bug here in the SMB Bandwidth Limits feature in Server 2016. I cannot find any evidence online that anyone else has experienced this, however it is 100% repeatable every time, regardless of whether Server 2016 is running on physical hardware or in a VM.
We have also tested this on various patching levels, from completely unpatched to fully patched with no difference in results.
In good old KB Article speak, consider the following:
- You create an SMB Bandwidth limit using the "Set-SMBBandwidthLimit" cmdlet.
- You then attempt to remove the previously created SMB Bandwidth Limit using the "Remove-SMBBandwidthLimit" cmdlet.
The machine will then immediately blue screen with Bugcheck 0x0000003b. Analyising the memory dump that is generated presents the following:
PRIMARY_PROBLEM_CLASS: 0x3B_SmbBandwidthLimitFilter!SchedDispatchDeviceControl
Can Microsoft support test and investigate if possible? We initially disovered this in a production S2D cluster, however after much testing, it doesn't matter where this is demonstrated, it will happen every time.
If anybody dares reply with "Please try running SFC /ScanNow", there will be a reckoning
Thanks
Matthew
Continue reading...