NiceHash crashes when Querying OpenCL Devices

[kunambi]

Starting NiceHash (tried with multiple versions, but also latest 2.0.1.10) on my Windows 10 computer, and after I've entered the captcha, the program crashes when reaching Querying OpenCL Devices.

I have installed the latest Nvidia drivers. Cleanly as well.

Is there a way to edit the General.json to disable the querying? The legacy miner has this feature.

Error log from nhm2\logs\log.txt

{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[NICEHASH] Initializing NiceHashMiner v2.0.1.10 - Beta","time":"2018-01-31T06:58:26.761Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[NICEHASH] Checking system version","time":"2018-01-31T06:58:27.063Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[NICEHASH] Checking system version DONE!","time":"2018-01-31T06:58:27.924Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[NICEHASH] Starting Device Detection...","time":"2018-01-31T06:58:27.924Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs START","time":"2018-01-31T06:58:28.433Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs result: [\"status\": true, \"resultStr\": '{\"CPUInfo\":{\"Brand\":\"Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz\",\"Features\":{\"AES\":true,\"AVX\":true,\"AVX2\":true,\"SSE2\":true,\"SSE41\":true,\"SSE42\":true},\"LogicalCores\":4,\"PhysicalCPUsCount\":1,\"PhysicalCores\":2,\"TotalCores\":-1},\"ErrorString\":\"\"}']","time":"2018-01-31T06:58:28.433Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] ---\n  detect: \"QueryCPUs\"\n  parsed: \n    CPUInfo: \n      Brand: \"Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz\"\n      Features: \n        AES: true\n        AVX: true\n        AVX2: true\n        SSE2: true\n        SSE41: true\n        SSE42: true\n      LogicalCores: 4\n      PhysicalCPUsCount: 1\n      PhysicalCores: 2\n      TotalCores: -1\n    ErrorString: \"\"\n","time":"2018-01-31T06:58:28.434Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs END","time":"2018-01-31T06:58:28.436Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices START","time":"2018-01-31T06:58:28.436Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices result: [\"status\": true, \"resultStr\": '{\"CudaDevices\":[{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":0,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-088a625f-0861-0ec8-4d89-cc60724db533\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":1,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":1,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-17ebef6b-6ce8-83e7-563c-cc4032075df2\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":2,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-d784da26-6063-420a-4d3e-dd6d03cc539b\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":3,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-d745b64b-5751-fae4-42f2-1773e85d23e1\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294}],\"DriverVersion\":\"388.71\",\"ErrorString\":\"\"}']","time":"2018-01-31T06:58:29.200Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] ---\n  detect: \"QueryCudaDevices\"\n  parsed: \n    CudaDevices: \n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 0\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-088a625f-0861-0ec8-4d89-cc60724db533\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 1\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 1\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-17ebef6b-6ce8-83e7-563c-cc4032075df2\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 2\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-d784da26-6063-420a-4d3e-dd6d03cc539b\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 3\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-d745b64b-5751-fae4-42f2-1773e85d23e1\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n    DriverVersion: \"388.71\"\n    ErrorString: \"\"\n","time":"2018-01-31T06:58:29.201Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices END","time":"2018-01-31T06:58:29.202Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":6228,"level":30,"msg":"[ComputeDeviceManager.Query] QueryOpenCLDevices START","time":"2018-01-31T06:58:29.203Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[NICEHASH] Initializing NiceHashMiner v2.0.1.10 - Beta","time":"2018-01-31T06:58:57.994Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[NICEHASH] Checking system version","time":"2018-01-31T06:58:58.297Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[NICEHASH] Checking system version DONE!","time":"2018-01-31T06:58:58.690Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[NICEHASH] Starting Device Detection...","time":"2018-01-31T06:58:58.691Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs START","time":"2018-01-31T06:58:59.080Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs result: [\"status\": true, \"resultStr\": '{\"CPUInfo\":{\"Brand\":\"Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz\",\"Features\":{\"AES\":true,\"AVX\":true,\"AVX2\":true,\"SSE2\":true,\"SSE41\":true,\"SSE42\":true},\"LogicalCores\":4,\"PhysicalCPUsCount\":1,\"PhysicalCores\":2,\"TotalCores\":-1},\"ErrorString\":\"\"}']","time":"2018-01-31T06:58:59.081Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] ---\n  detect: \"QueryCPUs\"\n  parsed: \n    CPUInfo: \n      Brand: \"Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz\"\n      Features: \n        AES: true\n        AVX: true\n        AVX2: true\n        SSE2: true\n        SSE41: true\n        SSE42: true\n      LogicalCores: 4\n      PhysicalCPUsCount: 1\n      PhysicalCores: 2\n      TotalCores: -1\n    ErrorString: \"\"\n","time":"2018-01-31T06:58:59.082Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs END","time":"2018-01-31T06:58:59.083Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices START","time":"2018-01-31T06:58:59.084Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices result: [\"status\": true, \"resultStr\": '{\"CudaDevices\":[{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":0,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-088a625f-0861-0ec8-4d89-cc60724db533\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":1,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":1,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-17ebef6b-6ce8-83e7-563c-cc4032075df2\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":2,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-d784da26-6063-420a-4d3e-dd6d03cc539b\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":3,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-d745b64b-5751-fae4-42f2-1773e85d23e1\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294}],\"DriverVersion\":\"388.71\",\"ErrorString\":\"\"}']","time":"2018-01-31T06:58:59.597Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] ---\n  detect: \"QueryCudaDevices\"\n  parsed: \n    CudaDevices: \n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 0\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-088a625f-0861-0ec8-4d89-cc60724db533\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 1\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 1\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-17ebef6b-6ce8-83e7-563c-cc4032075df2\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 2\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-d784da26-6063-420a-4d3e-dd6d03cc539b\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 3\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-d745b64b-5751-fae4-42f2-1773e85d23e1\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n    DriverVersion: \"388.71\"\n    ErrorString: \"\"\n","time":"2018-01-31T06:58:59.597Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices END","time":"2018-01-31T06:58:59.598Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":7924,"level":30,"msg":"[ComputeDeviceManager.Query] QueryOpenCLDevices START","time":"2018-01-31T06:58:59.598Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[NICEHASH] Initializing NiceHashMiner v2.0.1.10 - Beta","time":"2018-01-31T06:59:17.038Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[NICEHASH] Checking system version","time":"2018-01-31T06:59:17.341Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[NICEHASH] Checking system version DONE!","time":"2018-01-31T06:59:17.604Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[NICEHASH] Starting Device Detection...","time":"2018-01-31T06:59:17.604Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs START","time":"2018-01-31T06:59:17.988Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs result: [\"status\": true, \"resultStr\": '{\"CPUInfo\":{\"Brand\":\"Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz\",\"Features\":{\"AES\":true,\"AVX\":true,\"AVX2\":true,\"SSE2\":true,\"SSE41\":true,\"SSE42\":true},\"LogicalCores\":4,\"PhysicalCPUsCount\":1,\"PhysicalCores\":2,\"TotalCores\":-1},\"ErrorString\":\"\"}']","time":"2018-01-31T06:59:17.989Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] ---\n  detect: \"QueryCPUs\"\n  parsed: \n    CPUInfo: \n      Brand: \"Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz\"\n      Features: \n        AES: true\n        AVX: true\n        AVX2: true\n        SSE2: true\n        SSE41: true\n        SSE42: true\n      LogicalCores: 4\n      PhysicalCPUsCount: 1\n      PhysicalCores: 2\n      TotalCores: -1\n    ErrorString: \"\"\n","time":"2018-01-31T06:59:17.990Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCPUs END","time":"2018-01-31T06:59:17.991Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices START","time":"2018-01-31T06:59:17.992Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices result: [\"status\": true, \"resultStr\": '{\"CudaDevices\":[{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":0,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-088a625f-0861-0ec8-4d89-cc60724db533\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":1,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":1,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-17ebef6b-6ce8-83e7-563c-cc4032075df2\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":2,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-d784da26-6063-420a-4d3e-dd6d03cc539b\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294},{\"DeviceGlobalMemory\":8589934592,\"DeviceID\":3,\"DeviceName\":\"GeForce GTX 1070\",\"HasMonitorConnected\":0,\"SMX\":15,\"SM_major\":6,\"SM_minor\":1,\"UUID\":\"GPU-d745b64b-5751-fae4-42f2-1773e85d23e1\",\"VendorID\":4318,\"VendorName\":\"NVIDIA\",\"pciDeviceId\":461443294,\"pciSubSystemId\":461443294}],\"DriverVersion\":\"388.71\",\"ErrorString\":\"\"}']","time":"2018-01-31T06:59:18.498Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] ---\n  detect: \"QueryCudaDevices\"\n  parsed: \n    CudaDevices: \n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 0\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-088a625f-0861-0ec8-4d89-cc60724db533\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 1\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 1\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-17ebef6b-6ce8-83e7-563c-cc4032075df2\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 2\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-d784da26-6063-420a-4d3e-dd6d03cc539b\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n      - \n        DeviceGlobalMemory: 8589934592\n        DeviceID: 3\n        DeviceName: \"GeForce GTX 1070\"\n        HasMonitorConnected: 0\n        SMX: 15\n        SM_major: 6\n        SM_minor: 1\n        UUID: \"GPU-d745b64b-5751-fae4-42f2-1773e85d23e1\"\n        VendorID: 4318\n        VendorName: \"NVIDIA\"\n        pciDeviceId: 461443294\n        pciSubSystemId: 461443294\n    DriverVersion: \"388.71\"\n    ErrorString: \"\"\n","time":"2018-01-31T06:59:18.498Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] QueryCudaDevices END","time":"2018-01-31T06:59:18.499Z","v":0}
{"name":"NHM","hostname":"STATIONARY-M","pid":612,"level":30,"msg":"[ComputeDeviceManager.Query] QueryOpenCLDevices START","time":"2018-01-31T06:59:18.499Z","v":0}

