Journey 1 Walkthrough

Crashless

System Health

GPU42°C

CPU38°C

All healthy

My Issues

Active0

Resolved0

Credits

Balance0

🎁 First session free

A crash was captured in Cyberpunk at 14:32. No existing issue matches this signature. Where should this go?

📥 Captured event

Cyberpunk · nvlddmkm driver crash

Time: 14:32 today
Signature: DXGI_ERROR_DEVICE_HUNG
Module: nvlddmkm.sys · driver 572.86
Evidence: Minidump · Event log · System snapshot

1Start a new issuerecommended

2Search existing issues

3Dismiss this event

✏️Something else

Journey Progress

Triage · Routing

Phase 0 · Evidence

Phase 1 · Diagnosis

Phase 2 · Fix

Phase 3 · Monitor

Event

Captured 3 min ago
Game: Cyberpunk
Auto-analysis: complete

Crashless

System Health

GPU42°C

All healthy

My Issues

Active1

Credits

Balance0

🎁 First session free

Issue #14 · Just now

Your GPU driver crashed rendering Cyberpunk. I captured the dump and matched it to a known driver issue (47 other users saw the same pattern).

Quick question — what were you doing right before the crash?

1Just playing normally

2Opened a menu or cutscene

3Alt-tabbed or switched apps

4Ray tracing or DLSS was on

✏️Describe what happened

⏩Skip questions — diagnose now

Journey Progress

Triage · Routing

Phase 0 · Evidence

Phase 1 · Diagnosis

Phase 2 · Fix

Phase 3 · Monitor

Q&A Rounds

Round 1 · active
Asking about crash context

Evidence

Minidump ✓
Event log (5) ✓
KB match found

Crashless

System Health

All healthy

My Issues

Active1

Credits

🎁 First session free

Issue #14 · 2 min elapsed

Round 1 · "Ray tracing or DLSS was on" ✓

Ray tracing was on — pretty sure DLSS too

Got it. Have you changed anything this week? Driver update, Windows update, new hardware, new game?

1No changes

2Windows updated recently

3Installed NVIDIA driver update

4New game installed

✏️Something else

⏩Skip questions — diagnose now

Journey Progress

Triage

Phase 0 · Evidence

Phase 1 · Diagnosis

Phase 2 · Fix

Phase 3 · Monitor

Q&A Rounds

✓ Round 1 — Ray tracing on
▸ Round 2 — Recent changes?

AI Confidence

Building · 0.65
Likely: driver 572.86 DXGI bug

Crashless

System Health

All healthy

My Issues

Active1

Credits

🎁 First session free

Issue #14 · 3 min

Phase 0 · 2 rounds (Ray tracing on · No changes)

Based on what you've told me, NVIDIA driver 572.86 has a known DXGI timeout bug with Cyberpunk's ray-tracing pipeline. 47 other users reported the same pattern. Here's what I'd try, in order:

🔍 DiagnosisHigh confidence

NVIDIA driver 572.86 DXGI timeout bug with Cyberpunk ray-tracing.

1Roll back to 572.02recommended

2Clean install with DDU

3Run GPU stress test first

🤖Let AI investigate1 credit

✏️Something else

Journey Progress

Triage

Phase 0 · Evidence

Phase 1 · Diagnosis

Phase 2 · Fix

Phase 3 · Monitor

Phase 0 Recap

2 Q&A rounds · Key: ray tracing was on · driver unchanged

Evidence

Minidump ✓
Driver 572.86 ✓
KB · DXGI-TIMEOUT ✓

Crashless

System Health

All healthy

My Issues

Active1

Credits

🎁 First session free

Issue #14 · confirming fix

Phase 0 · Phase 1 · Diagnosis confirmed — driver rollback chosen

Roll back to 572.02

⚠️ About to change your system

I'll roll back your NVIDIA driver from 572.86 to 572.02.

System restore point created first (safety net)
Driver downloaded from Crashless cache — no internet needed
Display driver restarts — your screen will flicker briefly
Takes about 3 minutes
Fully reversible — I can undo it if anything goes wrong

Journey Progress

Triage

Phase 0

Phase 1 · Diagnosis

Phase 2 · Fix

▸ 2.1 Confirm

2.2 Execute

2.3 Outcome

Phase 3 · Monitor

Fix Plan

Rollback NVIDIA
572.86 → 572.02
~3 min · reversible

Safety

Restore point: ready
Cache: driver 572.02 ✓
UAC: will prompt

Crashless

System Health

Modifying…

My Issues

Active1

Credits

🎁 First session free

Issue #14 · executing fix

Phase 2.1 · Confirmed — proceeding

