Gateless Gate Sharp 1.3.8: 30Mh/s (Ethash) on RX 480!

[zawawa]

Thanks, that worked for me

I am going to test your miner again soon, any idea what might be triggering the cpu usage? It is not there at the start, but after 2-3 hours it ends up using 70-80% cpu and the hashrate becomes unstable.

Im using the first version of the adrenaline driver, and I do have bios mods applied though, I have currently not tested the 1.3.7 version, but the issue is not on my test machine which only has 4 cards, that is perfectly stable, the issues appears only on my machines with 6 or more cards.

I would say, just don't use v1.3.2. v1.3.7 is so much better and lighter IMHO.

[1713509693]

1713509693

[1713509693]

1713509693

[1713509693]

1713509693

[UnclWish]

Let's see if I can beat LLVM and AMD display drivers with this "bomb"...

It's cool!!!
But be carefull - I woudn't want to matrix has you ))))

A day ago you wanted to test hynix mjr memory... What's you results?

[Littlegrand]

I am getting all rejected shares mining haven cryptonight heavy saying wrong algo.  I noticed in the log there is this: Switching to Monero Version 2.  Did I do something wrong?

Thanks
--J

[UnclWish]

I am getting all rejected shares mining haven cryptonight heavy saying wrong algo.  I noticed in the log there is this: Switching to Monero Version 2.  Did I do something wrong?

Thanks
--J

Check is you right choosen pool and port.

[Littlegrand]

It is all right. The log shows cryptonight heave loaded, the share submitted to the correct url, just rejected wrong algo...

[UnclWish]

It is all right. The log shows cryptonight heave loaded, the share submitted to the correct url, just rejected wrong algo...

Correct url didn't means that you select correct url for cryptonight heavy algo.
Most pools have several ports for different algos. If you chose port for cryptonightv7 but in miner you select CN heavy algo, miner will connect to pool via seleted port, and pool allows to connect, but miner will finds shares for heavy and send them on pool to port from wich pool wait shares for cryptonightV7, due to port.
Check port number for your pool. Is you right pointed it for CN heavy.

[FFI2013]

Ok Im going nuts I install 18.3.4 drivers and tries GGS 1.36 and 1.37 and cannot get any of my r9 cards to run 270,280 and 390's Im on win 10 I tried mph ethash but it wont connect I have to use a different port than ETH because of the dag the log keeps saying something about the key also I tried cn7 and my hashrates either suck or when I use default settings it crashes could someone give me a good settings on xmr for theses older cards Thanks
Also I no its not GGS its the fact Im using older cards on this rig
edit: I also tried stock clocks and OC I wonder if I need to reinstall win for some reason when you use claymore miners than switch to a different miner you get nothing but problems this always happened to me on win7  

I heard a rumor that Claymore's miners rewrite display drivers for stability.
I didn't confirm that rumor myself, but it makes a perfect sense. I was at least pretty certain that they use exploits in Windows to gain administrative privileges. (I don't think it's a coincidence antivirus software marks his miners as threats.)

These are all speculations and I might be completely wrong. That is why I prefer open-source
projects over closed-source ones, although I take a substantial financial hit that way. Just my two cents.

Thanks I believe this is the problem I can use any claymore miner without a problem as soon as I try any other miner I have problems or crashes even when I run DDU I think a fresh install of win 10 is the way to go Im going to try and see whats happens

[UnclWish]

Ok Im going nuts I install 18.3.4 drivers and tries GGS 1.36 and 1.37 and cannot get any of my r9 cards to run 270,280 and 390's Im on win 10 I tried mph ethash but it wont connect I have to use a different port than ETH because of the dag the log keeps saying something about the key also I tried cn7 and my hashrates either suck or when I use default settings it crashes could someone give me a good settings on xmr for theses older cards Thanks
Also I no its not GGS its the fact Im using older cards on this rig
edit: I also tried stock clocks and OC I wonder if I need to reinstall win for some reason when you use claymore miners than switch to a different miner you get nothing but problems this always happened to me on win7  

I heard a rumor that Claymore's miners rewrite display drivers for stability.
I didn't confirm that rumor myself, but it makes a perfect sense. I was at least pretty certain that they use exploits in Windows to gain administrative privileges. (I don't think it's a coincidence antivirus software marks his miners as threats.)

These are all speculations and I might be completely wrong. That is why I prefer open-source
projects over closed-source ones, although I take a substantial financial hit that way. Just my two cents.

