EventID 6004: A driver packet from the I/O Subsystem.... error on Windows 2003

We get several of these error messages a day on our Event Viewer. The computer is a Windows 2003 server with SP2.

Having read up on previous threads dedicated to this, I can assure you that we don't have McAfee installed on here (We have AVG 8 Network Edition). Also Windows said that my driver for our network adapter is up to date.

After reading KB171332 I ran NET CONFIG WORKSTATION. Here is the result (with server name and domain changed)

C:\Documents and Settings\Administrator\My Documents>net config workstation
Computer name                        \\SERVERNAME
Full Computer name                   SERVERNAME.DOMAIN.ORG
User name                            Administrator

Workstation active on
        NetbiosSmb (000000000000)
        NetBT_Tcpip_{B39CA089-2F3D-43D5-BF67-70B54E660202} (001422B36C60)
        NetBT_Tcpip_{67A1FABB-B269-4A97-9750-39CDF8748829} (005345000000)

Software version                     Microsoft Windows Server 2003

Workstation domain                   DOMAIN
Workstation Domain DNS Name          DOMAIN.ORG
Logon domain                         DOMAIN

COM Open Timeout (sec)               0
COM Send Count (byte)                16
COM Send Timeout (msec)              250
The command completed successfully.

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

Is there anything else I can try and look at? We've been having a lot of server instability lately and I'm trying to rule out any possible causes of that, so any help would be appreciated. Thanks!
caitechAsked:
Who is Participating?
 
ChiefITConnect With a Mentor Commented:
Well, as I am sure you have done, I did a lot of research on this issue. I did find others with similar issues and running AVG, that may be a common factor.

I think what we need to do is find the actual funky driver.

This appears to be a very hard thing to track. Within the text of the error, is there anything that says what system driver it is.( xxx.sys)?

If not, maybe poolmon will pick it up as a free or used memory block, (you know a memory leak).

Another thing we could do is prevent it from restarting upon error, this is assuming the problem reboots the computer. If you prevent it from restarting upon error you should see a memory dump or Blue Screen of death on the error.

Another thing you might try is Driver verifyer:
http://support.microsoft.com/kb/244617

Let me know if you need additional information on any of these.
0
 
ChiefITCommented:
Netconfig looks good:

Does this Event error tell us what the driver is?

xxx.sys?
0
 
ChiefITCommented:
Also what service pack are you on?

If on SP1, consider downloading and installing SP2
0
 
caitechAuthor Commented:
We are on SP2. How would I find out the exact driver that is causing this?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.