Well, I am not having any of those problems mentioned here. Sound is okay, VMware is good, Macrium still working.
But this morning out of the blue at sign in time I got a GSOD saying that "Windows Service Exception" Win32KFull.sys.
Emilcioran99, here's a copy of a post I made on December 12:In the model page is posted the Realtek Audio Driver V6.0.1.8437 and as I said at the beginig of the discussion , tried already.
Tried 5-6 (older and newer) Realtek drivers. There are no differencies regarding the sound in 18298.
At the end, didn't understand (and seems till now that nobody understands) what is wrong in this build.
What's so different from the previous version to make system at boot to not recognize/see the audio controllers?
Editing . . . OK, done editing; had to get the graphic in; it wasn't in my original post when I copied it.Well, folks, I think I found where Microsoft blew up Windows . . . Looky this:
Since it's December 12, it stands to reason the Driver date in the above belongs to Microsoft and not my system. Look at the Driver Provider: Microsoft; Driver Date: 12/5/2015; Driver version: 10.0.18298.1000; Digital Signer: Microsoft Windows
It looks to me like Microsoft updated the driver, but screwed up the installation! Gahhhhhhhhhhhhhhh, so it looks like all you have to do is update the High Definition Audio CODEC, but follow @Andre's instructions.
Edit 2: And now we know that there's more wrong with the "new drivers" than I thought. It won't be a simple modification, but I'm pretty sure that's where Microsoft Dev Team went wrong.
At this point, I think the only one taking responsibility for his actions was on Good Morning America this morning. :) Microsoft sure ain't agonna admit nuttin'!
Although I sometimes get a bit of nastiness out of my Insider Builds, normally, I'm the one who gets to say "everything seems to be working fine for me", but not this time!
That said, I was one of the lucky ones and my sound is now working in Build 18298. <knocking on wooden head> Never have experienced a GSOD nor any of the other problems others are having.
Tired to work to make sound works again in 18298, reverted back to 18290.
But the devil didn't let me rest so... tried to found the devil's nest...
Look at this picture:
It's my device manager in 18298.
As you see there are no audio controllers in sound, video and game controllers other than the Nvidia virtual audio.
But in the system devices there is a hd audio controller that have a yellow triangle and that didn't work.
I posted few days ago that this controller wasn't there in 18290 but now I found that exists either in 18290 and found that is the Intel SST controller even if there are stated that have a M$ driver.
The controller id is:
- PCI\VEN_8086&DEV_A348&SUBSYS_1BC01043&REV_10
- PCI\VEN_8086&DEV_A348&SUBSYS_1BC01043
- PCI\VEN_8086&DEV_A348&CC_040300
- PCI\VEN_8086&DEV_A348&CC_0403
I think that for me this bug (no sound in 18298) is Intel driver related and think that is like few builds behind when was a big problem with Windows build and Intel drivers.
Tommorow I'll try to reinstall 18298... again and after I'll try to update that driver that didn't work with the last Intel SST driver to see what's happening.
Edit:
In 18292 the driver for that controller is 10.0.18290.1000 but in 18298 the driver is 10.0.18298.1000.
For me, this means that you are right. They worked on this driver and broke it.
Glad to hear that you got your sound back!
Mine has been OK with this build, the only exception was for the 2 starting ones (it killed my Sandboxie and somehow it ran all my scheduled task), apart from that it is working well (I guess) but the GSOD I received this morning was a surprise.
Hi there @JGToy
I see you have no issues with VMWare on this release unlike many people both here and on the VMWare forums.
Do you have INTEL or AMD CPU as I believe the problem might be related to INTEL CPU IPM / security module or similar.
Please post back as I think a lot of VMware users would love to see this issue moved on a bit as it's the 2nd skippy release where a number of us have encountered problems with VMWare.
For others -- I've no sound issues at all on this release on HP laptop (Intel CPU/Graphics /HD sound). ASpart from the VMWare issue I don't have problems with this release so far.
Thanks
Cheers
jimbo
Hello all,
New, but wanted to chime in and say im having the exact same issues as @emilcioran99 to the letter. Different machine but also semi new hardware. I have spent several days uninstalled / reinstalling trying various methods listed in here to no avail also. Rolled back to 18290 as well. Want to thank everyone in the thread for their input.
Tried to PM you @emilcioran99 but i need to be registered for a few days. Reach out if you read this.
Cheers, Jason.
Sorry if this shows up double, I didnt notice the Mod approval needed.
Quote
