Crash on exit in KERNELBASE.dll, on Windows 10

razvan

Well-known member
(creating a separate thread, as it's different than the other reports).

I've just discovered several crash dump in %LOCALAPPDATA%\CrashDumps and after a bit of experimentation, it turns out they are created when closing PI. The crash is happening after the PI window is closed, so there's no obvious indication to the user, nonetheless it's reproducible every time. Note that there may have been earlier dumps, I check and clean that folder periodically. Still, I think it's a relatively new problem, perhaps caused by the latest Windows update, as I never had that many files there and I have times when I open PI frequently.

It's happening on two different computers, both Windows 10 Home 20H2, v 10.0.19042.

PI: PixInsight Core 1.8.8-8 Ripley (x64) (2021-05-31)

From the event log (both computers have the same version of Windows and KERNELBASE.DLL in particular. The exception code and fault offsets are the same).

Faulting application name: PixInsight.exe, version: 1.8.8.8, time stamp: 0x60b522a2
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1023, time stamp: 0x924f9cdb
Exception code: 0xc0000602
Fault offset: 0x000000000010b39c
Faulting process id: 0xf44
Faulting application start time: 0x01d77336d549dc64
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: ca24099f-85f1-491d-94c9-445adb4fa3e4
Faulting package full name:
Faulting package-relative application ID:


One computer is a Dell XPS 8930 desktop, i7-8700 CPU @ 3.20GHz, 64GB of RAM.
The second is a Thinkpad T410 laptop, i7-7500U CPU @ 2.70GHz, 24GB of RAM.

Crash dumps:

2021-07-06 11:14 PM 297,034,112 PixInsight.exe.11244.dmp
2021-06-26 04:29 PM 309,994,401 PixInsight.exe.11744.dmp
2021-06-29 05:06 PM 297,035,454 PixInsight.exe.12428.dmp
2021-06-27 11:37 PM 297,064,189 PixInsight.exe.14968.dmp
2021-07-03 10:43 PM 297,035,720 PixInsight.exe.16720.dmp
2021-06-26 06:17 PM 297,062,941 PixInsight.exe.19328.dmp
2021-07-07 09:49 AM 297,035,880 PixInsight.exe.3908.dmp
2021-07-07 09:48 AM 297,033,456 PixInsight.exe.6748.dmp
2021-07-02 10:58 PM 297,034,480 PixInsight.exe.7648.dmp
2021-07-06 11:14 PM 297,163,996 PixInsight.exe.8020.dmp


If there's any more info I can supply, please let me know,
Razvan
 
Update #1: I checked the entire Application Log in Windows and found earlier crashes going back to 2020-11-11 (earlier log entries are no longer available). So it's not specific to 1.8.8.8.

Faulting application name: PixInsight.exe, version: 1.8.8.6, time stamp: 0x5f415e20
Faulting module name: KERNELBASE.dll, version: 10.0.19041.572, time stamp: 0x1183946c
Exception code: 0xc0000602
Fault offset: 0x000000000010b65c

Faulting application name: PixInsight.exe, version: 1.8.8.7, time stamp: 0x5fdb8c78
Faulting module name: KERNELBASE.dll, version: 10.0.19041.662, time stamp: 0xec58f015
Exception code: 0xc0000602
Fault offset: 0x000000000010bd5c


Also saw occurrences of the crash in Qt5core.dll reported on a different thread.

I'm going to update to the latest Windows patches released yesterday, then update to 21H1, then try again.
 
Update #2: I applied the security patch and updated Windows to 21H1 (10.0.19043). The problem persists. I can supply a dump file via Dropbox to the PI team if it helps. BTW, since it's a common cause, I only have the default Windows Defender on this computer and no other security or management bloatware (i.e. nothing from Dell or Lenovo).
 
Last edited:
Update #3: I watched the pixinsight process with ProcMon from just before closing the main window (I had started it just before, without doing anything). In case it helps, below is the activity (basically, showing several dozens of threads ending) as well as the stack of the last thread. It's true that there's no guarantee that's the thread with the problem if they are closed in parallel, but maybe it helps (the stack contains KERNELBASE.DLL as well so it might be).

Any insight will be appreciated. At this time, my workaround is to empty those files periodically.

Thank you.



procmon.png
last thread.png
 
Update #4: the crash continues to occur on both computers that I have, after yesterday's Windows patches as well. Not having heard any comment on the matter, I set up a scheduled task to empty the CrashDumps directory every day.
 
Have a look here :
 
Thanks. I have an NVIDIA GTX 1080 card on the desktop but the built-in adapter on the laptop (Intel HD Graphics 620). Will post info on the other thread.
 
Back
Top