The short answer
Confirm 1002, leave/rejoin the call, then fully restart Discord if needed. If it persists, record the original suppression setting and compare original → off → original while keeping the mic and phrase unchanged. Judge the code, intelligible speech and background noise separately.
Different symptom or still not fixed? Find the next check →Key facts
- Official first checks
- Leave/rejoin, then fully restart Discord
- Controlled comparison
- Original suppression → off → original; keep other settings fixed
- Different notification
- Krisp automatically turning off under CPU load is not itself proof of 1002
Find your symptom
Start with your symptom. Skip steps that do not apply to your setup.
| What you see | What to check | Go to |
|---|---|---|
| 1002 has just appeared | Rejoin and fully restart before changing settings. | Step 1 |
| Off clears the code and speech arrives | Compare once after restoring the original setting. | Step 2 |
| Original setting reproduces 1002; off allows calls | Use the working state temporarily and inspect conditions/update. | Step 3 |
| Code clears but noise or clipped speech remains | Assess audio quality separately in a quieter setting. | Step 3 |
| Both enabled and disabled states show 1002 | Compare client/version conditions, not only suppression. | Step 3 |
| RTC Connecting/No Route or a silent joined call | Separate connection, microphone and output failures. | Step 4 |
Fixes, in order
Continue this issue
Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.
Step 1｜Confirm 1002, rejoin and fully restart in that order
These are Discord’s explicit first checks for its noise-canceller error.
Time: Compare one change at a time
- Record the number, time and whether it began on call entry or during gaming. Leave and rejoin the same call.
- Check whether 1002 returns and separately whether the other person hears you. If the call works without recurrence, stop changing settings.
- If it continues, quit Discord from the Windows tray. Closing/minimizing a window may leave the app running.
- If needed, use Ctrl+Shift+Esc to confirm identified Discord processes have ended, then reopen and compare the same call. Continue to Step 2 only if the issue remains.
Results that did not fix the problem help the next reader too.
Step 2｜Compare original, off and original suppression settings
Keep input device, volume, sensitivity and echo cancellation fixed so the comparison concerns suppression.
Time: Compare one change at a time
- Open User Settings → Voice & Video → Noise Suppression. Record the exact current choice, including Krisp or another available mode.
- With the original setting, say a short repeatable phrase such as “Audio check: can you hear the end of this sentence?” Ask the listener about clipped beginnings/endings and keyboard/background noise.
- Disable suppression using the available off/None choice. Rejoin the same call and repeat the phrase at the same distance.
- Record three outcomes separately: 1002 present/absent, speech quality and background noise. Any example format is a recording aid, not a measured result to copy as your own.
- If off works, restore the original mode once, rejoin and compare. Keep it if normal; if 1002 returns, use the working off state and continue to Step 3.
If suppression was already off, record that 1002 occurred in that state. A mic test can inspect input when no partner is available, but cannot replace checking delivery and recurrence in a real call. Stop the test before returning to the call.
Results that did not fix the problem help the next reader too.
Step 3｜If restoring the setting reproduces the issue, narrow the conditions
That result suggests examining suppression conditions; it does not prove a broken mic or inadequate CPU.
Time: Compare one change at a time
- If calls work with suppression off, use that temporarily. Move somewhere quieter or mute when not speaking if background noise increases; do not repeatedly force the failing mode.
- Update and fully restart Discord, then repeat the controlled comparison once. If it recurs, record the version and original suppression mode.
- If it happens only while gaming/streaming, compare a call without those tasks. Inspect CPU load in Task Manager → Processes and compare after closing your own unnecessary apps.
- Distinguish a notification that Krisp disabled itself under CPU load from a displayed 1002 code. Discord documents automatic disabling, but the notification alone does not diagnose this error.
- If both suppression states fail, leave the desktop call and compare the browser on the same PC with the same mic/person. Record its site permission and actual suppression setting before reporting app-only versus both-client failure.
Browser and desktop features/settings can differ. One succeeding does not prove that identical suppression processing was compared.
Results that did not fix the problem help the next reader too.
Step 4｜If calling still fails, follow the stage that remains broken
Do not keep toggling suppression when the remaining problem is connection or input/output.
Time: Compare one change at a time
- For RTC Connecting or No Route, the connection has not reached a useful voice comparison. Follow the relevant connection guide.
- For a single server/channel, ask its administrator to inspect Connect/Speak permissions and Server Mute.
- If you hear the other person but they do not hear you, inspect physical/Discord mute, input selection and mic testing using the microphone guide.
- If your speech arrives but you cannot hear them, check deafen, output and individual volume using the incoming-voice guide.
Results that did not fix the problem help the next reader too.
Avoid
- Do not label every noisy or clipped voice as error 1002.
- Do not change suppression, sensitivity, device and volume simultaneously or bypass channel restrictions.
Important cautions
- For support, include the code screen, OS/app versions, devices, original mode, original/off/original results, game-load comparison and browser result.
- Report any residual clipped speech separately even if the code clears. Do not describe unavailable call comparisons as successful.
FAQ
Must I turn suppression back on?
No. If speech is clear in a quiet setting without it, that can be usable. If restoring it reproduces 1002, keep the working state temporarily and recheck after an update; ask the listener about background noise.
Will my Krisp setting remove another person’s background noise?
Your setting filters your outgoing audio. The other person must inspect their own microphone path, so use a listener to judge your comparison.
Is Krisp automatically switching off always 1002?
No. Discord documents automatic disabling under high CPU load to preserve voice performance. Record whether the actual error number appeared or only the notification.
Is the issue fixed when 1002 disappears?
Also confirm that intelligible speech reaches the listener without disruptive noise. Follow connection or input/output checks if those failures remain.
Sources
English adaptation of the Japanese guide with the same cause IDs, action sequence, cautions and source scope. Official Discord, Microsoft and relevant browser documentation support the checks. Comparison examples are editorial guidance, not measured results. Test with a willing participant, keep recordings private and restore unhelpful changes.
Discord: audio and video error codesDiscord: voice and video troubleshootingDiscord: Krisp controls, voice quality and high-load behaviorDiscord: contact supportDiscordJapanese version of this page