Excel 2013 High CPU Usage

Anonymous
2013-10-21T13:21:14+00:00

We work on a product that uses Excel, we are now testing all aspects of Excel 2013. During these tests, we seem to have encountered a problem where excel suddenly causes high CPU usage by only drawing some shapes. We have been able to minimize the problem into the following few steps:

  • Open a new, clean workbook
  • Draw an oval, give it a material (right-click, choose “Format Shape”, click “Effects”, “3D Format”, “Material”. Choose any material.)
  • Duplicate the Shape four times, producing Oval2, 3, 4 and 5.
  • Group Oval2 and 3. Group Oval 4 and 5.
  • Press Alt-F10, in the selection window, hide the group containing Oval2 and 3.
  • Deselect everything (!) by clicking in an empty cell.

Now observe the task manager. On an I7 Windows 7 PC, Excel now runs 4 cores at around 50%. Also, OnTime functions are not being called anymore because of this rendering bug. Once you select any shape, or un-hide the hidden group, Excel becomes quiet once again. Also, the problem can be prevented from happening by removing the materials in the shapes.

This bug (?) seems to happen also on most of our more complicated applications, and it would take lots of work to re-design everything not to use materials. Can anyone confirm this problem, provide a workaround?

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

86 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-03-10T06:59:11+00:00

    This is very simple to replicate with a native Excel-born file:

    1. Open Excel.  Start a new blank workbook.
    2. Set Excel window so it is not maximized.
    3. Put 1,2,3,4,5,6 in cells A1:A6
    4. Put 2,4,6,8,20,12 in cells B1:B6
    5. select cells A1:B6.  Insert scatter plot.
    6. Right click on scatter plot > move to its own chart sheet.
    7. Select the chart sheet. > CPU usage is very low

    1. Maximize Excel > CPU goes high

    1. There are 2 threads utilizing the CPU.  These are their call stacks

    Thread 11456

    dxgi.dll!ApplyCompatResolutionQuirking+0x710

    mso40uiwin32client.dll!Ordinal929+0xdcf

    dxgi.dll!ApplyCompatResolutionQuirking+0x710

    mso40uiwin32client.dll!Ordinal3051+0x23b83

    mso40uiwin32client.dll!Ordinal4435+0x573

    mso40uiwin32client.dll!Ordinal2547+0x6bc

    mso40uiwin32client.dll!Ordinal929+0xddd

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x439

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x404

    Thread 7080

    mso40uiwin32client.dll!Ordinal1629+0x360

    mso40uiwin32client.dll!Ordinal1052+0x16b9e

    mso40uiwin32client.dll!Ordinal1629+0x360

    mso40uiwin32client.dll!Ordinal1629+0x14d

    mso40uiwin32client.dll!Ordinal1629+0xe9

    mso40uiwin32client.dll!Ordinal30+0x385

    USER32.dll!SetManipulationInputTarget+0x53

    USER32.dll!DispatchMessageW+0x8fa

    USER32.dll!DispatchMessageW+0x254

    USER32.dll!DispatchMessageW+0x10

    EXCEL.EXE!Ordinal42+0x2eab4

    EXCEL.EXE!Ordinal42+0x6da8

    EXCEL.EXE!Ordinal42+0x1163

    KERNEL32.DLL!BaseThreadInitThunk+0x24

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x439

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x404

    All that was replicated on the same system I described above.

    Hope that helps!

    Sean

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-03-13T11:03:49+00:00

    I've tried these steps on three different computers with and without hardware accelerations and all the times everything is normal. CPU is stable on 1%-3% only when maximizing (half of one second) and right after that CPU usage goes down to zero (0.1%-0.14%).

    Will try again on newly installed laptop in next couple days.

    And it looks like 3 different bugs.

    1. Yours - mso40uiwin32client.dll and dxgi.dll (last one is DirectX Graphics Infrastructure and I think this bug can be solved by disabling Hardware acceleration).
    2. Mine with Excel 2016. This looks like Race Condition cause two threads have multiple kernel calls to KeWaitForMutexObject and on the top - KeSynchronizeExecution, I have no idea what resource can cause such state, but may be connected with hardware interrupts and the same situation like you have but on the other level - video drivers.
    3. Old mine with Excel 2013. But this situation has absolutely different roots cause it is caused by mso.dll. But I prefer to solve problem with Excel 2016.

    In my case MS closed case with "Unsupported" diagnosis.

    Also they don't provide debugging symbols for office. Only for some builds of Windows.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-03-13T13:02:48+00:00

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-03-13T20:13:20+00:00

    Sorry, I had hardware acceleration turned off previous.  I completed these steps:

        Open Excel.

        Click on file, Options.

        Go to the Advanced tab.

        Under the Display section, check the box for 'Disable hardware graphics acceleration'.

        Click ok and restart Excel.

    and repeated the above test:

     ...with hardware acceleration disabled:

    Thread 13292:

    wow64cpu.dll!TurboDispatchJumpAddressEnd+0x540

    wow64cpu.dll!TurboDispatchJumpAddressEnd+0x9e

    wow64.dll!Wow64KiUserCallbackDispatcher+0x4151

    wow64.dll!Wow64LdrpInitialize+0x120

    ntdll.dll!LdrInitializeThunk+0x16d

    ntdll.dll!LdrInitializeThunk+0xe

    ntdll.dll!ZwWaitForMultipleObjects+0xc

    KERNELBASE.dll!WaitForMultipleObjects+0x18

    mso40uiwin32client.dll!Ordinal2547+0xa1f

    mso40uiwin32client.dll!Ordinal929+0xddd

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x439

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x404

    Thread 8492:

    wow64win.dll+0x100f4

    wow64win.dll+0xc487

    wow64.dll!Wow64SystemServiceEx+0x155

    wow64cpu.dll!TurboDispatchJumpAddressEnd+0xb

    wow64.dll!Wow64KiUserCallbackDispatcher+0x4151

    wow64.dll!Wow64LdrpInitialize+0x120

    ntdll.dll!EtwEventProviderEnabled+0x1cb1

    ntdll.dll!memset+0x1c006

    ntdll.dll!LdrInitializeThunk+0xe

    win32u.dll!NtGdiPatBlt+0xc

    GDI32.dll!PatBlt+0x2e

    EXCEL.EXE!Ordinal42+0x4155a

    EXCEL.EXE!Ordinal42+0x41c95

    EXCEL.EXE!MdCallBack12+0x85011

    EXCEL.EXE!MdCallBack12+0x8474b

    EXCEL.EXE!Ordinal42+0x3828fa

    mso40uiwin32client.dll!Ordinal1076+0x37d

    mso40uiwin32client.dll!Ordinal1629+0x388

    mso40uiwin32client.dll!Ordinal1629+0x14d

    mso40uiwin32client.dll!Ordinal1629+0xe9

    mso40uiwin32client.dll!Ordinal30+0x385

    USER32.dll!SetManipulationInputTarget+0x53

    USER32.dll!DispatchMessageW+0x8fa

    USER32.dll!DispatchMessageW+0x254

    USER32.dll!DispatchMessageW+0x10

    EXCEL.EXE!Ordinal42+0x2eab4

    EXCEL.EXE!Ordinal42+0x6da8

    EXCEL.EXE!Ordinal42+0x1163

    KERNEL32.DLL!BaseThreadInitThunk+0x24

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x439

    ntdll.dll!RtlSubscribeWnfStateChangeNotification+0x404

    Regards,

    Sean

    Was this answer helpful?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more