ti="00320670-C1257F1B" sq="00000DB3" THREAD [0F10:000C-3528] WAITING FOR WRITE LOCK ON FRWSEM 0x3ABD (@17EDC2F4) (R=0,W=1,WRITER=0F10:4524,1STREADER=0000:0000) FOR 30000 ms
ti="00321228-C1257F1B" sq="00000DB7" THREAD [0F10:000C-3528] WAITING FOR WRITE LOCK ON FRWSEM 0x3ABD (@17EDC2F4) (R=0,W=1,WRITER=0F10:4524,1STREADER=0000:0000) FOR 30000 ms
ti="00321DE0-C1257F1B" sq="00000DC0" THREAD [0F10:000C-3528] WAITING FOR WRITE LOCK ON FRWSEM 0x3ABD (@17EDC2F4) (R=0,W=1,WRITER=0F10:4524,1STREADER=0000:0000) FOR 30000 ms
ti="00322998-C1257F1B" sq="00000DC3" THREAD [0F10:000C-3528] WAITING FOR WRITE LOCK ON FRWSEM 0x3ABD (@17EDC2F4) (R=0,W=1,WRITER=0F10:4524,1STREADER=0000:0000) FOR 30000 ms
A manually created Notes System Diagnostics (NSD) from the server having the issue you will see the following nHTTP thread if experiencing the same problem:

Note: We read this from bottom to top. Notice how our extension manager (nEVDominoEM) goes down the path of calling CoInitializeEx and then immediately CoUnintialize leading to RtlEnterCriticalSection.