Benchmarking ... Let's see how good we are ... ;)

[BabisTs]

B-die rules.......Πρέσσα για μεγάλα νούμερα σε mhz και σφιχτά primary και δυνατά secondary timmings.......ότι θες εδώ είμαστε αν χρειαστείς οτιδήποτε.....

Επεξ/σία 19 Φεβρουαρίου 2019 από BabisTs

[d4ydr33m3r]

24 λεπτά πριν, BabisTs είπε

Δυνατό κομμάτι ......Ψάξου για 5,1ghz και κάτω του 1,3v για daily stability........Τι ψύξη έχεις?

Κάπου εκεί το υπολογίζω Μπάμπη για να μην ανεβάσω καθόλου vcore.. Τώρα έβαλα x72 με noctua d14 ήμουν. Μεγάλη διαφορα και ας διαβάζω διάφορα.. 

21 λεπτά πριν, akoinonitos είπε

Πρέπει να ρίξεις μια επένδυση σε ένα καλό κιτακι, ρωτά το  @BabisTs πόσο παίρνει από τις μνήμες

Πως καταφέρνω και τις αφήνω πάντα για άλλες επενδύσεις δεν ξέρω  😬😂

1 λεπτό πριν, BabisTs είπε

B-die rules.......Πρέσσα για μεγάλα νούμερα σε mhz και σφιχτά primary και δυνατά secondary timmings.......ότι θες εδώ είμαστε αν χρειαστείς οτιδήποτε.....

Εντάξει δεν έχουμε και AMD αλλά ναι  b die φυσικά! Μια ιδέα έχω αλλά όταν είναι θα σου πω  😉

[BabisTs]

18 λεπτά πριν, d4ydr33m3r είπε

Κάπου εκεί το υπολογίζω Μπάμπη για να μην ανεβάσω καθόλου vcore.. Τώρα έβαλα x72 με noctua d14 ήμουν. Μεγάλη διαφορα και ας διαβάζω διάφορα..

Η x72 είναι πολύ δυνατή aio ..............προσωπικά προτιμώ να είμαι με αέρα ..........Βάλε στόχο κάτω του 1,3vcore και ότι συχνότητα βγάλεις......χειμώνα-καλοκαίρι θα είσαι άνετος σε αυτό το vcore......εκτός να θες να παίζεις με δύο bios προφίλ (ένα επιθετικό σε vcore και σε ghz για χειμώνα και ένα πιο light για καλοκαίρι)........

μνήμες όταν πάρεις παίξε μέχρι 1,45v αν είναι b-die άφοβα...... Τα vccio & vssa πρόσεχε γιατί εκείνα κάνουν degrade στον memory controller

Επεξ/σία 19 Φεβρουαρίου 2019 από BabisTs

[d4ydr33m3r]

43 λεπτά πριν, BabisTs είπε

Η x72 είναι πολύ δυνατή aio ..............προσωπικά προτιμώ να είμαι με αέρα ..........Βάλε στόχο κάτω του 1,3vcore και ότι συχνότητα βγάλεις......χειμώνα-καλοκαίρι θα είσαι άνετος σε αυτό το vcore......εκτός να θες να παίζεις με δύο bios προφίλ (ένα επιθετικό σε vcore και σε ghz για χειμώνα και ένα πιο light για καλοκαίρι)........

μνήμες όταν πάρεις παίξε μέχρι 1,45v αν είναι b-die άφοβα...... Τα vccio & vssa πρόσεχε γιατί εκείνα κάνουν degrade στον memory controller

Πάντα παίζω κάτω από 1.3 για καφέ έτσι ήμουν από day 1 και στον 8700k.. Δεν πάω ποτε παραπανω για 24/7 δεν υπάρχει λόγος.. Αυτό που ήθελα το πέτυχα δηλαδή 8700k clocks-vcore@8c/16t.. Τώρα για κάνα  bench ή μελλοντικά αν δεν αναβαθμισω βλέπω τα 5.2 άνετα χωρίς σκοτωμα σε ρεύματα..  Ναι το ξέρω για αυτά  το προσέχω ιδιαίτερα γιατί έμεινα με το z370 και θέλω να δω πως τα πηγαίνει..

Τώρα θα ξεκινήσω ring να δω πόσο θα ανεβάσω εδώ.  Καλά μνήμες περιμένω λίγο ακόμη  να πέσουν οι τιμές γιατί θα πάω για  32Gb.. Αυτές να καταλαβεις είναι αγορασμένες από 5820k σε x99 οταν βγήκε.. Και παράπονο δεν έχω τόσο παλιες να παίζουν 3200... 

