Re: Error 7023

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Here goes my life story... Hope it makes more sense to you than it does to
me...

Also, even if I have just restarted computer and opened nothing more than OE
and SystemInformation, memory is down to 8.52 MB. Is this normal?


Nome do SO Microsoft Windows XP Home Edition
Versão 5.1.2600 Service Pack 3 Compilação 2600
Fabricante do SO Microsoft Corporation
Nome do sistema SMALL
Fabricante do sistema TOSHIBA
Modelo do sistema Satellite 1900
Tipo do sistema X86-based PC
Processador x86 Family 15 Model 2 Stepping 4 GenuineIntel ~1993 Mhz
Data/versão de BIOS TOSHIBA V2.10, 10/07/2003
Versão SMBIOS 2.31
Directório do Windows C:\WINDOWS
Directório do sistema C:\WINDOWS\system32
Dispositivo de arranque \Device\HarddiskVolume1
Localização Espanha
Camada de abstracção de hardware (HAL) Versão = "5.1.2600.5512
(xpsp.080413-2111)"
Nome de utilizador SMALL\Qim
Fuso horário Hora de Verão de GMT
Memória física total 256.00 MB
Memória física disponível 8.52 MB
Memória virtual total 2.00 GB
Memória virtual disponível 1.96 GB
Espaço de ficheiro de página 626.25 MB
Ficheiro de paginação C:\pagefile.sys


I have a laptop Toshiba Satellite1900-303.
"R. McCarty" <PcEngWork-NoSpam_@xxxxxxxxxxxxxx> escreveu na mensagem
news:uBA9U2l7IHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
No problem on providing assistance.

Usually the key to BIOS updating is HOW many revisions down your
current BIOS firmware is from the latest available. It's also a good idea
to read the change log for each release. (Readme.Txt or a .Pdf file ) &
note whether any releases address APIC compliance issues.

The issue with capped IRQs at 15 may be a BIOS setup problem. On
some motherboards the APIC controller can be disabled. It might
help to know what Vendor/Model motherboard you have in your PC.

There are just too many variables to give you a definitive answer on
why your setup isn't fully mapping IRQs. This problem might also be
the lack of a proper Chipset driver being installed. ( Or out of date ).

"Peter" <abc@xxxxxxxx> wrote in message
news:OcLqttl7IHA.5024@xxxxxxxxxxxxxxxxxxxxxxx
IRQ 15 is the highest number.

Does this sound to you as if I could do with a Bios upgrade?

Thank you veru much for your very comprehensive and professional
information.

JB



"R. McCarty" <PcEngWork-NoSpam_@xxxxxxxxxxxxxx> escreveu na mensagem
news:O$$29kl7IHA.1080@xxxxxxxxxxxxxxxxxxxxxxx
Newer motherboards employ an APIC ( Advanced Programmable
Interrupt Controller ). This extends the original PC IRQ range up
to 23 Interrupt lines. This helps a PC to map devices using IRQ
Sharing. When XP is first installed it interrogates the BIOS to see
if the motherboard supports extended IRQ mapping and loads a
HAL (Hardware Abstraction Layer) driver appropriate for the type
of hardware. From the name, I'd suspect that you have an issue with
some form of APIC support. You can usually determine if your
setup has APIC by using System Info tool, Hardware Resources
category, IRQs - and noting the highest numbered IRQ in the map.

"Peter" <abc@xxxxxxxx> wrote in message
news:%23T8wBfl7IHA.3648@xxxxxxxxxxxxxxxxxxxxxxx
Thank you so much.

Could you give me an idea of what the ID: 1: ACPIEC is all about?

Best

JB


"R. McCarty" <PcEngWork-NoSpam_@xxxxxxxxxxxxxx> escreveu na mensagem
news:uVUMwVl7IHA.1420@xxxxxxxxxxxxxxxxxxxxxxx
Using McAfee almost always inflicts a "Noticeable" performance loss.
So some of your issues are most definitely related to McAfee. The boot
sequence indicates service time outs ( up to 30 Seconds ).

The kind of errors you report can be the result of Registry Cleaning.
It's
like death of a thousand cuts for a PC. The registry is a large
database
of "HIGHLY" interdependent links and associations. Removing what
seems to be invalid keys/values may not result in immediate damage,
but
will show up later as that association is called on.

