frodr Posted September 25, 2021 Share Posted September 25, 2021 I am about to convert a Windows Server 2019 to Unraid. The this kernel panic appear during startup. I tested 3 different USB sticks in 3 different USB ports When running memtest this comes up. It it a small error, big error? And likely to cause the panic? Note that the server is running Windows Server 2019 on daily basis. Any thought will be appreciated. Quote Link to comment
JonathanM Posted September 25, 2021 Share Posted September 25, 2021 32 minutes ago, frodr said: When running memtest this comes up. It it a small error, big error? And likely to cause the panic? Note that the server is running Windows Server 2019 on daily basis. Any thought will be appreciated. Any error can be fatal. You must suspect any file that touches a system with bad RAM, as it's practically impossible to know whether or not it has been silently corrupted. Quote Link to comment
itimpi Posted September 25, 2021 Share Posted September 25, 2021 The only acceptable number of errors in memtest is zero. Quote Link to comment
trurl Posted September 25, 2021 Share Posted September 25, 2021 You shouldn't even attempt to use a computer with any RAM problems. Everything goes through RAM, the OS and other code, your data, everything. Quote Link to comment
Squid Posted September 26, 2021 Share Posted September 26, 2021 13 hours ago, frodr said: Windows Server 2019 on daily basis And probably bluescreening or having weird crashes etc Quote Link to comment
JonathanM Posted September 26, 2021 Share Posted September 26, 2021 5 hours ago, Squid said: And probably bluescreening or having weird crashes etc That's the best case scenario. If windows appears to run flawlessly with bad RAM, it's likely that there is file corruption happening silently in the background. It's much better for the system to halt at the first sign of trouble than to run like nothing is wrong while mangling your data. I'm convinced 99% of the reports of silent bit rot on otherwise healthy hard drives is caused by bad system RAM. Quote Link to comment
frodr Posted September 27, 2021 Author Share Posted September 27, 2021 Thanks for advice. The same error occur with all mem config tested, leading me suspect the mainboard. New mainboard is ordered. Quote Link to comment
ChatNoir Posted September 27, 2021 Share Posted September 27, 2021 51 minutes ago, frodr said: Thanks for advice. The same error occur with all mem config tested, leading me suspect the mainboard. New mainboard is ordered. The memory controller is most probably in the CPU, not directly on the MB. Might be a MB problem, but it is not guaranteed. Quote Link to comment
frodr Posted September 27, 2021 Author Share Posted September 27, 2021 I have another Xeon processor that I will try. That could make things a bit clearer. Quote Link to comment
frodr Posted September 28, 2021 Author Share Posted September 28, 2021 Same error with another cpu. Then I removed all pice cards, no error. Quote Link to comment
frodr Posted September 30, 2021 Author Share Posted September 30, 2021 Then I tested pcie cards, one at the time. And the devil is a Mellanox 40Gbe card. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.