Not sure I understand the reference to the file c:\windows\system32\drivers\AmdGpuTweak.sys on GitHub. Where is this file and is it required?
Well, you have the path right there, "c:\windows\system32\drivers" if it's not there, good, launch the tool, should be fine. how close test mode?
every reset win go in test mode.
c:\windows\system32\drivers\AmdGpuTweak.sys not exist
Latest XL version has a button to turn it off. Otherwise run the command posted here above. (bcdedit) I always get a "NullReferenceException" window asking me to activate the test mode. I allow it, then reboot. My system is then running in test mode (indicated on the bottom right of the windows desktop). But when I launch the AMD.Memory.Tweak.XL, I get the same "NullReferenceException" window.
How can I solve this please ?
Check my quote here, remove the old driver from drivers folder in system32, then get the latest version and launch it. I gotta say, this tool is cool as hell.
Although, I'm having some trouble with it. Probably because I'm a noob.
I went ahead and downloaded it and installed it, manually with the terminal, running HiveOS, the VEGA supported version.
I'm running 6x 1070s, 1x 1070ti, and 4x Vega 64s.
The trouble I'm having is HiveOS kinda sucks at overclocking when it comes to AMD. Claymore isn't doing the job either; and my Linux illiteracy and lack of Google returns isn't helping.
I love how you can modify the hell out of the stuff with this tool, but I can't seem to get the GUI working so I can modify the DPM/Memstates (which, honestly, is all I'm tryna do). Is there a way to get the GUI working in HiveOS that I just don't know about? Or a command line? Or do I just suck at life?
GUI is Windows only mate. Cheers |
|
|
|
Wow been a while since I've seen a new version of Claymore coming out. Looks like V15.0 has been released for over about a day and only about 20 posts followed the launch. This is actually pretty low compared to the good old days of 2017 where whenever Claymore released a new version usually about 5-10 pages would happened in the following hours after the launch. His ZEC miner was also pretty popular during those days.
Its sad to see GPU mining going downhill where many people have moved onto something else. Really hoping that ETH devs do something and get ProgPOW added to the Q1 2020 fork and we might see a comeback of miners.
But right now in my area, I am getting barely a quarter a day of net profit with a single GPU. Sure wish the days of $1/day/GPU would come back.
ProgPow is not going to solve that. On the contrary. The algorithm is designed to make it easier for FPGA's to join the game. I hope i'm wrong. |
|
|
|
Added Navi10 support to AMD Mem Tweak XL would be nice if you guys tested a bit. LinkCheers! |
|
|
|
With the new XL version, I can only occasionally update the the values on the fly. Most often not. The added tools are nice to have though. My system always fails to read the injected strap ... pops and error dialog box to that effect.
I still regret moving to Win10 1903 as I think that's what took away my ability to modify things real-time, while Claymore is running.
You probably need an option or button to revert out of test mode. Obviously, you can flip into test mode if you don't detect it running but then there's no automated way back out in the XL Win tool.
Edit:
bcdedit /set TESTSIGNING OFF
just in case someone was looking for it.
I've tried to recreate your problem with the straps not injecting .. Just to be clear here, you can only inject a strap at the selected frequency. So if you're currently running your memory at 1900 Mh and you do a modification/strap injection for freq 2000, you're not going to notice any differences. However, that doesn't mean that you should get those error messages. It's the driver that fails to inject the strap. Probably something to do with Claymore's driver Button to turn test mode off has been added to latest release As well as NAVI10 support  Only Strap injection and Power Play support (read from vbios/registry and write to registry for now) Latest versionCheers! |
|
|
|
1. I hope that you will aquire a signed certificate and sign driver....
2. This is what I doing now ))) But want to use XL version in future without test mode.
Anyway, great work! Thank you!
We'll, see, maybe some good samaritan will offer to solve that  Anyhow, just published a new release which fixes the startup bug. HereCheers! |
|
|
|
Hello  Would it be possible to convert the current settings back to a timing strap? (so we can put it inside a bios file and make it permanent) It could be even just a location reference, like "tREF is located in the x-th byte inside the timing strap". Btw, really a nice app I'm tweaking the hell out of my GPU. Yes, i've implemented this into the Extended XL version. Check OP for more info Link: HereCheers! It's very good! Only two questions: 1. Did you plan to sign your custom driver to run tool in usual not test mode? 2. Can you make use of tool in nontest mode with use driver IOMap for only changing timining like in non XL version? 1. I'd need a signed certificate for that. Not expensive, not "that" easy to aquire. 2. Can't you just use Non xl version then? Cheers |
|
|
|
Hello Would it be possible to convert the current settings back to a timing strap? (so we can put it inside a bios file and make it permanent) It could be even just a location reference, like "tREF is located in the x-th byte inside the timing strap". Btw, really a nice app I'm tweaking the hell out of my GPU. Yes, i've implemented this into the Extended XL version.  Check OP for more info Link: HereCheers! |
|
|
|
Hah. I'd rather have you release them than your good friend Ohgoda*****. After all, I'm sure she'd be all over them and dying to claim them as her work...
Well, i made the decision a long time ago to never ever release this for several reasons that are absolutely not important But i don't mind annoying you guys with some screenshots   well done, but i have problem to running cli version, the error message was " C:\Users\3\Desktop\amdo>WinAMDTweak.exe --current
Failed to load EIO.dll"how to fix it, thanks you need to have the two dll's in the same directory as the amdtweak tool and that will resolve that. they are built in the download. I have done that I had the same thing happen with the newest release. The previous version works fine for me. Redownload the binary from releases. It'll work fine now |
|
|
|
Hah. I'd rather have you release them than your good friend Ohgoda*****. After all, I'm sure she'd be all over them and dying to claim them as her work...
Well, i made the decision a long time ago to never ever release this for several reasons that are absolutely not important But i don't mind annoying you guys with some screenshots |
|
|
|
So i just released both windows and linux cli with a ton of timings exposed. Be aware, i exposed them, i made em almost all writable but that does not mean that you should write to them ;-) Getting BSOD's is a great learning curve Please also check comments in the code..... Just so you know, you can yet again improve speed on Polaris  that's all i'm saying. Hope there'll be some juicy way to tweak GDDR6 timings on RTX cards... I'm not going to release Nvidia mem tweak, so don't count on it Cheers |
|
|
|
Thank you Eliovp for the info. I only tried raising the REF from 5 to 9 and got a 1.178 increase from my MSI Rx580 G8 Hynix and a 0.739 increase from my XFX RX580 G8 Samsung memory. I'll play with the RFC after I now the 2 card types are stable. Update: I raised my REF to 10 for the last 12 hours and has been stable. Original 27.803 to 29.313, a 5.43% increase and Original 24.852 to 25.854, 4.03% increase. Thanks again Eliovp for the info! RFC is next for both cards after another 12 hours.
You're welcome. It's not there, Refresh Rate is a completely different register and is not a part of the vbios Strap. I'll be releasing a new CLI version soon with almost all timings exposed. Some things that no one has seen before (or almost no one) GUI version i will update when i find a bit more time (with some juicy stuff :p) Cheers! |
|
|
|
Didn't you miss my post? Loading fan speeds for Polaris cards from saved profile seems to be broken in beta 5.
No sir, i didn't, check releases ;-) Thank you very much! Sure thing! @Eliovp
Would you possibly have looked at offering a similar tool for nVidia RTX GPUs with GDDR6?
Afaik the Ethlargement tool only works on GDDR5X cards...
Nvidia made RTX regs read-only. There might be a way around it, who knows |
|
|
|
Didn't you miss my post? Loading fan speeds for Polaris cards from saved profile seems to be broken in beta 5.
No sir, i didn't, check releases ;-) Could GUI version running and apply at startup ?
Because it did not change anything yet if run at start up, so must apply it manually
CLi version only change REF, rfc and others not chamge
Just test it with Polaris, that did not work Just tested it on Polaris as well, works fine Cheers! |
|
|
|
Finally got 33 mh/s with RX470 - with rxboost
I have some rx470's Samsung, Elpida and Hynix, using rxboost my rigs are crashing what driver are you using and are your cards bios modded or stock? I use bios modded straps, not the freaky on the fly, looks like some of the gpus already bricked with this when i go back some pages here. Elpida and hynix the same, 32.7 to 32.9mh/s with rxboost and phoenixminer. what rxboost are you combining here? the rxboost is on Clay or what am I missing? No i use the rxboost tool for linux from simplemining os, best you switch to simpleminingOS run your own straps and run with phoenixminer... for rx400/500 You can use Amd Memory Tweak and use "REF" flag, it's the same thing, free to use Cheers! |
|
|
|
@Eliovp - a couple bugs/issues to report (latest version, linux, gddr5):
1. setting --RAS reports as having set --PA2RDATA. Looks like maybe just a display issue tho, as --current then reports RAS as having been set properly
2. setting --RC is also applying the value to CL - and since setting CL doesn't work (prevents card from being initialized by miner, reboot required) effectively RC cannot be set
3. you might be missing some bits for RC (or it's just incorrectly mapped to CL)? strap says 65, but it reads same values as CL, and if i set > 31, i get an overflow (e.g. setting 32 results in 0).
EDIT: Btw - any hints why DRAM1/2 values change under load, even when the core/mem state haven't changed?
I'm going to check this tomorrow, did everything in a rush without even testing Should clean a bit up because it's becoming a mess. Already saw some issues going over the code. And Laik2 pointed out that some bits are wrong, he's right (PMG for example.. 3-1-3-1-4-6-3..) (See that Laik2, i'm not too "Godlike" to acknowledge my mistakes) I'll see to add some extra timings that i didn't yet expose, will expose HBM2 Memory Manufacturer as well. Anyhow, when i wake up i'll take some more time to test and clean up code because after adding hbm1 it's a total mess. Cheers! Fixed the bitfield bugs, cleaned a bit up, added a few things. More detailsOnly done so on linux version, will update the rest asap as well. Direct link to linux cli binary: hereGreetings |
|
|
|
@Eliovp - a couple bugs/issues to report (latest version, linux, gddr5):
1. setting --RAS reports as having set --PA2RDATA. Looks like maybe just a display issue tho, as --current then reports RAS as having been set properly
2. setting --RC is also applying the value to CL - and since setting CL doesn't work (prevents card from being initialized by miner, reboot required) effectively RC cannot be set
3. you might be missing some bits for RC (or it's just incorrectly mapped to CL)? strap says 65, but it reads same values as CL, and if i set > 31, i get an overflow (e.g. setting 32 results in 0).
EDIT: Btw - any hints why DRAM1/2 values change under load, even when the core/mem state haven't changed?
I'm going to check this tomorrow, did everything in a rush without even testing Should clean a bit up because it's becoming a mess. Already saw some issues going over the code. And Laik2 pointed out that some bits are wrong, he's right (PMG for example.. 3-1-3-1-4-6-3..) (See that Laik2, i'm not too "Godlike" to acknowledge my mistakes) I'll see to add some extra timings that i didn't yet expose, will expose HBM2 Memory Manufacturer as well. Anyhow, when i wake up i'll take some more time to test and clean up code because after adding hbm1 it's a total mess. Cheers! |
|
|
|
Built the latest linux version from github but get the following error message Cannot find DRI instance for pci:0000:01:00.0
Same message regardless of what I pass with --i , e.g. root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 0 --current
Cannot find DRI instance for pci:0000:01:00.0
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 1 --current
Cannot find DRI instance for pci:0000:01:00.0
root@minivega:/home/miner/scratch/amdmemorytweak/linux# ./amdmemtweak --i 2 --current
Cannot find DRI instance for pci:0000:01:00.0
System details: root@minivega:/dev/dri# uname -a
Linux minivega 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@minivega:/dev/dri# apt list --installed | grep amdgpu-pro
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
amdgpu-pro-core/unknown,now 18.10-572953 all [installed,automatic]
clinfo-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed]
libopencl1-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed,automatic]
opencl-amdgpu-pro/unknown,now 18.10-572953 amd64 [installed]
opencl-amdgpu-pro-icd/unknown,now 18.10-572953 amd64 [installed,automatic]
opencl-orca-amdgpu-pro-icd/unknown,now 18.10-572953 amd64 [installed]
Anyone else got the same problem, or do I need to update amdgpu-pro? I just pushed a new CLI version both for windows and Linux, can you please try that one. (there's a pre-built one in releases) Cheers |
|
|
|
Spamming? I just checked out your posts, spamming several threads with useless info. I know you're pissed off at me Ddobbrev, fishing for info on skype for god knows how long and when i released Amd Mem tweak open source, getting all mad at me Again, it's ok, i released it open source so that people use it or the idea behind it, that was to expect. Cheers! Also our binary is from 20 may 2019 while you just released yours. So it is 1 day after our release. I would not scream on your place Eliovp ... My idea could be that someone just took idea from our binary ... But i do not have time for this. I am glad that people will get better speed. All good mate, no worries! Editing this post because i don't want to keep "spamming" this thread @Dobromir Dobrev (aka Laik2) Well, if you're calling yourself smart, because that's what you just did and comparing me with ogac, i guess i just wasted a lot of keystrokes then And by all means, go ahead mate, share whatever you want. |
|
|
|
Please post your results BEFORE and AFTER using rxboost tool Show some pictures You really should credit Eliovp for allowing you to be able to do this. Got to give credit where credit is due. Yeah well . ... doesn't surprise me :p Here, for the people on Windows --> LinkWill upload CLI version for Linux users asap as well amdmemorytweak has nothing to do with this rxboot tool. rxboost tool can be used as long with amdmemorytweak under linux It does something that amdmemorytweak does not do. I can increase speed even on heavily modded bioses and also on not modded. I cannot give credit to someone who is not involved at all in rxboost tool. It has nothing to do with him. Also i cannot tell who made this tool either. Anyway there is not any similar tool in linux which would be doing what that tool does. So you're saying that it's a coincidence that when you activate "rxboost" that it raises refresh rate? If you go check out my tool, it's there as well, i created a separate textbox to make it easy, and guess what, it also works with a modded vbios (like it always did :p) But doesn't matter mate. I'm glad for you Stop spamming and playing Godlike. Its not always you and its not a coincidence. Spamming? I just checked out your posts, spamming several threads with useless info. I know you're pissed off at me Ddobbrev, fishing for info on skype for god knows how long and when i released Amd Mem tweak open source, getting all mad at me Again, it's ok, i released it open source so that people use it or the idea behind it, this was to expect. Cheers! |
|
|
|
Please post your results BEFORE and AFTER using rxboost tool Show some pictures You really should credit Eliovp for allowing you to be able to do this. Got to give credit where credit is due. Yeah well . ... doesn't surprise me :p Here, for the people on Windows --> LinkWill upload CLI version for Linux users asap as well amdmemorytweak has nothing to do with this rxboot tool. rxboost tool can be used as long with amdmemorytweak under linux It does something that amdmemorytweak does not do. I can increase speed even on heavily modded bioses and also on not modded. I cannot give credit to someone who is not involved at all in rxboost tool. It has nothing to do with him. Also i cannot tell who made this tool either. Anyway there is not any similar tool in linux which would be doing what that tool does. So you're saying that it's a coincidence that when you activate "rxboost" that it raises refresh rate? If you go check out my tool, it's there as well, i created a separate textbox to make it easy, and guess what, it also works with a modded vbios (like it always did :p) But doesn't matter mate. I'm glad for you |
|
|
|
|
Show Posts
