[BUG] BSOD when running Companion

[Yabbuck]

Is this a bug in companion itself or a module?

• [X] I believe this to be a bug in companion

Is there an existing issue for this?

• [X] I have searched the existing issues

Describe the bug

I've been experiencing random BSODs (Blue Screen of Death) while running shows using vMix along with Companion 3.3.1. The BSODs don't always appear immediately. Sometimes, the machine runs for 24 hours without crashing, while other times, it crashes within minutes.

After troubleshooting for hours and running several hardware test suites, I discovered that I could most reliably trigger a BSOD by repeatedly running and quitting Companion. Since I wasn't sure what else to try, I performed a clean installation of Windows 11.

The machine remained stable while I reinstalled vMix and other software. However, as soon as I installed Companion (by this time, version 3.4.0 had been released) and ran it for the first time, the BSODs returned.

Now, every time I start Companion 3.4.0, I reliably encounter the following BSOD errors:

[DRIVER_IRQL_NOT_LESS_OR_EQUAL] [PAGE_FAULT_IN_NONPAGED_AREA]

I also get the same results with Companion versions 3.3.1 and 3.3.0. Versions lower than that haven't crashed instantly and I am currently running 3.2.2.

The machine has so far never crashed without Companion running.

Steps To Reproduce

1. Run Companion 3.3.0 or higher
2. CRASH
3. repeat

Expected Behavior

No response

Environment (please complete the following information)

- OS: Windows 11 Pro
- Browser: Microsoft Edge Version 128.0.2739.79
- Companion Version: multiple Versions. most reliable crash on 3.4

Additional context

Windows version: Windows 11, 10.0, version 2009, build: 22631 (x64) Hardware: ASRock, X299 Taichi CLX CPU: GenuineIntel Intel(R) Core(TM) i9-10900X CPU @ 3.70GHz 8664, level: 6 Processor count: 20 logical processors, active mask: 1048575 RAM: 32449,7MB

[MeestorX]

BSOD are almost always a driver or hardware failure. Nothing to do with Companion.

[Julusian]

I think it is possible that we could be causing this, there are a couple of other reports of the hid library we use causing crashes of companion/satellite on occasion (#2735 https://github.com/bitfocus/companion-satellite/issues/141), but causing a blue screen is new and fills me with such confidence on windows..

But this enters the unfortonate area of without being able to reliably reproduce it myself, attempting to fix it becomes a game of re-reading all the code and trying to find any mistakes that I didn't see in the last read, or guessing on what the cause and trying to fix that.

[Yabbuck]

Thanks for commenting. I'll try to rule out any hardware failure by swapping ram and mobo whenever I find the time.

[Julusian]

I've added a library that will log certain crashes that wouldn't have been logged before. It's only in the betas for now

If you're willing to try running that and sharing the log that it produces, that should help narrow down the cause of this

[MatthewGrantAU]

We also have BSOD issues for the last few weeks on our vMix PC with Companion. Not sure what version was running when this began, but tried 3.4.4 which still crashes, tried going back to 3.2.2 as mentioned above, but this still crashes also. It occured on Win 10 Home and we clean installed Win 11 Home and it has continued to occur. The machine does not BSOD if Companion is not running, and when it is running, the crashes occur 20min - 2hr after restarting Companion. We've seen both: [DRIVER_IRQL_NOT_LESS_OR_EQUAL] [PAGE_FAULT_IN_NONPAGED_AREA]

We might give the current beta a go this week and try to capture some data.

[DynamoBen]

Are you using the PTZoptics module too? I am and ran into this bug. I moved to a raspberry pi with the same config and had lockups. I removed the PTZoptics module and I have not seen any lockups. I haven't moved back to the PC to see if removing the plugin fixes the BSOD.

[Julusian]

Has anyone seen anything like this recently? Without confirmation that this is still happening and some logging from the library I added this is stuck as not being reproducible

[Julusian]

Without any confirmation that this is still happening, I think it best to close this. If you are still seeing this, this can either be reopened or a new issue opened