You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
Run Companion 3.3.0 or higher
CRASH
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
The text was updated successfully, but these errors were encountered:
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 (#2735bitfocus/companion-satellite#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.
Is this a bug in companion itself or a module?
Is there an existing issue for this?
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
Expected Behavior
No response
Environment (please complete the following information)
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
The text was updated successfully, but these errors were encountered: