OXC0000142 Error

  • Thread starter Thread starter Phyllis
  • Start date Start date
P

Phyllis

I am getting "OXC0000142 program failed to initialize properly" error at
shutdown. What can I do to get rid of this? Thanks
 
Phyllis said:
I am getting "OXC0000142 program failed to initialize properly" error at
shutdown. What can I do to get rid of this? Thanks

You need to determine what program or process is running in the background
and not exiting gracefully.

The program and/or process can be from malware or can be legitimate (such as
an invasive antivirus like Norton or McAfee). If you are using a Norton or
McAfee product, uninstall it and replace with a better program such as
NOD32, Kasperksy, or Avast (free). The Windows Firewall is adequate for most
people. With Vista, shutdown issues can also be caused by old/poorly written
drivers so make sure all drivers are updated. See Step B. below for general
driver directions.

A.The first step is always to make sure your computer is virus/malware free.

http://www.elephantboycomputers.com/page2.html#Removing_Malware

B. Drivers - The First Law of Driver Updates is "if it ain't broke, don't fix
it". Normally if everything is working you want to leave things as they are.
The exception is that heavy-duty gamers will usually want to update their
video and sound drivers to squeeze every last bit of performance out of the
hardware to get the fastest frame rates. If you're not one of those people,
you don't need to update your drivers if there are no problems you are
trying to solve.

Never get drivers from Windows Update. Get them from:

1. The device mftr.'s website; OR
2. The motherboard mftr.'s website if hardware is onboard; OR
3. The OEM's website for your specific machine if you have an OEM computer
(HP, Dell, Sony, etc.).

Read the installation instructions on the website where you get the drivers.

To find out what hardware is in your computer:

