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: Oldest
  1. Anonymous
    2018-02-02T21:55:43+00:00

    Yes, the recently-released KB4058258 update to build 16299.214 should resolve this:

    https://support.microsoft.com/en-us/help/4058258/windows-10-update-kb4058258

    It should now be available in Windows Update.  Sorry again for the issue.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-04T12:04:59+00:00

    Early days, but I force downloaded the update that Jeffhubb linked and, fingers crossed, it seems to have fixed the issues so far.     (I don't think it's auto-rolling out yet)

    I'll be sure to report back if the BSOD happens again, but if I don't, assume it worked if you're reading this and having the same issue.

    Anyone else updated and confirmed the fix?   I've only been using the updated version for a day so far.

    Thanks to all at MS for sorting.     Think I'll go out and buy a surface machine now!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-04T12:58:23+00:00

    I can also confirm that it is fixed in the build xxx.214

    I have a relatively complex OneNote page with many pictures copied from Powerpoint. Before I downloaded and installed the update, I got a bluescreen every time I zoomed in or out. Sometimes even while launching OneNote. I could reproduce the blue screen every time before the update. Now, after the the update, I tried several times to reproduce the bug but it didn't happen again. 

    Strange thing is, that the fix is not mentioned in the description of the update. (Or I didn't find it)

    Thanks for the fix. The Surface pro is worthless with such a severe bug. Would be nice if Microsoft would inform the owners of a surface about this important update/fix as soon as possible.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-06-08T02:24:45+00:00

    Yes, the recently-released KB4058258 update to build 16299.214 should resolve this:

    https://support.microsoft.com/en-us/help/4058258/windows-10-update-kb4058258

    It should now be available in Windows Update.  Sorry again for the issue.

    Hi,

    This patch worked really well for a couple of months or more.

    However a couple of weeks ago the Blue Screens returned.

    Almost always the driver failure is indicated as win32kbase.sys. 

    The failing module is normally ONENOTE.EXE but can sometimes be dwm.exe or ShellExperienceHost.exe.

    Can anyone offer any advice? 

    Our machines are primarily Win10/64bit v1709 and Office Click To Install 2016 fully patched.

    Regards

    John

    Was this answer helpful?

    0 comments No comments