-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 3 App Hang Mining Intel 6950X CPU #90
Comments
yes just create hodlcoin.conf in the same folder where your binary or wallet.dat is, you can verify after you start if its disabled by looking in debug.log , look for: first line is detected flag state, second line is what the cpu accepted. |
I created the hodlcoin.conf and the app still hangs and crashes after I turn on solo mining. 2017-04-30 09:04:21 Optiminer Flags: AES-NI = 0, AVX2 = 0 |
Does the debug.log have any info about the crash , or your windows event log ? if that still doesnt hellp, and you have time can you try the 2.0.0 version again and see if that has the same issue ? |
Version 2 runs great no issues. I added minermemory=1 & genproclimit=4 and same result it hangs and crashes within seconds of turning on solo mining. I have this showing up in the debug log: 2017-04-30 14:06:23 Optiminer Flags: AES-NI = 0, AVX2 = 0 I wonder what this missing argument 2016 means? |
Found the following in the event viewer: Event 1000 application error Faulting application name: hodlcoin-qt.exe, version: 3.0.0.0, time stamp: 0x5903f45d |
thanx, "QString::arg: Argument missing" suggest we have a string format issue somewhere. |
I'm not sure I understand what "hodlings defined" means? I can sort the columns including the estimated date column and no issues at all. |
you answered my question so its not an issue on the hodlings table. |
one more thing to try, add to hodlcoin.conf then try to mine, provide us the debug.log, |
2017-04-30 16:42:09 HOdlcoin version v3.0.0 (2017-04-28 19:03:09 -0700) |
yup, try adding optimineraes=0 to your command line - you can do that in the shortcut too Then in the debug you should see - Optiminer Flags and CPU support: AES-NI = 0, AVX2 = 0 |
@FreeTrade I did try that but it made no difference so I removed it but I've added it back again now and testing with or without gives the same result with the APP hang. |
ok, can you post the debug.log with the aes flag switched off |
This is from the event viewer: Faulting application name: hodlcoin-qt.exe, version: 3.0.0.0, time stamp: 0x5903f45d This is from the debug.log 2017-04-30 22:44:49 HOdlcoin version v3.0.0 (2017-04-28 19:03:09 -0700) |
so the last line in the log is always "2017-04-30 22:47:26 create sha512 data 0.622" ? or did you omit the last part ? |
Yeah, looks like the problem is with creating the AES data which is weird, because it should just be using the 2.0 code if that aesoptimization switch is off. |
master of disaster, you were mining fine with 2.0 right? |
Can you try minermemory=1 genproclimit=1 with optimineraes=0 and optimineravx2=0 that should give us a really basic mining setup |
minermemory=1 genproclimit=1 with optimineraes=0 and optimineravx2=0 in conf file and the app still hangs as soon as I turn on solo mining. It was mining very nice on 2.0. Debug Log on the latest attempt: 2017-05-01 09:19:13 HOdlcoinMiner started It seems to hang at this same spot when it tries to create the AES data. Just for good measure I tried uninstalling 3.0 and then deleted the folders. I then re-booted and reinstalled 3.0 clean and then brought in my wallet.dat file. Still hangs just the same. Also, in the event viewer there is an Exception code: 0xc0000005 which could be an access violation. I installed 3.0 as an Admin and I also launch it as an Admin. Just noticed wisebc over at https://bitcointalk.org/index.php?topic=1317918.3920 is running into this same issue although he is on an AMD 6 core cpu. |
After updating to Version 3 the HOdl GUI loads fine but within seconds of turning on solo mining the APP crashes and closes. System OS is Windows 10 Pro CPU is Intel 6950X 10 core.
Can I add a switch to the shortcut icon target path to correct this issue? If so are there any instructions on how to do that?
The text was updated successfully, but these errors were encountered: