News Despite Intel patch, Black Myth: Wukong devs warn about Core 13th and 14th Gen CPU crashing — studio provides a few workarounds to avoid crashing i...

[Geekaycee]

Intel patch? What patch? Those beta bioses from mobo manufacturers are no patch, nope.

 

[stuff and nonesense]

third attempt, the Asus mobos have very similar names).

I empathise, Gigabyte are as bad… Aorus Elite AX V2.

 

[watzupken]

The warnings in this game is reasonable. The problem is not many people who owns a Raptor Lake based computer knows about flashing BIOs and updating microcode. So most of them will likely still run into this problem. The enthusiast community is very small as compared to the non tech savvy folks.

In any case, I still don't think Intel actually fixed the issue. This is not some 1 month old issue, but has been going on since the 13th gen Intel processors. If the fix was so straightforward, I wonder what took them so long to get to the bottom of it.

 

[Gururu]

The warnings in this game is reasonable. The problem is not many people who owns a Raptor Lake based computer knows about flashing BIOs and updating microcode. So most of them will likely still run into this problem. The enthusiast community is very small as compared to the non tech savvy folks.

In any case, I still don't think Intel actually fixed the issue. This is not some 1 month old issue, but has been going on since the 13th gen Intel processors. If the fix was so straightforward, I wonder what took them so long to get to the bottom of it.

Totally, the game will reach far more people than those aware of the bios. Also agree about the fix. The first thing they would have asked themselves, once they knew it was electron migration, is "How do we limit the voltage?". I guess it is plausible that they needed a solid scientific determination on the loss of conductor in the chip. That could take months.

 

[stuff and nonesense]

Nobody knows, maybe not even intel knows about that in the meantime, but it is reasonable to assume after almost 2 years since 13th gen release, and 99.99% of users won't even touch bios, not to say aggressive undervolting and hard cap the max voltage in day 1 (which need intensive stability tests to begin with), that a ton of degraded CPUs are out there, not showing signs of the CPU failing in daily use, only to start failing left and right in the UE5 engine, when the devs saw a considerable amount of stability complains with the RPL processors they would put out such notes to warn players about the issue and not flooding their CS hotline/email

I saw another article, it clarified the warning as for units still running on the old firmware. Hopefully all motherboards for 13/14 gen will be updated soon.

 

[Gururu]

Just cranked out 11 FPS average on two bench runs. I guess that means my CPU has tiger blood!

 

[YSCCC]

I saw another article, it clarified the warning as for units still running on the old firmware. Hopefully all motherboards for 13/14 gen will be updated soon.

But TBH, the crashing is the result of already degraded CPU, so updating firmware won't stop it from crashing, only (might) stop those not yet degraded from degrading, it kinda looks more like a RMA reminder to me

 

[stuff and nonesense]

But TBH, the crashing is the result of already degraded CPU, so updating firmware won't stop it from crashing, only (might) stop those not yet degraded from degrading, it kinda looks more like a RMA reminder to me

It might be, but I can’t say that.

The question I asked was whether the warning was to do with the update being installed or not. The report I saw said it was. Before seeing the subsequent I was wondering if the developer had seen repeated crashing after the the update. There is no evidence for that today. We will see in 6 months time..

Degraded CPU is, while connected, a different issue. Look at buildzoid and his experiments with CB15. The pre update config would reliably crash with default settings and a CPU that wasn’t broken (yet).

 

[YSCCC]

It might be, but I can’t say that.

The question I asked was whether the warning was to do with the update being installed or not. The report I saw said it was. Before seeing the subsequent I was wondering if the developer had seen repeated crashing after the the update. There is no evidence for that today. We will see in 6 months time..

Degraded CPU is, while connected, a different issue. Look at buildzoid and his experiments with CB15. The pre update config would reliably crash with default settings and a CPU that wasn’t broken (yet).

It could be both way, but TBH, with the problematic microcodes and the unlimited profiles out there for so long if I am the dev I will be also warning about the issues, one can't expect more than 0.1% of their customer are buildzoid and when intel is dominating the market it will be very sensible to warn about it regardless.

I didn't recall the whole buildzoid video as it's usually very boring and records everything, but from what I can recall it was related to vdroop and excessive voltage spikes, this should be fixed by now but who knows how many OEM PCs have issues and have no idea of how to update