[geo5275]

I have exactly the same problem. I noticed that when I reinstall drivers it works but as soon as I open either MSI afterburner or ASUS GPU Tweak II I start getting this error.

[tionchek]

i have the same problem , i uninstalled driver and everything cant get nicehash to work, did you guys figure it out ?

[nuonrg]

same problem on NiceHash 2.0.1.11 - NVIDIA NiceHash crashes when Querying OpenCL Devices

[utmath]

I have the same problem. If I run NiceHash after removing all the GPUs from my mother board, I do not encounter this problem. However, of course, running NiceHash without GPUs is almost meaningless (T_T)

[tionchek]

i just installed windows again, first registry tweaks -> http://1stminingrig.com/best-windows-setup-configuration-tweaks-for-mining/ , than drivers and nicehash and it works

[utmath]

@tionchek It does not help me but thank you for your advice.

[fancyHeat]

I'm experiencing the same issue. Reinstalling did not work.

[braadz33]

Gad same errors, fixed below

1. Ensure gpu on riser to monitor, no onboard use at all
2. Install fresh windows 10 pro
3. Install all motherboard drivers, restart between drivers
4. Run 1st mining rig windows tweaks
5. Restart
6. Install gpu drivers
7. Restart
8. Install nicehash 2

Worked first go after that order

