Topic: Claymore&#039;s Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1347. (Read 6590757 times)

Quote from: melloyellow on April 29, 2016, 12:37:10 AM

Quote from: kanoptx on April 29, 2016, 04:47:12 AM

Could you have by accident installed 32bit windows? I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

I can confirm it is indeed x64 via the Control Panel's basic system information. I have the same distro installed on two other rigs, one of which is an Intel Bad Axe 2 seating 1 390x, 1 290x & 1 290 w/ 2 x 1 GB + 2 x 2GB where all 6GB are properly allocated and the other from vague recollection is an Asus P5b also on socket 775 with 2 x 2GB where only 3.25GB is usable as indicated in the motherboard's manual.

fo00ok

I have a very similar PC - s.775, 4GB RAm, Win7, 3.25GB recognized with latest bios and 290 inside.
It works flawlessly with Virtual memory set to static 16GB size and all Genoil/Claymore versions

froilan_rivero

newbie

Activity: 25

Merit: 0

What's the point of the NO DAG FILES ANYMORE?

I mean will it work for 1GB-2GB VRAM cards? will it be stored on normal RAM or Hard drive?

Pleae excuse the ignorance

merc84

hero member

Activity: 799

Merit: 1000

Quote from: kanoptx on April 28, 2016, 08:17:22 PM

I've been getting around 2000mh. which according to this calculator: http://decred-calc.cryptohub.info/ should give me about 1.40 dcr. i'm getting around 1.10. is this normal? is it something to do with dual mining? i've changed to supernova, and same thing... is it the calculator? thx

is no one else having this problem? sorry to be pushy, but it rly sucks :\. ethereum payout seems to be correct. i've tried 2 pools supernova and coinmine. same results with both. less than it should be

Mining calculators are only a rough guide .3 dcr is nothing to lose sleep over.

freeapp

member

Activity: 137

Merit: 10

Quote from: kanoptx on April 29, 2016, 04:47:12 AM

Quote from: kanoptx on April 28, 2016, 08:17:22 PM

I've been getting around 2000mh. which according to this calculator: http://decred-calc.cryptohub.info/ should give me about 1.40 dcr. i'm getting around 1.10. is this normal? is it something to do with dual mining? i've changed to supernova, and same thing... is it the calculator? thx

is no one else having this problem? sorry to be pushy, but it rly sucks :\. ethereum payout seems to be correct. i've tried 2 pools supernova and coinmine. same results with both. less than it should be

Hi,
sounds ok.
because of up/down of diff because all the dual miner comes from eth only to dcr also...

one week ago you would get with 2gh/s about 2dcr a day...

EDIT:
try also http://www.whattomine.com/

kanoptx

sr. member

Activity: 406

Merit: 250

www.cryptocompare.com

Quote from: kanoptx on April 28, 2016, 08:17:22 PM

I've been getting around 2000mh. which according to this calculator: http://decred-calc.cryptohub.info/ should give me about 1.40 dcr. i'm getting around 1.10. is this normal? is it something to do with dual mining? i've changed to supernova, and same thing... is it the calculator? thx

is no one else having this problem? sorry to be pushy, but it rly sucks :\. ethereum payout seems to be correct. i've tried 2 pools supernova and coinmine. same results with both. less than it should be

dpcoinz

newbie

Activity: 24

Merit: 0

Has anyone gotten the dual miner to work with miningrigrentals.com ? I can't seem to figure out a combination that will work with it.

dp

Hoang152

newbie

Activity: 33

Merit: 0

DCR works but speed too slow Huh

Zitdadast

sr. member

Activity: 312

Merit: 250

LTC fan 4ever

Quote from: adaseb on April 29, 2016, 03:59:09 AM

I built a new rig with only 2GB of ram and it wouldn't start anyways, just wondering what the point of the DAG loading only on GPU is ?

If the DAG is stored in the hard disk, it might be corrupted by certain operations. That is the reason for the on card DAG.

o00o

member

Activity: 93

Merit: 11

Quote from: melloyellow on April 29, 2016, 01:50:02 AM

Quote from: melloyellow on April 29, 2016, 12:37:10 AM

Quote from: mineromineroso on April 29, 2016, 03:37:04 AM

Could you have by accident installed 32bit windows? I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

I can confirm it is indeed x64 via the Control Panel's basic system information. I have the same distro installed on two other rigs, one of which is an Intel Bad Axe 2 seating 1 390x, 1 290x & 1 290 w/ 2 x 1 GB + 2 x 2GB where all 6GB are properly allocated and the other from vague recollection is an Asus P5b also on socket 775 with 2 x 2GB where only 3.25GB is usable as indicated in the motherboard's manual.

