What are pixel size limits of GDI bitmaps/DCs in 32-bit and 64-bit processes?

Question

I'm coding a Win32 application that performs low-level printing, for which I'm dealing with GDI bitmaps and device contexts.

The code basically does this (pseudo-code):

HDC hCompDc = ::CreateCompatibleDC(hDC);

BITMAPINFOHEADER infoHeader = {0};

infoHeader.biSize          = sizeof(infoHeader);
infoHeader.biWidth         = nWidth;
infoHeader.biHeight        = -nHeight;      //The document must be right side up
infoHeader.biPlanes        = 1;
infoHeader.biBitCount      = 24;
infoHeader.biCompression   = BI_RGB;

BITMAPINFO info;
info.bmiHeader = infoHeader;

//Use file on disk to store large bitmap data
HANDLE hFileScatch = ::CreateFile(strTempPath, 
    GENERIC_READ | GENERIC_WRITE, 0, NULL, 
    CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL);

UINT64 ncbLineSz = nWidth * 3;
if(ncbLineSz & 0x3)
    ncbLineSz = (ncbLineSz & ~0x3) + 0x4;       //Must be DWORD aligned

UINT64 uiSzBmp = ncbLineSz * nHeight;

HANDLE hFileMapObj = ::CreateFileMapping(hFileScatch,
    NULL, PAGE_READWRITE, (DWORD)(uiSzBmp >> 32), (DWORD)(uiSzBmp), NULL);

BYTE* pMemory = 0;
HBITMAP hBitmap = ::CreateDIBSection(hDC, &info, DIB_RGB_COLORS, (void**)&pMemory, hFileMapObj, 0);

::SelectObject(hCompDc, hBitmap);

//Do drawing on `hCompDc` using other GDI APIs
//...

//And print
::SetAbortProc(hPrintDC, _printerAbortProc);
::StartDoc(hPrintDC, &docInfo);
::StartPage(hPrintDC);

::BitBlt(hPrintDC, 
    rcPrintArea.left,
    rcPrintArea.top, 
    rcRenderArea.Width(), 
    rcRenderArea.Height(), 
    hCompDc,                    //DC from
    rcRenderArea.left,
    rcRenderArea.top,
    SRCCOPY);

::EndPage(hPrintDC);

//Clean up, etc.
//...

This works but to a certain degree. Let me explain:

Since I'm dealing with printer resolutions running at 300 dpi (vs. 96 dpi for a usual screen) the sizes of bitmaps turn out pretty large.

For instance, if I have a bitmap that is 3900x86625 pixels, it requires a DIB section of around 966 MB. (I can learn that if I substitute default memory allocation in CreateDIBSection in my code above with a file mapping object backed by a file on disk.) Otherwise, I understand that I can hit a limit of contiguous RAM space in a 32-bit process with that chunk of memory. But that is not what happens.

When I run my code with that size of a bitmap in a 32-bit process, the bitmap is created OK using file mapping object backed by a file on disk, but the resulting bitmap/image comes out completely blank, while the exact same code compiled in a 64-bit process, produces a normal looking bitmap.

So in light of that I was curious if there are specific image size restrictions that those GDI objects have? For 32-bit and 64-bit processes.

And also a side question -- is there any way to know that such size limit was reached while drawing?

PS. My actual code has all error checks in place for all Win32 APIs, and while the 32-bit process that I described above produced a blank bitmap, it did not fail in a single GDI API.