Looks like an I/O problem. Is this still the dual-processor system with the 24-bit Soundblaster?
This is usually a sign of a process hogging all CPU quantums and/or disk I/O. But it could also be broken PCI timing (PCI Creative cards love to hog the bus all to themselves; also, on an SMP box the affinity/IRQ will have to be set manually to ensure the Creative card is being driven by only one CPU). A "legacy" driver in slow timing mode (virtual ISA or non-busmastering PCI), such as an unidentified PCI busmastering device, might also be causing this. The general description of the problem is - a background process interfering with PCI and/or filesystem I/O or CPU scheduling (usually all at once).
- the PCI SB Live 24-bit was particularly picky and could even lock/BSOD an SMP system.
Other bits... An antivirus or file indexer (Windows' own indexing service or something like Google Desktop) could be hogging the I/O system while polling the filesystem. An antivirus intercepts filesystem calls, so if its driver/service is poorly implemented, it can cause choppiness (though less severe than what you've got).
A faulty hard drive with lots of bad blocks will also cause crawling and stutter when the damaged area is read. Game files are large, so they have more chances of falling into a damaged area. But, there would also be weird effects inside a game booted from a damaged HD area - colour noise, missing or damaged sounds, missing textures, etc.
SMP systems can be tricky, as software usually isn't written with SMP in mind. Running a game on a single CPU (with an affinity tool or affinity assigned by the task manager) might help
Are there any driverless/"broken" device links in the Device Manager? Those will usually interfere with I/O, as they're being run in "compatibility" slow clocking mode.
Adding my little chunk o' experience, multiple core systems seem to have a problem with the task switcher under XP. Switching out of a task running in user space appears to occasionally result in problems with the task when switching back. I know for a fact that you tab in and out of programs willy-nilly, so this might be a possibility. Do they *always* run choppy from the very moment you load them, or only after you've switched out of them?
I have my suspicion that, since the alt-tab function is implemented by CSRSS, which also handles threading, the problem lies in CSRSS trying to reassign threads on a core (just my guess, not in any way diagnostic). If that were actually the case I'd expect setting the affinity of the game to a single core to remedy the situation.
This is usually a sign of a process hogging all CPU quantums and/or disk I/O. But it could also be broken PCI timing (PCI Creative cards love to hog the bus all to themselves; also, on an SMP box the affinity/IRQ will have to be set manually to ensure the Creative card is being driven by only one CPU). A "legacy" driver in slow timing mode (virtual ISA or non-busmastering PCI), such as an unidentified PCI busmastering device, might also be causing this. The general description of the problem is - a background process interfering with PCI and/or filesystem I/O or CPU scheduling (usually all at once).
Reply
Reply
Reply
- the PCI SB Live 24-bit was particularly picky and could even lock/BSOD an SMP system.
Other bits... An antivirus or file indexer (Windows' own indexing service or something like Google Desktop) could be hogging the I/O system while polling the filesystem. An antivirus intercepts filesystem calls, so if its driver/service is poorly implemented, it can cause choppiness (though less severe than what you've got).
A faulty hard drive with lots of bad blocks will also cause crawling and stutter when the damaged area is read. Game files are large, so they have more chances of falling into a damaged area. But, there would also be weird effects inside a game booted from a damaged HD area - colour noise, missing or damaged sounds, missing textures, etc.
SMP systems can be tricky, as software usually isn't written with SMP in mind. Running a game on a single CPU (with an affinity tool or affinity assigned by the task manager) might help
Reply
Reply
I have my suspicion that, since the alt-tab function is implemented by CSRSS, which also handles threading, the problem lies in CSRSS trying to reassign threads on a core (just my guess, not in any way diagnostic). If that were actually the case I'd expect setting the affinity of the game to a single core to remedy the situation.
Reply
Reply
Leave a comment