Cycles. I do not think I tested Eevee yet

I will try seeing if I can upgrade the driver without getting bloatware shoved into my machine this time.

hmmmyeah, I just updated and it keeps happening.

Thanks for the update. Can you provide system info file? Help → Save System Info
Freeze occur with both CPU and GPU?
I can not reproduce with your given file (tested on 3.0.1)

System Information
Operating system : Windows-10-10.0.18362-SP0 64 Bits
Graphics card : AMD Radeon(TM) 535 ATI Technologies .

Sure thing, here you go:

I do not believe gpu or cpu changes anything, but I can check.
Yea, cpu hangs exactly the same way.

Some more info I wanted to give:
I am using the current steam release version. 3.0.1, like you.
That file is just my modified default file carried over from 2.7-something btw, I do not believe it would matter what file it is.
I was hoping that maybe there is some issue that was caused by this, or a way to get a more verbose log. Currently, the console just repeats something about multi-device stuff not being enabled.
It is seemingly completely random. Sometimes the render status says something about finalizing, sometimes buffering stuff... No pattern.
And different to an abort, any video file made with this does not get created properly, meaning the process is just stuck. I always have to force-close blender when it happens.

Hi, does this occur with provided file only?
Can you check if factory preferences helps?: Edit → Preferences → Save & Load (3 horizontal lines) → Load Factory preferences

It happens with rendering. No matter what, no matter when, constant 1d100 of crashing.

Previous versions worked, so if ram/Vram is the issue, that would be the issue to fix in the software.

Anyways, from what I can tell, factory settings have the same issue, unless some level of reloading/restarting is required for that to have any effect.

Just to make sure btw, Yes, I tested the factory settings thing. This is EXTREMELY frustrating.

Thanks for the info. Can you check the RAM usage when freeze occurs?

Just to make sure, does this occur on recent blender builds (3.1.0, 3.2.0)?: https://builder.blender.org/download/daily/

Ram does not even get close to being an issue, I had problems with ram before and that usually just completely cripples the current session. (would love being able to set max ram use)

but you were right, 3.2 seems to not have these issues. this is not usually what I would say should be in a beta.

Can you also test on 3.1.0Beta?: https://builder.blender.org/download/daily/

Would that mean the ticket is closed

If you can't reproduce on both 3.1.0 beta and 3.2.0, yes.

I cannot reproduce it.

I assume this means there will be a fix for this in some upcoming stable?

I have to say, I was kinda under the impression that betas are where issues like these are, which then turn into stable versions once they were thoroughly ironed out. This is weird for me.