Repository navigation
[GUI] Strata Desktop 0.2.7/0.2.8 causes system-wide Windows freeze immediately after launch (0.2.6 works) #4661
Description
Problem
Strata Desktop 0.2.7 and 0.2.8 cause a system-wide Windows freeze immediately after launching the application.
No user interaction is required to trigger the problem. No model is loaded.
The system drive (C:) reaches 100% active time and remains at 100%, while disk read/write throughput is approximately 0 KB/s. Windows becomes unresponsive, eventually requiring a forced power-off.
Strata Desktop 0.2.6 works normally on the same machine.
Environment
OS: Windows 11 Home, build 26300 (
windows 10.0.26300in Strata logs)CPU: Intel Core i9-9900K (8 cores / 16 threads)
RAM: 128 GB DDR4
Primary compute GPU: NVIDIA Tesla V100-PCIE-32GB (32 GB VRAM, sm_70, TCC mode)
Additional GPU: NVIDIA GeForce RTX 3060 12 GB (Device Manager Code 31; currently unusable)
NVIDIA driver: 582.99 (V100)
Inference engine: Strata engine 0.1.52, successfully detected by Desktop 0.2.6
Desktop versions tested: 0.2.6, 0.2.7, 0.2.8
Model: None loaded when the freeze occurs
Steps to reproduce
Start Windows normally.
Launch Strata Desktop 0.2.7 or 0.2.8.
Do not interact with the application after launching it.
Observe the system drive (C:) reaching 100% active time and remaining stuck there, despite disk read/write throughput being approximately 0 KB/s.
Windows becomes increasingly unresponsive. The taskbar, Task Manager, PowerShell, and other applications stop responding.
No model loading, inference, or Settings interaction is required.
Expected behavior
Strata Desktop should launch normally without affecting the responsiveness of Windows, as it does with version 0.2.6.
If an internal host process or component fails to initialize, the application should display an error or terminate safely instead of causing a system-wide freeze.
Actual behavior
The C: drive's active time reaches 100% and stays there.
Disk read/write throughput is approximately 0 KB/s despite the reported 100% active time.
The Windows taskbar and desktop context menus stop responding.
Task Manager, PowerShell, Notepad, and other applications become unresponsive.
Mouse movement may remain possible, but clicks and keyboard input stop working.
Chrome Remote Desktop becomes unreachable.
Terminating the Strata process does not necessarily restore system responsiveness.
Windows cannot be restarted normally and requires a forced power-off.
This behavior occurred repeatedly with 0.2.7 and again with 0.2.8.
Version comparison
| Version | Result |
|---|---|
| 0.2.6 | Works normally. V100 and 128 GB RAM are detected; inference works. |
| 0.2.7 | System-wide Windows freeze after launching. |
| 0.2.7.1 | Not tested. |
| 0.2.8 | Same system-wide Windows freeze after launching. |
Reverting to 0.2.6 restores normal application operation.
Relevant logs
Strata Desktop 0.2.8 (affected)
[shell] Strata desktop 0.2.8 starting (pid 2484)
[shell] System: windows 10.0.26300
[host] engine bundle: kept in the install folder (0.1.46-windows-x86_64-cuda-cuda13 is not (or not completely) in the engine store)The log ends here. No [host] strata host message appears.
Strata Desktop 0.2.6 (working)
[shell] Strata desktop 0.2.6 starting (pid 6516)
[shell] System: windows 10.0.26300
[host] engine bundle: kept in the install folder (0.1.46-windows-x86_64-cuda-cuda13 is not (or not completely) in the engine store)
[host] strata host ... http://127.0.0.1:47831
[host] hardware ... Tesla V100-PCIE-32GB / cuda / 8 cores / 128 GB
[host] inference ... Strata engine 0.1.52 is installed; no model is loaded yetThe cuda-cuda13 engine bundle message is present in both working and affected versions, so this message alone does not appear to explain the freeze.
Strata Desktop 0.2.7
The logs from 0.2.7 showed inconsistent startup progress: some attempts reached hardware detection, while others stopped after the initial startup messages.
No definitive crash exception was recorded.
Windows Event Viewer findings
I inspected Windows event logs after the freezes:
No matching Application Error / Application Hang / Windows Error Reporting events were found in the inspected time windows.
No matching storage or NVIDIA GPU driver warning/error events were found in the inspected System log interval.
Kernel-Power Event ID 41 and EventLog ID 6008 were recorded following forced shutdowns.
Windows reports the physical disks as
Healthy / OK.
These observations do not rule out a driver, storage I/O, or host initialization issue.
The system drive reaching 100% active time with approximately 0 KB/s throughput may indicate stalled I/O, but the underlying cause has not been identified.
Reproduction status
Reproduced locally with both 0.2.7 and 0.2.8.
Strata 0.2.6 works with the same V100 GPU, NVIDIA driver, RAM, and Windows environment.
Because the affected versions can freeze the entire operating system and require forced shutdowns, I have stopped further reproduction attempts for now.
Request
Could you investigate changes to Desktop startup, host initialization, or component handling introduced between versions 0.2.6 and 0.2.7?
In particular, I would appreciate guidance on whether there are any known compatibility issues involving:
Windows build 26300
Tesla V100 (sm_70, TCC mode)
Mixed NVIDIA GPU environments where a second GPU is present but unavailable (Code 31)
Desktop host initialization and disk I/O
I can provide additional sanitized logs and perform read-only diagnostics, but I would prefer to avoid repeating the system-wide freeze.
Thank you for your work on Strata!
Activity
Monitor: the drive-temperature reader (every physical drive, from the…
gentia commentedon Oct 31, 2026
Thank you so much for investigating this issue and pushing a fix so quickly, @Niko1221 ! ☕
I really appreciate your work on Strata!
I'll test the fix once it's available in a release and report back with the results.
Niko1221 commentedon Oct 31, 2026
0.2.9 is out now, so you can test it. We found one change in 0.2.7 that fits what you saw: the app read the temperature of every disk from the first second, even with the Monitor page closed, and on some PCs that kind of query can stall the system. It now runs only while the Monitor page is open. We couldn't try this on your PC, so we don't know yet that it's the cause. Please tell us if the freeze is gone. If it isn't, please send the model names of your disks. Keeping this open until we hear from you.
gentia commentedon Oct 31, 2026
Hi @Niko1221, thank you for the quick response and the fix!
I tested Strata Desktop 0.2.9 on the same machine.
The application now launches successfully, but unfortunately the system-wide freeze still occurs when I try to open the Settings window.
The 0.2.9 desktop log confirms that host initialization completes and the V100 is detected:
As requested, these are the disk models installed in my PC:
Windows reports all three disks as
Healthy / OK.I haven't confirmed whether disk active time reaches 100% again in 0.2.9.
The startup behavior appears to have improved, but the freeze is not completely resolved. I have stopped further reproduction attempts because Windows becomes unresponsive and may require a forced shutdown.
Please let me know if there are any safe, read-only diagnostics I can run to help narrow down the cause.
Thank you again for your help!
gentia commentedon Oct 31, 2026
Hi @Niko1221, I found a significant clue!
Strata Desktop 0.2.9 now appears to work normally when I run it as Administrator.
On the same machine:
I also tested the disk temperature query:
PermissionDenied (MI RESULT 2)errors.$c.Count = 1.This suggests a possible permission-dependent difference in the storage telemetry path. In particular, the non-elevated query may trigger the
DeviceIoControlfallback, whereas the elevated query can return temperature data directly.However, since v0.2.9 should only start temperature telemetry when Monitor is open, I can't yet confirm that this is the actual cause.
Running as Administrator seems to be a workaround, but I hope the application can eventually run safely without elevation.
Thank you again for investigating!