BSOD - Windows 10版本1703和带有多个容器的Windows窗体 [英] BSOD – Windows 10 version 1703 and Windows Forms with multiple containers
问题描述
（这可能不是正确的论坛，但你必须从某处开始）
自从Windows 10 Creator更新以来，我们一直在从我们的应用程序导致BSOD的各种用户。
$
以下是示例事件日志条目...
日志名称：   申请
来源：     Windows错误报告
日期：       4/21/2017 2:50:50 PM
活动编号：   1001
任务类别：无
级别：      信息
关键词：   经典
用户：       N / A
电脑：  
$
描述：
故障桶0x7f_8_STACK_USAGE_RECURSION_win32kfull！xxxDCEWindowHitTest2Internal，类型0
事件名称：BlueScreen
响应：不适用
驾驶室ID：97fafc99-cb7a-4f41-b078-ba229b1fcf05
问题签名：
P1 ：7f
P2：8
P3：ffff8c012c365af0
P4：ffff8c012d300fd0
P5：ffffe2884ba58f56
P6：10_0_15063
P7：0_0
P8：256_1
P9：
P10 ：
$
我们发现当webbrowser控件使用Adobe Reader DC显示PDF时，只有当webbrowser控件深深地嵌入其他容器中时我们才能获得BSOD 。我们设置了一个项目，在添加webbrowser控件之前嵌入了20个面板，以重现
问题。 PDF将正确显示，当您将鼠标移动到将发生BSOD的PDF区域时。
还有其他方法可以获得相同的信息。具有web浏览器控件的BSOD，因此切换到Edge以显示PDF（有效）只能修复部分问题。
webbrowser控件中的任何更改都会改变行为浏览器插件？ BSOD出现在多个硬件平台和虚拟环境中。我有一个小型和完整的验尸转储。
嗨greg，
>> webbrowser控件中是否有任何更改会改变浏览器插件的行为？
Web浏览器控件 - 默认情况下 - 永久停留在IE 7渲染模式下。尽管我们现在已经升级到IE 11和一个合理的HTML5兼容浏览器，但Web浏览器控件总是默认使用IE 7渲染引擎。这是因为ActiveX控件的
原始版本使用了这种模式，并且为了向后兼容性，Control继续这种过时且非常HTML5不友好的默认值。
我建议你可以参考以下文档以了解有关Web控制兼容性的更多信息：
希望它有所帮助！
最好的问候，
Stanly
(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.
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
这篇关于BSOD - Windows 10版本1703和带有多个容器的Windows窗体的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
