Scaler EQ crashes Reaper at 176400khz

I have always experienced crashes with Reaper when using Scaler EQ at 176.4k.

Here are some windows 11 logs. New Reaper.

Log Name: Application
Source: Windows Error Reporting
Date: 11/06/2026 00:00:41
Event ID: 1001
Task Category: None
Level: Information
Keywords:
User: GB-5950X\grego
Computer: GB-5950X
Description:
Fault bucket 1885622827698963368, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: reaper.exe
P2: 7.7.4.0
P3: 6a26f475
P4: StackHash_6464
P5: 10.0.26100.8328
P6: 0022b8e0
P7: c0000374
P8: PCH_91_FROM_ntdll+0x00000000001627F4
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5e185018-3a62-4962-ba33-62e28a1cbc24.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b1593aa9-b264-4a40-98e1-6a76f3713dc3.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.db22d930-14d3-4864-85d8-82d7acb702f6.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d083b823-e53b-47d8-83b2-20f6fdadb5af.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6a01f295-c6ab-444e-b43e-0b11c72fecda.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_reaper.exe_b6f3c533b470c32fc6f9f6bb639f6c5b33ed1b_70d6da33_8a1427f4-f579-430b-80dc-343ae0cedcd3

Analysis symbol:
Rechecking for solution: 0
Report Id: fb5855e0-190c-4f44-82cc-91b0f1fad658
Report Status: 268435456
Hashed bucket: 9f39de3d19c33fdb9a2b13f8a95d43a8
Cab Guid: 0
Event Xml:

1001
0
4
0
0
0x8000000000000000

176781

Application
GB-5950X

1885622827698963368
4
APPCRASH
Not available
0
reaper.exe
7.7.4.0
6a26f475
StackHash_6464
10.0.26100.8328
0022b8e0
c0000374
PCH_91_FROM_ntdll+0x00000000001627F4

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5e185018-3a62-4962-ba33-62e28a1cbc24.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b1593aa9-b264-4a40-98e1-6a76f3713dc3.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.db22d930-14d3-4864-85d8-82d7acb702f6.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d083b823-e53b-47d8-83b2-20f6fdadb5af.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6a01f295-c6ab-444e-b43e-0b11c72fecda.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_reaper.exe_b6f3c533b470c32fc6f9f6bb639f6c5b33ed1b_70d6da33_8a1427f4-f579-430b-80dc-343ae0cedcd3

0
fb5855e0-190c-4f44-82cc-91b0f1fad658
268435456
9f39de3d19c33fdb9a2b13f8a95d43a8
0

Log Name: Application
Source: Application Error
Date: 11/06/2026 00:00:39
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: GB-5950X\grego
Computer: GB-5950X
Description:
Faulting application name: reaper.exe, version: 7.7.4.0, time stamp: 0x6a26f475
Faulting module name: ntdll.dll, version: 10.0.26100.8328, time stamp: 0x0022b8e0
Exception code: 0xc0000374
Fault offset: 0x0000000000117175
Faulting process id: 0x5F0C
Faulting application start time: 0x1DCF92C0F283DEF
Faulting application path: C:\Program Files\REAPER (x64)\reaper.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: fb5855e0-190c-4f44-82cc-91b0f1fad658
Faulting package full name:
Faulting package-relative application ID:
Event Xml:

1000
0
2
100
0
0x8000000000000000

176780

Application
GB-5950X

reaper.exe
7.7.4.0
6a26f475
ntdll.dll
10.0.26100.8328
0022b8e0
c0000374
0000000000117175
0x5f0c
0x1dcf92c0f283def
C:\Program Files\REAPER (x64)\reaper.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
fb5855e0-190c-4f44-82cc-91b0f1fad658

Any update on reaper and 176k?

Wow, 176 kHz? We’ll definitely take a look. Off the top of my head, we’re not aware of many users working at that sample rate. When recording drift cars for a major video game, we used 192 kHz and 32 bit depth to give ourselves plenty of headroom without worrying about unexpected SPL spikes. Beyond specialised applications like that -or perhaps processing recordings from high-end digital microphones in spaces such as the V&A Hall - I’m curious what workflow is driving the need for 176 kHz in a DAW.

Audiophile quality recordings of acoustic instruments with analogue mics (Schoeps, B&K).

Interesting @Tristan would you mind checking this on Monday please?

At the moment, SEQ crashes when I close the GUI.

The higher sample rates make a difference on the clarity of instruments with a lot of delicate top end.

A simple test is to record a 12-string at 44.1k, and then 176k and then listen back and compare while focusing on the top end.

Hi Any update to the crash situation?

Hi @gregb We’ve confirmed it. Can’t give you any ETA at the moment but will have some news soon!