Just got my 560 Ti back from RMA and it has been replaced from Gigabyte as far as i know. Had the card running several hours playing nothing to really push it then decided to hit up the latest Deus Ex.
After 20 minutes the system just turned its self off. I personally thought it's just kicked the bucket like the previous one.
Pushed the power button to see if it was just a system crash, the power came on for a split second, heard a crackle then a plume of smoke came out of the top of the case.
Opened the side up, looked at everything. Seemed fine. Trying the system again and it boots up all hunky dory, but the obvious thing is, something must have popped as i can smell the nasty burnt plastic oder.
Looking at my system spec the only change i can honestly see is that my installed ram on win764bit is now showing as 4.00gb (3.25gb usable). This is not what bios claims though as both the full 4gb is usable, theirs no onboard graphics card and i am using 64bit.
So after all this wall of text does anything have a clue at all what's happened? I'm gonna use a stress testing program after writing this to see what happens. Could it be some blocks of ram has just kicked it? I'm clueless as to what just happened.
After 20 minutes the system just turned its self off. I personally thought it's just kicked the bucket like the previous one.
Pushed the power button to see if it was just a system crash, the power came on for a split second, heard a crackle then a plume of smoke came out of the top of the case.
Opened the side up, looked at everything. Seemed fine. Trying the system again and it boots up all hunky dory, but the obvious thing is, something must have popped as i can smell the nasty burnt plastic oder.
Looking at my system spec the only change i can honestly see is that my installed ram on win764bit is now showing as 4.00gb (3.25gb usable). This is not what bios claims though as both the full 4gb is usable, theirs no onboard graphics card and i am using 64bit.
So after all this wall of text does anything have a clue at all what's happened? I'm gonna use a stress testing program after writing this to see what happens. Could it be some blocks of ram has just kicked it? I'm clueless as to what just happened.
