Author Topic: A few change on Windows 10 1607  (Read 7450 times)

Offline BenYeeHua

  • Member#
  • *****
  • Posts: 2243
  • Gender: Male
A few change on Windows 10 1607
« on: September 10, 2016, 07:38:07 PM »
Just some change that I observed.

The Adobe Flash Player will calling the Multimedia Scheduler Driver to set the Timer Resolution as 0.5ms, which causing your CPU running 95% non-stop, and wasting your power. :P

While the Edge will compress the Memory and showing as Paged Pool in Windows Task Manager, and freeze itself sometimes. :o

And also, WDDM 2.1 is included, but most graphic card driver not catching up yet. ::)
https://en.wikipedia.org/wiki/Windows_Display_Driver_Model#WDDM_2.1

That's all. ;D



Offline edkiefer

  • Volunteer User Moderator
  • Member#
  • *****
  • Posts: 1677
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #1 on: September 10, 2016, 09:55:23 PM »
I don't have that problem with CPU usage with flash, I use Palemoon browser (FF based, kind a ).
AU (1607) has been running well for me, as have 1511 too.
Bitsum QA Engineer

Offline BenYeeHua

  • Member#
  • *****
  • Posts: 2243
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #2 on: September 16, 2016, 04:17:13 PM »
I don't have that problem with CPU usage with flash, I use Palemoon browser (FF based, kind a ).
AU (1607) has been running well for me, as have 1511 too.
Not the CPU usage, but the CPU C-status, it is keep running in C0-C1e states without going into deeper C-status, which causing more power usage.
It is nothing on older CPU than Haswell, but as I tested on newest laptop, with 1-5% CPU usage(idle), it drop from 4w to 1w, based on the Package power, so it is a lot for newer CPU. :)

Offline edkiefer

  • Volunteer User Moderator
  • Member#
  • *****
  • Posts: 1677
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #3 on: September 16, 2016, 05:15:11 PM »
Ok, I see, well I am on Ivybridge, 3570k so even older.
Bitsum QA Engineer

Offline Hotrod

  • Member++
  • ****
  • Posts: 265
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #4 on: September 17, 2016, 01:50:34 AM »
I have had 2 laptops now that have gotten stuck with a black screen after the 1607 AU. One (Asus) was totally black with only a flashing cursor that you can't actually type from or use. This one needed a complete re-install of Windows 10 to fix it. The other was a Gateway that got stuck on a black screen with the spinning update dots for 2 days. I got it to reboot after several power cycles but then it reverted to an earlier restore point and upon completing the AU a second time it did it again. I have it back up now but i dare not login yet for fear of losing it again. I'm hoping if i wait long enough Microsoft will fix the issue. If it comes down to it I may need to do a clean install on this one too.

Offline edkiefer

  • Volunteer User Moderator
  • Member#
  • *****
  • Posts: 1677
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #5 on: September 17, 2016, 06:50:01 AM »
Luckly I have not run into that problem, but i have read other have it, the black screen is not new one AFAIK, not sure if vid driver but I have seen it reported before (pre AU 1607).
With a Win10 VM I get sometimes the "getting ready to config" when I close it, even though no updates were DL. I just terminate whole thing and its ok on next startup, that's probably just a VM issue.
Bitsum QA Engineer

Offline edkiefer

  • Volunteer User Moderator
  • Member#
  • *****
  • Posts: 1677
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #6 on: September 17, 2016, 06:54:23 PM »
The biggest annoyance in 1607 is the new UAC window, which can't seem to keep itself in foreground.
This may help users for now with this issue.

http://winaero.com/blog/enable-windows-7-like-uac-prompt-in-windows-10-anniversary-update/ (http://winaero.com/blog/enable-windows-7-like-uac-prompt-in-windows-10-anniversary-update/)
Bitsum QA Engineer

Offline BenYeeHua

  • Member#
  • *****
  • Posts: 2243
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #7 on: September 19, 2016, 12:05:26 PM »
I have had 2 laptops now that have gotten stuck with a black screen after the 1607 AU. One (Asus) was totally black with only a flashing cursor that you can't actually type from or use. This one needed a complete re-install of Windows 10 to fix it. The other was a Gateway that got stuck on a black screen with the spinning update dots for 2 days. I got it to reboot after several power cycles but then it reverted to an earlier restore point and upon completing the AU a second time it did it again. I have it back up now but i dare not login yet for fear of losing it again. I'm hoping if i wait long enough Microsoft will fix the issue. If it comes down to it I may need to do a clean install on this one too.
Ya, I facing this similar bug(waiting the spinning bootup dots, no facing update bug yet) since 10240, but it only hang on it sometimes, most of the time, it is slow on shut down...

I think it is a bug on the AHCI driver, because the harddisk is working as it should be(the harddisk light is constant on), and I removed my intel AHCI driver after I update to Win 10, so...
The biggest annoyance in 1607 is the new UAC window, which can't seem to keep itself in foreground.
This may help users for now with this issue.

