CPU (P4)question

  • Thread starter Thread starter MrCPea
  • Start date Start date
M

MrCPea

Hi,
I have 2 asus mobos ( PR800-VM & P4V8X-MX)
I used a 2.4 celeron in the PR800-VM without any problrms what so
ever, & a celeron D 2.93 in the P4V8X-MX also without any problems.
When I upgraded to a P4 2.8 hyperthreading 800 FSB cpu in both boards,
they ran very well for a few hours (various amounts of time), then I
get an error message
"Application failed to initalize properly (0xc0000142)", which means a
reboot before anything works again.
Why would this be the case with the P4 CPU, & not the celeron &
celeron D. The cpu support list says that the P4 hyperthreading CPU
should work as standard without a BIOS upgrade.
If any more system info is needed, please let me know.
Any advice given would be greatly recieved.
Many thanks for your time

Rich
 
MrCPea said:
Hi,
I have 2 asus mobos ( PR800-VM & P4V8X-MX)
I used a 2.4 celeron in the PR800-VM without any problrms what so
ever, & a celeron D 2.93 in the P4V8X-MX also without any problems.
When I upgraded to a P4 2.8 hyperthreading 800 FSB cpu in both boards,
they ran very well for a few hours (various amounts of time), then I
get an error message
"Application failed to initalize properly (0xc0000142)", which means a
reboot before anything works again.
Why would this be the case with the P4 CPU, & not the celeron &
celeron D. The cpu support list says that the P4 hyperthreading CPU
should work as standard without a BIOS upgrade.
If any more system info is needed, please let me know.
Any advice given would be greatly recieved.
Many thanks for your time

Rich
Click to expand...

This page explains about a wide variety of "Stop" errors,
and the 0xC0000142: DLL Initialization Failure code is
listed here.

0xC0000142: DLL Initialization Failure

As part of installing your new processor, first go to
Device Manager, select the "Computer" entry, then do
"Properties" on it. The value listed there is the HAL or
Hardware Abstraction Layer. The P4 with Hyperthreading
would use ACPI Multiprocessor, while the Celeron would
use ACPI Uniprocessor for a HAL.

You should be able to do a "Driver Update" to that HAL
entry, and change it from Uniprocessor to Multiprocessor.
Not all HAL changes are as easy as the one needed in
this case. And you may find it is already set correctly.

After that, when you open Task Manager, you should see
two CPU traces for the performance monitoring screen.
(Assuming you've enabled "trace per CPU" viewing mode
for that display - it is possible to combine it all into
one trace, so you should check the preference being
used for the display.)

Also, on some Asus motherboards, there is a BIOS option
to disable Hyperthreading, which is another thing you
can check. (Just in case you cannot get two traces in
the Task Manager display.)

If, in fact, your HAL is set for Multiprocessing,
the other thing I found in a search, is to run the
WinXP System File Checker (SFC), as it has the
ability to repair system files and replace any
that are damaged. That may correct your problem
as well, if the problem is a corrupt file of some
sort. That only works for system files, and
actual applications files may need an uninstall/reinstall
to get the same effect.

Paul
 
MrCPea said:
Hi,
I have 2 asus mobos ( PR800-VM & P4V8X-MX)
I used a 2.4 celeron in the PR800-VM without any problrms what so
ever, & a celeron D 2.93 in the P4V8X-MX also without any problems.
When I upgraded to a P4 2.8 hyperthreading 800 FSB cpu in both boards,
they ran very well for a few hours (various amounts of time), then I
get an error message
"Application failed to initalize properly (0xc0000142)", which means a
reboot before anything works again.
Why would this be the case with the P4 CPU, & not the celeron &
celeron D. The cpu support list says that the P4 hyperthreading CPU
should work as standard without a BIOS upgrade.
If any more system info is needed, please let me know.
Any advice given would be greatly recieved.
Many thanks for your time
Click to expand...
Did you get heatsinks with the P4 chips, or did you reuse the old ones?

Bob
 
This page explains about a wide variety of "Stop" errors,
and the 0xC0000142: DLL Initialization Failure code is
listed here.

0xC0000142: DLL Initialization Failure

As part of installing your new processor, first go to
Device Manager, select the "Computer" entry, then do
"Properties" on it. The value listed there is the HAL or
Hardware Abstraction Layer. The P4 with Hyperthreading
would use ACPI Multiprocessor, while the Celeron would
use ACPI Uniprocessor for a HAL.

You should be able to do a "Driver Update" to that HAL
entry, and change it from Uniprocessor to Multiprocessor.
Not all HAL changes are as easy as the one needed in
this case. And you may find it is already set correctly.

After that, when you open Task Manager, you should see
two CPU traces for the performance monitoring screen.
(Assuming you've enabled "trace per CPU" viewing mode
for that display - it is possible to combine it all into
one trace, so you should check the preference being
used for the display.)

Also, on some Asus motherboards, there is a BIOS option
to disable Hyperthreading, which is another thing you
can check. (Just in case you cannot get two traces in
the Task Manager display.)

If, in fact, your HAL is set for Multiprocessing,
the other thing I found in a search, is to run the
WinXP System File Checker (SFC), as it has the
ability to repair system files and replace any
that are damaged. That may correct your problem
as well, if the problem is a corrupt file of some
sort. That only works for system files, and
actual applications files may need an uninstall/reinstall
to get the same effect.

Paul
Click to expand...


Paul,
Many thanks indeed for your reply.
I'm using the P4V8X-MX at the moment with the cleron d 2.93 &
it's showing up as ACPI Multiprocessor in the Device manager.
I did notice that, when I had the P4 HT CPU in the board at the
weekend, there were 2 CPU's present in the device manager & also in
the task manager, like you mentioned. I couldn't see any way of
enabling the Hyperthreading function in this mobo, but in the PR800-VM
mobo, the Hyperthreading facility was showing up as enabled, with the
P4 CPU in the board.

I tried to run the system file checker, but all I got up was DOS box
flash up on the screen then dissapear within under a second.

I have an asrock 478 board that supports hyperthreading P4 CPU, so
I'll try a new install of windows on that board, with the P4 & let you
know how that goes.

Regards

Rich
 
Did you get heatsinks with the P4 chips, or did you reuse the old ones?

Bob
Click to expand...
Hi Bob, many thanks for the reply.
I'm using a heatsink previously used with other CPU's.
It's a copper core intel one, rated for 3.0 P4 CPU's.

Regads

Rich
 
MrCPea said:
Hi Bob, many thanks for the reply.
I'm using a heatsink previously used with other CPU's.
It's a copper core intel one, rated for 3.0 P4 CPU's.
Click to expand...

OK - just a wild guess that the HS/fan was under specced, but it seems OK(it
would tie in with the "runs OK for a time" symptom). Sorry if there is a
grandmother/eggs situation, but I assume you put new HS compound on?

Bob
 
OK - just a wild guess that the HS/fan was under specced, but it seems OK(it
would tie in with the "runs OK for a time" symptom). Sorry if there is a
grandmother/eggs situation, but I assume you put new HS compound on?

Bob
Click to expand...


Hi Bob,
Thx for the reply.
Yes, compound was cleaned off, then new stuff applied to CPU.
I'm trying to check every option in the BIOS at the moment between
working. I'll have a bit more time at the weekend.

The funny thing is, that I had the PC running for a couple of days
once, with the P4 inserted. Then other times, it will last for just a
few hours. Ive never had the error message whilst using the PC, it's
always been overnight when not using, or during the day, when I've
popped out.
Thanks,
Rich.
 
Back
Top