[Thread Ufficiale] ATi Radeon HD 5850

[bati1971]

gentilmente mi postate le vostre temp e velocita di rotazione% ventola

in game


vorrei fare un confronto con qll della gtx 470

grazie mille

[Drakogian]

Al tuo posto lo sarei.
Visto l'impossibilità di aumentare la tensione al core GPU è un bel risultato.

[maranga1979]

1020-1300

http://img408.imageshack.us/img408/1...00tuttohig.jpg

di piu si blocca

[maranga1979]

Originariamente inviato da Drakogian

Al tuo posto lo sarei.
Visto l'impossibilità di aumentare la tensione al core GPU è un bel risultato.

bene! allora il liquido ha reso!

per aumentare la tensione infatti so che non montando i volterra sei fregato. ma allora perche di default è a 0,95 di vcore e adesso che l'ho portata a 1020 è a 1,165??

[maranga1979]

Originariamente inviato da bati1971

gentilmente mi postate le vostre temp e velocita di rotazione% ventola

in game


vorrei fare un confronto con qll della gtx 470

grazie mille

per la rotazione non ti posso aiutare,non ce l'ho piu!

per le temp con pro evo soccer 2010 arriva max a 38 gradi
con gli altri non so dirti per ora perche sto giocando solo a questo per ora...

[Pelvix]

E' uscito MSI AB 1.60: qualcuno lo ha già provato?
Conviene aggiornare?
Cosa migliora?

[jaja36]

Originariamente inviato da Guerrilla86

Scheda montata da un giorno e già ho un problema

Quando accendo il pc lo schermo resta nero ma il pc va, solo se schiaccio il tasto per il reset il pc si resetta e lo schermo va.

Ho già provato hdmi e dvi ma stesso risultato, lo schermo va bene ho provato con un'altra scheda, come mobo ho una p5n-e sli alimentatore cooler master 600w silent pro, potrebbe essere la ram? Ma non credo visto che con una gt220 il pc va perfettamente

Che test potrei fare per capire cosa non funziona?

Devi semplicemente aggiornare all'ultimo bios per la tua scheda madre.Vedrai che torna tutto a posto.

[Drakogian]

Afterburner 1.6.0 Final + Kombustor 1.0.10

Link: http://event.msi.com/vga/afterburner/

Nessuna grande novità per la serie ATI 5000...

[Afterburner v1.6.0 Changelog]

