Model: TS-464
RAM: 16GB Crucial (2x8GB)
Previous stability: ~2 years stable operation
Issue description
After upgrading to QTS 5.2.8, my NAS started experiencing random restarts and unexpected shutdowns. These issues had never occurred before on this hardware configuration.
The system had been running completely stable for approximately 2 years using the same Crucial RAM modules, with no crashes, freezes, or unexpected reboots.
Steps taken to isolate the issue
To rule out hardware failure, I performed multiple tests:
-
Ran MemTest86 on both RAM modules → no errors detected
-
Verified system logs (no consistent hardware fault indicators)
-
Downgraded firmware to QTS 5.2.7.3297
-
Tested older version QTS 5.1.9 as well
Result
-
On QTS 5.2.8 → random reboots / shutdowns occurred
-
On QTS 5.2.7.3297 → system is fully stable again (currently running for multiple days with 0 issues)
-
Same exact hardware, same configuration, no other changes
Conclusion based on testing
Given the consistent behavior across firmware versions, this strongly suggests a firmware-level regression or compatibility change introduced in 5.2.8, rather than a hardware issue.
The RAM itself appears healthy based on MemTest86 and long-term prior stability.
Support interaction
When contacting QNAP support, the only recommendation provided was to use QNAP-certified memory modules (TS-464-8G(Q23AF055243)), without addressing the firmware behavior difference between versions.
While I understand official compatibility guidelines, this does not explain:
-
Why the system was stable for ~2 years on the same RAM
-
Why the issue appears only on 5.2.8
-
Why the issue disappears completely after downgrading to 5.2.7.3297
Current workaround
Due to stability requirements, I have:
-
Disabled automatic firmware updates
-
Remained on QTS 5.2.7.3297 where the system is fully stable
Request / Discussion
Has anyone else experienced similar behavior after upgrading to QTS 5.2.8 with non-QNAP certified RAM?
Specifically:
-
Random reboots or shutdowns
-
Stability restored after downgrade to 5.2.7.x
It would be helpful to know if this is an isolated case or a broader compatibility regression.
Additionally, if QNAP engineering is aware of any changes in memory handling, training, or compatibility enforcement in 5.2.8, clarification would be appreciated.
