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
    2017-12-31T14:57:50+00:00

    Sorry, to have misled...my problem was actually with OneNote 2013 desktop version.  And I resolved the problem. It is/was one page that contained multiple, maybe 20 or so stick people figures ...made using the straight line and circle shapes then copy pasted as a picture.  Whenever this page is/was selected to view ...85/95% of the time I get the BSOD.  Just so happened that I created this page after install of 1709 Fall Creator update.  

    I can continually recreate the BSOD with this page, so I am confident it is the problem.  Thank you for the help in this matter.

    Greg

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-30T21:31:52+00:00

    I to have similar problem (BSOD in win32kbase.sys) using OneNote and Windows after install of 1709 Fall Creator Update.

    Additionally I to have notice that the more complex the OneNote page...crash occurs...BSOD occurs immediately.

    I had the same problem. But after the restart of a BSOD onenote presented me with a screen where I had the choice to delete my cache, delete my notebooks or to restore onenote to the default settings. I choice to delete the cache and until now I haven't received a BSOD anymore from Onenote. Maybe if you delete your cache the problem will be solved...

    In C:\Users**<user>**\AppData\Local\Microsoft\OneNote\16.0

    you'll find a cache folder. Delete it after closing Onenote.

    I hope this will help you ;)

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-12-28T03:38:10+00:00

    Hi,

    It is possible that there is a third party service running in the background that is causing the issue. This service may not be compatible anymore to the new version of Windows 10 and OneNote 2016 and it is affecting their performance. We recommend that you perform a clean boot to see if the issue will occur while your third party apps are disabled.

    If the issue persists, we suggest that you post yout concern in the Feedback Hub application. You can follow the steps that was provided by Michelle Her to know how to post the issue in the application. You can also search the Feedback Hub for any posts regarding the same concern and upvote those posts.

    Regards.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-12-27T23:07:18+00:00

    I to have similar problem (BSOD in win32kbase.sys) using OneNote and Windows after install of 1709 Fall Creator Update.

    Additionally I to have notice that the more complex the OneNote page...crash occurs...BSOD occurs immediately.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-12-24T02:27:05+00:00

     When I rolled back to Version 1703 the problem vanished. After trying again later the problem was there again.

    By this, do you mean to say that the problem initially went away after rolling back. But then it suddenly reappeared?

    Has there been any solution to this in the past couple of weeks?

    Was this answer helpful?

    0 comments