Event Id 11 Aic78xx
However, serious problems might occur if you modify the registry incorrectly. Sometimes a low-level format performed by the SCSI controller will resolve these event messages. Our Products Main Page Applications .Net Framework Error AOL Browser Errors Installer Errors Internet Explorer Macro Errors Media Player MS Outlook Network Errors Outlook Express Windows Live Articles DLL Errors Exe And did you install Seagates drive overlay program? 0Votes Share Flag Collapse - by Dragon Emperor · 13 years ago In reply to I used PowerQuest DriveImage 2002 to copy and this contact form
See ME188646 for a possible cause of this event`s appearance. The system boots fine. 0Votes Share Flag Collapse - by Don_C · 13 years ago In reply to System Log Events you copy from 80gig to 200gig even if they were Slow down the transfer rate settings if timeouts are associated with tape drives; using a 5-mbs transfer rate usually cures the timeouts. Remove any other controllers that might create bus contention issues. internet
Join Us! *Tek-Tips's functionality depends on members receiving e-mail. Also you can check the cabling on the device named in the message. This website should be used for informational purposes only. If the source of the error is a tape drive, set the sync transfer rate in CTRL-A to a lower setting to troubleshoot.
Source aic78xx Category None Event ID 11 The driver detected a controller error on \Device\Scsi\aic78xx1. When you have a long chain of cables with mixed internal and external cabling, you run the risk of degrading the signal. x 7 EventID.Net For some troubleshooting tips to help diagnose and pinpoint the problem see ME154690. Share Flag This conversation is currently closed to new comments. 15 total posts (Page 1 of 2) 01 | 02 Next + Follow this Discussion · | Thread display:
The source of this message can also be various controller installed on the system i.e. Private comment: Subscribers only. The source of the error could have been a connector on the CDROM, because we swapped in a known good cable and it still gave that error. If Windows NT is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file.
You can leave a response, or trackback from your own site. Every time the system boots it gives a series of 15 events of the types previously listed. Replacing the CDROM fixed the issue. Check the revisions of the SCSI controller BIOS and of device firmware, and obtain the latest revisions from the manufacturer. (There is a procedure for checking the model number and firmware
registration for the full version is $29.95 USD for 1-year subscription to use all the features.
If both internal and external SCSI devices are attached, make sure that the last device on each SCSI chain is terminated, and make sure that intermediate devices are not terminated. weblink If there is only a single SCSI chain (either all internal or external), make sure that the last device of the SCSI chain is terminated and that the SCSI controller itself Many modern SCSI controllers require active terminators (at least one of the devices on the bus must provide termination power). The SCSI driver is located in the %Systemroot%\System32\Drivers directory.
When troubleshooting, we detached the CDROM and tape drive from the controller and the error stopped. I ran Seagate's utility and it reports both drives are fine, as does chkdsk. Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? navigate here This is usually a BIOS setting.
Like this:Like Loading... See example of private comment Links: ME153128, ME154690, ME188646, ME211214, ME259237, ME289189, ME314093, Veritas TechNote ID: 231918, Event id 9 from adpu160m Search: Google - Bing - Microsoft - Yahoo - Possible Solution: http://www.eventid.net/display.asp?app=Top10&eventid=11 This is usually caused by inadequate or faulty SCSI termination.
Check the Microsoft Hardware Compatibility List to verify that the hardware that you have removed and its drivers are compatible with Windows NT.
I have 2GB of RAM. Look for loose or poor-quality SCSI cabling. If there is no Last Known Good configuration, try using the Emergency Repair Disk. Close this window and log in.
x 6 Friedrich When the I/O request expires (times out), the driver resets the SCSI bus. Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber? If the message continues to appear, select the Last Known Good option when you reboot. his comment is here The following event ID messages may be logged in your system log (use Event Viewer to view the log), although the source can be any controller name (for example, Atdisk, Atapi,