1. Read any documentation you got when you bought the computer.
2. If the computer is OEM, go to the OEM's website for your specific model
machine and look at the specs (you'll be there to get the drivers anyway)
3. Download, install and run a free system inventory program like Belarc
Advisor or System Information for Windows.

http://www.belarc.com/free_download.html - Belarc Advisor
http://www.gtopala.com/ - System Information for Windows

C. If the computer is virus/malware-free, drivers are current, and no Norton
or McAfee programs are installed, then do clean-boot troubleshooting to see
which program/process is the culprit:

How to perform a clean boot in Vista and XP -
http://support.microsoft.com/kb/331796

D. If you need more information, here is an excellent shutdown
troubleshooter:

http://www.aumha.org/win5/a/shtdwnxp.htm

Standard caveat: If troubleshooting the issue is too difficult - and there is
absolutely no shame in admitting this isn't your cup of tea - take the
machine to a computer repair shop. This will not be your local
BigComputerStore/GeekSquad type of place. Get recommendations from family,
friends, colleagues.

Malke
 
Malke said:
You need to determine what program or process is running in the background
and not exiting gracefully.

The program and/or process can be from malware or can be legitimate (such
as
an invasive antivirus like Norton or McAfee). If you are using a Norton or
McAfee product, uninstall it and replace with a better program such as
NOD32, Kasperksy, or Avast (free). The Windows Firewall is adequate for
most
people. With Vista, shutdown issues can also be caused by old/poorly
written
drivers so make sure all drivers are updated. See Step B. below for
general
driver directions.

A.The first step is always to make sure your computer is virus/malware
free.

http://www.elephantboycomputers.com/page2.html#Removing_Malware

B. Drivers - The First Law of Driver Updates is "if it ain't broke, don't
fix
it". Normally if everything is working you want to leave things as they
are.
The exception is that heavy-duty gamers will usually want to update their
video and sound drivers to squeeze every last bit of performance out of
the
hardware to get the fastest frame rates. If you're not one of those
people,
you don't need to update your drivers if there are no problems you are
trying to solve.

Never get drivers from Windows Update. Get them from:

1. The device mftr.'s website; OR
2. The motherboard mftr.'s website if hardware is onboard; OR
3. The OEM's website for your specific machine if you have an OEM computer
(HP, Dell, Sony, etc.).

Read the installation instructions on the website where you get the
drivers.

To find out what hardware is in your computer:

1. Read any documentation you got when you bought the computer.
2. If the computer is OEM, go to the OEM's website for your specific model
machine and look at the specs (you'll be there to get the drivers anyway)
3. Download, install and run a free system inventory program like Belarc
Advisor or System Information for Windows.

http://www.belarc.com/free_download.html - Belarc Advisor
http://www.gtopala.com/ - System Information for Windows

C. If the computer is virus/malware-free, drivers are current, and no
Norton
or McAfee programs are installed, then do clean-boot troubleshooting to
see
which program/process is the culprit:

How to perform a clean boot in Vista and XP -
http://support.microsoft.com/kb/331796

D. If you need more information, here is an excellent shutdown
troubleshooter:

http://www.aumha.org/win5/a/shtdwnxp.htm

Standard caveat: If troubleshooting the issue is too difficult - and there
is
absolutely no shame in admitting this isn't your cup of tea - take the
machine to a computer repair shop. This will not be your local
BigComputerStore/GeekSquad type of place. Get recommendations from family,
friends, colleagues.

Malke


I am running McAfee Internet Security, but I have had it for almost a year
now and the error message just started and the only time I see it is when I
click to shutdown the computer. It comes up and leaves so fast I don't have
time to read all of it.
 
Phyllis said:
I am running McAfee Internet Security, but I have had it for almost a year
now and the error message just started and the only time I see it is when
I
click to shutdown the computer. It comes up and leaves so fast I don't
have time to read all of it.

Then answer The First Question Of Troubleshooting: If the problem is new,
what changed between the time things worked and the time they didn't?

Unless you know what changed and can reverse that change, I would still
uninstall McAfee - at least temporarily - because the program gets updated
all the time.

If you can't pinpoint a change, then you have to do systematic
troubleshooting as detailed in my last post.

Malke
 
Malke said:
Then answer The First Question Of Troubleshooting: If the problem is new,
what changed between the time things worked and the time they didn't?

Unless you know what changed and can reverse that change, I would still
uninstall McAfee - at least temporarily - because the program gets updated
all the time.

If you can't pinpoint a change, then you have to do systematic
troubleshooting as detailed in my last post.

Malke

The only thing that has changed is I installed Vista SP2 from microsoft
updates and I did routine maintenance - delete temporary internet files,
etc., ran spyware scan, anti-virus scan, chkdsk, and defrag. Don't know how
to undo all that, other than uninstalling SP2 and a system restore. Have
you seen anyone else having any problems after installing SP2?
 
//
// MessageId: STATUS_DLL_INIT_FAILED
//
// MessageText:
//
// {DLL Initialization Failed}
// Initialization of the dynamic link library %hs failed. The process is
terminating abnormally.
//
#define STATUS_DLL_INIT_FAILED ((NTSTATUS)0xC0000142L)
 
Phyllis said:
The only thing that has changed is I installed Vista SP2 from microsoft
updates and I did routine maintenance - delete temporary internet files,
etc., ran spyware scan, anti-virus scan, chkdsk, and defrag. Don't know
how
to undo all that, other than uninstalling SP2 and a system restore. Have
you seen anyone else having any problems after installing SP2?

The only time I've seen issues with SP2 is on machines that already had
problems such as being infected or if SP2 was installed with an antivirus
active. For most machines installing it is non-eventful. I don't consider
running Chkdsk to be part of routine maintenance; it should be run when
troubleshooting a file system/disk problem. However, I doubt that's the
cause. What other security programs do you have that run resident? Perhaps
one of them is the culprit - but you will only find out if you do the
systematic troubleshooting.

Malke
 
Malke said:
The only time I've seen issues with SP2 is on machines that already had
problems such as being infected or if SP2 was installed with an antivirus
active. For most machines installing it is non-eventful. I don't consider
running Chkdsk to be part of routine maintenance; it should be run when
troubleshooting a file system/disk problem. However, I doubt that's the
cause. What other security programs do you have that run resident? Perhaps
one of them is the culprit - but you will only find out if you do the
systematic troubleshooting.

Malke

OK . . . thanks for your help.
 
Back
Top