Windows 10 Pro 2004 and 20H2 crash to bluescreen

Question

After update to 2004 or 20H2 version I have problem with crashing bluescreen. The crash is after maping network unit. When I logged on and login script is automatically run, the computer crash to bluescreen. When I try open cmd, I'll write "net use I: \path of the unit /PERSISTENT:YES" and I'll send it, then the computer crash to bluescreen too
The problem is on many computers (Dell Latitude 5590 and Dell Latitude 5500) using version 2004 and 20H2 and all drivers are up to date and system update are up to date too.
There aren't any log about this problems in Event viewer.
In attachment I'm sending photo with bluescreen.

Thank you for your help

Answer 1

@Adam Suchomel

Which version of SMB is implemented in your share?

Have a look to this page:
1383449-win10-gsod-rdr_file_system-mrxsmbsys

Answer 2

@Adam Suchomel

Increase Offline Files size and check if you solve the issue:
122995-change-offline-files-disk-usage-limits-windows.html

Answer 3

We are experiencing also issues with our Latitude 55x0 devices: After 20H2 update, I get bluescreens (PNP fatal error).

• Rollback fails
• uninstalling updates (from the recovery screen) doesn't work

Answer 4

Hi,

Welcome to Microsoft Q&A.

Try following methods to see if it helps:
1 . Disable 3rd party antivirus software

2 . Perform clean boot in safe mode
Force the machine to reboot --> keep pressing F8 --> into Advanced Boot Options --> select Safe Mode
Clean boot steps are as follow
https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows

3 . Check for hardware malfunctions
Try running the hardware diagnostics supplied by the manufacturer or contact them directly for help.

Best regards,
Molly

--------------------------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.