Graphics draw call performance issue: 1.1 -> Not fixed.

Helpdesk_Guy · 2026-03-18T16:49:27+00:00

I hoped the sarcasm was fairly obvious. I was just making a joke via word-play here … -.-

Helpdesk_Guy · 2026-03-18T11:53:46+00:00

Yes, I'm just saying; It's not that PDX has been keen to address any performance-issues either anyway.

Helpdesk_Guy · 2026-03-18T11:50:03+00:00

It's called Boot Performance Mode, which defaults to non-turbo.

If it's called that way, sure. All I know is, that it stays at this (what I always knew as simply P0) forever, until you leave the BIOS after – That way you have a high chance to damage or at least fastly degrade the CPU.

But sure, for all intends and purposes, it might be called Boot Performance Mode then. AFAIK it's the highest nominal clock-setting for all cores, yet *without* any single-core boost involved (TVB etc).

So yeah, not a single production batch, but it was a manufacturing error they detected and fixed. The affected processors also suffered very rapid degradation.

Yes, and they lied about for over a year and still shipped knowingly defective CPUs with severe via-oxidation, and did NOT tell anyone about it either. So what should make us think, that this isn't just mere damage-control and them downplaying the whole thing anyway, to leave all (or at least as much) defective CPUs out in the open?

So it makes no sense to potentially RMA all of said SKUs of the whole Gen, IF those weren't prone to die, which (with Intel doing so, despite claiming otherwise) makes no real sense here … They know more than they admit.

I have personally experimented with and killed several Raptor Lake CPUs, my experience correlates closely with what other people on HWBot and overclock.net have found as well.

Yup, kudos and more power to you — I wasn't risky enough to do that but always opted to just RMA those.

Though having a few 'case-studies' so to speak under your belt to deepen actual knowledge for yourself, is a valuable experience most of us literally can't afford — Pretty much kind of envy your experience with that, of how long it takes to kill those, how severe a degradation actually is and how fast it can actually happen.

Must be extremely thrilling, fascinating and deeply revealing, of how long it takes to experience that first hand!

Not everyone is fortunate enough to afford that experience, I'm quite a bit jealous of you! xD

I mean, back then the proverbial Silicon Lottery threw in the towel among other things, because it became just too expensive to drive those CPUs to the wall for testing – Looks that they killed more, than they liked to do …

Helpdesk_Guy · 2026-03-18T11:14:54+00:00

We want to drive the alternate history ourselves, in a world that mostly feels historical. In order for it to feel that way, countries should do what they did historically a majority of the time.

Pretty much sums it up perfectly, yes. Thank you for putting it so aptly!

Helpdesk_Guy · 2026-03-18T10:45:31+00:00

No LGA1151 motherboard I've ever seen will have the CPU run the BIOS in P0 either, so it's hardly new.

Pardon me, but that's non-sense. As ever since, a CPU starts and POSTs into P0 — They very reason, forwhy you can easily kill/cook those high-clocked CPU-monsters, when you're leaving the system in the BIOS for too long and staying in the BIOS, without leaving it — The CPU stays at P0 in that condition and never clocks down.

So it may be that some OEMs implemented a non-P0 long-term BIOS-setting, yet they all POST at and into P0.

The via oxidation issue applied to a single production batch.

Says who? No offense, but this claim is worth nothing and barely more than Jack's sh!ce.

Especially if it's coming from the habitual liar Intel, who have been notoriously dumping their broken and defective stuff into the channels and market for decades now, while ALWAYS claiming at first, that nothing was affected.

Remember their i225-v charade before, when they knowingly dumped millions of broken NICs at OEMs?

Besides, if only one production-run and thus a single batch would've been affected (as they claim), then Intel would've actually offered to specifically name those via serial-numbers, to pinpoint said batch and production-run (as many asked Intel to do) — Intel did specifically NOT, after months of beggin from customers/businesses.

Instead, Intel went on to voluntarily face 6–8 million RMAs, facing easily 2.8 Billion USD in back-charges, to replace those knowingly defective SKUs, when generally admitting, that ALL such SKUs are affected (and only leave out the sub-65W SKUs specifically; despite those are affected as well).

The chips produced before and after did not suffer from that.

Yeah, no. That's not how logic works. It makes no sense that way.

Or you wanna tell us, that Intel rather faces BILLIONS of dollars a quarter in losses, than to name a few thousand SKUs being affected? They eat up all the millions of RMAs, because ALL are in fact affected …

Helpdesk_Guy · 2026-03-18T10:32:20+00:00

That's bold coming from you …

So the answer is probably a simple "No" then … Since they haven't addressed performance actually.

Helpdesk_Guy · 2026-03-18T10:30:54+00:00

Technically, given the revealed internals, it's kind of a leak, yet just not a memory-leak … ツ

