Windows 10: BSOD on Winows 10 1909

I am getting periodic BSODs on my home PC. I have re-installed Windows several times.

Can you please help me diagnose the cause?

Minidumps at https://www.dropbox.com/s/5uozqk47sqt7umc/minidumps.zip?dl=0

msinfo at https://www.dropbox.com/s/mb9rabza29dr0ya/msinfo.txt?dl=0

:)

 

Windows 10 1909 Causes Secondary Hard Drive to not be Recognized

Installing the Windows 10 1909 Update causes my secondary hard drive to not be recognized.

Steps to confirm issue:

• Secondary drive not visible in Windows Explorer
• Secondary drive not visible in device manager
• Secondary drive not visible in disk manager

Steps to replicate issue:

• Installing 1909 update

Steps to resolve issue:

• Uninstall 1909 update

Since updates can only be delayed for so long, an actual fix would be appreciated.

 

User.000 issue after updating to 1909

I'm one of the many people suffering from issues with user profiles after applying Update 1909 to Windows 10. I've read all the threads I can find on the topic here and have followed the suggestions, all to no avail. Any other thoughts are appreciated.

After applying Update 1909, the ProfileImagePath was changed to c:\users\User.000
One file that was always in use and couldn't be removed was left in c:\users\User (can't recall or find the exact file now), so I could never rename or remove the c:\user\User directory.

I followed the multiple suggestions from Brink and others:

• Rebooted at least 6 times
• Enabled hidden Administrator
• Booted into Safe Mode
• Changed ProfileImagePath
• Tried to rename c:\users\User but couldn't because a file was still in use
• Copied all data from c:\users\User.000 into c:\users\User
• Rebooted and had temporary profile
• Followed steps in Brink tutorial to change ImageProfilePath; rebooted with no change
• Restored using Restore Point from before Update 1909 - returned to single profile state (User.000)
• Removed each update that was installed individually and rebooted after each update removal - profile state never changed
• After all updates were removed, repeated the steps above with hidden Administrator, changing profile, etc. - same issue with file in use in c:\users\User
• Followed all steps above with hidden Administrator but without copying files from User.000 to User - same results

Any suggestions are greatly appreciated!

 

BSOD, Black Screen, and General Freezing while gaming on Windows 10 1909

Recently I was sent a preinstalled Windows 10 Pro 1909 SSD, unable to reinstall different OS version or downgrade without voiding a warranty. Now, I am essentially stuck on Windows 10 1909 and while utilizing it I have run into a specific repeatable issue
that I have tried numerous strategies to repair with no success.

Specs:

• Alienware 17R4
  
• Windows 10 1909 Build 18363.657
  
• 256 GB NVMe M.2 SSD (OS Drive)
  
• 1TB HDD (Secondary Drive)
• Nvidia GTX 1080 (Notebook edition)
• Intel i7-7820HK CPU
• 16GB Memory

Problem: When playing any graphically demanding game (will list a few below), within ~5-20 minutes, the computer will Crash to BSOD (various errors/not consistent message), Crash to Black Screen, or just simply freeze; all of which require
a hard reboot of the device.

• Two of the BSOD errors [UNEXPECTED_KERNEL_MODE_TRAP and KMODE_EXCEPTION_NOT_HANDLED].

Troubleshooting Attempts: Thus far I have tried the following to see what the issue might be

• Ran various hardware performance utilities to diagnose any current hardware issues (None found)
  
• Installed, uninstalled, and reinstalled different Nvidia graphics drivers (Same issue persists)
• Reinstalled fresh edition of Win 10 1909 OS (Same issue presists)
  
• Reinstalled fresh Nvidia driver (version 442.19) after Win 10 reinstall (Same issue persists)
  
• Installed only minimal software to replicate the problem (Steam with 1-3 games) (Same issue persists) [Game Examples: Assassins Creed Odyssey, The Witcher 3, Session, and Wolcen]
  • Was able to play a non-graphically demanding game (Roblox) without crashing
• Installed different gaming software to see if the issue was related to Steam - Blizzard Launcher+ Diablo 3 (Same issue persists)
• Tested if problem occurs while not gaming, running HD video, etc. (Issue does not occur); can run for hours or even days with no problem as long as games are not played

At this point, I am unable to determine the next best course of action to resolve this issue.