Windows 10 Insider Preview Fast Build 19608.1006 - April 17 Insider

DOWNLOADING ALL OVER AGAIN AFTER COMPLETE DOWNLOAD!!! Seems like Windows Update is going backward. Good gosh all mighty.

Still issues with audio on the Toshiba. Will run with audio disabled for a while to see if it crashes.

Still have the sound issue with the built-in Windows sounds.

Berton said:

Still have the sound issue with the built-in Windows sounds.

Same here. Disabling audio drivers didn't work. Froze so left it alone a while and GSOD with DPC Watchdog Violation error showing. Running sfc in safe mode. Most probably will have to roll back to the working version again.

IownAmoneyPit said:

I still have the same problem as last build 19603 with garbled sound and the whole computer locks up after I try to open a webpage or two.

Edit: Tenforuums seems to work fine but If I go to "The Weather Network" the machine immediately locks up and if I wait a couple of minutes I will get a GSOD (DPC WATCHDOG VIOLATION)

I'll have to revert back to build 19592 (Macrium Image) to await a fix and hope this gets acknowledged as a known issue between now & next build.

Edit 2:

I have submitted this to the Feedback Hub under "Garbled sound and the whole computer locks up after I try to open a webpage or two (Builds 19603 & 19608)" you can use the recent posts filter to view this feedback.

Uhoh! Well, I’m in the last phase of installing on laptop on which I have had this issue, so we’ll see if I have the same issue again. If so, I’ll be rolling it back again. No since having code that prevents major functionality—freeze ups. Garbled sound can be switched off but freeze ups are not acceptable.

Fabler2 said:

Same here. Disabling audio drivers didn't work. Froze so left it alone a while and GSOD with DPC Watchdog Violation error showing. Running sfc in safe mode. Most probably will have to roll back to the working version again.

Same here. System froze after a few minutes. And disabling sound systems did not correct issue. Am restoring previous build that worked. @IownAmoneyPit and @Berton same issues as before with last 2 builds. Returning to functional build to wait till the problem is fixed.