BSOD – Windows 10 version 1703 and Windows Forms with multiple containers

Question

(This may not be the correct forum, but you have to start somewhere)

Since the Windows 10 Creator update we have been getting reports from various users that our application is causing a BSOD. 

Here is sample Event log entry …
Log Name:      Application
Source:        Windows Error Reporting
Date:          4/21/2017 2:50:50 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      
Description:
Fault bucket 0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 97fafc99-cb7a-4f41-b078-ba229b1fcf05

Problem signature:
P1: 7f
P2: 8
P3: ffff8c012c365af0
P4: ffff8c012d300fd0
P5: ffffe2884ba58f56
P6: 10_0_15063
P7: 0_0
P8: 256_1
P9: 
P10:

We found that when the webbrowser control uses Adobe Reader DC to display a PDF we would get the BSOD, only if the webbrowser control was embedded in deeply in other containers. We setup a project to embed 20 panels before adding the webbrowser control to reproduce the problem. The PDF will display correctly, it’s when you move the mouse into the area of the PDF that the BSOD will occur. 

There are other ways to get the same BSOD with the webbrowser control, so switching to Edge to display a PDF (which works) only fixes part of the problem. 

Did anything change in webbrowser control that would change the behavior of browser plugins? The BSOD occurs on multiple hardware platforms and virtual  environments. I have a mini and a full post-mortem dump available.

Answer 1

Hi greg,

>>Did anything change in webbrowser control that would change the behavior of browser plugins?

The Web Browser Control is - by default - perpetually stuck in IE 7 rendering mode. Even though we're now up to IE 11 and a reasonably HTML5 compatible browser, the Web Browser Control always uses the IE 7 rendering engine by default. This is because the original versions of the ActiveX control used this mode and for backwards compatibility the Control continues this outdated and very HTML5 unfriendly default.

I suggest you can refer to the following document to learn more about web control compatibility:

Controlling WebBrowser Control Compatibility

Web Browser Control & Specifying the IE Version

Hope it helps!

Best Regards,

Stanly

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 2

Stanly,

I've been setting the webbrowser control to run in the current IE release since IE9. Most of the testing I've done so far has been with setting the webbrowser control to IE11. 

Greg

Answer 3

Stanly,

First a big thank you! Your reply got me thinking, so I tried a different test. The BSOD is not because of the webbroser control or Adobe Reader, but the number of embedded windows. I just embedded 46 panels into a split container and got the same BSOD.

Greg

Answer 4

The trick to reproducing this problem is to create a set of nested panels, then put the top level panel on the form, move the mouse into the panel area and wait a couple of seconds for the BSOD. 

Answer 5

Hi greg,

>>I just embedded 46 panels into a split container and got the same BSOD.

Sorry there are too many panels in the container,so have you solved this problem?

Best Regards,

Stanly

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 6

No, I have not solved the problem. We have a complex application with lots of user controls and 3rd party controls. The example of nesting the panels was just a way emulate what is going on in the application. This application has been working fine until the last update to Windows 10.

Answer 7

Hi greg,

>>This application has been working fine until the last update to Windows 10.

Perhaps there are some factors of windows 10 that load this issue instead of the webBrowser or another controls, Have you tried to revert to the previous version? Or run the application on another computer.

Best Regards,

Stanly

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 8

I have a similar issue since the update to 1703. 

At first i thought it was a driver problem but it only happens when a lot of containers are present on the screen. As soon as they get focus (mouseover) we get an BSOD.

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffb68024676af0
Arg3: ffffb6802ea2d000
Arg4: ffffb15b6c026c0b

................................

TRAP_FRAME:  ffffb68024676af0 -- (.trap 0xffffb68024676af0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb6802ea2d028 rbx=0000000000000000 rcx=ffffe186b846a080
rdx=ffffb6802ea2d040 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb15b6c026c0b rsp=ffffb6802ea2d000 rbp=ffffb6802ea2d4e0
 r8=ffffb6802ea2d038  r9=ffffb6802ea2d048 r10=ffffb119800beab0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
win32kbase!IsRestricted+0x1b:
ffffb15b`6c026c0b ff1597731200    call    qword ptr [win32kbase!_imp_PsReferenceImpersonationToken (ffffb15b`6c14dfa8)] ds:ffffb15b`6c14dfa8={nt!PsReferenceImpersonationToken (fffff802`d6b32620)}
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: a22

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

