Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum+Decred GPU Miner v4.0
by
o00o
on 29/04/2016, 05:26:19 UTC

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.

@ 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.
@ 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!

@ 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.