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

Tools & Diagnostics

This page is the other half of DAW Tuner. The generator script helps Windows behave better for real-time audio; these tools help you verify what the machine is actually doing under load.

Use these when you hear crackles, see unexplained CPU spikes, get GUI stutters, or have a DAW that simply feels unstable.

Quick jump
  • LatencyMon — for crackles, pops, dropouts, and DPC / ISR latency.
  • HWiNFO64 — for thermals, throttling, and falling clocks under load.
  • Process Lasso — for process priority, background junk, and controlled testing.
  • Event Viewer — for DAW crashes, vanished apps, and faulting modules.
  • Simple troubleshooting flows — for deciding what to check first.

LatencyMon DPC / ISR latency

Use LatencyMon when you hear crackles, pops, or dropouts even though the DAW’s CPU meter does not look terrible. It helps identify bad driver behavior, especially around network, Wi-Fi, GPU, storage, and power-state transitions.

Use it when

  • Playback or recording has random clicks or crackles.
  • The audio engine stops even though overall CPU looks reasonable.
  • The machine gets worse after wake-from-sleep, long uptime, or lots of window switching.

Step-by-step

  1. Close background-heavy apps you do not need for the test.
  2. Launch LatencyMon as Administrator.
  3. Click Start.
  4. While it runs, use the system like you actually would:
    • play a real DAW session
    • move the mouse
    • open plugin GUIs
    • switch windows
  5. Let it run for at least 5 to 10 minutes.
  6. Check the Main tab for the overall suitability message.
  7. Then check the Drivers tab and sort by Highest execution (ms).
Rough interpretation
Under 500 µs peaks is usually workable for very low buffer sizes.
500 to 2000 µs is more borderline and depends on session load and buffer size.
Over 2000 µs means you should expect trouble at low buffers and should inspect the driver list closely.
A good LatencyMon result does not prove everything is perfect. It only tells you that obvious real-time driver latency problems did not show up during that test window.

HWiNFO64 Thermals & throttling

Use HWiNFO64 when the machine starts out strong and then gradually falls off: rising CPU meters, laggy plugins, hot fans, or reduced responsiveness over time.

What you are checking

  • CPU package and core temperatures
  • clock speeds under sustained load
  • thermal throttling or power-limit behavior

Step-by-step

  1. Start HWiNFO64 and choose Sensors-only.
  2. Reset the min/max values before testing.
  3. Open a project that is actually demanding for your machine.
  4. Let it play for 10 to 15 minutes while you work normally.
  5. Check:
    • CPU temps
    • core clocks
    • thermal throttling flags
    • power limit exceeded flags
If clocks drop hard or throttling appears under sustained work, no Windows tuning script is going to solve that by itself. That points more toward cooling, power limits, boost behavior, or hardware configuration.

Process Lasso Process priority & CPU affinity

Process Lasso is optional. It can help you test whether background tasks are getting in the way, but it should be used with restraint.

What it is good for

  • keeping your DAW at High priority
  • pushing obvious background junk lower
  • testing whether one process is interfering with audio work

Safe, simple setup

  1. Launch Process Lasso.
  2. Find your DAW executable in the process list.
  3. Set the DAW to Priority class → Always → High.
  4. For obvious non-audio background apps, consider Below Normal or Low.
  5. Avoid fancy affinity rules unless you are solving a specific, repeatable problem.
Think of Process Lasso as a controlled testing helper, not as the foundation of the tuning strategy. Keep changes simple, readable, and reversible.
If Process Lasso fixes a problem, that does not automatically mean it should stay deeply involved forever. It may simply be revealing that one background process or one driver is the real problem.

Windows Event Viewer Crashes & hangs

If your DAW or plugin host just vanishes, freezes, or crashes with little explanation, Event Viewer often records the faulting module that caused it.

Quick crash investigation

  1. Press Win + X and open Event Viewer.
  2. Go to Windows Logs → Application.
  3. Use Filter Current Log… and check Error and Critical.
  4. Reproduce the crash if possible.
  5. Look for entries from Application Error or similar sources.
  6. Read the Faulting module name and the application path.
If the same plugin DLL or driver module keeps showing up, treat that component as suspect even if the rest of the machine seems healthy.

Simple troubleshooting flows

When to start with which tool

  • Random crackles at any buffer size → start with LatencyMon.
  • Starts fine, gets worse over time → start with HWiNFO64.
  • DAW disappears or crashes → start with Event Viewer.
  • Everything feels busy when other apps are open → use Process Lasso as a controlled test.
Practical rule
Do not change ten things at once. Change one variable, test it, and keep notes so you know what actually helped.