The day after the windows update all was working OK until I tried to open a writer file. Windows then crashed with the stop code APC_INDEX_MISMATCH. What failed win32kfull.sys.
On restarting I found and deleted a .lock file in the profile.
On trying to open LibreOffice this problem repeated.
I then uninstalled the windows security update.
LibreOffice then told me I was using version 7 for the first time. I thought I was already using this version.
Everything now seems to be working normally. However I don't have the security update installed.
The stop error indicates some hardware/driver problem . It could be triggered by something in LibreOffice (most likely Vulkan), but the real issue is likely video drivers not handling the requests correctly (no user-space applications should be ever able to create BSODs: that always indicate low-level system component bugs).
For now, try to force Skia software rendering under Options->LibreOffice->View, and check if this allows you to have the update installed. Please try to file a bug to your video driver manufacturer, if this helps.
(In reply to mejames1974 from comment #0)
> LibreOffice then told me I was using version 7 for the first time. I thought
> I was already using this version.
This only means that the stop error happened at the moment when the profile was written, and so it got corrupted to the point that LibreOffice had to re-create it the next time. Having re-created the profile, it lost the memory of being already used here.
Please mention your video hardware model, video driver version, and which security update was that that caused this. Thanks!
Windows 10 security update of 10 April 2021
AMD RX570 8GB
The video driver dated from 2019.
Unfortunately I subsequently let AMD update everything and consequently my monitors do not get a signal (giving me another headache) so I can't be more precise since I can't, at present access my computer.
oops 10th March!
Likely that's https://support.microsoft.com/en-us/topic/march-9-2021-kb5000802-os-builds-19041-867-and-19042-867-63552d64-fe44-4132-8813-ef56d3626e14
which has this entry in "Known issues in this update":
> After installing this update, you might receive an APC_INDEX_MISMATCH error
> with a blue screen when attempting to print to certain printers in some apps.
and this "Workaround":
> We are presently investigating and will provide an update when more
> information is available.
It looks like not related to video (and thus it is unlikely to be solved by forcing Skia software mode), but to some printer. Could you please tell which printer and printer driver you are using?
I did not attempt to print anything after switching the computer on the day after the update.
(The printer I use is a Kyocera FS C5100DN colour laser)
(In reply to mejames1974 from comment #8)
> I did not attempt to print anything after switching the computer on the day
> after the update.
LibreOffice might still communicate with driver of the printer configured in the document when loading it, e.g. to get a list of supported paper types, or margins, or something like that. See e.g. tdf#42673, or tdf#116679, where printer was communicated at opening Format -> Character.
> (The printer I use is a Kyocera FS C5100DN colour laser)
(In reply to Mike Kaganski from comment #6)
> Likely that's
... or https://support.microsoft.com/en-us/topic/march-9-2021-kb5000808-os-build-18363-1440-6989940a-252d-48f3-a2a7-a42bf19fa2c8
from see also https://bugs.documentfoundation.org/show_bug.cgi?id=140997#c2
This is known and NOB, if you are affected will depend on the printers you have installed for use by LibreOffice and other products.
Removing the printers, they get recorded into your LibreOffice profile, should help--but it is really up to Microsoft to fix issues with KB5000802 (or KB5000808, KB5000809, KB5000822 for older Win10 builds).
Thanks for your work investigating this problem, much appreciated.
is reported to fix this issue.
*** Bug 141246 has been marked as a duplicate of this bug. ***
*** Bug 141046 has been marked as a duplicate of this bug. ***
*** Bug 141991 has been marked as a duplicate of this bug. ***