Θα δείξει..

 

Επεξ/σία 19 Φεβρουαρίου 2019 από d4ydr33m3r

[d4ydr33m3r]

[email protected] με 1.36v OCCT 2hrs small data,Prime 2hrs,realbench 2hrs .. Δεν στρεσαρω παραπανω γιατι δεν θα μεινω εκει για 24/7 φυσικα..

Μερικα σκορακια..

 

[obijuan1983]

Ξεθάφτηκε...10+ χρόνια καθόταν.

Αύριο R404 και νέο condeser.

 

 

Επεξ/σία 21 Φεβρουαρίου 2019 από obijuan1983

[d4ydr33m3r]

Ωραιος! Για δες εδω.. Σημερα την ξεθαψα καθαριζα το παταρι.. 😂

[ultraex2003]

μερικα run !!!

3770k @  4.8

RAM 16 G @ 2400 

1060 6G @  2050 /9500

drivers 418.91

win 10 insider 1903/ build 18336

Metro Exodus /in game settings /1080p /DX12

Extreme Preset

Ultra Preset

High Preset

Normal Preset

Επεξ/σία 22 Φεβρουαρίου 2019 από ultraex2003

[d4ydr33m3r]

Συνεχιζουμε εχει ζουμι

Στα 5.3 και χωρις avx offset  (4.7 uncore/ring δεν εχει νοημα για παραπανω τζαμπα στρεσαρεις cpu) μπουταρει και κανει validation με 1.38V αλλα λογικα θελει παραπανω vcore και φαινεται απο το validation score..

https://valid.x86.fr/alz28n

Mπαινω bios δινω 1.41 και ολα δειχνουν πιο σωστα.. 

https://valid.x86.fr/uphetj

Ενα cinebench και ενα timespy στα 5.3GHz.. 

Ειναι κατι τετοιες στιγμες που λες που ειναι οι μνημες ρεεε; Κοβουν αρκετο σκορ απο τα benches  

Δεν ξερω μηπως και σε Z390 μηπως ειχα καλυτερο vcore λογω καλυτερων vrm και power management στα αναλογα board

Δεν εχω παραπονο απο τον 9900k μου..

https://www.3dmark.com/3dm/33890961?

 

 

Επεξ/σία 23 Φεβρουαρίου 2019 από d4ydr33m3r

[ultraex2003]

φρεσκα νουμερακια !!!

3770κ @ 4.8 

1060 6G @  2050 /9500

drivers  419.17 

win 10 insider preview /1903 build 18841

Metro Exodus /High Preset / 1080P/in game bench settings

 

FarCryNewDawn /High Preset/1080P in game bench settings

 

 

 

FarCryNewDawn /Ultra Preset/1080P in game bench settings

 

 

 

Επεξ/σία 24 Φεβρουαρίου 2019 από ultraex2003

[obijuan1983]

7 ώρες πριν, ultraex2003 είπε

φρεσκα νουμερακια !!!

3770κ @ 4.8 

1060 6G @  2050 /9500

drivers  419.17 

win 10 insider preview /1903 build 18841

Metro Exodus /High Preset / 1080P/in game bench settings

FarCryNewDawn /High Preset/1080P in game bench settings

FarCryNewDawn /Ultra Preset/1080P in game bench settings

Ωραίος, ανέβασε και κανένα νούμερακι στο HWBOT σε φτάνω επικίνδυνα!

[BabisTs]

Far Cry New Dawn & Ultra Preset at 1080P ......stock Rtx 2080

 

[BabisTs]

Metro Exodus ........ότι έπιασα Taiga ......stock gpu.....

rtx ultra vs rtx off

 

 

Επεξ/σία 27 Φεβρουαρίου 2019 από BabisTs

[ultraex2003]

νεο Afterburner 4.6.0 Beta 15 v14697 - Adds Radeon VII support + RTSS 7.2.1 Beta 5 (build 20189) (included in beta download)

https://www.guru3d.com/files-get/msi-afterburner-beta-download,34.html

MSI Afterburner 4.6.0 beta 15

