Another faulty GFX card?

Landerin

New member
I recently replaced a faulty 8800gts with a nice shiny new Saphir Radeon 4850 512mb, but now i have the problem that i can't play games due to the GPU idleing at 80c and when i log into eve it shoots to 85c and shuts down my PC.

Would you say this is a faulty card, or is the stock cooler on them not enough to cool the card to be able to game on?
 
Although the 4850 is toasty, the stock cooler on the two cards I have used keeps it around a fair idle and scorching 85*C at full load. My guess is bad chip or someone forgot to put the thermal crap between the card and cooler. Which would be silly.
 
4850's run hot as hell as standard, check in the catalyst control center, the overdrive part, if the fans are on at all? Personally I think they borked up how / when the fans should start.

Anyhoo, you can enable manual fan control here, to say always have them on 50% etc etc, though the fans themselves are damn noisy. Have a play with the fan setting see if you can get the heat under control.

Other thing is to whip off the stock cooler, should just be a simple case of a few small screws on the back, and could then clean off the GPU and reapply some arctic silver, reseat the heatsink/fan and see if that helps.
 
name='fruityness' said:
Other thing is to whip off the stock cooler, should just be a simple case of a few small screws on the back, and could then clean off the GPU and reapply some arctic silver, reseat the heatsink/fan and see if that helps.
I'd be using something non-conductive myself instead of Arctic Silver - try some Arctic Ceramique or any of the number of 'new breed' thermal pastes like Noctua NT-H1/Tuniq TX.
 
well i have manualy put the fan speed to 100% through Catalyst and now the temps are at about 70c when i am running eve-online, but if i stay in eve for too long can be 5-30mins with the screen sat there the screen suddenly goes blank and comes up with either, out of range, or no signal input.

edit P.S. i will try an get some pic uploaded.
 
Sounds like your GPU is brokdededed, having a temp of 70c will NOT make your graphics card overheat, the problem could be your case and circulation, have you tried reseating your GPU and checking the fan is not dusty etc... Just the simple things make a big difference.
 
well the gfx card is only a week old and i clean the dust from my PC every so often anyways, but i will just see what happens i can easily take it back.
 
the PSU is poweful ebough, the max output is 251w and i have a 500w PSU but today while watching some american dad episodes, i got a BSOD message of Bad_Pool_Cooler come up, this is a message i can find very little on, is anyone able to enlighten?
 
Here are some photos of the inside of my case, the cable management isnt great but i dont think that any of it should be interfering with any of the cooling.
 

Attachments

  • P1010001.JPG
    P1010001.JPG
    89.9 KB · Views: 103
  • P1010002.JPG
    P1010002.JPG
    92.8 KB · Views: 38
  • P1010003.JPG
    P1010003.JPG
    90.4 KB · Views: 42
it was defo the card which was faulty, and i ended up going to get it replaced with the same one, but got a full refund instead and went and purchased an XFX Radeon 4870 1gb whcich works no problems.
 
Pool damage may be the root cause of many of the most evasive issues with Windows NT. Pool damage is caused when a kernel-mode component writes to memory outside of its allocated pool area. By writing to memory beyond the boundary of its allocated area, it is likely that another area of allocated memory, possibly owned by another component, is overwritten. This damage can cause problems such as blue screens in completely unrelated areas of code. A kernel-mode component reading beyond its allocated area can also cause problems.

Whether it is caused by Original Equipment Manufacturers (OEM) drivers or problems in Windows NT, pool damage problems are some of the most difficult to identify. Usually, all that can be seen in a crash dump analysis is the symptom of the real problem, such as a data area becoming damaged and causing problems in a completely unrelated piece of code. Up until now it has been almost impossible to identify the piece of code damaging the memory.

The source of pool damage can now be identified at the instruction causing the pool damage. A new memory management utility called Special Pool is included with Windows NT 4.0 Service Pack 4 (SP4) and Windows 2000. The Special Pool utility identifies the kernel-mode component that is damaging pool data by writing to memory outside its allocated area.
 
Back
Top