Event Viewer Error 9
Contents |
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to event viewer error 4201 see an entire company using just one server, these days that's no longer the case. event viewer error 10016 New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on event viewer error 10 these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking
Event Viewer Error 55
on any of the servers. read more... Event ID: 9 Source: iaStor Source: iaStor Type: Error Description:The device \Device\Ide\iaStor0 did not respond within the timeout period. English: This information is only available to subscribers. An example of English, please! Comments: Christopher In my case, the Lenovo Quick Test Disk Diagnostic Utility (had to be downloaded) revealed that there is an unreadable sector on the C drive, and that appears to be the cause of this error event viewer error 7001 message from iaStor. It appears that since the drive can not read from the bad sector, the drive is timing out on read requests for that sector. The newly installed ShadowCraft Shadow Protect Desktop software would not create a backup of the C drive because of the bad sector. Image for Windows (still installed but just deprecated) however, has a setting that allows it to continue even if there are I/O errors. If necessary I hope to use that setting to get a snapshot of the drive that I can re-image to a new drive. Some app may need to be reinstalled if it's got a key file that includes the bad sector. But I'm counting on the rest of the image from Image for Windows being good to get the re-imaged computer up and running quickly for the client, with a new hard drive. The computer is a Lenovo ThinkCentre Desktop MT 7052, with 500G factory HDD. x 159 Anonymous I had this problem myself. I talked to Intel, GigaByte and Samsung with no luck. Then I found this. As Tim said. This is a most probably a power problem. Glitches in the SATA power cable or the SATA cable itself. x 170 Rick Valstar Seems Vista made the problem worse, see the "Possible issues with Windows Vista" link. I'm still running WXP and W2K3 and still having issues
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it event viewer error codes list was still common to see an entire company using just one server, these days that's
Event Viewer Error 36888
no longer the case. New computers are added to the network with the understanding that they will be taken care of by
Event Viewer Error 10010
the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything http://www.eventid.net/display-eventid-9-source-iaStor-eventno-7933-phase-1.htm is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 9 Source: atapi Source: atapi Type: Error Description:The device, \Ide\IdePort0, did not respond within the timeout period. English: This information is only available to subscribers. An example of English, please! Comments: Anonymous In my case, this problem was solved after uninstalling KASPERSKI AV/IS. x 11 Anonymous In my case, error indicated \Device\Ide\IdePort1. Upon going to http://www.eventid.net/display-eventid-9-source-atapi-eventno-2060-phase-1.htm registry, went to regedit and navigated to hkey_local_machine\hardware\devicemap\scsi\scsi port 1 - noticed it was labeled as "cdrom peripheral" - replaced cdrom drive, no more errors. x 4 John Panton Message: IDE-port 0 not responding within the timeout period. It 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. x 9 Alexander Solano In my case, this problem was solved after uninstalling Roxio's Easy CD Creator 5.0. There are known compatibility issues between Windows XP and versions of Easy CD Creator earlier than version 5.1. See ME310628 for details. x 51 Peter Hayden In one case, a computer was running Windows 2000 Professional SP4 that was configured to boot from a SCSI drive. An IDE drive was temporarily added in order to perform some work on it. When the computer was started this event was repeated four times and then followed by EventID 11 from source atapi. Windows showed the disk as normal but Partition Magic 8.0 showed it as "BAD". Remove or replace the faulty hard drive. x 54 Anonymous Getting this error could mean that your hard disk controller is not working well.
Gaming Smartphones Tablets Windows 8 PSUs Android Your question Get the answer Tom's Hardware>Forum>Systems>Why am I getting Error iaStor ent id 9 on my event log?> Why am I getting http://www.tomshardware.com/forum/216269-31-error-iastor-event Error iaStor ent id 9 on my event log? Tags: Homebuilt NAS / RAID Systems Last response: 16 July 2009 03:04 in Systems Share 430752 3 January 2007 21:11:21 My build is an AW9D-Max mobo, Intel e6600 cpu, 2x1gig Curcial Ballistix Ram, WD Raptor X 150gig HD (non-raid) used for Windows XP Pro SP2 and programs, 2x Samsung Spinpoint P 250gig drives event viewer in Raid 0 array, Evga geForce 7900 GTO, 2x samsung dvd-ram r/w drives, Abit uguru panel and digital doc5+ panel. Built about one month ago, been adding software, programs, periphs and generally getting things tidy since then. However, since I reinstalled windows in order to install Intel Matrix drivers using F6 method, (about 2 weeks ago) my system has been hanging after the event viewer error BIOS loads and Windows boots (after the windows splash screen with the progress bar) but before Windows actually loads and can be used. The "hang" time lasts between 10 and 30 seconds, but usually at 15 secs or so. This has been after I reinstalled Windows to install the Intel Matrix drivers so as to use RAID (but not for my Raptor boot harddrive, which is NOT part of my RAID array). I did not get this problem before initialising RAID and installing these drivers (although I had other problems resulting from not having proper drivers installed, which I resolved through OS reinstall with F6 process). What happened was two days ago I installed a Canon MP printer driver. Since then, I've had one BSOD per day (e.g., 2 BSOD's total). So, trying to figure this out, with an Stop Code of 100000d1 (DRV-IRQ), I read to check my Event Log for clues. So, I went into event log and looked under system errors and saw the once daily System Error for BSOD, but also saw a recurring error for an "iaStor" error, logged with ev