r/rewasd

So i wanted to get into apex lately but i know that the game wont let me in because i have rewasd installed. So what did you do to enhance compatibility with ea games in version 9.4? Is it another detection bypass or did you come to some agreement with ea? I hope it is the latter since im tired of this cat and mouse game from yall. I really wish there could be some time-proof if a bit compromised solution to ea/rewasd beef.

Also if i dont need rewasd to play apex anyways (i use k&m and dont cheat) do i need to use the compatibility mode? Or can i just shut down the app using task manager? Or do i need to use the emergency driver disable option as well....?

My Discord account was compromised and used to send crypto spam, which got me removed from several servers, including reWASD 😞

Hi, I apologize if any of this is unclear as I'm not particularly adept with the software or controller mapping in general

I have a Razer BlackWidow Elite from several years ago, which, like many other Razer keyboards has suffered the loss of a working volume knob. It often will randomly adjust the computer volume whenever it feels like it. I have been attempting to use reWASD to unbind these functions so that this does not occur, as I use an audio interface to control my computer's output volume anyway. reWASD seems to detect the Volume Up and Down inputs, but when I select to mute them and apply the changes, nothing happens and I still get the junk volume adjustments from the broken wheel. I am not sure whether this is an error of the program or the user (probably the latter) but I have not been able to figure this out after several sessions of trying.

In the event it proves useful to anyone trying to help me with this, I have the keyboard configured in a group along with my mouse, which is a Razer Basilisk V3 X Hyperspeed. The mapping profile is set to run along with Wallpaper Engine, which is essentially running whenever my PC is on, since I couldn't figure out how (if it's possible) to just have it globally remap the keyboard across any program. I do also have a PS4 controller plugged in at all times although it's not part of the group mapping. I have no idea if any of this makes a difference towards resolving this problem but now you know just in case.

I appreciate if anyone is able to provide some insight into getting this to work. Thanks in advance

Every time I hit Shift or Control, I can't move my character or summon my sparrow. I do not have sticky keys or any of that on, and I've already changed keyboards off said keys. Update: I also can't hit Caps Lock or Ctrl, or else my movement locks in place and WASD is useless. I also can't tab out without WASD bricking.

Keyboard:Steelseries Apex Pro TKL Mouse:Lamzu Maya X 1000hz polling Moniter: Samsung Odessy G9 5120px1440p NATIVE set to 3440x1440

**TL;DR:** After weeks of troubleshooting audio crackling/popping during gameplay, I discovered reWASD's driver was causing severe DPC latency spikes that ultimately resulted in audio buffer underruns during combat. Disabling reWASD completely resolved the issue. Posting to warn others and ask the devs to investigate.

## The Problem

For weeks, I'd been experiencing audio crackling and popping during gameplay in both WoW Retail and Classic. The pattern was consistent:

- Audio would be fine for the first 20-30 minutes of play

- Crackling would start, especially during combat

- It would progressively worsen the longer I played

- Happened on both HDMI audio through my TV AND wired headphones via 3.5mm motherboard jack

- Affected both games equally