fo00ok

Could you humor me for a sec and run cpu-z to see what kind of processor you're running? Just a quick search on the pentium d and there are conflicting answers that some pentium d's are only 32 bit capable. (also the p5b should be able to handle 8gb of ram) You can install a 64 bit OS on a 32bit only processor. I've done it on accident, I put W7 x64 on my dell mini 9 and it worked for what I needed it to do. If your processor is 32bit that would answer the 2 problems, 3.25gb of available ram and not being able to run this 64bit miner.

I'll get back to you as soon as I can. I run multiple 64-bit applications on this sytem and like I have said many times now, if this would truly be the issue, I would have never been able to use it in the first place.

Quote from: melloyellow on April 29, 2016, 01:50:02 AM

Quote from: melloyellow on April 29, 2016, 12:37:10 AM

Quote from: adaseb on April 29, 2016, 03:59:09 AM

Could you have by accident installed 32bit windows? I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

I can confirm it is indeed x64 via the Control Panel's basic system information. I have the same distro installed on two other rigs, one of which is an Intel Bad Axe 2 seating 1 390x, 1 290x & 1 290 w/ 2 x 1 GB + 2 x 2GB where all 6GB are properly allocated and the other from vague recollection is an Asus P5b also on socket 775 with 2 x 2GB where only 3.25GB is usable as indicated in the motherboard's manual.

fo00ok

Could you humor me for a sec and run cpu-z to see what kind of processor you're running? Just a quick search on the pentium d and there are conflicting answers that some pentium d's are only 32 bit capable. (also the p5b should be able to handle 8gb of ram) You can install a 64 bit OS on a 32bit only processor. I've done it on accident, I put W7 x64 on my dell mini 9 and it worked for what I needed it to do. If your processor is 32bit that would answer the 2 problems, 3.25gb of available ram and not being able to run this 64bit miner.

Some intel chipsets from 775 era show less ram if you install more pci devices like more graphics cards. Try to boot only with one graphics card and see if it's only 3.25gb or 3.66, 3.75...

The 290x is the only GPU present in this system.

I built a new rig with only 2GB of ram and it wouldn't start anyways, just wondering what the point of the DAG loading only on GPU is ?

adaseb

legendary

Activity: 3808

Merit: 1723

I built a new rig with only 2GB of ram and it wouldn't start anyways, just wondering what the point of the DAG loading only on GPU is ?

mineromineroso

newbie

Activity: 33

Merit: 0

Quote from: melloyellow on April 29, 2016, 01:50:02 AM

Quote from: melloyellow on April 29, 2016, 12:37:10 AM

Could you have by accident installed 32bit windows? I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

I can confirm it is indeed x64 via the Control Panel's basic system information. I have the same distro installed on two other rigs, one of which is an Intel Bad Axe 2 seating 1 390x, 1 290x & 1 290 w/ 2 x 1 GB + 2 x 2GB where all 6GB are properly allocated and the other from vague recollection is an Asus P5b also on socket 775 with 2 x 2GB where only 3.25GB is usable as indicated in the motherboard's manual.

fo00ok

Could you humor me for a sec and run cpu-z to see what kind of processor you're running? Just a quick search on the pentium d and there are conflicting answers that some pentium d's are only 32 bit capable. (also the p5b should be able to handle 8gb of ram) You can install a 64 bit OS on a 32bit only processor. I've done it on accident, I put W7 x64 on my dell mini 9 and it worked for what I needed it to do. If your processor is 32bit that would answer the 2 problems, 3.25gb of available ram and not being able to run this 64bit miner.

Some intel chipsets from 775 era show less ram if you install more pci devices like more graphics cards. Try to boot only with one graphics card and see if it's only 3.25gb or 3.66, 3.75...

melloyellow

full member

Activity: 176

Merit: 100

Quote from: melloyellow on April 29, 2016, 12:37:10 AM

Quote from: sp_ on April 29, 2016, 01:13:43 AM

Could you have by accident installed 32bit windows? I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

I can confirm it is indeed x64 via the Control Panel's basic system information. I have the same distro installed on two other rigs, one of which is an Intel Bad Axe 2 seating 1 390x, 1 290x & 1 290 w/ 2 x 1 GB + 2 x 2GB where all 6GB are properly allocated and the other from vague recollection is an Asus P5b also on socket 775 with 2 x 2GB where only 3.25GB is usable as indicated in the motherboard's manual.

fo00ok

Could you humor me for a sec and run cpu-z to see what kind of processor you're running? Just a quick search on the pentium d and there are conflicting answers that some pentium d's are only 32 bit capable. (also the p5b should be able to handle 8gb of ram) You can install a 64 bit OS on a 32bit only processor. I've done it on accident, I put W7 x64 on my dell mini 9 and it worked for what I needed it to do. If your processor is 32bit that would answer the 2 problems, 3.25gb of available ram and not being able to run this 64bit miner.