CPU_MICROCODE: 6,3d,4,0 (F,M,S,R)  SIG: 23'00000000 (cache) 23'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  saplogon.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  XXXXXX

ANALYSIS_SESSION_TIME:  05-22-2017 15:20:12.0146

ANALYSIS_VERSION: 10.0.15063.137 x86fre

STACK_OVERFLOW: Stack Limit: ffffb6802ea2d000. Use (kF) and (!stackusage) to investigate stack usage.

STACKUSAGE_FUNCTION: The function at address 0xffffb15b6bc72ad3 was blamed for the stack overflow. It is using 15552 bytes of stack total in 36 instances (likely recursion).

FOLLOWUP_IP: 
win32kfull!xxxDCEWindowHitTest2Internal+803
ffffb15b`6bc72ad3 488bd8          mov     rbx,rax

STACK_COMMAND:  .trap 0xffffb68024676af0 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  5208cf8fcfb29666f1f13a11f080009f59aa52bc

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  cc27ae4eebe42f9e2e5783a66019522c251ea881

THREAD_SHA1_HASH_MOD:  acd713acb63c604bd6b7d650694f8d13e23a9acd

FAULT_INSTR_CODE:  ffd88b48

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32kfull!xxxDCEWindowHitTest2Internal+803

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.15063.296

BUCKET_ID_FUNC_OFFSET:  803

FAILURE_BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

PRIMARY_PROBLEM_CLASS:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

TARGET_TIME:  2017-05-22T12:19:54.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-04-28 01:52:30

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  865

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_stack_usage_recursion_win32kfull!xxxdcewindowhittest2internal

FAILURE_ID_HASH:  {bf1823fb-da15-f301-8ca8-5d738570a28e}

Kind regards
Stefan

Answer 9

Hi, similar problem has been occured on my computer after 1703 update.

It occur when i am pointing at adobe preview form by the mouse.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8032a1dfe70
Arg3: ffffa800fc8a3fd0
Arg4: fffff80327f07dd4

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER:  Hewlett-Packard

SYSTEM_PRODUCT_NAME:  HP ProBook 430 G2

SYSTEM_SKU:  N0Z21EA#AKD

SYSTEM_VERSION:  A3009DD10303

BIOS_VENDOR:  Hewlett-Packard

BIOS_VERSION:  M73 Ver. 01.42

BIOS_DATE:  09/26/2016

BASEBOARD_MANUFACTURER:  Hewlett-Packard

BASEBOARD_PRODUCT:  2246

BASEBOARD_VERSION:  KBC Version 59.23

DUMP_TYPE:  1

BUGCHECK_P1: 8

BUGCHECK_P2: fffff8032a1dfe70

BUGCHECK_P3: ffffa800fc8a3fd0

BUGCHECK_P4: fffff80327f07dd4

BUGCHECK_STR:  0x7f_8

TRAP_FRAME:  fffff8032a1dfe70 -- (.trap 0xfffff8032a1dfe70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00008551b28c1e79
rdx=0000000000000034 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80327f07dd4 rsp=ffffa800fc8a3fd0 rbp=ffffa800fc8a49d0
 r8=ffffa800fc8a4b58  r9=0000000000000001 r10=fffff80327f07b80
r11=fffff80327bf71f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!NtQueryInformationProcess+0x254:
fffff803`27f07dd4 e837e3ccff      call    nt!_security_check_cookie (fffff803`27bd6110)
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 893

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3d

CPU_STEPPING: 4

CPU_MICROCODE: 6,3d,4,0 (F,M,S,R)  SIG: 22'00000000 (cache) 22'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  Foonsy.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  CHUDINIPC

ANALYSIS_SESSION_TIME:  05-24-2017 10:00:32.0941

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_OVERFLOW: Stack Limit: ffffa800fc8a4000. Use (kF) and (!stackusage) to investigate stack usage.

STACKUSAGE_FUNCTION: The function at address 0xFFFFC94C3FD22AD3 was blamed for the stack overflow. It is using 12960 bytes of stack total in 30 instances (likely recursion).

FOLLOWUP_IP:
win32kfull!xxxDCEWindowHitTest2Internal+803
ffffc94c`3fd22ad3 488bd8          mov     rbx,rax

STACK_TEXT:  
ffffa800`fc8a3fd0 fffff803`27bf7213 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryInformationProcess+0x254
ffffa800`fc8a48e0 fffff803`27bef4f0 : ffffc94c`3fd1e65e 00000000`00000000 ffffc94c`3fd1ebb1 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
ffffa800`fc8a4ae8 ffffc94c`3fd1e65e : 00000000`00000000 ffffc94c`3fd1ebb1 00000000`00000000 ffffa800`fc8a5140 : nt!KiServiceLinkage
ffffa800`fc8a4af0 ffffc94c`3fd1dfdf : ffffc907`c008bd30 fffff803`27f07dd9 00000000`00000000 ffffcc84`c9948f50 : win32kfull!xxxHkCallHook+0x9e
ffffa800`fc8a4c30 ffffc94c`3fd1d500 : 00000000`00000000 00000000`00000000 00000000`01f603a8 fffff803`fffffffe : win32kfull!xxxCallHook2+0x36f
ffffa800`fc8a4e80 ffffc94c`3fd22c14 : ffffc907`00000000 ffffc907`c0831800 00000000`00000000 00000000`01f603a8 : win32kfull!xxxSendTransformableMessageTimeout+0x1c0
ffffa800`fc8a4fe0 ffffc94c`3fd2227b : 00000000`00000000 00000000`6caaec90 00000000`1d58ef94 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x944
ffffa800`fc8a5190 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a52f0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a51f0 ffffc94c`3fd2227b : ffffc907`00000030 fffff803`27f07dd9 ffffa800`fc8a5478 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a53a0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a5500 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a5400 ffffc94c`3fd2227b : ffffa800`fd8f2000 00000000`00000002 ffffc907`c008bd70 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a55b0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a5710 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a5610 ffffc94c`3fd2227b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a57c0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a5920 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a5820 ffffc94c`3fd2227b : 00000000`60863be3 00007ff8`1c7d52c0 ffffc907`c3c885e0 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a59d0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a5b30 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a5a30 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffa800`fc8a5cb8 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a5be0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a5d40 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a5c40 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a5df0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a5f50 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a5e50 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffc907`c3c885e0 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6000 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a6160 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a6060 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffa800`fc8a62e8 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6210 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a6370 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a6270 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffffff`ffb3b4c0 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6420 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a6580 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a6480 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6630 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a6790 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a6690 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 fffff7b5`c0001910 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6840 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a69a0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a68a0 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffc907`c008bd70 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6a50 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a6bb0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a6ab0 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6c60 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a6dc0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a6cc0 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffc907`c3c885e0 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a6e70 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a6fd0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a6ed0 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`000003e8 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a7080 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a71e0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a70e0 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffa800`fc8a7a40 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a7290 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a73f0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a72f0 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffcc84`cc499080 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a74a0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a7600 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a7500 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffa800`fc8a7a68 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a76b0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a7810 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a7710 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`0000001c 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a78c0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a7a20 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a7920 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a7ad0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a7c30 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a7b30 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a7ce0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a7e40 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a7d40 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000012 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a7ef0 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8050 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a7f50 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8100 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8260 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a8160 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000008 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8310 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8470 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a8370 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffa800`fc8a87c0 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8520 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8680 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a8580 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8730 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8890 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a8790 ffffc94c`3fd2227b : 00000000`00000000 ffffc94c`3fd22299 ffffcc84`ccd09dd8 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8940 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8aa0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a89a0 ffffc94c`3fd2227b : 00000000`00000001 ffffc94c`40e8a32b 00000000`00000000 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8b50 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8cb0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a8bb0 ffffc94c`3fd2227b : 00000000`00000200 00000000`00001000 00000000`00000002 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8d60 ffffc94c`3fd22ad3 : 000001f6`000003a8 000001f6`000003a8 000001f6`000003a8 ffffa800`fc8a8ec0 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a8dc0 ffffc94c`3fd2227b : ffffc907`c2d3e430 ffffa800`fc8a9b80 ffffc907`c3c88380 00000000`00000001 : win32kfull!xxxDCEWindowHitTest2Internal+0x803
ffffa800`fc8a8f70 ffffc94c`3fd10d56 : 000001f6`000003a8 000001f6`000003a8 00000000`00000200 ffffa800`fc8a9b80 : win32kfull!xxxDCEWindowHitTestIndirect+0x12b
ffffa800`fc8a8fd0 ffffc94c`3fd1bcbe : ffffc907`c3c88380 ffffa800`fc8a9b80 ffffc907`c3c88380 00000000`00000012 : win32kfull!xxxScanSysQueue+0xa96
ffffa800`fc8a9890 ffffc94c`3fd1afa6 : ffffa800`fc8a9a48 00000000`0000c240 ffffa800`00000000 ffffa800`fbf992e8 : win32kfull!xxxRealInternalGetMessage+0xc9e
ffffa800`fc8a9a00 fffff803`27bf7213 : ffffcc84`cc499080 00000000`1d28e5c8 ffffa800`fc8a9aa8 00000000`1d58efa0 : win32kfull!NtUserPeekMessage+0x96
ffffa800`fc8a9a90 00000000`531118a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1d28e5a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x531118a4


STACK_COMMAND:  .trap 0xfffff8032a1dfe70 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  167a049658fde57c647f0b699d8a706a6737f430

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0d356837f9240d2ce2cc4229724568a6254f1960

THREAD_SHA1_HASH_MOD:  b091b2b50dd899763f7b9df7f0d5b623c8890a6a

FAULT_INSTR_CODE:  ffd88b48

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  win32kfull!xxxDCEWindowHitTest2Internal+803

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  win32kfull.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: win32kfull

BUCKET_ID_FUNC_OFFSET:  803

FAILURE_BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

PRIMARY_PROBLEM_CLASS:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

TARGET_TIME:  2017-05-23T13:51:14.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-04-28 01:52:30

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME: 696

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_stack_usage_recursion_win32kfull!xxxdcewindowhittest2internal

FAILURE_ID_HASH:  {bf1823fb-da15-f301-8ca8-5d738570a28e}

Followup:     MachineOwner
---------

Answer 10

We are also having a similar issue with numerous controls docked inside panels, splitcontainers and flowpanels.

When scrolling up/down the flowpanels we BSOD.  Again this has only happened to users on the Creators Update version - all previous version of Win 10, 8.1,8 and 7 work fine.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, fffff802c8264e70, ffff84812427f000, ffffafb59e13d84f}

Probably caused by : win32kfull.sys ( win32kfull!xxxDCEWindowHitTest2Internal+803 )

Followup:     MachineOwner
---------

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff802c8264e70
Arg3: ffff84812427f000
Arg4: ffffafb59e13d84f

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.15063.296 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  innotek GmbH

VIRTUAL_MACHINE:  VirtualBox

SYSTEM_PRODUCT_NAME:  VirtualBox

SYSTEM_VERSION:  1.2

BIOS_VENDOR:  innotek GmbH

BIOS_VERSION:  VirtualBox

BIOS_DATE:  12/01/2006

BASEBOARD_MANUFACTURER:  Oracle Corporation

BASEBOARD_PRODUCT:  VirtualBox

BASEBOARD_VERSION:  1.2

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: 8

BUGCHECK_P2: fffff802c8264e70

BUGCHECK_P3: ffff84812427f000

BUGCHECK_P4: ffffafb59e13d84f

BUGCHECK_STR:  0x7f_8

STACK_OVERFLOW: Stack Limit: ffff84812427f000. Use (kF) and (!stackusage) to investigate stack usage.

STACKUSAGE_FUNCTION: The function at address 0xffffafb59e142ad3 was blamed for the stack overflow. It is using 15984 bytes of stack total in 37 instances (likely recursion).

FOLLOWUP_IP: 
win32kfull!xxxDCEWindowHitTest2Internal+803
ffffafb5`9e142ad3 488bd8          mov     rbx,rax

CPU_COUNT: 1

CPU_MHZ: 8f7

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 0'00000000 (cache) 0'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  Infinity.Conso

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-SO3MB8I

ANALYSIS_SESSION_TIME:  05-24-2017 12:26:24.0527

ANALYSIS_VERSION: 10.0.15063.0 amd64fre

STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  84ccd5710f359b6836c6c40f8c7535dfa3ee5bf2

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ef380f05c5be9d232ea77ec7e7e2b78d55a18235

THREAD_SHA1_HASH_MOD:  05cee09b5941fe9f6e461aee30a08979f493b687

FAULT_INSTR_CODE:  ffd88b48

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32kfull!xxxDCEWindowHitTest2Internal+803

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.15063.296

BUCKET_ID_FUNC_OFFSET:  803

FAILURE_BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

BUCKET_ID:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

PRIMARY_PROBLEM_CLASS:  0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal

TARGET_TIME:  2017-05-24T11:18:55.000Z

OSBUILD:  15063

OSSERVICEPACK:  296

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-04-28 00:52:30

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.15063.296

ANALYSIS_SESSION_ELAPSED_TIME:  4b1

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7f_8_stack_usage_recursion_win32kfull!xxxdcewindowhittest2internal

FAILURE_ID_HASH:  {bf1823fb-da15-f301-8ca8-5d738570a28e}

Followup:     MachineOwner
---------

kd> !stackusage
Stack Usage By Function
=================================================================================

      Size     Count  Module
0x00003E70        37  win32kfull!xxxDCEWindowHitTest2Internal
0x00000E40        38  win32kfull!xxxDCEWindowHitTestIndirect
0x000008C0         1  win32kfull!xxxScanSysQueue
0x000001B0         1  win32kfull!xxxDCEWindowHitTest2Internal
0x00000170         1  win32kfull!xxxRealInternalGetMessage
0x00000160         1  win32kfull!xxxSendTransformableMessageTimeout
0x00000090         1  win32kfull!NtUserPeekMessage
0x00000010         2  win32kfull!xxxSendMessageToClient

Total Size: 0x00005A90


Stack Usage By Module
=================================================================================

      Size     Count  Module
0x00005A90        82  win32kfull

Total Size: 0x00005A90

Answer 11

We have the same issue in a C# application making heavy use of nesting WinForms controls. The application exists since Vista and .NET 3.5 and was continuously updated (currently runs against .NET 4.5, built with VS 2015/2017 and runs fine on Windows 10 Anniversary).

Up until Windows 7 there were no problems, but starting with Windows 8 we experienced first issues regarding the nesting level. We thus limited the nesting level to 35 by displaying a message that the user should rather open a new window than drill down further in the current window. So far this has mitigated the problem (there are multiple windows however). The OP mentions 46 nested panels which seem like a ridiculous number. The question might be why would anyone do that? But consider that you reach a high amount of nesting with a couple of nested tab controls, split containers and group boxes in addition to a few panels. With the Windows 10 creators update a nesting level of 25 had to be chosen in order to avoid BSODs.

Also, it's a really severe error since a BSOD is about the worst that can happen, not just for the one application, but also for all other applications that are running. And this BSOD is completely and easily reproducible. It would be rather easy for Microsoft to track down the issue. Has this been reported to the developers? Is there going to be a fix? Do we have to expect even worse problems in the future? Is this even taken seriously?

Answer 12

I found a hotfix for Windows 8 for a similar issue:

https://support.microsoft.com/en-us/help/2870007/-0x0000007f-stop-error-when-you-move-the-mouse-pointer-over-nested-windows-in-windows-8-or-windows-server-2012

Source: https://stackoverflow.com/questions/44481376/nested-control-bluescreen-with-latest-windows-creators-update

But i dont think that it will work for Windows 10 Creators Update ;)

