10 Replies Latest reply on Aug 10, 2016 2:41 AM by flori3000

    Calling ChoosePixelFormat causes Blue Screen on Windows 10 x64

    brettsr

      I created very small test application for it. It crashed into Blue Screen at ChoosePixelFormat when I try to print (Ctrl+P) on any printer.

      void CTest3View::OnBeginPrinting(CDC* pDC, CPrintInfo* pInfo)

      {

          PIXELFORMATDESCRIPTOR pfd ;

          memset(&pfd,0, sizeof(PIXELFORMATDESCRIPTOR)) ;

          pfd.nSize = sizeof(PIXELFORMATDESCRIPTOR); 

          pfd.nVersion = 1 ;                          // Version number

          pfd.dwFlags = PFD_SUPPORT_OPENGL | PFD_SUPPORT_GDI | PFD_DRAW_TO_BITMAP;

          pfd.iPixelType = 0;

          pfd.cColorBits = 24;

          pfd.cDepthBits = 32 ;                       // 32-bit depth buffer

          pfd.iLayerType = PFD_MAIN_PLANE ;           // Layer type

       

          int nPixelFormat = ChoosePixelFormat(pDC->m_hDC, &pfd);

      }

       

      It crashed with the latest driver Crimson Edition 16.1.1 Hotfix.

      Source code of the application are in the attachment or can be found at https://downlaod.dlubal.com/download/temp/Test3_Src.zip

       

      -= Motherboard =-

      Product: H55M-UD2H

      Manufacturer: Gigabyte Technology Co., Ltd.

      BIOS: Award Modular BIOS v6.00PG

       

      -= CPU =-

      CPU1

      Name: Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz

      Caption: Intel64 Family 6 Model 30 Stepping 5

       

      -= Video =-

      Video1

      Name: AMD Radeon HD 5570

      Driver: Crimson Edition 16.1.1 Hotfix

       

      -= OS =-

      Caption: Microsoft Windows 10 Pro

      OS Version: Microsoft Windows NT 6.2.9200.0

      Build: 6.2.9200.0

      Is 64-bit: Yes

      NET Framework: 4.0.30319.42000

      UI Culture: en-US

        • Re: Calling ChoosePixelFormat causes Blue Screen on Windows 10 x64
          amdmatt

          Just wanted to let you know that we were able to reproduce this issue and we are working on fixing it. Thank you for the post.

           

          dipak

            • Re: Calling ChoosePixelFormat causes Blue Screen on Windows 10 x64
              flori3000

              As our customers (we are selling Engineering software) are waiting since February 2016 for a solution, I kindly ask you  how long will it take to release a fixed driver?

              Currently they can´t print any PDF > there is always that Blue Screen.

                • Re: Calling ChoosePixelFormat causes Blue Screen on Windows 10 x64
                  picardo

                  Hi Flori300

                   

                  This issue seems to be a regression in Windows 10 and not in our driver. We can reproduce the same behavior on Nvidia cards.

                  We are continuing to investigate to see if we can find a workaround for you.

                  2 of 2 people found this helpful
                  • Re: Calling ChoosePixelFormat causes Blue Screen on Windows 10 x64
                    jiansan

                    Hi Flori,

                     

                    We looked into this issue and most likely it is a Windows 10 regression issue. First of all, Win7 and latest Windows RedStone are OK. Only Windows 10 (10240, 10586) has this issue. We uses NV's board and saw same problem with Windows 10 (10240, 10586). From the kernel debug output we got.

                     

                    2: kd:x86> k

                    # ChildEBP RetAddr          

                    00 00efe2cc 6eb2e6fe GDI32!NtGdiDdDDIOpenAdapterFromHdc+0xc

                    01 00efe774 6eb2f0c9 OPENGL32!EscapeCB+0x15e

                    02 00efeb68 6eb3d139 OPENGL32!wglCbGetAdapterLuid+0x239

                    03 00efeb80 6eb3defc OPENGL32!wglNumHardwareFormats+0x12

                    04 00efec30 6eb3d485 OPENGL32!wglDescribePixelFormat+0x10c

                    05 00efecc0 74c27b19 OPENGL32!wglChoosePixelFormat+0x55

                    06 00efece0 009f75ec GDI32!ChoosePixelFormat+0x39

                    WARNING: Stack unwind information not available. Following frames may be wrong.

                    07 00efed40 6bb83dcd Test3+0x75ec

                     

                    2: kd:x86> .cxr 0xffffd001f4661390

                    eax=c000000d ebx=ffffd001 ecx=00000000 edx=00ef0000 esi=f4661ec0 edi=ffffd001

                    eip=0000000b esp=00000000 ebp=00000000 iopl=0         nv up di pl nz na po nc

                    cs=0000 ss=0018  ds=1db0  es=f901  fs=f030 gs=0000 efl=00000000

                    00000000`0000000b ?? ???

                     

                    Looks like the process's stack is corrupted and the OGL driver is not loaded yet. So the suggested solution is to update your Windows 10 to the latest RedStone release (14393).

                     

                    BTW, at the very beginning of this thread, the OS information is as follows. It is quite confusing as 6.2.9200 should be the version number of Windows 8. Why the caption tells it is Windows 10? How did you get the OS version information?

                    -----------------------------

                    Caption: Microsoft Windows 10 Pro

                    OS Version: Microsoft Windows NT 6.2.9200.0

                    ----------------------------

                    Please feel free to tell us if you observe different result from ours.

                    1 of 1 people found this helpful