this post was submitted on 27 Mar 2024
14 points (85.0% liked)
PC Master Race
14975 readers
728 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.
Notes:
- PCMR Community Name - Our Response and the Survey
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It really shouldn't lockup the whole machine or BSOD still, 3DSMax plugins don't run as kernel drivers (I hope?). Although the lockups could eventually lead to BSODs if it corrupts files everytime you have to hard reset. The kernel has the final word unless compromised by a driver, it really should be able to kill 3DSMax and leave you with a usable computer.
I don't know Windows enough, but you should be able to configure it so it can't use quite all of your RAM and CPU so there's always a bit of memory and a CPU core available for Windows to function. That would greatly help not being stuck unable to open task manager. Run 3DSMax as a low priority task as well, so that Windows will prefer giving CPU time to literally any process first and 3DSMax gets whatever is left (which should still be plenty).
I'd still make sure to Google any BSOD codes and investigate their cause. Maybe over time your CPU gets a little toasty, or the CPU vendor got a little too greedy with the turbos and boosts, or just can't sustain the load all that long. I had to underclock mine because I had occasional lockups during long builds and it's been solid since.
It's generally preferable to leave some performance on the table if that avoids full crashes. Each crash is a potential corruption of your project's files, a long interruption in your workflow, and an annoyance.