Cyberwise Crashes

Cyberwise: crashes, hangs and bisecting

Verified: Cyberpunk 2077 patch 2.31 - August 2026 Re-check after a patch: Confirm log paths and the crash-report filename first; those move between versions.

Check the patch version before hunting for a log - the paths and the crash-report filename move between versions, and a log you cannot find reads as a log that was never written:

(Get-Item "$GameRoot\bin\x64\Cyberpunk2077.exe").VersionInfo.ProductVersion

Load cyberwise alongside this for the method rules. Two matter enormously here:

• Reproduce before bisecting. One crash is not a deterministic fault. Bisect noise and you will "fix" it by coincidence, then be surprised later.
• Confirm the mod is deployed. A crash blamed on a mod that was never actually deployed is a whole evening.

When a crash happens, in this order

The order matters more than any single step, and step 3 is the one that gets skipped.

0. Preserve, before anything else - including thinking.

.	ools\Save-CrashSnapshot.ps1 -GameRoot '<path>'

A relaunch destroys the evidence. redscript_rCURRENT.log is replaced at every launch; CET truncates scripting.log and gamelog.log; CrashInfo.json is overwritten by the next crash. On 2026-08-23 a crash was looked at twenty minutes later and every one of those had already been rewritten - the only survivor was CrashInfo.json, and only because the watcher had copied it.

0b. SAY WHEN THEY CAN LAUNCH AGAIN. The moment the snapshot is written, tell them plainly: "evidence is preserved, you can launch."

They are sitting at a dead game waiting for permission they were never told they needed. Every second you spend analysing before saying it is a second they spend not playing, and they will either wait needlessly or relaunch early and destroy the evidence you were about to read. One sentence, before any analysis.

Say it again whenever a step ends: after a snapshot, after a diff, before you start reasoning. "I have what I need, go ahead" costs nothing and is the difference between a diagnosis that fits around them and one they have to sit through.

0c. If the game is HUNG rather than dead, sample it before killing it. A hung process is still alive and can be interrogated - responding state, thread state counts, CPU delta over a short interval, and which log is still growing. None of that survives the kill, and the engine's own watchdog ends the process after 120 seconds anyway. Two cores pegged with every log silent for minutes is native code spinning, and rules out a script loop outright, because a looping script logs. Also check the RED4ext log for Watchdog timeout! before treating the crash report as evidence of a fault - a watchdog kill is indistinguishable from a fault crash in CrashInfo.json. Wiki: /diagnosis/a-hang-and-a-crash-are-different-faults.

1. Take the bare facts from the crash reporter. Time, district, coordinates, tracked quest, isOom, session length. Facts, not readings. Resist the theory forming while you read them - the first theory becomes the frame everything else gets fitted into, and it is usually wrong.

2. List what is deployed, trusting nothing but the disk. Not the mod manager, not modlist.txt, not a bisect manifest, not what was said earlier in the conversation. Save-CrashSnapshot.ps1 writes deployed.txt for exactly this. See NEVER name a mod you have not confirmed is installed in the front-door skill.

3. ASK THE USER what quest was active and what they were doing.

This is the step that saves the hour. The crash reporter knows the tracked quest, which is often not what the player was doing, and it knows nothing at all about the last thirty seconds - a scene, a menu, a vehicle, a load. On 2026-08-23 the coordinates and quest id were in hand and the search space was still enormous; the user said "corpo-rat intro, near Jenkins' office" and it collapsed immediately.

Ask before analysing, every time. It costs one message. Analysis before asking costs an hour and arrives at a worse question.

4. Only now, analyse and dereference. Cross the deployed list against the quest, the district, the coordinates and what the user described. Check the telemetry for a resource signature - and be willing to find there is none: crashed sessions on one install peaked at 3,090-3,548 handles while healthy ones reached 7,731, which killed the leak theory outright.

Not step 5: a suspect list. A crash with one occurrence and no reproduction does not get a culprit named. It gets a watcher left running and more captures.

Why each of those steps is what it is - the crash report's fields, the dedupe trap, the memory measurement traps - is in the wiki: /diagnosis/the-games-own-crash-report and /diagnosis/memory-is-usually-a-red-herring.

Start by asking what changed - and now you can answer it

