12 Replies Latest reply on Jun 14, 2016 2:18 PM by EstebanC_Intel

    Windows 10 (1511) high CPU usage by 'System and compressed memory' process

    WimC

      Hi,

       

      I have a Macbook Pro 15" 2015 with an Intel Core i7-4980HQ and Intel Iris Pro 5200 graphics (discrete IGP only, no Nvidia card).

       

      Under Windows 10 Treshold 2 (v1511) (bootcamp) one of the eight cores is continuously used by the System and compressed memory process when the Intel driver is used for the discrete graphics. When the Intel driver is uninstalled and I revert back to the Microsoft driver the problem goes away.

       

      The problem also happens only when you do a cold start (after shutdown) or reboot. If you put the laptop to sleep or hibernate to problem also goes away. So the workaround for now is not do a reboot or shut down but hibernate or sleep.

       

      I have tested this with the Apple provided drivers for the Iris Pro and the latest drivers from Intel: Download Intel® Graphics Driver for Windows® 10 [15.40][4th Gen] version 15.40.10.64.4300.

       

      The problem is easily reproducible: uninstall the Intel Iris Pro from device manager and tick "remove driver software" and after a reboot the problem is gone. Reinstall the Intel Graphics Driver and after a reboot the problem is back. So I suspect somewhere along the line there is a conflict between the driver and Windows 10. Since the issue can be solved with sleep or hibernate I'd suspect something with the ACPI driver.

       

      Has anyone else had this problem or contacted Intel about this?

       

      See also: Win 10 'Treshold 2' very high cpu usage by 'Sys... | Apple Support Communities

       

      Category

      Questions

      Answers (N/A if not applicable)

      Description

      Provide a detailed description of the issue

      Cold boot or reboot causes high CPU usage from Windows System and compressed memory process

      Does it fail every single time, or only sometimes?
      If you can offer a % rate please do.

      100%

      Hardware (HW)

      Brand and Model of the system.

      Apple Macbook Pro 15" Mid 2015

      Hybrid or switchable graphics system?
      ie Does it have AMD or NV graphics too?

      No, discrete only

      Make and model of any Displays that are used to see the issue (see note2 below).
      LFP
      = Local Flat Panel (Laptop panel)
      EFP = External Flat Panel (Monitor you plug in)

      Both:

      - LFP

      - 2x EFP (Dell U2715H)

      How much memory [RAM] in the system (see note2 below).

      16GB

      Provide any other hardware needed to replicate the issue.
      ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc

      None

      Hardware Stepping (see note1 below).

      Software (SW)

      Operating System version (see note2 below).

      Windows 10 Pro (10.0.10586)

      VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.

      1215.0

      Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).

      20.19.15.4300

      SW or Apps version used to replicate the issue.

      Windows 10 Pro Treshold 10, Bootcamp 5.1.5769 (Download Boot Camp Support Software 5.1.5769)

      Configurations

      Single display, clone, or extended (see note2 below).

      Both: on laptop screen and when used with 2 external monitors

      Display resolution & refresh rate setting of each display (see note2 below).

      LFP: 1920x1200x60Hz

      EFP: 2560x1440x59Hz

      AC or DC mode, i.e. is power cable plugged in or not?

      Happens in both cases

      How to reproduce

      Please provide steps to replicate the issue.  These steps are very crucial to finding the root cause and fix.
      A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.

      1. Install Windows 10 via Bootcamp
      2. Install Apple provided drivers
      3. See first core being used continously
      4. Hibernate or sleep
      5. See CPU act normal
      6. Uninstall Intel drivers via device manager
      7. See CPU act normal
      8. Reinstall Intel drivers
      9. See first core being used continously

      KR,


      Wim