* Added NVIDIA GeForce GTX 400 series graphics cards support (including voltage control!)
* Added voltage control for MSI N240GT Low Profile series graphics cards
* Changed marketing name for MSI R5670-PD512 in hardware database
* Added basic screen capture support by means of built-in screen capture engine of MSI On-Screen Display server. Now it is possible to assign the hotkey for capturing screenshots in BMP,PNG or JPG formats on desktop, in DirectX or in OpenGL applications
* Added hardware monitoring history logging support. Now MSI Afterburner is able to save history in native RivaTuner Hardware Monitoring Log file format. The log files captured with MSI Afterburner can be viewed in any text editor like Notepad or in graphics form in RivaTuner's HML file viewer (RivaTuner must be installed for viewing log files in graphics form)
* Added new safety option allowing forcring constant voltage on some cards with voltage regulators supporting programmable dynamic voltage management (e.g. VT1165 or uP6266). New safety option may improve stability on some systems a well as provide power state independent voltage control on the systems with non-standard voltage control implementation
* Screen capture and On-Screen Display hotkey events are now being processed via direct connection to the On-Screen Display server instead of command line. Due to this change Screen capture and On-Screen Display visibility control hotkeys are being processed faster now
* MSI On-Screen Display server has been upgraded to version 3.7.1. New server gives you a lot of improvements including:
* DirectX11 On-Screen Display and screen capture support
* DirectX screen capture engine is no longer using DirectX runtimes to capture and compress screenshots. Screen capture and compression to PNG/JPG formats in DirectX applications is now handled by own more effective LIBPNG/JPEGLIB based library
* PNG and JPG screen capture support for desktop and OpenGL applications
* Adjustable JPG screen capture quality for experienced users
* Screen capture support for DirectX10 and DirectX11 applications using multisampled antialiasing or non-standard frame buffer formats (e.g. sRGB)
* Optional On-Screen Display 3D rendering mode. New mode uses 3D accelerated DirectX functions to emulate previously used 2D framebuffer access functions and render 2D text. New rendering mode provides On-Screen Display support in DirectX10 and DirectX11 applications using multisampled antialiasing and can also drastically reduce OSD related performance hit on the systems with badly optimized 2D acceleration in display drivers
* Simplified On-Screen Display coordinate space settings. Rarely used desktop and window coordinate space modes have been merged into single framebuffer coordinate space mode
* Now the server automatically selects framebuffer coordinate space instead of viewport coordinate space when viewport is not accessible (e.g. if pure Direct3D8 device is in use)
* Improved application notification scheme during runtime profiles adjustment. Now runtime changes in OSD application profiles (e.g. OSD zoom ratio change on the fly) are reflected in affected application almost immedaitely instead of approximately 1 second delay in the previos versions
* Reduced runtime skin engine memory footprint due to dynamic skin storage unloading
* Improved race condition protection system for multithreaded 3D engines (e.g. Age of dragons : Origins and ArmA II)
* Improved race condition protection system for the systems running multiple OSD applications simultaneously (e.g. OSD server, FRAPS and STEAM In-Game Chat)
* Improved floating injection address hooking technology. Due to more advanced built-in code analyzer hooks can be injected deeper into 3D application code if stealth mode is enabled. These changes improve stealth mode compatibility with third party tools using similar stealth injection technologies (e.g. FRAPS v2.9.8 and newer)
* Now stealth mode cannot be toggled during 3D application runtime to reduce the risk of crashing 3D application
* Removed single screen capture per second limitation
* Updated profiles list
* Now MSI Afterburner distributive includes original 128x128 PNG application logo (stored in .\Graphics folder) for dockbar applications like RocketDock or ObjectDock
* It is no longer necessary to close the application to save monitoring window attachment state
* [Stop the task if it runs longer than 3 days] option is no longer set in the task settings when using alternate startup mode via the task scheduler under Windows Vista / Windows 7
* Full list active of On-Screen Display server clients is now displayed in window instead of the most recent client
* Floating tooltips help system is now reinitialized properly after runtime skin switching
* Added Ukrainian localization


[Kombustor v1.0.10 Changelog]

* Bugfix: when PCB1 temperature was enabled in Afterburner OSD, the PCB temperature was copied in GPU temperture.
* Bugfix: in ATI cards indexing. The sorting is now the same than Afterburner.
* Bugfix: config file was not properly loaded when Kombustor is launched from Afterburner.

[Pelvix]

Originariamente inviato da Drakogian

Afterburner 1.6.0 Final + Kombustor 1.0.10

Link: http://event.msi.com/vga/afterburner/

Nessuna grande novità per la serie ATI 5000...

[Afterburner v1.6.0 Changelog]

