Skip to content

USER_MANUAL.md

Latest commit

 

History

History
187 lines (138 loc) · 11.7 KB

USER_MANUAL.md

File metadata and controls

187 lines (138 loc) · 11.7 KB
Raw

📘 PboStudio — Master Manual & Complete Documentation

PBO Studio: The All-in-One Stability Testing & Live Curve Optimizer Suite for AMD Ryzen Processors.

📋 Table of Contents

  1. About the Project
  2. Prerequisites & PawnIO Kernel Driver
  3. User Interface Overview
  4. System Health Audit (EXPO RAM & AGESA BIOS Check)
  5. WHEA Watchdog & Smart Recommendations (Coarse vs. Fine)
  6. The Auto-Tuner Engine (Automated CO Step-Down)
  7. Applying CO Values Live vs. Motherboard BIOS Flashing
  8. HTML Stability Certificate Exporter
  9. Crash Protection & BSOD Recovery
  10. Frequently Asked Questions (FAQ)

1. About the Project

PboStudio combines true per-core stress testing (popularized by tools like CoreCycler) with direct live control of the AMD Curve Optimizer via the SMU (System Management Unit) in a single native desktop interface.

No manual .ini file editing is required — testing, error analysis, and core voltage adjustments occur in real-time within a unified workspace.

2. Prerequisites & PawnIO Kernel Driver

  • Operating System: Windows 10 / 11 (64-Bit)
  • Processor: AMD Ryzen (Zen 2, Zen 3, Zen 4, Zen 5 including X3D variants)
  • Permissions: Administrator Privileges (Required for Ring-0 SMU hardware access)
  • Kernel Driver: PawnIO (Digitally signed Windows driver; eliminates unsafe legacy WinRing0/inpoutx64 drivers). Installable with 1 click via the built-in ⚙️ Driver & Engines Manager.

3. User Interface Overview

  • Header:
    • Top left: brand and detected CPU. Below it the 🛡️ WATCHDOG and live telemetry as individual chips (CLOCK, PPT, TDC, EDC, TEMP, SCALAR), each with a utilisation bar against its limit.
    • Top right: language switcher, clickable platform check (🔍 System OK · 95/100) and ⚙️ Driver & Engines.
    • Setup banner: if Prime95, y-cruncher or PawnIO is missing it says so before you press start, and the start button stays disabled.
  • Left Column (Core Table & Recommendations):
    • Smart Recommendation Card: WHEA mitigation proposals with a ⏩ Coarse (+4) vs. 🎯 Fine (+2) toggle, ⚡ Apply values, 🧹 Reset WHEA, plus the recommended profile and a Load profile action.
    • Core Table: every physical core with
      • a CCD chip when the CPU has more than one chiplet (resolved from the topology, not assumed),
      • 🥇/🥈 for the preferred cores — shown only when the processor actually reports CPPC rankings; the tooltip quotes the measured value,
      • a risk-coloured CO value (green → amber → orange → red as it approaches the chip limit),
      • a ▲/▼ delta against the BIOS starting value (amber while only the table knows it, muted once the CPU holds it),
      • status carried by glyph and colour (○ Ready, ● running, ✓ passed, ✕ FAILED, 🔒 limit).
    • Quick actions: [⚡ All to -30] (or -50 on Zen 4 and newer, with a confirmation) and [🔄 BIOS values].
    • APPLY CO VALUES sits directly below the table: all three routes side by side (see section 7).
  • Right Column (3-tab control panel):
    • [🎯 Setup]: profile selector with explanation, runtime estimate, auto-tuner card with step-down progress.
    • [⚡ Engine]: minutes per core, passes, engine choice, instruction set up to AVX-512, FFT range including a custom range, transient pause, core order including a custom order, stop-on-error, skip-core-on-error and delay between cores.
    • [🛡️ System]: emergency temperature limit, treat-WHEA-as-failure, post-test action, Discord webhook.
    • The progress panel lives outside the tabs and stays visible whichever tab is open.
    • Sticky footer: 🚀 Start test / 🤖 Start auto-tuner / ⏹ Cancel test.
  • Bottom Workspace Card (height adjustable via the splitter):
    • Tab 1: 📊 Live telemetry — three separate lanes for clock, temperature and PPT, each with its own labelled scale, a 15-minute time axis, the configured emergency temperature limit drawn in, and a crosshair tooltip with real timestamps.
    • Tab 2: 📜 Log — coloured by severity, with Copy, Folder and Clear.

Settings persist. Language, profile, engine parameters, temperature limit, webhook and window size are stored in runs/settings.json and restored on the next start.

3.1 Test Profiles & Tuning Strategy (Full Run vs. Overnight)

PboStudio includes pre-configured test profiles tailored for Curve Optimizer validation:

  • ⚡ Full Run (SSE & AVX2 Combined):

    • Duration: ~1.5 to 4 hours (on 8-core CPUs).
    • Phases: Phase 1 (SSE with Huge FFTs) + Phase 2 (AVX2 with Smallest FFTs).
    • Purpose: Primary Tuning Preset. Combines low-voltage high-boost limit testing (SSE) with heavy heat & power testing (AVX2). Perfect for standard tuning and Auto-Tuner optimization.

  • 🌙 Overnight Thorough Validation:

    • Duration: ~8 to 16+ hours.
    • Phases: 3 phases across ALL FFT sizes (4K to 8960K+) for SSE, AVX, and AVX2.
    • Purpose: Final Rock-Solid Verification. Tests every single frequency step, cache block, and execution unit across your CPU. Passes here guarantee 100% 24/7 stability before permanent BIOS entry.

