2.0.6

Expanded firmware controls for supported RTX 50 cards on NVIDIA driver 621.01, improved Settings responsiveness, tray profile switching, window-close choices, and fixes for Apply, Reset and power controls.

Older drivers retain their supported tuning paths. Available controls follow the GPU currently selected.

Read first: runtime settings and firmware limits

xOCD supports two separate workflows:

• Runtime tuning: enable a control on Tuning, enter its target and choose Apply changes.
• Firmware overrides: edit a supported field under Settings → XOC → Firmware limits, choose Save overrides, restart the GPU or Windows, then wait for activation verification.

Firmware overrides are stored in Windows and consumed during GPU initialization. They do not flash the graphics card’s ROM.

Saving a value does not mean it is active. Check Active value and the activation status after restarting.

Increasing a limit provides headroom. Actual voltage, clocks and power consumption still depend on the workload and the GPU’s other limits.

Voltage controls on driver 621.01

Change a live voltage range

On a supported RTX 50 configuration with exact driver 621.01:

1. Check the selected GPU and driver in the header.
2. Open Tuning → Voltages.
3. Enable NVVDD voltage range or MSVDD voltage range.
4. Edit Floor and Ceiling within the available range. Leave Floor unchanged when adjusting only the upper limit.
5. Choose Apply changes and check the result.

xOCD performs its supported 621.01 compatibility preparation automatically. This runtime operation does not require saving a firmware override or restarting the GPU.

NVVDD supplies the GPU core. MSVDD is a separate fabric rail; it is not the VRAM voltage.

Change firmware REL and ALT/OP

1. Open Settings → XOC → Firmware limits → Voltage.
2. Find the supported NVVDD REL / ALT/OP or MSVDD REL / ALT/OP pair.
3. Edit either value. Its partner moves by the same amount, preserving the gap verified for that firmware.
4. Choose Save overrides.
5. Complete the offered GPU or Windows restart.
6. Wait for verification and check both active values before continuing to tune.

Firmware voltage policies and live voltage readings are different values. Existing runtime offsets can also make the Tuning policy differ from the firmware value.

The separate runtime NVVDD OV offset and MSVDD OV offset controls remain disabled on 621.01 and newer. Older drivers retain their supported behavior.

NVVDD and MSVDD current limits

1. Open Firmware limits → Power & current.
2. Find NVVDD current limit or MSVDD current limit.
3. Enter the intended startup default within the verified bounds.
4. Choose Save overrides, then restart the GPU or Windows.
5. Wait for activation verification and confirm the active value.

These firmware rows change the rail’s startup current default. Runtime current requests remain separate.

Unlock OCP limits can remain unavailable when the driver exposes no additional runtime range above the active default. That switch does not need to turn on for a supported firmware-default change to activate.

Board power and input current

The live power controls distinguish:

• Input current: the requested board-input current.
• Power target: the runtime watt target.
• Power budget: the separate watt budget.

Where supported, xOCD displays Requested current separately from the Evaluated limit. A retained 70 A request alongside an evaluated 45 A limit remains visible as a mismatch.

Supported firmware layouts also expose Input-current linked limit under Advanced details. This is a separate initialization field and uses the Save, restart and verification workflow.

The experimental Board input default remains separate from the board-input maximum, linked limit and live request.

These changes do not establish a universal fix for every approximately 530 W limit. Requested values, evaluated constraints and measured power must be checked separately.

When the Tuning power slider is unavailable

A separate active power budget can own the power control.

Choose Use power limit to release that budget through the verified reset workflow. After it succeeds, the percentage control becomes available. Choose the intended percentage and apply it normally.

Expanded firmware editor

Supported configurations provide four tabs:

Tab	Controls
Clocks	Supported core, memory, XBAR, SYS and video offset ranges
Power & current	Power maximum, board-input maximum and rail startup current defaults
Voltage	Linked REL/ALT policies, supported OV/VMIN fields, declared maxima and Speedo
Fans	Verified fan-channel layouts and firmware PWM choices

• Switching tabs preserves drafts.
• Save considers supported edits across the tabs.
• Advanced details keeps additional controls accessible without filling the main tables with experimental fields.
• Speedo uses a separate Windows initialization input. Save it separately from changed ROM controls, restart and verify its effective readback.

The Firmware default column describes a verified default in the currently consumed firmware, which can include an active override. The originals retained for recovery are stored separately.

Older drivers and additional GPU support

When the selected session exposes only the legacy firmware controls, xOCD uses the earlier compact layout. Configurations such as the reported 617.70 setup no longer need expanded tables filled with unavailable rows.

This update adds:

• Conditional linked-current firmware support for matching RTX 5090, RTX 5070 Ti, RTX 5060 Ti and RTX 5060 layouts alongside RTX 5080.
• Recognition of the supplied RTX 3090 Ti and RTX 4070 power-policy variants.
• Continued separation of each selected GPU’s capabilities, drafts, profiles and recovery data.

Model recognition alone does not enable every field. The card’s firmware and native readback must match the supported layout.

The additional Blackwell firmware controls require exact driver 621.01 and matching device evidence. Support for later drivers is not implied.

RTX 20/30/40 firmware editing remains power-only.

Responsiveness and applying settings

• Removed one redundant full maintenance scan after ordinary successful Apply operations when extended-limit maintenance is unnecessary.
• Reduced repeated firmware-editor layout calculations while opening Settings.
• Avoided repeating dashboard scaling when cancelling Settings without a scale or DPI change.
• Preserved final readback, recovery checks and selected-GPU verification.

In four measured synthetic Settings cases, firmware placement calculations fell from 342 to 150, approximately 56% fewer calculations.

This measures reduced layout work. It is not a claimed percentage improvement in live Apply time.

Live readings on tuning controls

Supported tuning rows now show live readings directly beside their controls, including:

• Clock speeds
• Core voltage
• Board power
• Temperature
• Fan data

Targets and pending edits remain separate from telemetry. Missing sensors display —, and stale live readings clear when monitoring or the selected GPU sample becomes unavailable.

Tray profiles and window closing

• Apply saved profiles from the tray Profiles submenu without opening the main window.
• Profile choices follow the selected GPU.
• Add Window X behavior under General Settings:
  • Ask every time
  • Minimize to tray
  • Exit xOCD
• The close prompt offers Minimize, Exit and Cancel.

Reset and recovery

The latest fix addresses a 621.01 discovery bug where an earlier object alias could hide a valid GPU ownership path.

Failure reports now include clearer evidence about selected PCI matching, the required driver object and supported ownership paths. GPU identity checks remain enforced.

Tuning → Reset restores runtime controls against the defaults currently in force. It does not remove saved firmware overrides.

Restore original firmware limits

1. Open Settings → XOC → Firmware limits.
2. Choose Restore original limits.
3. Complete the offered restart.
4. Wait for restoration verification.
5. Follow any further restoration step shown for separately owned inputs such as Speedo.

Closing xOCD does not remove saved firmware overrides.