Windows 10: Windows 11 WinForms BSOD kernel crash - UNEXPECTED_KERNEL_MODE_TRAP

In 2017 I had described an issue in Windows 10 where "the kernel started crashing with BSOD very consistently after performing certain UI actions in our Eclipse SWT desktop application". This issue was fixed in KB4022716 which "Addressed issue Error 0x7F with Windows Forms WinForms that causes the system to crash after upgrading to the Creators Update." For reference, this was my original post: https://answers.microsoft.com/en-us/windows/forum/all/windows-10-creators-update-bsod-kernel-crash/b8ec01a2-4086-4048-8557-417eb79ce813Now, the exact same issue is happening again in Windows 11.

:)

 

Windows 10 Pro 2004 crash with BSOD "UNEXPECTED_KERNEL_MODE_TRAP(0x0000007f)"

When having many layers in a Windows Forms Application and click this WinForm Application,
Windows 10 Pro 2004(19041.488) always crashes.
BSOD error code is UNEXPECTED_KERNEL_MODE_TRAP(0x0000007f)

And this problem do not happen on Windows 10 Pro 1909,1903 and so on.

When Creators Update had same problem,

but this problem was fixed by update : "https://support.microsoft.com/en-us/help/4022716/windows-10-update-kb4022716"

> Addressed issue (Error 0x7F) with Windows Forms (WinForms) that causes the system to crash after upgrading to the Creators Update.

I think this 2004's problem is similar with this Creators Update's problem.

When Creators Update , some website report this problem.

> Windows 10 Creators Updates breaks WinForms apps / BSOD
> Redirecting

I had already post this problem to MS feedback hub ...

Our Windows Form application is legacy and have deep layers,
So it is difficult to remake this one ...

Anyone have a good solution? Please help us .

 

Windows 10 Creators Update BSOD kernel crash - UNEXPECTED_KERNEL_MODE_TRAP

Hello again...

today I did some tests also using InsidePreview Build 16215.1000.

I could not force BSOD with our Winform-Apps so far, but using Powershellscript mentioned by Marc Lasson I still keep getting BSOD. With Powershellscript I always get win32kfull.sys as crash address.

It also seems Adress is slightliy changing depending on how many iterations you set in powershellscript for nesting Panels (e.g. 45 iterations -> win32kfull.sys+72310, 35 iterations-> win32kfull.sys+6de00).

On my production PC running 15063.413 I get ntoskernel with our Winform Appllikation and win32kfull.sys when crashing via powershellscript.

Then I did a sample Application in VB.net (Win 10 Build 15063.413) which does the same nesting of Panels as in powershellscript -> get's me back to my "good old" crash Address ntoskrnl.exe+16c3f0.

Crash started by Panel Nr. 29.

I'm for sure there's got to be a secret registry key "MaxNoOfNestedPanelsAfterThatBSODHasToOccurJustForFun" ;-)

Any help is highly appreciated!

Best regards, Michael

BTW: I really enjoy "GSOD" of InsidePreview, it gives me a much better feeling but BSOD ;-)

 

Windows 10 Creators Update BSOD kernel crash - UNEXPECTED_KERNEL_MODE_TRAP

Hi Bernat,

Blue screen of death associated with UNEXPECTED_KERNEL_MODE_TRAP error can be related to hard drive corruption. We suggest that you scan and repair blue screen errors by running "Check Disk" command (chkdsk) by following the steps below:

• Click on Start.
  
• Type "command" in the Search box.
  
• While holding CTRL + Shift on your keyboard, press Enter. You will be prompted with a permission dialog box.
• Click Yes. A black box will open with a blinking cursor.
• Type "chkdsk /f" and press Enter. It will begin scanning for hard disk corruption that could be causing 0x7F stop error.
• Follow the on-screen instructions.

You can also refer to this
article to resolve blue screen errors in Windows 10.

Let us know if you need further assistance.