Rolling back your NVIDIA driver now. Leave it running — I'll notify you when it's done. (If you're watching, expect a brief screen flicker.)

Rolling back NVIDIA driver

✓Restore point created — "Crashless — before rollback"

✓Stopped display driver service

✓Uninstalled 572.86

▸Installing 572.02… (65%)

○Restart display driver

○Verify new version

Elapsed: 1m 47s · ~1 min remaining

Cancel at next safe point

Journey Progress

Triage

Phase 0

Phase 1

Phase 2 · Fix

2.1 Confirm

▸ 2.2 Execute

2.3 Outcome

Phase 3 · Monitor

Rollback Log

Restore point ✓
Uninstall ✓
Install ···
Restart pending
Verify pending

Crashless

System Health

All healthy

My Issues

Active1

Credits

🎁 First session free

Issue #14 · awaiting outcome

Phase 2.2 · Rollback completed in 2m 47s · now on driver 572.02

Driver rolled back to 572.02. Your display should look normal. Try launching Cyberpunk — does it start and run without crashing for a few minutes?

It's working — launched OK

Display looks weird or glitchy

Game crashed again right away

✏️Something else

Journey Progress

Triage

Phase 0

Phase 1

Phase 2 · Fix

2.1 Confirm

2.2 Execute

▸ 2.3 Outcome

Phase 3 · Monitor

Fix Applied

Driver 572.02 ✓
Restore point saved
Journaled at %AppData%

Crashless

System Health

All healthy

My Issues

Active0

Monitoring1

Credits

🎁 First session free

Issue #14 · Monitoring

Phase 2.3 · "It's working" ✓

Monitoring your gameplay. I'll let you know if anything happens.

Looking good — fix holding

No crashes in 14 hours.
3h 12m of Cyberpunk play since the fix.

Confidence building40%

I'll let you know if anything happens

Journey Progress

Triage

Phase 0

Phase 1

Phase 2 · Fix

Phase 3 · Monitor

Phase 4 · Resolved

Monitor

Running · ●
Event watcher: active
GPU temp polling: active

Fix History

Driver 572.86 → 572.02
Applied 14h ago
Rollback available

Crashless

System Health

All healthy

My Issues

Active0

Resolved1

Credits

Balance0

🎁 First free session saved

Resolved · 26h

Phase 3 · 22h of clean gameplay · confidence reached

✓ Issue resolved

Resolved in 26 hours. Root cause NVIDIA driver 572.86 incompatibility with Cyberpunk's ray-tracing pipeline. Fix applied Rollback to driver 572.02. Signal 22h of crash-free gameplay across 3 sessions.

Was this helpful?

👍Yes, helpful

👎No / could be better

Skip

Journey Progress

Triage

Phase 0 · Evidence

Phase 1 · Diagnosis

Phase 2 · Fix

Phase 3 · Monitor

Phase 4 · Resolved ✓

Summary

Duration: 26h
Fix type: driver rollback
Confidence: 100%
Gameplay: 22h clean

Export

📄 Save as PDF
📤 Share link

Complete walkthrough — what's here

Every phase of Journey 1 in the locked Option C shell (window chrome + breadcrumb nav + widgets left + activity right). Click through the phase tabs to follow the user's flow from "crash just happened" to "issue resolved with feedback."

Phase flow (full timeline)

-1 Triage — captured event + routing options (start new / search / dismiss). Entry from notification click.
0 · Round 1 — AI's first Q&A question. Contextual chips + escape options.
0 · Round 2 — follow-up question. Past rounds collapse to timeline chip.
1 Diagnosis — AI diagnosis card + ranked fix options + Investigator Mode (FREE badge for first session).
2.1 Confirm — destructive-action pre-flight. Warning card with bulleted "what will happen" + Proceed/Cancel.
2.2 Execute — live progress with spinner, checkmark-by-checkmark log, progress bar, elapsed time, cancel-at-next-safe-point link.
2.3 Outcome — AI asks "did it work?" · three color-coded outcome chips (good / warn / bad).
3 Monitor — watcher card (accumulating state). Game-time counter, confidence progress bar, Mark-resolved primary action.
4 Resolved — summary card + 👍/👎 feedback + export links. Widget panel shows "1 Resolved" now.

Right activity panel evolves per phase

Phase 0 rounds show Q&A log + AI confidence tracker
Phase 1 shows Phase 0 recap + evidence
Phase 2 sub-phases expand the Fix row into 2.1 / 2.2 / 2.3 substeps
Phase 3 shows Monitor status + Fix History
Phase 4 shows final Summary + Export options

What this unlocks

Full Journey 1 is now designed. Every screen the user will see exists as mockup.
Ready to port to SvelteKit components in crashless-web/src/routes/desktop/.
Patterns transfer to Journey 2 (Ambiguous Recurring), Journey 3 (Cold Return), Journey 4 (Recurrence) — same shell, different content per phase.
Light-spec journeys (5-9) and onboarding meta-flow inherit the same shell.

Still open / deferred

Monitor phase shown in "accumulating" state only — 6 other states live in v4, not swapped into this walkthrough
Investigator Mode flow (when user picks it) — separate rail, not shown here
"None of these fit" / low-confidence variants — not exercised in this high-confidence scenario
Failure branches (execution fails, rollback fails) — deferred to a failure-walkthrough
Cold return + recurrence re-entry — handled by Journey 3 / Journey 4 mockups (future)