Dell Pro Max 16/18 Plus (2025 model) pre-release discussion — MB16250, MB18250

[yslalan]

https://github.com/LevinAi-arch/rtx-5070ti-laptop-160w-power-limit/releases/tag/v1.8.0

Interesting repo. Just modified a few lines of code to make it work with the RTX PRO. 

 

[SuperMG]

1 hour ago, yslalan said:

https://github.com/LevinAi-arch/rtx-5070ti-laptop-160w-power-limit/releases/tag/v1.8.0

Interesting repo. Just modified a few lines of code to make it work with the RTX PRO. 

 

Hello. Can this work for RTX Ada Lovelace mobile cards? 

 

Because I found this: https://github.com/timmyy123/nvidia-power-control

[yslalan]

Ada and Blackwell should both work. You may just need to add logic to detect the device name properly.

 

27 minutes ago, SuperMG said:

Hello. Can this work for RTX Ada Lovelace mobile cards? 

 

Because I found this: https://github.com/timmyy123/nvidia-power-control

 

[SuperMG]

20 minutes ago, yslalan said:

Ada and Blackwell should both work. You may just need to add logic to detect the device name properly.

 

 

No way my 4090 150W MXM card can do 175W+ easily on my Clevo? But I would get limited by the power resistors (R006)...

 

And power limiting could work too... Back then we used the bugged Nvidia drivers to power limit our mobile GPUs.

[delboi]

I’m investigating this further with the recurrent WHEA-Logger Event 17 / PCIe AER events on a Dell Pro Max 16 Plus MB16250 with Core Ultra 9 285HX. They occur during early Windows boot across multiple unrelated PCIe endpoints: Intel BE200 Wi-Fi, NVMe SSD and NVIDIA GPU.

Raw WHEA/CPER records show the same AER signature:
UncorrectableErrorStatus = 0x100000 = Unsupported Request
CorrectableErrorStatus = 0xa000 = Advisory Non-Fatal + Header Log Overflow

Captured TLP headers decode as PCIe Configuration Read Type 0 requests, apparently probing absent functions/BDFs during early PCI enumeration. Some requests occur only microseconds apart.

Linux PCI enumeration source:
https://github.com/torvalds/linux/blob/master/drivers/pci/probe.c

Linux PCIe AER documentation:
https://www.kernel.org/doc/html/latest/PCI/pcieaer-howto.html

Intel Arrow Lake Series 2 specification update / errata:
https://edc.intel.com/content/www/us/en/design/products/platforms/details/arrow-lake-s/core-ultra-200s-series-processors-specification-update/errata-details/

Relevant Intel erratum: ARL068 — PCIe Gen5 Link Exit from L1 Sub-state Low Power State. It specifically mentions short back-to-back PCIe configuration-space accesses as one trigger condition.

Dell also has an official article stating that boot-time WHEA-Logger ID17 is “expected behavior as per Intel” on certain earlier Intel HX systems. Note that Dell’s listed affected systems are 12th-gen/HX platforms, not the MB16250/285HX, so it does not by itself prove this newer system is expected to behave the same way:
https://www.dell.com/support/kbdoc/en-uk/000216115/laptops-with-12th-gen-and-12th-gen-hx-intel-core-processors-may-display-warning-message-whea-loggerid17

WHEA-17 itself is quite generic, and I think the associated symptoms may be more significant than the event alone. In my case, I’ve seen intermittent freezing and occasional mouse slowdowns. Dell support has also told me that some users experience BSODs or system crashes. What I’m really looking for here is other people’s ideas, observations and possible avenues to investigate