• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Does Conroe need the Windows XP Multiprocessor Patch?

I've read several notes about AMD dual core processors requiring a patch for Windows XP to perform properly.

Does anyone know if this patch is needed for Conroe?
 
patsh? um...no

I installed a x2 3800+ and windows recognised a new CPu (changed the HAL to multiprocessor) and asked me to restart and I was done. The drivers and stuff from AMD are based on games not being able to time the cycles of both cores at once and stuttering or being unplayable as a result.
 
I'm a gamer (not hardcore) and haven't had to install nothing special. As others haven't either. Its apparently because some games use the rdtsc cycle counter and thus, when Windows switches the game from core0/core1, it gets alittle screwy because of the rdtsc value of core0 being out of sync with core1's rdtsc cycle value and vice-versa.

I made my own realtime clockspeed monitor and had the same problem. It would show the proper 2600mhz and then the next loop would show 1370 or whatever, then 5500 or something, then back to 2600mhz and what-not. Once I set the affinity of the thread to either core0/core1, then the clockspeed would be perfectly stable and the calculated rdtsc values would be the accurate, true clockspeed.

I installed the so-called DualCore optimizer and I know longer have to set the affinity of the clockspeed monitor I made to either core0/core1. I can let Windows determine the affinity back and forth and the rdtsc is in perfect sync.

So, that appears to be why some games had the timing problems on the x2's. From what I can gather anyways 🙂



Jason
 
Back
Top