Overclock.net banner
Cancel
Create thread New Forums

[Official] Zen 5 Owner's Club (9600X / 9700X / 9900X / 9950X)

5 reading
Jump to Latest
2,021 - 2,040 of 2,522 Posts
#2,021 ·
I see people have vcore running higher than 1.4v but my 9900x never sees it running above 1.4v is that normal?
Even in bios it only shows 1.39v and never touches 1.4v
hwinfo64 reports never exceeds 1.4v
Font Number Screenshot
 
Save
Reply Quote Rep+ Rep+
#2,022 ·
Anhphe93 said:
I see people have vcore running higher than 1.4v but my 9900x never sees it running above 1.4v is that normal?
Even in bios it only shows 1.39v and never touches 1.4v
hwinfo64 reports never exceeds 1.4v
View attachment 2689378
Click to expand...
You need to look at Core EFFECTIVE Clocks under full load
 
Save
Reply Quote Rep+ Rep+
#2,023 ·
Save
Reply Quote Rep+ Rep+
#2,024 ·
Anhphe93 said:
I see people have vcore running higher than 1.4v but my 9900x never sees it running above 1.4v is that normal?
Even in bios it only shows 1.39v and never touches 1.4v
hwinfo64 reports never exceeds 1.4v
View attachment 2689378
Click to expand...
That's correct. My 9950X hits 1.39-1.40 max. Avg sits around 1.26-1.28 if I remember in HWinfo
 
  • Rep+
Reactions: Anhphe93
Save
Reply Quote Rep+ Rep+
#2,025 · (Edited)
Does anyone know what sort of settings can result in hard reboots when memory testing, as opposed to errors, freezes, bluescreens etc.?

I'm testing an 8000MT/s daily stable OC on my 9700x, and it will suddenly hard reboot sometimes after 4 hours of Karhu, sometimes it will pass then reboot 15mins into a new run (without reboot).

In my experience it's usually one of the following:

1. Too high vSOC (probably not an issue at 1.1v)
2. Too low Curve Optimizer offset (currently at 0)
3. Unstable FCLK (mine is 2000MHz)
4. MCR/PDM - tried both enabled and both disabled.

Anyone know of any other settings which can be stable to memory errors but result in hard reboots?

Screenshot Font Number
 
#2,026 ·
RonLazer said:
Does anyone know what sort of settings can result in hard reboots when memory testing, as opposed to errors, freezes, bluescreens etc.?

I'm testing an 8000MT/s daily stable OC on my 9700x, and it will suddenly hard reboot sometimes after 4 hours of Karhu, sometimes it will pass then reboot 15mins into a new run (without reboot).

In my experience it's usually one of the following:

1. Too high vSOC (probably not an issue at 1.1v)
2. Too low Curve Optimizer offset (currently at 0)
3. Unstable FCLK (mine is 2000MHz)
4. MCR/PDM - tried both enabled and both disabled.

Anyone know of any other settings which can be stable to memory errors but result in hard reboots?

View attachment 2689437
Click to expand...
Any errors logged around the time of the reboot?

I would probably look at COs and load-line calibration settings first (revert to the stock 2/3 levels, if needed). Probably don't need to change vSOC, but 1.1v may be too low on some samples.

As far as the memory settings themselves go try increasing DRAMDqDs and ProcCaDs impedance one step while reducing ProcODT and VDDP.

Also, what VDDIO are you using? 1.35v should probably be sufficient here.
 
