This patch has to go through more testing in Taiwan from several departments before it is released officially and in fact will probably end up being a silent install patch in the next version of the 4in1 drivers – that is if further rigorous testing proves that it is in fact a fix to this issue. If you choose to install this patch on your computer, you do so at your own risk and full responsibility yourself. Speaking frankly, normally new fixes, patchs, drivers and the like are never released beta to the public.
So what does it do? It closes the RX55 memory register in BIOS. The RX55 register's official name and function is Memory Write Queue (MWQ) timer. The MWQ timer is actually a timing device included in the memory host controller to prevent write data being held in the memory queue too long. After the data has been in the queue too long it times out. This timed out data is then given a higher write request priority. Now that might sound nice – a bit of extra performance BUT the procedure fails when overloaded. 3D games and Win XP put too much load on the memory queuing timer procedure. The nVidia new driver exaggerates the problem even more as the driver enables nVidia cards to use even more memory than previous driver versions.
So in a nutshell it’s a memory timing problem that only happens when the RX55 register is opened. Some motherboard manufacturers have already released new BIOS that have the register closed. In other instances, this patch is needed.
One thing I have noticed is that I think some people in are confusing one issue with the issue that I am referring to here. Symptoms I am talking about are the infinite loop error, dropping to desktop in 3D games or spontaneous reboot in 3D games. What I strongly suggest is that you try these trouble shooting suggestions before trying the patch:
- Load optimized defaults in your BIOS and do not modify memory settings
- set your memory settings in the BIOS less aggressively and test
- make sure you have an adequate power supply
- update your BIOS and test
- disable or enable AGP fast write and test (this has worked for some people)
The reason that I make these suggestions is that I think some people are confusing general instability because their systems are being pushed to the max, with this error. For example, if you have a 250watt power supply, 128mb RAM and have all your memory settings at max then you may be asking for trouble – the symptoms may be similar to this issue but it’s not the same. If you still get the issue after gong through these suggestions then try the beta patch (if you want to – remember it is BETA).