Help... Audio Drop Out Detected Error and Peak

CPU : Intel i7 - 13700KF

GPU : GeForce RTX 3070

RAM : 64Gb

Cubase 13

Audio Interface : Topping E2X2 OTG

POWER : 1000W

44100 / 256

When I run my heaviest project,
CPU and RAM usage are as follows:

Even though it’s not at all demanding, it always peaks and the sound cuts out.

And when I record, I get an “Audio Drop Out Detected” error.

As you can see from the audio performance, playback is at that level, but then it suddenly peaks, and it seems to happen randomly.

I tested the buffer size at 512 and 1024, but the same thing happens.

I’m curious to know why.
This has been preventing me from working properly lately.

Look at your individual core loading in windows recourse monitor. You may have high use of a single core and you only need to overload one core to get dropouts.

If it’s not that then you might try to run latencymon and see what it reports.

It’s probably not a core problem.

I ran latencymon to check, and found that a significant amount of delay was occurring in a file called wdf01000.sys. I’ve tried everything but nothing works.

Could it be related to the CPU’s E-CORE?

The most likely cause of a wdf01000.sys issue is an outdated audio driver. Try uninstalling all audio drivers that you don’t absolutely need and reinstalling only the necessary ones in their latest versions.

wdf errors are usually pretty non specific….something else wil be the cause. But what does a significant amount mean to you…..just say if it passes or fails??

Confirm you use Steinberg power scheme or you have set windows power scheme to high performance or ultimate performance.

Confirm you made the usual tweaks for usb audio if you use usb interface….disable selective suspend and untick turn off this device to save power….in device manger for every usb hub.

Confirm if you have Nvidia gfx that you use the studio driver or have at least made the prefer maximum performance tweak.

Post the drivers tab sorted by highest execution if ll that is done and you still get drops

What ASIO driver are you using with that interface?

Thank you for your kind reply.

The cause of the problem was the E-CORE feature supported by the Intel CPU.

When I monitored the usage of each core with Latencymon,
I suspected that the problem was caused by E-CORE, as a specific core wasn’t working properly, and that was correct.

I don’t know the specific reason, but it seems that enabling E-CORE causes certain cores to idle, causing problems with program execution.

After disabling E-CORE, I increased the sample late from 256 to 128, but no peaks occurred.

I encourage everyone struggling to figure out the cause to try disabling E-CORE.

Thank you for your reply.

The problem was the E-CORE feature supported by the Intel CPU.

Disabling E-CORE completely resolved the issue.

1 Like

I’m not sure, but the cause of the problem was the E-CORE feature of the Intel CPU.