BSOD on OneNote 2016 after Upgrade to Windows 10 Fall Creators Update 1709

Anonymous
2017-11-15T15:14:04+00:00

I have this problem (BSOD in win32kbase.sys) on different computers (dell optiplex 760 & 780, optiplex 7020, hp elitedesk 800 g2, home built on MSI mainboard with core i7 3rd generation, (some with NVIDIA NVS, some integrated graphics, different software), a Surface Book (!) from 2016 ) after upgrading to Windows 10 1709 on OneNote 2016 (coming with the Office 2016 package), but only for this combination of OneNote and Windows.

We use CurrentBranch for Business Enterprise and regular Professional version.

Common is to all the cases that a more complex OneNote slide crashes faster (within seconds):

we have tables (6x20) filled with screen-captured images (~1500pixels x 1000pixels) + some text, when zooming (control + mouswheel) in these files, BSOD occurs immediately.

No special additional hardware, update level on 2017-11-15 (just received KB4048951 and others, problem persits).

On request, I could share the OneNote file.

The exactly same OneNote file makes no problems on Win 10 1703/Win7/Win 8.1, or on a Win 10 1709 running OneNote from Office 2010/2013 packages.

Windows for home | Windows 10 | Performance and system failures

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

84 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-02T19:19:00+00:00

    Here's another thread in chinese where someone provided the minidump analysis that was very similar to the one I generated.

    https://answers.microsoft.com/zh-hans/windows/forum/windows\_10-hardware/%E5%9B%A0%E4%B8%BAonenote%E8%A7%A6%E5%8F%91/f3f8f39a-7077-4de1-8fd5-30f07dc825cb

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-02T19:24:40+00:00

    We have built multiple "clean" images and are having the same result once 1709 update is installed. We can reproduce the issue 100% of the time.

    Install Win10, make sure it is updated to 1709.

    Open Power Point and create a page of content.

    COPY AND PASTE that content from PowerPoint to OneNote (use ctrl  ctrl v or the menu)

    Zoom in and out (with the touch screen, mouse wheel, or typing it in (very fast)

    =

    BSOD

    EDIT:

    If you view the notebook online, it works fine.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-02T19:49:57+00:00

    Hi all, I did a clean install with 1703. This completely fixed the problem! Please keep this thread alive by posting if there are any fixes to this in 1709.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-03T08:30:52+00:00

    Problem is persisting. - Copied and pasted material, complex pages cause OneNote 2016  to crash. 

    Solutions:

    • Rollback to version 1703 if you can: The problem vanishes.
    • Use the OneNote UWP App: I had no problems whatsoever with the same notebooks that crashed Windows before.

    I had the same problems on two completely different machines, and one is a Surface Pro 3. It's a Windows or a OneNote 2016 problem and Microsoft should fix this. It's an embarassing long time since this problem came up. The users provided all the necessary information. Standard procedures where executed, dumps provided. There is nothing more to say...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-01-03T08:42:17+00:00

    Problem is persisting. - Copied and pasted material, complex pages cause OneNote 2016  to crash. 

    Solutions:

    • Rollback to version 1703 if you can: The problem vanishes.
    • Use the OneNote UWP App: I had no problems whatsoever with the same notebooks that crashed Windows before.

    I had the same problems on two completely different machines, and one is a Surface Pro 3. It's a Windows or a OneNote 2016 problem and Microsoft should fix this. It's an embarassing long time since this problem came up. The users provided all the necessary information. Standard procedures where executed, dumps provided. There is nothing more to say... 

    It may also be a Intel display driver problem, although some people described it also happens for nvidia cards. I can not reproduce it on my desktop computer with nvidia card, only on lenovo laptops. Although the error persists for me even after uninstalling the display driver or running safe mode, so that would argue against it.

    Was this answer helpful?

    0 comments