BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[sunk818]

my miner crashed too about 3.5 hours

https://chainz.cryptoid.info/bbp/tx.dws?1162443.htm

Can the miner handle a tx this big? 71kB!

says it was a heap corruption

Faulting application name: bbpminer-x86.exe, version: 0.0.0.0, time stamp: 0x5da4aacd
Faulting module name: ntdll.dll, version: 10.0.17763.802, time stamp: 0x125ac1e8
Exception code: 0xc0000374
Fault offset: 0x00000000000fb049
Faulting process id: 0xc60
Faulting application start time: 0x01d585e05653251f
Faulting application path: C:\bbp\bbpminer-x86.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5df0bfb2-9e13-4ecc-bde0-6b60db36bff6
Faulting package full name:
Faulting package-relative application ID:

[bible_pay]

my miner crashed too about 3.5 hours

https://chainz.cryptoid.info/bbp/tx.dws?1162443.htm

Can the miner handle a tx this big? 71kB!

says it was a heap corruption

Faulting application name: bbpminer-x86.exe, version: 0.0.0.0, time stamp: 0x5da4aacd
Faulting module name: ntdll.dll, version: 10.0.17763.802, time stamp: 0x125ac1e8
Exception code: 0xc0000374
Fault offset: 0x00000000000fb049
Faulting process id: 0xc60
Faulting application start time: 0x01d585e05653251f
Faulting application path: C:\bbp\bbpminer-x86.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5df0bfb2-9e13-4ecc-bde0-6b60db36bff6
Faulting package full name:
Faulting package-relative application ID:

Im starting to look at some of these external miner issues - but I have a lot going on- but I think you found the problem Sun - I believe our buffer is 65K - and if we sent out transactions bigger than that, I think that would crash the external miner.

Thats pretty huge.

Will look.  For some reason the CSS isnt showing up on bitcointalk and its hard to see quotes.

[bible_pay]

my miner crashed too about 3.5 hours

https://chainz.cryptoid.info/bbp/tx.dws?1162443.htm

Can the miner handle a tx this big? 71kB!

says it was a heap corruption

Faulting application name: bbpminer-x86.exe, version: 0.0.0.0, time stamp: 0x5da4aacd
Faulting module name: ntdll.dll, version: 10.0.17763.802, time stamp: 0x125ac1e8
Exception code: 0xc0000374
Fault offset: 0x00000000000fb049
Faulting process id: 0xc60
Faulting application start time: 0x01d585e05653251f
Faulting application path: C:\bbp\bbpminer-x86.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5df0bfb2-9e13-4ecc-bde0-6b60db36bff6
Faulting package full name:
Faulting package-relative application ID:

Im starting to look at some of these external miner issues - but I have a lot going on- but I think you found the problem Sun - I believe our buffer is 65K - and if we sent out transactions bigger than that, I think that would crash the external miner.

Thats pretty huge.

Will look.  For some reason the CSS isnt showing up on bitcointalk and its hard to see quotes.

Ok, I think I see the problem- that big transaction is bigger than the buffer for the external miner.

I think thats why we all crashed at the same time - everyone was trying to mine it at the same time.

So, I am very close to deploying NOMP (I think within 24 hours I should have a test setup ready for prod)- at the same time, we need an upgrade for the miner anyway; so Ill increase the buffer to the size of our block size.

I think this will need to be done by tomorrow by noon.

In the mean time the core client should be mining OK.

[sunk818]

Wow, first block in a while that took over 1 hour to mine.
Did not require ABN (could not find CPK) to mine this block.
https://chainz.cryptoid.info/bbp/block.dws?152520.htm
Good job BSVGwonbfwEYf26iwP8WB8ftC8Ghh74h9o

[Nipar]

hmm few minutes ago, all miners on all wallets on all PCs crashed... also on wallet copies... so it must have something to do with data from wallets


  "abninfo": "ABN: OK; ",
  "gsc_errors": "low abn weight 0",

but abn is ok
  "weight": 560430.9543402777,
and
  "weight": 1419968.982430556,

edit2: now i can start miners again, maybe chain moved to another block or what... maybe there was some weird block around 152537

I got the same thing at the same time. Segmentation faults, bus errors. Miners did core dump (cannot find the dump file....) and then couldn't be restarted for almost half an hour without aborting. Strangely, after restarting the wallet the miners were fine until I unlocked the wallet. Then they immediately crashed again.

I see I am late to the party... oh well lol

[bible_pay]

hmm few minutes ago, all miners on all wallets on all PCs crashed... also on wallet copies... so it must have something to do with data from wallets


  "abninfo": "ABN: OK; ",
  "gsc_errors": "low abn weight 0",

but abn is ok
  "weight": 560430.9543402777,
and
  "weight": 1419968.982430556,

edit2: now i can start miners again, maybe chain moved to another block or what... maybe there was some weird block around 152537

I got the same thing at the same time. Segmentation faults, bus errors. Miners did core dump (cannot find the dump file....) and then couldn't be restarted for almost half an hour without aborting. Strangely, after restarting the wallet the miners were fine until I unlocked the wallet. Then they immediately crashed again.

I see I am late to the party... oh well lol

Yeah, if you are trying to mine the same block that is too big for the miner, it will continually crash until the block passes.

