Problem
An automatic antivirus scan starts during the broadcast and causes unexpected disk and CPU spikes.
Solution
Root Cause / Diagnostic:
Scheduled background antivirus scans initiate exhaustive disk indexing, file heuristics, and memory analysis that peg CPU cores and storage bandwidth at 100%. When an automated scan triggers mid-broadcast, real-time priority threads allocated to video capture and hardware encoding become preempted by high-privilege security services. This instantaneous resource starvation leads to catastrophic stream buffering, encoder failure, and dropped frames.
Actionable Fix:
1. Configure antivirus software (e.g., Windows Defender or third-party suites) to add system exclusions for OBS Studio binaries, temporary recording directories, and media assets.
2. Enable 'Do Not Disturb' or 'Gaming Mode' in your security suite, and disable scheduled scans entirely during designated broadcast operational hours.
3. Verify running background processes in Windows Resource Monitor before launch to confirm background Antimalware Service Executable CPU draw is at 0%.
Pro Tip:
Create a dedicated broadcast user profile in Windows with automated maintenance, telemetry tasks, and indexing services permanently disabled during live operations.
Scheduled background antivirus scans initiate exhaustive disk indexing, file heuristics, and memory analysis that peg CPU cores and storage bandwidth at 100%. When an automated scan triggers mid-broadcast, real-time priority threads allocated to video capture and hardware encoding become preempted by high-privilege security services. This instantaneous resource starvation leads to catastrophic stream buffering, encoder failure, and dropped frames.
Actionable Fix:
1. Configure antivirus software (e.g., Windows Defender or third-party suites) to add system exclusions for OBS Studio binaries, temporary recording directories, and media assets.
2. Enable 'Do Not Disturb' or 'Gaming Mode' in your security suite, and disable scheduled scans entirely during designated broadcast operational hours.
3. Verify running background processes in Windows Resource Monitor before launch to confirm background Antimalware Service Executable CPU draw is at 0%.
Pro Tip:
Create a dedicated broadcast user profile in Windows with automated maintenance, telemetry tasks, and indexing services permanently disabled during live operations.