Blue Screen of Death (BSOD) when printing

We have been using SQL 2005 reporting services for a while but recently when
some one tries to print a report they will get a BSOD and the machine reboots.
Any Ideas'?We are also having the same problem when printing, blue screen with error
message 0X80070709.
"Eric Wainz" wrote:
> We have been using SQL 2005 reporting services for a while but recently when
> some one tries to print a report they will get a BSOD and the machine reboots.
> Any Ideas'?
>|||On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> We are also having the same problem when printing, blue screen with error
> message 0X80070709.
> "Eric Wainz" wrote:
> > We have been using SQL 2005 reporting services for a while but recently when
> > some one tries to print a report they will get a BSOD and the machine reboots.
> > Any Ideas'?
It sounds kind of like a printer driver issue. Does this occur when
exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
etc) and then printing?
Enrique Martinez
Sr. Software Consultant|||No, It does not happen when you export the report.
But, We have been able to narrow it down to PCL6 print drivers.
"EMartinez" wrote:
> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> > We are also having the same problem when printing, blue screen with error
> > message 0X80070709.
> >
> > "Eric Wainz" wrote:
> > > We have been using SQL 2005 reporting services for a while but recently when
> > > some one tries to print a report they will get a BSOD and the machine reboots.
> >
> > > Any Ideas'?
>
> It sounds kind of like a printer driver issue. Does this occur when
> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
> etc) and then printing?
> Enrique Martinez
> Sr. Software Consultant
>|||It isn't a printer driver issue, it is the ActiveX control RSClientPrint
Class that is causing the problem. It seems to be happening after a recent
Windows Update, but I have not attributed it to any particular one. Go to
C:\windows\downloaded program files and delete the RSClientPrint Class and
run your report again. It should prompt you to download the control again
and printing should resume after that.
Wish I could flag this so MS could figure out why it is happening. It has
happened to two of my users and I am sure there will be more to follow.
"Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
> No, It does not happen when you export the report.
> But, We have been able to narrow it down to PCL6 print drivers.
> "EMartinez" wrote:
>> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
>> > We are also having the same problem when printing, blue screen with
>> > error
>> > message 0X80070709.
>> >
>> > "Eric Wainz" wrote:
>> > > We have been using SQL 2005 reporting services for a while but
>> > > recently when
>> > > some one tries to print a report they will get a BSOD and the machine
>> > > reboots.
>> >
>> > > Any Ideas'?
>>
>> It sounds kind of like a printer driver issue. Does this occur when
>> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
>> etc) and then printing?
>> Enrique Martinez
>> Sr. Software Consultant
>>|||I did that and still is rebooting.
"Rockn" wrote:
> It isn't a printer driver issue, it is the ActiveX control RSClientPrint
> Class that is causing the problem. It seems to be happening after a recent
> Windows Update, but I have not attributed it to any particular one. Go to
> C:\windows\downloaded program files and delete the RSClientPrint Class and
> run your report again. It should prompt you to download the control again
> and printing should resume after that.
> Wish I could flag this so MS could figure out why it is happening. It has
> happened to two of my users and I am sure there will be more to follow.
>
> "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
> news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
> > No, It does not happen when you export the report.
> >
> > But, We have been able to narrow it down to PCL6 print drivers.
> >
> > "EMartinez" wrote:
> >
> >> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> >> > We are also having the same problem when printing, blue screen with
> >> > error
> >> > message 0X80070709.
> >> >
> >> > "Eric Wainz" wrote:
> >> > > We have been using SQL 2005 reporting services for a while but
> >> > > recently when
> >> > > some one tries to print a report they will get a BSOD and the machine
> >> > > reboots.
> >> >
> >> > > Any Ideas'?
> >>
> >>
> >> It sounds kind of like a printer driver issue. Does this occur when
> >> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
> >> etc) and then printing?
> >>
> >> Enrique Martinez
> >> Sr. Software Consultant
> >>
> >>
>
>|||I am almost positive it is not a printer problem and I can almost bet the
problem started after a recent Windows Update. I tried my solution on one
person in the office and it seemed to fix it. I tried it on another
computer, but I wasn't logged on under his user account and it BSOD'd and
restarted.
"Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
news:3CEBEA69-C6F9-4B28-BE47-C8CF01A76118@.microsoft.com...
> I did that and still is rebooting.
> "Rockn" wrote:
> > It isn't a printer driver issue, it is the ActiveX control RSClientPrint
> > Class that is causing the problem. It seems to be happening after a
recent
> > Windows Update, but I have not attributed it to any particular one. Go
to
> > C:\windows\downloaded program files and delete the RSClientPrint Class
and
> > run your report again. It should prompt you to download the control
again
> > and printing should resume after that.
> >
> > Wish I could flag this so MS could figure out why it is happening. It
has
> > happened to two of my users and I am sure there will be more to follow.
> >
> >
> > "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
> > news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
> > > No, It does not happen when you export the report.
> > >
> > > But, We have been able to narrow it down to PCL6 print drivers.
> > >
> > > "EMartinez" wrote:
> > >
> > >> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
> > >> > We are also having the same problem when printing, blue screen with
> > >> > error
> > >> > message 0X80070709.
> > >> >
> > >> > "Eric Wainz" wrote:
> > >> > > We have been using SQL 2005 reporting services for a while but
> > >> > > recently when
> > >> > > some one tries to print a report they will get a BSOD and the
machine
> > >> > > reboots.
> > >> >
> > >> > > Any Ideas'?
> > >>
> > >>
> > >> It sounds kind of like a printer driver issue. Does this occur when
> > >> exporting to any SSRS supported format (Excel, PDF, CSV, Web Archive,
> > >> etc) and then printing?
> > >>
> > >> Enrique Martinez
> > >> Sr. Software Consultant
> > >>
> > >>
> >
> >
> >|||What programs are installed on the computer getting the BSOD? Acrobat Pro,
IM? Others?
"Rockn" <Rockn@.newsgroups.nospam> wrote in message
news:eAXDzH8eHHA.4188@.TK2MSFTNGP02.phx.gbl...
>I am almost positive it is not a printer problem and I can almost bet the
> problem started after a recent Windows Update. I tried my solution on one
> person in the office and it seemed to fix it. I tried it on another
> computer, but I wasn't logged on under his user account and it BSOD'd and
> restarted.
>
> "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
> news:3CEBEA69-C6F9-4B28-BE47-C8CF01A76118@.microsoft.com...
>> I did that and still is rebooting.
>> "Rockn" wrote:
>> > It isn't a printer driver issue, it is the ActiveX control
>> > RSClientPrint
>> > Class that is causing the problem. It seems to be happening after a
> recent
>> > Windows Update, but I have not attributed it to any particular one. Go
> to
>> > C:\windows\downloaded program files and delete the RSClientPrint Class
> and
>> > run your report again. It should prompt you to download the control
> again
>> > and printing should resume after that.
>> >
>> > Wish I could flag this so MS could figure out why it is happening. It
> has
>> > happened to two of my users and I am sure there will be more to follow.
>> >
>> >
>> > "Eric Wainz" <EricWainz@.discussions.microsoft.com> wrote in message
>> > news:29A2AC00-2BDF-4052-AB0E-83D9C576EFC0@.microsoft.com...
>> > > No, It does not happen when you export the report.
>> > >
>> > > But, We have been able to narrow it down to PCL6 print drivers.
>> > >
>> > > "EMartinez" wrote:
>> > >
>> > >> On Apr 10, 1:00 pm, rcruz03 <bobby.c...@.Early-Warning.com> wrote:
>> > >> > We are also having the same problem when printing, blue screen
>> > >> > with
>> > >> > error
>> > >> > message 0X80070709.
>> > >> >
>> > >> > "Eric Wainz" wrote:
>> > >> > > We have been using SQL 2005 reporting services for a while but
>> > >> > > recently when
>> > >> > > some one tries to print a report they will get a BSOD and the
> machine
>> > >> > > reboots.
>> > >> >
>> > >> > > Any Ideas'?
>> > >>
>> > >>
>> > >> It sounds kind of like a printer driver issue. Does this occur when
>> > >> exporting to any SSRS supported format (Excel, PDF, CSV, Web
>> > >> Archive,
>> > >> etc) and then printing?
>> > >>
>> > >> Enrique Martinez
>> > >> Sr. Software Consultant
>> > >>
>> > >>
>> >
>> >
>> >
>|||We are getting the same problem!
Just started happening a few days ago.
"Eric Wainz" wrote:
> We have been using SQL 2005 reporting services for a while but recently when
> some one tries to print a report they will get a BSOD and the machine reboots.
> Any Ideas'?
>|||I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
"Eric Wainz" wrote:
> We have been using SQL 2005 reporting services for a while but recently when
> some one tries to print a report they will get a BSOD and the machine reboots.
> Any Ideas'?
>|||I fixed one of the computers using System Restore to a date before the
errors and it took care of his. I haven't narrowed it down yet, but I have
also tried removing all Windows updates for today and it still didn't fix
another users issue. I'll keep plugging away at it.
"ana9" <ana9@.discussions.microsoft.com> wrote in message
news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
> "Eric Wainz" wrote:
>> We have been using SQL 2005 reporting services for a while but recently
>> when
>> some one tries to print a report they will get a BSOD and the machine
>> reboots.
>> Any Ideas'?|||I rolled back the security updates and re-installed the active x driver to no
avail. All the printers use the PCL6 driver but crashes only occur when
trying to print to an HP4250...
"Rockn" wrote:
> I fixed one of the computers using System Restore to a date before the
> errors and it took care of his. I haven't narrowed it down yet, but I have
> also tried removing all Windows updates for today and it still didn't fix
> another users issue. I'll keep plugging away at it.
> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> > I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
> >
> > "Eric Wainz" wrote:
> >
> >> We have been using SQL 2005 reporting services for a while but recently
> >> when
> >> some one tries to print a report they will get a BSOD and the machine
> >> reboots.
> >>
> >> Any Ideas'?
> >>
>
>|||Is that a PLC 5e driver or something else?
"ana9" <ana9@.discussions.microsoft.com> wrote in message
news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
>I rolled back the security updates and re-installed the active x driver to
>no
> avail. All the printers use the PCL6 driver but crashes only occur when
> trying to print to an HP4250...
>
> "Rockn" wrote:
>> I fixed one of the computers using System Restore to a date before the
>> errors and it took care of his. I haven't narrowed it down yet, but I
>> have
>> also tried removing all Windows updates for today and it still didn't fix
>> another users issue. I'll keep plugging away at it.
>> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
>> > I'm having the same issue with RS 2000. Microsoft, we need a hotfix...
>> >
>> > "Eric Wainz" wrote:
>> >
>> >> We have been using SQL 2005 reporting services for a while but
>> >> recently
>> >> when
>> >> some one tries to print a report they will get a BSOD and the machine
>> >> reboots.
>> >>
>> >> Any Ideas'?
>> >>
>>|||It appears to be a print driver issue due to some recent update. If you
change your print drivers to PCL 5e it won't crash any longer.
ana9 had the answer, but the reason is still not figured out.
"Rockn" <Rockn@.newsgroups.nospam> wrote in message
news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> Is that a PLC 5e driver or something else?
>
> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
>>I rolled back the security updates and re-installed the active x driver to
>>no
>> avail. All the printers use the PCL6 driver but crashes only occur when
>> trying to print to an HP4250...
>>
>> "Rockn" wrote:
>> I fixed one of the computers using System Restore to a date before the
>> errors and it took care of his. I haven't narrowed it down yet, but I
>> have
>> also tried removing all Windows updates for today and it still didn't
>> fix
>> another users issue. I'll keep plugging away at it.
>> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
>> > I'm having the same issue with RS 2000. Microsoft, we need a
>> > hotfix...
>> >
>> > "Eric Wainz" wrote:
>> >
>> >> We have been using SQL 2005 reporting services for a while but
>> >> recently
>> >> when
>> >> some one tries to print a report they will get a BSOD and the machine
>> >> reboots.
>> >>
>> >> Any Ideas'?
>> >>
>>
>|||It doesn't appear to be a general print driver issue. As I said, only the HP
4250's have this problem. Do you see this as well, or does it effect all
your printers regardless of manufacturer?
"Rockn" wrote:
> It appears to be a print driver issue due to some recent update. If you
> change your print drivers to PCL 5e it won't crash any longer.
> ana9 had the answer, but the reason is still not figured out.
> "Rockn" <Rockn@.newsgroups.nospam> wrote in message
> news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> > Is that a PLC 5e driver or something else?
> >
> >
> > "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
> >>I rolled back the security updates and re-installed the active x driver to
> >>no
> >> avail. All the printers use the PCL6 driver but crashes only occur when
> >> trying to print to an HP4250...
> >>
> >>
> >> "Rockn" wrote:
> >>
> >> I fixed one of the computers using System Restore to a date before the
> >> errors and it took care of his. I haven't narrowed it down yet, but I
> >> have
> >> also tried removing all Windows updates for today and it still didn't
> >> fix
> >> another users issue. I'll keep plugging away at it.
> >>
> >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> >> > I'm having the same issue with RS 2000. Microsoft, we need a
> >> > hotfix...
> >> >
> >> > "Eric Wainz" wrote:
> >> >
> >> >> We have been using SQL 2005 reporting services for a while but
> >> >> recently
> >> >> when
> >> >> some one tries to print a report they will get a BSOD and the machine
> >> >> reboots.
> >> >>
> >> >> Any Ideas'?
> >> >>
> >>
> >>
> >>
> >
> >
>
>|||It only affects printers using the PCL 6 driver. If I print to any of the
others using a PCL 5e driver it works. All of our printers are HP.
"ana9" <ana9@.discussions.microsoft.com> wrote in message
news:7FEEEDFD-FBC1-45D8-915D-087F066D3108@.microsoft.com...
> It doesn't appear to be a general print driver issue. As I said, only the
HP
> 4250's have this problem. Do you see this as well, or does it effect all
> your printers regardless of manufacturer?
> "Rockn" wrote:
> > It appears to be a print driver issue due to some recent update. If you
> > change your print drivers to PCL 5e it won't crash any longer.
> > ana9 had the answer, but the reason is still not figured out.
> >
> > "Rockn" <Rockn@.newsgroups.nospam> wrote in message
> > news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> > > Is that a PLC 5e driver or something else?
> > >
> > >
> > > "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
> > >>I rolled back the security updates and re-installed the active x
driver to
> > >>no
> > >> avail. All the printers use the PCL6 driver but crashes only occur
when
> > >> trying to print to an HP4250...
> > >>
> > >>
> > >> "Rockn" wrote:
> > >>
> > >> I fixed one of the computers using System Restore to a date before
the
> > >> errors and it took care of his. I haven't narrowed it down yet, but
I
> > >> have
> > >> also tried removing all Windows updates for today and it still
didn't
> > >> fix
> > >> another users issue. I'll keep plugging away at it.
> > >>
> > >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> > >> > I'm having the same issue with RS 2000. Microsoft, we need a
> > >> > hotfix...
> > >> >
> > >> > "Eric Wainz" wrote:
> > >> >
> > >> >> We have been using SQL 2005 reporting services for a while but
> > >> >> recently
> > >> >> when
> > >> >> some one tries to print a report they will get a BSOD and the
machine
> > >> >> reboots.
> > >> >>
> > >> >> Any Ideas'?
> > >> >>
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> >|||Remove security patch KB925902 or MS07-017 related to GDI+. This was just
realeased. I understand a hot patch may be available as early as Monday.
As a pre-caution read why this security update was published before
removing. Might be more of a risk to remove that to have the end users export
to pdf then print which has been my work around.
John
"Rockn" wrote:
> It only affects printers using the PCL 6 driver. If I print to any of the
> others using a PCL 5e driver it works. All of our printers are HP.
> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> news:7FEEEDFD-FBC1-45D8-915D-087F066D3108@.microsoft.com...
> > It doesn't appear to be a general print driver issue. As I said, only the
> HP
> > 4250's have this problem. Do you see this as well, or does it effect all
> > your printers regardless of manufacturer?
> >
> > "Rockn" wrote:
> >
> > > It appears to be a print driver issue due to some recent update. If you
> > > change your print drivers to PCL 5e it won't crash any longer.
> > > ana9 had the answer, but the reason is still not figured out.
> > >
> > > "Rockn" <Rockn@.newsgroups.nospam> wrote in message
> > > news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
> > > > Is that a PLC 5e driver or something else?
> > > >
> > > >
> > > > "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > > > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
> > > >>I rolled back the security updates and re-installed the active x
> driver to
> > > >>no
> > > >> avail. All the printers use the PCL6 driver but crashes only occur
> when
> > > >> trying to print to an HP4250...
> > > >>
> > > >>
> > > >> "Rockn" wrote:
> > > >>
> > > >> I fixed one of the computers using System Restore to a date before
> the
> > > >> errors and it took care of his. I haven't narrowed it down yet, but
> I
> > > >> have
> > > >> also tried removing all Windows updates for today and it still
> didn't
> > > >> fix
> > > >> another users issue. I'll keep plugging away at it.
> > > >>
> > > >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
> > > >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
> > > >> > I'm having the same issue with RS 2000. Microsoft, we need a
> > > >> > hotfix...
> > > >> >
> > > >> > "Eric Wainz" wrote:
> > > >> >
> > > >> >> We have been using SQL 2005 reporting services for a while but
> > > >> >> recently
> > > >> >> when
> > > >> >> some one tries to print a report they will get a BSOD and the
> machine
> > > >> >> reboots.
> > > >> >>
> > > >> >> Any Ideas'?
> > > >> >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> > >
>
>|||That did the trick, you are the man!!
"John" <John@.discussions.microsoft.com> wrote in message
news:3B16020C-2B19-40F9-BF4D-811DC1995D95@.microsoft.com...
> Remove security patch KB925902 or MS07-017 related to GDI+. This was just
> realeased. I understand a hot patch may be available as early as Monday.
> As a pre-caution read why this security update was published before
> removing. Might be more of a risk to remove that to have the end users
> export
> to pdf then print which has been my work around.
> John
> "Rockn" wrote:
>> It only affects printers using the PCL 6 driver. If I print to any of the
>> others using a PCL 5e driver it works. All of our printers are HP.
>> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> news:7FEEEDFD-FBC1-45D8-915D-087F066D3108@.microsoft.com...
>> > It doesn't appear to be a general print driver issue. As I said, only
>> > the
>> HP
>> > 4250's have this problem. Do you see this as well, or does it effect
>> > all
>> > your printers regardless of manufacturer?
>> >
>> > "Rockn" wrote:
>> >
>> > > It appears to be a print driver issue due to some recent update. If
>> > > you
>> > > change your print drivers to PCL 5e it won't crash any longer.
>> > > ana9 had the answer, but the reason is still not figured out.
>> > >
>> > > "Rockn" <Rockn@.newsgroups.nospam> wrote in message
>> > > news:%23rNh2sQfHHA.284@.TK2MSFTNGP05.phx.gbl...
>> > > > Is that a PLC 5e driver or something else?
>> > > >
>> > > >
>> > > > "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> > > > news:27CF0AFF-AC34-4E24-81B8-34C5D446BA1F@.microsoft.com...
>> > > >>I rolled back the security updates and re-installed the active x
>> driver to
>> > > >>no
>> > > >> avail. All the printers use the PCL6 driver but crashes only
>> > > >> occur
>> when
>> > > >> trying to print to an HP4250...
>> > > >>
>> > > >>
>> > > >> "Rockn" wrote:
>> > > >>
>> > > >> I fixed one of the computers using System Restore to a date
>> > > >> before
>> the
>> > > >> errors and it took care of his. I haven't narrowed it down yet,
>> > > >> but
>> I
>> > > >> have
>> > > >> also tried removing all Windows updates for today and it still
>> didn't
>> > > >> fix
>> > > >> another users issue. I'll keep plugging away at it.
>> > > >>
>> > > >> "ana9" <ana9@.discussions.microsoft.com> wrote in message
>> > > >> news:093ABBB0-B29D-47FD-82A5-3AD3FC109510@.microsoft.com...
>> > > >> > I'm having the same issue with RS 2000. Microsoft, we need a
>> > > >> > hotfix...
>> > > >> >
>> > > >> > "Eric Wainz" wrote:
>> > > >> >
>> > > >> >> We have been using SQL 2005 reporting services for a while but
>> > > >> >> recently
>> > > >> >> when
>> > > >> >> some one tries to print a report they will get a BSOD and the
>> machine
>> > > >> >> reboots.
>> > > >> >>
>> > > >> >> Any Ideas'?
>> > > >> >>
>> > > >>
>> > > >>
>> > > >>
>> > > >
>> > > >
>> > >
>> > >
>> > >
>>|||Please review this article http://support.microsoft.com/kb/935843/. It has two patches, one for Windows 2000 and another one for Windows XP. The crashing will stop after you apply this patch
From http://www.developmentnow.com/g/115_2007_4_0_0_955642/Blue-Screen-of-Death-BSOD-when-printing.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com