View Full Version : Winfast A400 GT problem

06-29-2005, 07:53 PM

I have got a Leadtek WinFast A400gt TDH today. I have installed it and installed the driver but it is giving me grief. When I ran 3dMark's and Battlefield 2 (not tried anything else yet) I get graphical problems. I have huge lines all over the screen, where the game should normally be. I took a screenshot of Battlefield 2:


This happens with the driver the card came with, the latest Nvidia driver and the latest one from the Leadtek website.

Any Ideas? :uhh:

06-29-2005, 08:14 PM
Double check to make sure the video board isn't overclocked. When you find out it isn't, RMA the board or return it to where you bought it to have it replaced.

06-29-2005, 08:21 PM
Thanks for the reply,

how do I find out if it is overclocked? What does RMA it mean? So many questions!!

I bought it from www.overclockers.co.uk so it is knackered I can replace it.


06-30-2005, 12:19 AM
There are any number of overclocking utilities that will tell you the speeds of the core and memory. Just make sure it is running at the speed it is supposed to be running at and not faster by a good deal. This will likely be the case since you say it is new. High overclocking can cause artifacts when the board can't keep up with the speeds it is trying to run at.

RMA is an acronym for Return Material Authorization. If you can't get an exchange from the place you bought it, this is what you'll need to ask the manufacturer for. It is the company's permission to return the product, usually for a replacement of a defective component.

07-01-2005, 02:31 PM
I had this problem, with my BFG 6800GT, when I used windows overclocking utilities to adjust voltages to my CPU and RAM, if you have any overclocking in windows shut that program off and OC using bios if possable, also the power supply may have something to do with it...

07-01-2005, 05:14 PM
I have nothing overclocked on my system, and I have a 350w psu when Nvidia recomends only a 300w psu. I have sent it back and hopefully they will say it is the card's fault, not my system's.


07-02-2005, 06:34 AM
I can safely say that it is probably be the PSU, I had a 420W PSU And I couldent get it stable with the 6800GT it all depends on the quality of the Power Supply. I now have a 520W wich may not seem like a big upgrade but it is because the quality is a lot better and more efficient, which means more power and less heat.

07-02-2005, 06:07 PM
Another things would be that while you were installing the card you may have dislodged the card's cooling or that your case doesn't have enough airflow to provide enough cool air for it.

07-02-2005, 06:42 PM
I dont think its a cooling problem, because when I installed it a second time I didnt put the case back on because I couldn't be bothered, so the whole side of the tower was open, and it happened instantly, before it got a chance to get warm.

I've asked around and some people say the PSU is fine, some say its the problem, some say its busted memory on the card casuing the problem. Too much scare mongering!!!

I'll just wait and see what the shop says when they test it..... :uhh:

07-02-2005, 06:50 PM
Personally I'd have gone with a 420+W PSU but not knowing the rest of your system I can't really say.

07-02-2005, 08:19 PM
I have a Athlon 3000+, 1 gig of PC2700 DVD drive, CD writer and 60GB hard drive. I have a Jetway V500DAP motherboard and thats about it.

I went to this website (http://www.jscustompcs.com/power_supply/Power_Supply_Calculator.php?cmd=AMD) to calcute what power my system should need and it came to only 269watts, well within my 350w PSU.

This is the PSU I have:


I dont really think that is my problem though.....

07-05-2005, 03:38 PM
Thats most likely your problem, power ratings mean nothing really, its the quality of the PSU, and that one is not great for your system setup, maybe a good Athlon XP system, but not yours. Try another more powerfull PSU if you or buddy has one available.

07-14-2005, 02:30 AM
Hello all, I returned the card to the retailer I got it from and they have confirmed it to be faulty. :)

Problem solved!