Print spooler sub system App stopped working

Hi, I have a problem with my printer. I am getting a message saying that
the spooler subsystem has stopped working and closed. I have tried manually
restarting the spooler but I then get a interactive services message, saying
that there is a message that cannot be viewed in windows, I click the view
message button and I get a blue screen with a black window then I am told
the it does not need to show me the message.

I am running Vista SP2 64bit

AMD athlon 64X2 Dual core processor 6400+ 3.20GHz with 4.00Gb RAM
Thanks in advance.

Nig

Whilst I appreciate your reply Stan, it is somewhat akin to gloating that
you are superior.
Whilst I am sure that you are more than able to argue your point to the Nth
degree, there are I am sure many others who would disagree.
I do not really have a point of view.
What I have, I have to deal with, it is too late to start wishing I had
different equipment. I have a problem, I have asked for advice. There is
little point arguing whether 64 bit is worse than 32 bit as is the AMD Intel
argument.

The best advice you give is to wait until someone with knowledge of the
problem suggests a solution.

Nig

"Stan Starinski" <China@stealsUSJobsPatentsSoftwareMusicVideo> wrote in
message news:#5woM#...
> Wait for responses but Just FYI:
> I only use Intel.
> I only use genuine Windows or UNIX for networked labs.
> And I only use prevalent 32-bit client version for normal, "mass-market"
> softwares" such as Office, productivity, communications, etc.
> I use 64-bit only for hard-core floating point intensive softwares such as
> CAD, Image & Video editing, engineering simulations.
>
> Basically you invite problems by violating all above. Don't use AMD,
> don't flirt with 64 bit UNLESS you know 100% your printer driver was
> TESTED to work in 64-bit Windows.
>
> No wmy suggestion is goback to printer mfg's website and check if 64-bit
> driver update is available, and replace yours if available.
>
> If not, wait for more responses.

Do yourself a favor and ignore Stan. He's a well known and disliked troll
here, and most have him blocked.

--


"Don't pick a fight with an old man.
If he is too old to fight, he'll just kill you."


"Nig" <> wrote in message
news:#...
> Whilst I appreciate your reply Stan, it is somewhat akin to gloating that
> you are superior.
> Whilst I am sure that you are more than able to argue your point to the
> Nth degree, there are I am sure many others who would disagree.
> I do not really have a point of view.
> What I have, I have to deal with, it is too late to start wishing I had
> different equipment. I have a problem, I have asked for advice. There is
> little point arguing whether 64 bit is worse than 32 bit as is the AMD
> Intel argument.
>
> The best advice you give is to wait until someone with knowledge of the
> problem suggests a solution.
>
> Nig
>
> "Stan Starinski" <China@stealsUSJobsPatentsSoftwareMusicVideo> wrote in
> message news:#5woM#...
>> Wait for responses but Just FYI:
>> I only use Intel.
>> I only use genuine Windows or UNIX for networked labs.
>> And I only use prevalent 32-bit client version for normal, "mass-market"
>> softwares" such as Office, productivity, communications, etc.
>> I use 64-bit only for hard-core floating point intensive softwares such
>> as CAD, Image & Video editing, engineering simulations.
>>
>> Basically you invite problems by violating all above. Don't use AMD,
>> don't flirt with 64 bit UNLESS you know 100% your printer driver was
>> TESTED to work in 64-bit Windows.
>>
>> No wmy suggestion is goback to printer mfg's website and check if 64-bit
>> driver update is available, and replace yours if available.
>>
>> If not, wait for more responses.
>

Really dissing AMD does not solve my problems, If you have nothing
constructive to say, please keep it to yourself!

"Stan Starinski" <China@stealsUSJobsPatentsSoftwareMusicVideo> wrote in
message news:#5woM#...
> Wait for responses but Just FYI:
> I only use Intel.
> I only use genuine Windows or UNIX for networked labs.
> And I only use prevalent 32-bit client version for normal, "mass-market"
> softwares" such as Office, productivity, communications, etc.
> I use 64-bit only for hard-core floating point intensive softwares such as
> CAD, Image & Video editing, engineering simulations.
>
> Basically you invite problems by violating all above. Don't use AMD,
> don't flirt with 64 bit UNLESS you know 100% your printer driver was
> TESTED to work in 64-bit Windows.
>
> No wmy suggestion is goback to printer mfg's website and check if 64-bit
> driver update is available, and replace yours if available.
>
> If not, wait for more responses.

