Constant crashes

Thanks for your reply, I have run full hardware diagnostics multiple times over many weeks, across every single piece of hardware. All drivers have been updated. All 24 cores tested individually with intel test software. GPU BIOS updated, I mean everything has been patched to the latest level. I've turned off hardware acceleration, disabled all extensions, and all 3rd party injections. Have rebuilt the machine from scratch 4 times with Windows. Have spoken to the vendor whom supplied with all the latest drivers etc. Have been through mini dumps and remediated appropriately.

The machine is still under warranty, and yes, am aware of the CPU bug requesting 'bad' voltages.

I am at a total loss. Interesting that it's at random points with no correlation. I am in a different country to where I purchased the laptop, and have been holding off sending it back due to logistical issues. But I think that is my only recourse at this stage.

Thank you for your words of advice.

Regards

Adrian

I wish I could help more, it seems you've researched the particular Raptor Lake variant issues extensively so you definitely have more context than me at this point — unfortunately once you pass a certain point of degradation in the silicon there's no SW/FW remediation and the registers will just yield randomly buggy results.

There are some very typical and consistent crashes due to it: bugzil.la/cpu-raptor-lake-bugs which is the most common patterns — but having every single one at a unique place makes the whole issue even less actionable:[

I'll walk you through one of the (completely distinct each) crashes you provided above, and put it into bigger perspective to give you the idea. Looking at the same signature across all of Firefox users: https://crash-stats.mozilla.org/signature/?product=Firefox&signature=js%3A%3Ajit%3A%3AICScript%3A%3AisInlined&date=%3E%3D2026-01-19T11%3A18%3A00.000Z&date=%3C2026-06-20T11%3A18%3A00.000Z for the past six months. Which itself shows this is not in thousands or tens of thousands, it's a good representation of an absolutely random crash in a random spot coming in at just around two hundred crashes in 2026H1. If you click "Aggregations" tab, and in the combo "Aggregate on…" select/type "cpu info" it will add a table (far bottom right for me) that besides the single occurrences long tail has an apparent common cause: CPU "family 6 model 183 stepping 1" in 158 (71.49 %) cases — which is if you decode the CPU details on your system most likely something as "Raptor Lake, Model: 6, Ext. Model: B7"

While none of this helps to stabilize the issue for your workflow, it's a good paper trail for you to get the faulty chip replaced in case everything else appears to work just fine — it's not the most practical resolution, but at least if it helps to draw attention to a flaw you're already having fully exhibiting, it might help prevent later issues down the road if caught now early enough.