• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

AMD Zen 2 (Ryzen 3000) - *** NO COMPETITOR HINTING ***

HAHAHA I'w found some bugs and fixes for them aka Sound Stuttering.... On new bios Its due to Storport.sys by looks of it im trying 3rd fix no. Not sure why on this bioss it bugs out and jumps to 100ms latency and sound stutters like crazy after 11 minutes lol Passed 10000% ramtest and stress tests and boots up as you seen very good just need to figure out fix for this sound stutter bug. It must be new 1.0.0.3 agesa bug by looks of it cause not had this one before :D
https://www.overclock.net/forum/11-amd-motherboards/1713860-storport-sys-dpc-latency.html
 
So far tested
Full uninstall of Sound drivers from safe mode usingDDU full uninstall of gpu drivers full uninstal off chipset deivers. Installed Samsung NVME driver Again ran system checks ect

@opethdisciple you have some sound stutters ye ?? Well by looks of it You are looking in wrong place mate. As its not CPU or memory related....
 
michty_me said:
Thanks for sharing Zeed. I don't think we would get anywhere without the likes of you sharing your vast knowledge of all this.
Thank you
Click to expand...
I'w spent 4 hours looking for solution and its fixed.
Latency of drivers ect back to normal and even better than before :D
moDkmv8.png

So Generally besides AMD's sata drivers having some problem with nvme and sata on 1.0.0.3 in my case. Noticed taht NV's lates drivers are on high end also.
So started digging as i do.
Two thing that help with driver latency and got mine down as You see
1. Disable nv thelemetry
https://github.com/Sleepydragn1/Disable-Nvidia-Telemetry
2. Got no idea why it works but works its an old laptop nv gpu fix dumps stupid pwoer saving features.
https://nvworld.ru/utilities/pmmanager/

And It;s fixed no sound stuttering ect been playing Wow for hour or so before it was starting very fast like after 4 minutes.

If You having stuttery system check latency and have a look if storport.sys or gpu drivers are not the problem. I can try to et some sleep now. This **** would keep me awake at night if i would not fix it or roll abck to 2501 where this problem is non existant lol
 
ljt said:
Load up Taiphoon

>Click Read (at top)
>Click Read SPD (on any of the list that shows up)
>Click Report (at top)
>Scroll to bottom of report
>Click "show delays in nanoseconds"
>Click Export (at top)
>Click Complete HTML Report
>Save the file

Open DRAM Calculator

