I have a mini and a full post-mortem dump available. 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.ĭid anything change in webbrowser control that would change the behavior of browser plugins? The BSOD occurs on multiple hardware platforms and virtual environments. The PDF will display correctly, it’s when you move the mouse into the area of the PDF that the BSOD will occur.
We setup a project to embed 20 panels before adding the webbrowser control to reproduce 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. Since the Windows 10 Creator update we have been getting reports from various users that our application is causing a BSOD.įault bucket 0x7f_8_STACK_USAGE_RECURSION_win32kfull!xxxDCEWindowHitTest2Internal, type 0Ĭab Id: 97fafc99-cb7a-4f41-b078-ba229b1fcf05 (This may not be the correct forum, but you have to start somewhere)