• Includes full RVII support, including overclocking (which was missing in the previous early b15 build).
• Now you can use <Tab> and <Shift>+<Tab> keys to select next/previous point on the curve. This feature is useful for those who prefer to use keyboard <Up>/<Down> keys to fine-tune selected point frequency offset instead of adjusting the point with mouse cursor. I'm not sure if many of you know that, but I'll remind that you can also hold <Ctrl> while fine-tuning frequency offset with <Up>/<Down> keys to jump to the nearest frequency value rounded to 10MHz
• Now you can press <Enter> key to edit selected point frequency offset from keyboard. Alternately you may press <Shift>+<Enter> to specify absolute target frequency value, so the editor will calculate desired offset automatically
• Slightly changed keyboard control interface for AMD implementation of V/F curve editor. Previously you could select P-State and fine-tune frequency with <Up>/<Down> or <Ctrl>+<Up>/<Ctrl>+<Down> keys or fine-tune voltage <Left>/<Right> or <Ctrl>+<Left>/<Ctrl>+<Right> keys. Now both frequency and voltage are adjusted with <Up>/<Down> or <Ctrl>+<Up>/<Ctrl>+<Down> keys and voltage or frequency keyboard input focus is selected with <PageUp> / <PageDown> keys. Voltage or frequency keyboard input focus is now highlighted by selected point brightness on the curve. Keyboard input focus also affects new <Enter> / <Shift> + <Enter> functionality, allowing you to type in target voltage or frequency in both offset or absolute form
• Similar to NVIDIA implementation, now you may also hold <Alt> when dragging V/F curve point on AMD systems. This will result in moving whole curve up/down while preserving each point's offset
• Added undo/redo support to voltage/frequency curve editor:
  • Now voltage/frequency curve editor is saving up to 1024 last states of the curve during editing and allows you to undo/redo changes with <Ctrl>+<Z> or <Ctrl>+<Y> / <Ctrl>+<Shift>+<Z> keys
  • Undo history is discarded when you apply the curve, forcibly reread it from hardware with <F5> key or switch to different GPU on multi-GPU system
  • Number of recorded undo/redo steps is displayed in square brackets in the editor window caption
• Application properties dialog window is now displayed with topmost style when the properties are activated from detached monitoring window and "Always on top" mode is enabled for it
• NVIDIA Scanner components are updated to latest version, NVML.dll issue should be addressed now

RTSS 7.2.1 Beta 5 (build 20189) (included in beta download)
 

• Slightly refactored Direct3D and Vulkan On-Screen Display rendering codepaths due to implementation of optional offscreen rendering mode. This mode is currently disabled by default, it is reserved for future versions as a codebase for asynchronous On-Screen Display rendering implementation
• Changed power user protected settings locking approach. Now power user settings ("Enable Custom Direct3D support" options and Vector2D On-Screen Display rendering mode) are locked for enabling by default in the global profile only, but you can still change them at application profiles level
• Now RivaTuner Statistics Server validates DirectX runtimes installation at startup and displays warning message if required DirectX runtime components are missing. Power users may disable this warning message as well as any previously existing diagnostic warning messages displayed at RivaTuner Statistics Server startup and enable silent startup mode via the configuration file if necessary
• Added user extendable exclusions list for desktop windows notification performed during installation and uninstallation of system CBT hooks. Currently the only exclusion in the list is Microsoft Outlook process, which previously tended to display help popup window on closing RivaTuner Statistics Server
• Rendering pipeline flushing no longer stays active if you enable scanline sync mode but disable framerate limiting support with hotkeys from MSI Afterburner
• Fixed multhithreaded active busy-wait loop based frame capture implementation, which could prevent desktop videocapture from working in the previous version

** A few important notes for RADEON VII owners:

