Has the mscorlib recursive resource lookup bug been fixed?

Question

Recently I have been getting this fatal error sporadically and it crashes the computer so that it displays a black screen.
This is one of the instances where we were able to observe the error message before completely crashing.

I have used the same code before in other projects and it is part of a socket packet writer.
The place where it starts from in my C# code I call string.Format:

public static void WriteInt( BinaryWriter bw, int intValue, DSize dSize, ref byte bcc )  
        {  
            byte[] bytes;  
            switch ( dSize )  
            {  
                // 2-digit: 00->99  
                case DSize.D2:  
                    bytes = Encoding.ASCII.GetBytes( string.Format( "{0:D2}", intValue ) );  
                    break;  

                // 3-digit: 000->999  
                case DSize.D3:  
                    bytes = Encoding.ASCII.GetBytes( string.Format( "{0:D3}", intValue ) );  
                    break;  

                // 4-digit: 0000->9999  
                case DSize.D4:  
                    bytes = Encoding.ASCII.GetBytes( string.Format( "{0:D4}", intValue ) );  
                    break;  

                default:  
                    throw new Exception( "Unknown byte size!" );  
            }  
            XOR( bytes, ref bcc );  
            bw.Write( bytes );  
        }  

Using
* Japanese version Windows 10
* .NET Framework Ver. 4.8
* No recursion involved on my part; and called on a Task.

Has Microsoft fixed this bug or are they trying to?