
UNSOLVED
[SOLVED] BSOD 0x1E ~5 min after every boot on Inspiron One 2330 (2012) — 2026 Secure Boot certificate rollout task; fix inside
TL;DR: If an old machine (2012-era, last BIOS from ~2018) started blue-screening or freezing a few minutes after every normal boot since mid-2026, but is perfectly stable in Safe Mode, check the scheduled task \Microsoft\Windows\PI\Secure-Boot-Update. Microsoft's 2026 Secure Boot certificate rollout makes it call UEFI SetVariable() minutes after each boot, and some old firmwares crash hard on that write. Disabling the task stopped a 13-BSOD streak instantly.
The machine: Dell Inspiron One 2330 AIO (2012), BIOS A16 (2018, the last one Dell ever released for it), Windows 10 Home 22H2 fully patched (consumer ESU).
Symptom: Bugcheck 0x1E (KMODE_EXCEPTION_NOT_HANDLED) with parameters (0xffffffffc0000005, <RIP>, 1, 0x100) — i.e. an access-violation write to address 0x100 — roughly 5 minutes after every normal boot, with nobody logged in. Instruction pointer always at the same offset (ends in ...3d14) across 13 crashes. Safe Mode: 100% stable, indefinitely. That pattern (timer-like crash, stable in safe mode) screams "something scheduled runs a few minutes after boot".
Root cause: the Windows Update-delivered 2026 Secure Boot certificate rollout (the 2011 KEK/DB certs expire June 2026). It's applied by the scheduled task \Microsoft\Windows\PI\Secure-Boot-Update, which fires minutes after boot and calls UEFI SetVariable() to install the new certificates. This firmware (and apparently other old Dells — see the Inspiron 3542 report mentioned below) crashes in kernel mode when the write happens. The task re-arms and retries every boot, so you get a permanent crash loop. There is no firmware fix: Dell stopped releasing BIOS updates for this model in 2018.
Things that did NOT work (so you don't waste days like I did):
AvailableUpdates=0inHKLM\SYSTEM\CurrentControlSet\Control\SecureBootwas already 0 — the 2026 rollout path uses theSERVICINGsubkey instead (UEFICA2023Status=NotStarted+Refire*values) and the task retries regardless.- Setting the opt-out (
...\SecureBoot\MicrosoftUpdateManagedOptIn=0) did not stop the retries. - Deleting the task via its TaskCache registry keys fails with Access Denied (SYSTEM-only ACL).
- Driver bisection (we suspected a banking-security kernel driver first) — red herring; the dump eventually proved the crash context.
The fix (normal boot, admin prompt):
schtasks /Change /TN "\Microsoft\Windows\PI\Secure-Boot-Update" /DISABLE
Caveat 1: the Task Scheduler service doesn't run in Safe Mode, so this must be done in a normal boot — you have ~5 minutes before the task fires. (I scripted it to run right after boot.)
Caveat 2: cumulative updates can re-enable or recreate this task. After the October 2026 CU I verified it — check it after every CU and re-disable if needed.
Caveat 3 (trade-off, be honest with yourself): disabling the task means this machine never gets the 2026 certificates. On firmware that bluescreens on the attempt there's nothing to lose — the alternative is an unusable machine — but know that at some point future boot components signed only with the new certs may not validate. For a 2012 machine on ESU, that's acceptable.
Result: 13 BSODs over two weeks → zero since the task was disabled, through multiple reboots and an October CU install.
Related reports: Reddit thread on an Inspiron 3542 freezing (not BSODing) from the same task after the June 2026 CU; Microsoft's official "Secure Boot troubleshooting guide" (March 2026) and "Secure Boot playbook for certificates expiring in 2026" (Tech Community) — both acknowledge firmware-dependent failures but the consumer-facing symptom (crash loop minutes after boot on old hardware) is barely documented anywhere.
Responses (0)
Solutions (0)
