Quote from: Borgholio on March 28, 2020, 04:30:56 PM

Ok so I have more information regarding my inability to report BBP shares to the pool.

Unfortunately I am still not showing up on the list of workers, but I did make some progress in other areas. Firstly, I was able to solve the issue of the miner randomly crashing. I set the miner to run in Windows 7 compatibility mode and let it run overnight. Instead of crashing out after just a couple of accepted shares, it now ran successfully without crashing for several hours and has submitted 337 shares (and still going). So that's a great improvement.

Now as for the bigger issue with the pool not seeing my shares, unfortunately that has not changed at all. Even with 337+ shares submitted, I'm still not showing on the BBP worker list. I am no longer able to check the XMR tab to see how many XMR shares I've submitted since that tab doesn't seem to be working. It's just showing blank.

I don't see any reason why it wouldn't be working, everything checked out. Here's what I've tried so far:

Running the miner as administrator.
Launching the miner from an elevated command prompt.
Unblocking the .exe and the winring.sys files.
Adding the mining folder to the exception list of Windows Defender.
Added the individual files in the folder to the exception list of Windows Defender.
Completely disabling Windows Defender.
Added exceptions in Windows Firewall for the mining .exe file.
Completely turned off Windows Firewall.
Tested two versions of the mining .exe - 5.6.2 and 5.6.3.
Successfully telnet to rx.biblepay.org at both ports 3001 and 3020.
Ran the miner at both ports 3001 and 3020.
Generated a new receiving address in the BBP wallet.
Tested mining on a different computer.
Tested mining using a different internet connection.
Tested static IP with Google DNS.
Tested disabling IPv6.
Tested using the --keepalive switch.

That's pretty much everything. Not sure what to try next.

Well, on win7 compatibility mode, the only thing I can say about that is it probably forces your jit compiler to generate slightly different machine code. As I want to point out, the "crash" or silent exit you experience, we do know where that happens and why. Its happening inside the generated machine language, in a stack trace generated by RX's virtual machine (another words, its not in biblepay code). And we know that a segfault cannot be contained safely. Thats why I recommended the goto loop as that is the only safe way to handle that. Just so people dont get the impression that you found a solution to a 'biblepay crash', he found a solution to the jit machine's machine language crash for his particular os and processor.

As far as not being able to submit bbp solutions, the only other suggestion I have is to run wireshark on your machine and monitor for the submit share packing (mining.submit). Once you see this going out in wireshark, capture the traffic and see if your machine blocks the submission, or, if it goes out and does not receive a response.

The other suggestion is trying a different router and plugging directly into the WAN. It could be software setting in the router resetting the packet outbound.
The other suggestion would be uninstalling any software on the machine other than mining software. You might have a proxy of some sort, or a firewall block you are not aware of. Or you can install a virtual machine and try mining in that pristine environment just to prove you can mine.
Your house is the only one not mining, so it must be a networking issue in your house.

Can you give us a screenshot of the XMR tab not populating? Thats also not happening on any of my machines, and not reported anywhere.
Is it that you just have to paste the address in and click lookup?