Registry Cleaning ( & it's merits ) ranks as the top on-going issue
here.
This post is likely to kick off the "Yes it works", "No it Doesn't"
threads.

Unfortunately once the Registry is hacked on, there is no method of
repair to a known valid state. You can probably get the machine back
to
a working state, but you'll never know or trust the integrity of the
Registry.
The time it will take to get a Clean/Error free boot may not be worth
the
effort. I'd be inclined to recommend a fresh install and choose
another
Security product excluding any McAfee or Norton brand.

If you can't resist the urge to clean the Registry at the least invest
in an
imaging program like Acronis True Image and make regular images. This
way when something gets broken you can roll the machine back to a
working/reliable state.


"Peter" <abc@xxxxxxxx> wrote in message
news:%23fpI6pk7IHA.4040@xxxxxxxxxxxxxxxxxxxxxxx
Thank you very much for your help.

As for Registry cleaner the answer is yes. Over the years (4/5) I
have used in the past RegCleaner and more recently CCleaner.

I nver played around with Services, other than in MSconfig, where I
disabled most of what I felt was not necessary at Startup.

The boot is very long! I get the clock after some 15 seconds
followed by the battery and the sound icons, but then I have to wait
some 90/120 seconds for the Internet and McAfee to come up, strangely
usually Internet before McAfee. I have cable connected to a router
and then to the computer through a cable. The delay, I guess in my
ignorance may be due to handshaking between the computer and the
router with McAfee making things worse. Even after all the icons are
up I find it difficult to open anything at all for some time.
Eventually everything works reasonable well, until McAfee or someone
else decides to check updates and then the susytem goes into a crawl,
as if the memory was being hijacked. Checking on CPU use does not
show excessive use which makes it strange why the computer should
virtually hang if the CPU has over 90% free usage.

Incidentally, I have done repeatedly all sorts of Virus/trojan/etc
checks and I am confident that the computer is clean; unmless of
course all the different programmes are useless...

Thank you again for your help.

JB

I will wait for your response before clearing the App and System
Event Logs.
"R. McCarty" <PcEngWork-NoSpam_@xxxxxxxxxxxxxx> escreveu na mensagem
news:ui4l7Yk7IHA.4532@xxxxxxxxxxxxxxxxxxxxxxx
Has this computer ever had a Registry Cleaner used on it ? Also has
any Services had their Start Mode modified. It seems to me like
you've
got a series of dependency group failures. I would clear both the
App
and System Event Logs and do a reboot. Then check both logs for all
warnings and errors. Does your boot cycle time run ~45-60 Seconds
or is it significantly longer.

As to the hardware issue does your Device Manager have a clean
listing ? - ( No Red X's or Yellow Exclamation marks ).


"Peter" <abc@xxxxxxxx> wrote in message
news:O3TlWRk7IHA.3648@xxxxxxxxxxxxxxxxxxxxxxx
As far as Error 7023, it only happens when I Add/Delete a program
(I think only deleting). I have other Errors: 10010 DCOM which
happens EVERY TIME I start the computer and I don't know what to
do; and ID1 ACPIEC which is happening more and more frequently and
again I am at a loss.

Any help on these would be much appreciated, so that I try to
understand what is going on in my very slow computer. All the MS
updates are up to date. I have XP Home SP3.

Below the errors that I keep getting:


Product: Windows Operating System
ID: 7023
Source: Service Control Manager
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_SERVICE_EXIT_FAILED
Message: The %1 service terminated with the following error:
%2

Explanation
The specified service stopped unexpectedly with the error indicated
in the message. The service closed

safely.


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

Product: Windows Operating System
ID: 10010
Source: DCOM
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_RPCSS_SERVER_START_TIMEOUT
Message: The server %1 did not register with DCOM within the
required timeout.

Explanation
The Component Object Model (COM) infrastructure tried to start the
named server; however, the server

did not reply within the required timeout period. There might be a
deadlock, or the program might not

have responded to the server initialization code within the timeout
period of two minutes

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

Product: Windows Operating System
ID: 1
Source: ACPIEC
Version: 5.2
Symbolic Name: ACPIEC_ERR_WATCHDOG
Message: %1: The embedded controller (EC) hardware didn't respond
within the timeout period. This

may indicate an error in the EC hardware or firmware, or possibly a
poorly designed BIOS which

accesses the EC in an unsafe manner. The EC driver will retry the
failed transaction if possible.










"MowGreen [MVP]" <mowgreen@xxxxxxxxxxxxx> escreveu na mensagem
news:O2XcQDO7IHA.1952@xxxxxxxxxxxxxxxxxxxxxxx
Is the system event log showing the exact same error as in the KB
article ? Update.exe should have been updated to a much higher
version [the latest is V. 6.3.13.0] than what is showing in the
article by the installation of SP2 and SP3, along with the myriad
security updates issued since this KB was published.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


Peter wrote:

I get error 7023 repeatedly whenever I delete a programme.

I can't understand how to get the Hotfix below, and whether it is
applicable to XP SP3.

http://support.microsoft.com/kb/328213/en-us

help!

JB


















.

Relevant Pages

  • Re: Error 7023
    ... This helps a PC to map devices using IRQ ... HAL (Hardware Abstraction Layer) driver appropriate for the type ... So some of your issues are most definitely related to McAfee. ... The kind of errors you report can be the result of Registry ...
    (microsoft.public.windowsxp.general)
  • Re: Error 7023
    ... This helps a PC to map devices using IRQ ... So some of your issues are most definitely related to McAfee. ... The kind of errors you report can be the result of Registry Cleaning. ... Product: Windows Operating System ...
    (microsoft.public.windowsxp.general)
  • Re: Error 7023
    ... This helps a PC to map devices using IRQ ... So some of your issues are most definitely related to McAfee. ... The kind of errors you report can be the result of Registry Cleaning. ... Component: System Event Log ...
    (microsoft.public.windowsxp.general)
  • Re: Error 7023
    ... HAL (Hardware Abstraction Layer) driver appropriate for the type ... So some of your issues are most definitely related to McAfee. ... The kind of errors you report can be the result of Registry Cleaning. ... Component: System Event Log ...
    (microsoft.public.windowsxp.general)
  • Re: Error 7023
    ... IRQ 15 is the highest number. ... So some of your issues are most definitely related to McAfee. ... The kind of errors you report can be the result of Registry Cleaning. ... Component: System Event Log ...
    (microsoft.public.windowsxp.general)