.\tools\New-InstallSnapshot.ps1 -Label 'before the DF update'
.\tools\Compare-InstallSnapshot.ps1            # newest vs the one before
.\tools\Compare-InstallSnapshot.ps1 -Since 20260810

"It worked yesterday" is the most common and least usable sentence in mod support, because nothing records yesterday. A snapshot costs about a second and a megabyte and records every archive, the modlist order, every loose script, tweak, Lua and plugin, and the framework versions. Two of them turn "somewhere in 700 mods" into a diff that is usually three lines long.

Watch-Crashes.ps1 takes one automatically at every session start, so the history builds itself. A snapshot taken by hand is a snapshot nobody takes.

Read the diff before proposing a bisect. Bisecting is for when nothing else narrows it - it is not the opening move, and at this game's load times it costs an evening to rediscover something a diff names immediately.

The one it catches that nothing else does: LOAD ORDER ... moved. A mod whose position changed now wins or loses files it did not before, and nothing about it looks different on disk - same file, same size, same timestamp. Verified on a 727-archive install: one entry moved from position 131 to 10 was reported exactly, with no false positives anywhere else.

A diff that finds nothing is also an answer: the install did not change, so look at settings, save state or drivers - or accept it may not be deterministic.

Start by asking what changed

Bisection is for when the suspect set is too big to inspect - it is not a ritual. At every size the first question is what changed, not which half. Under about twenty mods, a binary search is roughly five launches to find something the user could have named in zero.

references/bisecting.md sizes the method to the list, and covers why parking files on disk is unreliable on a managed install - a manager can restore a parked file mid-test, and on MO2 the archives may not physically be there at all.

Snapshot modlist.txt before the first round. A bisect parks archives and rewrites the load order repeatedly, and a run that ends in a crash - or a mod manager that redeploys mid-test - can leave the order in a state nobody can reconstruct. cyberwise/tools/ModFileBackup.ps1 takes the snapshot and restores it; -Restore on the round below only undoes the parking, not an order that something else rewrote underneath it.

NEVER PARK, UNLINK, DISABLE OR REMOVE A MOD WITHOUT ASKING FIRST.

Not as a bisect round, not as a quick test, not "just to check". Name the mod, say what parking it would prove, and wait for a yes. It is their install and their playthrough, and a mod removed underneath them can cost save state, not just time. The tooling makes parking easy, which is exactly why the rule has to be explicit - the cost of asking is one message, and the cost of not asking is somebody's game.

This holds even when the suspect is obvious and the test is one round. An obvious suspect is a good reason to ASK CONFIDENTLY - "this one mod places an object exactly where you crash, may I park it and have you reload?" - not a reason to skip asking.

When you do bisect: arm the round AND launch the game yourself.

tools\Invoke-BisectRound.ps1 -GameRoot '<path>' -Round C -Park cut3.txt -Plan
tools\Invoke-BisectRound.ps1 -GameRoot '<path>' -Round C -Park cut3.txt -Launch
tools\Invoke-BisectRound.ps1 -GameRoot '<path>' -Round C -Restore
tools\Invoke-BisectRound.ps1 -GameRoot '<path>' -Status

The tester has exactly one job that cannot be automated - looking at the screen and saying what happened. Everything either side of that is chores, and handing them back is what makes twenty rounds feel like a punishment. They glance over, the game is up, they try the thing. It launches through the storefront so their own launch options still apply, writes a manifest per round so "which config was that?" is answerable three rounds later, and refuses to park a partial set - a name that resolves to nothing parks nothing, which scores as "the fault went away".

The verdict stays theirs. No watcher can tell a livelock from a loaded game sitting at a menu.

And a failing round narrows nothing. Halve-and-keep-the-failing-half assumes exactly one culprit; with two, every half fails and each round clears innocent and guilty alike. A clean round is the informative one - it proves every cause sits in the set you disabled - so once you get one, invert and add mods back in groups. Name a cause only by adding it back alone to a proven-clean base. Never by elimination. references/bisecting.md, and /diagnosis/a-failing-round-narrows-nothing for why.

When halving has named the mod but not what it is doing, write a guard - a throwaway one-function mod that logs the value separating your hypotheses, in CET rather than redscript. /diagnosis/writing-a-guard-mod.

The game swallows its own crash - so attach a debugger