* Added NVIDIA GeForce GTX 400 series graphics cards support (including voltage control!)
* Added voltage control for MSI N240GT Low Profile series graphics cards
* Changed marketing name for MSI R5670-PD512 in hardware database
* Added basic screen capture support by means of built-in screen capture engine of MSI On-Screen Display server. Now it is possible to assign the hotkey for capturing screenshots in BMP,PNG or JPG formats on desktop, in DirectX or in OpenGL applications
* Added hardware monitoring history logging support. Now MSI Afterburner is able to save history in native RivaTuner Hardware Monitoring Log file format. The log files captured with MSI Afterburner can be viewed in any text editor like Notepad or in graphics form in RivaTuner's HML file viewer (RivaTuner must be installed for viewing log files in graphics form)
* Added new safety option allowing forcring constant voltage on some cards with voltage regulators supporting programmable dynamic voltage management (e.g. VT1165 or uP6266). New safety option may improve stability on some systems a well as provide power state independent voltage control on the systems with non-standard voltage control implementation
* Screen capture and On-Screen Display hotkey events are now being processed via direct connection to the On-Screen Display server instead of command line. Due to this change Screen capture and On-Screen Display visibility control hotkeys are being processed faster now
* MSI On-Screen Display server has been upgraded to version 3.7.1. New server gives you a lot of improvements including:
* DirectX11 On-Screen Display and screen capture support
* DirectX screen capture engine is no longer using DirectX runtimes to capture and compress screenshots. Screen capture and compression to PNG/JPG formats in DirectX applications is now handled by own more effective LIBPNG/JPEGLIB based library
* PNG and JPG screen capture support for desktop and OpenGL applications
* Adjustable JPG screen capture quality for experienced users
* Screen capture support for DirectX10 and DirectX11 applications using multisampled antialiasing or non-standard frame buffer formats (e.g. sRGB)
* Optional On-Screen Display 3D rendering mode. New mode uses 3D accelerated DirectX functions to emulate previously used 2D framebuffer access functions and render 2D text. New rendering mode provides On-Screen Display support in DirectX10 and DirectX11 applications using multisampled antialiasing and can also drastically reduce OSD related performance hit on the systems with badly optimized 2D acceleration in display drivers
* Simplified On-Screen Display coordinate space settings. Rarely used desktop and window coordinate space modes have been merged into single framebuffer coordinate space mode
* Now the server automatically selects framebuffer coordinate space instead of viewport coordinate space when viewport is not accessible (e.g. if pure Direct3D8 device is in use)
* Improved application notification scheme during runtime profiles adjustment. Now runtime changes in OSD application profiles (e.g. OSD zoom ratio change on the fly) are reflected in affected application almost immedaitely instead of approximately 1 second delay in the previos versions
* Reduced runtime skin engine memory footprint due to dynamic skin storage unloading
* Improved race condition protection system for multithreaded 3D engines (e.g. Age of dragons : Origins and ArmA II)
* Improved race condition protection system for the systems running multiple OSD applications simultaneously (e.g. OSD server, FRAPS and STEAM In-Game Chat)
* Improved floating injection address hooking technology. Due to more advanced built-in code analyzer hooks can be injected deeper into 3D application code if stealth mode is enabled. These changes improve stealth mode compatibility with third party tools using similar stealth injection technologies (e.g. FRAPS v2.9.8 and newer)
* Now stealth mode cannot be toggled during 3D application runtime to reduce the risk of crashing 3D application
* Removed single screen capture per second limitation
* Updated profiles list
* Now MSI Afterburner distributive includes original 128x128 PNG application logo (stored in .\Graphics folder) for dockbar applications like RocketDock or ObjectDock
* It is no longer necessary to close the application to save monitoring window attachment state
* [Stop the task if it runs longer than 3 days] option is no longer set in the task settings when using alternate startup mode via the task scheduler under Windows Vista / Windows 7
* Full list active of On-Screen Display server clients is now displayed in window instead of the most recent client
* Floating tooltips help system is now reinitialized properly after runtime skin switching
* Added Ukrainian localization


[Kombustor v1.0.10 Changelog]

* Bugfix: when PCB1 temperature was enabled in Afterburner OSD, the PCB temperature was copied in GPU temperture.
* Bugfix: in ATI cards indexing. The sorting is now the same than Afterburner.
* Bugfix: config file was not properly loaded when Kombustor is launched from Afterburner.

Ma che è sto "Kombustor"?

[Drakogian]

Originariamente inviato da Pelvix

Ma che è sto "Kombustor"?

E' un test per l'overclocking simile a Furmark.

[Athlon 64 3000+]

