high "system" process cpu after mobo laptop swap.

[TheOriginalDogbyte]

had the mobo swapped out on a latitude d510 (running xp pro sp2)yesterday, then when the dell tech left the laptop was runnin fine, but the "system" process was running near 100%, and it wont shutdown all the way, it hangs near the end. ive checked the event log, but im sure its hanging after the service is stopped. i have a feeling that this high percentage is caused by maybe a driver issue from the new mobo, but its supposed to be an identical swap. ive never had to diagnose a high process running like this that could be hardware related, so i really dont know where to begin, i just keep goin in circles, ive tried viewing which thread is pulling the high cpu but i get lost. since its a laptop, i cant really go about unplugging all the peripherals until i find the bad one. but not for sure that is even the problem, really kinda lost. what surprised me was to find that it was running this high cpu %, cause it doesnt really act like its slow, or as slow as it should be with the cpu clocked at 100. thats why i figured the swap went well, just didnt find the problem until i tried to shut it down. i just need steered in the right direction.

thanks

 

[TheOriginalDogbyte]

i would also like to mention that the windows update shield is down in the taskbar showing 0% downloaded, its done that since the swap.

 

[kmcferrin]

It should be an indentical swap, but it's possible that you have a later revision of the motherboard (some chips but with some fixes). It's also likely that the new board has a different BIOS revision from the old board, which could cause some issues.

Are you seeing any error messages in the event log? I would suspect that a driver update or repair install would fix it, but I wouldn't do the repair until you've done a little more troubleshooting first.

 

[TheOriginalDogbyte]

nope im not seeing any errors in the log, other than a few saying that it couldnt connect to the internet to sync the time. but i squared that away already. i was also wondering about the bios version, it would most likely be newer, but i didnt know that might butt heads with the OS. im in the middle of uninstalling some updates it did on the first attempted shutdown, i went to lunch when i shut it down, then came back and seen that it had hung, but apparently it finished with the updates, so im getting rid of those to make sure it wasnt a botched update.

 

[kmcferrin]

BIOS is Basic Input Output System. The OS interfaces with the BIOS to access hardware, so changes to the way it works can mess with your OS, especially if the newer version has a different set of default settings than your old version.

 

[TheOriginalDogbyte]

but where would the OS need to be changed, to where it sees a change in the bios? ive never had to think about this before.

 

[kmcferrin]

It depends on what has changed. It could be as simple as a driver re-install/update, but it really depends. For example, if you go from a BIOS that has ACPI disabled by default to one that has ACPI enabled by default, you'll get a BSOD and have to update the HAL to fix it. Or you could just disable ACPI too I guess.