BD PROCHOT Issues

[VortexSupernova]

Fellas,

Also, note my laptop is the Acer Nitro 5 AN515-57-(919C, if anyone wants the end code), and I got it in September 2022.

First issue: I've noticed that BD PROCHOT isn't the most reliable system. I've got it disabled for gaming power plan because it violently throttles my CPU whenever the temperatures are roughly around 60-65, although it triggers and continues even after it drops below 60. Since then, I've disabled it because the amount of throttling it does is ridiculous.

Second issue: whenever I'm on battery, I get EDP other in all 3 columns. Yes I know, battery blah blah. But when I plug my laptop in, Core and GPU (and sometimes Ring) all get BD PROCHOT going yellow in them. It happens consistently every time. Core and GPU always get BD PROCHOT when I plug in (my AC power plan has BD PROCHOT enabled, my gaming plan is a different plan). Why is this? Why does it set off when plugging in? It doesn't matter about the % battery, it always goes yellow. After I've plugged in, I clear it, and it doesn't show again.

 

[unclewebb]

Some laptops use BD PROCHOT throttling when changing between AC and battery power. The purpose is to protect the battery. Some laptops might forget to turn this off. It really is a horrible throttling method.

I cannot help you with EDP issues without seeing some screenshots of the TPL and FIVR windows. Lowering one of the current limits is another method used by manufacturers to protect the battery.

 

[quillo]

Bit late to the party but came to comment that BD_PROCHOT issues seem to be prevalent on this chassis. I've also found with it disabled in TS that eventually the system hits thermal cutoff and just hard stops. I've done a bunch of testing around this and I don't think the issue relates to CPU or GPU temperature (at least, not directly). The BD_PROCHOT is being triggered before either of those sensors are particularly high, and BD implies that the event is being triggered by a device other than the CPU.

I have made some other minor changes to the system, such as applying new thermal compound, unlocking the BIOS to allow more frequency control, undervolting, etc. I found that there were multiple memory chips that appeared to be intended to make contact with the heatsink (via a THICK blob of thermal paste) but were not. I've also found that running heavy workloads with the screen open seems to help somewhat.

Ultimately the best "fix" I have found is to create TS profiles to throttle a bit earlier. I suspect that once the heatsink is soaked its just not dissipating heat fast enough from some component that doesn't expose a temperature sensor to the OS. More specifically; I suspect one of the memory chips, as after a hard thermal cutoff the system behaviour is a bit weird (random bluescreens, hangs) that are reminiscent of bad RAM until it has cooled down a bit.

 

[VortexSupernova]

Bit late to the party but came to comment that BD_PROCHOT issues seem to be prevalent on this chassis. I've also found with it disabled in TS that eventually the system hits thermal cutoff and just hard stops. I've done a bunch of testing around this and I don't think the issue relates to CPU or GPU temperature (at least, not directly). The BD_PROCHOT is being triggered before either of those sensors are particularly high, and BD implies that the event is being triggered by a device other than the CPU.

I have made some other minor changes to the system, such as applying new thermal compound, unlocking the BIOS to allow more frequency control, undervolting, etc. I found that there were multiple memory chips that appeared to be intended to make contact with the heatsink (via a THICK blob of thermal paste) but were not. I've also found that running heavy workloads with the screen open seems to help somewhat.

Ultimately the best "fix" I have found is to create TS profiles to throttle a bit earlier. I suspect that once the heatsink is soaked its just not dissipating heat fast enough from some component that doesn't expose a temperature sensor to the OS. More specifically; I suspect one of the memory chips, as after a hard thermal cutoff the system behaviour is a bit weird (random bluescreens, hangs) that are reminiscent of bad RAM until it has cooled down a bit.

I'm completely fine leaving BD_PROCHOT off, yeah? No harm done? I'll be repasting in a couple months with PTM 7950 and k5 pro or u6 upsiren on the VRAM and stuff (All I have to do is replace the pink shit with it, as I've been told). BD PROCHOT is never really an issue until the CPU starts violently throttling, it's just annoying to have to keep clearing my warnings whenever plugging in.