David McFarland

Do you get any more output above that? Do you get a windows error reporting box when it fails? If you do get an error reporting box, and you have...

That does look like the same problem, since it ran for a little while successfully before failing. I would still try disabling authenticode to see if it's more stable.

Oh, also, which CPU do you have exactly?

Ok, thanks for trying that. You're certainly seeing the same problem I have. I've been running with authenticode disabled, and the system seems fairly stable. Just keep an eye out...

Sorry for the delay. Yeah, that looks like it's failing as well... Our (launch window) processors were failing in both linux and windows, but the RMA ones only fail on...

@kikijiki Well shit, I was hoping to buy one of those, but I'm hesitant until I know more about what's causing this. Which MB are you using?

The no-op changes seem to come from roslyn. This change suppresses them for me: ```diff diff --git a/src/Formatters/WhitespaceFormatter.cs b/src/Formatters/WhitespaceFormatter.cs index b7fecac..57abfe5 100644 --- a/src/Formatters/WhitespaceFormatter.cs +++ b/src/Formatters/WhitespaceFormatter.cs @@ -55,7 +55,8 @@...

We've found that authenticode needs to be enabled for this crash to happen, which makes sense based on the call stack.

@alexat Thanks for posting. My experience is that the post-RMA chip (week 39) no longer crashes in the linux test, but still crashes with this one. AMD also confirmed they...

I've been able to get `fcontext` working in cygwin as described here: https://cygwin.com/pipermail/cygwin-developers/2020-September/011970.html It also seems the `ucontext` is broken for the same reason that `fcontext` was: https://cygwin.com/pipermail/cygwin-developers/2021-December/012536.html