[utmath]

@braadz33 It works in my environment. It seems that not using onboard monitor is important. Thank you!

[braadz33]

@utmath yes I suspect when drivers install, or windows along with the Visual Basic crap that goes with it must allow some openCL rights to the GPU.

I did not install my on board vga drivers and did not touch it. Any rig install you do, always make sure the gpu on riser is working in bios etc before moving forward.

Glad it helped

Cheers

[shiankiri]

@braadz33 @tionchek Thanks for the suggestions. I managed to get my rig to work based on what you guys have said.

I'd like to add, however, that it may be an order of operations thing requiring updates to your hardware before you can even do any of these steps.

Reinstalling Windows 10 didn't solve the issue at first. Following braadz33's steps also didn't solve the issue afterwards. Reinstalling Windows 10 AFTER doing braadz33's steps DID work.

It may be a combination of events and order of operations that will solve this issue.

You may need to install an OS first and update all the drivers to your GPUs and Motherboard, etc. Pretty much make sure everything is up to date.

If running NiceHash still crashes on OpenCL query, reinstalling Windows 10 alone and updating the GPU drivers will allow it to work.

I don't know the full details of why this was the case, but the key seems to be having updates applied to your hardware at some point and then a fresh reinstall of Windows 10 is what will solve this issue.

[braadz33]

@shiankiri , did you format? I would expect my steps to work if running from the riser/gpu. The need to go through them, then install again sounds weird. Interesting none the less ..

[shiankiri]

@braadz33 When reinstalling, I deleted the partitions and installed into the allocated space. I guess that would be the same thing as a quick format.

I definitely agree, it’s weird. Figured I post something because it was so fresh in my memory given I had literally JUST got it all to work an hour before I posted.

If someone ran through the steps and still had an OpenCL crash problem, it might be a time savor to just roll through the steps again for sure instead of wasting hours trying to debug the problem like I had.

[nuonrg]

Has nothing to do with all of that. It seems NiceHash nvidia can not run on a rig without connected monitor and/or disabled on board VGA. Try running it on a box with only ethernet connected through teamviewer or RDP or vnc. Wont work cause of the opencl problem. Can I have some confirmations on this?

[braadz33]

I don’t have my monitor plugged in anymore, only during install. Haven’t touched on board settings for video or installed vga drivers. I remote in and all fine

On 25 Mar 2018, at 10:00 pm, Wilco van Boxtel notifications@github.com wrote:

Has nothing to do with all of that. It seems NiceHash nvidia can not run on a rig without connected monitor and/or disabled on board VGA. Try running it on a box with only ethernet connected through teamviewer or RDP or vnc. Wont work cause of the opencl problem. Can I have some confirmations on this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[shiankiri]

@nuonrg Currently, my rig is not hooked up to any monitors what so ever. It's in the basement running on a wifi transmitter on the motherboard, no ethernet cable.

The only time I had a monitor was to adjust BIOS, install Windows 10 and Teamviewer. Afterwards, I removed the monitor.

Tweaked the registry. Updated GPU drivers. Updated Windows 10. Launched NiceHash and started mining.

Did all of that through Teamviewer on a Surface Pro while watching Jessica Jones S2 in bed.

[nuonrg]

Thanks guys for the comments. I am gonna give it another try, cause I see it works for you.

[VGerris]

I have the same issue. Unless a monitor is connected to the IGPU and thus it is being selected, nicehash starts, otherwise it hangs. Horrible bug that has cost me quite some cycles. Please fix this Nicehash devs or while your at it, deliver the Linux versions you promised ages ago :)!

[nuonrg]

Yes @VGerris I also still have the same problem. Nicehash won't start without monitor connected. But I switched to manual mining. Nicehash Linux version and new Algo's added would be nice and very much awaited.

[VGerris]

Feel free to elaborate, I'm sure many people are interested in a Linux based setup. I despise Windows and I love Linux, but I just don't like to get in setting everything up myself, I really like the automatic switching of it. I almost went for it, but I found the issue now, so I'll have some monitor attached. Any numbers on the Linux performance vs Windows? 5% gain would make it easy. In the mean time, bug is reported here too: https://github.com/nicehash/NiceHashMiner/issues/1499 let's hope for a fix. Don't have the issue on a AMD motherboard with Ryzen CPU. I recommend that anyway above intel, more value for money and longer socket support.

[silverinnovation]

Just to chime in, for me, this is categorically a problem with no monitor being attached when Windows boots and NiceHash tries to fire up.

I used a HDMI cable to the on-board graphics card to configure the rig. However the moment I disconnect it and reboot the machine, NiceHash crashes when it gets to the Querying OpenCL Devices bit

Switch the machine off, reconnect the HDMI cable, it fires up and NiceHash loads without issue.

I'm guessing maybe Windows is changing registry settings expecting there to be a HDMI monitor connection the next time it boots and maybe NiceHash cannot cope with that? The other people who posted here about not having an issue, I wonder if they used a VGA/DVI connection to a monitor? Or used one of the mining graphics cards instead of the on-board graphics?

Running v2.0.1.10 beta. Would be great if NiceHash devs could investigate this as it means I can't de-tether my rig from a monitor!

[VGerris]

I have this problem always. Not a problem with either HDMI or DVI attached monitor onboard. Forgot about attached to video card but think it was an issue too. Could be windows failing but since Nicehash hangs, it's a bug there.

[shiankiri]

I only ever used HDMI for Monitor connection.

Have you tried reinstalling Windows and seeing if it works out?

Further up the thread, I mentioned what I did to resolve the problem.

Since then, I’ve built an additional 3 rigs. Each time, it came down to order of operations.

Each time, NiceHash crashes out on querying OpenCL. However, this problem is not limited to NiceHash. I’ve had ccminer crash on trying to initialize CUDA Devices.

All 4 of my rigs went through the same issues. I installed Windows to update the BIOS. I install GPU Drivers and attempt to run NiceHash. It crashes on Querying OpenCL.

Reboot system. Delete all partitions. Fresh install Windows a second time. Install GPU Drivers since BIOS is now up to date. Launch NiceHash, everything is cool.

It’s always that first install that doesn’t work.

[braadz33]

I never have this issue, can leave GPUs unplugged fine

On 3 May 2018, at 5:22 pm, shiankiri notifications@github.com wrote:

I only ever used HDMI for Monitor connection.

Have you tried reinstalling Windows and seeing if it works out?

Further up the thread, I mentioned what I did to resolve the problem.

Since then, I’ve built an additional 3 rigs. Each time, it came down to order of operations.

Each time, NiceHash crashes out on querying OpenCL. However, this problem is not limited to NiceHash. I’ve had ccminer crash on trying to initialize CUDA Devices.