Kind regards
Stefan

Answer 13

Hi together,

I have a similiar issue in win 10 1703 and a SAP Transaktion SEGW.

if I look into resp double click the Mapping of the Method GetEntity I got Blue Screen with

Stillstandcode: UNEXPECTED KERNEL MODE TRAP.
Fehlerursache win32kfull.sys.

Have anybody an idea what could be done to solve these error?

if I look into a MiniDump file I see the following:

for File 1:

##########################

Microsoft (R) Windows Debugger Version 10.0.15063.400 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\062817-8406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Error: Set symbol search path attempts to access 'c:\windows\i386' failed: 0x2 - Das System kann die angegebene Datei nicht finden.

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Error                                          c:\windows\i386

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`7c48c000 PsLoadedModuleList = 0xfffff803`7c7d85a0
Debug session time: Wed Jun 28 09:09:41.570 2017 (UTC + 2:00)
System Uptime: 0 days 16:44:33.248
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {8, fffff8037e7d8e70, ffff8881f5046fc0, fffff11ae807249f}

Probably caused by : win32kfull.sys ( win32kfull!xxxDCEWindowHitTest2Internal+803 )

Followup:     MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff8037e7d8e70
Arg3: ffff8881f5046fc0
Arg4: fffff11ae807249f

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.15063.413 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  Latitude E7440