Thanks I believe this is the problem I can use any claymore miner without a problem as soon as I try any other miner I have problems or crashes even when I run DDU I think a fresh install of win 10 is the way to go Im going to try and see whats happens

I think that it's only rumors about Claymore's rewtining drivers...
More trully as I heard that Claymore have access to Microsoft development. His miners didn't rewrite any Windows drivers (at least on Windows 10) because it not so easy to change driver that's work at this moment without reinstalling it. And don't forget about digital signing of drivers...
But his miners can do things that other miners can't. I think that Claymore knows significant more about drivers on Windows and how them works. He maked his miners with low access to GPU maybe without driver at all if it possible... Maybe he worked for MS earler or something like this.
For me any other miner normal works after launching his miners. And even more - I often use his miners for setting overclock, fans, etc. It's very usefull that his miners leave HW changes in GPU work after closing miner.

zawawa, maybe you make this option too? To leave OC and fan settings changed after closing GGS? And return please "Release memory" button, I used it often...

[zawawa]

Not bad, not bad... This is just a beginning.

[zawawa]

More trully as I heard that Claymore have access to Microsoft development. His miners didn't rewrite any Windows drivers (at least on Windows 10) because it not so easy to change driver that's work at this moment without reinstalling it. And don't forget about digital signing of drivers...

Well, that's exactly what PhyMem does. Are you impressed now?  

[zawawa]

"Release memory" button, I used it often...

Use "Relaunch" instead. I got rid of it because it was redundant.

[zawawa]

Let's turn up the parameters of the new code analyzer/optimizer and see what's going to happen.
This is so much fun!

[UnclWish]

More trully as I heard that Claymore have access to Microsoft development. His miners didn't rewrite any Windows drivers (at least on Windows 10) because it not so easy to change driver that's work at this moment without reinstalling it. And don't forget about digital signing of drivers...

Well, that's exactly what PhyMem does. Are you impressed now?  

As I reads, Phymem didn't change driver, it's just access GPU bypassing the driver... But I can be wrong, of course.

"Release memory" button, I used it often...

Use "Relaunch" instead. I got rid of it because it was redundant.

Oh, every time when change something relaunch GGS? it's annoying.... Just return this button, don't be such a nasty man.

[zawawa]

More trully as I heard that Claymore have access to Microsoft development. His miners didn't rewrite any Windows drivers (at least on Windows 10) because it not so easy to change driver that's work at this moment without reinstalling it. And don't forget about digital signing of drivers...

Well, that's exactly what PhyMem does. Are you impressed now?  

As I reads, Phymem didn't change driver, it's just access GPU bypassing the driver... But I can be wrong, of course.

Well, it can do a lot of wild things, you know...

[zawawa]

Code optimization takes so much time! Then again, I heard a developper of John the Ripper the password
cracker spent months optimizing his S-Boxes for Bitslice-DES with a water-cooled PC to set a world record.
I guess waiting for an hour or so shouldn't be that bad...

[UnclWish]

Code optimization takes so much time! Then again, I heard a developper of John the Ripper the password
cracker spent months optimizing his S-Boxes for Bitslice-DES with a water-cooled PC to set a world record.
I guess waiting for an hour or so shouldn't be that bad...

Of course, you're absolutly right!

[zawawa]

I just found something pretty interesting online.
After all, it seems that memory timing mods are possible with NVIDIA, too.
Good stuff.

[UnclWish]

Sorry for offtopic... But my W10 1709 updates to 1803. And now AtiFlash 2.77 didn't run... Anyone knows what to do?

[rednoW]

You'll better find the way to tweak mem timings for Vega.
For nvidia there is a solution already - OhGodETHEnlargement.

For polaris your program is a piece of ... well ... I just don't like it.
I tested it yesterday with my fresh computer with new rx570 8gb sapphire nitro+ micron memory. 18.3.4 drivers. Original bios.
First of all from the start your program screwed up my downvolt settings (made by overdriventool) and fired it up mining with huge voltage.
Than I tried to tweak (downvolt, timings) using your program only.
And it gets bsods "thread stuck in device driver" every try
I had no time to struggle with your buggy undocumented software. I've just flashed good timings, applied 850mv and went mining SUMO with 1khs@80watt with doctor's SRBminer ...

[UnclWish]

Strange... Windows 10 1803 - GGS identified my RX 580 as R200 GPU's. Very nice...
Installed back 18.3.4. - all return to normal...