M
MadBirdCZ
Before I go out and try to search answer somewhere else I will try it here.
I just installed an older dual CPU system. After installation, everything
was OK. Both CPUs were visible and identified in device manager and also in
task manager separate graphs were shown for each CPU. However, after some
time one of the CPUs vanished from the task manager but both are still shown
in device management console. I did some checking and it looks like that
windows replaced the ntoskrnl.exe with a single-cpu version of it, or one
that acording to its internal filename should be a MP one but does not
really work like that. When I log in from the recovery console and replace
the "new" ntoskrnl.exe with the ntkrnlmp.exe that comes on the XP Pro SP1 CD
and reboot, both CPUs are shown in task manager again and are also used. But
after few days the situation reverts to this state with no remarks in event
logs etc.
Could really use some info about this one (also the same thing happened on a
different system so it has to be something more than just a random anomaly
related to an old P2 MP system because the other system is a P4 HT machine
which had exactly the same symptoms)
Thanks in advance for any information,
Zdenek Cizek
I just installed an older dual CPU system. After installation, everything
was OK. Both CPUs were visible and identified in device manager and also in
task manager separate graphs were shown for each CPU. However, after some
time one of the CPUs vanished from the task manager but both are still shown
in device management console. I did some checking and it looks like that
windows replaced the ntoskrnl.exe with a single-cpu version of it, or one
that acording to its internal filename should be a MP one but does not
really work like that. When I log in from the recovery console and replace
the "new" ntoskrnl.exe with the ntkrnlmp.exe that comes on the XP Pro SP1 CD
and reboot, both CPUs are shown in task manager again and are also used. But
after few days the situation reverts to this state with no remarks in event
logs etc.
Could really use some info about this one (also the same thing happened on a
different system so it has to be something more than just a random anomaly
related to an old P2 MP system because the other system is a P4 HT machine
which had exactly the same symptoms)
Thanks in advance for any information,
Zdenek Cizek