cancel
Showing results for 
Search instead for 
Did you mean: 

Archives Discussions

dave3
Journeyman III

ChoosePixelFormat() with memory DC crashes in Windows 10 with latest drivers

We have been using ChoosePixelFormat() successfully with memory DC, for all versions of Windows, including Windows 10, up to version 10.0.10576.  With 10.0.10586, this call makes the computer hard reset.  We have also tested our software on Redstone 1 version 10.0.14257 with a similar result.  The ability to render to bitmap is important in our work, as well as to the screen.  Here is an example of what we do in our software, which runs fine in Windows XP, 7, 8, and earlier versions of Windows 10:

PIXELFORMATDESCRIPTOR pfd = {
       sizeof(PIXELFORMATDESCRIPTOR), // Size of this structure
       1,    // Version of this structure
       PFD_DRAW_TO_BITMAP |  // Draw to bitmap (not to window)
       PFD_SUPPORT_OPENGL,  // Support OpenGL calls in window
       PFD_TYPE_RGBA,   // RGBA Color mode
       24,    // Number of color bitplanes
       0,0,0,0,0,0,   // Not used to select mode
       0,    // Number of alpha bitplanes
       0,    // Not used to select mode
       0, //  64,    // Number of bitplanes in the accumulation buffer
       0,0,0,0,   // Not used to select mode
       24, //  32,    // Size of depth buffer
       0, //  8,    // Size of stencil buffer
       0,    // Size of auxiliary buffer
       PFD_MAIN_PLANE,   // Draw in main plane
       0,0,0,0 };   // Not used to select mode

int nGLPixelFormat = ChoosePixelFormat( hMemDC, &pfd ); <<< Ouch

What can we do to work-around this problem, or is AMD even aware of the problem.

Thanks!

0 Likes
2 Replies
picardo
Staff

Hi Dave,

This issue is also reported as

Calling ChoosePixelFormat causes Blue Screen on Windows 10 x64

The issue seems to be a regression in Windows 10 not specific to our driver since we see the same problem on Nvidia cards too.
We are continuing to investigate to see if we can find a workaround.

Thanks

0 Likes

Hi Dave,

The issue should be resolved by updating Window to the latest RedStone release (14393).

0 Likes