IRP StackSize BSOD

Vista Ultimate SP1.

Was using Kaspersky Internet Security v7 with no problems. Upgraded to
v8 for the claimed better security, it was a free upgrade.

With KIS v8, whenever I try to send or receive more than a trivial
amount of data between the Vista machine and a mapped network drive (on
an XP Pro machine, if it makes any difference) I get a BSOD about
insufficient IRP_STACKSIZE.

The only semi-relevant info I've been able to locate in the MS KB is
http://support.microsoft.com/kb/285089 which gives info about the
parameter, its default setting and range. And Vista is conspicuously
missing from the article's list of "Applies to" versions of Windows. I
made the change anyway, which neither broke anything nor fixed the
problem. I tried incrementing the setting up as high as decimal 45
before giving up, as I started to notice a hit on my available system
memory. And I did reboot after each change to the registry key.

Reverting back to KIS v7 and the problem goes away.

Kaspersky support pointed me to the same KB article.

Assuming I'm still interested in putting KIS v8 on my Vista machine,
what now?

Note that the same version of KIS is running without any problems on my
XP Pro SP3 machine.

--
Jeffrey Kaplan www.gordol.org
Double ROT13 encoded for your protection

"If I am ever the Hero top 100 list: #25. I will never travel back
into the past in order to prevent the current situation. It never
works.

On Mon, 09 Feb 2009 19:30:45 -0500, Jeffrey Kaplan <>
wrote:

>Vista Ultimate SP1.
>
>Was using Kaspersky Internet Security v7 with no problems. Upgraded to
>v8 for the claimed better security, it was a free upgrade.
>
>With KIS v8, whenever I try to send or receive more than a trivial
>amount of data between the Vista machine and a mapped network drive (on
>an XP Pro machine, if it makes any difference) I get a BSOD about
>insufficient IRP_STACKSIZE.
>
>The only semi-relevant info I've been able to locate in the MS KB is
>http://support.microsoft.com/kb/285089 which gives info about the
>parameter, its default setting and range. And Vista is conspicuously
>missing from the article's list of "Applies to" versions of Windows. I
>made the change anyway, which neither broke anything nor fixed the
>problem. I tried incrementing the setting up as high as decimal 45
>before giving up, as I started to notice a hit on my available system
>memory. And I did reboot after each change to the registry key.
>
>Reverting back to KIS v7 and the problem goes away.
>
>Kaspersky support pointed me to the same KB article.
>
>Assuming I'm still interested in putting KIS v8 on my Vista machine,
>what now?

Find a way to stop yourself from being interested until Kaspersky
comes up with an incremental version change.

>Note that the same version of KIS is running without any problems on my
>XP Pro SP3 machine.

Previously on microsoft.public.windows.vista.general, Steve McGarrett
said:

> >Assuming I'm still interested in putting KIS v8 on my Vista machine,
> >what now?
>
> Find a way to stop yourself from being interested until Kaspersky
> comes up with an incremental version change.

As far as that, goes, my current Kaspersky license expires in just over
a month. Elsewhere, ESET is being recommended.

Would like to find an actual solution to this issue though.

Update: Kaspersky support recommended that I get and install the
current build due to prior similar problems when v8 was initially
released. I have the current build. Downloaded last week, and
besides, the thing checks for and installs updates automatically for
both the database and program files when installed and then
periodically after.

--
Jeffrey Kaplan www.gordol.org
Double ROT13 encoded for your protection

"If I am ever the Hero top 100 list: #25. I will never travel back
into the past in order to prevent the current situation. It never
works.