%LOCALAPPDATA%\CrashDumps on a modded machine will hold dumps for every other application and none for this game. That is not a misconfiguration. The game installs its own unhandled-exception filter: it catches the fault, writes CrashInfo.json, and exits cleanly, so Windows never sees a crash and Windows Error Reporting has nothing to report. Turning on WER LocalDumps does not fix it - the game's handler runs first.

A debugger sees the exception first. That is the whole trick:

winget install --id Microsoft.WinDbg          # once; provides cdb.exe
.\tools\Watch-CrashDump.ps1                   # then start the game

It waits for the game, attaches cdb, and on an access violation records the faulting module, the stack, !analyze -v and a small minidump - then hands the fault straight back with gn, so the game dies exactly as it would have and still writes its own CrashInfo.json. Nothing is prevented; we only read on the way past. FAILURE_BUCKET_ID in the log names the module.

Three things that are easy to get wrong here:

• Do not take a full dump. .dump /ma writes the process's whole private working set, measured at 27-30 GB on one install. A minidump is ~170 KB and !analyze gives the same answer.
• Paths inside cdb's -c "..." string need FORWARD SLASHES. Backslash is an escape there, so a Windows path arrives mangled - the first attempt here wrote C:Users<TAB>ohuw... and failed with Win32 error 123.
• gn, never gh. "Go, not handled" passes the fault back to the game. gh would swallow it and change what the game does, which is lying to the thing you are measuring.

Limits, and say them out loud: it catches access violations only - a fail-fast or an abort will not trip it, and the log saying "no access violation" is itself a finding. Attaching a debugger also changes timing, so a race-shaped crash can move or vanish; that is not the same as fixed.

A missing log is not a silent log

None of REDscript, RED4ext, CET, ArchiveXL or TweakXL ship with the game. An archives-only load order legitimately has none of them, and r6\logs\ may not exist. Absence means "that framework is not installed", not "that framework reported nothing".

references/diagnosis.md says what to do about it; /diagnosis/which-log-carries-which-symptom maps symptom to the log that actually carries it, and covers why a log's last line is not the moment of death.

Memory is usually a red herring

Only open a memory investigation when it is genuinely a suspect - isOom: true, or a crash that only appears deep into long sessions. Startup legitimately ramps GPU memory hard, so a reading taken during it proves nothing.

references/crashes.md gives the order of operations; /diagnosis/memory-is-usually-a-red-herring covers the measurement traps, and /diagnosis/the-games-own-crash-report the crash report the game writes itself and why Windows Error Reporting never fires for it.

Tools

.\tools\Register-CrashWatch.ps1 -Dir "<somewhere writable>" -GameRoot "<game>"
.\tools\Register-CrashWatch.ps1 -Status      # registered? running?
.\tools\Register-CrashWatch.ps1 -Remove

The tray app is optional, and you build it for them

There is a tray icon in app/ that runs the watcher and shows its state. Build it for the user - do not hand them build instructions. It compiles with the C# compiler already present in Windows, so nothing needs installing:

cd app; .\build.ps1 -Run

Say it is optional, because it is. Everything works from the scripts alone. The tray exists so somebody who never opens a terminal can see whether recording is happening, and start or stop it.

Expect questions, and answer them plainly rather than technically:

• "Is it safe?" - it watches memory use and copies the crash report the game writes. It changes nothing in the game or in mods.
• "Will Windows warn me?" - yes, it is not code-signed, so SmartScreen shows "unknown publisher". That is a statement about a certificate nobody bought, not about the file. They can read the source and you just built it in front of them.
• "Does it phone home?" - no. Nothing here contacts the internet except the mod inventory, and only if they supply a Nexus key.
• "Can I remove it?" - close it from the menu, delete the folder. It puts one entry in the startup list, removable from the same menu or Task Manager.

Three things about this that are not obvious:

