How to read the scores in this report. There is one headline number — Capture Health above — which reflects how the game actually ran during this session. The other scores further down are drill-downs that each measure a different axis and are not expected to equal Capture Health:
Gaming Setup Score — how well your Windows/hardware is configured for gaming (ReBAR, HAGS, power plan, drivers). A config rating, not this session's result.
Pre-Game Health — a pre-flight static check of drivers/config before you play. It doesn't see this session at all.
Priority Rules — the count of high-priority rules that drive the verdict above. It is not the total of every tip in the report — lower-priority config suggestions (HAGS, Game Mode, PCIe link, RAM kit, etc.) are listed further down as quick wins.
Results disclaimer: Performance outcomes vary by hardware, game build, drivers, background load, thermal state, and applied settings. Values shown are measured for this capture and are not guaranteed future results.
Apply optimizations selectively and re-capture to verify impact.
🛑 Capture Reliability
Status
Healthy
Stop Requested
No
Stop Latency
N/A
Escalation Used
No
Force Kill Used
No
Run Result
Completed
Lingering ETW sessions after stop:
None detected
🏆
Gaming Setup Score
Configuration & hardware readiness
ⓘ How is this calculated?
Drill-down score. This rates how well your system is configured and equipped for gaming (config + hardware axes). The single headline session verdict is Capture Health at the top of the report — this number won’t necessarily match it.
🚨 PRIMARY LIMITER — GPU is overheating and thermal throttling: Most of your system is healthy, but this is the biggest factor holding back performance right now. Fix this first — see the ranked actions below.
🚨 GPU BOTTLENECK DETECTED: Your NVIDIA GeForce RTX 3080 Ti (97% util) is the limiting factor. Lower graphics settings (resolution, shadows, RT) for higher FPS. PresentMon analysis: GPU BOUND.
Memory subsystem healthy (0.00 hard faults/sec) - no RAM-related stuttering expected.
ℹ️ Detected security software: Windows Defender. No significant performance impact observed during this session.
⚠️ SCREEN TEARING DETECTED: 52.1% of frames had visible tearing. Enable G-Sync/FreeSync or V-Sync to eliminate tearing for smoother visuals.
🛠️ OPTIMIZATION TIPS: 1 minor issue(s) detected. Apply the suggested fixes for a smoother gaming experience.
📋 All Findings at a Glance (hover for details)
GPU at Maximum Load
79%
CPU Load
97%
GPU Load
0.00
RAM Faults/s
129µs
Input Latency
🎯
Top 3 Actions
Ranked across every check by measured impact — do these first. Hover a card to see why it ranked.
1GPU is overheating and thermal throttlingCritical impactHigh confidence
Cool the GPU: clear dust, raise the fan curve (e.g. MSI Afterburner), improve case airflow, and cap the frame rate or lower one heavy setting. Full step-by-step guidance is in Your Game Plan below.
2Graphics card is not getting its full PCIe lane widthHigh impactModerate confidence
Seat the card in the top x16 slot, and in BIOS enable 'Above 4G Decoding' and 'Resizable BAR'. Full steps are in Your Game Plan below.
3Virtualization-Based Security / Memory Integrity is onMedium impactModerate confidence
Settings → Core isolation → turn off Memory Integrity (weigh the security impact). Some competitive anti-cheats require it — leave on if so.
Confidence reflects how strongly the telemetry supports each finding — it is a qualitative signal strength, not a performance guarantee. Full step-by-step guidance is in Your Game Plan below.
🎮 Your Game Plan
Plain-English summary and step-by-step fixes — start here if you're not sure what to change.
We found a few things slowing your games down. Let's fix them.
Your average frame rate was about 49 FPS, dipping to roughly 36 FPS in the rough patches.
We found 2 main issues to fix and 4 quick optimizations. They're listed below, most important first.
1Cool down your graphics card
Your GPU reached 88°C while gaming. When it gets this hot it deliberately slows itself down to avoid damage, which costs you FPS and causes stutters.
Do this:
Make sure your PC has room to breathe — keep it off carpet and away from walls.
Gently clean dust from the case fans and graphics card with compressed air (PC off and unplugged).
In MSI Afterburner (a free tool), raise the fan speed a little or set a steeper fan curve.
If it is still hot, lower one or two heavy settings in-game (shadows, ray tracing).
✅ Check it worked: Re-run Arbiter while gaming — the GPU temperature should stay under about 80°C and the thermal-throttling warning should disappear.
⏱ 10–20 min🔧 Medium🎯 High impact⚠️ Low risk🔁 Reboot: No
2Give your graphics card its full lane width
GPU is capable of x16 but is currently linked at x8 (~50% PCIe bandwidth reduction). Confirm the GPU is in the primary x16 slot, review BIOS PCIe / bifurcation settings, and check whether an M.2 drive is sharing the GPU's lanes.
Do this:
Power off and unplug the PC, then open the side panel.
Make sure the graphics card is in the top PCIe slot (closest to the CPU) — that is the full-speed x16 slot.
If you have an M.2 SSD, check your motherboard manual: some M.2 slots borrow lanes from the graphics card. Moving the SSD to a different M.2 slot can free them.
In BIOS, enable 'Above 4G Decoding' and 'Resizable BAR', and set the main slot to x16 if the option exists.
✅ Check it worked: Re-run Arbiter — the GPU's PCIe slot on the hardware map should turn green and read x16.
⏱ 15–30 min🔧 Advanced🎯 High impact⚠️ Medium risk🔁 Reboot: Yes
3Virtualization-Based Security / Memory Integrity is on
VBS and HVCI (Memory Integrity) virtualize parts of the kernel for security. This is good for safety but measurably taxes CPU-bound games (often 5-10%+). Only disable it if you understand the security trade-off and your anti-cheat doesn't require it.
Do this:
Settings -> Core isolation -> turn off Memory Integrity (weigh the security impact)
Some competitive anti-cheats require it — leave on if so.
✅ Check it worked: Re-run Arbiter — this finding should clear from the OS Diagnostics panel.
⏱ 5–15 min🔧 Medium🎯 Medium impact⚠️ Low risk🔁 Reboot: Yes
4Heavy startup-app load
Several resource-heavy apps launch at startup and keep running in the background during gameplay, consuming RAM, CPU and disk.
Do this:
Open Task Manager -> Startup apps and disable anything you don't need at boot (launchers, sync clients, RGB/monitoring utilities).
✅ Check it worked: Re-run Arbiter — this finding should clear from the OS Diagnostics panel.
⏱ 5–15 min🔧 Medium🎯 Medium impact⚠️ Low risk🔁 Reboot: No
5Turn on Windows Game Mode
Game Mode tells Windows to prioritise your game and hold back background tasks and updates while you play.
Do this:
Press the Windows key and type 'Game Mode settings'.
Switch Game Mode to On.
✅ Check it worked: Re-run Arbiter — Game Mode should show as Enabled.
⏱ 30 sec🔧 Easy🎯 Medium impact⚠️ Low risk🔁 Reboot: No
6Turn on Hardware-Accelerated GPU Scheduling
This lets your graphics card manage its own work more directly, which can shave off a little input lag.
Do this:
Press the Windows key, type 'Graphics settings', and open it.
Turn on 'Hardware-accelerated GPU scheduling'.
Restart the PC.
✅ Check it worked: Re-run Arbiter — HAGS should show as Enabled.
⏱ 2 min🔧 Easy🎯 Low impact⚠️ Low risk🔁 Reboot: Yes
After you make a change, run Arbiter again and compare — fixed issues should disappear and your scores should climb. ⬆️
📋 Primary Finding— see Capture Health at the top for the headline score
⚙️ GPU at Maximum Load
WARNING: 1 rule(s) triggered — GPU at Maximum Load
🎮 Gaming/Home
📸 Shareable Scorecard
Save or copy a single-image summary of this session to share with your squad or support
✅ Verified Gains
Measured before/after for Diablo IV — proof a change actually helped, not a guess
VERIFIED IMPROVEMENTvs your previous Diablo IV run (2026-09-29T22:00:39)
Metric
Before
After
Change
Average FPS
46.3fps
49.3fps
▲ +3.0fps (+6.5%)
1% low FPS
26.8fps
35.9fps
▲ +9.1fps (+34.0%)
0.1% low FPS
24.3fps
31.2fps
▲ +6.9fps (+28.4%)
Stutters
2.0
0.0
▲ -2.0 (-100.0%)
Peak DPC latency
142.9
128.6
▲ -14.3 (-10.0%)
Hard-fault rate
0.0/s
0.0/s
— 0.0/s
Dropped frames
0.0%
0.0%
— 0.0%
Frame consistency
99.98%
100.0%
— +0.02%
⚡ QUICK WINS — Instant FPS Boosts
Top 3 easiest optimizations ranked by impact
🏆
🎮
①
Enable Windows Game Mode
+3-5%
FPS Boost
30 sec
Easy
● Settings → Gaming → Game Mode → ON
⚠
②
Improve GPU Cooling
+10-20%
FPS Boost
5 min
Medium
● Open case, clean dust, or increase fan curve in MSI Afterburner
✅ Core gaming toggles look tuned, but capture-level performance concerns were detected elsewhere in this report.
💡 Use the Quick Fixes panel in the app to apply these optimizations automatically.
🛠️ OS Diagnostics & Troubleshooting
Includes a live scan of installed drivers, startup apps, Windows configuration and general system health (disk, memory, CPU, network).
OS Health
70/100
Minor issues
● 3 Medium● 6 Lowℹ️ 1 Info
● Virtualization-Based Security / Memory Integrity is on
Security↻ Reboot
VBS and HVCI (Memory Integrity) virtualize parts of the kernel for security. This is good for safety but measurably taxes CPU-bound games (often 5-10%+). Only disable it if you understand the security trade-off and your anti-cheat doesn't require it.
🔎 VBS=on, HVCI=on
Fix: Settings → Core isolation → turn off Memory Integrity (weigh the security impact). Some competitive anti-cheats require it — leave on if so.
● Heavy startup-app load
Startup
Several resource-heavy apps launch at startup and keep running in the background during gameplay, consuming RAM, CPU and disk.
🔎 3 high-impact of 11 startup entries: OneDrive, Battle.net, SteelSeriesGG
Fix: Open Task Manager → Startup apps and disable anything you don't need at boot (launchers, sync clients, RGB/monitoring utilities).
● WMI activity storm during gameplay
Services
A high volume of WMI activity occurred during gameplay. Management/monitoring agents (OEM utilities, RGB software, some anti-cheat and enterprise tools) can hammer WMI and cause periodic CPU spikes and hitching.
🔎 1,416 WMI operations · top consumer powershell (1,181)
Fix: Identify the noisy app (often OEM/RGB/monitoring software) and close it before gaming, or disable its background service.
● Network adapter power saving is enabled
Network
'Allow the computer to turn off this device to save power' can introduce micro-drops and latency spikes on Wi-Fi/Ethernet, which show up as lag or rubber-banding in online games.
🔎 Power saving on: Ethernet 2
Fix: Device Manager → your network adapter → Properties → Power Management → uncheck 'Allow the computer to turn off this device'.
● USB Selective Suspend is enabled
Device
Windows can power down USB devices it thinks are idle. For gaming this occasionally resets or briefly drops a controller, mouse or headset, feeling like input lag or a device hiccup.
🔎 DisableSelectiveSuspend is not set (power saver active)
Fix: Device Manager → each USB Root Hub → Power Management → uncheck 'Allow the computer to turn off this device', or disable USB selective suspend in the advanced power plan settings.
● Outdated audio driver: Realtek Audio Universal Service
Driver
This driver is well over a year old. Newer drivers frequently fix stutter, latency and stability bugs — especially for GPU, network and audio devices.
🔎 Version 1.0.551.0 dated 2022-08-08 (~50 months old)
Fix: Install the latest driver from the device maker's website (not just Windows Update).
This driver is well over a year old. Newer drivers frequently fix stutter, latency and stability bugs — especially for GPU, network and audio devices.
🔎 Version 1125.13.424.2023 dated 2023-04-24 (~41 months old)
Fix: Install the latest driver from the device maker's website (not just Windows Update).
ℹ️ Game folder not excluded from real-time antivirus
Security
Real-time scanning can add disk latency when a game streams assets. Adding the game's folder as an exclusion can reduce texture-streaming hitches. Only exclude trusted game folders.
🔎 No Defender exclusion matched diablo iv.exe
Fix: Windows Security → Virus & threat protection → Exclusions → add your game's install folder (trusted titles only).
These findings cover both game-specific and whole-PC issues that slow the machine —
driver DPC latency, GPU driver resets, background service/WMI storms, device resets, crashes,
outdated drivers, heavy startup load, low disk space or a failing/HDD system drive, memory
pressure, background CPU hogs, and configuration such as Memory Integrity, page file, HPET and
antivirus. Always weigh security trade-offs before disabling protections.
🏥
Pre-Game Health Check
100/100
Drill-down check. This is a live pre-flight scan of drivers and Windows config run right now — it does not measure this capture. For the session verdict see Capture Health at the top of the report.
Click any finding to expand details. Hover for quick summary.
🎮GPU Thermal Throttling (88°C peak)▸ expand
The GPU hit a thermal slowdown condition during gameplay. This can reduce clocks and amplify frame-time spikes.
🧠 Why This Happens
Cooling capacity is being exceeded under sustained load, or airflow/fan behavior is insufficient for the workload.
🛠️ How To Fix
Clean the GPU heatsink and filters, improve case airflow, raise the fan curve, and verify the card is not being choked by dust or restricted intake.
📊 Game Performance Metrics
Hover over any metric for detailed explanation
CPU Load
✅
33.2%
Processor utilization
Game Thread Switches/s
✅
124
Context switches for this game process
Memory Faults/s
—
Hard page faults per second
Asset Loading/s
✅
1
Disk I/O operations
GPU Utilization
✅
97%
NVIDIA GeForce RTX 3
GPU Temp
⚠️
88°C
Graphics card temperature
VRAM Usage
✅
84%
10320/12288 MB
GPU Status
🔥 Throttling
Thermal limit reducing clocks
Avg FPS
⚠️
49
Average framerate
1% Low FPS
✅
36
Bottom 1% framerate
DPC Latency
✅
0.1ms
Peak driver latency
DPC Spikes
✅
0
Latency events >500µs
Disk Throughput
Read: — Write: —
Network Throughput
Down: 441.83 B/s Up: 53.27 B/s
●
System Performance Timeline — CPU, RAM, Disk & Network
● What This Chart Shows
This timeline tracks system-wide metrics from Windows ETW kernel tracing (not GPU-specific): ● CPU % (processor load) · ● DPC Latency (driver delays) · ● Memory Faults (RAM/paging) · ● Context Switches · ● Disk I/O
Use this chart to identify: CPU bottlenecks, driver latency spikes (DPC), memory pressure, and storage stalls. Compare with GPU Timeline: If FPS drops here don't match GPU issues above, the bottleneck is your CPU or RAM, not GPU.
How to read: FPS drops that align with CPU/DPC spikes indicate CPU bottleneck. Drops with Memory Faults = RAM issue. Drops with high Disk I/O = asset streaming hitch. FPS note: This chart uses window-averaged FPS aligned to the snapshot cadence, so it will look smoother/steppier than the FPS & Frame Time Timeline above.
FPS (window-avg)
CPU %
DPC Latency
Memory Faults
Context Switches
Disk I/O
● Correlation Analysis Tips
🎮 FPS drop + CPU spike → CPU bottleneck (close background apps)
🎮 FPS drop + Mem Faults → RAM exhausted (close Chrome)
🎮 FPS drop + Disk spike → Asset streaming (need SSD)
🎮 GPU Diagnostics — Your Graphics Card's Vital Signs
Arbiter is monitoring your GPU: Tracking utilization (is it maxed out?), temperature (thermal throttling?), VRAM usage (out of memory stutters?), and clock speeds (boosting properly?). Problems here directly impact your FPS and frame pacing.
⚠️ Clock/power adjusted to load: the driver’s point-in-time snapshot reported an idle p-state (very low clocks/power) that contradicted the measured load and temperature — a common stale read after a driver reset or when the GPU was polled between frames. The values above use the highest-load sample instead. Treat the exact MHz/W as approximate; utilization and temperature are the reliable load signals.
🔴 Max GPU Load🔴 High Temp
🔧 PCIe Slot Configuration
✅ Load-qualified: the GPU was under load (avg 97%) when this link was read, so a reduced width/gen below is a real finding worth investigating.
Current Configuration
PCIe 4.0 (16.0 GT/s)
x8 lanes
GPU Maximum
PCIe 4.0 (16.0 GT/s)
x16 lanes
⚠️ Configuration Issues Detected:
🎮 REDUCED LANE WIDTH: GPU capable of x16 running at x8 (50% bandwidth loss)
Likely cause: PCIe lane bifurcation (M.2 drives sharing lanes with GPU slot) or installed in secondary x8 slot
Common culprit: M.2 expansion cards in lower PCIe slots can force GPU lane reduction AND speed downclocking
Check BIOS: Look for 'PCIe Bifurcation', 'M.2 Mode', or 'PCIe Lane Distribution' settings
Note: PCIe 4.0 (16.0 GT/s) x8 = ~8 GB/s — still faster than PCIe 3.0 x16 (15.75 GB/s)
🔧 Recommended Actions:
CHECK M.2 CONFIGURATION: Many motherboards share PCIe lanes between GPU and M.2 slots
M.2 EXPANSION CARDS: If using M.2 adapter cards in lower PCIe slots, they can cause lane contention AND force entire PCIe bus to downclock
SOLUTION: Remove M.2 expansion cards from lower PCIe slots, use only motherboard-integrated M.2 slots when possible
In BIOS, check if M.2_1 or M.2_2 slot is stealing 8 lanes from GPU (look for PCIe Bifurcation settings)
If GPU is in secondary slot, move to primary PCIe x16 slot (topmost, closest to CPU)
Performance impact: Minimal for most games at 1080p/1440p, ~5-10% at 4K with high VRAM usage
🎮 FPS & Frame Time Timeline — GPU Performance Over Time
Performance Telemetry Overview
Real-time GPU metrics sampled directly from your graphics card and driver telemetry stack:
🎮 FPS — DirectX Present timing
📊 GPU Load — Utilization %
🌡️ Temperature — Thermal state
🧠 VRAM — Memory usage
⚡ Power — Draw in watts
⏱️ Clock — GPU frequency
🌡️ Use this to spot: Thermal throttling (temp spikes), GPU bottlenecks (100% util), VRAM exhaustion, frame drops
Forensic Mode Active: DirectX Graphics Kernel (DxgKrnl) events captured for frame-level analysis. Shows Present() calls, frame timing, DWM composition, and per-process GPU usage. Enabled when using --focus-app with benchmark/game.
ℹ️ Why the frame numbers differ across panels. Three different counters measure three different things over different time windows, so they are expected to disagree:
• PresentMon frames (17,282) — every present from the whole session (all layers/overlays), used for FPS %, 1% lows and tearing.
• DxgKrnl Present() calls (4,893) — only the focused process’s frame submissions captured by the kernel provider (a narrower window).
• DWM refreshes (934) — desktop compositor vsync events, i.e. how often Windows composited, not how many frames your game rendered.
Tearing is judged from the PresentMon present stream (AllowsTearing flag); a “no tearing” note on the DWM/DxgKrnl side only means the composited desktop path didn’t tear — it does not override the PresentMon tearing figure.
✅ Gamer Quick Triage (Do These First)
1) FPS shows 0: Present() events were not captured (fix by running as Admin + --focus-app; update to latest build).
2) Stutter / spikes: Close overlays + GPU background apps (Discord/Chrome HW accel/OBS/NVIDIA Overlay).
3) VRAM > 90%: Lower textures first (biggest VRAM win), then resolution; disable RT if enabled.
4) GPU temp > 85°C: Clean dust, improve airflow, set a more aggressive fan curve (throttling = FPS drops).
5) TDR / Present failures: Revert GPU overclocks, verify PSU + PCIe power cables. Advanced / risky: Clean-install driver with DDU only if standard reinstall fails.
🎮 Frame Drops
4,893
Frames Rendered
0 frames dropped — rendering pipeline perfect
⚠️ GPU Contention
32,846
Context Switches
Heavy GPU multitasking — background apps fighting for GPU time
● DWM Present Sync
934
Compositor refreshes | on pace
● VRAM Requests
1,413
0 MB requested
Per-Process GPU Usage
VRAM Usage Over Time
570 samples collected every 2 seconds
10,283 MB avg
Min: 10,231 MB | Max: 10,320 MB
Peak: 84.0% of 12,288 MB
Process
Present Calls
Context Switches
GPU Share %
Diablo IV.exe
3,530
5,139
74.6%
dwm.exe
550
892
11.6%
System
230
21,831
4.9%
WmiPrvSE.exe
167
1,317
3.5%
AWCCOverlay.exe
89
877
1.9%
csrss.exe
51
79
1.1%
explorer.exe
27
120
0.6%
powershell
20
289
0.4%
svchost.exe
17
108
0.4%
Taskmgr.exe
10
85
0.2%
● Understanding This Table:
• Present Calls: Frame submissions to GPU - higher = more rendering activity from this process
• Context Switches: GPU scheduling events - high values indicate GPU multitasking between apps
• GPU Share %: Share of total frame submissions (Present calls), i.e. how often each process handed a frame to the GPU — not GPU compute/SM utilization. A high share for your game (e.g. the compositor DWM or System taking a slice) is normal and does not by itself mean those apps are stealing GPU horsepower.
High GPU Contention: 32,846 context switches (109/sec) - multiple apps competing for GPU. Background apps (Chrome, Discord, OBS) degrading performance.
Perfect VSync Alignment: 934 refresh events with 0.00% miss rate - frame delivery synchronized to 60Hz.
High VRAM Usage: Peaked at 10,320 MB (84.0%), averaged 10,283 MB. Approaching capacity limit - reduce texture quality or close background apps.
ℹ️ What These Metrics Mean & How To Improve Them:
• Present() Calls: Frames submitted to GPU. More = higher FPS. Low? Check CPU bottleneck or game settings.
• Context Switches: GPU switching between apps. High (>1000)? Close background apps like Chrome, Discord, OBS.
• DMA Buffers: Command queue latency. Slow (>16ms)? Update GPU drivers, check VRAM usage.
• VSync: Monitor refresh sync. Misses? GPU cannot maintain refresh rate - lower graphics settings or enable G-SYNC/FreeSync.
• TDR: GPU driver crash. Any TDR events? Update drivers immediately, check for overheating, remove GPU overclock.
• DWM: Windows desktop compositor. Frame drops? Disable visual effects in Settings → System → Display → Graphics.
🧪 Data Source: GPU metrics captured via Microsoft-Windows-DxgKrnl ETW provider. For focused app analysis with FPS timeline, use: --focus-app YourApp.exe. System-wide VRAM tracking requires nvidia-smi in PATH (included with NVIDIA drivers).
🩺 GPU Health & Performance Analysis
Comprehensive diagnostics covering thermal state, VRAM allocation, power delivery, driver stability, and performance optimization.
⚠️ WARNING: GPU temperature at 88°C - thermal throttling imminent (clocks reducing to maintain safe temp)
🛠️ Recommended Actions:
Thermal Analysis: Current temp 88°C approaching throttle threshold (typically 83-87°C for modern GPUs)
Maintenance: Clean GPU fans/heatsink with compressed air, verify case has adequate ventilation (2+ intake fans)
Monitoring: Install HWiNFO64 to log 'GPU Temperature' and 'GPU Clock' during gaming - watch for clock speed drops indicating throttling
Results are workload-dependent and not guaranteed. Validate each change with a fresh capture and keep rollback options (restore point/driver rollback) available.
Technical Note: GPU diagnostics captured via NVML (NVIDIA Management Library) - full power, clock, thermal, PCIe, encoder/decoder, and throttle reason telemetry with ultra-low overhead (~0.05% CPU). Correlate GPU activity with ETW CPU/DPC/Power events to identify graphics-induced system-level anomalies.
Discrete stutter events isolated by the Arbiter Stutter Autopsy engine (the same count shown on the scorecard). Use the 1% low (73% of average) and smoothness score (91/100) for overall stability.
⚡
Advanced Frame Timing
ⓘ PresentMon Data
🎮GPU Render Timeⓘ
Average
12.35ms
Min
0.21ms
Max
28.95ms
95th %ile
22.57ms
⚡Display Latency (Input Lag)ⓘ
Average
19.91ms
Min
11.42ms
Max
48.16ms
95th %ile
31.17ms
💻CPU Present API Overheadⓘ
Average
0.30ms
Max Spike
5.64ms
🖼️
Present Mode & Frame Delivery
ⓘ Presentation Analysis
Active Present Mode
✅ OPTIMAL
Hardware: Independent Flip
Hardware-accelerated flipping. Best performance, lowest latency.
Mode Distribution:
Hardware: Independent Flip9,002 frames (52.1%)
Hardware: Legacy Flip7,375 frames (42.7%)
Composed: Flip905 frames (5.2%)
⚡Screen Tearing
9,002
52.09% of frames
📉Dropped Frames
0
0.00% of frames
📊
Per-Process Frame Breakdown
ⓘ Process Attribution
Process
Frames
Avg FPS
Avg Frame Time
Diablo IV.exe
9,002 (52.1%)
49.3
20.28ms
dwm.exe
7,375 (42.7%)
40.4
24.75ms
Battle.net.exe
905 (5.2%)
54.6
18.31ms
⚠️ Background App Impact
Background applications (Discord overlays, browsers, streaming software) submit frames and consume GPU resources. Close non-essential apps for maximum gaming performance.
🎮
Bottleneck Analysis
85% confidence
CPU79%
vs
GPU97%
🎮 GPU BOTTLENECK
GPU at 97% while CPU at 79%. Your graphics card is the limit.
💡 Lower resolution, quality settings, or ray tracing to improve FPS. Consider GPU upgrade for more performance.
ℹ️ Why CPU% differs from Task Manager
Report shows: Peak single-thread/per-core usage during gaming (79% on busiest core) Task Manager shows: Average across all cores (e.g., 1 core at 88% ÷ 8 cores ≈ 11% total)
Gaming bottlenecks happen on individual threads, not total CPU%. One maxed-out core = CPU bottleneck, even if total CPU usage looks low!
No significant stutters detected across 9,002 frames — frame delivery was 100.0% consistent. Nothing to dissect. Smooth sailing.
📊 Frame Delivery Timeline
Temporal Frame Timing Analysis
Temporal analysis of frame timing showing GPU render time, display latency, and frame delivery over the session.
Spikes indicate exact stutter moments and bottleneck transitions.
Avg GPU Render Time
11.9ms
Time GPU spends drawing each frame
Avg Display Latency
19.7ms
Input-to-photon lag
Avg Frame Time
20.2ms
Total delivery time (1000/FPS)
📖 How to Read This Timeline
GPU Render Spikes: Entered demanding area (dense city, explosions) - GPU bottleneck
Display Latency Spikes: V-Sync kicked in, alt-tabbed, or borderless windowed lag penalty
All Metrics Spike Together: Loading screen, shader compilation, or level transition
Flat Lines: Stable performance - the ideal state
Recurring Patterns: Background process interference (Windows Update, anti-virus scan)
🖥️ Your Gaming Rig — Hardware Health Check
Arbiter is analyzing your hardware: Checking PCIe lanes (is your GPU bottlenecked?), RAM speed & dual-channel status, CPU clock speeds (throttling?), storage performance (SSD vs HDD impact on loading), and Windows power plan (gaming mode?). Hover over components below for detailed diagnostics.
🧩 System Board Configuration & Health
Detailed component-level diagram with health indicators. Hover over any component for specifications and detected issues.
⚠️ Hardware Configuration Issues Detected
⚠️ WARNINGS (Performance Impact Likely)
[PCIe Link Width] GPU PCIe Link Running Below Capability
GPU is capable of x16 but is currently linked at x8 (~50% PCIe bandwidth reduction). Confirm the GPU is in the primary x16 slot, review BIOS PCIe / bifurcation settings, and check whether an M.2 drive is sharing the GPU's lanes.
🔧 Reseat the GPU in the primary x16 slot (top slot, closest to the CPU), check BIOS for PCIe / bifurcation settings, and ensure an M.2 drive is not sharing the GPU lanes.
[Storage] Suboptimal allocation unit size (2048 bytes instead of 4096)
Suboptimal allocation unit size (2048 bytes instead of 4096)
🔧 Reformat with 4K allocation units for NVMe performance
[Memory] Mismatched RAM Speeds Detected
RAM modules running at different speeds: 3200, 2667 MHz
🔧 All RAM will run at speed of slowest module. Consider replacing with matched kit for optimal performance.
[Memory] XMP/DOCP Profile Not Enabled
RAM running at 2667MHz instead of rated 3200MHz (JEDEC fallback mode)
🔧 Enable XMP/DOCP profile in BIOS to run RAM at full rated speed. Performance impact: 5-15% FPS loss in CPU-bound games.
ℹ️ INFORMATIONAL (Optimization Opportunities)
[Storage] Non-optimal filesystem: FAT32
Non-optimal filesystem: FAT32 — Consider NTFS or ReFS for best Windows compatibility
[Memory] Mismatched RAM Capacities
RAM modules with different capacities: 32, 16 GB — For best performance, use matched capacity modules. Flex mode may reduce performance.
Critical gaming hardware configuration that directly impacts FPS and responsiveness
⚠️ Monitor
59Hz
3840x2160
🔴 Low Refresh
⚡ Tip: High refresh rate monitor (144Hz+) reduces input lag and provides smoother gameplay
🧠 RAM Profile
2667 MHz
Rated: 3200 MHz
⚠️ XMP/DOCP Disabled
⚠️ Unbalanced memory kit (Mismatched RAM Capacities; Mismatched RAM Speeds Detected). Mixed speeds run every module at the slowest speed, and mixed capacities can force asymmetric/Flex mode — that caps memory bandwidth more than an XMP toggle would. Fix: fit a matched kit (identical capacity and speed) before relying on XMP/EXPO.
⚠️ Mouse
USB Input Device
● Check mouse software (Logitech G Hub, Razer Synapse, etc.) to verify 1000Hz polling rate
⚙️ CPU Performance State
Processor: 11th Gen Intel(R) Core(TM) i7-11700KF @ 3.60GHz
3.50 GHz
Base Clock
3.50 GHz
Current Speed
8/16
Cores/Threads
Cache: L2: 4096 KB, L3: 16384 KB
ℹ️ Why CPU % can be misleading
Windows Task Manager reports CPU usage relative to the processor's base clock, so a modern CPU that boosts above base can read over 100%, while a single saturated core (for example a game's render thread) can bottleneck FPS even when total CPU looks "low." To see this yourself, switch Task Manager to per-core graphs (Performance tab → right-click the CPU graph → Change graph to → Logical processors), or open Resource Monitor.
🖥️ System Status
System Uptime
11 days, 21 hours
Page File Usage
59.7 GB / 101.7 GB
Power Plan: Ultimate Performance
🌐 NETWORK DIAGNOSTICS — Online Gaming Readiness
Packet Loss • Latency • DNS Resolution • Connection Stability
✅
NETWORK OPTIMIZED
Your network is performing excellently with minimal packet loss and fast DNS resolution. You're ready for competitive online gaming with stable connections.
Packet Loss
0.4%
✅ Game Ready
Slow DNS
—
No data
TCP Sessions
1,321
5 retransmits
Connection Fails
0
✅ All connected
🔗 TCP/IP Stack — HEALTHY
Connections:1,321
Retransmits:5
Loss Rate:0.4%
Failures:0
🌐 DNS Resolution — NO DATA
Total Queries:0
Slow (>1s):0
Avg Latency:0ms
Failures:0
🔥 Top Talkers — Throughput by Process
Which processes moved the most data during capture, split by protocol (TCP vs UDP)
Process
Sent
Received
TCP
UDP
Total
Avg Rate
Diablo IV.exe
3.1 KB
25.9 KB
29.0 KB
0.0 B
29.0 KB
160.4 B/s
SteelSeriesGGEZ.exe
4.4 KB
1.8 KB
6.2 KB
0.0 B
6.2 KB
34.5 B/s
Agent.exe
3.8 KB
144.0 B
3.9 KB
0.0 B
3.9 KB
21.6 B/s
Battle.net.exe
144.0 B
3.8 KB
3.9 KB
0.0 B
3.9 KB
21.6 B/s
SteelSeriesGG.exe
1.4 KB
1.6 KB
3.0 KB
0.0 B
3.0 KB
16.6 B/s
SteelSeriesGGClient.exe
837.0 B
1.8 KB
2.7 KB
0.0 B
2.7 KB
14.7 B/s
SteelSeriesEngine.exe
520.0 B
1.5 KB
2.0 KB
0.0 B
2.0 KB
11.1 B/s
SteelSeriesPrism.exe
0.0 B
485.0 B
485.0 B
0.0 B
485.0 B
2.6 B/s
ℹ️ TCP vs UDP — and why your game may not top this list.
Most online games carry their real-time gameplay over UDP, which is connectionless and low-latency: a dropped packet is simply skipped rather than re-sent, avoiding the stalls that TCP's retransmit-and-wait behaviour causes during fast action. TCP is used for launchers, patch downloads, login/auth, text chat, web, and background telemetry. As a result, the heaviest TCP talkers are usually background apps (overlays, updaters, browsers) rather than the game itself — and a mostly single-player session can show very little network traffic at all.
Deep Analysis & Root Cause
Arbiter verdict · AI insights · correlations · root-cause tree
Arbiter Gaming Verdict
Confidence: MEDIUM
⚠️ MINOR CONCERNS DETECTED - GPU THERMAL LIMITING
🎮 GPU at Maximum Load: GPU at Maximum Load (affects FPS)