And I believe this is the company registration.

http://company.lursoft.lv/4150...

PROOF

http://www.lsm.lv/en/article/e...

For those discussing Ubiquiti, they probably also used Quanta as an OEM for some switch designs. There's some talk of the LB4M and LB6M firmware being very similar on a few forums.

I'm guessing the spoofed company is Quanta. There's a lot of surplus last-gen equipment on eBay (meaning companies would be upgrading), and I believe Facebook used them as an OEM for their Open Compute nodes (Quanta Mindmill). Not sure who else uses Quanta OEM in particular, but some of their switches appear to be reference designs for Dell, etc.

I met a marketing exec at the Freescale Technology Forum in Austin last May. Their take on things was the good 'ol way was still the best way. I need to find his business card since he said he'd buy me lunch if Bitcoin was still around a year later.

I get to deal with weird stuff like this at work all the time. Based on the behavior, I'd guess there's a clock and/or data running at a harmonic of the wifi data. Freezing seems to indicate it's coupling into the core of the LCD controller board, which again I would guess is a timing violation or data corruption. Where it's coupling in is a bit hard to determine without further testing. It could be the video cable, could be the power cable (not likely), could be the LCD panel itself acting as an antenna, or an interconnect cable that is poorly shielded or just the right length to couple in wifi. It could also be power supply ripple caused by a feedback loop getting energy coupled in, though if that's possible then there's not enough timing margin to begin with.

I suggest a number of tests to narrow down details of the source:
- Test 2.4GHz and 5GHz independently. Test each wifi channel independently.
- Try a different length cable. Try a different brand cable. Does this monitor remain on with nothing connected? If so then try it with no cable, or no PC at the end.
- Try different antenna angles. Try different TX power levels (at what level does it start).
https://tech.slashdot.org/stor...
Based on those results I'd have more recommendations.

If someone wants the real root cause, feel free to send me one and I'll debug it (though it will probably require disassembly).

They'll probably just raise prices for no improvement in service, making more of us commoners poorer. In the end they win, the public looses.

Reminds me of debugging errors related to digital logic race conditions. When you are on the edge of meeting timing, a slight shift in the wrong direction can cause the result to be incorrect, sometimes with an order of randomness. Until you violate that timing you have the feeling of security since everything is going smoothly. I'm sure there's a more mathematical way to explain this, but similarly I think much more testing could be done to understand what variables effect the outcome. It would be interesting to see more details, such as how many pixels must be modified for a failure? To what magnitude do the pixels have to be changed by? Is there a tradeoff between # of pixels and magnitude of change per pixel? Are certain pixels more important than others (edge detection for example)?

National Instruments is providing information on how to get Government-paid NI training and certification. You have to complete a couple steps (depending on your state) to get assistance, but there is a good amount of information and assistance available here.

Given the flowcharts (not the shiny video that catches your attention first) it appears that instead of shutting down, they simply reboot the system and once it reaches the state where the OS has finished loaded it then goes to sleep or hibernate. Once you power it back on it just returns to the freshly loaded OS.
So it appears that while it starts up faster, you should end up spending more time shutting down (actually rebooting and reloading the OS). You could also do this manually by rebooting Windows and once it gets to the desktop/login screen go into hibernate/sleep.