💡 Recommended Tuning Workflow:

  1. Run ⚡ Full Run or launch 🤖 Auto-Tuner to find your optimal per-core offsets quickly.
  2. Once your offsets are found, run 🌙 Overnight once overnight for 100% final confirmation.
  3. Click 📋 Copy BIOS List and enter your tested values into your motherboard BIOS.

4. System Health Audit (EXPO RAM & AGESA BIOS Check)

Clicking the platform-check pill (🔍 System OK · 95/100) runs a full diagnostic audit:

  1. RAM EXPO / XMP Profile: Queries WMI for active memory clock speed. If your RAM runs at fallback JEDEC speeds (e.g., 4800 MT/s instead of 6000 MT/s), an optimization alert is flagged.
  2. AGESA BIOS Release Date: Audits motherboard BIOS release dates. BIOS versions older than 9 months trigger a recommendation to update for improved Ryzen stability and memory compatibility.

5. WHEA Watchdog & Smart Recommendations (Coarse vs. Fine)

The integrated Watchdog monitors the Windows Event Log in real-time for WHEA hardware errors 18/19, mapping them strictly in ascending numerical order to physical CPU cores (Core 0, Core 1, Core 4).

Precision Modes:

  • ⏩ Coarse (+4): Backs off voltage magnitude by +4 steps (e.g., -30 ➔ -26). Recommended for quickly stabilizing volatile cores.
  • 🎯 Fine (+2): Backs off voltage magnitude by +2 steps (e.g., -30 ➔ -28). Tailored for precision tuning to preserve maximum performance.

Clicking ⚡ Apply Values updates all core margins in the table instantly.

6. The Auto-Tuner Engine (two-way search)

The auto-tuner writes every value itself, over the SMU, immediately before the core is measured — nothing needs confirming. Every one of those writes is in the log.

Per core:

Situation What happens
Passed, above the limit one step lower (-3 coarse, -1 fine)
Passed at the chip limit locked (🔒) — the limit is proven
Failed, but passed at a higher value earlier back to that value and locked. No retest: it already survived a full slot
Failed, never passed raise the voltage and test again, step by step upward, until a value actually holds. Only that one is locked
Failed at 0 this core stops with a note that the cause is not the Curve Optimizer (RAM/EXPO, cooling, BIOS version)

So no locked value carries the label "done" without having been tested.

Two things worth knowing:

  1. Starting at the chip limit (say -30) means no downward search happens — there is nothing below it. The tuner tests -30 and works upward on a failure. For a real search, start mild (0 or -5) and let it descend.
  2. The search is bounded by "Passes". From -30 with coarse steps and 3 passes you only reach -24. If that is not enough the core stays open rather than locked. The runtime estimate in the Setup tab accounts for the worst case.

The Auto-Tuner automatically discovers individual core stability limits:

  1. Selecting Mode:
    • Coarse (-3 steps): Fast discovery mode. Steps down passing cores by 3 points per iteration.
    • Fine (-1 step): Precision mode. Steps down passing cores by 1 point per iteration.
  2. Workflow:
    • When a core passes a test iteration, the Auto-Tuner lowers its voltage offset for the next round.
    • When a core fails or trips a WHEA error, the Auto-Tuner steps back to the last safe margin, locks the core as optimal, and continues testing remaining cores.

7. Applying CO Values Live vs. Motherboard BIOS Flashing

All three routes sit together under the core table in the APPLY CO VALUES block.

⚡ Apply live (Ctrl+S)

Writes the changed values straight into the AMD SMU registers. Takes effect at once, no reboot.

  • It is gone on the next boot, because the BIOS reapplies its own values at POST. Closing the app changes nothing — the values stay active as long as Windows is running.

🔄 On every Windows start

The checkbox in the apply block creates the scheduled task PboStudioWatchdog, which reapplies your saved values in the background after every boot. More convenient than the BIOS route, but it only takes effect a few seconds after login and needs administrator rights. A completed auto-tuner run updates this profile automatically.

Permanent Motherboard BIOS Entry:

No Windows application can flash or alter motherboard SPI BIOS chips during runtime. To enter your tested values permanently into BIOS:

  1. Note your stable core margins from PboStudio (or click 📋 Copy BIOS List).
  2. Reboot PC and press DEL or F2 to enter BIOS.
  3. Navigate to: Advanced ➔ AMD Overclocking ➔ Precision Boost Overdrive ➔ Curve Optimizer.
  4. Set Curve Optimizer to Per Core, sign to Negative, and enter magnitudes (e.g., Core 0 = 20, Core 1 = 25...).
  5. Press F10 to save and exit.

8. HTML Stability Certificate Exporter

Clicking 📄 Export Report generates a standalone, interactive HTML stability certificate featuring:

  • Complete hardware summary (CPU, RAM, System Audit Score)
  • Completed iterations, test durations, and failure counts
  • Final recommended Curve Optimizer core matrix ready for printing or forum sharing.

9. Crash Protection & BSOD Recovery

If a system crash (BSOD) occurs during heavy testing:

  • PboStudio saves test state after each iteration to runs/state.json.
  • Upon reboot, PboStudio detects the interrupted state and prompts: ✓ Apply Recommended Offset & Resume.

10. Frequently Asked Questions (FAQ)

Q: Why does PboStudio require Administrator rights?
A: AMD SMU firmware communication requires Ring-0 kernel access. Administrator rights are required to interact with the PawnIO driver.

Q: Does PboStudio work on Intel CPUs?
A: Per-core stress testing (Prime95 / y-cruncher rotator) works on all processors. AMD Curve Optimizer controls are specific to Ryzen CPUs.

Q: How does PboStudio differ from CoreCycler?
A: CoreCycler is a PowerShell wrapper script without SMU writing capabilities. PboStudio provides direct live SMU read/write, automated auto-tuning, WHEA watchdog tracing, live telemetry graphing, and a native UI without manual .ini file editing.