I told you last month to PLONK this moron.

--


"Don't pick a fight with an old man.
If he is too old to fight, he'll just kill you."


"Nig" <> wrote in message
news:uy6oV#...
> Really dissing AMD does not solve my problems, If you have nothing
> constructive to say, please keep it to yourself!
>
> "Stan Starinski" <China@stealsUSJobsPatentsSoftwareMusicVideo> wrote in
> message news:#5woM#...
>> Wait for responses but Just FYI:
>> I only use Intel.
>> I only use genuine Windows or UNIX for networked labs.
>> And I only use prevalent 32-bit client version for normal, "mass-market"
>> softwares" such as Office, productivity, communications, etc.
>> I use 64-bit only for hard-core floating point intensive softwares such
>> as CAD, Image & Video editing, engineering simulations.
>>
>> Basically you invite problems by violating all above. Don't use AMD,
>> don't flirt with 64 bit UNLESS you know 100% your printer driver was
>> TESTED to work in 64-bit Windows.
>>
>> No wmy suggestion is goback to printer mfg's website and check if 64-bit
>> driver update is available, and replace yours if available.
>>
>> If not, wait for more responses.
>

?

"Michael" <> wrote in message
news:...
> I told you last month to PLONK this moron.
>
> --
>
>
> "Don't pick a fight with an old man.
> If he is too old to fight, he'll just kill you."
>
>
> "Nig" <> wrote in message
> news:uy6oV#...
>> Really dissing AMD does not solve my problems, If you have nothing
>> constructive to say, please keep it to yourself!
>>
>> "Stan Starinski" <China@stealsUSJobsPatentsSoftwareMusicVideo> wrote in
>> message news:#5woM#...
>>> Wait for responses but Just FYI:
>>> I only use Intel.
>>> I only use genuine Windows or UNIX for networked labs.
>>> And I only use prevalent 32-bit client version for normal, "mass-market"
>>> softwares" such as Office, productivity, communications, etc.
>>> I use 64-bit only for hard-core floating point intensive softwares such
>>> as CAD, Image & Video editing, engineering simulations.
>>>
>>> Basically you invite problems by violating all above. Don't use AMD,
>>> don't flirt with 64 bit UNLESS you know 100% your printer driver was
>>> TESTED to work in 64-bit Windows.
>>>
>>> No wmy suggestion is goback to printer mfg's website and check if 64-bit
>>> driver update is available, and replace yours if available.
>>>
>>> If not, wait for more responses.
>>

What part of "plonk Stan the moron" don't you understand?

--


"Don't pick a fight with an old man.
If he is too old to fight, he'll just kill you."


"Nig" <> wrote in message
news:...
> ?
>
> "Michael" <> wrote in message
> news:...
>> I told you last month to PLONK this moron.
>>
>> --
>>
>>
>> "Don't pick a fight with an old man.
>> If he is too old to fight, he'll just kill you."
>>
>>
>> "Nig" <> wrote in message
>> news:uy6oV#...
>>> Really dissing AMD does not solve my problems, If you have nothing
>>> constructive to say, please keep it to yourself!
>>>
>>> "Stan Starinski" <China@stealsUSJobsPatentsSoftwareMusicVideo> wrote in
>>> message news:#5woM#...
>>>> Wait for responses but Just FYI:
>>>> I only use Intel.
>>>> I only use genuine Windows or UNIX for networked labs.
>>>> And I only use prevalent 32-bit client version for normal,
>>>> "mass-market" softwares" such as Office, productivity, communications,
>>>> etc.
>>>> I use 64-bit only for hard-core floating point intensive softwares such
>>>> as CAD, Image & Video editing, engineering simulations.
>>>>
>>>> Basically you invite problems by violating all above. Don't use AMD,
>>>> don't flirt with 64 bit UNLESS you know 100% your printer driver was
>>>> TESTED to work in 64-bit Windows.
>>>>
>>>> No wmy suggestion is goback to printer mfg's website and check if
>>>> 64-bit driver update is available, and replace yours if available.
>>>>
>>>> If not, wait for more responses.
>>>