MSI Creator TRX40 - Error 56 ACPI 15 Crashes

[davisrichardg]

I have an MSI Creator TRX40 (BIOS/UEFI fully up-to-date as of today), an AMD Threadripper 3970X, 128GB DDR4 3600 RAM. When I leave the system idle, it will randomly crash and reboot into the BIOS. At that point, the 1st NVMe drive shows as not detected, but upon a power cycle it works without issue and boots back into Windows. This process will continue to happen, randomly, but again, ONLY when the computer is at idle. I've stress tested the CPU, GPU, Memory, and Disks, and the system performs flawlessly. I don't think it has anything to do with the drive, as the health check and SMART status show no issues. As to why the first Sabrent PCIe 4.0 NVMe drive will show as not detected and the system will boot into the BIOS when this happens - I assume it's because of Windows crashing and the drive controller becoming confused or in a non-stable state. A power off/power on always works without issue, and the drive is always detected, with the computer booting back into Windows.

In the System event log, every time this happens there will be Error Code 56 ACPI 15 error messages.

I have reset the BIOS settings, enabled XMP so the memory runs at 3600MHz instead of 2100MHz, enabled CPU Virtualization, and that is it -- no other settings changed. No overlclocking, no tweaks.

The last thing I've just tried is "Global C-State Control", which was set to Auto. I have changed this to Disabled and am waiting for the problem to happen again. I have doubts this will fix it, but I saw it as a suggestion.

Any help would be appreciated.

 

[laurence1211]

Did that fix it?

 

[davisrichardg]

Actually, what fixed it was downloading the newest chipset drivers from AMD directly, and not using the ones offered by the MSI Creator app. The system is completely stable now, and I have reverted "Global C-State Control" to Auto.

 

[giann150a02d3]

Actually, what fixed it was downloading the newest chipset drivers from AMD directly, and not using the ones offered by the MSI Creator app. The system is completely stable now, and I have reverted "Global C-State Control" to Auto.

Did you menage to fix the problem for good? I have a similar set up and have been having the same problem for the good part of a year (since I built the workstation). The last thing I've tried is your suggestion above, which I thought had finally fixed the problem, but then came back after 2 full days of stability. Don't know what else to try.

 

[Alan J T]

Did you menage to fix the problem for good? I have a similar set up and have been having the same problem for the good part of a year (since I built the workstation). The last thing I've tried is your suggestion above, which I thought had finally fixed the problem, but then came back after 2 full days of stability. Don't know what else to try.

Please start new Topic
This topic is a bit on the old side.
>>Please read and comply with the Forum Rules.<<