Message 3 of 3
13 Jul 17 10:33
Join Date: 08 Sep 2005
Posts To This List: 10157
D0Entry on resumption from Hibernation
How are you verifying D0entry is not being called? Debug print statements are
not sufficient as there may be lost prints when resuming. What does the wdf log
Bent from my phone
From: email@example.com on behalf of Sunil Kumar
Sent: Thursday, July 13, 2017 5:26:40 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] D0Entry on resumption from Hibernation
What kind of device is it? USB based ? Does it support D3Cold?
I have seen it on a platform which supports D3Cold. D3Cold device need support
from BIOS\ACPI to go D3Cold. While resuming from Hibernation if BIOS\ACPI doed
not turn on device correctly you may see this issue.
Refer this link details
Not sure if it matches what you looking for!
On Thu, Jul 13, 2017 at 7:05 PM, firstname.lastname@example.org
Upon resumption from Hibernation, I see that my driver doesn't get a D0Entry
notification. Instead I see that the driver is getting a surprise removal
notification. As per MSDN links, I see that upon failure from D0Entry, surprise
removal gets invoked.
However, I in my case I see the D0Entry itself isn't getting invoked. What could
be the possible reasons for D0Entry "not" getting called and for surprise
removal getting invoke?
NTDEV is sponsored by OSR
Visit the list online at:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software
To unsubscribe, visit the List Server section of OSR Online at
--- NTDEV is sponsored by OSR Visit the list online at: MONTHLY seminars on
crash dump analysis, WDF, Windows internals and software drivers! Details at To
unsubscribe, visit the List Server section of OSR Online at