Bitcoin Forum
August 05, 2020, 02:14:10 PM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 [1195] 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 ... 1401 »
  Print  
Author Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)  (Read 6506096 times)
iSuX
Jr. Member
*
Offline Offline

Activity: 42
Merit: 8


View Profile
May 27, 2018, 11:04:11 AM

Huh Cry
We are having the same problem that Marius 85 and others seem to be having.

How may i fix this? I get a loop with this and it doesn't start mining..

Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)
ETH: Authorized
Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)


We reformatted our hard drive, reinstalled windows 10...had to go with 1803 as we did not have an older version available.  Downloaded Radeon driver 18.5.2 and Claymore 11.7.  We put the EthDcrminer64.exe into windows defender exceptions and still shuts off as soon as we start.  Here is the last log

20:26:15:884   e38   Check and remove old log files...
20:26:15:884   e38   args: -epool us2.ethermine.org:4444 -ewal xxxxxxxxxxxxxxxxx -epsw x
20:26:15:884   e38   
20:26:15:899   e38   浜様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様融
20:26:15:899   e38                   Claymore's Dual GPU Miner - v11.7               
20:26:15:899   e38                 ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             
20:26:15:899   e38   藩様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様夕
20:26:15:899   e38   
20:26:15:899   e38   b583
20:26:16:149   e38   ETH: 1 pool is specified
20:26:16:149   e38   Main Ethereum pool is us2.ethermine.org:4444
20:26:16:149   e38   DCR: 0 pool is specified


We even went into the console and tried to run the program...exactly the same log as this one. Just keeps shutting down as soon as it starts.

Very frustrated as the miner was running so well for the past four months.  We're newbies so we're at the limit of our knowledge base.
We are running three RX 570's with moded bios....ran patch...they are recognized and in compute mode.  One XFX RX 570 not moded on compute mode....we had stable 111mh/s on previous windows and Claymore 11.0.

Is there any hope?Huh



Clone the SSD from another working rig. Update drivers only, if required.

Interesting "solution". I'd suggest this is NOT a good idea. While svdinu might have the ability to get this to work, I'd suggest it will, in the long run, create a mass of issues, and even if you get it to work, it will take a LOT longer than a OS reinstall of Win10. (especially if you have an SSD, reinstall of Win10home, takes about 15min at most).

On cloning: Actually, unless the motherboard and peripheral devices are identical, it's quite likely the system will fail to boot, or have a bunch of driver issues, which, in the first place, IF you have the ability to solve, (and they are even solvable at all), you would simply know better than to try this solution to start with.

No criticism of svdinu here, simply that when troubleshooting, you need to ensure you are working to eliminate issues, and not introducing any new ones along the way. This solution, introduces a huge array of issues, and potential issues, and potential issues mean doubt later on when you have other problems with the rig.

Start as you intend to go on! (known good etc)

I mention this here, as I say, not to be critical of svdinu, clearly he's trying to help, but when I read that someone formatted/reinstalled their OS, that tells me, they are possibly lacking the experience to know how to identify their issue, and have opted for reinstall, which is extreme, but which is a FAR better idea under these circumstances, (given their skill level)  than trying to clone a SSD, assuming you even have one to clone from.

From a personal POV, I HAVE cloned OS discs many times, would I try it in the context of this problem? NO.

In fact, I build identical rigs for people, and I STILL don't clone SSDs, (unless I'm installing bigger ones, or replacing them etc), but for a new build, I only install fresh, this ensures stability, and no cross pollination, (security for both the client, but also security of stability).

My 5 cents.
Happy Mining





Oh man.. you sure have a lot of not-so-useful experience to share.
1) clones work just fine (all your ideas in this area is total crap, sorry. I have dozens of workers cloned and it works like a charm even WITH different HW, like MB and the rest. Also I once was doing production grade virtual appliances with MS OS, and the only issue with cloning is Microsoft support (none) and VERY rare conflicts in clones within Active Directory due to same SIDs issue)
2) to setup amd drivers  for 12 GPUs takes 2 minutes: 
* DDU(proper! until all gpus are microsoft adapters);
* unpack any driver since 17.10.2 (around here 8+ GPUs became supported ),
* update driver from device manager by navigating to the unpacked driver;
* set compute mode for all your devices here(0 dev sample):
Code:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
"KMD_EnableInternalLargePage"=dword:00000002
* if you have modded bioses run dagpatcher to bypass the signature
*use overdriven tool profiles for clocks and volts


Well ok Ursul0, you're entitled to your opinion and abilities, but regardless, your response is not helpful, constructive, or even civil.
Something for YOU to think about, look up "good manners" in the dictionary for a start!

Furthermore, you take this totally out of context, bringing in virtual machines! Well you SHOULD know full well, as a hardware abstraction layer solution, that in itself "solves" most of the driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.

Why you seem to think that is useful to these guys, is anyone's guess, other than to bolster your opinions, it provides no constructive, useful solution to the problem, you just add noise.

Granted you do have some good tips there, (apart from that redundant patcher), so one has to wonder why you didn't offer these suggestions sooner, although as I say, they are mostly not applicable as was already stated, these guys HAVE NO OS to clone from!


NOTE: there is no place for a pissing contest here on this forum! Lets try to keep it civil.





KISS. Did you read the Readme.txt?
Summarise/Itemise your hardware/versions/expectations/batchfile & results. The more specific, detailed, the better
1596636850
Hero Member
*
Offline Offline

Posts: 1596636850

View Profile Personal Message (Offline)

Ignore
1596636850
Reply with quote  #2

1596636850
Report to moderator
1596636850
Hero Member
*
Offline Offline

Posts: 1596636850

View Profile Personal Message (Offline)

Ignore
1596636850
Reply with quote  #2

1596636850
Report to moderator
1596636850
Hero Member
*
Offline Offline

Posts: 1596636850

View Profile Personal Message (Offline)

Ignore
1596636850
Reply with quote  #2

1596636850
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1596636850
Hero Member
*
Offline Offline

Posts: 1596636850

View Profile Personal Message (Offline)

Ignore
1596636850
Reply with quote  #2

1596636850
Report to moderator
1596636850
Hero Member
*
Offline Offline

Posts: 1596636850

View Profile Personal Message (Offline)

Ignore
1596636850
Reply with quote  #2

1596636850
Report to moderator
1596636850
Hero Member
*
Offline Offline

Posts: 1596636850

View Profile Personal Message (Offline)

Ignore
1596636850
Reply with quote  #2

1596636850
Report to moderator
forbidden
Hero Member
*****
Offline Offline

Activity: 1344
Merit: 536


View Profile
May 27, 2018, 11:59:13 AM

11.7 gives error, DevFee: failed to mine for a long time, something is wrong, "nofee" mode is enabled until successful devfee mining.

Code:
-epool stratum+tcp://pooladdress -ewal wallet.$rigName/mail -esm 0 -epsw x -allpools 1 -asm 1 -wd 0

What the problem?
vapourminer
Legendary
*
Offline Offline

Activity: 2954
Merit: 1543

what is this "brake pedal" you speak of?


View Profile
May 27, 2018, 12:01:10 PM
Last edit: May 27, 2018, 12:45:29 PM by vapourminer
Merited by iSuX (1)

So, in summary, do these old boards/CPUs have a GPU limit?

its not the cpu, undernourished cpus are usually fine in miners. even single core cpus have been used with no problems (in most miners).

probably a bios limitation. vga cards need a lot of resources, and the mobo/bios can run out unless special settings are used.

see if the bios has something like "above 4g decoding". short version is it increases the range of memory the mobo can assign to the cards, which is likely the issue. that bios setting is fairly recent in consumer mobos as having 4+ video cards wasnt very common back then when those mobos came out.

Ursul0
Sr. Member
****
Offline Offline

Activity: 771
Merit: 260


View Profile
May 27, 2018, 12:21:23 PM

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.




RE clones:
Using Acronis TrueImage, I've got the same UEFI Win10 image running on ASROCK H110, MSI Z270, ASROCK B150,  ASROCK H81. With various AMD and NVIDIA GPUs and ZERO issues. I reiterate myself: the only known problem with cloning is absence of official Microsoft support. (and I know this because see earlier)
Also how comes dagpatcher is "outdated" or whatever is your claim

RE problem:
I'm just cautioning these guys from listening to incompetent "yet very helpful"(?) people

They are just doing something terribly wrong (like not having their drivers properly installed) as it's extremely simple:
Do this: disable windows & drivers updates, do proper DDU, add multiple GPUs (better with stock bioses), install driver (see my post above), run claymore.
for polarises you can set extremely safe 1140MHz core and 1750 mem at 900mv
You can also try other algoes / miners.


It's not what you don't know that kills you, it's what you know for sure that ain't true.

― Mark Twain
Ursul0
Sr. Member
****
Offline Offline

Activity: 771
Merit: 260


View Profile
May 27, 2018, 12:24:19 PM

So, in summary, do these old boards/CPUs have a GPU limit?

see if the bios has something like "above 4g decoding". short version is it increases the range of memory the mobo can assign to the cards, which is likely the issue. that bios setting is fairly recent in consumer mobos as having 4+ video cards wasnt very common back then when those mobos came out.


that is correct, do remember that in order to be able to access GPUs this way ALL system drivers must support 64bit address space and this means Windows MUST be installed in UEFI mode.
iSuX
Jr. Member
*
Offline Offline

Activity: 42
Merit: 8


View Profile
May 27, 2018, 12:38:45 PM

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.




RE clones:
Using Acronis TrueImage, I've got the same UEFI Win10 image running on ASROCK H110, MSI Z270, ASROCK B150,  ASROCK H81. With various AMD and NVIDIA GPUs and ZERO issues. I reiterate myself: the only known problem with cloning is absence of official Microsoft support. (and I know this because see earlier)
Also how comes dagpatcher is "outdated" or whatever is your claim

RE problem:
I'm just cautioning these guys from listening to incompetent "yet very helpful"(?) people

They are just doing something terribly wrong (like not having their drivers properly installed) as it's extremely simple:
Do this: disable windows & drivers updates, do proper DDU, add multiple GPUs (better with stock bioses), install driver (see my post above), run claymore.
for polarises you can set extremely safe 1140MHz core and 1750 mem at 900mv
You can also try other algoes / miners.


It's not what you don't know that kills you, it's what you know for sure that ain't true.

― Mark Twain


Yes, better to keep these,  technical discussions, rather than personalising them.
It also helps you make your point!

OK, but like I said, as indeed did the original poster, they are a small outfit, they have a single rig, and Acronis cost what?
Another fifty bucks, to do what, make a single clone, from a disc they don't have?

Again, for the last time, cloning in the context raised is not a good solution, in fact it's not even possible.
End of discussion if you please.

A bit of attention to detail would not go amiss, nowhere did I say the dagpatcher was outdated, YOU said that!
What I wrote was it was redundant, that's it.

KISS. Did you read the Readme.txt?
Summarise/Itemise your hardware/versions/expectations/batchfile & results. The more specific, detailed, the better
Ursul0
Sr. Member
****
Offline Offline

Activity: 771
Merit: 260


View Profile
May 27, 2018, 01:32:34 PM
Last edit: May 27, 2018, 02:00:56 PM by Ursul0

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.




RE clones:
Using Acronis TrueImage, I've got the same UEFI Win10 image running on ASROCK H110, MSI Z270, ASROCK B150,  ASROCK H81. With various AMD and NVIDIA GPUs and ZERO issues. I reiterate myself: the only known problem with cloning is absence of official Microsoft support. (and I know this because see earlier)
Also how comes dagpatcher is "outdated" or whatever is your claim

RE problem:
I'm just cautioning these guys from listening to incompetent "yet very helpful"(?) people

They are just doing something terribly wrong (like not having their drivers properly installed) as it's extremely simple:
Do this: disable windows & drivers updates, do proper DDU, add multiple GPUs (better with stock bioses), install driver (see my post above), run claymore.
for polarises you can set extremely safe 1140MHz core and 1750 mem at 900mv
You can also try other algoes / miners.


It's not what you don't know that kills you, it's what you know for sure that ain't true.

― Mark Twain


Yes, better to keep these,  technical discussions, rather than personalising them.
It also helps you make your point!

OK, but like I said, as indeed did the original poster, they are a small outfit, they have a single rig, and Acronis cost what?
Another fifty bucks, to do what, make a single clone, from a disc they don't have?

Again, for the last time, cloning in the context raised is not a good solution, in fact it's not even possible.
End of discussion if you please.

A bit of attention to detail would not go amiss, nowhere did I say the dagpatcher was outdated, YOU said that!
What I wrote was it was redundant, that's it.


That's exactly my point. Whomever raised question of clones was not me, but your comment apparently caught my attention NOT because it was out of place, but because it was wrong. Also again why is pixelpatcher redundant? I'm not aware of AMD starting to skip the signature check in their drivers (it was re-enabled with 16.12.1)


EDIT: @marius85 try 18.2 - 18.3 versions
svdinu
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile
May 27, 2018, 02:13:56 PM

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.




RE clones:
Using Acronis TrueImage, I've got the same UEFI Win10 image running on ASROCK H110, MSI Z270, ASROCK B150,  ASROCK H81. With various AMD and NVIDIA GPUs and ZERO issues. I reiterate myself: the only known problem with cloning is absence of official Microsoft support. (and I know this because see earlier)
Also how comes dagpatcher is "outdated" or whatever is your claim

RE problem:
I'm just cautioning these guys from listening to incompetent "yet very helpful"(?) people

They are just doing something terribly wrong (like not having their drivers properly installed) as it's extremely simple:
Do this: disable windows & drivers updates, do proper DDU, add multiple GPUs (better with stock bioses), install driver (see my post above), run claymore.
for polarises you can set extremely safe 1140MHz core and 1750 mem at 900mv
You can also try other algoes / miners.


It's not what you don't know that kills you, it's what you know for sure that ain't true.

― Mark Twain


Yes, better to keep these,  technical discussions, rather than personalising them.
It also helps you make your point!

OK, but like I said, as indeed did the original poster, they are a small outfit, they have a single rig, and Acronis cost what?
Another fifty bucks, to do what, make a single clone, from a disc they don't have?

Again, for the last time, cloning in the context raised is not a good solution, in fact it's not even possible.
End of discussion if you please.

A bit of attention to detail would not go amiss, nowhere did I say the dagpatcher was outdated, YOU said that!
What I wrote was it was redundant, that's it.


That's exactly my point. Whomever raised question of clones was not me, but your comment apparently caught my attention NOT because it was out of place, but because it was wrong. Also again why is pixelpatcher redundant? I'm not aware of AMD starting to skip the signature check in their drivers (it was re-enabled with 16.12.1)


EDIT: @marius85 try 18.2 - 18.3 versions


Well, I'm enjoying the tough debate my comment lead to. Smiley

Question still remains: How can one "roll back" to Win 10 1709 on a fresh install, providing that 1803 release is not good for mining?
Onbusy
Newbie
*
Offline Offline

Activity: 43
Merit: 0


View Profile
May 27, 2018, 02:17:21 PM

Is there a post somewhere discussing what people are dual mining?  I went from Sia to Decred to Verge and now I'm just mining Keccak algo on an autoexchange.  Keccak seems to draw more power (20-30w per card) than most of the other algos I was dual mining, I'm running AMD with dcri of 7.  Curious to see what options other people are dabbling in.

I tried searching for dual mining on here, but...so many results that do not apply
iSuX
Jr. Member
*
Offline Offline

Activity: 42
Merit: 8


View Profile
May 27, 2018, 02:28:09 PM

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.




RE clones:
Using Acronis TrueImage, I've got the same UEFI Win10 image running on ASROCK H110, MSI Z270, ASROCK B150,  ASROCK H81. With various AMD and NVIDIA GPUs and ZERO issues. I reiterate myself: the only known problem with cloning is absence of official Microsoft support. (and I know this because see earlier)
Also how comes dagpatcher is "outdated" or whatever is your claim

RE problem:
I'm just cautioning these guys from listening to incompetent "yet very helpful"(?) people

They are just doing something terribly wrong (like not having their drivers properly installed) as it's extremely simple:
Do this: disable windows & drivers updates, do proper DDU, add multiple GPUs (better with stock bioses), install driver (see my post above), run claymore.
for polarises you can set extremely safe 1140MHz core and 1750 mem at 900mv
You can also try other algoes / miners.


It's not what you don't know that kills you, it's what you know for sure that ain't true.

― Mark Twain


Yes, better to keep these,  technical discussions, rather than personalising them.
It also helps you make your point!

OK, but like I said, as indeed did the original poster, they are a small outfit, they have a single rig, and Acronis cost what?
Another fifty bucks, to do what, make a single clone, from a disc they don't have?

Again, for the last time, cloning in the context raised is not a good solution, in fact it's not even possible.
End of discussion if you please.

A bit of attention to detail would not go amiss, nowhere did I say the dagpatcher was outdated, YOU said that!
What I wrote was it was redundant, that's it.


That's exactly my point. Whomever raised question of clones was not me, but your comment apparently caught my attention NOT because it was out of place, but because it was wrong. Also again why is pixelpatcher redundant? I'm not aware of AMD starting to skip the signature check in their drivers (it was re-enabled with 16.12.1)


EDIT: @marius85 try 18.2 - 18.3 versions


Like I said, end of discussion!
Nothing I said was WRONG, and throwing all your toys out of your pram does nothing to further your point(less) posting.
You might like to also look up the word "apology", and be wise enough  (one day), to know when to do that.

Pay better attention to detail, it's all written down here after all, no need to paraphrase or morph what other people write.
If you don't understand it, that's fine, all you need to do is copy/paste and ask for help.

If you're  going to counter point what others post, at least give them the courtesy to take your time to read it first, understand it, and MAKE your counter points, specific and to the point. But do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"

Equally, you can look up the word redundant for yourself.

And again, some understanding or manners and protocol would do you no harm either.

Bullying a technical argument does you no credit, neither is it necessary assuming you're intentions are to be helpful.
That does not mean you assassinate other people in the process.

I suggest you let this go, you're out of order, and that is my final word on the matter.
I'm not going to be drawn into your pissing contest, this is a technical forum, sigh.
End of discussion!







KISS. Did you read the Readme.txt?
Summarise/Itemise your hardware/versions/expectations/batchfile & results. The more specific, detailed, the better
iSuX
Jr. Member
*
Offline Offline

Activity: 42
Merit: 8


View Profile
May 27, 2018, 02:40:38 PM
Last edit: May 27, 2018, 04:41:10 PM by iSuX

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.





Well, I'm enjoying the tough debate my comment lead to. Smiley

Question still remains: How can one "roll back" to Win 10 1709 on a fresh install, providing that 1803 release is not good for mining?

Yeah, I can't say I'm enjoying the banality of it, in that there is no debate as such, not a single statement was rebutted on a technical level, and  emotional, personal attacks are hardly going to help you, or anyone in fact.
Anyway, moving on, I don't think you can roll back here, as you have nothing to roll back on, you've installed a newer win build.

OK, so some time has passed, you've been hard at it, how about a recap?

What is the current situation?

You're on 1803, you have a single GPU in the rig, drivers installed, debug on, can you post the log just before and after the hang?

Don't stress it man, you'll get it running.

Sorry man, I forgot to ask, where did you get your original Win10 install? Did you buy that rig perhaps?
What I mean is, could you maybe have your Win10 1607 install media kicking about somewhere?

That said, I'm not sure that 1803 is necessarily a dead duck for mining, clearly you had some issue right back at the start, that caused you to format and reinstall Win10, I'm just curious as to how your present situation compares with the original one.

What I mean is, that rig was stable, running some months as you said, then it broke, you've done a lot of work on the problem, is it still broke in the same way?

Could you have a hardware issue, is the question I have in my mind right now.

Indeed UFEI install is necessary if you plan on having multiple GPU in the rig, but it wouldn't prevent a single GPU halting claymore init, so considering your present situation, I'd set that aside for now, and focus on specific the issues as they present themselves now.




KISS. Did you read the Readme.txt?
Summarise/Itemise your hardware/versions/expectations/batchfile & results. The more specific, detailed, the better
svdinu
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile
May 27, 2018, 03:05:38 PM

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.





Well, I'm enjoying the tough debate my comment lead to. Smiley

Question still remains: How can one "roll back" to Win 10 1709 on a fresh install, providing that 1803 release is not good for mining?

Yeah, I can't say I'm enjoying the banality of it, in that there is no debate as such, not a single statement was rebutted on a technical level, and  emotional, personal attacks are hardly going to help you, or anyone in fact.
Anyway, moving on, I don't think you can roll back here, as you have nothing to roll back on, you've installed a newer win build.

OK, so some time has passed, you've been hard at it, how about a recap?

What is the current situation?

You're on 1803, you have a single GPU in the rig, drivers installed, debug on, can you post the log just before and after the hang?

Don't stress it man, you'll get it running.


Well, that was not me asking.

As far as I go, I have one rig/work PC with only 2 cards that got itself upgraded to 1803 and it's working just fine with AMD 18.3.4. The rest of my rigs I rolled them to Win 1709 and AMD 17.11.4 as they used to be. All my rigs run 2 epochs without any crash (5-10 days). Good enough to allow some maintenance once in a while.
74hawksfan
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
May 27, 2018, 03:16:59 PM

Hello,
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified

Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!

Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1


I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.

I would post a pic to make it easier but I cannot figure out how to do that :-)



Hey there,
So you have debug on, what do your logs tell you?

Try adding

-di 0

Start with GPU0 only, would be a good thing to try, as you could be overloading your PSUs.
If it's a new rig, never been running/stable, break it down, get through the init on one GPU, prove your config and basic hw/sw enviro, and take it from there.

jooi, what PSU are you using, and how many GPU on each, how many risers per cable?

Kudos on the 13gpu rig man, not so easy to get those stable.

Good luck.


footnote:
Try this.

setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool ssl://eu1.ethermine.org:5555 -ewal wallet.rig -epsw x -di 0 -gser 1 -esm 0 -etha 0 -ethi 16 -eres 2 -erate 1 -estale 1 -asm 1 -platform 1 -y 1 -dcri 9 -wd 1 -ftime 5 -r 1440 -cclock 1200 -cvddc 900 -mclock 2100 -mvddc 850 -tstop 83 -tstart 50 -tt 60 -fanmin 40 -fanmax 100 -ttdcr 80 -ttli 80 -mode 1 -dbg 1 -altnum 3 -mport -3333 -mpsw whatever -logfile logs\




So that was a great idea taking the cards out and just doing 1, I should have tried that before posting.  Unfortunately it didn't work, same result. Here is the last log file, the others say the exact same thing :-(

20:25:58:457   1460   Check and remove old log files...
20:25:58:457   1460   args: -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
20:25:58:457   1460   
20:25:58:457   1460   浜様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様融
20:25:58:457   1460                   Claymore's Dual GPU Miner - v11.7              
20:25:58:457   1460                 ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK            
20:25:58:457   1460   藩様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様夕
20:25:58:457   1460   
20:25:58:457   1460   b583
20:25:58:685   1460   ETH: 1 pool is specified
20:25:58:685   1460   Main Ethereum pool is eth.suprnova.cc:5005
20:25:58:685   1460   DCR: 0 pool is specified
20:26:31:509   d48   
20:27:04:325   d48   
20:27:37:141   d48   
20:28:09:957   d48   
20:28:42:541   d48   



2x 1,200 watt gold psu's, even distrubuted as with my other one.
and only 2 risers per sata leg

Thank you for you help!


OK, will it sounds like your PSU and topology is thought through, so maybe leave that for now.
Could you post the debug log, from the batch file I added above?

(Just to rule out the pool angles, as I have no experience with suprnova, and Ethermine, being pretty much the biggest there is, makes for a good choice when testing, even if you don't plan on mining with those guys).

Now that said, what SHOULD be happening at this stage is the init of OpenCL, (or CUDA if you're using Nvidia).
OpenCL is managed via the AMD driver, so assuming you don't have a problem with the pool, I think you need to investigate if OpenCL is available.

One way to do that, (with a only single GPU in the rig), is you use GPU-z, and see if the OpenCL check box is populated.

Now, I have also seen perfectly good working rigs, where that checkbox is NOT populated, and clearly that is wrong, so to be absolutely sure, you (again with only 1 GPU in the rig), could boot to safe mode, DDU, reboot, install the AMD driver, set to compute, reboot, and check GPU-z, I have never seen that fail to confirm OpenCL.

From there, try my batch file again, and post the log if you're still stuck.
Good luck

Also, VM? Set to 48000GB if need be.

Foot note, in case anyone needs convincing of the single GPU method. If you do a clean AMD driver install with 13GPU, this alone can take hours, more so, if it fails, and AMD themselves STILL have an open bug on init fail with more than 12GPU.

Often when testing theories, working through troubleshooting etc, this is time consuming, and for sure you probably work at testing, (proving) some angles that were perfectly fine to start with. Time is not wasted of course, as you can cross those off the list, elimination of them, takes you closer to the answer.
But all the same, if you have multiple GPU, that's an exponential multiplier on the possibilities of fault, and means more time to troubleshoot is a given.
Breaking it down to basics, (you only need to pull the USB cables from the MB, for the most part), is pretty quick, you don't need to physically remove the GPUs etc, means you can run DDU, and reinstall the AMD driver with the minimum time consumed, and get back to starting Claymore as quickly as possible.

AMD driver install time, is pretty acceptable with a single GPU, but 12 and 13 is really nasty, and I have seen that fail many times, so working on proof of concept with a single GPU is by far the fastest, and most likely to provide solutions imho.

BTW 18.3.4 is a stable driver for mining.
Note: there is NOTHING mentioned in any release notes from AMD, on any mining related improvements in the drivers release since 18.3.4.
That is not to say the newer drivers are bad, (some are though), but simply, 18.3.4 has been out for a while, rolls up all the mining related things you probably need for RX570/580 hardware, and has proved itself far more than any of the drivers released since then. So, if you're going to DDU etc, I'd suggest 18.3.4 is a good choice, known good, known stable, well proven choice, and when you're troubleshooting, you need to focus on elimination of doubt. Go with what you know, (is good).



I was wondering why niether of the cuda opencl boxes were checked, and there has been an error that GPU-Z gives me when I open it or switch cards. I installed W10 1709 I believe then it updated to 1803, so I reverted back and have had strange things since. So I'mma do a fresh install and see what happens, I was able to flash the mod bios already so I don't really need atiflash to work anyway so I'll try 1803 fresh.
Thank you so much!
Ursul0
Sr. Member
****
Offline Offline

Activity: 771
Merit: 260


View Profile
May 27, 2018, 03:26:23 PM

do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"
my mistake. it just never happens this way. alright. Windows reinstall is not the best idea here, nor cloning. Good advice.
 
I'm sorry I said that all your ideas in this area are total crap, actually it's just everything you said about cloning and driver issues... and also something about "client security trough fresh windows install" and... uhh...sorry again...

@svdinu Reinstall older build. Quick search finds this (Anniversary is good enough for almost all use cases): http://windowsiso.net/windows-10-iso/windows-10-anniversary-update-1607-download-build-14393-0/windows-10-anniversary-update-1607-iso-download-standard/
You can look for SHA1 hash values of the original MS ISOs and check if it's proper
Code:
Edition: Windows 10, product language = English

Windows 10 English 64-bit download

File name = Win10_1607_English_x64

SHA1 hash value: 99fd8082a609997ae97a514dca22becf20420891
svdinu
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile
May 27, 2018, 03:39:47 PM

do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"
my mistake. it just never happens this way. alright. Windows reinstall is not the best idea here, nor cloning. Good advice.
 
I'm sorry I said that all your ideas in this area are total crap, actually it's just everything you said about cloning and driver issues... and also something about "client security trough fresh windows install" and... uhh...sorry again...

@svdinu Reinstall older build. Quick search finds this (Anniversary is good enough for almost all use cases): http://windowsiso.net/windows-10-iso/windows-10-anniversary-update-1607-download-build-14393-0/windows-10-anniversary-update-1607-iso-download-standard/
You can look for SHA1 hash values of the original MS ISOs and check if it's proper
Code:
Edition: Windows 10, product language = English

Windows 10 English 64-bit download

File name = Win10_1607_English_x64

SHA1 hash value: 99fd8082a609997ae97a514dca22becf20420891


Great! Thanks. As far as I remember, Windows will update itself on first run without asking. Let's see how it goes, it was not me in need, but I'm waiting for users to report.

All the best!
iSuX
Jr. Member
*
Offline Offline

Activity: 42
Merit: 8


View Profile
May 27, 2018, 03:54:45 PM

Hello,
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified

Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!

Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1


I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.

I would post a pic to make it easier but I cannot figure out how to do that :-)



Hey there,
So you have debug on, what do your logs tell you?

Try adding

-di 0

Start with GPU0 only, would be a good thing to try, as you could be overloading your PSUs.
If it's a new rig, never been running/stable, break it down, get through the init on one GPU, prove your config and basic hw/sw enviro, and take it from there.

jooi, what PSU are you using, and how many GPU on each, how many risers per cable?

Kudos on the 13gpu rig man, not so easy to get those stable.

Good luck.


footnote:
Try this.

setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool ssl://eu1.ethermine.org:5555 -ewal wallet.rig -epsw x -di 0 -gser 1 -esm 0 -etha 0 -ethi 16 -eres 2 -erate 1 -estale 1 -asm 1 -platform 1 -y 1 -dcri 9 -wd 1 -ftime 5 -r 1440 -cclock 1200 -cvddc 900 -mclock 2100 -mvddc 850 -tstop 83 -tstart 50 -tt 60 -fanmin 40 -fanmax 100 -ttdcr 80 -ttli 80 -mode 1 -dbg 1 -altnum 3 -mport -3333 -mpsw whatever -logfile logs\




So that was a great idea taking the cards out and just doing 1, I should have tried that before posting.  Unfortunately it didn't work, same result. Here is the last log file, the others say the exact same thing :-(

20:25:58:457   1460   Check and remove old log files...
20:25:58:457   1460   args: -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
20:25:58:457   1460   
20:25:58:457   1460   浜様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様融
20:25:58:457   1460                   Claymore's Dual GPU Miner - v11.7              
20:25:58:457   1460                 ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK            
20:25:58:457   1460   藩様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様様夕
20:25:58:457   1460   
20:25:58:457   1460   b583
20:25:58:685   1460   ETH: 1 pool is specified
20:25:58:685   1460   Main Ethereum pool is eth.suprnova.cc:5005
20:25:58:685   1460   DCR: 0 pool is specified
20:26:31:509   d48   
20:27:04:325   d48   
20:27:37:141   d48   
20:28:09:957   d48   
20:28:42:541   d48   



2x 1,200 watt gold psu's, even distrubuted as with my other one.
and only 2 risers per sata leg

Thank you for you help!


OK, will it sounds like your PSU and topology is thought through, so maybe leave that for now.
Could you post the debug log, from the batch file I added above?

(Just to rule out the pool angles, as I have no experience with suprnova, and Ethermine, being pretty much the biggest there is, makes for a good choice when testing, even if you don't plan on mining with those guys).

Now that said, what SHOULD be happening at this stage is the init of OpenCL, (or CUDA if you're using Nvidia).
OpenCL is managed via the AMD driver, so assuming you don't have a problem with the pool, I think you need to investigate if OpenCL is available.

One way to do that, (with a only single GPU in the rig), is you use GPU-z, and see if the OpenCL check box is populated.

Now, I have also seen perfectly good working rigs, where that checkbox is NOT populated, and clearly that is wrong, so to be absolutely sure, you (again with only 1 GPU in the rig), could boot to safe mode, DDU, reboot, install the AMD driver, set to compute, reboot, and check GPU-z, I have never seen that fail to confirm OpenCL.

From there, try my batch file again, and post the log if you're still stuck.
Good luck

Also, VM? Set to 48000GB if need be.

Foot note, in case anyone needs convincing of the single GPU method. If you do a clean AMD driver install with 13GPU, this alone can take hours, more so, if it fails, and AMD themselves STILL have an open bug on init fail with more than 12GPU.

Often when testing theories, working through troubleshooting etc, this is time consuming, and for sure you probably work at testing, (proving) some angles that were perfectly fine to start with. Time is not wasted of course, as you can cross those off the list, elimination of them, takes you closer to the answer.
But all the same, if you have multiple GPU, that's an exponential multiplier on the possibilities of fault, and means more time to troubleshoot is a given.
Breaking it down to basics, (you only need to pull the USB cables from the MB, for the most part), is pretty quick, you don't need to physically remove the GPUs etc, means you can run DDU, and reinstall the AMD driver with the minimum time consumed, and get back to starting Claymore as quickly as possible.

AMD driver install time, is pretty acceptable with a single GPU, but 12 and 13 is really nasty, and I have seen that fail many times, so working on proof of concept with a single GPU is by far the fastest, and most likely to provide solutions imho.

BTW 18.3.4 is a stable driver for mining.
Note: there is NOTHING mentioned in any release notes from AMD, on any mining related improvements in the drivers release since 18.3.4.
That is not to say the newer drivers are bad, (some are though), but simply, 18.3.4 has been out for a while, rolls up all the mining related things you probably need for RX570/580 hardware, and has proved itself far more than any of the drivers released since then. So, if you're going to DDU etc, I'd suggest 18.3.4 is a good choice, known good, known stable, well proven choice, and when you're troubleshooting, you need to focus on elimination of doubt. Go with what you know, (is good).



I was wondering why niether of the cuda opencl boxes were checked, and there has been an error that GPU-Z gives me when I open it or switch cards. I installed W10 1709 I believe then it updated to 1803, so I reverted back and have had strange things since. So I'mma do a fresh install and see what happens, I was able to flash the mod bios already so I don't really need atiflash to work anyway so I'll try 1803 fresh.
Thank you so much!

No worries, wow, that is a nasty situation with win updates. But before you roll back, it would be very helpful to know, if the DDU, clean install, or alternatively a manual driver install in devman as Ursul0 pointed out, gets you anywhere.

Because one would hope that DDU/clean install-driver option is an available solution.

But indeed, you could be right, I have seen some systems in a real mess after a OS roll back, and while that isn't to say that applies in your case, it's always one of those nasty things that sow the seeds of doubt later.

Also, you might like to set all your NICs to metered connection, that at least for the most part, prevents MS from updating your rig, or if nothing else, gives you some warning when they try to.

Regedit
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost]

Grant your user "folder" permissions, and change all NICs to dword 2.
e.g.
"3G"=dword:00000002
"4G"=dword:00000002
"Default"=dword:00000002
"Ethernet"=dword:00000002
"WiFi"=dword:00000002

It won't help you with your current problem, but might be useful on your rigs
Good luck.

KISS. Did you read the Readme.txt?
Summarise/Itemise your hardware/versions/expectations/batchfile & results. The more specific, detailed, the better
iSuX
Jr. Member
*
Offline Offline

Activity: 42
Merit: 8


View Profile
May 27, 2018, 04:35:35 PM

do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"
my mistake. it just never happens this way. alright. Windows reinstall is not the best idea here, nor cloning. Good advice.
 
I'm sorry I said that all your ideas in this area are total crap, actually it's just everything you said about cloning and driver issues... and also something about "client security trough fresh windows install" and... uhh...sorry again...

@svdinu Reinstall older build. Quick search finds this (Anniversary is good enough for almost all use cases): http://windowsiso.net/windows-10-iso/windows-10-anniversary-update-1607-download-build-14393-0/windows-10-anniversary-update-1607-iso-download-standard/
You can look for SHA1 hash values of the original MS ISOs and check if it's proper
Code:
Edition: Windows 10, product language = English

Windows 10 English 64-bit download

File name = Win10_1607_English_x64

SHA1 hash value: 99fd8082a609997ae97a514dca22becf20420891

OK, Ursul0, you surprised me, THANK YOU, apology heartly accepted.
Kudos also, most people are too pig headed to do it these days.

Hey so to be clear, I don't disagree with your views on cloning, simply that as a posted cloning solution to the problem tabled.
Assuming that will work in all and every case, is a generalisation, very much dependant on specific hardware, means and ability of the person doing it.
Those guys are running a single rig, and on a learning curve, and as you well know, that is a really tough combination.
Even if you have a tiny "other" rig, at least you have the vastness of differentiation available when you're trying to troubleshoot.

Anyway, all water under the bridge, they had already done an OS install.

As you asked, to clarify, why I don't clone for clients on mining rigs, (and I DO CLONE, also with Acronis, just as you do), but not for clients.
Why? Protection, mine and theirs.
Mining involves money, my clients money.

If I make a mistake, somewhere, and have cloned 50 rigs off that, and later I find out I messed up, that is a 50x mistake multiplier I'm not prepared to risk. You can mess up just as easily by something you don't do.
With single install, I'm isolating risk, constraining it to THAT rig.`
So to be clear here, this is my CHOICE in this context, but equally none of us want to clone/deploy our mistakes either.

While it might not be THE solution, it's the one I've adopted to date. I've not had to consider building more than one or two rigs, single builds, or tiny batches if you like, so clone rollout is not a big time saver for me, and certainly does nothing to build customer confidence.

Of course I have a bunch of reg files, and envrio tweaks, so the additional deploy time is minimal, and I usually multi task while doing those build stages, so I'm not idle in that time.

One thing I often see in tech support is what seems simple to you, me, is often too complex or outside the comfort zone of the people asking for help.
Usually I probe with a few questions to get a feel for their ability and experience level, and get some dialogue going, before settling on what advice to give, and walk them through it, (not so easy on a part time forum basis).
But assuming they have, blah, blah means and ability, etc etc, actually assuming anything about them at all, is my error, and usually going to cause them more issues.

Take your logical method of driver install, (extract and do it in devman), absolutely, I could not agree more, however, while that is known to you, it's not the AMD advertised method, they steer the user to setup.exe, which does usually work, time consuming as it is, but is that the "best" method?
Well, probably for the majority, yes it is according to AMD, which is why AMD release that way.
Is it the best method you have? No.

OK, so question to you, there are a lot of postings "blaming" issues on stable rigs, after updating to this recent (April) 1803 update.
For sure, some of those cases are possibly blaming 1803 unfairly, but that isn't the question.
Have you tried that update?
What issues, if any, did you encounter?

I have a feeling this is going to be a mini-plague for the coming months, and while "don't update" is one obvious answer, I'm curious to know, specifically why that breaks, (assuming it does), and how to solve that, (other than fallback etc).
If the answer is fallback, is that the only answer, or have you recovered a rig in that situation?
Cheers

KISS. Did you read the Readme.txt?
Summarise/Itemise your hardware/versions/expectations/batchfile & results. The more specific, detailed, the better
Jonet
Newbie
*
Offline Offline

Activity: 48
Merit: 0


View Profile
May 27, 2018, 04:54:58 PM


Question still remains: How can one "roll back" to Win 10 1709 on a fresh install, providing that 1803 release is not good for mining?

You cant.
But it looks like you can download both 1709 and 1803 from MicroSoft.

https://www.microsoft.com/en-gb/software-download/windows10ISO

If you have accidentally updated from 1709 to 1803 you can rollback (within 1 month?) by selecting Setup - Recovery - Go back to the previous version of Windows 10
iSuX
Jr. Member
*
Offline Offline

Activity: 42
Merit: 8


View Profile
May 27, 2018, 04:56:18 PM

Hello guys, i have a problem, the cards are 1050ti 4gb, updated to latest drivers and latest claymore, tried changing virtual memory, but there is still problem. What to do? Thanks in advance!

CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:234   ab8   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:240   1f48   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:258   1f18   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:295   1b30   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:24:991   a58   Set global fail flag, failed GPU2
19:36:24:999   a58   GPU 2 failed
19:36:24:998   1fec   Setting DAG epoch #189 for GPU2
19:36:25:010   1fec   GPU 2, CUDA error 11 - cannot write buffer for DAG

19:36:25:241   ab8   Set global fail flag, failed GPU0
19:36:25:247   ab8   GPU 0 failed
19:36:25:254   af0   Setting DAG epoch #189 for GPU0
19:36:25:251   1f48   Set global fail flag, failed GPU4
19:36:25:266   1f48   GPU 4 failed
19:36:25:277   af0   GPU 0, CUDA error 11 - cannot write buffer for DAG

19:36:25:272   1f18   Set global fail flag, failed GPU5
19:36:25:289   1f2c   Setting DAG epoch #189 for GPU4
19:36:25:305   1f2c   GPU 4, CUDA error 11 - cannot write buffer for DAG

19:36:25:311   1e08   Setting DAG epoch #189 for GPU5
19:36:25:305   1b30   Set global fail flag, failed GPU3
19:36:25:326   1b30   GPU 3 failed
19:36:25:337   1e08   GPU 5, CUDA error 11 - cannot write buffer for DAG

19:36:25:343   1f18   GPU 5 failed
19:36:25:350   1ff0   Setting DAG epoch #189 for GPU3
19:36:25:360   1ff0   GPU 3, CUDA error 11 - cannot write buffer for DAG

19:36:25:394   1ff4   buf: {"id":0,"jsonrpc":"2.0","result":["0x8cc05aa8be75170e0cf74ab6ac892516828e014b33e2ece87efcf493ff753f1d","0x7bb6f14a940828054edc1aa9ec9f31e274e036a730709926e1f2900225e2f745","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x56c530"]}

19:36:25:403   1ff4   ETH: 05/27/18-19:36:25 - New job from eu1.ethermine.org:4444
19:36:25:407   1ff4   target: 0x0000000112e0be82 (diff: 4000MH), epoch 189(2.48GB)
19:36:25:414   1ff4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
19:36:25:423   1ff4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
19:36:28:018   1fec   Set global fail flag, failed GPU2
19:36:28:023   1fec   GPU 2 failed
19:36:28:289   af0   Set global fail flag, failed GPU0
19:36:28:294   af0   GPU 0 failed
19:36:28:312   1f2c   Set global fail flag, failed GPU4
19:36:28:322   1f2c   GPU 4 failed
19:36:28:344   1e08   Set global fail flag, failed GPU5
19:36:28:351   1e08   GPU 5 failed
19:36:28:367   1ff0   Set global fail flag, failed GPU3
19:36:28:376   1ff0   GPU 3 failed

Hey there, by any chance, are you dual mining?
BTW 3GB cards can't mine ETH any more, and probably, given time, 4GB will go the same way, but at least right now, 4GB cards are ok.
Things to check, Nvidia driver, (cuda) install ok, or DDU, and clean install Nvidia drivers.

Post your batchfile content, it's helpful to get a better understanding about your rig and expectations.
Also, how much VM are you running?



KISS. Did you read the Readme.txt?
Summarise/Itemise your hardware/versions/expectations/batchfile & results. The more specific, detailed, the better
Ursul0
Sr. Member
****
Offline Offline

Activity: 771
Merit: 260


View Profile
May 27, 2018, 05:04:42 PM


Great! Thanks. As far as I remember, Windows will update itself on first run without asking. Let's see how it goes, it was not me in need, but I'm waiting for users to report.

All the best!

to get rid of the windows updates: 1) disconnect Internet (not really a must, but will be even better) 2) run gpedit.msc, find Windows Updates under Administrative templates and set (at least...as there's much more stuff to get rid of) "Configure Automatic Updates" to "disabled" and "Do not include drivers with windows update" to "enable"  3) run "gpupdate -force" from CMD and reboot
Pages: « 1 ... 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 [1195] 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 ... 1401 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!