SYSTEM_SKU:  05CB

SYSTEM_VERSION:  00

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  A21

BIOS_DATE:  05/08/2017

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  0RYCC9

BASEBOARD_VERSION:  A00

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: 8

BUGCHECK_P2: fffff8037e7d8e70

BUGCHECK_P3: ffff8881f5046fc0

BUGCHECK_P4: fffff11ae807249f

BUGCHECK_STR:  0x7f_8

STACK_OVERFLOW: Stack Limit: ffff8881f5047000. Use (kF) and (!stackusage) to investigate stack usage.

STACKUSAGE_FUNCTION: The function at address 0xfffff11ae8072af3 was blamed for the stack overflow. It is using 16416 bytes of stack total in 38 instances (likely recursion).

FOLLOWUP_IP:
win32kfull!xxxDCEWindowHitTest2Internal+803
fffff11a`e8072af3 488bd8          mov     rbx,rax

CPU_COUNT: 4

CPU_MHZ: a22

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 1D'00000000 (cache) 1D'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  saplogon.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  NB-POLIWODA

ANALYSIS_SESSION_TIME:  06-28-2017 10:57:38.0853

ANALYSIS_VERSION: 10.0.15063.400 x86fre

STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  de7ef96dcbd1e0e24984d259df2b3329ddee07c7

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  63bae0fee7619561b8fbee07b6a1a0e0aae52acd

THREAD_SHA1_HASH_MOD:  05cee09b5941fe9f6e461aee30a08979f493b687

FAULT_INSTR_CODE:  ffd88b48

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32kfull!xxxDCEWindowHitTest2Internal+803

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  104c5f6b

IMAGE_VERSION:  10.0.15063.349

BUCKET_ID_FUNC_OFFSET:  803

FAILURE_BUCKET_ID:  OLD_IMAGE_win32kfull.sys

BUCKET_ID:  OLD_IMAGE_win32kfull.sys

PRIMARY_PROBLEM_CLASS:  OLD_IMAGE_win32kfull.sys

TARGET_TIME:  2017-06-28T07:09:41.000Z

OSBUILD:  15063

OSSERVICEPACK:  413

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-06-03 10:53:36

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.15063.413

ANALYSIS_SESSION_ELAPSED_TIME:  86e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:old_image_win32kfull.sys

FAILURE_ID_HASH:  {82623c84-b248-63a9-bf6b-8baba6170086}

Followup:     MachineOwner
---------

#####################

for File 2:

##################

Microsoft (R) Windows Debugger Version 10.0.15063.400 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\062717-8234-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Error: Set symbol search path attempts to access 'c:\windows\i386' failed: 0x2 - Das System kann die angegebene Datei nicht finden.

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Error                                          c:\windows\i386

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`5541b000 PsLoadedModuleList = 0xfffff801`557675a0
Debug session time: Tue Jun 27 16:24:39.254 2017 (UTC + 2:00)
System Uptime: 0 days 0:01:52.919
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...............
GetContextState failed, 0x8007001E
CS descriptor lookup failed
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get program counter
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, fffff801577d8e70, ffffe7814f4a6f60, ffff960ab727231e}

GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup:     MachineOwner
---------

GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
0: kd> !analyze -v
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get program counter
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff801577d8e70
Arg3: ffffe7814f4a6f60
Arg4: ffff960ab727231e

Debugging Details:
------------------

GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.15063.413 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  Dell Inc.

SYSTEM_PRODUCT_NAME:  Latitude E7440

SYSTEM_SKU:  05CB

SYSTEM_VERSION:  00

BIOS_VENDOR:  Dell Inc.

BIOS_VERSION:  A21

BIOS_DATE:  05/08/2017

BASEBOARD_MANUFACTURER:  Dell Inc.

BASEBOARD_PRODUCT:  0RYCC9

BASEBOARD_VERSION:  A00

DUMP_TYPE:  2

BUGCHECK_P1: 8

BUGCHECK_P2: fffff801577d8e70

BUGCHECK_P3: ffffe7814f4a6f60

BUGCHECK_P4: ffff960ab727231e

BUGCHECK_STR:  0x7f_8

BAD_STACK_POINTER:  0000000000000000

CPU_COUNT: 4

CPU_MHZ: a22

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 1D'00000000 (cache) 1D'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  ZEROED_STACK_0x7f_8

PROCESS_NAME:  saplogon.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  NB-POLIWODA

ANALYSIS_SESSION_TIME:  06-28-2017 11:20:22.0373

ANALYSIS_VERSION: 10.0.15063.400 x86fre

STACK_TEXT:  
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  ZEROED_STACK_0x7f_8

PRIMARY_PROBLEM_CLASS:  ZEROED_STACK

FAILURE_BUCKET_ID:  ZEROED_STACK_0x7f_8

TARGET_TIME:  2017-06-27T14:24:39.000Z

OSBUILD:  15063

OSSERVICEPACK:  413

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-06-03 10:53:36

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.15063.413

ANALYSIS_SESSION_ELAPSED_TIME:  14f2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:zeroed_stack_0x7f_8

FAILURE_ID_HASH:  {bd1940d8-ed36-69da-df17-1bf11350d0e6}

Followup:     MachineOwner
---------

GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E

Answer 14

The solution for me were some windows and dell updates that were available today 20170628.

After rebooting including the installation of the updates, the error do not appear anymore.

Answer 15

I have a similar problem with MSSQL Workbench.  One screen which is the users panel causes the BSOD, windows 64, I have not had the update from MS that fixes this problem.  All other screens are fine, no hardware added, or taken away, Windows 10 64 completely up-to-date.  The only change was 1703 update and KB4022405, and a couple of security updates for Flash and one for creative.  For me it started on the 23/6.

Answer 16

The 1703 update happened on the 16/6, however I had not opened workbench until 23/6 so it could have been the other updates, but there is very little information about those updates do.

Answer 17

I could not restore back to prior to 1703 since my creating restore points was not activated.  See https://www.tenforums.com/backup-restore/20397-cant-enable-system-restore.html to fix this and get it activated.

Really Microsoft can you come up better defaults for

 Windows 10 Pro, 1703,15063.413.  64 bit.

Answer 18

Some of our customers also reported this issue. I was able to reproduced it in a laptop with OS build 15063.413. Then I updated to 15063.447 and it solved the problem.

https://support.microsoft.com/en-us/help/4022716/windows-10-update-kb4022716

this update states that fixed this problem:

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

Best regards,

Nuno Pereira