This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello,
We have an application we use to reproduce the issue, which in summary, gets to a point where it prints from a 32 bit application to the the 64 bit Amyuni PDF Converter on Windows 11 and the print job has a TIFF image with transparencies, when printing at DPI of 300 or above, Windows 11 crashes with a BSOD.
I retrieved crash Minidump file and compared it to a dump from a similar crash happening also on Windows 11 only with a similar situation, 32 bit Wordpad.exe printing an RTF file that has a pngblip element (embedded PNG image) and also crashing Windows 11 64 bit only.
Both scenarios described above work with no issues when tested on Windows 10.
I tested printing to another printer driver “HP LaserJet Professional CM1410 Series PCL 6” redirected to file output. It also crashed with the same error in the Minidump crash report.
The issue does not happen on Windows 11 when printing with same test to any Type 4 printers or to Type 3 Class Driver printers (i.e. through the XPSDrv print path.)
It seems to happen with some Type 3 printer drivers only.
I have an RTF file
myfile.rtf
to test the issue with. If we open this file with Wordpad.exe, we get a warning that it might not be safe. It just contains a PNG image encoded in hexadecimal.
When using the 64 bit Wordpad.exe to print, for example to "HP LaserJet Professional CM1410 Series PCL 6", we get no crash or error. Only when we use the 32 bit Wordpad.exe and print to the same printer that we get the crash and only on Windows 11.
From the Minidump crash file I have this:
The stack trace at the time the BSOD is happening
The kernel function causing the crash is win32kfull!UMPDOBJ::BackPropagateBitmapBits+0x2c.
nt!KeBugCheckEx
nt!MiSystemFault+0x22d76b
nt!MmAccessFault+0x29c
nt!KiPageFault+0x369
win32kfull!memcpy+0x92
win32kfull!UMPDOBJ::BackPropagateBitmapBits+0x2c
win32kfull!UMPDDrvCopyBits+0x29d
win32kfull!EngStretchBltNew+0xc250f
win32kfull!EngStretchBlt+0xf4
win32kfull!EngStretchBltROP+0xc2461
win32kfull!BLTRECORD::bStretch+0x686
win32kfull!GreStretchBltInternal+0x599
win32kfull!NtGdiStretchBlt+0x68
win32k!NtGdiStretchBlt+0x81
nt!KiSystemServiceCopyEnd+0x25
0x00007ff9`742726c4
Any suggestions?
Thanks,
Roger
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 10%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIL%3C/text%3E%3C/svg%3E)
Seems there is some memory problem, the error occurs in memory copying function. Maybe it is BIOS related, it is too old for Windows 11.
Please run Windows memory diagnostic tool and switch it to extended mode when it starts (F1 key). Note, test hang at ~21% for more than 3-5 hours means memory error too.
Sorry, this file is of zero size.
Hi Igor,
This is the minidump file
022224-10921-01_WordPadPrint.dmp
I also wanted to add that the issue happens on all Windows 11 machines I tested on. Also on a Win 11 VM.
Thanks,
Roger
Hi Roger,
My name is Igor, it's a pleasure for me to help others and I'll try to help you.
Please share memory minidumps to OneDrive for analysis.