LatencyMon was showing DPC latency spikes of 6,000-8,000+ μs (yes, microseconds — that's catastrophic for real-time audio).

## My System

- Ryzen 5 5600X, ASUS TUF B550-PLUS (BIOS 3636)

- RTX 3070, 16GB DDR4-3200

- Intel 660p NVMe SSD

- Windows 10 Home 22H2

- Xbox Elite Controller via reWASD (back paddles + Xbox button → Win+H remap)

## What I Ruled Out Before Finding the Cause

This was a marathon. I went through:

- BIOS power settings (C-states, Core Performance Boost — disabled, then re-enabled when reverting)

- NVIDIA driver versions (rolled back from 596.49 to 552.44 via DDU)

- AMD chipset drivers (updated from 5 years old to current)

- HDR settings (was on, turned off — helped a little)

- TP-Link USB Wi-Fi adapter (Realtek rtwlanu.sys — switched to iPhone tethering)

- Brave hardware acceleration

- Logitech Gaming Software (leftover from old hardware)

- DirectX 12 → DirectX 11

- Windows audio enhancements (disabled)

- MSI mode for GPU (already enabled)

- Windows Memory Diagnostic (passed)

- DISM and SFC (found and fixed corrupted system files)

- Microphone + Windows Speech Recognition (disabled completely)

- All WoW addons (disabled, tested clean for 39 min — but no combat)

- Switched audio paths (HDMI → 3.5mm onboard audio)

Nothing fully fixed it. Every test still produced crackling within 24-30 minutes of gameplay, especially during combat.

## How I Found reWASD Was the Cause

Late in the troubleshooting process, I casually mentioned to a friend helping me debug that I use reWASD for my Elite controller's back paddles and to map the Xbox button to Win+H for voice-to-text. I'd had reWASD running through every single test. It was the invisible constant.

I closed reWASD from the system tray and ran a normal Classic WoW session — addons enabled, combat, controller, everything normal — for **1 hour 19 minutes**. Zero audio crackling.

## The LatencyMon Numbers Tell the Story

**With reWASD running (typical results across multiple tests):**

- Highest interrupt-to-process latency: 6,400-8,400 μs

- ntoskrnl.exe DPC: up to 3,834 μs

- Wdf01000.sys consistently dominant in DPC count

- Audio crackling within 24-30 minutes

**With reWASD closed (79-minute test):**

- Highest interrupt-to-process latency: 320 μs

- ntoskrnl.exe DPC: 338 μs (91% reduction)

- Wdf01000.sys still elevated but no audio impact

- Zero audio crackling

One particularly telling moment: the DPC bar in LatencyMon visibly spiked the moment I interacted with the reWASD exit confirmation dialog. The driver responds to interaction in real-time.

## Why This Likely Happens

reWASD installs a kernel-mode driver to intercept and remap controller input. It hooks into the Windows Driver Framework (Wdf01000.sys). Under sustained gaming load — especially during combat when controller inputs are constant and rapid — its DPC handling appears to compete with real-time audio processing in a way that causes audio buffer underruns.

This would explain why:

- Combat triggers it (more input events to process)

- Both Retail and Classic are affected (reWASD runs system-wide)

- The 24-30 min pattern (cumulative driver state)

- Switching audio paths didn't help (problem is upstream of the audio output)

- Nothing else I tried fixed it (was treating symptoms)

## To the reWASD Devs

I genuinely like reWASD and want to keep using it — the back paddle remapping is great and the Xbox button → Win+H mapping is something nothing else really does as cleanly. But this DPC behavior under sustained gaming load is a real issue. I'd love to see:

- Investigation into the WDF driver's DPC handling during high-input scenarios

- Possibly an optional "gaming mode" with reduced polling/processing overhead

- Documentation acknowledging this issue and recommended mitigations

I'm happy to provide additional LatencyMon data or test pre-release builds if it would help.

## How to Check if This Is Your Issue

If you're experiencing audio crackling, popping, or buffer underruns during gameplay (especially during combat or high-input scenarios) and you use reWASD:

1. Download LatencyMon (free from Resplendence)

2. Run it during a gaming session that normally produces the crackling

3. Check the Drivers tab for high DPC counts on Wdf01000.sys

4. Test by completely **uninstalling** reWASD (not just closing — the driver stays loaded)

5. Play normally and see if the issue resolves

## What I'm Doing Now

For anyone in the same boat who needs alternatives:

- **Xbox Accessories app** (free from Microsoft) handles back paddle remapping at the controller firmware level — no Windows driver involved

- **AutoHotkey** or **PowerToys Keyboard Manager** can handle controller-button-to-keyboard-shortcut mappings at user level instead of driver level

It's a tradeoff but at least I can actually play games now without my ears bleeding.

Has anyone else run into this? Would love to know if this is a widespread issue or something specific to my hardware combination.