Driver check plan: PC 2's crash named from its event log (bugcheck 0x3B during the silent Intel install over a mining eGPU; the app off until the next logon)

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/plans/driver-check.md

@@ -43,7 +43,7 @@ Sizes: the installers are 889 MB to 1.0 GB each; the download lands in `<app dat
 
 ## 3b. A card in an external enclosure (7 October 2026, after PC 2)
 
-PC 2 at 16:26Z: the Intel installer started with the app's own worker mining on the Arc B580 in the Razer Core X V2. The installer's display reset took the machine down at 16:27:14Z (every log stops together; a power cycle). The rule, on this branch:
+PC 2 at 16:26Z: the Intel installer started with the app's own worker mining on the Arc B580 in the Razer Core X V2. Seventy seconds later the kernel crashed (System log 1001: bugcheck 0x3B SYSTEM_SERVICE_EXCEPTION, minidump 100726-22234-01.dmp; Kernel-Power 41), the machine came back at 16:27:56Z and the per-user app waited for a logon until 17:34:46Z; 9034 was never staged (pnputil: oem41.inf 6733 only). The rule, on this branch:
 
 - A driver install on a card the app reads as `external` (the eGPU kind: a USB4 or Thunderbolt router in the device's parent chain, update-return-21b) stops that card's worker before the installer starts (`drivertable::install_hold_keys`, through the cards path with the restore choice kept, the `--cards-off` shape). The vendor's cards inside the case and every other vendor's card keep mining.
 - The row says so before the click ("This card's worker stops for the install and comes back after it; the other cards keep mining. The display reset can take the machine for a minute and may need a restart: save your work first.") and while it runs ("This card's worker is stopped until the installer ends; the display reset can take the machine for a minute.").