Melkor
24-12-2005, 01:56
I don't know if this has been discussed before but I couldn't find anything like this during a brief search in the forums.
My PC:
Asus A7N8X
Athlon XP 3000+ @ 2.1GHz
2x512MB Kingston PC-2700 valueRAM @ DDR333
nVidia Club 3d 6600GT AGP 128MB
Maxtor 80GB IDE HDD
Q-tec 550W PSU
The problems my PC has have been going on for a while now. I'm not sure when they started but I think it was around the time when I bought an additional stick of 512MB DDR333 PC-2700 RAM. Suddenly my PC started hanging up and all sorts of random reboots occured. I thought the problem was the mainboard I had, ePox something, so I upgraded to ASUS A7N8X. Everything was fine until I started watching movies. It appeared as if the movies I had tried to watch had had small patches of pixel corruption. I thought the problem was related to codecs and/or video drivers so I reinstalled everything I could think of. The problem, however, was not resolved. Soon I begun to notice random glitched frames in games (Halo, CSS, NFS: U2) and things really got hectic when I tried to do the 'liquify' effect in Adobe Photoshop CS 2.
My dad, a computer specialist with over 10 years of experience as a network and hardware administrator, suggested changing the PSU (as the one at the time had only 350W of maximum power capacity and some random resets still occured). After changing the PSU, I was freed of the resets but the graphical errors continued. The thing that ticked me off the most was the fact that after a reboot no problems would occur. I was staying up late today to find out what would cause the problem (and running my PC with only 1 512MB stick as my dad had suggested) when I suddenly got a match and needed to go onto TS. It was a false alarm but I stayed in TS and kept trying to find out what could cause the problem. I tried the liquify tool again and it just happened that I got corrupted pixels. Shocked, I turned TS off and alas! upon retrying there were no corrupted pixels. I tried a few more times and came to the conclusion that TS was causing the bug.
Does anyone have ideas what could solve this bug and if not, I hope that it would be fixed in the next release of TS.
Thank you very much for your kind patience and all the best wishes!
Merry Christmas!
-- Melkor
My PC:
Asus A7N8X
Athlon XP 3000+ @ 2.1GHz
2x512MB Kingston PC-2700 valueRAM @ DDR333
nVidia Club 3d 6600GT AGP 128MB
Maxtor 80GB IDE HDD
Q-tec 550W PSU
The problems my PC has have been going on for a while now. I'm not sure when they started but I think it was around the time when I bought an additional stick of 512MB DDR333 PC-2700 RAM. Suddenly my PC started hanging up and all sorts of random reboots occured. I thought the problem was the mainboard I had, ePox something, so I upgraded to ASUS A7N8X. Everything was fine until I started watching movies. It appeared as if the movies I had tried to watch had had small patches of pixel corruption. I thought the problem was related to codecs and/or video drivers so I reinstalled everything I could think of. The problem, however, was not resolved. Soon I begun to notice random glitched frames in games (Halo, CSS, NFS: U2) and things really got hectic when I tried to do the 'liquify' effect in Adobe Photoshop CS 2.
My dad, a computer specialist with over 10 years of experience as a network and hardware administrator, suggested changing the PSU (as the one at the time had only 350W of maximum power capacity and some random resets still occured). After changing the PSU, I was freed of the resets but the graphical errors continued. The thing that ticked me off the most was the fact that after a reboot no problems would occur. I was staying up late today to find out what would cause the problem (and running my PC with only 1 512MB stick as my dad had suggested) when I suddenly got a match and needed to go onto TS. It was a false alarm but I stayed in TS and kept trying to find out what could cause the problem. I tried the liquify tool again and it just happened that I got corrupted pixels. Shocked, I turned TS off and alas! upon retrying there were no corrupted pixels. I tried a few more times and came to the conclusion that TS was causing the bug.
Does anyone have ideas what could solve this bug and if not, I hope that it would be fixed in the next release of TS.
Thank you very much for your kind patience and all the best wishes!
Merry Christmas!
-- Melkor