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 No comments

84 answers

Sort by: Most helpful
  1. Anonymous
    2018-01-11T08:22:50+00:00

    Please take a look at earlier posts (pages 1-5):

    "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... "

    The Problem: The UWP can't really replace OneNote2016 and there are people that can't go back to Version 1703 of Win 10 because they use enterprise or school licences

    Other solutions as deleting the cache and reopen the notebooks and/or installing 64-bit Version of OneNote 2016 didn't work in my case...

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-01-09T20:31:34+00:00

    Hi, everyone,

    at least for me the problem with OneNote 2016 desktop version is solved. I got a BSOD right at the start of OneNote, just after the splash screen of OneNote.

    In an article I read that I should delete the cache of OneNote. At the last start of OneNote a small window appeared unexpectedly, which gave me the possibility to clear the cache of OneNote with a button.

    When I restarted OneNote, all books were closed and I opened them all one after the other. The BSOD no longer appeared. Probably I didn't have had the problem with the vector graphics and the zoom but a different one with creators update 1709 and OneNote. Anyway, OneNote works optimally on my computer now. Hopefully OneNote will be supported by Microsoft for a long time, because there is nothing better for me.

    Many greetings

    Wolfgang

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-01-09T18:41:45+00:00

    This is no solution, and moreover your/the support's speculations help no one dealing with the immediate problem. 

    If the problem is known (should be, I personally called to report it), they should have also been able to inform you about the cause of the problem, drivers/too many vector graphics/inherent windows problem. People pay money for office and windows and there must be support for the software as long as it exists and is in active use - especially if there is no better alternative by Microsoft.

    Did they elaborate on the more precise cause of the problem (analyzed kernel dumps)? Actual solutions / workarounds? What can be done to get an update to patch this mess?!

    I contacted the Office support and asked if the problem is known: It is! - Regrettably there seems to be no simple solution in the forseeable future for OneNote 2016. There seems to be no patch/update planned that could solve the problem when updating to Windows to version 1709.

    There where rumors a few months ago, that OneNote 2016 will die. Instead there would be an UWP App of OneNote that would integrate the features of the desktop version. That's only a speculation but now it seems this seems to be not totally improbable.

    For all people who rely on the desktop version for now, that's quite bad news... OneNote 2016 is a extremely good and versatile piece of software and Microsoft seems not to give a damn. The future is in the cloud(s)...

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-01-09T18:26:39+00:00

    Yes! If I zoom in and out some specific pages that contain many pictures, this annoying problem will appear and I don't know how to avoid it.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-01-04T16:09:32+00:00

    I contacted the Office support and asked if the problem is known: It is! - Regrettably there seems to be no simple solution in the forseeable future for OneNote 2016. There seems to be no patch/update planned that could solve the problem when updating to Windows to version 1709.

    There where rumors a few months ago, that OneNote 2016 will die. Instead there would be an UWP App of OneNote that would integrate the features of the desktop version. That's only a speculation but now it seems this seems to be not totally improbable.

    For all people who rely on the desktop version for now, that's quite bad news... OneNote 2016 is a extremely good and versatile piece of software and Microsoft seems not to give a damn. The future is in the cloud(s)...

    Was this answer helpful?

    0 comments No comments