WakeX
Active member
- Joined
- Jun 16, 2023
- Messages
- 133
Nope, only exact same as the last beta:
- AGESA ComboPI 1.0.0.7a updated with the required solution.
So far after punching in all my settings again, I've noticed the following two new entries in the BIOS:
Under OC there is a setting below Memory Context Restore called Memory Failure Retry Count which defaults to 1, nice to have for memory settings which only sometimes fail to train I guess.
Under ACPI Settings there is a new entry called CPU Fan Fail Warning Control which defaults to Disabled, which is also a good addition.
Not sure why it's set to disabled as default though, shouldn't the opposite the case and only need disabled if you're not running a fan/pump but some other external solution like LN2 or a chiller maybe?
The time spent on post code 15 (memory training) was also cut down massively on my settings (MCR auto, PD off) to around 32 seconds - Last BIOS time reported by task manager was way over 100 seconds easily on the prior beta BIOS, now it's consistently below 50 seconds. I wonder if I force MCR to enabled if it would affect anything and be even faster (or if I'd get BSODs like some reported with PD off), gonna try later.
Unfortunately the PCIe 1.1-bug still is present and showed up quite fast on the third and fourth reboot in a row, while on the fifth everything was fine again:
Once it runs at 4.0 I don't notice any instability, crashes or the like - so I'm not sure why that happens, if the signaling was bad wouldn't it have issues at 4.0?
I've got a Crucial T700 5.0 4TB on the way, maybe even this week already which will replace the slow WD Blue SN550 3.0 250GB (which will go into an external case) in the slot closest to the CPU - wonder if changing that will impact this pesky PCIe 1.1-issue, if at all.
Oh yeah, almost forgot:
Trying to get into M-Flash to update the screen froze and I was greeted with a 00 on the post code.
I pressed the power button on the case first to try getting a shutdown but that just restarted the system and then it went into M-Flash - after which I flashed the new BIOS without a hitch (should've probably rebooted cleanly and try again but yeah...).
Odd behavior to say the least.
- AGESA ComboPI 1.0.0.7a updated with the required solution.
So far after punching in all my settings again, I've noticed the following two new entries in the BIOS:
Under OC there is a setting below Memory Context Restore called Memory Failure Retry Count which defaults to 1, nice to have for memory settings which only sometimes fail to train I guess.
Under ACPI Settings there is a new entry called CPU Fan Fail Warning Control which defaults to Disabled, which is also a good addition.
Not sure why it's set to disabled as default though, shouldn't the opposite the case and only need disabled if you're not running a fan/pump but some other external solution like LN2 or a chiller maybe?
The time spent on post code 15 (memory training) was also cut down massively on my settings (MCR auto, PD off) to around 32 seconds - Last BIOS time reported by task manager was way over 100 seconds easily on the prior beta BIOS, now it's consistently below 50 seconds. I wonder if I force MCR to enabled if it would affect anything and be even faster (or if I'd get BSODs like some reported with PD off), gonna try later.
Unfortunately the PCIe 1.1-bug still is present and showed up quite fast on the third and fourth reboot in a row, while on the fifth everything was fine again:
Once it runs at 4.0 I don't notice any instability, crashes or the like - so I'm not sure why that happens, if the signaling was bad wouldn't it have issues at 4.0?
I've got a Crucial T700 5.0 4TB on the way, maybe even this week already which will replace the slow WD Blue SN550 3.0 250GB (which will go into an external case) in the slot closest to the CPU - wonder if changing that will impact this pesky PCIe 1.1-issue, if at all.
Oh yeah, almost forgot:
Trying to get into M-Flash to update the screen froze and I was greeted with a 00 on the post code.
I pressed the power button on the case first to try getting a shutdown but that just restarted the system and then it went into M-Flash - after which I flashed the new BIOS without a hitch (should've probably rebooted cleanly and try again but yeah...).
Odd behavior to say the least.
Last edited:
! This fix would be delivered as a new BIOS in MSI Center? The new BIOS solve the VSoC voltage issue (<1.3v)
.