This source thread contains a useful community-verified stability experiment, but not a proven kernel root cause. An Aoostar R1 with Intel N150 would run ZimaOS for roughly a day and then hard-lock: the display went blank, ping stopped, and the WebUI became unreachable until power was cycled.
The original poster eventually added several Intel i915 power-management parameters plus an NVMe power-state parameter to ZimaOS's boot command line. Four days later they reported continuous uptime and called the change successful. That is meaningful user verification, but no crash dump tied the failure to one specific i915 feature, the NVMe controller, or both.
This Was a Full Host Lock, Not a Single App Crash
The source symptoms were a blank display, failed ping, an unreachable WebUI, and a required physical power cycle. That failure class is broader than a crashed Docker container or stale browser session and should be investigated at host/kernel/hardware level.
The Same Mini PC Had Been Stable Under Unraid
The user said the Aoostar R1 had stayed stable for several days under Unraid while preclearing drives, then began freezing daily after ZimaOS was installed. That made a software/driver interaction plausible, but different operating systems use different kernels, drivers, and power policies on the same hardware.
i915 and NVMe Power Management Became the Main Community Hypothesis
The user found ZimaOS's boot command line at /mnt/boot/cmdline.txt and appended:
nvme_core.default_ps_max_latency_us=0
i915.enable_psr=0
i915.enable_fbc=0
i915.enable_dc=0
i915.enable_guc=0These were user-selected troubleshooting parameters, not an IceWhale-prescribed standard configuration for Intel N100/N150 systems.
The User Reported Four Days of Uptime After the Change
On November 21, the original poster returned and said the system had reached four days of uptime and was still running. This supports the conclusion that the changes improved that machine's stability, but it does not isolate which parameter mattered.
IceWhale Separately Suggested Testing with Search Disabled
Zima-Giorgio pointed to other reports where disabling ZimaOS Search improved stability on some machines. That is separate official troubleshooting guidance and should not be merged with the i915/NVMe theory as though IceWhale confirmed the same cause.
Crash Evidence Is More Valuable Than Tweaking Every Possible Power Setting
Another participant warned that without dump or previous-boot logs, users can end up changing GPU power, NVMe power, ASPM, C-states, networking, and Search without knowing which layer actually failed. For a current case, collect the previous boot's kernel/system logs after recovery and compare the timestamps around the last successful activity.
Generic x86 Support Does Not Mean Every Mini PC Power Policy Is Pre-Validated
Current ZimaOS officially supports generic x86-64 hardware, but third-party motherboards, storage controllers, graphics adapters, and NICs can need additional compatibility checks.
Use the current third-party x86 troubleshooting boundaries before assuming an N150 lockup has one universal fix.
A Safer Current Troubleshooting Order
- Update to the current stable ZimaOS release.
- Record BIOS version and restore conservative firmware defaults.
- Collect previous-boot kernel/service logs after a crash.
- Check SSD/NVMe health, temperature, RAM, and power.
- Test whether Search or another reproducible workload correlates with the lock.
- Change one boot parameter at a time when practical.
- Keep a copy of the original boot command line so the change is reversible.
Aoostar N150 Freeze FAQ
Did the source user report improved stability?
Yes. They reported four days of uptime after changing i915 and NVMe power-related boot parameters.
Did IceWhale confirm i915 was the root cause?
No. IceWhale separately suggested testing with Search disabled; no dump log confirmed the exact failure source.
Should every Intel N150 ZimaOS user disable PSR, FBC, DC, and GuC?
No. Those settings were a source-specific troubleshooting experiment, not a universal recommended configuration.
