The biggest change: The Desktop Window Manager (DWM) will use the DirectX 10.1 API instead of 9, and it will offer some nice performance enhancements. (Everything won’t suddenly be more colorful, of course: Your graphics drivers, display, and full-screen applications all need to support WDDM to see the effects.) WDDM 1.1 adds a new API, called Connecting and Configuring Displays (CCD), which ostensibly makes life simpler for end users with multiple displays, like a notebook with a projector or a docking station, for example. There’s support for high-fidelity graphics, for one thing, with 10-bit color per channel for dynamic 48-bit color.
#Amd display driver stopped responding windows 7 windows 7#
Windows 7 introduces WDDM 1.1, which brings only minor tweaks to the underlying architecture.
And frankly, given the problems these companies had with the Vista launch, that worries me. The new version of the application programming interface (API) drives the graphics system in the operating system, yet we still don’t have final graphics hardware. Windows 7 won’t transform that new driver model too much, but it will bring one fairly important change: DX11. I saw and was frustrated by those messages for literally years. I’m sure readers of this site are painfully aware of the message “nvlddmkm.sys has stopped responding and has recovered,” or its ATI-related counterpart. The new driver architecture was also supposed to bring new levels of reliability, but for end users, it was a complete fiasco.
WDDM brought 3D effects to the desktop and introduced “GPU multitasking,” as well as other dramatic changes. Windows Vista introduced a new graphics architecture, called WDDM 1.0, or Windows Display Driver Model, an overhaul of Windows XP’s XPDM display architecture that “gives users a better performing, more reliable desktop experience, while supporting new scenarios, graphics, and applications,” according to MSDN. This site may earn affiliate commissions from the links on this page.
0 kommentar(er)
