- User Since
- Apr 9 2020, 10:28 AM (7 w, 2 d)
Sat, May 23
I built it from source and suddenly, the problem is gone, with all versions. It's really weird, sometimes it just fixes itself like that, but it always comes back. I'll write here once it begins again, thanks everyone for help
Tue, May 19
Removing preferences nor running the factory startup helped. I've tried latest GPU drivers, both studio and game optimized, nothing. I don't want to reinstall windows, I still have the option of running blender in a sandbox and manually retrieve the files from sandboxie, but that's a pain. Tomorrow I'll try to build code between 2.42a and 2.43, but I've never built anything from source, so I'm not giving it much hope. I've run Procdump and got a ~600mb memory dump file, but I can't read it, would that be useful?
So, there's two things that I think could help solve it:
The problem is somewhere between 2.42a and 2.43, are there more versions between those points that I could try?
If I run it in sandboxie, it works perfectly fine. If anyone knows how to use sandboxie, could I gradually allow access to more and more to find where the problem is?
Not sure about the trace file, never heard of that, where do I find it?
All the other versions I tried were run from D:\Test Blender Versions, but I also now tried moving a fresh 2.82a zip directly to C, didn't help, still crashes.
I've clean installed the latest (studio) drivers as of today, as Alaska asked, but it's the studio driver, so it was 442.92. So to test it out, I've downloaded the latest game ready driver, 445.87, didn't help.
Huh? Blender is supposed to support cards as old as nvidia's 400 series, I have a card that's like 6 generations newer. The oldest version that crashes this way is 2.43, at that point, this card wasn't even close to release yet. Is there something in the logs that suggests blender thinks it's an old AMD card? Anyway, I tried a clean installation as I've only installed updates normally, didn't help, but thanks for trying