[bible_pay]

BiblePay - External CPU Miner
1.0.0.6-Mandatory upgrade for Miners

- Prevent crash during big blocks

Binaries:

https://github.com/biblepay/cpuminer/tree/master/binaries

[bible_pay]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **



I am proud to announce our new NOMP pool is now opening in Beta mode.

You must use the BBP external miner to mine against our NOMP pool (as nomp requires stratum).

Note, that ABN's are going to be supported, however today all the shares temporarily pay the same amount (as ABN is not configured on the server side yet).

The goal today is to ensure the shares are being accepted in prod, the miners do not crash in stratum mode, the miners continually receive new work, and that we can actually solve blocks in prod.  Also, we need to ensure payouts work correctly from the NOMP side.

Regarding payouts:  NOMP pays every 15 minutes, but does require each solved block to be fully matured; here is an example of how your payout would work:
Miner A solves block 100,000.  NOMP records this miners shares and BBP address in the database (even if you stop mining, NOMP will remember your work).
At block 100,120, NOMP will see the block has matured.  Within 30 minutes, it will distribute all of the payouts (for every share that participated in that block).
So from a high level, you will be paid about 12 hours later for shares you solved.

WEB SITE URL:

http://nomp.biblepay.org

I have added some preliminary instructions on how to mine against NOMP on the home page.  Please see the wiki.

Basic configuration from our external miner:

https://wiki.biblepay.org/Nomp_mining
(See the Easy setup section)


As soon as ABN is configured on the server, I will post and explain how you can see your ABN status and ABN payout information, etc.

[sunk818]

some windows 10 users are stating the 1006 is crashing right away.
the error message is:

0xc00000fd stack_overflow

[fenin0018]

BiblePay - External CPU Miner
1.0.0.6-Mandatory upgrade for Miners

- Prevent crash during big blocks

Binaries:

https://github.com/biblepay/cpuminer/tree/master/binaries

Mandatory from block nº?

[capulo]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **



I am proud to announce our new NOMP pool is now opening in Beta mode.

there is 1 worker and 220mhash? should not it be khash?

[Nipar]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **



I am proud to announce our new NOMP pool is now opening in Beta mode.

there is 1 worker and 220mhash? should not it be khash?

I see 2 workers, one is mine. However I doubt I am doing Mega Hash so something isn't configured right on the pool end. The pool needs some tweaks but is currently doing alright
I actually am doing Mega Hash per second..... 78690 kh/s is after all 78.69 Mega Hash per second.... silly me lol

[orbis]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **


I am proud to announce our new NOMP pool is now opening in Beta mode.

I want to create miner "harder" way, but it's not possible.
When I put BBP receiving address as miner name it give me this result:

Code:

Error while Adding Miner
Miner WorkerName must not be greater than 19 characters long. Record Not Saved. Miner Name updated to 19 length on page. (Error 60002)

[Nipar]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **


I am proud to announce our new NOMP pool is now opening in Beta mode.

I want to create miner "harder" way, but it's not possible.
When I put BBP receiving address as miner name it give me this result:

Code:

Error while Adding Miner
Miner WorkerName must not be greater than 19 characters long. Record Not Saved. Miner Name updated to 19 length on page. (Error 60002)

yeah, that's not good. It's a limitation in the code for the old pool not the miner software.

Hopefully just a quick fix as I am also trying to make a "hard" account on NOMP pool

[bible_pay]

BiblePay - External CPU Miner
1.0.0.6-Mandatory upgrade for Miners

- Prevent crash during big blocks

Binaries:

https://github.com/biblepay/cpuminer/tree/master/binaries

Mandatory from block nº?

Its just an upgrade to keep you from crashing, so at your leisure.

[bible_pay]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **



I am proud to announce our new NOMP pool is now opening in Beta mode.

there is 1 worker and 220mhash? should not it be khash?

Pool is using the defaults, which are probably ASIC.

Yes, I will need to update this parameter to KH/S.

[bible_pay]

** BiblePay - New NOMP Pool - Opening in BETA mode for testing **


I am proud to announce our new NOMP pool is now opening in Beta mode.

I want to create miner "harder" way, but it's not possible.
When I put BBP receiving address as miner name it give me this result:

Code:

Error while Adding Miner
Miner WorkerName must not be greater than 19 characters long. Record Not Saved. Miner Name updated to 19 length on page. (Error 60002)

I haven't deployed the ABN changes yet; but I am trying to get to that next. 

[sunk818]

Hopefully just a quick fix as I am also trying to make a "hard" account on NOMP pool

Are you trying to register an account on the pool?

Let's keep it user name as the BBP receiving address. The point is to keep the process simple for miners.

[Nipar]

Hopefully just a quick fix as I am also trying to make a "hard" account on NOMP pool

Are you trying to register an account on the pool?

Let's keep it user name as the BBP receiving address. The point is to keep the process simple for miners.

It's the bbp address that's the problem, it's tooo long.

[bible_pay]

some windows 10 users are stating the 1006 is crashing right away.
the error message is:

0xc00000fd stack_overflow

Have the person paste a screenshot showing the error, and a screenshot showing the configuration they typed in at launch, and conditions leading up to the crash.

After that try to reproduce the problem on windows 10.