http://winaero.com/blog/enable-windows-7-like-uac-prompt-in-windows-10-anniversary-update/ (http://winaero.com/blog/enable-windows-7-like-uac-prompt-in-windows-10-anniversary-update/)
Hmm, I always disable the UAC dialog, but keep the UAC enable, as I know what's software I am running, and my mom don't know about UAC and it is disabled for most people(windows 7), this is also a good solution for people that just keeping click on "ok". :)

Offline edkiefer

  • Volunteer User Moderator
  • Member#
  • *****
  • Posts: 1677
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #8 on: September 19, 2016, 02:45:46 PM »
I think it only affects if you set it to get the pop up but not back-ground darkening.
I haven't tested it as I hate the darkening with prompt.
Bitsum QA Engineer

Offline BenYeeHua

  • Member#
  • *****
  • Posts: 2243
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #9 on: September 19, 2016, 10:55:29 PM »
Ya, that is secure desktop, it avoid any software other than admin to access it, I am still a bit hate that delay when you switch to it.... :P
https://technet.microsoft.com/en-us/library/dd834746(v=ws.11).aspx

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5245
  • Gender: Male
  • The Lasso
    • Bitsum
Re: A few change on Windows 10 1607
« Reply #10 on: September 24, 2016, 11:41:07 AM »
I, too, on one system (laptop) have had a lot of BSODs in the latest Win10 build, the culprit being Intel's Graphics Driver in my case. It could be thermal issues, but the device is new, so was built bad if so. It is becoming quite inconvenient.

I have not seen ANY problems with the latest Windows 10 build on my desktop machines, they are fine (maybe because they have AMD graphics adapters?).

Same goes for virtual machines. No issues.
Software Engineer. Bitsum LLC.

Offline Jeremy Collake

  • Administrator
  • Member#
  • *****
  • Posts: 5245
  • Gender: Male
  • The Lasso
    • Bitsum
Re: A few change on Windows 10 1607
« Reply #11 on: September 24, 2016, 11:43:44 AM »
Just some change that I observed.
The Adobe Flash Player will calling the Multimedia Scheduler Driver to set the Timer Resolution as 0.5ms, which causing your CPU running 95% non-stop, and wasting your power. :P
While the Edge will compress the Memory and showing as Paged Pool in Windows Task Manager, and freeze itself sometimes. :o
And also, WDDM 2.1 is included, but most graphic card driver not catching up yet. ::)
https://en.wikipedia.org/wiki/Windows_Display_Driver_Model#WDDM_2.1
That's all. ;D

That probably explains the Intel graphics adapter issues, maybe. We'll see.

No surprise Flash doesn't behave like it should. Someone needs to stick a wooden stake in it's heart.
Software Engineer. Bitsum LLC.

Offline edkiefer

  • Volunteer User Moderator
  • Member#
  • *****
  • Posts: 1677
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #12 on: September 24, 2016, 03:47:50 PM »
its been very stable for me, the only issue that came up was with WU a definition for defender, got an error installing.
All I had to do to fix it was an update from within Defender and it updated fine there.
« Last Edit: August 27, 2018, 04:00:51 PM by edkiefer »
Bitsum QA Engineer

Offline Hotrod

  • Member++
  • ****
  • Posts: 265
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #13 on: September 24, 2016, 04:03:33 PM »
I got mine both up and running with several reboots and spinning dots on Black BSOD's. The ASUS had to be completely re-installed as it only had BIOS left available. The Gateway refused for a long time...then one day for no reason at all it booted up like nothing had happened. It finally took the updates by itself after that. Maybe MS did some tweaking??

Offline BenYeeHua

  • Member#
  • *****
  • Posts: 2243
  • Gender: Male
Re: A few change on Windows 10 1607
« Reply #14 on: September 24, 2016, 05:27:53 PM »
No surprise Flash doesn't behave like it should. Someone needs to stick a wooden stake in it's heart.
After I testing, it is all software that calling MMCSS(Multimedia Scheduler)'s API, I just run "net stop mmcss", and open a page with Flash Player that playing video,  run "net stop mmcss" again, and found MMCSS is running again.

But it is still not clear that, it is MMCSS changed and start setting timer resolution to 0.5ms, or Adobe Flash Player(Active-X version) start calling MMCSS's api and causing this issues.
Too bad I don't use MPC-HC a lot of time, and monitoring the timer resolution... :P

PS:The Active-X version has been changed a lot by MS, compare to NPAPI and PPAPI, but it seem like they are stop changing it, which start causing a lot of issues, like same CPU usage with PPAPI version now, by going from 5% to 20%...(should be hardware acceleration related)

I got mine both up and running with several reboots and spinning dots on Black BSOD's. The ASUS had to be completely re-installed as it only had BIOS left available. The Gateway refused for a long time...then one day for no reason at all it booted up like nothing had happened. It finally took the updates by itself after that. Maybe MS did some tweaking??
Not sure, Windows Update is always a mess, MS even break Windows 7 as they updated Windows Update on Windows 7, while Windows 7 has released too many patch for it to re-scan each time you want to check for update.

So on Windows 7, you just take 1 hours to scanning with 1 core maxed.. :P