iPod causes Bluescreen when Windows detects it

[Thomas Adams]

I have been using a Mac-formatted iPod (2nd gen. - FW only) successfully for
a while. I use "MacOpener 6.05" in order to access the iPod.

Recently the computer started to crash (Bluescreen) when I connect the iPod.
As soon as Windows detects its presence (you hear the "new device detected"
sound) it will bluescreen and present the following error message:

NO_MORE_IRP_STACK_LOCATIONS
STOP: 0x00000035

As this functioned very well for a while I suspect the following software to
be the culprit. It was installed by our system administrators and is here to
stay:
- Kaspersky antivirus
- SUS client

Does anybody know if the problem could really be caused by these programs?
An additional reason for me to believe this is the fact that my PC at home
which is not using these programs does not crash when I attach the iPod.

Is there any way for me to trace the problem so that I *know* what's causing
this?

thanks,
Thomas

 

[Larry Sabo]

Recently the computer started to crash (Bluescreen) when I connect the iPod.
As soon as Windows detects its presence (you hear the "new device detected"
sound) it will bluescreen and present the following error message:

NO_MORE_IRP_STACK_LOCATIONS
STOP: 0x00000035

As this functioned very well for a while I suspect the following software to
be the culprit. It was installed by our system administrators and is here to
stay:
- Kaspersky antivirus
- SUS client

Does anybody know if the problem could really be caused by these programs?
An additional reason for me to believe this is the fact that my PC at home
which is not using these programs does not crash when I attach the iPod.

Is there any way for me to trace the problem so that I *know* what's causing
this?

thanks,
Thomas

I just tried to install Kaspersky Anti-Virus Personal on my Win2K
system last week and got the same error message and a memory dump.
Fortunately, I was able to restore my WINNT directory from a recent
back-up. Adding IRPStackSize (REG_DWRD) to
HKLM\System\CurrentControlset\Lanmanserver\Parameters\ with a value of
0x0b as suggested in some web references did nothing.

Kaspersky has yet to answer my e-mail requesting help, sent March 4th.

Sorry I don't have a solution to offer, but will post one when I find
one.

Larry

 

[Brandon]

What I think is happening with the Ipod, is that the real-time monitor
function of KAV is trying to scan your Ipod when you plug it in and
some kind of incompatibility between KAV and something in your system
rears its ugly head at that time. I have problems with the monitor
function of KAV on my system. My windows 2000 installations will not
even boot if I have the KAV monitor installed. My Windows XP
installation will boot but it is unstable with the Kaspersky real-time
monitor installed. The error is the same as you speak of
"no_more_irp_stack_locations" The details are below:

I recently downloaded a copy of KAV Pro. After installing the
product, the installer asks me to reboot my machine, so I do…and on
the next boot, I get a blue screen error that reads
"no_more_irp_stack_locations". I have to restart in safe mode and then
uninstall KAV so that my machine will boot.

I tried everything to get this error to go away. I tried uninstalling
my video driver; I tried removing all over clocking from my CPU and
memory; I tried using very conservative settings in my bios like
disabling video bios caching and memory holes.

I tried disconnecting all of my USB devices except for my internal
card reader. I tried increasing the IRPStackSize value in my registry
to 20 and then 30 and then 50. It still refused to boot. I then tried
selecting only certain components of KAV in my installation. I found
that my machine will boot if I install KAV without the real time
monitor. As soon as I install the real time monitor…boom…my machine
kicks the "no_more_irp_stack_locations" blue screen error on the next
boot. This is happening on my machine with both of my operating
systems. The error is the same on both Windows 2000 and XP except on
XP it happens on shutdown instead of boot for some reason. I tried
the latest KAV 4.5.0.94 version from your site as well as the new KAV
5.0 beta 2; both versions will not work on my system.

I have never, ever, had a blue screen error on my system prior to
this. The following security products have worked well on my system
without any problems: NOD32, NIS 2003, NIS2004, MacAfee VirusScan,
TDS-3, TrojanHunter, Sygate Pro, Zonealarm Pro, and Grisoft AVG. None
of them are currently installed…I just want you to know that my system
has accepted these other program in the past without any troubles.

After much head scratching, I decided to do a completely fresh
installation of windows and try it again. I reformatted and
reinstalled windows on my disk and tried installing KAV again. The
same thing happened on the first reboot after installation. I decided
to dig deeper into my bios at this point. I started disabling
peripherals and then tried booting after each one was disabled. As a
last resort, I moved my boot drive to the standard Intel IDE
controller and then tried disabling my IDE RAID controller, it is a
High Point HPT374 RAID controller that is integrated into my Abit
motherboard...I found that disabling the HPT374 RAID controller
allowed my machine to boot with the KAV monitor installed. This is
not a solution, but at least it gives us some direction. After
discovering this, I tried updating my RAID controller's drivers and
bios but the error was persistent. My conclusion is that currently
KAV is not compatible with systems that have a HPT374 IDE RAID
controller or more specifically --- with the Abit IT7 motherboard.
Perhaps KAV is also not compatible with other RAID controllers. This
is unfortunate because the HPT374 controller was used exclusively in
many of the new Abit boards that have been released in the past few
years. There are many potential customers out there that have the
same configuration as this. Here is a link to the manufacturer of my
RAID controller http://www.highpoint-tech.com . Here is a link to my
motherboard manufacturer's web site
http://www.abit-usa.com/products/mb/products.php?categories=1&model=33
.. Lastly, here is a link to a google groups search query. It will
show you that there are others who are experiencing this problem as
well: http://groups.google.com/groups?hl=..._stack_locations+kaspersky&btnG=Google+Search
..


Please help me sort this out

--------------------------------------------------------------------------------


My system specs are below:

Motherboard: Abit – IT7
Video card: Vision Tek Geforce4 ti4200
Processor: Pentium 2.2b Northwood (BX80532PE2266d)
Memory: 512mb Corsair pc3000 memory stick (CMX5123000C2)

Hard drives: Qty (1) Western Digital 80GB (WD800JB)
Qty (1) Western Digital 40GB (WD400BB)
Qty (2) Toshiba (formerly IBM) 40GB
Deskstar 120GXP (IC35L040AVVA07)

All drives are installed on the HPT374
IDE RAID controller of the Motherboard

Floppy drive: Sony
DVD+R/W-R/W drive: Sony (DRU500ax)
Modem: USR (5610b) Controller Based PCI Modem
Power supply: ANTEC TruePower 430
CD RW Drive: Sony (CRX220A1)
Case: Lian-li (PC-65)
USB keyboard: Microsoft Wireless Optical Desktop Elite
USB mouse: Microsoft Wireless Intellimouse Explorer
USB PCI Card: ADS Technologies USB Turbo 2.0 PCI card
Card Reader: Atech Flash Technologies 9 in 1
internal/external USB 2.0 flash card reader

Printer: HP Office Jet G55 All-in-one
Web cam: Logitech Quickcam

 

[Brandon]

A solution to this problem was provided to me by Kaspersky's Support
team.

There is a registry entry that controls the load order of the
Kaspersky driver that causes this error.

The key is located at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Klif

Inside of the Klif key is an entry named "Start" the default value is
1.

The possible values for the entry are 1,2, and 3.

The values define the order of driver load:

1. Boot
2. Automatic
3. Demand

Level "2" allows the driver to load after all main drivers have been
loaded.

Kaspersky asked that I try using value "2" by booting into safe mode
and changing the value. They said that this does not reduce
protection level at any rate, but can solve conflicts that can occur
with the IRP stack.

I followed their advice and changed the value from 1 to 2 and it fixed
the problem.