All 4 of my rigs went through the same issues. I installed Windows to update the BIOS. I install GPU Drivers and attempt to run NiceHash. It crashes on Querying OpenCL.

Reboot system. Delete all partitions. Fresh install Windows a second time. Install GPU Drivers since BIOS is now up to date. Launch NiceHash, everything is cool.

It’s always that first install that doesn’t work.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[VGerris]

I have a recent bios and I actually did reinstall Windows because it's known to be crap and that sometimes it solves things. At first I thought it did, but in the end it was just because of the monitor being attached. I wouldn't even touch it if there was a Linux version, because it's a complete waste of time. I hope people realize reinstalling an OS shouldn't be a solution, ever.

[nuonrg]

Maybe plugging in a dumb hdmi dongle will help? But think only smart hdmi dongles are on the market right now.

[shadz3rg]

Go to Device Manager -> Display -> Show hidden devices -> remove Intel Graphics -> reboot Boom, problem solved.

[Perefin]

Same issue here. Confirmed @shadz3rg that this solution DOESN'T solve the issue. Please help! Can no longer run NiceHash on my purpose built 1080 Ti rig. Worked for months without issue previously and I've already tried a number of the solutions above, including messing with the displays connected etc, several clean installs and uninstalls of various of the past 4 versions. Again... please help! This is a GAPING open issue that has not been even close to resolved.

[VGerris]

Even if it would work, it's a workaround, not a solution. It's a Nicehash bug that should be fixed, without needing to switch to an AMD based setup, which I would by the way happily so if it gets paid for :)

[kunambi]

Are the NH team even reading any tickets?

I honestly can't understand the difficulty of adding an option to skip the check.

[shiankiri]

That doesn’t make any sense to me.

Have you tried running a miner that isn’t NiceHash and see if you could?

Querying OpenCL and crashing out isn’t so much a bug as it is a driver/hardware failure. In code, if you couldn’t send information to your devices and get information back, there’s no amount of coding that will fix that in your program.

At least for me, running ccminer and other mining software, it would crash all the same until the OpenCL issue was resolved.

I don’t think skipping the check would do anything.

[kunambi]

I can run NH Miner Legacy, and skip the check, which allows me to run the mining. So it's evident that the problem lies in the check, not later.

[shiankiri]

@kunambi Just a little background on my end: I'm a programmer. I do this stuff everyday. What you're posting has me really skeptical because this is the kind of nonsense that people try to pass by me constantly and I find out that the problem lies with the user instead of the program. What you just did was the equivalent of putting a flat edge to the ground and exclaimed: "Look! The Earth is flat!"

I'm not trying to prove you wrong or ridicule you or anything, but it's getting a bit frustrating man because I'm legitimately trying to help you.

When you ran NiceHash Miner Legacy: Did you check to see what pieces of hardware was doing work? Because I suspect that what is happening is, you're not running optimally. There's a good chance the algorithm you're running ended up being placed on your CPU or the algorithm is no longer used.

Did the logs error out the entire time when you attempted to mine?

There's a long list of things you need to look at to make sure you're actually mining.

It's why I keep mentioning, use a different miner and see if the results are the same because I suspect that if you couldn't run a different miner, you wouldn't be able to run NiceHash 2.

There is a reason why that check exists. The program is trying to confirm that your devices can use the CUDA Cores to process information. If it can't, it's just going to run... I don't know, CryptoNight on your CPU.

The best analogy I have for you is: Would you prefer to scrape the dirt for gold or dig a shaft to get to the veins?

When you run Legacy, you're doing the former, not the latter.

[jonathanlouisaguilar]

shadz3rg Go to Device Manager -> Display -> Show hidden devices -> remove Intel Graphics -> reboot Boom, problem solved.

Thanks!!!

This worked for me thank god, all the nh admin tickets response was to make sure I have the latest visual c++

[kins888]

I've just had the white screen issue. I tried the suggested fix from shadz3rg and it worked for me. That's a big thank you from me - I was going crazy trying to resolve the issue.

[frankfuu]

Thanks @shadz3rg

Go to Device Manager -> Display -> Show hidden devices -> remove Intel Graphics -> reboot Boom, problem solved.

This did it for me! Hopefully this can be addressed soon.

[huntsman4596]

I fixed it by removing the opencl_device_detection.dll file from the main directory. Nothing else worked for me. I am using NVIDIA GPUs and the legacy version.

[jz02182]

renaming opencl_device_detection.dll to opencl_device_detection.old fixed for me thanks