I`m currently running a Asus A7v266-E, Athlon xp1800+, 512mb pc2100, geforce2 pro 64mb system with Windows XP Pro. My system, which I built 2 weeks ago is perfectly stable, and hasn`t crashed once. I`m well chuffed with it in general.
However tonight I discovered that Nvidia`s Opengl implementation is completely and utterly problematic when running in Windows XP. Problem game was Counterstrike. It worked perfectly well in direct3d and plays even better in OpenGL mode. Its truely awesome to see 100fps in 1024x768x32 in Opengl. The BIG problem came when I actually exited the game.
My entire computer froze up. I hit the reset button and then was given a lovely "serious problem" screen by microsoft. My motherboard then decided to start beeping incessently as if it was trying to send out a priority morse code to Afghanistan. The only thing i could do was hit the psu button on the back of the power supply. When I restarted my bios screen was up telling me that my cpu had overheated and it had set my fsb to 100. I corrected my settings and windows xp booted up fine.
It don`t look like any harm has been done. Now the strange thing is, I told my good friend W4zy who also has XP PRO and a geforce2 pro in his machine about the improvements graphically in Opengl over direct3d. We decided to have a game on counterstrike and we had a lovely 1 hour session with no problems or crashes at all. Mine didn`t crash on exit this time, but his did! And he had to hard reset too, just like I did the first time.
This is worrying because I know for a fact my pc is stable and isn`t overheating, but this error due to OpenGL appears to me to be a VERY serious issue that Nvidia needs to look at soon! If on exit of counterstrike (and quake3 i also hear) it causes the cpu to lock at 100% full cpu cycles and locks the OS, nvidia could be looking at damaging peoples hardware!
It certainly looks like until it does we are stuck with directx8 for our games.
However tonight I discovered that Nvidia`s Opengl implementation is completely and utterly problematic when running in Windows XP. Problem game was Counterstrike. It worked perfectly well in direct3d and plays even better in OpenGL mode. Its truely awesome to see 100fps in 1024x768x32 in Opengl. The BIG problem came when I actually exited the game.
My entire computer froze up. I hit the reset button and then was given a lovely "serious problem" screen by microsoft. My motherboard then decided to start beeping incessently as if it was trying to send out a priority morse code to Afghanistan. The only thing i could do was hit the psu button on the back of the power supply. When I restarted my bios screen was up telling me that my cpu had overheated and it had set my fsb to 100. I corrected my settings and windows xp booted up fine.
It don`t look like any harm has been done. Now the strange thing is, I told my good friend W4zy who also has XP PRO and a geforce2 pro in his machine about the improvements graphically in Opengl over direct3d. We decided to have a game on counterstrike and we had a lovely 1 hour session with no problems or crashes at all. Mine didn`t crash on exit this time, but his did! And he had to hard reset too, just like I did the first time.
This is worrying because I know for a fact my pc is stable and isn`t overheating, but this error due to OpenGL appears to me to be a VERY serious issue that Nvidia needs to look at soon! If on exit of counterstrike (and quake3 i also hear) it causes the cpu to lock at 100% full cpu cycles and locks the OS, nvidia could be looking at damaging peoples hardware!
It certainly looks like until it does we are stuck with directx8 for our games.
Facebook
Twitter