Events Queue

EventID.Net Comments Queue

Comments for event ID 9 currently in the processing queue.

Note: We have not reviewed this information yet so it is unfiltered, exactly how it was submitted by our contributors.

Event ID: 9
Event Source: jahci
Event Type: Warning
Event Description: A pending interrupt was detected on device \Device\Scsi\JAHCI1 during a timeout operation.  A large number of these warnings may indicate that the system is not correctly  receiving or processing interrupts from the device.

For more information see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 54 00   ......T.
0008: 00 00 00 00 35 00 04 80   ....5..€
0010: 15 02 00 00 03 01 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........

Comment:

Event ID: 9
Event Source: atapi
Event Type: -
Event Description: -
Comment: Read Event Viewer. IDE-port 0 not responding within the timeout period.
Could be HDD 0 or IDE/ATAPI controller, but first:
Check the cables from the MB to the HDD.
Check the operation of any other devices connected to the same cable as HDD 0 - even disconnect any CD/DVD drives on that cable. Index: 2060

Event ID: 9
Event Source: atapi
Event Type: -
Event Description: -
Comment: In my case, this problem was solved after uninstalling KASPERSKI AV/IS Index: 2060

Event ID: 9
Event Source: adpu160m
Event Type: -
Event Description: -
Comment: Also take a look at the same Source, EventID 11 - You might simply have forgotten to ground a newly installed device correctly. Especially when the device is decoupled using rubber attenuators. Index: 2059

Event ID: 9
Event Source: atapi
Event Type: -
Event Description: -
Comment: In my case, error indicated \Device\Ide\IdePort1
upon going to registry, went to regedit and navigated to hkeylocalmachine\ hardware\devicemap\scsi\scsi port 1 - noticed it was labeled as "cdrom peripheral" - replaced cdrom drive, no more errors Index: 2060

Event ID: 9
Event Source: Sophos Anti-Virus
Event Type: Error
Event Description: "c:\WINDOWS\tbicd2hd.exe" returned SAV Interface error oxaoo40210: The file could not be accessed.
Comment:

Event ID: 9
Event Source: tsmlvsa
Event Type: Error
Event Description: Encountered create freeze point error [C0000184].
Comment:

Event ID: 9
Event Source: SideBySide
Event Type: Error
Event Description: Log Name:      Application
Source:        SideBySide
Date:          7/29/2011 8:20:07 AM
Event ID:      9
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      NWODLR.mka.local
Description:
Activation context generation failed for "C:\Program Files\Google\Connect\Office\2.0\adxloader.dll.Manifest".Error in manifest or policy file "C:\Program Files\Google\Connect\Office\2.0\adxloader.dll.Manifest" on line 2. The manifest file root element must be assembly.

Comment: I think this error is related to doing searches. It seems that when I try to search for a particular file or document my Explorer locks up and closes unexpectedly. When doing some research on this issue I found a site where someone commented stating it was related to how Adobe displays pdf files in the preview of Explorer. They recommend a registry change. The article was found here: http://news.office-watch.com/t/n.aspxa=1350

Event ID: 9
Event Source: GFI EventsManager
Event Type: Warning
Event Description: <xml version="1.0" encoding="utf-16">
<CheckResults xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <checkID>2</checkID>
  <setID>0</setID>
  <checkResult>0</checkResult>
  <computer>matute.local</computer>
  <resultDetails>
    <string>624 milliseconds</string>
  </resultDetails>
</CheckResults>.

Comment:

Event ID: 9
Event Source: mv61xx
Event Type: Error
Event Description: The device/DEVICE/Scsi/mv61xx1 hasn''t answered within the fault waiting time.
Comment: