Not sure I believe Intel after they laid off over 14000 employees last year. I bet they are just looking for a jump in their stock. We will see I guess... btw.. how can a processor hold passwords?.. is there ram in there?

Yes, actually, there is. Its called "cache memory", and its directly wired into the CPU.

And not only one, for example my Core i7-4790 has three Levels of cache, two L1 (both 32 KBytes), one L2 (256KBytes) and one L3 (8 MBytes).

Anyway altough they say that OS patch for Meltdown may decrease performance, it is only in very specific cases, normal users should not be affected.

I have a problem on one of my rigs since I started using 0.5.8. The miner crashes every like 2 days. So, what info can I provide to you so you can check it out? It was stable on 0.5.7 since it was released.

For people that are wondering about the "Meltdown" security patch performance decrease on their mining rigs on Windows 10From the one miner that i have which is running Intel G4400 and 8 GPUs (1x 980ti, 7x 1060 3GB).

yeah pretty nasty. ms has a patch out for meltdown but it can slow your machine down. wonderful.

but trezor or ledger nano s for the win.

or fire up that old pentium 2 or 3 although i think the jury is still out on whether those are immune.

or maybe olde skoole: S-100 or CP/M anyone?

Not sure I believe Intel after they laid off over 14000 employees last year. I bet they are just looking for a jump in their stock. We will see I guess... btw.. how can a processor hold passwords?.. is there ram in there?

meltdown can allow other programs on the machine (even in other VMs) to read the processor cache (fast ram built into the cpu for fast access to data/instructions it thinks it will need next compared to going out to main memory). its possible (guessing here) that network share passwords and credentials may be there on occasion. if you have those, your network is compromised. although other malware would have to work in concert with it to do that. at least as far as i understand it.

keep in mind im no expert, but i do take my rigs and network seriously. this treat seems more serious for cloud computing then home users but hey additional security is additional security. every little bit helps.

Thanks for this, I find this version much more stable compared to 0.5.4 which I'd last tried on my Windows 10, Nvidia rig (2 x 1070, 1 x 1080) and also 6-7% better performance than EWBF.

I wanted to ask how to get email notifications whenever there are updates? The forum only offers notifications for the entire post/all new replies and I don't want that.

Let me know if there's a way to do that. Thanks!

@DSTM - I'm still using ver 0.5.7 and gratefully paying the 2% devfee, but I have a question/suggestion - Why does the console output keep changing the order of the GPU stats it displays. It starts out as GPU0 onwards in order, but after an hour or two or three, it appears to randomize the order. See screenshot #1 linked below. This makes it quite confusing (and annoying) while viewing the console output to gauge real-time changes.

p.s. Also - re: the versioning updates question - can't you put this up on Github or somewhere similar so we can get push notifs for updated versions? This is a very minor issue though, the above issue is higher priority, at least for me. The randomized ordered display of GPUs is quite annoying

yeah pretty nasty. ms has a patch out for meltdown but it can slow your machine down. wonderful.

but trezor or ledger nano s for the win.

or fire up that old pentium 2 or 3 although i think the jury is still out on whether those are immune.

or maybe olde skoole: S-100 or CP/M anyone?

Not sure I believe Intel after they laid off over 14000 employees last year. I bet they are just looking for a jump in their stock. We will see I guess... btw.. how can a processor hold passwords?.. is there ram in there?

meltdown can allow other programs on the machine (even in other VMs) to read the processor cache (fast ram built into the cpu for fast access to data/instructions it thinks it will need next compared to going out to main memory). its possible (guessing here) that network share passwords and credentials may be there on occasion. if you have those, your network is compromised. although other malware would have to work in concert with it to do that. at least as far as i understand it.

keep in mind im no expert, but i do take my rigs and network seriously. this treat seems more serious for cloud computing then home users but hey additional security is additional security. every little bit helps.

Do you guys run any kind of malwarebytes, or Norton, windows defender security?

This is my first post on this forum, despite being interested in crypto coins practically since beginning of BTC, so Hi everyone.

I'm thinking about building rig that would be most efficient. Everyone is comparing Sol/s or Sol/W, but as dstm stated (went practically through whole thread yesterday ), performance should be measured by I/s.Do you know if anyone performed comparison based on I/s per W and how it relates to Sol/s and Sol/W in long term (as those are probablistic) for specific card models, brands? Could I ask you to submit your data here in following format:

When adding yours, please include result posted by previous users and add yours at the end. Normally I would add link to some anonymous notepad like shrib under #nv_dstm_zcash_perf, so others can process and compare it as they wish, but unfortunately i can't post any links

24h runs averages would be best. If brand model name has been previously added by someone, use the same model / brand name so in longer term we can easy compare between products and models by filtering only by them. If possible provide results without OC/Undervolting.

I'm about the last person to defend the devfees charged by some of these miners, because many of them are still beta or even alpha-level in functionality/reliability, but I suspect the explanation here is that the devfee shares are mined at a much lower difficulty to better ensure a share is earned during the short mining period allotted.