Hi,
I am trying to hibernate the system (Windows 2003 SP2) using a boot controller (OS disk sitting behind the adapter). What I see that the Storport driver is calling the driver StopAdapter(), followed by FindAdapter() and HwScsiInitialize() entry points. After successful completion of these entry points, it calls Driver with SCSI INq to the boot drive which I am completing successfully (with the same data when OS booted). After the SCSI INQ completion, Storport pauses for few seconds (don’t know why) and then reloads the driver again w/o going into hibernation and sending any further commands to the hiber driver.
I try reducing the size of SrbExtension, non-cachedextension but this issue doesn’t go away. I also tried bang.exe to simulate crash dump but with same symptoms.
Any pointers to nail down this issue will be appreciated.
TIA,
Gurpreet
I installed the checked build version of W2K3 x86 and I saw the below message:
CRASHDUMP: Unable to initialize driver; error = c0000001
Driver is not returning any errors not why it is coming.
— On Wed, 4/15/09, Gurpreet Anand wrote:
> From: Gurpreet Anand
> Subject: [ntdev] Hibernation fails on W2K3 SP2
> To: “Windows System Software Devs Interest List”
> Date: Wednesday, April 15, 2009, 9:08 AM
> Hi,
>
> I am trying to hibernate the system (Windows 2003 SP2)
> using a boot controller (OS disk sitting behind the
> adapter). What I see that the Storport driver is calling the
> driver StopAdapter(), followed by FindAdapter() and
> HwScsiInitialize() entry points. After successful completion
> of these entry points, it calls Driver with SCSI INq to the
> boot drive which I am completing successfully (with the same
> data when OS booted). After the SCSI INQ completion,
> Storport pauses for few seconds (don’t know why) and
> then reloads the driver again w/o going into hibernation and
> sending any further commands to the hiber driver.
> I try reducing the size of SrbExtension,
> non-cachedextension but this issue doesn’t go away. I
> also tried bang.exe to simulate crash dump but with same
> symptoms.
>
> Any pointers to nail down this issue will be appreciated.
>
> TIA,
> Gurpreet
>
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars
> visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online
> at http://www.osronline.com/page.cfm?name=ListServer
This is not my thing, but back in the Vista beta cycle, I recall getting that error due to either
the BIOS not recognizing drives, or because of some truly pathological behavior caused by burning
the vista iso ‘incorrectly’ - too fast and/or poor media.
I have no idea if this comments on your case or not, but there it is, for what it’s worth.
Good luck,
mm
Gurpreet Anand wrote:
I installed the checked build version of W2K3 x86 and I saw the below message:
CRASHDUMP: Unable to initialize driver; error = c0000001
Driver is not returning any errors not why it is coming.
— On Wed, 4/15/09, Gurpreet Anand wrote:
>
>> From: Gurpreet Anand
>> Subject: [ntdev] Hibernation fails on W2K3 SP2
>> To: “Windows System Software Devs Interest List”
>> Date: Wednesday, April 15, 2009, 9:08 AM
>> Hi,
>>
>> I am trying to hibernate the system (Windows 2003 SP2)
>> using a boot controller (OS disk sitting behind the
>> adapter). What I see that the Storport driver is calling the
>> driver StopAdapter(), followed by FindAdapter() and
>> HwScsiInitialize() entry points. After successful completion
>> of these entry points, it calls Driver with SCSI INq to the
>> boot drive which I am completing successfully (with the same
>> data when OS booted). After the SCSI INQ completion,
>> Storport pauses for few seconds (don’t know why) and
>> then reloads the driver again w/o going into hibernation and
>> sending any further commands to the hiber driver.
>> I try reducing the size of SrbExtension,
>> non-cachedextension but this issue doesn’t go away. I
>> also tried bang.exe to simulate crash dump but with same
>> symptoms.
>>
>> Any pointers to nail down this issue will be appreciated.
>>
>> TIA,
>> Gurpreet
>>
>>
>>
>>
>> —
>> NTDEV is sponsored by OSR
>>
>> For our schedule of WDF, WDM, debugging and other seminars
>> visit:
>> http://www.osr.com/seminars
>>
>> To unsubscribe, visit the List Server section of OSR Online
>> at http://www.osronline.com/page.cfm?name=ListServer
>
>
>
>
> the BIOS not recognizing drives, or because of some truly pathological behavior caused by burning
the vista iso ‘incorrectly’ - too fast and/or poor media.
Comparing md5 checksums after each burn is a good idea.
“md5sum \.\e:” works OK for CD/DVD media.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Indeed. I learned that one the hard way over the course of maybe two months of vista betas failing
installation after after like two hours with the strangest errors, like ‘unsupported language,’ and
I went through a whole lot of wasted effort looking at things like BIOS settings, et. c. before
something finally arrived from MSDN that worked, which is what made me think of it. Had the
installations failed during the copy/extraction phase, it would have been a lot more obvious that
perhaps this was an ISO burning thing, but for whatever reason, as I recall, they always failed
after that.
mm
Maxim S. Shatskih wrote:
> the BIOS not recognizing drives, or because of some truly pathological behavior caused by burning
> the vista iso ‘incorrectly’ - too fast and/or poor media.
Comparing md5 checksums after each burn is a good idea.
“md5sum \.\e:” works OK for CD/DVD media.