Quote from: BogdanCo on June 10, 2018, 06:45:39 AM

Quote from: Xardas2014 on June 09, 2018, 10:00:09 PM

Quote from: Xardas2014 on June 09, 2018, 09:22:52 PM

Quote from: BogdanCo on June 06, 2018, 07:31:32 PM

Quote from: Xardas2014 on June 06, 2018, 03:17:14 AM

Quote from: BogdanCo on June 02, 2018, 10:05:33 AM

Quote from: cryptobias on June 02, 2018, 08:25:06 AM

Quote from: BogdanCo on June 01, 2018, 09:30:30 PM

Quote from: cryptobias on June 01, 2018, 09:16:25 PM

Hello,

I have issue with my rx480 mining rig, it runs before perfect, but i ahve to change ssd, and after the new win10 installation, the miner stuck after detecting pools.

I use latest win10 ltsb, asrock h81 btco pro r2.0 mobo. Onboard display is selected, and gen1 also.
I see my cards at the device manager, also installed the chipset driver, but the miner cannot start.

OverdriveNtool also detect my gpus. Change the mobo and the cpu as well, it isnt solve the issue, any idea?
I think something missing, but i dont have a clue, out of ideas Sad

Disable ULPS from regedit... also, just a little patience, it's not stuck, it just takes a little more time than usual but if you disable the ULPS then it should start faster

Just put 0 instead of 1 and do a restart.

I forget it to write, vut i also disable ULPS, i leave the miner running for 2-4 hours, and it gives, the claymore sign and pools again and again

Then maybe use DDU in Safe mode, disable ULPS again and see if it's working... if not, then is something else wrong there.

I have two rigs that have me baffled. Both are exact copies of each other, other than cards, but anyway all they do is https://ibb.co/cnLC8T which finally goes to https://ibb.co/gvf12o The 5 minute timer just goes on and on. I have set the EnableULPS to 0 but this prob persists. Any ideas? Sorry but the forum didn't like the image host. Dunno why, but you can copy the links to see the pics.

I have no ideea other than do a DDU in safe mode, install latest drivers and set ULPS to 0 for each card. Are AMD or Nvidia? You have this issue after latest Win10 update to v1803?

Neither rig has taken the v1803 update. At this point I have tried 9 different drivers from the blockchain driver forward. I've used regedit to search "EnableULPS" and set it to zero.(This location can be in different places with different drivers, so use the regedit search feature). Rebooted and CLaymore does the same thing. Nicehash 1.9.0.3 doesn't detect any AMD cards. Right now both rigs are running the flakeyass SMOS, 6 of 8 cards on each rig. SMOS drops caards and spits out too many errors to risk running all 8.

I'm recovering from colon cancer surgery, so it is quite difficult for me to run back and forth testing rigs. I hope someone finds the solution. I did a fresh install of win10 pro disconnected from the net, stopped updates and a host of spying shit, installed drivers and all 8 are detected. Disabled ULPS, ran the ati patcher, set all the cards to compute, set virtual memory to 16k-32k. Connected the net and fired up Claymore only to see the same shit I have been seeing........it won't initialize. Tried nicehash 1.9.0.3 and it still doesn't detect the AMD cards. Back to SMOS and 6 cards until someone finds a solution.

No, it is not always in the same location. Using the newest drivers from AMD it moved from \0000 to \0001. It doesn't exist at \0000 in the latest driver. I know because I added a DWORD value for it set to 0 and that did nothing. So I used the regedit search and found it at \0001.

\0000
\0001
\0002
...
etc

are the card's number installed into your rig.... You have to turn ULPS to 0 for every card.
So if you have 8 cards then go to {4d36e968-e325-11ce-bfc1-08002be10318} and inside every folder /0000.... /0007 you must switch the ULPS to 0;
Yes, if you installed one card and then remove it and now install another one, then you can see /0000 and /0001... buy always use DDU in safe mode and then install drivers for the new card.

Ok, I have narrowed the problem down and am looking for a solution to fix it. Using gpu-z openCL is unchecked. Something is disabling openCL detection. On a fresh install of windows 10 enterprise and the latest drivers, Claymore worked for a few seconds, but I got a BSOD three times. I DDU and tried to install aug23 blockchain drivers and Claymore wouldn't initialize again. DDU and tried 17.2.1 with the same results before thinking about checking stuff with GPU-Z. GPU-Z only has the direct compute checked, the rest are unchecked. After some reading a few years back they said the intel igpu driver was bad and causing havoc with opencl. As yet I haven't solved this since it is bedtime. I have to figure out what is causing openCL detection to not work. If you have any ideas, please throw'em at me.

Xardas2014

Posts

Merits