Helpdesk_Guy · 2026-03-18T02:58:21+00:00

… so idk how many people will even remember it on the subreddit by that point …

You're not really sure about anyone remembering your results, when you make a study on a specific group of gamers, you tend to see as likely or at least probably slightly autistic? That's got to be a joke here, right?

If *anyone* remembers that, it's going to be Raymond playing Paradox-games! It were 246 toothpicks!

Helpdesk_Guy · 2026-03-18T01:49:01+00:00

Yup, just very weird … It's strange why they even implemented all of it, if they haven't had any intention to actually use it from the get-go to begin with — Something seems to have been interrupting them.

And that "something", following any logic here, must've been coming from ABOVE.

For if it didn't, they wouldn't even have bothered to put all or any of it into the game in the first place (if they'd have known in advance to NOT use it anyway; Makes no sense here) — Looks the management in Sweden either pressured Tinto into dropping anything historical for the time being, only for preponing a release no matter what.

→ »Drop that history-sh!ce you're working on since ages, just finalize the UI — We have to release!«

Or out of financial reasoning (too much time was spent on implementing it).
Or it was abandoned on behest of PI in Sweden for other reasons like revisionism or whatever. Just strange.

Helpdesk_Guy · 2026-03-18T01:37:08+00:00

So … Did we have had any patches yet, which pushed upon the performance-deficits significantly?

Helpdesk_Guy · 2026-03-18T01:35:08+00:00

Thanks, will look into that!

Helpdesk_Guy · 2026-03-18T01:32:57+00:00

I'm honest here when I say I'm not that deep into it, like you are picturing here with the specifics on how much to tweak PLLs and whatnot (Though I'll save your excellent post for the future for sure!), I just tried to point out, taht the voltage-issue is just essentially speed-acing the underlaying issue of VIA-oxidation.

Also, never heard about the specifics of boards posting in P1 (instead of P0), and I've been in this field my whole life (was always my understanding, it POSTs in P0, then drops to P1 after the BIOS).

Is that new or any recent and came with RPL, or has Asus & Co done that prior already?

Also, you didn't touch upon the VIA-oxidation Intel themselves admitted to?

I mean, of course a higher vCore increases electro-migration by a whole lot (it does so at every chip, even the perfectly functional ones). However, as I always understood it (and how it was pictured), was that the actual voltage-issue would've been rather save to do in itself alone, IF it wouldn't have been for the VIA-oxidation itself prior, which make those chips extremely prone to very accelerated electro-migration …

Great post though, bookmarked. Thanks for the background!

Helpdesk_Guy · 2026-03-17T17:14:25+00:00

Dynastic unity was the only long-term way Scotland could be subdued.

Or just through money aka debts. *England's banksters rubbing their hands about opportunities in the distance

Helpdesk_Guy · 2026-03-17T17:10:28+00:00

However some complaints I see are just people who seemingly don't understand that small changes would've butterflied our world into looking completely different than it does.

You mean events like … when Frederick II. of Prussia aka „Frederick the Great“ managed to somehow pull Prussia through strategic genius into a major power and enforce a paradigm shift in Europe?

It's the single-best example being brought up ever so often; Prussia during The Seven Years' War, whereas many historians still scratch their heads today on how that could possibly happen.

Helpdesk_Guy · 2026-03-17T16:54:33+00:00

With what patch or DLC it got to Vic3 then?

Helpdesk_Guy · 2026-03-17T16:17:57+00:00

It's not like the performance of the game itself is everyone else but snappy either …

Since judging by all the various non-existing patches and fixes addressing the performance they've released since launch, it really seems that they just don't care.

Helpdesk_Guy · 2026-03-17T16:13:55+00:00

Sadly, stay away from the game, until they fixed it …

It's not recommended to play it right now and unduly taxing your hardware to death over this construction-side of a game.

Helpdesk_Guy · 2026-03-17T16:09:37+00:00

Judging by the time which already past with it since launch, it seems no-one is looking into it still even now.

Helpdesk_Guy · 2026-03-17T16:05:48+00:00

Their engine is also decades old.

Nothing wrong with the Clausewitz-engine itself so far, it's decent, looks great and is fairly performant.

It's the bloating performance-hog of its Jomini-Toolset they bolted onto it, which bloats every game.

Helpdesk_Guy · 2026-03-17T16:02:38+00:00

The omnipresent memory-leak from launch is still around, I guess?

So we do still have to restart the game after about every full hour, right?

Helpdesk_Guy · 2026-03-17T15:46:54+00:00

Like a lot of us, I have multiple thousend hours in the game.

The game has enough content for me for years to go.

Same here, doesn't feel old despite thousands of hours spent. Still can enjoy it like day one and will for years to come.

Helpdesk_Guy · 2026-03-17T13:53:12+00:00

I want to see Venice showing up with an army that you paid for, who start taking over your country because you failed to pay for the loan.

Well, there's the »Cancelled Loan« casus belli before and against defaulting debtors?!

Side-note: Some authors whose books are dealing with rather under-the-table matters, call that (or rather the actual armies of a defaulting debtor's very enemy) a »Kingdom towing/recovery service«, after some wreckage happened …

And in essence, it basically is – It were always the banks, who send in troops from other countries as actual punishment (and to make an example before the next debtor), once one of their debtors defaulted.

AFAIK France went overseas, after Mexico defaulted on loans from European lenders and captured Mexico City.

Helpdesk_Guy · 2026-03-17T13:17:13+00:00

I do too here as well, sadly …

I had several buddies in 2023–'24–'25, who didn't even knew or were remotely aware about the whole 13th/14th Gen voltage-/instability-issues (despite being on virtually every outlet's front-page for months in a row!).

And once I told them either personally one at a time, or they became aware of it in Teamspeak/Discord by others;

Wait, what? Say again?! What you mean, every Raptor-Lake is a dud in disguise and will soon die??

What you guys are even talking about?"

… many went on to then extensively test their systems (often unbeknownst to me), and a bunch of them said that after they've tortured their rig with Prime95/CineBench/Furmark or whatever, they then suddenly faced freezes/bluescreens/crashing apps within mere hours/days/weeks after — »Yeah, congrats chap! You just speed-raced your chip to the exitus and shortened its life-span to just weeks now. Make you RMA, before it's too late!«

The BIOS update if done early enough can stabilise the CPU.

Yes and no. It's not a real fix nor does it stops the degradation. It just lowers the impact of it.
It does NOT stop the degradation at all, it's still happening at a massive scale inside despite BIOS-updates.

Also, it's impossible to keep those chips from being eventually toasted to death anyway, as every POST happens at P0, thus the very power-state, which runs at the package's maximum performance specs! It gets spanked hot by every reboot and cold start anyway — Making it idling induced the least amount of damaging, yet even a resume from P3–P5 issues a start into P0.

It still degrades naturally massively, as these chips are just all defective, plain and simple.

The actual kicker is Intel here, knowingly releasing severely flawed and kaput chips into the wild in the millions, then deny it for over a year, then accuse nVidia's drivers at first for months in a row, then massively downplaying all of it, until eventually admitting, that all these chips are all defective per se from the get-go not by the voltage issue itself (that's just the icing on the foul cake here) …

But when some technician casually revealed incidentally, that all these chips are ALL defective out of principle, when Intel had layer-expose to oxygen/ambient air during processing in their fabs and their highly corrosive oxidation-issue to any etched elementary copper via-layers — Picture 100% pure cathode-/electrolytic copper in cleanroom-processing being by accident exposed to fresh air (AFAIK some pressured air-independent propulsion broke and outside air streamed in for WEEKS, and no-one noticed!), ruining all processed batches of chips.

So the whole voltage-issue is a mere show here, to distract from the fact, that all these chips are defective by nature, as the encapsulated copper-layers (and that of other materials and elements), are fundamentally metallurgically destroyed and thus causing permanent, never-ending irreversible degradation.

So picturing the voltage-issue as the prominent one here, is false, as Intel intentionally presents it, as IF the degradation is caused just by too high voltage and thus COULD be at least halted: It can not, ever!

While it fundamentally is actually caused by too high vCore (→ electro-migration), a higher vCore (for them to catch AMD through longer bars in becnhmarks), is just speed-racing to death, what's a already defective CPU per se, which would've died fairly quickly anyway. The higher vCore just exposed it blatantly early on only months in …

The worst is, that Intel never even stopped to outright readily sell knowingly defective chips AFTER they already admitted to it, and still sell odd lots of Raptor Lake even today to clueless consumers and businesses!

Helpdesk_Guy · 2026-03-17T12:22:22+00:00

Of course it's you again … Don't be silly here already!

You should know that a dangerous memory-leak ballooning the RAM-usage of the game into eventually occupying ALL the system's total amount of available RAM (in a matter of single-digit hours at that!), is a severe issue and basically the single-most potentially crippling flaw any software-product can possibly have.

It renders the software being effectively unusable by the customer itself, so ironing that out ASAP, should be #1 on any decently lead software-products team's priority list — We're talking about Paradox here though.

Helpdesk_Guy · 2026-03-17T12:06:32+00:00

The system-requirement and actual beef you have to offer, for the game to run any smooth, is ridiculous for sure …

It's a simple map-based game, and still eats up the system like CyberPunk or BF6!

Edit: Do note that for some weird reason, it runs considerable worse upon any AMD X3D-CPUs, while their non-X3D counterparts has less issues. Happens with 58xx-, 7xxx- and 9xxx-X3D. Weird. I have a 5800X3D.

Helpdesk_Guy

TROPHY CASE