A
Alexander McDiarmid
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.
Continue reading...
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.
Continue reading...