>Click Import XMP and choose the file you just saved
> In drop down lists choose the Processor version you want (i.e. Ryzen 2 gen for the 3000 series CPU's), Memory Type you have (i.e. B-die), Memory Rank, Frequency you are wanting to achieve and the amount of DIMMS, and which motherboard chipset you are using.
>Choose either safe or fast preset
>Click Advanced tab and near the bottom left it will tell you your IC quality and what it thinks is the best Frequency you will get
Click to expand...
So I followed this last night just to check out the results.
First thing to note, it didn't calculate the quality of my Micron e-die RAM. In the Advanced tab it simply said n/a for the 3 boxes at the bottom.
Second thing to note, it wouldn't allow me to click Fast whilst using my manually imported profile.

My 3200MHz CL16 sticks are rated for 16-16-18-18-36 and at 3200MHz the calculator states they can do 14-17-17-17-34 as a Safe preset at 1.35V.
I've not manually overclocked RAM before so my first question is: should I alter all of those primary timings in one hit, or one at a time?
I'll only look at secondary timings once the primary timings are stable.
I've also looked at 3600MHz and it calculated something like 16-19-19-19-38. From what I've read and understood, this is likely to perform better than the 3200MHz CL14 settings primarily due to being able to increase the IF clock from 1600MHz to 1800MHz, however it'll need more voltage.
It should be noted that I haven't tried loading up 3600MHz with everything on Auto yet either.
 
Zeed said:
So far tested
Full uninstall of Sound drivers from safe mode usingDDU full uninstall of gpu drivers full uninstal off chipset deivers. Installed Samsung NVME driver Again ran system checks ect

@opethdisciple you have some sound stutters ye ?? Well by looks of it You are looking in wrong place mate. As its not CPU or memory related....
Click to expand...

Of course it is. It's FCLK related. Up to 1800MHz. Lovely jubbly. Over 1800MHz FCLK audio corruption. Others have confirmed they have experienced the same.
 
ChrisD. said:
DDU causes more problems than it fixes. Just do a regular uninstall and only use DDU as an absolute last resort.
Click to expand...
Normally I just reinstall windows DDU i my case is the Easy option. I dont mess about. You forget that my windows i heavly gutted out on registry level.


So I dont know what problems You have I'w been using DDU since it came out.

Now I need to wait for custom modyfied version of this bios With unlocked extra options from mtrai
 
Last edited:
opethdisciple said:
Of course it is. It's FCLK related. Up to 1800MHz. Lovely jubbly. Over 1800MHz FCLK audio corruption. Others have confirmed they have experienced the same.
Click to expand...
well drop screenshot from latencyMon when You are stuttering. Cause even when io drialled back to 3600/1800 still had same problem.


Anyhow new bios got my scores up across the board. No peroblems with mining overnight either.
e6d470c99b2f37228ea0e433eb83dd524890b891.jpeg
 
Those Those 1.0.0.3ABB bioses remind me of ones we had like October when Zen1 came out. They mess around with devices ID and windows reinstalls half o drivers when You flash. That must be reason everyone testing them seem to have problems. Cpu and Memory stability seems great its the system that gets confused when reinstalling drivers. Cant see other reason why Sata drivers ended up with AMD ones that ware not working correctly..

All in all when flashing those Asus ABB bioses I can recommend reinstalling whole windows from point 0 if You dont want to mess around with reinstalling all drivers manually.

AAA and one more thing. If You will flash those bioses Change pcie and M2 generation from AUTO to Gen3. Board tries to run Gen4 that been removed from 1.0.0.3ABB by AMD and some people have problem's when on autom
 
Last edited:
Potatowithearsontheside said:
So I followed this last night just to check out the results.
First thing to note, it didn't calculate the quality of my Micron e-die RAM. In the Advanced tab it simply said n/a for the 3 boxes at the bottom.
Second thing to note, it wouldn't allow me to click Fast whilst using my manually imported profile.

My 3200MHz CL16 sticks are rated for 16-16-18-18-36 and at 3200MHz the calculator states they can do 14-17-17-17-34 as a Safe preset at 1.35V.
I've not manually overclocked RAM before so my first question is: should I alter all of those primary timings in one hit, or one at a time?
I'll only look at secondary timings once the primary timings are stable.
I've also looked at 3600MHz and it calculated something like 16-19-19-19-38. From what I've read and understood, this is likely to perform better than the 3200MHz CL14 settings primarily due to being able to increase the IF clock from 1600MHz to 1800MHz, however it'll need more voltage.
It should be noted that I haven't tried loading up 3600MHz with everything on Auto yet either.
Click to expand...

I get the N/A sometimes in advanced, so I press reset and import again, and before going to the advanced tab i'll click calculate safe/fast and then look and it normally populates the quality field then.

I'd try the safe primaries @ 1.35v first and just run at least a 400% HCI to see if it throws any errors, then work down from there. (don't forget to do about 3 runs of AIDA64 memory before changing anything to get an average of the default XMP so you can compare and see if the bandwidth numbers actually increase and latency decrease) Then repeat after each change, as if the numbers start to drop then you know even before HCI then it isn't stable and is error correcting, hence the lower numbers.

With regards to which will perform better, it all depends, some games prefer bandwidth and some prefer lower latency, so it's finding a happy medium.
 
opethdisciple said:
You're better of doing a clean windows reinstall once you think it's time to reach for DDU.

I cannot think of a single instance when it has a use.
Click to expand...
I have used ddu for years, when flagging my gpu bios and when changing graphics card. Even to remove dodgy chipset drivers before I update it.
Always in safe mode and then a second time after to be sure. It's fixed many problems for me over time
 
Yeah I remember beta testing my 1700 in the CH6.

To be fair on 1.0.0.2 it hasn't been terribly bad although vCore on auto is firing my 3600 at at least 1.52 and no matter if I input my ram voltage at 1.35 it decides 1.41/2 xmp on or off
 
You must log in or register to reply here.
Back
Top Bottom