hold on, what’s your chipset? and a 105 unknown devices seems like a lot for a system?
you should complete the windows update and reboot several times up until you are current on 1703
without installing ANY 3rd PTY drivers
anything up to Z277 is natively supported by Windows, this should not happen.
Is your system OC’d? did you reset your BIOS to optimum defaults?
What installer are u using for windows? you can create the most recent installer by just running the media creation tool
almost every month there is a new version of the installer.
We WILL solve this, it just takes cautious steps in order to make sure we don’t overlook anything, step by step
It is a 1703 installation off of a USB device. This is the X299 chipset. Update will/has installed the drivers on previous installs as I stated. It also installs the nvidia driver through update.
ok good, so you install 1703, run all the updates and do the reboots and once there is nothing more in windows update for you, you still have several unknown devices?
The I would recommend to install the above intel chipset installer. It will trigger different windows update catalogues and you will get the missing updates incl. the 3.84.x Nvidia driver.
once you have no longer unknown devices in the device manager, I would install C9 and run with internal audio (generic ASIO) and see if that survives longer than 5 mins, it’s just for testing purposes
if this survives, change to RME.
no, to be clear. Windows updates the chipset drivers once I connect to the internet. In my case through wifi, which works automatically without additional driver support. The usb installer does not contain any 3rd drivers from intel or anyone else. Just so we’re on the same page…Thanks again by the way!!! much appreciated
So, if we decide that I should let the microsoft update server carry on, all of those drivers get installed essentially in one shot. Wouldn’t this put me in the same situation with regards to differentiating the problem driver?
I did this very thing on a previous fresh install… no good.
I’m going to try it again since I’m already here…Now Iv’e already installed Cubase 9 and the realtek audio driver, generic asio driver and no crashing. I also have the mpk249 plugged in. its showing up in the device manager just fine.
Looks like there’s no need…I just went back and launched Cubase 9 on my fully built partition and its working. Its playing in the background as I type this post. can’t piss it off. Changing audio drivers and mashing on keys. Nothing. This is great, but what???
I cannot explain this. maybe an update came through from windows
Oh i know, I’ll just startup Live and run that on the the uad thunderbolt driver while ALL OF THE OTHER STUFF IS STILL GOING ON!!! Don’t mind me I forgot to turn on the UAD Apollo. No sweat, just turned it on and audio is blasting!!! Can’t hear myself think…
I will not understand this clearly…I’ll keep updating on this over the next few days. Thanks for just being there. Seriously, It was getting lonely…
Now that I think about it, I did disable all of the speed stepping and power saving bios features I could find last night while tweaking on the asio driver. I’ll go back in a bit and turn it all back on to test. That is a big deal and I should have considered that…
I’m not a troll and I’m not your pal. Disabling any type of power saving features is one of the first things to do when setting up a new system for DAW use. I wasn’t trying to be a jerk (it just comes naturally ). Actually, I was getting ready to make a thoughtful and courteous reply until I noticed the edit to your post. I hope things continue in a positive fashion for you.
). Actually, I was getting ready to make a thoughtful and courteous reply until I noticed the edit to your post. I hope things continue in a positive fashion for you.