Ho deciso per vari motivi di mettere il bios della HD 5870 e devo decidere se mettere quello MSI o Asus,secondo voi qual è il miglore?
Per il resto ho gia la guida e tutto l'occorrente necessario per fare il flash del bios.

[Pelvix]

Originariamente inviato da Drakogian

E' un test per l'overclocking simile a Furmark.

Capito, grazie 1000....

Ne approfitto per chiedere lumi su un dubbio che ho...

La mia vga in OC 900/1200 @ 1,10 v, mentre gioco ha temp un po' troppo basse, tipo giocando a Stars Wars Jedi..., non ho passato mai i 50 gradi.
Ora, vabbè che la serie 5000 è nota per scaldare poco, ma così mi pare un po' troppo poco, o no?
Non è che ho il sensore della temp che conta i paracarri?
Come posso vedere se funziona?

[Drakogian]

Originariamente inviato da maranga1979

... cut...
per aumentare la tensione infatti so che non montando i volterra sei fregato. ma allora perche di default è a 0,95 di vcore e adesso che l'ho portata a 1020 è a 1,165??

Perchè il Powerplay gestisce dei profili per bilanciare i consumi in base ai diversi usi della GPU.

Ad esempio:

[Drakogian]

Originariamente inviato da Pelvix

Capito, grazie 1000....

Ne approfitto per chiedere lumi su un dubbio che ho...

La mia vga in OC 900/1200 @ 1,10 v, mentre gioco ha temp un po' troppo basse, tipo giocando a Stars Wars Jedi..., non ho passato mai i 50 gradi.
Ora, vabbè che la serie 5000 è nota per scaldare poco, ma così mi pare un po' troppo poco, o no?
Non è che ho il sensore della temp che conta i paracarri?
Come posso vedere se funziona?

Ma lo fa anche con giochi più pesanti tipo Crysis ?

Prova a lanciare qualcosa di più pesante tipo Furmark in modalità 1.7.0 (per pochi minuti... ) o lo stesso Kombustor e vedi se le temperature salgono.

[Pelvix]

Originariamente inviato da Drakogian

Perchè il Powerplay gestisce dei profili per bilanciare i consumi in base ai diversi usi della GPU.

Ad esempio:

Ma il max voltaggio del 3d di default non è 1,85 v?
Perchè il Powerplay dovrebbe settare 1,11 v?

[Drakogian]

Originariamente inviato da Pelvix

Ma il max voltaggio del 3d di default non è 1,85 v?
Perchè il Powerplay dovrebbe settare 1,11 v?

Quelle sono le tensioni rilevate direttamente sul PCB di una HIS HD 5850 iCooler V Turbo...

Era solo un esempio per far capire il diversi stati del Powerplay...

[f0rest]

Originariamente inviato da Pelvix

Ma il max voltaggio del 3d di default non è 1,85 v?
Perchè il Powerplay dovrebbe settare 1,11 v?

A 1,85 penso che devi iniziare a procurarti un estintore

Il voltaggio di default per la 5850 reference è 1,088V, e se guardi in prima pagina il massimo overvolt è stato fino a 1,462V

[Pelvix]

Originariamente inviato da f0rest

A 1,85 penso che devi iniziare a procurarti un estintore

Il voltaggio di default per la 5850 reference è 1,088V, e se guardi in prima pagina il massimo overvolt è stato fino a 1,462V

No certo, intendevo scrivere 1,085 v..

[Athlon 64 3000+]

Ho trovato come bios uno asus per la HD 5870 datato 11/3/2010 e MSI 22/1/2010,secondo quale dei 2 è il migliore?

[beuna]

Originariamente inviato da Athlon 64 3000+

Ho trovato come bios uno asus per la HD 5870 datato 11/3/2010 e MSI 22/1/2010,secondo quale dei 2 è il migliore?

Dovrebbe essere indifferente.
Io ho quello asus.