Windows 10 GSOD when printing in XnView Classic 2.47

Bugs found in XnView Classic. Please report only one bug per topic!

Moderators: XnTriq, xnview

Post Reply
drageset
Posts: 2
Joined: Mon Sep 15, 2008 8:36 am
Location: Arendal

Windows 10 GSOD when printing in XnView Classic 2.47

Post by drageset » Tue Jan 22, 2019 8:59 pm

Hi,

Just wondering if anyone else is experiencing this?

Whenever I print a picture from XnView Classic v2.47 my Windows 10 gives me GSOD.
I did not have this problem with my previous combination, which I think was XnView Classic v2.39 and Windows 1703.

My system today is:
Dell Precision T5610 Dual Xeon E5-2609 v2
64GB ECC RAM (I'm only running XnView, so it's not a memory issue)
Windows 10 Pro 64-bit Insider Preview Version 1809, build 18317.1000, prerelease 190111-1556

Whilst I accept that this could be related to me running an Insider Preview version of Windows, I can print the same picture from Picasa v3.9.141.259.

The GSOD stop code is SYSTEM_SERVICE_EXCEPTION, and it states that win32kfull.sys has failed.

sunnivah
Posts: 2
Joined: Mon Dec 17, 2018 9:57 am

Re: Windows 10 GSOD when printing in XnView Classic 2.47

Post by sunnivah » Wed Jan 23, 2019 8:08 am

I also have problems printing with Windows 10 1809 (new installation, official version not the Insider Preview). For me, the GSOD only occurs when printing via network printer.

viewtopic.php?f=36&t=38279

drageset
Posts: 2
Joined: Mon Sep 15, 2008 8:36 am
Location: Arendal

Re: Windows 10 GSOD when printing in XnView Classic 2.47

Post by drageset » Wed Jan 23, 2019 8:40 pm

Thanks Sunnivah,

I should have included that I was also printing to a network printer, a Kyocera TASKalfa 300ci.
I tried printing to an Epson Stylus Photo PX720WD connected through USB (Virtual printer port for USB - USB002) just now, and it worked.
I also tried printing to my Brother DCP-J552DW, through USB (Virutal port USB003).

My Kyocera is connected through both USB and network, but I've only been printing over the network earlier.
It's listed on USB001 and WSD-port (WSD-46da9d9a-99d1-42b7-950b-ab9b112acad5). I tried printing over USB now, and voila, it worked.

Now, just to verify that it would crash over network, I tried printing over network again.
Well, guess what, todays it works :(

Go figure... But, since the error can't be reproduced today I'll subtract my bug-report.

Post Reply