Joplin blue screens Windows 11 on startup

Support
1

Operating system

Windows

Joplin version

3.2.12

Desktop version info

Joplin 3.2.12 (prod, win32)

Client ID: 4d8e2fda9d4d4f1398d8994cca0374de
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: d6f1ca4

Backup: 1.4.2
Freehand Drawing: 2.14.0

What issue do you have?

Joplin seems to blue screen my Windows on this version for some reason on startup. I can replicate this by either starting Joplin in startup apps or start Joplin manually very near startup. I'm on Joplin cloud. I have not had this problem before in Joplin. Sometimes it happens and sometimes it doesn't. Removing and reinstalling doesn't solve the problem. I think the blue screen happens after

2025-01-29 22:57:20: DecryptionWorker: cannot start because no master key is currently loaded.

Log file

log.txt (2.26 MB)

2

Does the issue still happen if Joplin starts in safe mode? (Help > Toggle safe mode).

1 Like
3

Would you mind posting the blue screen information here? Like the Stop Code and What failed

1 Like
4

Two errors and one critical error appear in Event Viewer:

Error	29/01/2025 22.59.05	stornvme	11	None The driver detected a controller error on \Device\RaidPort1.

Error	29/01/2025 22.59.06	volmgr	161	None Dump file creation failed due to error during dump creation. BugCheckProgress was: 0x00040049

Critical	29/01/2025 22.59.06	Kernel-Power	41	(63) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

These three seem to appear every time Joplin causes a blue screen on startup.

I will try if the issue persists on safe mode.

edit: typo

5

Issue still happens in safe mode.

6

Are you using RAID? If so, what type of RAID are you using?
I don't know if chkdsk /F can resolve this.

7

I found several posts about this error

https://www.reddit.com/r/framework/comments/yq6f6w/the_driver_detected_a_controller_error_on/

It seems like the root cause could be the SSD driver. Could you please try the solutions in these posts and check if the issue persists?

1 Like
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.