Windows 10 (Bootcamp) Bluescreen when connected to home networks due to Active Directory – Works fine on Company Network

I’m running a 2018 MacBook pro with Windows 10 via bootcamp.

It’s managed via active directory by my company.

When connected to the company network on premises, everthing is fine – regardless of whether a wired or a wireless connection is used – so I don’t think it is a WiFi driver as others have suggested. I also know for a fact that this isn’t a deliberate policy applied by the company – we often work from home so the company doesn’t have issues with us using home networks.

The bluescreen error code is 0x0000082d. A little bit of research didn’t turn up much about this particular error.

I suspect that what is happening

I suspect that what is happening is that when I am on a home network (tried on multiple networks) the laptop reaches out to the active directory server for some reason, can’t reach it because I am not on the company network, and then crashes.

This suspicion is further supported after I have checked the Windows “Event Viewer” – I see the following Error event:

The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator. 

which is then immediately followed by a “BugCheck” event:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000082d (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 53fb8cde-6982-4bb5-84d8-7e9ecdd3d860. 

There are other users experiencing the same issue, but not all users. Additionally, there doesn’t seem to be a set time interval. The bluescreens happen approximately every 20 minutes or so, but this does not appear to be a firm number.

What gives? Is this the result of a screwed up AD policy? Or something else?