• Core voltage slider in MSI AB is supposed to be locked on RVII, that’s normal and by design. On the previous AMD GPUs the slider provided direct voltage control mode implemented via low-level access to SMC or voltage controller (slider position defined either full target voltage override or P-State independent voltage offset) and such voltage adjustment form was required because native AMD driver’s voltage adjustment range was too low. On RVII series cards AMD driver allows up to 1.2V overvoltage (from default 1V) and voltage control is provided in MSI AB at voltage/frequency curve editor level. So simply open the editor (either press VF editor button in the skin next to core clock slider or hit <Ctrl>+<F> keyboard shortcut to open the editor) and you’ll be able to adjust voltage there.
• Temperature limit slider is also supposed to be locked by design on RVII, it was a part of old AMD fan control algorithm. It is gone with Adrenalin 2019 drivers family when fan curve adjustment approach was introduced by AMD. So it is no longer adjustable in AMD driver and supposed to be locked now.
• Voltage/frequency editor is allowing you to adjust frequencies and voltages independently for all 3 V/F curve points (or 3 P-States), however AMD driver and RVII architecture put some restrictions on the curve editing approach. So the curve will be corrected according to the following limitations when you apply it:
  • You can adjust the frequency independently for the first and the last point only. Middle point frequency cannot be adjusted independently, frequencies are always linearly interpolated from the first point to the last point. So if you try to adjust frequency for the middle point, it will be corrected according to interpolation rule mentioned above right after applying new settings
  • Unlike the frequencies, you can independently adjust voltages for all 3 points
  • You cannot set frequencies and voltages below the minimum (which is rather strict and very close to default). This puts some limitations on lower P-State downclocking/downvolting
  • 2 GPU temperatures displayed by MSI AB hardware monitoring module are mapped to edge and junction temperatures. 4 displayed VRM temperatures are mapped to core VRM, SOC VRM and 2 memory VRM sensors. AMD’s fan curve is using junction temperature for their fan speed adjustment. I’m not sure if it is really good idea because it is skyrocketing to 100C area pretty rapidly when GPU is busy, that’s actually direct reason why RVII cooling is so loud by default. Opposing to that, MSI AB’s software fan curve implementation is still using traditional edge temperature sensor. Probably I’ll add an ability to select input thermal sensor for software fan curve adjustment in future versions, but honestly I’m not sure if it worth the efforts
  • Currently AMD's own GPU usage sensor is suffering from pretty bad 0%->100%->0% fluctuations. Similar issues affected some old GPUs in the past but it is much worse on RVII now. I believe that it is what they mean with "Performance metrics overlay and Radeon WattMan gauges may experience inaccurate fluctuating readings on AMD Radeon VII" in the driver's known issues, so there is a hope to see a fix from AMD in future. I remind you that it is possible to get rid of such fluctuations via enabling unified GPU usage monitoring in MSI AB properties, however this option depends on DirectX GPU usage performance counter and this counter requires OS and display driver WDDM versions to match. Current AMD drivers are targeted to WDDM 2.5 OS (October Update), so this option will only help you if you have 1809 OS version installed. Otherwise you'll see zero GPU usage all the time after enabling it.

 

[ultraex2003]

νεο update Afterburner 4.6.0 Beta 16 build 14806 - more Radeon VII and a new skin

https://www.guru3d.com/files-details/msi-afterburner-beta-download.html

 

MSI Afterburner 4.6.0 beta 16

• Includes full RVII support, including overclocking (which was missing in the previous early b15 build).
• Now you can use <Tab> and <Shift>+<Tab> keys to select next/previous point on the curve. This feature is useful for those who prefer to use keyboard <Up>/<Down> keys to fine-tune selected point frequency offset instead of adjusting the point with mouse cursor. I'm not sure if many of you know that, but I'll remind that you can also hold <Ctrl> while fine-tuning frequency offset with <Up>/<Down> keys to jump to the nearest frequency value rounded to 10MHz
• Now you can press <Enter> key to edit selected point frequency offset from keyboard. Alternately you may press <Shift>+<Enter> to specify absolute target frequency value, so the editor will calculate desired offset automatically
• Slightly changed keyboard control interface for AMD implementation of V/F curve editor. Previously you could select P-State and fine-tune frequency with <Up>/<Down> or <Ctrl>+<Up>/<Ctrl>+<Down> keys or fine-tune voltage <Left>/<Right> or <Ctrl>+<Left>/<Ctrl>+<Right> keys. Now both frequency and voltage are adjusted with <Up>/<Down> or <Ctrl>+<Up>/<Ctrl>+<Down> keys and voltage or frequency keyboard input focus is selected with <PageUp> / <PageDown> keys. Voltage or frequency keyboard input focus is now highlighted by selected point brightness on the curve. Keyboard input focus also affects new <Enter> / <Shift> + <Enter> functionality, allowing you to type in target voltage or frequency in both offset or absolute form
• Similar to NVIDIA implementation, now you may also hold <Alt> when dragging V/F curve point on AMD systems. This will result in moving whole curve up/down while preserving each point's offset
• Added undo/redo support to voltage/frequency curve editor:
  • Now voltage/frequency curve editor is saving up to 1024 last states of the curve during editing and allows you to undo/redo changes with <Ctrl>+<Z> or <Ctrl>+<Y> / <Ctrl>+<Shift>+<Z> keys
  • Undo history is discarded when you apply the curve, forcibly reread it from hardware with <F5> key or switch to different GPU on multi-GPU system
  • Number of recorded undo/redo steps is displayed in square brackets in the editor window caption
• Application properties dialog window is now displayed with topmost style when the properties are activated from detached monitoring window and "Always on top" mode is enabled for it
• NVIDIA Scanner components are updated to latest version, NVML.dll issue should be addressed now

RTSS 7.2.1 Beta 5 (build 20189) (included in beta download)
 

• Slightly refactored Direct3D and Vulkan On-Screen Display rendering codepaths due to implementation of optional offscreen rendering mode. This mode is currently disabled by default, it is reserved for future versions as a codebase for asynchronous On-Screen Display rendering implementation
• Changed power user protected settings locking approach. Now power user settings ("Enable Custom Direct3D support" options and Vector2D On-Screen Display rendering mode) are locked for enabling by default in the global profile only, but you can still change them at application profiles level
• Now RivaTuner Statistics Server validates DirectX runtimes installation at startup and displays warning message if required DirectX runtime components are missing. Power users may disable this warning message as well as any previously existing diagnostic warning messages displayed at RivaTuner Statistics Server startup and enable silent startup mode via the configuration file if necessary
• Added user extendable exclusions list for desktop windows notification performed during installation and uninstallation of system CBT hooks. Currently the only exclusion in the list is Microsoft Outlook process, which previously tended to display help popup window on closing RivaTuner Statistics Server
• Rendering pipeline flushing no longer stays active if you enable scanline sync mode but disable framerate limiting support with hotkeys from MSI Afterburner
• Fixed multhithreaded active busy-wait loop based frame capture implementation, which could prevent desktop videocapture from working in the previous version

** A few important notes for RADEON VII owners:

• Core voltage slider in MSI AB is supposed to be locked on RVII, that’s normal and by design. On the previous AMD GPUs the slider provided direct voltage control mode implemented via low-level access to SMC or voltage controller (slider position defined either full target voltage override or P-State independent voltage offset) and such voltage adjustment form was required because native AMD driver’s voltage adjustment range was too low. On RVII series cards AMD driver allows up to 1.2V overvoltage (from default 1V) and voltage control is provided in MSI AB at voltage/frequency curve editor level. So simply open the editor (either press VF editor button in the skin next to core clock slider or hit <Ctrl>+<F> keyboard shortcut to open the editor) and you’ll be able to adjust voltage there.
• Temperature limit slider is also supposed to be locked by design on RVII, it was a part of old AMD fan control algorithm. It is gone with Adrenalin 2019 drivers family when fan curve adjustment approach was introduced by AMD. So it is no longer adjustable in AMD driver and supposed to be locked now.
• Voltage/frequency editor is allowing you to adjust frequencies and voltages independently for all 3 V/F curve points (or 3 P-States), however AMD driver and RVII architecture put some restrictions on the curve editing approach. So the curve will be corrected according to the following limitations when you apply it:
  • You can adjust the frequency independently for the first and the last point only. Middle point frequency cannot be adjusted independently, frequencies are always linearly interpolated from the first point to the last point. So if you try to adjust frequency for the middle point, it will be corrected according to interpolation rule mentioned above right after applying new settings
  • Unlike the frequencies, you can independently adjust voltages for all 3 points
  • You cannot set frequencies and voltages below the minimum (which is rather strict and very close to default). This puts some limitations on lower P-State downclocking/downvolting
  • 2 GPU temperatures displayed by MSI AB hardware monitoring module are mapped to edge and junction temperatures. 4 displayed VRM temperatures are mapped to core VRM, SOC VRM and 2 memory VRM sensors. AMD’s fan curve is using junction temperature for their fan speed adjustment. I’m not sure if it is really good idea because it is skyrocketing to 100C area pretty rapidly when GPU is busy, that’s actually direct reason why RVII cooling is so loud by default. Opposing to that, MSI AB’s software fan curve implementation is still using traditional edge temperature sensor. Probably I’ll add an ability to select input thermal sensor for software fan curve adjustment in future versions, but honestly I’m not sure if it worth the efforts
  • Currently AMD's own GPU usage sensor is suffering from pretty bad 0%->100%->0% fluctuations. Similar issues affected some old GPUs in the past but it is much worse on RVII now. I believe that it is what they mean with "Performance metrics overlay and Radeon WattMan gauges may experience inaccurate fluctuating readings on AMD Radeon VII" in the driver's known issues, so there is a hope to see a fix from AMD in future. I remind you that it is possible to get rid of such fluctuations via enabling unified GPU usage monitoring in MSI AB properties, however this option depends on DirectX GPU usage performance counter and this counter requires OS and display driver WDDM versions to match. Current AMD drivers are targeted to WDDM 2.5 OS (October Update), so this option will only help you if you have 1809 OS version installed. Otherwise you'll see zero GPU usage all the time after enabling it.