o00o

member

Activity: 93

Merit: 11

try to locate an option called

render standby
deep render standby

in the bios and disable them both. Also disable the internal graphics.

I'll most certainly take another look at the bios precisely for render standby & deep render standby. There is no option to disable internal graphics or anything else for that matter as the bios is very basic. I also assumed that could have accounted for the 768MB which I cannot allocate to the oS but I do have PEG highlighted which should also disable internal graphics if selected.

Thanks for your advice!

Ale-x

newbie

Activity: 36

Merit: 0

Have tried v4.0 - very good! Hashrate is the same v3.2 or v3.3, maybe even more.
R9 270 ~ 14Mh/s
7950 ~ 18,5 - 19,5Mh/s depends on model
R9 280x ~ 21Mh/s

But have experience with one issue - can't set -cclock or -mclock values - the miner crashes. AMD Driver 15.12, 4 Gb RAM, 16GB swapfile, 5x R9 270 2 Gb. I would attach screenshots but I have localized version of Windows 7 x64. In logfile is no usefull info.

sp_

legendary

Activity: 2954

Merit: 1087

Team Black developer

try to locate an option called

render standby
deep render standby

in the bios and disable them both. Also disable the internal graphics.

o00o

member

Activity: 93

Merit: 11

Quote from: melloyellow on April 29, 2016, 12:37:10 AM

Could you have by accident installed 32bit windows? I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

I can confirm it is indeed x64 via the Control Panel's basic system information. I have the same distro installed on two other rigs, one of which is an Intel Bad Axe 2 seating 1 390x, 1 290x & 1 290 w/ 2 x 1 GB + 2 x 2GB where all 6GB are properly allocated and the other from vague recollection is an Asus P5b also on socket 775 with 2 x 2GB where only 3.25GB is usable as indicated in the motherboard's manual.

fo00ok

melloyellow

full member

Activity: 176

Merit: 100

Quote from: restless on April 29, 2016, 12:04:42 AM

Could you have by accident installed 32bit windows? I know you said it's x64 but it sounds like you're pressing that 4gb limit (~3.25gb addressable)

o00o

member

Activity: 93

Merit: 11

Quote from: o00o on April 28, 2016, 07:18:36 PM

I'm guessing my memory controller hub can only allocate up to 3.25GB of memory. I inspected the motherboard's bios in hopes of finding an option which would allow me to remove RAM reserved for GPU but none was available.

I exhausted every possible solution which crossed my mind.

Why not using v4.0 ?

It unfortunately does not resolve the issue.

Quote from: kirilvvbg on April 29, 2016, 12:09:38 AM

Quote from: Claymore on April 28, 2016, 06:51:45 PM

Quote from: Claymore on April 28, 2016, 05:39:45 PM

Quote from: kirilvvbg on April 29, 2016, 12:12:51 AM

@ Claymore

I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer. I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem. Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem. I also tried renaming the dag files successfully created by QTminer in hopes of using them with yours but that also didn't work. My other rig is also Hawaii-based and surprisingly doesn't suffer from this symptom. I just gave v4.0 a try but it still introduces the same error.

Any feedback would be much appreciated!

v3.3 takes may be 10-20 more GPU memory, that's the only difference between previous versions. You even did not mention what cards are used, how much RAM etc.

I'm clueless as to why all versions excluding v1.2 fail to create a big buffer despite the fact that they were previously working prior to updating to v3.3. I did mention that the rig in question is seated with a Hawaii-based GPU, more precisely a reference Sapphire 290x operating on Windows 7 x64, Intel Pentium D w/ 2 x 2GB RAM although only 3.25 GB are usable. I can send you my log along with any other information deem it necessary.

Thanks for the quick reply!

Why only 3.25GB are usable?

3.25 only because of WIN 7

That is true only to Windows 7 32-bit but as I'm using the 64 bit-one, I'm almost certain it's due to my motherboard's chipset.

Quote from: o00o on April 28, 2016, 07:18:36 PM

Quote from: Eyedol-X on April 28, 2016, 06:47:18 PM

Quote from: Claymore on April 28, 2016, 05:39:45 PM

Quote from: Claymore on April 28, 2016, 06:51:45 PM

@ Claymore

I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer. I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem. Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem. I also tried renaming the dag files successfully created by QTminer in hopes of using them with yours but that also didn't work. My other rig is also Hawaii-based and surprisingly doesn't suffer from this symptom. I just gave v4.0 a try but it still introduces the same error.

