Here is a summary of my solutions to the problems I was having with my newly updated computer. I am copying this in part from another forum on the Internet that focuses on ASUS motherboards.
I am beginning to believe there is a problem with Windows XP Pro and the TUSL2-C that uses a video board based on a GeForce chipset. I end up getting a pair of "machine check" messages during bootup that always was coincidental to data corruption on the drive. This message in the event log is very unusual and apparently few users get this message, as discovered from my searches on the Internet. And no one has found an answer for it.
I fist saw it on my TUSL2-C 1G Coppermine desktop setup. When the message showed up, there usually is other behavior from the OS that indicates some data corruption problem. I have been using a rented portable until I can fix my desktop machine. Funny thing I ended up with a data corruption problem on the portable too. I was just running reports on a database, which does not add or change or delete information on the application level. So I look, and what a surprise the same pair of error messages shows up. The portable uses the mobile version of the same chip set of the TUSL2-C. I also find both the portable and the desktop uses a GeForce video chip set. The portable uses the Home edition of Windows XP while the desktop uses the Professional version of Windows XP. Now I understand this is not anywhere close to being conclusive, but I would say it is suspicious, given how I have already thoroughly tested the desk top machine up to this point.
Once I changed the OS to Windows 2000 Professional, apparently the problem now has gone away. I have been running without any problems for a period of time now except for one time when the machine did not appear to boot successfully from a software install, leaving me with a blank screen. A reboot solve the problem. Both the data corruption, the odd "machine check" error messages, and my original video problem has gone away. The original video problem was a consistently late video signal to the monitor after Windows XP was already up and running.
The solution took a swap of both generic memory, and a swap of the motherboard to another TUSL2-C which solved the video problem, and a change From WIndows XP Pro to the Windows 2000 Pro OS, which apparently has solved the "machine check" message and associated data corruption problem. The generic memory was not able to operate at its stated specifications. As Doug mentioned before, it appears that NVidia is selling their chips to every Tom, Dick, and Harry which can cause quality control problems that will muddy up the name of NVidia. Some people had *several* bad boards before getting one that worked. My first copy of the 440 MX when bad inside of 15 minutes of operation. There is a definite problem here. Also I suspect the rectifier on the TUSL2-C have have been the remaining problem that caused the late video signal.
The 1G Coppermine started out as an overclocked chip. Batches are tested on the assembly line to see what speed the chip can be successfully clocked at. Those that cannot run at the 1G will then be checked at lower speeds and relabeled. This is not a completely reliable quality control process. So IMO there will be a higher incidence of bad chips entering the market. Intel changed their manufacturing process when the first batch released to the public had problems. This may have solve the problem to their satisfaction, but I have doubts that this has eliminated all the chips not capable of 1G operation from entering the market. Depending on what batch the CPU comes from, this will determine how much the chip needs to be overclocked for 1G Mhz operation. This is why some chips will operate cooler than other chips.
Also I see many drivers, including the Win2000 drivers from NVidia, altered to work on both XP and 2000 operating systems. At least in some cases I think this was a quick fix to get something out that works for XP by making a few quick changes to the Win2000 drivers. This can lead to problems for some user, for the hacked Win2000 drivers may still not be completely compatible with WinXP and the underlying hardware.
One conclusion is that Windows XP is not ready for prime time, but can work for many who are willing to take a risk and work with their machine until it is operable. The upcoming maintenance release may take care of this problem. Also there are allot of problem NVidia boards getting out in the market, some of the problem that may relate to the driver. This driver issue may also relate to other hardware plugged into the motherboard.
I an finding Windows 2000 similar to Windows XP minus some nice features like the rollback of drivers, checkpoints of the operating system, a more intelligent memory management routine, a more intelligent IRQ mapping scheme, and so forth. But Win2000 works, and the OS with its drivers have been out for some time now having been "beta" tested by the public at large. And one additional problem has disappeared. My USB powered ZIP 250 drive would disable the cache to my drive. This does not happen any longer with Windows 2000.
I also see the overall quality of hardware has gone down, perhaps due to price competition. Just look at the NVidia video cards, the Intel 1G processor, and the generic memory chips as examples that I gave above. I will stick with a well-recognized and supported Intel based motherboard that has been out for at least 6 months, good non-generic memory like Crucial, Matrox video cards, and a specific setup configuration that I find already working well for others. And I will never install an OS previous to its first maintenance release. I will stay away from NVidia and ATI graphics cards, and particularly VIA chipset based MBs. No Windows XP for me until their new version coming up next year.
Any thoughts?
Bob Graham |
