Problems with Windows 10 and Komplete Audio 6 Mk 1 driver
Answers
-
I know that you could do that in the registry if you wanted to. I’d just prefer to have it done by someone who is an expert and knows exactly what they’re doing.
Next update:
What I also noticed yesterday is that under "Windows -> Sounds -> Playback", both 'Main Output' and 'Output 3/4' were set as default playback, which actually isn’t possible, because you can only set one of them as default playback. How, when and why that happened – no idea. That means both had the white tick on the green circle. I’ve now set it so that only 'Main Output' is selected as the default playback again. Let’s see if that’s the solution.
0 -
Next update: I was still researching for what caused this problem. Then I noticed that in the UEFI BIOS some things were not configured correctly for recording studio usage. Maybe the technician forgot to deactivate these things. On the Steinberg website you can read what you have to do. Unfortunately, I just have the link with the German text for you: [English language link inserted by Moderator]
https://helpcenter.steinberg.de/hc/en-us/articles/360008589880-Windows-How-to-set-up-and-optimize-a-Digital-Audio-Workstation
In a nutshell: You have to deactivate all CPU energy saving things and in Windows things like synchronisation (e. g. OneDrive). According to Steinberg, it can cause heavy problems for recording studio / audio usage.
That's what I said, the reason of all these problems, DPC Watchdog Violation bluescreens and audio driver disappearing, could have been caused by something else.
Since then the system works fine. I'll see how it goes from here.0 -
in the UEFI BIOS some things were not configured correctly for recording studio usage.
On the Steinberg website you can read what you have to do.
In a nutshell: You have to deactivate all CPU energy saving things and in Windows things like synchronisation (e. g. OneDrive). According to Steinberg, it can cause heavy problems for recording studio / audio usage.
That's what I said, the reason of all these problems, DPC Watchdog Violation bluescreens and audio driver disappearing, could have been caused by something else.
Since then the system works fine. I'll see how it goes from here.
@Jeremy_NI , one for your note book..
0 -
Next update: Hey guys, this seems to be the solution. Normally, if I booted the system on the next day often the audio driver "disappeared" after half an hour / one hour. Since yesterday, when I found out that the UEFI BIOS were not configured correctly for recording studio usage and when I changed it as recommended by Steinberg it works. In addition to that the quiet noises I had on the left speakers disappeared.
If you will not hear anything anymore from me regarding this topic you can assume that this was the reason for that problem.0 -
@PoorFellow and @sylpre Thanks for sharing.
0 -
Update: Now I can tell you this really solved this problem. Not a single audio driver disappearance, no bluescreen / DPC Watchdog Violation crashes anymore. After 6 month, I've found what caused this problem. Nonetheless I think that one of the Windows updates last year was additionally the 2nd problem and that this was the thing + CPU energy saving modes and OneDrive synchronisation didn't "understand" each other very well. And, as I said, no more noise on the left speakers anymore.
1 -
Last update to this topic (I think): Yesterday, I had a single audio driver glitch after starting up the audio workstation. I think it was because the day before Windows downloaded another update. After that I have deactivated the update function in the Windows Dienste (German for Services. I don't know how it is called in the English Windows version). This was the only one audio driver glitch I had since I have deactivated the CPU energy saving mods in the UEFI BIOS and OneDrive synchronisation. At least I can say the system is extremely much more stabil now. No DPC Watchdog Violation bluescreen crashes anymore. Before that I had audio driver glitches at least 2 to 6 times a day, including DPC Watchdog Violation bluescreen crashes at least 1 to 3 times a day.
A few weeks ago, I spoke with the Steinberg support. They told me that they have the same problems with Microsoft as well, regarding the updates and the problems caused by the updates. They got in contact with Microsoft to speak about that but Microsoft didn't respond. Obviously, recording studios and everything related to that isn't really important to Microsoft. Sad but true.0 -
We could all start to write to Microsoft one by one about those issues.
Maybe showing them users are affected (and not silent) will shift our importance in their book 😏
(Yes… I know… I’m an optimist…😂)
0 -
I dont think so 😜
1 -
Next update: Today I had 2 audio driver dropouts but no DPC Watchdog Violation bluescreen crashes anymore. I checked the Steinberg website again (https://helpcenter.steinberg.de/hc/de/articles/360008589880-Windows-Einrichtung-und-Optimierung-einer-DAW) and I became aware of the Intel Link Power Management. I deactivate it and I will see how it works and if this can stop the rest of the few audio driver dropouts. I'll check it for a couple of days and will let you know how it goes.
0 -
Next update: Yesterday, I changes the sample rate from the audio interface from 192 samples to 256 samples and changed the USB buffer size from 1 to 4 ms. Today, I had not a single one audio driver dropout. I think that was the rest of the solution. I'll keep an eye on it and will check it out for the rest of the week and will give you (maybe) a last update at the end of this week.
0 -
Last update: I still have audio driver dropouts but less than before. The DPC Watchdog Violation bluescreen crashes disappeared. That's an significant advantage. Yesterday, I had no audio driver dropbout but today I got two. It's not nice but much better than before. If I should find the whole solution for this problem I'll let you know.
0 -
What is the USB layout on this machine? If you are using the audio interface on a USB port that is shared - either with system components OR other physical devices - you could be chasing ghosts forever.
Like I suggested for another user earlier this week - look up a free utility called USBTreeView ( from Uwe Sieber) that will give a nice visual representation of all USB ports and if they are shared etcYou need your audio interface standing alone on it own unique USB port to really isolate its traffic and potential for more dropouts.
VP
0 -
Thanks for the tip. I'll check that. I've found some more tips in a YouTube tutorial about optimising the audio workstation for DAWs.
https://www.youtube.com/watch?v=Nj20gcQ1nTQ0 -
PS: I can't tell you what the USB layout is. Or do you mean where I plugged the audio interface? I plugged it directly into one of the PC USB ports on the back.
0
Categories
- All Categories
- 18 Welcome
- 1.6K Hangout
- 66 NI News
- 863 Tech Talks
- 4.4K Native Access
- 17.6K Komplete
- 2.1K Komplete General
- 4.6K Komplete Kontrol
- 6.1K Kontakt
- 1.6K Reaktor
- 398 Battery 4
- 894 Guitar Rig & FX
- 456 Massive X & Synths
- 1.4K Other Software & Hardware
- 6.2K Maschine
- 7.9K Traktor
- 7.9K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators