Problems with Windows 10 and Komplete Audio 6 Mk 1 driver
Answers
-
Yes - that is exactly what I mean. That port you are plugged into - could have all sorts of shared action with other ports on board - leading to contention, blocking and eventually audio artifacts.
Hence my suggestion for the USB tool - you need to make sure the audio interface is plugged into the USB port with the least amount of traffic - ideally all to itself.
Only using the USBViewTool can tell you which one of your available ports - is the best option.
VP
0 -
Thanks for the info. With the help of ChatGPT I was made aware to have a look at the hidden device drivers in the Windows Device Manager. And the Komplete Audio 6 WDM audio driver was actually displayed twice. That shouldn't be the case. This can of course cause conflicts. I then disconnected the audio interface and uninstalled the two entries. I then restarted the computer and checked whether the two entries in the Device Manager had disappeared. Then installed the latest Komplete Audio 6 Mk 1 driver (4.2.0). Restarted the computer and reconnected the audio interface. Then check the Device Manager again to see what is there. And there is now only one entry left. Let's see if that was the problem.
So much for “My last update on the subject” :-)
1 -
PS: LatencyMon, sfc /scannow, Windows DISM, hard disk check etc. and everything else to check for system errors were all OK.
1 -
If you took a look to the suggestions in this tutorial you can find at the end a tip to adjust the audiodg.exe in the task manaager under the register card 'details'. But there is problem. 1. You just can find the audiodg.exe if you are running audio. For example a YouTube video. If you are closing the video or restarting your audio workstation the audiodg.exe disappears and Windows is resetting your settings to default.
After researching I found the Process Lasso software. The basic version is for free and it saves the settings. Then it doesn't matter if you are running an audio application or not or if you are restarting your audio workstation. It saves the settings.
I'll try it for a couple of days and let you know how it goes.0 -
Process Lasso was never needed for Windows 10.
Windows 11? Absolutely.
Been running Windows 10 here since summer 2015 and have never had any audio glitches. Or even knew what Process Lasso was until my first Windows 11 test flight in early 2024.
Your issue will eventually be found to have a different cause. Like a USB conflict.
And - have we ever determined exactly what hardware you are running? Computer? CPU? RAM?VP
0 -
Computer (custom-made), Intel Core i7, 32 GB RAM.
Yes, it could be a USB conflict because almost all of the USB ports are USB 3.0 and the Komplete Audio 6 Mk 1 is USB 2.0.
Until now I had no audio driver dropout again. A couple of minutes ago, It started to crackle for a couple of seconds and then it disappeared and runs stabil. When it started to crackle I was able to start LatencyMon. And it displayed again that the system is suitable for real-time audio.
When I'm running Nuendo, I noticed a further advantage, after installing Process Lasso. I don't have real-time audio peaks anymore. I had just few real-time audio peaks before, but enough memory and very far away from the performance limit, no matter how many performance intensive VSTs I loaded.
I'll check the USBViewTool.0 -
And this one is important to configure Process Lasso for DAWs.
https://www.youtube.com/watch?v=yrcASU9auwA&t=553s0 -
After I have set the rest of the configuration in the Process Lasso software (see the last video tutorial on YouTube I posted yesterday) I can say that today were no problems anymore. As I said before, I had no DPC Watchdog Violation bluescreens anymore but still few audio driver dropouts, but much less than before all of these adjustments. Now, when I set the priority of the Komplete Audio 6 Native Instruments Services exe from 'normal' to 'high' it runs perfect.
Process Lasso can be one part of all these adjustments you have to do to solve this problem.
Now, I really think about to change next time from Windows to Mac. Windows seemed to be a great solution for an OS in recording studios because I was working in recording studio where Mac OS wasn't a good solution but Windows / Microsoft seems to be not a good "partner" for recording studios in the future with all their stupid changes they made. I spoke with the Steinberg support who told me that they have feedback from many other recording studio with much bigger problems triggered by changes Microsoft has made on Windows. Since then, a lot of them can use just one MIDI device anymore because Windows doesn't support MIDI anymore. Really "great"! Windows is becoming a no-go for recording studios.0 -
Do you think the situation would be better with Apple?
Maybe the problems will be different ones, but, believe me… all of them cause problems…
And Apple isn’t really famous for “updates don’t cause any sort of issue”
0 -
Respectfully - it sounds like you are reacting to having a very old audio interface finally collide with the passage of time and need to blow off some steam by blaming it all on Windows.
And tools like Process Lasso have no bearing on Windows 10 whatsoever as it does not feature the poorly written thread director contained within Windows 11. But if it makes you feel better - use it.
There are literally thousands of us in here - with Windows 10 and 11, with modern interfaces and have no troubles whatsoever.
If you really think Apple is the answer, buff up that credit card and get ready for way more fun and games than you have had thus far.
We tried to help - but we can only go so far as you have seemed resistant to any additonal help.
Personally - I think there is nohing wrong with your machine at all. It is the audio interface that needs a changeout. That would be done for a couple hundred bucks and this would be done.
Good luck with your next move.
VP
0 -
With all due respect to you too: I am not at all opposed to any help. I just don't see the point in throwing away hardware just because it's “old”, even though it still works perfectly. Where is this going to lead? And I have found a solution that now works perfectly. I also didn't say that I would definitely switch to Mac later, as we had exactly the same problems with Mac in the recording studio back then. And as you should know, it's always a search for a needle in a haystack, because recording studios are complex and all systems, hardware and software, have to work together. In 25 years of working in recording studios, I've generally come across sources of error that nobody would have thought of at the beginning. In the end, it always turned out to be something else than many people thought. And it's impossible to say for sure from a distance.
1 -
"In 25 years of working in recording studios, I've generally come across sources of error that nobody would have thought of at the beginning"
Respectfully - with 25 years experience in actual recording studios - I would expect you would know exactly how a DAW workstation BIOS should be configured for audio with leaning on Steinberg articles and YouTube videos etc. I am also very certain you would also know the difference between a pro level interface vs the one that you have.
Finally - at this experience level - pretty sure this thread would not even be required. You would have easily solved this long ago without needing any additional help.
I really do hope you catch a break.
VP
0 -
It also turned out that the CPU fan speed was set to standard instead of full speed in the UEFI BIOS and that the RAM was also set to energy-saving mode. The company that assembled the studio computer really didn't do a good job, despite the fact that I sent them the requirements.
Now the computer has been running for a few days without a single problem. No more audio driver dropouts and no more DPC watchdog violation bluescreen crashes.
I think now the thread can really be closed. Everything has been said.
1 -
I really don't know what your problem is. You don't know me personally! You don't know the background and you think you have to attack me personally in your posts! I did not assemble the studio computer myself, but had it assembled by a company that apparently set the BIOS incorrectly, as I have now discovered. This company had the specifications from Steinberg and apparently did not take them into account. Then perhaps you should complain to the company and not attack me personally! Are you not quite right, or what is wrong with you?
0 -
"I did not assemble the studio computer myself, but had it assembled by a company that apparently set the BIOS incorrectly, as I have now discovered. This company had the specifications from Steinberg and apparently did not take them into account."
This information would have been very valuable to know - back in Post #1
And - my apologies if I came on strong - that was not the intent.
It is just that with a quarter century of experience as you mentioned - it is logical to assume you would probably know your way around any hardware at this point.
Glad you got it sorted.
VP
0
Categories
- All Categories
- 18 Welcome
- 1.6K Hangout
- 67 NI News
- 885 Tech Talks
- 4.5K Native Access
- 17.3K Komplete
- 2.2K Komplete General
- 4.7K Komplete Kontrol
- 6.2K Kontakt
- 1.1K Reaktor
- 404 Battery 4
- 902 Guitar Rig & FX
- 458 Massive X & Synths
- 1.4K Other Software & Hardware
- 6.2K Maschine
- 8K Traktor
- 8K 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