Mine is connected via a serial connector and a new pci serial board. The last thing that I have tried is not powering down the graphics card. I have nothing else that I can find that Win10 wants to put into sleep mode.
@bitsostring
why not try a version of WD before mid jan then?
I think Brian knows that the WMR200 is USB. . . you have a VP2?
WD has now been running OK on my desktop - with the same settings - since 1530. . . I may even leave it on overnight to see what happens 
I maybe should have said that the lock-up problem is occurring in build 106 from 11 January, when you added individual settings for custom label colours. . . now you have me wondering if that’s when it started :?
Desktop is now running build 108. . .
you can always try a version before that
Yes, I could go back to build 104 from 18 December last.
Let me see how build 108 does with the same settings on the desktop first. . .
you may need to do a memory test and surface scan of the hard drive
from the info posted I see the drive is partitioned, how much free capacity is on the C partition where WD is, if its getting low it will impact on windows10
84 GB free on the SSD partition. . . 
I have pulled out my ram and replaced it with 8 gig of different ram to see what happens. The ram that I had there was error checked and did not show any errors so I will see what happens.
OK, different memory didn’t do the trick. What I actually think might be causing the problem is this program, antimalware service executable. I think that it was chewing away at the memory until there is none left.
I have been looking on Google and have pretty much done everything that I can to reduce it’s impact, so now some more waiting to see if this helps.
I had a home built computer that worked perfectly for about 11 months. Then it started randomly locking up. wiped the hard drive, re-installed Windows 10 pro(2 times). Then started replacing components one at a time. Replaced everything but the processor and motherboard. Still random lockups. Took it to Computers Plus. They worked on it for 3 months and couldn’t figure it out. Finally found out the my AMD processor had difficulties working well with the exact motherboard that I was using. bought a different motherboard, put all of the original components back in it, and it is still running perfectly.
Have you tried a new install of Windows? If not, find a cheap hard drive, swap it out and re-install Windows on it.
Not yet. . . a few other things to try first
Quote from: bitsostring on 17 February 2020, 22:36:09
Let me see how build 108 does with the same settings on the desktop first
Build 108 has been running 24/7 for 5 days now on the desktop with the same settings and with no problems.
Yes, I could go back to build 104 from 18 December last.
Memory and SSD on weather machine checked OK, so I started up build 104 today. Locked up after an hour.
Machine will run OK for days uploading webcam with iSpy but when I start WD it locks up, sooner or later.
Interested to read another thread tonight about locking up, because I use a lot of custom tags. . . clutching at straws, here :?
P.S. for Billw69: new install of Win 10 1909 today, haven’t got the will to try WD again yet. 
it could be a procedure in the code that has got too long
(as people are always wanting new things added, customisation i.e people are never happy)
so i have split out one of the longer ones that changed recently in build 110
Thanks Brian, I’ll give it a go.
One possible problem with a computer locking up could be due to an overheating problem…
Have you checked the CPU heat-sink and fan for excessive dust build up?
I find this is a big problem for most customers that have lock up problems, sometimes the CPU heat-sink and fan get plugged up with dust bunnies, a good cleaning with some canned air (be careful, don’t let it spray liquid, this could crack something) this sometimes fixes it right up…Also blow out the power supply, it too can get all plugged up with dust.
I also brush things down with a large makeup brush, a good one should be static proof, and this is all done outside, you don’t want the dust bunnies running around the house.
One other possibility is an under rated power supply, the more you add to the computer hardware wise the greater the power draw, adding more ram, a plug in card, too many USB device’s or a better video card will increase the power draw on the computers power supply, and something may be overheating, thus the computer may/will lock up.
I had thought about an overheating CPU. When I installed and tested mine, it runs at around 40C. I also do not have any power hungry devices running.
I installed build 110 and it still ended up locking up.
I still really think that this is something to do with Windows Antimalware Service Executable, but I have not found and answer to why my WD computer continues to allow ASE to to consume memory, whereas my computer it doesn’t.
Speccy indicates everything OK in that area - or at least it did before I deleted the app at Microsoft’s suggestion (they would, wouldn’t they!). It’s an unattended (so usually no monitor) fanless Gigabyte BRIX with one internal SSD and one external, so not much extra load. But thanks for the suggestion.
Build 110 has now been running 30+ hours on a fresh install of Win 10, so I can’t say which change did the trick. . . but thanks for all the suggestions and for the changes to the code! Fingers crossed it will keep going. . .
Now I only have to solve problems with my temp/hum sensor and my website
@Eagleizer: I agree that the Antimalware Service Executable uses an inordinate amount of memory, but my weather computer usage keeps fluctuating up and down - it doesn’t keep going up. I presume it uses a proportion of the available memory: it uses twice as much on my desktop, which has twice the memory. Try a fresh install of Win 10. . .
there were a couple of other people affected by where some of the code in the program had got too long in the tooth
and one of those affected reports its fixed now with the change I made
(this same problem occured years ago )