Our Vista x64 DTM client is experiencing this blue screen on a fairly regular basis. This is on a driver that has already passed the test previously.
The MSDN page has explanations for up to 0x00000008 for parameter 1, but not 0x00000009.
Any ideas?
I asked the power team to clarify what this parameter means (and suggested that they get it documented ;)).
Thx
d
could you send all of the bugcheck parameters and the callstack?
thx
d
I will have to wait until it happens again for the bugcheck parameters.
I couldn’t get a crash dump when this happened. It got stuck forever at something like “initializing crash dump for write”. I waited at least 15 minutes.
Do we know what 0x00000009 means yet? At least in general?
I don’t need the dump ;), just the callstack if you can get it. 0x9, in general it means there was an error in the hibernation path, the remaining parameters will indicate what exactly is going on.
d
Doron Holan wrote:
I don’t need the dump ;), just the callstack if you can get it.
Well, okay. Since the crash dump doesn’t seem to want to cooperate when this happens, should I opt for a minidump instead?
sure, that should work…
d
Here’s the full STOP message:
0x000000A0 (0x0000000000000009, 0xFFFFFFFFC0000001, 0x0000000000000001, 0x0000000000000000)
I couldn’t capture the minidump either. Our boot device isn’t supported directly by the BIOS (we have to do the F6 thing when we install…), is this preventing us from taking the dump?
Here is what the power folks had to say, “The error was 0xc0000001, STATUS_UNSUCCESSFUL. This was a problem initializing the dump stack.” It looks like a minidump or dump would be useful, but I don’t know if that is possible at that stage of hibernation.
d
FYI, as a point of reference, the hiber dump stack is basically the same as the crash dump stack, so if you are having issues creating the hiber dump stack, you will have the same issues creating a crash dump stack.
d
Do we know what the likely cause of this failure is? Hardware problem? We’re only seeing it on this one machine.
And like I said, I don’t know why I can’t capture a dump, but it doesn’t seem to want to cooperate.
Don’t know if this is still relevant but I had an issue ages ago where
if you’re booting externally the device has got to have lun zero for the
dump to work… A quick Google shows that was still relevant for 2K3…
Might be worth you checking…
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@gmail.com
Sent: 17 November 2006 17:22
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Meaning of INTERNAL_POWER_ERROR with Parameter 1 =
0x00000009?
Here’s the full STOP message:
0x000000A0 (0x0000000000000009, 0xFFFFFFFFC0000001, 0x0000000000000001,
0x0000000000000000)
I couldn’t capture the minidump either. Our boot device isn’t supported
directly by the BIOS (we have to do the F6 thing when we install…), is
this preventing us from taking the dump?
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Bill Clark wrote:
Don’t know if this is still relevant but I had an issue ages ago where
if you’re booting externally the device has got to have lun zero for the
dump to work… A quick Google shows that was still relevant for 2K3…
Might be worth you checking…
I’ll look into that. I have no idea how it’s set up. For the moment I’ve swapped machines to see if that blue screen disappears, in the absence of other information.