BSOD - need help with analyzing my minidump

Hey guys,

yesterday I came back from work seeing my m17x R3 in some kind of boot-loop (it was up and running the whole day, I was logged onto it with logmein and everything worked). It wanted to do a PXE-boot and whatnot. I was wondering why it was in boot-mode in the first place, and just did a reboot. Win 7 booted as it should, the whole system was back to normal.

Well, after a closer look into the minidump (hadnt installed the debugging tools yet, so I had to use notepad) I saw a lot of stuff about hibernation, cooling and thermal stuff. Sorry for the upcoming format, but those infos arent in the windows debugger (more on that later)

Code:

PopConnectToPolicyDevice: ObReferenceObjectByHandle failed %x
 ÐPopConnectToPolicyDevice: ExAllocatePoolWithTag for SystemButton (%x) failed
 ÐÐPopConnectToPolicyDevice: RtlUpcaseUnicodeString for SystemButton failed with status %x
 ÐÐÐÐÐÐÐPopConnectToPolicyDevice: IoRegisterPlugPlayNotification for SystemButton failed with status %x
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐPopConnectToPolicyDevice: ExAllocatePoolWithTag for ThermalZone (%x) failed
 ÐÐÐdriver ÐÐÐÐÐÐÐÐÐdevice ÐÐÐÐÐÐÐÐÐPopFilterCapabilities: disabling sleep states due to legacy %s: %ws
 ÐÐÐÐÐÐÐÐÐÐÐV G A P N P . S Y S   ÐÐÐÐÐÐÐÐÐÐPopIdleDetection: IdleDetectionCallback failed (%x)
 ÐÐÐÐÐÐÐÐÐÐÐPopSetPowerSettingValue: state = %d, size = %d first ulong = 0x%08x.
 ÐÐÐÐÐÐÐÐÐÐPopSetPowerSettingValue: Creating new setting with empty values.
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐPopSetPowerSettingValue: Setting value didn't change.
 ÐÐÐÐÐÐÐÐÐPopSetPowerSettingValue: Allocating new value.
 \ h i b e r f i l . s y s   ÐÐÐÐPopCreateHiberFile: failed to create file %x
 ÐÐPopCreateHiberFile: failed to set eof %x  %x
 ÐÐPopCreateHiberFile: unable to flush hiberfile metadata (%x)
 ÐÐÐPopZeroHiberFile: Write of size %lx at offset %I64x failed %08lx
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐh i b e r _   ÐÐPopCriticalShutdown: type %x
 ÐÐPopSetPowerAction: %s, Flags %x, Min=%s
 ÐÐÐÐÐÐÐPopAction: dropped user event %x
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐPopPolicyWorkerAction: action request %d failed %08lx
 ÐÐÐÐÐÐÐÐÐPopAction: invalid state %d
 ÐÐÐPromote,  ÐÐÐÐÐÐ ÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐPowerAction: %s%s, Min=%s, Flags %x
 ÐÐÐÐÐÐÐÐÐÐÐPowerAction: Setting with direct call
 ÐÐÐÐÐÐÐÐÐPopSystemButtonHandler: unexpected error %x
 ÐÐÐPopSystemButtonHandler: removing button device
 PopSystemButtonHandler : removing power button
 PopSystemButtonHandler : removing sleep button
 PopSystemButtonHandler : removing lid switch
 ÐÐw i n r e s u m e . e f i   ÐÐÐÐw i n r e s u m e . e x e   ÐÐÐÐPopEventDispatch: full wake
 ÐÐÐPopNotify: Event %x
 ÐÐÐÐÐÐÐÐÐÐÐa c t i v e   ÐÐp a s s i v e   e n g a g e d   d i s e n g a g e d   ÐÐÐÐÐÐÐÐÐÐPopCB: New battery tag
 ÐÐÐÐÐÐÐÐPopCB: info read
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐPopCB: Status PwrState %x, Cap %x, Volt %x, Cur %x
 ÐÐÐÐÐÐÐÐÐÐÐÐPopCB: EstTime read
 ÐÐÐÐÐÐÐÐÐÐÐPopCB: error %x - new state %d
 PopCB: irp cancelled
 ÐÐÐÐÐÐÐÐÐÐPopCB: query tag
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐPopCB: query info
 ÐÐÐÐÐÐÐÐÐÐÐÐÐPopCB: timeout %x, pwrstate %x, low %x - high %x
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐPopCB: query est time
 ÐÐÐÐÐÐÐÐÐPopCB: Battery removed
 ÐÐÐÐÐÐÐÐP P M _ P r o c e s s o r _   ÐÐ% s % d   ÐÐÐÐÐÐPopUmpoSendLegacyEvent ÐÐÐÐÐÐÐÐÐ%s: Sending legacy event to UMPO, code=%d
 ÐÐÐÐÐPoSIdle: new idle params set
 ÐÐThermal Zone %p: going away
 ÐÐÐ
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐThermal Zone %p (READ_STATE):
 Ð  Current Temp:   0x%x
 ÐÐÐÐÐÐÐÐ  Critical Trip:  0x%x
 ÐÐÐÐÐÐÐÐ  Passive Trip:   0x%x
 ÐÐÐÐÐÐÐÐ  Active Trip %u: 0x%x
 ÐÐÐÐÐÐÐÐThermal Zone %p: Above critial temperature (_TMP 0x%x, _CRT 0x%x). Shutdown initiated
 ÐÐÐÐÐÐÐÐÐThermal Zone %p: Above critical S4 temperature (_TMP 0x%x, _HOT 0x%x). Hibernate initiated
 ÐÐÐÐThermal Zone %p: Pending Coooling Point is 0x%x
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐÐThermal Zone %p (SET_MODE):
 ÐÐÐ  Cooling mode set to 0x%x
 ÐÐÐÐThermal Zone %p (SET_ACTIVE):
 Ð  New Active cooling point: 0x%x
 ÐÐÐÐÐÐÐÐÐÐÐÐÐÐThermal Zone %p: unexpected error %x
 ÐÐÐÐÐÐÐÐÐÐThermal Zone %p: Sending Run Cooling Method: 0x%x
 ÐÐÐÐÐÐÐÐÐÐÐÐÐThermal Zone %p: Sending Set Cooling Policy: 0x%x
 ÐÐÐÐÐÐÐÐÐÐÐÐÐThermal Zone %p: Next read in %d sec
 ÐÐÐÐÐÐÐÐÐÐThermal Zone %p: Sending Query Temp - ThermalStamp = 0x%x
 ÐÐÐÐÐ\ R e g i s t r y \ M a c h i n e \ S o f t w a r e \ M i c r o s o f t \ W i n d o w s \ C u r r e n t V e r s i o n \ P o l i c i e s \ S y s t e m   ÐÐÐÐÐÐÐÐE n a b l e L U A   ÐÐÐÐÐÐÐÐÐÐÐÐE n a b l e V i r t u a l i z a t i o n   ÐÐÐÐÐÐE n a b l e I n s t a l l e r D e t e c t i o n   ÐÐÐÐÐÐÐÐÐÐÐÐÐÐD e v O v e r r i d e E n a b l e   ÐÐÐÐÐÐÐÐÐÐÐÐE n a b l e C p u Q u o t a   ÐÐTerminating critical thread 0x%p (in %s)
 ÐÐÐÐÐÐTerminating critical process 0x%p (%s)
 ÐÐÐÐÐÐÐÐBreak, or Ignore (bi)?  ÐÐÐÐÐÐÐÐCritical thread 0x%p (in %s) exited
 ÐÐÐÐÐÐÐÐÐÐÐCritical process 0x%p (%s) exited
 ÐÐÐÐÐÐÐÐÐÐÐÐÐD e b u g g e r

