BSOD hibernyte, amd-grafics, INTERNAL_POWER_ERROR (a0)

[namor82]

BSOD hibernate, amd-grafics, INTERNAL_POWER_ERROR (a0)

Hello,

I have following BSOD while I tried to shutdown to HIBERNATE.

Problemsignatur:
  Problemereignisname:	BlueScreen
  Betriebsystemversion:	6.1.7601.2.1.0.768.3
  Gebietsschema-ID:	1031

Zusatzinformationen zum Problem:
  BCCode:	a0
  BCP1:	0000000000000009
  BCP2:	FFFFFFFFC0000001
  BCP3:	0000000000000001
  BCP4:	0000000000000000
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	768_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
  C:\Windows\Minidump\052214-23634-01.dmp
  C:\Users\packard\AppData\Local\Temp\WER-78827-0.sysdata.xml

Lesen Sie unsere Datenschutzbestimmungen online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
  C:\Windows\system32\de-DE\erofflps.txt

I used the KB2541014 patch from microsoft and I tried also the powercfg 100% of memory command.
I have the newest AMD Driver 13.9 on my Packard Bell LJ71 Notebook with Windows 7 HomePremium x64.

With the WindowsDebuger I have collected following infomation

  Bugcheck Analysis 
***

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000009, A fatal error occured while preparing the hibernate file.
Arg2: ffffffffc0000001, Status code
Arg3: 0000000000000001, Mirroring phase
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xA0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8000391a905 to fffff800036ccbc0

STACK_TEXT:  
fffff880`06c9fb08 fffff800`0391a905 : 00000000`000000a0 00000000`00000009 ffffffff`c0000001 00000000`00000001 : nt!KeBugCheckEx
fffff880`06c9fb10 fffff800`03916694 : ffffffff`ffffffff ffffffff`ffffffff 00000000`001187a6 00000000`00000000 : nt!PopEndMirroring+0x145
fffff880`06c9fbe0 fffff800`0391abc5 : fffff880`06c9fd00 fffff880`00000007 00000000`00000000 fffffa80`00000007 : nt!MmDuplicateMemory+0xb64
fffff880`06c9fcd0 fffff800`0396873a : fffffa80`054ea650 fffff880`01240a8e fffffa80`03a16040 fffff880`012cc244 : nt!PopTransitionToSleep+0xd5
fffff880`06c9fd40 fffff800`036bd8e6 : fffff880`009e8180 fffffa80`054ea650 fffff880`009f2f40 00000000`00692200 : nt!PspSystemThreadStartup+0x5a
fffff880`06c9fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PopEndMirroring+145
fffff800`0391a905 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PopEndMirroring+145

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0xA0_IO_DUMPSTACK_INIT_ERROR_nt!PopEndMirroring+145

BUCKET_ID:  X64_0xA0_IO_DUMPSTACK_INIT_ERROR_nt!PopEndMirroring+145

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa0_io_dumpstack_init_error_nt!popendmirroring+145

FAILURE_ID_HASH:  {2bebd859-cf7d-df7b-8fc3-11bfefb9b9dd}

Followup: MachineOwner

What is that and is it a software failure or hardware failure ?!

 

[Arc]

Hi namor82.

This is neither a hardware failure nor a software failure. It is just a hibernate failure.

INTERNAL_POWER_ERROR (a0)
[COLOR=Red]The power policy manager experienced a fatal error[/COLOR].
Arguments:
Arg1: 0000000000000009, [COLOR=Red][B]A fatal error occured while preparing the hibernate file[/B][/COLOR].
Arg2: ffffffffc0000001, Status code
Arg3: 0000000000000001, Mirroring phase

If you disable hibernate, hopefully this BSOD will stop; but this will cause an extra load on the battery usage.

Sometimes disabling (that causes deleting hiberfile.sys) and then enabling hibernate back may cure the corruption of hiberfile.sys. You may try this way, too.

Let us know which way you taken and what is the result.

 

[namor82]

I allready did disable hibernate and reanabled it.
But the error while booting to hibernate-modus is the same. So this did not solve my problem.