Possible conflict with Iomega REV (Win XP, SP2)

Avast Free Antivirus / Premium Security
1

Hello,

I have recently installed an Iomega REV (external Firewire) drive on a PC running Windows XP SP2, with Avast! Home 4.5.549. It seems there is some conflict between Avast! and the REV drive and I would like to know whether anyone else has experienced this problem and knows of a solution or work-around.

The problem is quite repeatable when Avast! on-access protection is enabled: if I use Windows Explorer to copy and paste files or directories onto the REV drive, the system instantly re-boots without doing the copy/paste - there is no error message or blue screen whatsoever, it just drops immediately back to the BIOS as if by a hardware reset.

The problem does not occur if I copy/paste to any other drive, or if I copy files using the command prompt, or if Avast! on-access protection is disabled (using the “Stop On-Access Protection” command from the Avast! system tray icon). Also, it seems that once I have copied one or more files to the REV using the command prompt, copy-and-paste to the REV drive then works correctly!

I am using up-to-date drivers for the REV, which apart from this nuisance seems to work fine. I have no other third-party disc or file system related drivers installed, such as for writing CDs/DVDs.

Any solutions, work-arounds or suggestions as to how to debug this problem would be greatly appreciated.

Thanks!

2

Disable auto-reboot on your system and you should get a BSOD when something really goes wrong. Write down the error on the BSOD and let us know.

3

Thanks for the tip, Eddy. The blue screen has some generic messages but the only specific details are:

*** STOP: 0x0000008E (0xC0000005, 0x804E19EA, 0xF0CBEA04, 0x00000000)

I also checked the system event log, which has an Error event with the following details:

Source: System Error
Category: (102)
Type: Error
EventID: 1003
Error code: 1000008e
Parameters: 0xc0000005, 0x804e19ea, 0xf0cbea04, 0x00000000

I hope this is useful…

4

Can you follow this?

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
(http://msdn.microsoft.com/library/en-us/ddtools/hh/ddtools/BCCodes_12795dee-19a9-4461-a135-bbb882b81455.xml.asp)
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compability issues (which sometimes means a driver issue or a need for a BIOS upgrade).

“STOP 0x0000008e” Error Message During Windows XP Setup
http://support.microsoft.com/?kbid=315335&sd=RMVP

Games: “Stop” Error Message That References Nv4_disp.dll
http://support.microsoft.com/?kbid=325730&sd=RMVP

Your Computer Stops Responding When You Use the Highlighter Feature & the Font Color Feature
http://support.microsoft.com/?kbid=829578&sd=RMVP

5

Thanks, Technical - you beat me to posting the MSDN link…

It seems to say that the problem is down to an invalid memory access at address 0x804e19ea, but I don’t know how to track it down further. If it is a memory access fault it could be hard to find the original source of the problem anyway.

6

During the BSOD, a dump should be created (WinNT/Minidump).
It should contain some useful information…

7

There are some freeware to test memory (maybe ‘Links’ on my signature can give you a help). Anyway, Google is on its way 8)

8

Hello igor - yes, there is a Minidump. I’ll try to find some way of analysing it, and will post whatever I can dig out.

Technical - the system memory has been tested using Memtest86 and is working fine. The system is completely stable (famous last words!) except for the exact scenario I described.

9

The best way of analysing the minidump would be sending it to vlk@avast.com :slight_smile:

10

Igor - thanks for the suggestion - done!

11

??? Has there been any resolution to this issue?

I am having the same problems but with WinXP x64 Edition build 1289 and Iomega’s REV drive. All works fine til I install Avast. Uninstallation corrects the issue. Other zip drives were o.k.(atapi 250 and atapi 750) Only did the Win install , SB Audigy drivers 010405, REV system software 3005 (drivers only, no software as yet) and then Avast home 4.5.

12

Well, there is some hope…

I just downloaded a new version (3.0.1) of the Iomega REV System Software from their support pages, and it looks like the problem has “gone away”. I will keep playing with it over the next few days and post again if I see any crashes.