K Z

@A.Chu My network adapter is RealTek RTL816. Nothing conclusive.

Another test case is when hosting a local 1.17.x server (its shares the game code, of course), a BSOD will eventually occur, with the same error as usual.

@Steve_Hsu That's only partial true: this issue doesn't occur in Java 1.16.5, nor in Bedrock/Win10 edition, and thus some code in 1.17+ is incompatible with this PC or OP's PC. Of course, it doesn't affect a majority of its players, so it's unlikely to be easily diagnosed/solved.

Whether if its a driver issue, hardware issue, or software issue, this still only occurs with certain versions of Minecraft on certain PCs.

@Fannic64 Unfortunately, limiting the maximum processor usage to 80% (via Power options in Windows Settings) has no effect, and still promptly BSODs.

I've attached a BSOD dump - and it seems to be alluding that its paging an out-of-application memory address.

@GamerPro08 That doesn't seem to happen at all. It only peaks at 10/16 GB, but the BSOD doesn't occur because of that. It can still dip back down to 9 GB and then BSOD. And since it's Java, it will never over-allocate memory - by default it has a 2 GB limit, but I've also tested with a 6 GB limit. 

Also, it looks irrelevant to world lag - it can handle over 1000 cow entities just fine.

The same BSOD (DRIVER_IRQL_NOT_LESS_OR_EQUAL - afd.sys) occurs for me from Snapshot 21w19a to the latest 1.17.1 release.

However, it occurs within 80 minutes of gameplay, in both single player and multiplayer games (instead of on world load as the OP had).

I've already checked/updated all my drivers and did a fresh install of both the game and the PC, but it still occurs.

My afd.sys has a version number of 10.0.1904.1801, according to the windows-provided driver verifier, but I doubt that's relevant considering how old snapshot 21w19a is.