Thanks for the suggestion. Looking for “lightmass” code sends me in the right direction.
There is no crash dump. This is a total system lock-up. In past lives, I’ve debugged kernel issues using WinDBG over FireWire, but I sure hope I won’t have to do something as terrible to debug this particular issue … in fact, not even that may tell me what’s going on, because the kernel seems just gone (both Windows and Linux.)
Pretty sure this is some kind of hardware or BIOS related problem, but I can’t figure out what it is.
Prime95 runs fine. xmrig-cpu runs fine. HDBench runs fine. Unigine demos run fine. Unreal editor and levels and games run fine. memtestx86 runs fine.
But, pressing “build lighting” in the Unreal Editor, will export lighting, and then lock up the machine.
I actually saw one lock-up, once, about halfway through installing the Unigine Superposition demo.
I wonder if it’s doing lots of disk I/O that does it? But then why do HD benchmarks work fine?
And why does it happen both in Windows (on a 970 Evo drive) and Linux (on a 960 Evo drive, in a different M.2 slot?)
Yeah, this should go into some hardware debugging forum somewhere, but the only real reproducible case I have is the Unreal lighting builder. So … what’s so special about that workload?