• The capture is deduped on crashVisitId. CrashInfo.json is overwritten per crash but never deleted, so a watcher that copies it on every exit re-saves the same record after each normal quit. See references/crashes.md - that mistake produced 21 files holding 2 real crashes and a fabricated cluster.
• Register it rather than launching it. A shell-launched watcher dies with the shell, on reboot, and silently on error. Worse, an assistant may be unable to start one at all - a sandboxed tool session can reap the process tree when the call returns, so Start-Process reports success and nothing runs. The task scheduler owns the process instead.
• Verify it is actually running, with -Status. Match the process on its -File argument; a bare script-name substring also matches the query asking the question, which cheerfully reports a watcher that is not there.
• -Status knows all three autostart routes, and has to: the scheduled task, this script's own Run entry, and the tray's Run entry, which starts the watcher itself under a different value name. Seeing only its own two, it reported a perfectly good tray install as not registered while also reporting the watcher as running - which reads as "somebody started this by hand and it is gone after a reboot", the opposite of the truth.
• It also reports whether the running copy can take a snapshot at all. Watch-Crashes.ps1 resolves New-InstallSnapshot.ps1 from $PSScriptRoot, and the installer drops a flat fallback copy in {app} where that sibling does not exist. Run flat, the watcher works and silently records no session-start snapshot, so the one question the snapshots exist to answer - what changed since this last worked - has nothing behind it. snapshot NO in the status output means recording is happening but history is not.
• Starting it twice is safe. The watcher holds a mutex keyed on its output folder and a second launch exits immediately, so the tray, a logon entry and someone at a prompt cannot end up interleaving session CSVs. A second game install, with its own folder, still gets its own watcher.

"It stopped starting at logon" is almost always a moved folder. Both autostart routes - the tray's toggle and this script's fallback - write an absolute path into HKCU\Software\Microsoft\Windows\CurrentVersion\Run. Move, rename or delete the folder and Windows fails to launch it at logon and says nothing whatsoever. There is no error, no log, no dialog: the icon just stops appearing, and if the watcher started from there the recording stops with it. Weeks of "crashes" can pass with nothing recorded.

Check the entry against the filesystem before believing anything else. -Status now does this for whichever route is in use and says so in red, but by hand it is:

$v = (Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Run').'Cyberwise'
$v; Test-Path ($v -replace '"','')      # False = this is your problem

The tray detects this itself now - it warns at startup and --selftest reports the target path and flags a missing one - but a user who has not opened it will not have seen that. Turning the setting off and on again re-points it at the copy that is actually running.

Anything installed by cloning a repo has this property. It is the strongest argument for a real installer: a copy in a stable location does not move when somebody tidies their projects folder.

Task registration may simply be refused. On the machine this was written against, schtasks /Create returns "Access is denied" both from an agent session and from an ordinary PowerShell window - so treat the scheduled task as the nice case, not the expected one. Register-CrashWatch.ps1 falls back to a per-user HKCU\...\Run entry, which needs no elevation, and says plainly what that costs: the watcher starts at logon but nothing restarts it if it dies.

"The overlay stopped working" - snapshot the input stack

A CET overlay fault has twice traced to the HID layer, not to CET. The fix that worked was a USB re-enumeration, and that is the single biggest clue available: it places the fault below CET entirely, which makes reading CET's bindings, widgets or source a waste of an evening. Read what fixed it last time before reading anything else.

tools\New-InputSnapshot.ps1 -Label 'working'     # take this while it WORKS
tools\New-InputSnapshot.ps1 -Label 'broken'
tools\Compare-InputSnapshot.ps1                  # newest two

Take the working one first. Without it every not-OK device node looks guilty and none can be dated. Measured on one machine: 29 nodes were not OK and 26 were simply unplugged peripherals - an Apple trackpad, an HP headset.

Status -eq 'Error' is the wrong probe. It catches an interface that failed to START and misses a device whose delivery is broken while its driver runs fine. The shape worth finding is a half-enumerated composite: a node that is not OK while another node sharing its instance-ID stem IS present and OK. A wholly absent device is one you unplugged; one that is half here failed partway through enumerating.

A held-key sweep only sees PHYSICAL key state. CET keeps its own copy from window messages, so a stale key state inside CET - which is what makes an overlay open and then refuse to close - is invisible to any external tool. That state lives in the process, so no device-level fix can rescue a session already stuck: restart the game before judging whether a fix worked, or the test proves nothing either way.

Reference material

These three are now mostly pointers. The knowledge they used to carry lives in the base wiki under /diagnosis - a skill file is instructions and a wiki article is knowledge, and those rot at different rates. The reference files keep the parts that change what you do.

To capture the machine and install facts that change a crash diagnosis - VRAM against texture volume, pagefile, framework versions - cyberwise-reports has the system profiler. Start there when someone arrives with "it's broken" and no detail.