I dont know what this is all about, because I deactivated any kind of energy-saving stuff. And I never do hibernation anyway! And it wasnt the first time that my R3 idled for hours (10h and more w/o problems). BTW, this was my first BSOD with this system.

Well, here is the minidump from the debugging tools

Code:

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8008194060, Terminating object
Arg3: fffffa8008194340, Process image file name
Arg4: fffff80002fe7f40, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8008194060

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xF4

PROCESS_NAME:  wininit.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000306c7d2 to fffff80002ce4d00

STACK_TEXT: 
fffff880`0dceee38 fffff800`0306c7d2 : 00000000`000000f4 00000000`00000003 fffffa80`08194060 fffffa80`08194340 : nt!KeBugCheckEx
fffff880`0dceee40 fffff800`0301abdb : ffffffff`ffffffff fffffa80`09cd14a0 fffffa80`08194060 fffffa80`08194060 : nt!PspCatchCriticalBreak+0x92
fffff880`0dceee80 fffff800`02f9d838 : ffffffff`ffffffff 00000000`00000001 fffffa80`08194060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x179e6
fffff880`0dceeed0 fffff800`02ce3f93 : fffffa80`08194060 fffff800`c0000005 fffffa80`09cd14a0 00000000`028f04c0 : nt!NtTerminateProcess+0xf4
fffff880`0dceef50 fffff800`02ce0530 : fffff800`02d306cf fffff880`0dcefa38 fffff880`0dcef790 fffff880`0dcefae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0dcef0e8 fffff800`02d306cf : fffff880`0dcefa38 fffff880`0dcef790 fffff880`0dcefae0 00000000`028f1fd0 : nt!KiServiceLinkage
fffff880`0dcef0f0 fffff800`02ce4382 : fffff880`0dcefa38 00000000`0000aab7 fffff880`0dcefae0 00000000`028f1aa8 : nt! ?? ::FNODOBFM::`string'+0x49974
fffff880`0dcef900 fffff800`02ce2efa : 00000000`00000001 00000000`028f0bd8 00000000`00000001 00000000`0000aab7 : nt!KiExceptionDispatch+0xc2
fffff880`0dcefae0 00000000`778c8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`028f0be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778c8e3d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  wininit.exe

FAILURE_BUCKET_ID:  X64_0xF4_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IMAGE_wininit.exe

Followup: MachineOwner
---------

Strange thing: Heres nothing about hibernation at all - or do I miss something? Any ideas what could have caused the BSOD?

 

Well, I just had the same BSOD again

What's still strange: After I saw my m17 looping in PXE boot I just hit ctrl+alt+del. The system restartet with the alienware startup picture and whatnot, but didnt want to boot either (no boot device bla bla). I tried it again with the same effect. Then I hit the powerbutton to shut it down and hit it again after 3 seconds - it booted as it should and the system runs fine. Jeez, this BSOD is a pain in the :/

Any ideas? Why didnt it boot with a softreboot but with a hardreset? Whats the difference in this context?

Edit: Although I didnt have any LPM-related freezes and such, I just applied the LPM-fix. Maybe this will fix it, cause the dump (in txt form) says something about hibernation.

 

Well, since I got sooooooooooo much feedback to this thread.......NOT.... I can at least say that the LPM fix fixed the problem. Didnt think that this would help, but as it seems it does. My R3 idled a couple of hours (4-8) in the last few days w/o problems.