Constant Blue Screens

BSOD - Posting Instructions

It would seem your system is having trouble recovering from Hibernation. I'd recommend disabling it and see if the BSODs persist.

Enable or Disable Hibernate in Windows 10

Uninstall McAfee and use one Anti-virus software. I'd recommend Windows 10's built in Windows Defender and perhaps MBAM.

To be safe, run an integrity scan of the OS.

Open an elevated (Run as admin) Command Prompt and type the following:
sfc /scannow

Let it run. Do this after disabling Hibernation.

Code:

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

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 00000000000000f0, The system failed to complete(suspend) a power transition in a timely manner.
Arg2: 0000000000000000, The system power state in transition.
Arg3: 0000000000000004, The sleep checkpoint most recently reached.
Arg4: ffffc981c7571080, A pointer to the thread currently processing the request.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3874

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 16959

    Key  : Analysis.Init.CPU.mSec
    Value: 7124

    Key  : Analysis.Init.Elapsed.mSec
    Value: 90052

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 90

    Key  : Dump.Attributes.InsufficientDumpfileSize
    Value: 1

    Key  : Dump.Attributes.RequiredDumpfileSize
    Value: 0xcb4a4c14


DUMP_FILE_ATTRIBUTES: 0xc
  Insufficient Dumpfile Size
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a0

BUGCHECK_P1: f0

BUGCHECK_P2: 0

BUGCHECK_P3: 4

BUGCHECK_P4: ffffc981c7571080

FAULTING_THREAD:  ffffc981c7571080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffec01`0836f040 fffff805`138550b0     : ffffdc00`3118c180 00000000`ffffffff 00000000`00000000 00000000`00000006 : nt!KiSwapContext+0x76
ffffec01`0836f180 fffff805`138545df     : ffffc981`00000001 00000000`00000000 ffffec01`0836f340 00000000`00000000 : nt!KiSwapThread+0x500
ffffec01`0836f230 fffff805`13853e83     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc981`c75711c0 : nt!KiCommitThreadWait+0x14f
ffffec01`0836f2d0 fffffdd7`06c7cd4c     : ffffc982`0d2d6c10 00000000`0000000d 00000000`00000000 ffffc981`adf2f600 : nt!KeWaitForSingleObject+0x233
ffffec01`0836f3c0 fffffdd7`06c7c9b4     : 00000000`00000003 00000000`8000000a 00000000`c0000000 00000000`00000000 : win32kbase!QueuePowerRequest+0x15c
ffffec01`0836f400 fffffdd7`06c1b65a     : 00000000`00000004 ffffec01`0836f560 00000000`c000001c 00000000`00000000 : win32kbase!UserPowerStateCallout+0x114
ffffec01`0836f460 fffffdd7`071610d1     : 00000000`c000001c fffff805`1424ecc0 00000000`00000000 ffffec01`0836f950 : win32kbase!W32CalloutDispatch+0x70a
ffffec01`0836f670 fffff805`13cb0c5b     : 00000000`00000000 ffffc981`adf0a490 ffffc981`adf36140 00000000`00000000 : win32k!W32CalloutDispatchThunk+0x31
ffffec01`0836f6b0 fffff805`13c73894     : 00000000`00000010 00000000`00040086 ffffec01`0836f798 00000000`ffffffff : nt!ExCallSessionCallBack+0xa3
ffffec01`0836f770 fffff805`13cb0ac9     : ffffc981`b76142a0 ffffec01`0836f819 00000000`00000000 00000000`00000001 : nt!PsInvokeWin32Callout+0xd4
ffffec01`0836f7a0 fffff805`13d1537f     : 00000000`00000004 ffffec01`0836f950 ffffec01`0836f950 fffff805`13951024 : nt!PopInvokeWin32Callout+0x14d
ffffec01`0836f880 fffff805`13d65e2f     : ffffec01`0836f950 00000000`00000004 ffffec01`0836f950 00000000`00000000 : nt!PopDispatchStateCallout+0x5b
ffffec01`0836f8f0 fffff805`13d6558a     : 00000000`00000008 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PopSuspendServices+0x3b
ffffec01`0836f920 fffff805`13d65279     : 00000000`00000000 ffffc981`92bd2050 00000000`00000000 00000000`00000000 : nt!PopIssueActionRequest+0x1f2
ffffec01`0836f9c0 fffff805`13949094     : 00000000`00000001 00000000`00000000 ffffffff`ffffffff fffff805`14223a00 : nt!PopPolicyWorkerAction+0x79
ffffec01`0836fa30 fffff805`138bfae5     : ffffc981`00000001 ffffc981`c7571080 fffff805`13949000 ffffc981`00000000 : nt!PopPolicyWorkerThread+0x94
ffffec01`0836fa70 fffff805`138eea75     : ffffc981`c7571080 00000000`00000080 ffffc981`92ad4080 0041006e`00000001 : nt!ExpWorkerThread+0x105
ffffec01`0836fb10 fffff805`139ff428     : ffffdc00`3118c180 ffffc981`c7571080 fffff805`138eea20 00330025`00410061 : nt!PspSystemThreadStartup+0x55
ffffec01`0836fb60 00000000`00000000     : ffffec01`08370000 ffffec01`08369000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


STACK_COMMAND:  .thread 0xffffc981c7571080 ; kb

SYMBOL_NAME:  win32kbase!QueuePowerRequest+15c

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.19041.1767

BUCKET_ID_FUNC_OFFSET:  15c

FAILURE_BUCKET_ID:  0xa0_f0_win32kbase!QueuePowerRequest

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8aedff56-ba28-2a0b-c33f-66f34297de23}

Followup:     MachineOwner

In the start menu type "Command Prompt", right click and choose "Run as administrator".

Edit: If you use a password to logon, you may have to enter your password to proceed so in case that is the case, just type in the password used to logon.

patriceltic said:

Hi Kyle - figured out elevated cmd prompt - ran sfcscannow and it came up with the following:

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE fla

I still can't seem to get to that power setting in settings. Hope it is solved. When the scan first started system crashed. I went back in and restarted and it worked. Thanks again.

Start menu: Search for "Power & sleep settings" > "Additional power settings".

It should come up like this:

On the left pane click "Change when my computer sleeps".

After doing the above in the screenshot, reboot the system. Report back any issues that may follow.

This my support here solves your issue, please give "Thanks" as it adds to my rep. :)

patriceltic said:

OK did all of power settings - the NEVER was already in play on that setting. I was happy to see in that sfcscannow entry that corrupt files were found and fixed. I also don't know how that hibernation thing got into play either. I guess stuff just happens. Will give you a thanks for the help. I'll let you know if anything should change. Regards...

With laptops, hibernation is generally a feature of battery preservation. When the laptop isn't in use (when you close the lid for example, without shutting down correctly) it'll sometimes 'sleep' or 'hibernate' to conserve power, although the system technically still runs, it kind of runs in low power mode, or saves the current session into memory by something called NVRAM (Non-volitile Random Access Memory).

Once the lid opens back up, it should power back up and pick up where you left off. It's a handy feature but issues can potentially arise from its use sometimes.

You're most welcome. Feel free to submit a new thread if you have any further issues of a different nature (that don't pertain to the same BSOD). :)