1. Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

0.3.9 feedback on ati hd4290 (gpu integrated in amd ati 890gx) not working

Discussion in 'GPU-Z' started by guestuser, Mar 26, 2010.

  1. guestuser New Member

    Joined:
    May 5, 2008
    Messages:
    10 (0.00/day)
    Thanks Received:
    0
    hi there,

    same problem as in my old thread from gpuz 0.3.4 with hd4200 back then at:
    http://forums.techpowerup.com/showthread.php?t=101867


    this time its with gpuz 0.3.9 latest, with an asus m4a89gtd pro/usb3 board.

    win7 32bit/x86, ati catalyst 10.3 (march 2010) vanilla drivers.
    running with builtin 128megabyte sideport-only ddr3-1333mhz graphics ram bios settings.
    maybe the sideport-only stuff causing gpuz problems? will check back later to see if sideport+uma, uma-only and other modes work better.

    gpuz is very sluggish, reads a lot of weird stats in various places, causes full single-core (single thread) load on multicore cpu (aka 25% on quadcore).

    bare reacts and can barely be closed again properly. no bluescreens or real crashes so far though.

    anyone care to elaborate on this?

    any newer gpuz build? debugmode? logfiles to be generated for you developers?

    example validation which i manage to send when being really patient:
    http://www.techpowerup.com/gpuz/uf8pu/

    -1$ megaherz, -1gigabyte and such odd stuff.
    cheers
     
  2. guestuser New Member

    Joined:
    May 5, 2008
    Messages:
    10 (0.00/day)
    Thanks Received:
    0
    same everything, only this time biosettings to uma only (uma memory size as automatic).

    same behaviour of gpuz 0.3.9
    sluggish, barely reacting. error values in gui fields.


    still the same even with bios settings at uma+sideport (uma size: auto, sideport hardware at 128megabytes ddr3-1333)

    greets.
     
    Last edited: Mar 26, 2010
  3. guestuser New Member

    Joined:
    May 5, 2008
    Messages:
    10 (0.00/day)
    Thanks Received:
    0
    0.4.0 shows the same behaviour. can hardly be killed at all. no progress regarding the placeholder values, bogus and faulty informations for megaherz, gfx memory

    :(
     

Currently Active Users Viewing This Thread: 1 (0 members and 1 guest)

Share This Page