Any feedback would be much appreciated!

v3.3 takes may be 10-20 more GPU memory, that's the only difference between previous versions. You even did not mention what cards are used, how much RAM etc.

I'm clueless as to why all versions excluding v1.2 fail to create a big buffer despite the fact that they were previously working prior to updating to v3.3. I did mention that the rig in question is seated with a Hawaii-based GPU, more precisely a reference Sapphire 290x operating on Windows 7 x64, Intel Pentium D w/ 2 x 2GB RAM although only 3.25 GB are usable. I can send you my log along with any other information deem it necessary.

Thanks for the quick reply!

Hope my .02 can help with your issue,

Just my gut here but I'm betting you're running out of system memory(ram) when attempting to mine. I just checked one of my single card rigs and it's using 3GB of Ram while running a ETH miner.

...could try setting a huge pagefiles but this doesn't completely substitute ram in Windows.

I've already done so but thanks for your advice nonetheless!

Quote from: Claymore on April 28, 2016, 05:39:45 PM

Quote from: o00o on April 28, 2016, 07:18:36 PM

@ Claymore

I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer. I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem. Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem. I also tried renaming the dag files successfully created by QTminer in hopes of using them with yours but that also didn't work. My other rig is also Hawaii-based and surprisingly doesn't suffer from this symptom. I just gave v4.0 a try but it still introduces the same error.

Any feedback would be much appreciated!

v3.3 takes may be 10-20 more GPU memory, that's the only difference between previous versions. You even did not mention what cards are used, how much RAM etc.

I'm clueless as to why all versions excluding v1.2 fail to create a big buffer despite the fact that they were previously working prior to updating to v3.3. I did mention that the rig in question is seated with a Hawaii-based GPU, more precisely a reference Sapphire 290x operating on Windows 7 x64, Intel Pentium D w/ 2 x 2GB RAM although only 3.25 GB are usable. I can send you my log along with any other information deem it necessary.

Thanks for the quick reply!

Why only 3.25GB are usable?

I'm guessing my memory controller hub can only allocate up to 3.25GB of memory. I inspected the motherboard's bios in hopes of finding an option which would allow me to remove RAM reserved for GPU but none was available.

I exhausted every possible solution which crossed my mind.

Try WIN 8.1 instead of 7 in order to use all your RAM. I hope lack of RAM is the key to your problem.

I'm very reluctant to go to that extent since I doubt it's the cause of the problem given all versions which I've updated to were previously working just fine and v1.2 still does. I already wasted a few hours re-creating dag files for all versions above v1.2 in hopes of getting them to work again and really can't afford any further downtime especially if I end up having to revert to Windows 7.

kirilvvbg

full member

Activity: 213

Merit: 100

Quote from: Eyedol-X on April 28, 2016, 06:47:18 PM

Quote from: Claymore on April 28, 2016, 05:39:45 PM

Quote from: Claymore on April 28, 2016, 06:51:45 PM

@ Claymore

I updated to v3.3 from a previous 3.x version and was no longer able to mine due to failing to create a big buffer. I was forced to revert to v 1.2 to resolve the issue as any other builds replicate the problem. Absolutely no changes were made to the system in question; all I did was close the previously working miner and updated the directory's contents. All environment variables have been set as well as 2 x 8 GB pagefiles and I've also removed temp files as well as the dag directory which I additionally decided to provide an alternate one on a seperate hard drive to hopefully eliminate the problem. I also tried renaming the dag files successfully created by QTminer in hopes of using them with yours but that also didn't work. My other rig is also Hawaii-based and surprisingly doesn't suffer from this symptom. I just gave v4.0 a try but it still introduces the same error.

Any feedback would be much appreciated!

v3.3 takes may be 10-20 more GPU memory, that's the only difference between previous versions. You even did not mention what cards are used, how much RAM etc.

I'm clueless as to why all versions excluding v1.2 fail to create a big buffer despite the fact that they were previously working prior to updating to v3.3. I did mention that the rig in question is seated with a Hawaii-based GPU, more precisely a reference Sapphire 290x operating on Windows 7 x64, Intel Pentium D w/ 2 x 2GB RAM although only 3.25 GB are usable. I can send you my log along with any other information deem it necessary.

Thanks for the quick reply!

Hope my .02 can help with your issue,

Just my gut here but I'm betting you're running out of system memory(ram) when attempting to mine. I just checked one of my single card rigs and it's using 3GB of Ram while running a ETH miner.

...could try setting a huge pagefiles but this doesn't completely substitute ram in Windows.

I've already done so but thanks for your advice nonetheless!

Quote from: Claymore on April 28, 2016, 05:39:45 PM