Join us for a chat
Open sources of vvvv on GitHub
Follow our news on Mastodon
Follow a shared screenshot gallery on Pixelfed
Do big business on LinkedIn
Watch tutorials on YouTube
Join and organize meetups on MobilizonSince it was suggested that it is most likely an hardware or diver issue I went ahead and retested with 349. According to the changelog the only major difference to 351 should be Satori.
Tried over 10 times (deleting the package-cache between tries and rebooting windows once) but no bluescreen.
But maybe 349 has just more luck?
The machine I am testing on had 128 GB of RAM installed (4 * 32 GB). XMP disabled. Tried with only 32GB (with different Ram sticks in different slots). Did not make a difference.