PRB: Display Monitor Goes Blank After the Logo Display

 Last reviewed: March 27, 1995
Article ID: Q92532
The information in this article applies to:
  • Microsoft Windows Device Driver Kit (DDK) for Windows versions 3.1 and 3.11

SYMPTOMS

Under the debugging version of Windows, you may see something like "GlobalAlloc failed" or some other messages indicating problems, after the logo is displayed. Under non-debug Windows, the logo will display, then the screen will clear, then nothing else seems to happen. You must press CTRL+ALT+DEL to reset the system.

Note: This should happen only while developing a display driver that implements device bitmaps.

CAUSE

The display driver device returned 0 (zero) to fail a RealizeObject() function call after setting the RC_DEVBITS value in the dpRaster member of the GDIINFO structure.

RESOLUTION

Modify the device driver to prevent it from failing the RealizeObject() function call. A device driver cannot fail this call under Microsoft Windows 3.1. See section 2.1.14 of the 3.1 Device Driver Kit (DDK) "Device Driver Adaptation Guide" (DDAG) for more information.

Additional reference words: 3.10 DDK DeviceBitmap display
KBCategory: kbprg kbprb
KBSubcategory: D2DispProb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 27, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.