After installing the latest version as of yesterday 05/01/2022 - I am getting BSODs from Kerbal. This is the only mod I have updated in the last few days and I have been playing a TON of KSP over the last few days, so I can be certain these crashes coincide with the update to mechjeb.

I'm getting the WHEA_UNCORRECTABLE_ERROR message when I BSOD. This is a hardware code, but I dug into the crash dump and found it is being caused by KSP sending unusable data to the processor, causing the processor to hang and BSOD the entire PC. See copy of text from the crash report below.

Also, sort of unrelated - I've noticed burn times are 2-3 second late for some reason when I use the maneuver planner to execute nodes... like a 30 sec burn won't start until T - 12 to node... which is wrong and I end up screwing up my Dv calculations.

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb385c9eb2028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 30005

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: KSP_x64.exe

STACK_TEXT:
ffff8c00c8fef908 fffff8002f8b472a : 0000000000000124 0000000000000000 ffffb385c9eb2028 00000000b2000000 : nt!KeBugCheckEx
ffff8c00c8fef910 fffff8002d3315b0 : 0000000000000000 ffffb385c9eb2028 ffffb385c5340da0 ffffb385c9eb2028 : nt!HalBugCheckSystem+0xca
ffff8c00c8fef950 fffff8002f9b67fe : 0000000000000000 ffff8c00c8fef9f9 ffffb385c9eb2028 ffffb385c5340da0 : PSHED!PshedBugCheckSystem+0x10
ffff8c00c8fef980 fffff8002f8b6051 : ffffb385c9e88880 ffffb385c9e88880 ffffb385c5340df0 ffffb385c5340da0 : nt!WheaReportHwError+0x46e
ffff8c00c8fefa60 fffff8002f8b63c3 : 0000000000000001 ffffb385c5340df0 ffffb385c5340da0 0000000000000001 : nt!HalpMcaReportError+0xb1
ffff8c00c8fefbd0 fffff8002f8b62a0 : ffffb385c4eddbe8 41174d1100000001 0000000000000000 518b01458d4100e7 : nt!HalpMceHandlerCore+0xef
ffff8c00c8fefc20 fffff8002f8b64f1 : 0000000000000008 0000000000000001 0000000000000000 f749cccccccccccc : nt!HalpMceHandler+0xe0
ffff8c00c8fefc60 fffff8002f8b575b : 0000000000000000 0000000000000000 ffff8c00c8fefef0 458944bf4589ed33 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8c00c8fefc90 fffff8002f8b7fa5 : ffffb385c4eddbe8 001b20c53c8d4828 7d8948c74d894800 03d4870fd73b49ef : nt!HalpHandleMachineCheck+0x5f
ffff8c00c8fefcc0 fffff8002f90dab9 : 02d2850fc0854509 02ca850f40a80000 394810478b480000 48000002bd840f07 : nt!HalHandleMcheck+0x35
ffff8c00c8fefcf0 fffff8002f8069fa : 49000000e8b78d4c 894cd75d8948ce8b 48ffd916b9e8f775 b60f44378b704f8b : nt!KiHandleMcheck+0x9
ffff8c00c8fefd20 fffff8002f8066b7 : 0000000000000000 0000000000000000 000000480091f0a0 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff8c00c8fefe60 000001ca079b1a80 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
000000480091e9a0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x000001ca`079b1a80

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}

Followup: MachineOwner

Oh - followup - forgot to mention I use CKAN to manage my mods, so it is being loaded and handled via that app and not done manually by me/by hand.

Here's a list of all installed mods as well

Fixed as of v2.14.1.0-1127 released 5/11/22. No longer getting this issue. Appreciate ya!

The patches that went in had nothing to do with BSOD and wouldn't have fixed anything. WHEA_UNCORRECTABLE_ERROR is likely to be a hardware problem and probably something along the lines of bad overclocking. The "fix" may be that the CPU case is in a cooler environment or load is lower due to something else not running in the background or whatever. If its not overclocked then the CPU, RAM, motherboard may be bad, cheap, mismatched, etc. The problem likely surfaces with KSP running due to KSP hammering on the CPU core since it doesn't run physics on the GPU and the noodle rocket simulator aspect can't be parallelized.

Random googling for example:

https://linustechtips.com/topic/200161-whea_uncorrectable_error-while-overclocking-cpu/

"That particular BSOD notice means a failed overclock usually represented by either too high of a multiplier or not enough voltage."