Save
Reply Quote Rep+ Rep+
#2,027 ·
got the 9600x , to my understanding maximum PPT it can draw is 140-145w which gives me 18900-19000 in cinebench r23 with max temp 76C all cores boost around 5560mhz (on the asus board there is eco mode 105W and 170W but regardless which i select still goes to 140W , only selecting enabled gives it another extra 5W - 145W undecided should i leave it like that or limit it to 120W PPT (manual) which gives me score around 18500 max boost 5480mhz but lower max temps of 67C what do you think guys , post some 9600X cinebench scores
 
#2,029 · (Edited)
RonLazer said:
Does anyone know what sort of settings can result in hard reboots when memory testing, as opposed to errors, freezes, bluescreens etc.?

I'm testing an 8000MT/s daily stable OC on my 9700x, and it will suddenly hard reboot sometimes after 4 hours of Karhu, sometimes it will pass then reboot 15mins into a new run (without reboot).

In my experience it's usually one of the following:

1. Too high vSOC (probably not an issue at 1.1v)
2. Too low Curve Optimizer offset (currently at 0)
3. Unstable FCLK (mine is 2000MHz)
4. MCR/PDM - tried both enabled and both disabled.

Anyone know of any other settings which can be stable to memory errors but result in hard reboots?

View attachment 2689437
Click to expand...
Hi, certainly it your mems setup GearON are doing this, please get rid of it, why don't you start working step by step on GearOFF ?
I explained this too many times already,
you are not stable as y think y are, cause you are using Gear Enable !
Is more than clear, you build your foundation with GDM ON.
GDM Enabled hides issues. Always. Too much. Failure was expected, soon or later coz of that.
Gear ON it's putting a bandaid over it.
But if it was easy GearOFF you would have already found it.
Start removing that GDM and don't pick up the easy give-up route Enableing
Accepting defeat tho GDM Off, won't make your issues go away.
It's not tooo hard. Come on. Please work harder, pure 1T is your route to go, grab your GearOFF stable and your issues will gone 👍
Blue Screenshot Technology Software Number

Font Number Software Screenshot Technology
 
#2,030 ·
Blameless said:
Any errors logged around the time of the reboot?

I would probably look at COs and load-line calibration settings first (revert to the stock 2/3 levels, if needed). Probably don't need to change vSOC, but 1.1v may be too low on some samples.

As far as the memory settings themselves go try increasing DRAMDqDs and ProcCaDs impedance one step while reducing ProcODT and VDDP.

Also, what VDDIO are you using? 1.35v should probably be sufficient here.
Click to expand...
No errors except when rebooting and it says the shutdown was unexpected.

1. Using stock CO and load-line.
2. I did a sweep from 1.0v-1.2v and I found no errors until 1.025v when it would fail immediately when starting the CPU test. I assumed 1.1v was a pretty safe bet therefore.
3. Will try the lower VDDIO, its currently 1.45v.
4. What's the logic behind changing impedances/resistances/VDDP? These control memory bus signal strength, I would assume that memory errors on the bus would be detectable, not trigger a hard reboot?

EDIT: I have a theory that it might be memory temperature related, as pointing a fan at the dimms seems to have helped, will report if it holds up.
 
#2,031 · (Edited)
Tatili said:
certainly it your mems setup GearON are doing this, please get rid of it, why don't you start working step by step on GearOFF ?
Click to expand...
The HDV (which is a ~120 USD six-layer board) is rarely stable with GDM off at 8000+, but can frequently be stabilized up to 8200-8300 with GDM enabled.

RonLazer said:
No errors except when rebooting and it says the shutdown was unexpected.

1. Using stock CO and load-line.
2. I did a sweep from 1.0v-1.2v and I found no errors until 1.025v when it would fail immediately when starting the CPU test. I assumed 1.1v was a pretty safe bet therefore.
3. Will try the lower VDDIO, its currently 1.45v.
4. What's the logic behind changing impedances/resistances/VDDP? These control memory bus signal strength, I would assume that memory errors on the bus would be detectable, not trigger a hard reboot?

EDIT: I have a theory that it might be memory temperature related, as pointing a fan at the dimms seems to have helped, will report if it holds up.
Click to expand...
Most sufficiently severe errors are capable of triggering restarts and suboptimal settings can certainly increase sensitivity to other issues, like high temperatures.

Timings look sufficiently loose to not be the issue and I wouldn't expect the memory to get too hot, but 1.5 vDDP is still pretty high for what you're trying to run.
 
Save
Reply Quote Rep+ Rep+
#2,033 ·
RonLazer said:
It's 1.15v VDDP, and 1.5v VDD.
Click to expand...
Yes, my mistake, that's what I meant.

1.15VDDP and 1.5VDD/1.45VDDQ are all probably a bit excessive and the latter two likely on the warm side without extra airflow.
 
  • Rep+
Reactions: Tatili
Save
Reply Quote Rep+ Rep+
#2,034 ·
  • Rep+
Reactions: mirzet1976
Save
Reply Quote Rep+ Rep+
#2,035 ·
  • Rep+
Reactions: Mr.Sunshine
Save
Reply Quote Rep+ Rep+
#2,038 ·
ASRock B650M-HDV/M.2
New to this board as I just built son new gaming PC. Trying to PBO/CO a 7900X on this board and seems stuck power wise. Max out at 128w PPT and 84A EDC, 73A TDC. Temps are topping out at 84c and 5.5ghz.... Is there a setting I'm missing somewhere? I have a Asrock B650E and a familiar with BIOS on these board. Everything seems correct.
 
Save
Reply Quote Rep+ Rep+
#2,039 ·
Google Macrium Reflect Free, third-party sites still have it.

www.majorgeeks.com

Download Macrium Reflect FREE Edition - MajorGeeks

With Macrium Reflect Free Edition you'll be able to easily make an accurate and reliable image of your HDD or individual partitions. Using this image you can restore the entire disk, partition or...
www.majorgeeks.com

Then use it to make a boot USB, boot from USB, and back up your entire Windows drive to a secondary drive, preferably an M.2, so it's quick.

Then after a corrupt Windows or even just BSODs testing settings, you have an image of your Windows drive, boot partitions and all, to restore.

Plus the image is only the used space on your Windows drive, none of the unused free space, so not the size or your entire drive, and you can efficiently compress the image when you back it up at the cost of some backing up and restore speed.

I swear by it!!
 
  • Love
Reactions: anamolydetected😉
Save
Reply Quote Rep+ Rep+
#2,040 ·
KedarWolf said:
Google Macrium Reflect Free, third-party sites still have it.

www.majorgeeks.com

Download Macrium Reflect FREE Edition - MajorGeeks

With Macrium Reflect Free Edition you'll be able to easily make an accurate and reliable image of your HDD or individual partitions. Using this image you can restore the entire disk, partition or...
www.majorgeeks.com

Then use it to make a boot USB, boot from USB, and back up your entire Windows drive to a secondary drive, preferably an M.2, so it's quick.

Then after a corrupt Windows or even just BSODs testing settings, you have an image of your Windows drive, boot partitions and all, to restore.

Plus the image is only the used space on your Windows drive, none of the unused free space, so not the size or your entire drive, and you can efficiently compress the image when you back it up at the cost of some backing up and restore speed.

I swear by it!!
Click to expand...
It depends how damaged the OS is in the first place. If one can boot into the OS, just run cmd prompt with admin & type chkdsk /r to fix it. I never bother with 3rd party apps to fix windows if a failed OC setting ruins it & besides one can boot from a USB stick with windows installer on it & repair from there as well.
 
2,021 - 2,040 of 2,522 Posts
About this Discussion
2.5K Replies
180 Participants
Last post:
MarkPost
Overclock.net
posts
28M
members
562K
Since
2004
The premier forum for overclocking experts and enthusiasts. Discuss hardware optimization, custom builds, benchmarking, cooling solutions, and pushing the boundaries of computing performance. From beginner guides to extreme overclocking, join our technical community to master system tuning.
Full Forum Listing
Explore Our Forums
Intel CPUs Hardware News NVIDIA PC Gaming Water Cooling