Printing large photos using Windows Print Pictures

[newpersn]

I got a slight problem with a set of computers. (I3 2nd gen 4GB Ram)

 

When they try and print large set of photos for there coursework (GCSE Photography) their computers just crashes explorer.

 

I just sat here and done this

 

Selected 58 photos (around 2-3mb in size)

Right clicked print

Selected 9 prints to the page.

Clicked print and when it gets around 4/7 pages it crashes.

 

It sends what it got already to the printer but nothing after.

 

in the event log i get this

 

Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d6727a7

Faulting module name: igdumd32.dll, version: 8.15.10.2653, time stamp: 0x4f3aab9f

Exception code: 0xc0000005

Fault offset: 0x0027d0d8

Faulting process id: 0xc20

Faulting application start time: 0x01cf32ea0a42f541

Faulting application path: C:\Windows\Explorer.EXE

Faulting module path: C:\Windows\system32\igdumd32.dll

Report Id: 09a6b4c0-9edf-11e3-bc8d-386077bdf8b0

 

Something telling me its to do with the graphics driver?

 

HELP! ??

[newpersn]

I think i got it sorted.. Ive updated the graphics driver and it seems to have done the trick.

 

Whats printing got to do with the graphics driver? :s

[chazzy2501]

Graphics should have nothing to do with this issue... However, remember that the photos may only be 2 or 3 megs in stored size (thanks to some wicked fractal compression) but when the image is displayed on screen it's now in full decompressed glory (probably around 80+ megs) When that image is sent to the printer the decompressed version of the image is compressed by the print driver.

 

You can normally specify the print DPI and or the raster quality (basically how much to compress images) I usually use the second from lowest setting. This doesn't affect the vector quality (fonts etc.)

 

If you look at the print queue next time you'll see the size of the print job with 52 80meg images it's probably over a gigabyte in size Which may cause the spooler or others to wig out.

[newpersn]

Graphics should have nothing to do with this issue... However, remember that the photos may only be 2 or 3 megs in stored size (thanks to some wicked fractal compression) but when the image is displayed on screen it's now in full decompressed glory (probably around 80+ megs) When that image is sent to the printer the decompressed version of the image is compressed by the print driver.

 

You can normally specify the print DPI and or the raster quality (basically how much to compress images) I usually use the second from lowest setting. This doesn't affect the vector quality (fonts etc.)

 

If you look at the print queue next time you'll see the size of the print job with 52 80meg images it's probably over a gigabyte in size Which may cause the spooler or others to wig out.

 

thanks for that. It was printing at 600x600 (Max) as it was on a Konica C280. The spool size was around 300mb. Which coupled fine.

[Ste_Harve]

We had this problem on some lenovo machines, upgraded the graphics driver and it solved it.

 

We could print 9 pictures no probs, 18 pictures and it was 50/50 as to whether it would print or crash, any more and it would crash.

[AngryTechnician]

Whats printing got to do with the graphics driver? :s

The Windows print model from 2000-Windows 7 uses the GDI application interface for printing, the same as for drawing graphics on screen, so I'd wager it uses graphics driver functionality as part of this (probably to take advantage of hardware acceleration). In Windows 8 it uses Direct2D, so is probably even more integrated...

[MatthewL]

I am sure there was a similar problem before and it turned out to be graphics drivers.