Home | How It Works | Tools & Diagnostics | DAW Guides | Changelog | Feedback
Version: 0.3.0

Tools & Diagnostics

This page is the “other half” of DAW Tuner. The generator script sets Windows up for real-time audio; these tools tell you whether the machine actually behaves.

All of these tools are free (or have free versions). Use them when you hear crackles, random CPU spikes, or see GUI stutters.

LatencyMon DPC / ISR latency

Use LatencyMon when you hear crackles, pops, or dropouts even at safe CPU levels. It measures DPC/ISR latency and shows which drivers are misbehaving.

When to run it

  • Random crackles during playback or recording.
  • Audio engine stops even though CPU is low.
  • Problems that get worse over time (after wake from sleep, long uptime, etc.).

Step-by-step

  1. Close background heavy apps (browsers, games, streaming).
  2. Launch LatencyMon as Administrator.
  3. Click Start, then:
    • Play a real DAW session.
    • Move the mouse, open plugin GUIs, switch windows.
  4. Let it run for at least 5–10 minutes.
  5. Check the Main tab:
    • If it says “appears suitable for handling real-time audio” → Good baseline.
    • If it warns that the system is not suitable → check the Drivers tab.
  6. On the Drivers tab:
    • Sort by Highest execution (ms).
    • Look for repeat offenders (network, Wi-Fi, GPU, storage).
Interpretation (rough):
< 500 µs DPC peaks – usually OK for 64–128 sample buffers.
500–2000 µs peaks – borderline; fine for 256–512 samples, risky at 64–128.
> 2000 µs – expect dropouts at low buffers; look at driver list.

HWiNFO64 Thermals & throttling

Use HWiNFO when performance starts strong and then gradually falls off: CPU meters climb, fans spin, or plugins start lagging.

What you’re checking

  • CPU temperature (package & individual cores).
  • Clock speeds under load.
  • Thermal throttling or power limits being hit.

Step-by-step

  1. Start HWiNFO64 and choose Sensors-only.
  2. Press the reset (clear min/max) button.
  3. Open your DAW and a heavy project (virtual instruments, plugins, multiple tracks).
  4. Play the session for 10–15 minutes while working as you normally do.
  5. Alt-tab back to HWiNFO and check:
    • CPU temps – ideally under ~85°C for sustained loads.
    • Core clocks – should stay near turbo under load.
    • Any flags like “Thermal Throttling: Yes” or “Power Limit Exceeded”.
If you see Thermal Throttling or clocks dropping under load, DAW Tuner can’t fix that with software alone – you may need better cooling, lower overclocks, or less aggressive boost.

Process Lasso Process priority & CPU affinity

Process Lasso is optional but powerful. It lets you:

  • Keep your DAW at High priority and “Performance mode”.
  • Push background junk to lower priority automatically.
  • Limit misbehaving processes to specific cores.

Safe, simple setup for DAW use

  1. Install Process Lasso and launch it.
  2. Find your DAW executable in the process list (e.g., Studio One.exe, reaper.exe).
  3. Right-click the DAW process:
    • Priority class → Always → High (not Realtime).
    • CPU priority → Performance mode (if available).
  4. For obvious background apps (cloud sync, updaters, etc.):
    • Set Priority → Always → Below Normal or Low.
  5. Don’t overdo CPU affinity unless you have a specific reason; most DAWs like to see all cores.
If you already use DAW Tuner’s power-plan and MMCSS tweaks, Process Lasso should be seen as a gentle helper, not a replacement. Keep changes simple and reversible.

Windows Event Viewer Crashes & hangs

If your DAW or plugins just vanish (no error, just gone), Event Viewer often records exactly which module blew up.

Quick crash investigation

  1. Press Win + X → select Event Viewer.
  2. On the left, expand:
    • Windows Logs → Application.
  3. In the middle pane, click Filter Current Log…:
    • Check Error and Critical.
  4. Reproduce the crash, then check for entries with:
    • Source like Application Error.
    • Faulting application path pointing to your DAW.
  5. Read “Faulting module name” – this can identify a specific plugin DLL or driver.
If the same plugin DLL shows up repeatedly as the faulting module, treat that plugin as suspect, even if everything else seems fine.

Putting it together: simple troubleshooting flows

  • Random crackles at any buffer size → run LatencyMon.
  • Starts OK then degrades over time → HWiNFO for temps & throttling.
  • DAW vanishes / crashes → Event Viewer for faulting module.
  • Everything feels “busy” when you open a browser / video → Process Lasso to demote background tasks.