Windows 10: Windows 10 2004 upgrade issue Reported to Dell as "BSOD on resume from sleep".

Dell states:


It’s a Microsoft bug that affects the upgrade process to version 2004 from version 1904/1909 of Windows. Microsoft implemented some changes to how modern standby works and from what I am finding the DLLs that control that process are not properly replaced/updated. This can affect any install of Windows including Microsoft’s own image, the Dell image or any custom images that companies create. We can sometimes mitigate sleep issues with drivers of our own, but since the BSODs are caused by a Microsoft specific driver dam.sys, Microsoft would need to supply a fix. Since reinstalling Windows 10 2004 corrects the issue, they will not address it.


* At this point, Dell is saying it is a Microsoft issue and there is nothing they can really do but wait for MS to fix it.

* Anyone experience similar issues and have any solutions or advice?


Steps already taken: Dell Support & Dr. Google.


Report to Dell; non fix result.

Our Dell Latitude series laptops, specifically the 5400 series are having PDC Watchdog Timeout BSODs. The BSOD occurs when a user tries to wake the laptop when it goes to sleep. This issue only affects laptops that have been upgraded to the Windows 10 2004 update. Laptops installed with a fresh copy of Windows 10 2004 function fine regarding sleeping and waking.

Temporarily we have created a Device configuration profile in Intune that targets all our Dell laptops and configures them to hibernate instead of sleep. I am, however, looking for a more permanent solution.

Crash logs report that the dam.sys kernel drive that handles modern sleep driver attempts to access an unreadable memory address, fails, and then BSOD. We have tried the following:

· Advanced Drive Restore recommended by Dell

· Removing KB4537572, KB4535996, KB4571744 also recommended by Dell

· Hibernate circumvents our issues but does not actually solve it

Dell States:

The issue is not relegated to the Dell image. It’s a Microsoft bug that affects the upgrade process to version 2004 from version 1904/1909 of Windows. Microsoft implemented some changes to how modern standby works and from what I am finding the DLLs that control that process are not properly replaced/updated. This can affect any install of Windows including Microsoft’s own image, the Dell image or any custom images that companies create. We can sometimes mitigate sleep issues with drivers of our own, but since the BSODs are caused by a Microsoft specific driver dam.sys, Microsoft would need to supply a fix. Since reinstalling Windows 10 2004 corrects the issue, they will not address it.


Background note: We initially noticed this on Dell 5400 series, as we had just Endpoint Intune joined them and handed them out NIB. It later appeared on field laptops mostly Dell, we also have significant Lenovo; a few HP with images created in house From a MDT based on the Microsoft Windows image, at times including 1904/1909. Now deprecated in favor of autopilot, upgrade to 2004, cloud install, Endpoint Software Install. .


Worrying note note: This implies that everyone who has gotten a new laptop in the last two years may be affected.

:)

 

BSOD During Windows 10 2004 Update

My computer was one of many put on compatibility hold for the Windows 10 2004 update due to old Nvidia drivers. In this case, it's an old laptop (Asus M50VM-A1, state of the art way back in 2008), with a GeForce Go 9600M GS graphics card. The compatibility
hold was for graphics cards with drivers older than 358.00, and 342.01 is the final driver available for this card.

The compatibility hold was removed on August 13, and I have since tried to upgrade to 2004 without success. Every time I attempt to do so, I receive either a Kernel Security Check Error BSOD, or in one case, error 0x800704C7. The BSOD/error occurs sometime
after 91% installation completion, and prior to reboot. I have tried the following without success:

• Manually removing the downloaded files to force a redownload
• DISM and SFC on the current build (1909) - no violations reported
• Windows Update Troubleshooter

I have not tried, but am considering trying:

• Reinstalling driver 342.01 (I'm hesitant to as this driver has been installed since January 2016 without issue)
• Update in Safe Mode with Networking (I'd prefer not to due to Microsoft recommending against)

The BSOD suggests a corrupt system file, but multiple redownloads and SFC seem to exonerate the system. That makes me wonder if the old graphics driver is causing a failure despite Microsoft's comments to the contrary; or, perhaps, the graphics driver is
corrupt despite being stable for almost 5 years.

I have four minidumps at https://1drv.ms/u/s!AjRQX6iM6vWGviYKsPAZysLNO-YL?e=Q2abVP you can view.

As for computer specs, I'm not sure what you need, but here's a synopsis:

Asus M50VM-A1 laptop

Windows 10 Pro 1909

Intel Core 2 Duo P8400 @2.26 GHz

4 GB RAM + 15GB ReadyBoost (SDHC) (no issues reported on MemCheck)

Nvidia GeForce Go 9600M GS w/ 1GB vRAM (no issues reported on MemCheck)

300 GB HDD @5600 rpm (no issues reported on ScanDisk)

Please let me know if you need additional info or have suggestions. Thank you.

 

Windows 10 upgrade problem, no input accepted

I really hate having to come here and ask for help, but I really am stumped. It hurts my geek pride. I have a PC with fairly modern hardware in it. It has a p8p67 pro in it. I have tried upgrading windows 10 on it twice now. Both times I have had the same result.

After windows finishes upgrading it goes to the log in/set up screen. I can't do anything. No keyboard or mouse input is accepted.

I will list some, or hopefully all, of the troubleshooting steps I have tried:

• Move keyboard and mouse to different USB ports.
• Try different keyboard or mouse.
• Restart computer, repeatedly.
• Google for related issues.
• Update Bios, because why not.
• Create boot media and revert to windows 7.

The windows 10 system restore boot media works fine with keyboard and mouse. All USB ports work in windows 7. I don't know what is wrong. I suspect that windows 10 is lacking a driver of some sort, but since the computer accepts no input I have no way of checking for which driver let alone installing it.

Please help me figure this out. If I have to revert back to windows 7 again, I am not going to get it upgraded to windows 10. Thank you in advanced.

 

Win 10 2004 update No AMD graphics

Before upgrading anything else to 2004, I would suggest checking out the current Known Issues list.

There are several -

https://docs.microsoft.com/en-us/win...indows-10-2004