Please click the link below for your operating system to download the TSG SysInfo Utility. Click on "Save File" then double-click the file to run it. Copy and paste the report in your initial post. Windows 7 and later (downloads a file named tsginfo.exe) | Windows XP (downloads a file named SysInfo.exe)

XP error log

1119 Views 1 Reply 2 Participants Last post by Rollin' Rog, Sep 16, 2003

garyf

Discussion Starter · Sep 16, 2003

I recently installed XP Home Edition, like last week. I looked at the XP error log and found I had 18 pages of errors. I would appreciate help on what is causing these errors and how to fix.

1. Service Control Manager (212 errors). "The Application Management service terminated with the following error: The specified module could not be found."

2. ACPI (76 errors). "AMLI: ACPI BIOS is attempting to write to an illegal IO port address (0x70), which lies in the 0x70 - 0x71 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance."
(How would I know which system it is and what program or what device is causing this?)

3. ATAPI (10 errors). "The device, |Device\Ide\Ide\Port1, did not respond within the timeout period."
(Again how do I know what device this is?)

4. DCOM (47 errors). "The server {520CCA63-51A5-11D3-9144-00104 BA11C5E} did not register with DCOM within the required timeout.

5. Cdrom (21 errors). "The device, \Device\Cdrom1, has a bad block.

I can not play my CDROM that is in the computer...it says no disc in D drive...I can only play Windows Media Player..

Any help on these would certainly be appreciated.

Thank you for taking the time to respond to my concerns.

Gary

Save

Status: Not open for further replies.

1 - 2 of 2 Posts

Rollin' Rog

· #2 · Sep 16, 2003

It sounds like you may have installed XP using an outdated motherboard. BIOS updates are very risky, but that is what MS suggests:

http://support.microsoft.com/defaul...port/kb/articles/q283/6/49.asp&NoWebContent=1

On the cd rom message, about all I can suggest is checking through google and google groups, many others have had it; perhaps a bad lens on the drive?

http://groups.google.com/groups?q=T...lr=&ie=UTF-8&oe=utf-8&newwindow=1&sa=N&tab=wg

As for the DCOM error, it may not be significant. In fact it is a security risk all together, you might try disabling dcom using Steve Gibson's approach and see if that rids the event viewr of it.

http://grc.com/dcom/

Save

1 - 2 of 2 Posts

Status: Not open for further replies.

Top Contributors this Month