20080817 wof bsod
http://www.yippeesoft.com

抓狂
安装SP1后，原来的WPF程序一运行就蓝屏死机自动重启

倒腾半天，更新显卡驱动，更新 DIRECTX9后 终于可以正常运行了

Intel英特尔G35/945G/945GZ/946GZ/G965/Q963/Q965/940GML/943GML/945GM/945GMS/GM965系列芯片组视频部分(Intel Graphics Media Accelerator)最新驱动14.31.0.4859官方正式版For WinXP（2007年8月17日发布）

http://en.wikipedia.org/wiki/Windows_Presentation_Foundation
Windows Presentation Foundation
From Wikipedia, the free encyclopedia

Windows XP蓝屏解决技巧大揭秘

http://blogs.msdn.com/dwayneneed/archive/2007/04/26/multithreaded-ui-hostvisual.aspx
Multithreaded UI: HostVisual
Background: The WPF Threading Model

In general, objects in WPF can only be accessed from the thread that created them.  Sometimes this restriction is confused with the UI thread, but this is not true, and it is perfectly fine for objects to live on other threads.  But it is not generally possible to create an object on one thread, and access it from another.  In almost all cases this will result in an InvalidOperationException, stating that “The calling thread cannot access this object because a different thread owns it.”

http://msdn.microsoft.com/en-us/library/aa970912(VS.85).aspx#registry_settings
Graphics Rendering Registry Settings

http://channel9.msdn.com/forums/Coffeehouse/259706-Stats-on-Windows-BSOD-/
WPF for programs targeting CLR, but what about native programs, what about MIL? I prefer the CLR path, but am still interested in possible improvements for native applications. It seems to be that programming against scene graphs is a more structured and manageable approach that brings many benefits.

http://softwarecommunity.intel.com/isn/Community/en-US/forums/thread/30255443.aspx
Latest Intel GMA X3100 drivers FREEZE/BSOD running EVE Online (with software T&L enabled)

DirectX End-User Runtimes (June 2008) – 简体中文

http://www.driversdown.com/drivers/24608.shtml
IBM ThinkPad Intel X3100(GL960/GM965) Driver 7.14.10.1244 Windows Vista x32

Display driver (Intel 940GML, 945GM, GL960, GM965 – 950, X3100) for Windows XP, 2000 – ThinkPad
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-67838

Over the last month, I have had several blue screens when running Cider.  It has occurred relatively infrequently (5 times). My computer is a Lenovo/IBM Thinkpad T43p runnning in a dual monitor mode with a shared desktop. For a workaround,  I have made the XML editor my default XAML view and I have not experienced any blue screens.  Has anybody else had the problem?

Steve

Since Cider uses WPF and WPF uses DirectX this is more likely caused by video driver bugs. Maybe a driver update will solve the problem (if available).

I have posted this issue over in the WFF forums in response to some user who was reporting a BSOD when using the WWF designer in VS2008 (which is built using WPF):

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2820697&SiteID=1

I have a simiar problem when using the just the regular WPF designer in VS 2008.

Here are the steps which eventually cause a BSOD:
1) Create new WPF app project
2) Open up Window1.xaml in designer mode ( the more complex the XAML the better…)
3) Move VS window to 2nd monitor
4) Press Ctrl+Alt+Del to switch to windows security screen (note this has a 5-10 second delay before it responds)
5) Return to VS and witness the WPF rendering is corrupt. Moving it between primary and secondary monitor make the coruption come and go,
6) Exiting VS will usually initiate the BSOD

This BSOD also happens when running the Xceed Grid Designer Window from within VS 2008. But it also happens on systems without the Xceed Grid installed.

So far I have replicated this 20+ times on one machine. I have 3 other identical machines in my office and I can also get it to happen on them …. totally reproducable (given enough attempts)!

If anyone from MS is interested in more details I can send some (many) crash dumps, dxdiags etc. Most BSODs are  DRIVER_CORRUPTED_MMPOOL, but there can be others. Also its never the same module/image which indicates to me the rogue driver is corrupting other drivers pool memory. We also have tons of antivirus and other *** installed on our SOEs so it could be interacting with them, but I doubt it as most BSOD appear to be triggered from interacting with a WPF screen.

Some info about the PC setups:
Dell Dimension 490
Xeon Quad Core 5150
Windows XP Pro SP2
Matrox Millenium P650 LP PCIe 64
Dual Monitor setups

http://forums.msdn.microsoft.com/en-US/vswpfdesigner/thread/03fd3084-3167-4469-82c4-6518c6779157/
I recently upgraded to VS2008 and I have started having this problem. Specifically, I get the BSOD and it mentions the "DRIVER_CORRUPT_MMPOOL" error.

I am not using Windows Forms when the error happens. Typically, it happens while I am running a WPF app from VS2008, e.g. when debugging. I don\’t recall seeing this error outside of VS2008 but that may be a coincidence.

My graphics card is branded as an "ATI Mobility Radeon x1400." So far as I can tell, it\’s not a Matrox product, but I can\’t say that for sure. Sharing / re-branding of the same chipset is commonplace.

历史博文

标签：
四月 12, 2009 at 10:45 上午 by yippee 1,045 次
Category: RAN乱
Tags: