[Thread Ufficiale] CPU Zen 14/12/7nm: AMD Ryzen!

[Randa71]

Confermata da AMD la nuova versione
https://www.guru3d.com/news-story/am...blog-post.html

[fraussantin]

Originariamente inviato da Randa71

Confermata da AMD la nuova versione
https://www.guru3d.com/news-story/am...blog-post.html

Fra 2\3settimane .

Va buo' non c'é fretta , basta le testino perbenino.

[Alex656]

Originariamente inviato da Baio73

Beh, direi che la colpa non è proprio tutta tutta di ASUS a questo giro…

Ma per "scempio" a cosa ti riferisci esattamente?

Baio

Mi riferisco a problemi, anche gravi, che sembravano superati e si sono ripresentati; primi tra tutti i problemi all'avvio (cold/fake/double boot) e le ventole che si fermano rischiando di fare danni. Non vorrei sembrare quello che si lamenta sempre, se tornassi indietro ricomprerei comunque la CHVI e tutto il resto, però un pò più di professionalità da parte di Asus non guasterebbe.

[stefano192]

Ho visto un video dove fanno dei benchmark di un 3900x su una b450 e una x570 taichi e praticamente fanno gli stessi risultati. Confermate?

[ninja750]

scrivono che hanno reso disponibile un sdk per software terze parti per leggere meglio voltaggi e temperature, chissà che non vedremo un calo delle temperature rilevate es hwinfo?

[antonioalex]

Originariamente inviato da Baio73

Cosa c'entra ASUS con la scarsa disponibilità delle CPU 3900x?

Baio

E chi mai ha detto che la colpa è di Asus? Ho semplicemente detto che poco mi frega del bios, mi interesserebbe di più sapere sti benedetti 3900x che fine hanno fatto?

[paolo.oliva2]

Originariamente inviato da antonioalex

E chi mai ha detto che la colpa è di Asus? Ho semplicemente detto che poco mi frega del bios, mi interesserebbe di più sapere sti benedetti 3900x che fine hanno fatto?

Per me, bene o male è soggettivo, è perchè potrebbe essere un X24 l'entry-level TR4.

Facciamo un po' mente locale... la sigla 3950X è la naturale dal passaggio Zen+ a Zen2. Un TR4 X16 come lo sigleresti? SE AMD partirà con TR4 con un X24... 3970X e via.

Guardiamo un po' il prezzaggio quando nello stesso package c'è un chiplet in più (AM4 3900X e 3950X).

Il 3600X viene 250€... praticamente il 3900X viene una virgola in più del doppio, nonostante la selezione migliore. Il 3950X X16, costa meno rispetto a due 3800X, nonostante la selezione migliore.

Quindi è ovvio che il prezzo a core nelle varianti a più chiplet, da una parte AMD non lucra perchè non chiede di più (e con l'inesistenza di una offerta Intel oltre 18 core...lo potrebbe fare), ma è ovvio che ci guadagna un tot di più (Ovviamente il motherchip sarà dimensionato in proporzione a quanti chiplet si possono "attaccare" ma viene da se che a costo pachage quasi uguale, un 24 avrebbe 1 motherchip vs i 3 di 3 3900X, oltre al costo di 1 package + confezione che sarà certamente inferiore a quello di 3 package 3900X + 3 confezioni.

A me viene da pensare, che 3900X e 3950X AMD li ha proposti per fare immagine... ma per me lo scopo finale di AMD è quello di portare chi fa MT sulla piatta TR4... perchè se prezzi un 3950X X16 AM4 a 750€ e a fianco proponi un 3970X X24 TR4 a 1000€ (o 995€ per fare scena), ben più di una persona ci rifletterebbe.... ed AMD prenderebbe 2 piccioni con una fava... perchè da una parte sicuro guadagna di più con un 3970X vs 3950X, dall'altra metterebbe una voragine nel prezzo a core sulla proposta Intel.

Poi ora come ora che la mobo X570 top per un 3950X costerebbe addirittura di più di una X399 "tosta", e che un X16 con 16GB ci starebbe strezzo, e 32GB di DDR4 3600 costano un pozzo, mentre con <200€ ci prendi 32GB 2933 che su quad channel equivarrebbero a delle 5866... i pensieri li farei, ed anche più di uno.

[baila]

Originariamente inviato da Baio73

Cosa c'entra ASUS con la scarsa disponibilità delle CPU 3900x?

Baio

Disponibile dal sito AMD,e mi pare abbiano aumentato pure il prezzo
Anche Amazon.it ma in preordine...

[macchiaiolo]

Ho appena installato il bios nuovo di oggi su una Asus x470_f e nn è cambiato niente

Inviato dal mio HUAWEI VNS-L31 utilizzando Tapatalk

[capitan_crasy]

Hello, everyone! We're delighted by your support and the strong momentum of 3rd Gen AMD Ryzen processors in the marketplace, and we continue to watch your feedback closely. Today we have some important updates for you concerning processor boost behavior, desktop idle behavior, and a new monitoring SDK. The first two changes will be arriving in BIOSes based on AGESA 1003ABBA, and we are planning to make the SDK public on developer.amd.com with a target release date of September 30.

Boost Changes
Starting with our commitment to provide you an update on processor boost, our analysis indicates that the processor boost algorithm was affected by an issue that could cause target frequencies to be lower than expected. This has been resolved. We've also been exploring other opportunities to optimize performance, which can further enhance the frequency. These changes are now being implemented in flashable BIOSes from our motherboard partners. Across the stack of 3rd Gen Ryzen Processors, our internal testing shows that these changes can add approximately 25-50 MHz to the current boost frequencies under various workloads.

Our estimation of the benefit is broadly based on workloads like PCMark 10 and Kraken JavaScript Benchmark. The actual improvement may be lower or higher depending on the workload, system configuration, and thermal/cooling solution implemented in the PC. We used the following test system in our analysis:

• AMD Reference Motherboard (AGESA 1003ABBA beta BIOS)
• 2x8GB DDR4-3600C16
• AMD Wraith Prism and Noctua NH-D15S coolers
• Windows 10 May 2019 Update
• 22°C ambient test lab
• Streacom BC1 Open Benchtable
• AMD Chipset Driver 1.8.19.xxx
• AMD Ryzen Balanced power plan
• BIOS defaults (except memory OC)

These improvements will be available in final BIOSes starting in about three weeks' time, depending on the testing and implementation schedule of your motherboard manufacturer. Additional information on boost frequency in the 3rd Gen AMD Ryzen Processors can also be obtained from this separate blog update.

Going forward, it's important to understand how our boost technology operates. Our processors perform intelligent real-time analysis of the CPU temperature, motherboard voltage regulator current (amps), socket power (watts), loaded cores, and workload intensity to maximize performance from millisecond to millisecond. Ensuring your system has adequate thermal paste; reliable system cooling; the latest motherboard BIOS; reliable BIOS settings/configuration; the latest AMD chipset driver; and the latest operating system can enhance your experience.

Following the installation of the latest BIOS update, a consumer running a bursty, single threaded application on a PC with the latest software updates and adequate voltage and thermal headroom should see the maximum boost frequency of their processor. PCMark 10 is a good proxy for a user to test the maximum boost frequency of the processor in their system. It is fully expected that if users run a workload like Cinebench, which runs for an extended period of time, the operating frequencies may be lower than maximum throughout the run.

In addition, we do want to address recent questions about reliability. We perform extensive engineering analysis to develop reliability models and to model the lifetime of our processors before entering mass production. While AGESA 1003AB contained changes to improve system stability and performance for users, changes were not made for product longevity reasons. We do not expect that the improvements that have been made in boost frequency for AGESA 1003ABBA will have any impact on the lifetime of your Ryzen processor.

Revisiting Calmer Idle
In late July, we implemented a series of software changes that would help the processor ignore requests for voltage/frequency boost from lightweight applications. The goal was to make the processor more relaxed at the desktop, but poised to react for serious workloads. While many of you were happy with the effect of the software changes, some of you were still grappling with cases where the CPU was a bit overzealous with boost. We wanted to smooth those out, too.

Today we're announcing that AGESA 1003ABBA carries firmware-level changes designed to do just that. The changes primarily arrive in the form of an "activity filter" that empowers the CPU boost algorithm itself to disregard intermittent OS and application background noise. Example test cases might include: video playback, game launchers, monitoring utilities, and peripheral utilities. These cases tend to make regular requests for a higher boost state, but their intermittent nature would fall below the threshold of the activity filter.

Net-net, we expect you'll see lower desktop voltages, around 1.2 V, for the core(s) actively handling such tasks. We believe this solution will be even more effective than the July changes for an even wider range of applications.

Please keep in mind, however, that this firmware change is not a cap. The processor must still be free to boost if active workload(s) seriously require it, so you should still expect occasions where the processor will explore its designed and tested voltage range of 0.2 V to 1.5 V.

New Monitoring SDK
Obtaining reliable data about the operating behavior of a processor is important to enthusiasts such as myself. There are many monitoring utilities on the market, and we work with many of them to ensure they're accessing telemetry data in a sensible manner. Regardless of the utility, however, it's common sense that all the tools should roughly correlate when you ask a simple question like "what's my CPU temperature?"

Enabling a consistent experience across monitoring utilities is important to us. That's why we're announcing the September 30 release of the AMD Monitoring SDK that will allow anyone to build a public monitoring utility that can reliably report a range of key processor metrics in a consistent manner. Altogether, there are 30+ API calls within the first SDK release, but we've highlighted a few of the more important or interesting ones below:

• Current Operating Temperature: Reports the average temperature of the CPU cores over a short sample period. By design, this metric filters transient spikes that can skew temperature reporting.
• Peak Core(s) Voltage (PCV): Reports the Voltage Identification (VID) requested by the CPU package of the motherboard voltage regulators. This voltage is set to service the needs of the cores under active load, but isn't necessarily the final voltage experienced by all of the CPU cores.
• Average Core Voltage (ACV): Reports the average voltages experienced by all processor cores over a short sample period, factoring in active power management, sleep states, Vdroop, and idle time.
• EDC (A), TDC (A), PPT (W): The current and power limits for your motherboard VRMs and processor socket.
• Peak Speed: The maximum frequency of the fastest core during the sample period.
• Effective Frequency: The frequency of the processor cores after factoring in time spent in sleep states (e.g. cc6 core sleep or pc6 package sleep). Example: One processor core is running at 4 GHz while awake, but in cc6 core sleep for 50% of the sample period. The effective frequency of this core would be 2 GHz. This value can give you a feel for how often the cores are using aggressive power management capabilities that aren't immediately obvious (e.g. clock or voltage changes).
• Various voltages and clocks, including: SoC voltage, DRAM voltage, fabric clock, memory clock, etc.

A Preview in Action
This SDK will be available for public download on developer.amd.com on September 30. As a preview of what the new SDK can enable, AMD Ryzen Master (version 2.0.2.1271) has already been updated with the new Average Core Voltage API for 3rd Gen Ryzen Processors. It's ready for download today!

As noted above, Average Core Voltage shows you average voltages that all CPU cores are experiencing over a short sample period after you factor in sleep states, idle states, active power management, and Vdroop. Depending on the load on the processor, this value might be quite different from Peak Core(s) Voltage.

For example: if the processor is lightly loaded on a few cores, the overall activity level of all the CPU cores will be relatively low and, therefore, the Average Core Voltage will be low as well. But the active cores still need intermittently higher voltages to power boost frequencies, which will be reflected in the Peak Core Voltage. As the CPU comes under full load, these two values will eventually converge representing that all cores are active at approximately the same intensity. The overall goal of these two values is to show you what's happening moment-to-moment the most loaded cores (Peak), and what's happening more generally to the CPU cores over time (Average).

We hope new APIs like Average Core Voltage give you a better understanding of how our processors behave, and we can't wait to see more tools make use of the new monitoring SDK. Visit amd.com on September 30 for the first public release!

What to Expect Next
AGESA 1003ABBA has now been released to our motherboard partners. Now they will perform additional testing, QA, and implementation work on their specific hardware (versus our reference motherboard). Final BIOSes based on AGESA 1003ABBA will begin to arrive in approximately three weeks, depending on the testing time of your vendor and motherboard.

Going forward, we'll continue providing updates in this format as the updates are being prepped for release.

Clicca qui...

[paolo.oliva2]

Originariamente inviato da capitan_crasy

Hello, everyone! We're delighted by your support and the strong momentum of 3rd Gen AMD Ryzen processors in the marketplace, and we continue to watch your feedback closely. Today we have some important updates for you concerning processor boost behavior, desktop idle behavior, and a new monitoring SDK. The first two changes will be arriving in BIOSes based on AGESA 1003ABBA, and we are planning to make the SDK public on developer.amd.com with a target release date of September 30.

Boost Changes
Starting with our commitment to provide you an update on processor boost, our analysis indicates that the processor boost algorithm was affected by an issue that could cause target frequencies to be lower than expected. This has been resolved. We've also been exploring other opportunities to optimize performance, which can further enhance the frequency. These changes are now being implemented in flashable BIOSes from our motherboard partners. Across the stack of 3rd Gen Ryzen Processors, our internal testing shows that these changes can add approximately 25-50 MHz to the current boost frequencies under various workloads.

Our estimation of the benefit is broadly based on workloads like PCMark 10 and Kraken JavaScript Benchmark. The actual improvement may be lower or higher depending on the workload, system configuration, and thermal/cooling solution implemented in the PC. We used the following test system in our analysis:

• AMD Reference Motherboard (AGESA 1003ABBA beta BIOS)
• 2x8GB DDR4-3600C16
• AMD Wraith Prism and Noctua NH-D15S coolers
• Windows 10 May 2019 Update
• 22°C ambient test lab
• Streacom BC1 Open Benchtable
• AMD Chipset Driver 1.8.19.xxx
• AMD Ryzen Balanced power plan
• BIOS defaults (except memory OC)

These improvements will be available in final BIOSes starting in about three weeks' time, depending on the testing and implementation schedule of your motherboard manufacturer. Additional information on boost frequency in the 3rd Gen AMD Ryzen Processors can also be obtained from this separate blog update.

Going forward, it's important to understand how our boost technology operates. Our processors perform intelligent real-time analysis of the CPU temperature, motherboard voltage regulator current (amps), socket power (watts), loaded cores, and workload intensity to maximize performance from millisecond to millisecond. Ensuring your system has adequate thermal paste; reliable system cooling; the latest motherboard BIOS; reliable BIOS settings/configuration; the latest AMD chipset driver; and the latest operating system can enhance your experience.

Following the installation of the latest BIOS update, a consumer running a bursty, single threaded application on a PC with the latest software updates and adequate voltage and thermal headroom should see the maximum boost frequency of their processor. PCMark 10 is a good proxy for a user to test the maximum boost frequency of the processor in their system. It is fully expected that if users run a workload like Cinebench, which runs for an extended period of time, the operating frequencies may be lower than maximum throughout the run.

In addition, we do want to address recent questions about reliability. We perform extensive engineering analysis to develop reliability models and to model the lifetime of our processors before entering mass production. While AGESA 1003AB contained changes to improve system stability and performance for users, changes were not made for product longevity reasons. We do not expect that the improvements that have been made in boost frequency for AGESA 1003ABBA will have any impact on the lifetime of your Ryzen processor.

Revisiting Calmer Idle
In late July, we implemented a series of software changes that would help the processor ignore requests for voltage/frequency boost from lightweight applications. The goal was to make the processor more relaxed at the desktop, but poised to react for serious workloads. While many of you were happy with the effect of the software changes, some of you were still grappling with cases where the CPU was a bit overzealous with boost. We wanted to smooth those out, too.

Today we're announcing that AGESA 1003ABBA carries firmware-level changes designed to do just that. The changes primarily arrive in the form of an "activity filter" that empowers the CPU boost algorithm itself to disregard intermittent OS and application background noise. Example test cases might include: video playback, game launchers, monitoring utilities, and peripheral utilities. These cases tend to make regular requests for a higher boost state, but their intermittent nature would fall below the threshold of the activity filter.

Net-net, we expect you'll see lower desktop voltages, around 1.2 V, for the core(s) actively handling such tasks. We believe this solution will be even more effective than the July changes for an even wider range of applications.

Please keep in mind, however, that this firmware change is not a cap. The processor must still be free to boost if active workload(s) seriously require it, so you should still expect occasions where the processor will explore its designed and tested voltage range of 0.2 V to 1.5 V.

New Monitoring SDK
Obtaining reliable data about the operating behavior of a processor is important to enthusiasts such as myself. There are many monitoring utilities on the market, and we work with many of them to ensure they're accessing telemetry data in a sensible manner. Regardless of the utility, however, it's common sense that all the tools should roughly correlate when you ask a simple question like "what's my CPU temperature?"

Enabling a consistent experience across monitoring utilities is important to us. That's why we're announcing the September 30 release of the AMD Monitoring SDK that will allow anyone to build a public monitoring utility that can reliably report a range of key processor metrics in a consistent manner. Altogether, there are 30+ API calls within the first SDK release, but we've highlighted a few of the more important or interesting ones below:

• Current Operating Temperature: Reports the average temperature of the CPU cores over a short sample period. By design, this metric filters transient spikes that can skew temperature reporting.
• Peak Core(s) Voltage (PCV): Reports the Voltage Identification (VID) requested by the CPU package of the motherboard voltage regulators. This voltage is set to service the needs of the cores under active load, but isn't necessarily the final voltage experienced by all of the CPU cores.
• Average Core Voltage (ACV): Reports the average voltages experienced by all processor cores over a short sample period, factoring in active power management, sleep states, Vdroop, and idle time.
• EDC (A), TDC (A), PPT (W): The current and power limits for your motherboard VRMs and processor socket.
• Peak Speed: The maximum frequency of the fastest core during the sample period.
• Effective Frequency: The frequency of the processor cores after factoring in time spent in sleep states (e.g. cc6 core sleep or pc6 package sleep). Example: One processor core is running at 4 GHz while awake, but in cc6 core sleep for 50% of the sample period. The effective frequency of this core would be 2 GHz. This value can give you a feel for how often the cores are using aggressive power management capabilities that aren't immediately obvious (e.g. clock or voltage changes).
• Various voltages and clocks, including: SoC voltage, DRAM voltage, fabric clock, memory clock, etc.

A Preview in Action
This SDK will be available for public download on developer.amd.com on September 30. As a preview of what the new SDK can enable, AMD Ryzen Master (version 2.0.2.1271) has already been updated with the new Average Core Voltage API for 3rd Gen Ryzen Processors. It's ready for download today!

As noted above, Average Core Voltage shows you average voltages that all CPU cores are experiencing over a short sample period after you factor in sleep states, idle states, active power management, and Vdroop. Depending on the load on the processor, this value might be quite different from Peak Core(s) Voltage.

For example: if the processor is lightly loaded on a few cores, the overall activity level of all the CPU cores will be relatively low and, therefore, the Average Core Voltage will be low as well. But the active cores still need intermittently higher voltages to power boost frequencies, which will be reflected in the Peak Core Voltage. As the CPU comes under full load, these two values will eventually converge representing that all cores are active at approximately the same intensity. The overall goal of these two values is to show you what's happening moment-to-moment the most loaded cores (Peak), and what's happening more generally to the CPU cores over time (Average).

We hope new APIs like Average Core Voltage give you a better understanding of how our processors behave, and we can't wait to see more tools make use of the new monitoring SDK. Visit amd.com on September 30 for the first public release!

What to Expect Next
AGESA 1003ABBA has now been released to our motherboard partners. Now they will perform additional testing, QA, and implementation work on their specific hardware (versus our reference motherboard). Final BIOSes based on AGESA 1003ABBA will begin to arrive in approximately three weeks, depending on the testing time of your vendor and motherboard.

Going forward, we'll continue providing updates in this format as the updates are being prepped for release.

Clicca qui...

Esempio di cosa riporta HWinfo e CPU-z vs Ryzen Master.



OC manuale @4,1GHz, 5 core su 8 spenti e quei 3 frequenza max 436MHz... gli altri software rilevano 4,1GHz , HWinfo rileva 1,250V per tutti i core.

Per me... AMD ha dovuto allungare il tempo di funzionamento alla frequenza max... perchè come sopra viene rilevata (da altri software) una frequenza maggiore della realtà... possibilissimo che venga rilevata una frequenza inferiore (di 25MHz) rispetto alla realtà.
Poi c'è anche il fatto che in molti pensano che PBO AUTO vuol dire attivato... poi mi sembra che gran parte di chi aveva Zen 1000/2000 (e quindi conosce il sistema AMD), i più non hanno prb e se li anno ugualmente, allora il problema è nel bios della mobo.

Il miglior sistema per capire la frequenza effettiva del procio, per me rimane la comparazione del risultato in un bench.
Esegui il bench a frequenza fissa (impostando un clock/Vcore da bios), ed hai subito il metro... indipendentemente dalla frequenza riportata da Tizio, Caio e Sempronio.

[Avengedrobix]

Originariamente inviato da paolo.oliva2

Esempio di cosa riporta HWinfo e CPU-z vs Ryzen Master.



OC manuale @4,1GHz, 5 core su 8 spenti e quei 3 frequenza max 436MHz... gli altri software rilevano 4,1GHz , HWinfo rileva 1,250V per tutti i core.

Per me... AMD ha dovuto allungare il tempo di funzionamento alla frequenza max... perchè come sopra viene rilevata (da altri software) una frequenza maggiore della realtà... possibilissimo che venga rilevata una frequenza inferiore (di 25MHz) rispetto alla realtà.
Poi c'è anche il fatto che in molti pensano che PBO AUTO vuol dire attivato... poi mi sembra che gran parte di chi aveva Zen 1000/2000 (e quindi conosce il sistema AMD), i più non hanno prb e se li anno ugualmente, allora il problema è nel bios della mobo.

Il miglior sistema per capire la frequenza effettiva del procio, per me rimane la comparazione del risultato in un bench.
Esegui il bench a frequenza fissa (impostando un clock/Vcore da bios), ed hai subito il metro... indipendentemente dalla frequenza riportata da Tizio, Caio e Sempronio.

Quoto in tutto . E fatevi due bench invece di guardare YouTube 😁

Inviato dal mio ONEPLUS A6013 utilizzando Tapatalk

[Joe Average]

Ciao a tutti, ho intenzione di comprare un Ryzen 3000 ma non so ancora quale. Uso il PC per ufficio e gioco, niente di esoterico. Non ho competenze né sono interessato a fare OC, se non forse in modo automatico, sbloccando PBO o cose del genere. Ora ho un i5 4670 che ha fatto il suo dovere a lungo ma che inizia a segnare il passo giocando in 2k, specialmente in multiplayer.
Sono indeciso se comprare un 3600 e un buon cooler come un Noctua, tenerlo un paio d'anni per poi prendere l'ultima generazione AM4 quando uscirà oppure un 3700x e tenerlo fino al prossimo socket, usando il Prism.
Mi rendo conto che questo è un forum di entusiasti e che forse non è il posto giusto per quesiti così basic ma ci provo comunque.
Ah, venendo da Intel comprerei una 570 decente, magari datemi una dritta anche su questo se potete.

Inviato dal mio WAS-LX1A utilizzando Tapatalk

[fraussantin]

Un altra cosa strana che non ho capito il motivo.

Tw3 moddato a manetta :

Col 4690k 4 core stavano dal 50 a 99% di uso tutti uguali ,
Qui un solo core al 99% e un altro basso 30 ,40 ...

Il resto a zonzo.

Lock sempre a 60 fps ( tanto il collo è la GPU)

È normale sta cosa?

[Randa71]

Originariamente inviato da fraussantin

Un altra cosa strana che non ho capito il motivo.

Tw3 moddato a manetta :

Col 4690k 4 core stavano dal 50 a 99% di uso tutti uguali ,
Qui un solo core al 99% e un altro basso 30 ,40 ...

Il resto a zonzo.

Lock sempre a 60 fps ( tanto il collo è la GPU)

È normale sta cosa?

secondo me si. in base al thread grouping di ZEN 2

[Annamaria]

Originariamente inviato da Joe Average

Ciao a tutti, ho intenzione di comprare un Ryzen 3000 ma non so ancora quale. Uso il PC per ufficio e gioco, niente di esoterico. Non ho competenze né sono interessato a fare OC, se non forse in modo automatico, sbloccando PBO o cose del genere. Ora ho un i5 4670 che ha fatto il suo dovere a lungo ma che inizia a segnare il passo giocando in 2k, specialmente in multiplayer.
Sono indeciso se comprare un 3600 e un buon cooler come un Noctua, tenerlo un paio d'anni per poi prendere l'ultima generazione AM4 quando uscirà oppure un 3700x e tenerlo fino al prossimo socket, usando il Prism.
Mi rendo conto che questo è un forum di entusiasti e che forse non è il posto giusto per quesiti così basic ma ci provo comunque.
Ah, venendo da Intel comprerei una 570 decente, magari datemi una dritta anche su questo se potete.

Inviato dal mio WAS-LX1A utilizzando Tapatalk

Scheda madre Asus x570 Tuf, cpu, aspetta ancora, tipo Ottobre 2019 se volessi risparmiare qualcosa, ora non mi sembra un buon momento; io farò così!
3600x prenderei io, tutto in auto e ciao, il sogno sarebbe il 3900x ma praticamente 600,00€ con il 3950x in arrivo, insieme alle contro proposte di Intel (ho una CH7 WiFi in attesa di cpu quindi, zero flame)!

[Thricome82]

Ieri sera ho letteralmente inchiodato il PC, dopo aver provato AMD OC dal bios:
-freq 4.2 ghz
-Vcore 1.325v
Ho riavviato e la sequenza di boot si inchioda sul check GPU, ho fatto un clear Cmos, ho tolto la batteria tampone, non ho risolto nulla di nulla, rimane nel limbo e non si avvia più...

[freddye78]

Originariamente inviato da Annamaria

Scheda madre Asus x570 Tuf, cpu, aspetta ancora, tipo Ottobre 2019 se volessi risparmiare qualcosa, ora non mi sembra un buon momento; io farò così!

3600x prenderei io, tutto in auto e ciao, il sogno sarebbe il 3900x ma praticamente 600,00€ con il 3950x in arrivo, insieme alle contro proposte di Intel (ho una CH7 WiFi in attesa di cpu quindi, zero flame)!

Sul sito amd il 3900X è disponibile a 467 spedito

[Annamaria]

Originariamente inviato da Thricome82

Ieri sera ho letteralmente inchiodato il PC, dopo aver provato AMD OC dal bios:
-freq 4.2 ghz
-Vcore 1.325v
Ho riavviato e la sequenza di boot si inchioda sul check GPU, ho fatto un clear Cmos, ho tolto la batteria tampone, non ho risolto nulla di nulla, rimane nel limbo e non si avvia più...

Ho letto di vari problemi con le Gigabyte...
Possibile che tutti si avventurino in overclock fantasiosi.per un guadagno risibile invece di lasciare tutto su auto?
Per quel che serva, se si voglia fare overclock, risparmiare sua scheda madre non è sensato, una Taichi o Crosshair e via!
Spero tu risolva!

[freddye78]

Originariamente inviato da Annamaria

Ho letto di vari problemi con le Gigabyte...

Possibile che tutti si avventurino in overclock fantasiosi.per un guadagno risibile invece di lasciare tutto su auto?

Per quel che serva, se si voglia fare overclock, risparmiare sua scheda madre non è sensato, una Taichi o Crosshair e via!

Spero tu risolva!

Su queste CPU imho non occorre buttare soldi su mobo uber, non salgono più di tanto per scelta del produttore, quindi non ha alcun senso sbattersi per l'OC spinto