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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2018-01-12T10:10:55+00:00

    Doesn't help, here.

    BSOD, no matter if cache was deleted before or moved to another location, when zooming in OneNote 2016/Win10 1709.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2018-01-12T09:07:00+00:00

    Sorry, but I don't have a OneNote 2010 installer, nor did I try to install another version of OneNote in parallel.

    Our solution was to reinstall all the office computers with LTSB version of Windows10 1607 - quite a bit of work and really a shame, that Microsoft is doing nothig about it..

    On my Surface Book I still have the problem, but I can use the UWP app, there, which is a rather poor work around, considering the reduced functionality compared to the desktop version.

    I do really hope Microsoft is providing a proper fix, before our lab computers are forced by Microsoft to upgrade from 1703 to 1709.. here we do absolutely rely on the desktop version of OneNote.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2018-01-11T11:01:07+00:00

    Korjaa Windows 10 S. ei aktivoidu ja poista se

    Was this answer helpful?

    0 comments
  4. Anonymous
    2018-01-11T10:40:28+00:00

    I have the same Problem and need a solution. This is a showstopper on the Surface pro!

    Reinstallation of Windows 1703 is not an option. Going back to 1703 doesn't work, because the update is too long ago.

    OneNote 2010 would be a sufficient workaround to go on working until microsoft provides a bug fix. (Since the UWP App is a cloud-based program, it is not an option for us.)

    Is it possible to install OneNote 2010 in parallel, if you have installed Office 2016? If so could you (ChristianLotze) or someone from Microsoft provide a "OneNote 2010" installation file?

    -Patrick

    Was this answer helpful?

    0 comments
  5. 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