Share via

laptop wake up/power on issues dmp.file

angel dimitrov 1 Reputation point
2021-06-20T19:32:12.397+00:00

Hello,
I have this new laptop for few days and I am experiencing some strange behaviour from day one I installed windows.
It has the very last i7 gen 11 CPU and this is probably something to do with the errors. When left for some time in sleep or shut down, I must do a hard reset in order to start the laptop. It just simply does not start, no post, nothing. Here is the dump file. I am planning to see if this is a software issue or to return it to the seller. I did a completely clean windows install, for the second time, updated everything drivers and bios-wise with little to no success. Here is the dmp file:

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80478c00000 PsLoadedModuleList = 0xfffff8047982a230
Debug session time: Sun Jun 20 21:48:54.775 2021 (UTC + 3:00)
System Uptime: 0 days 4:45:18.394
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........................................
Loading User Symbols

Loading unloaded module list
........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80478ff6c20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb8004b55b910=0000000000000124
7: kd> !analyze -v

**

Bugcheck Analysis

**

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffcd8d33003028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000008100402, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

------------------

KEY_VALUES_STRING: 1 

Key  : Analysis.CPU.mSec  
Value: 3265  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 7718  

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

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

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

Key  : WER.OS.Branch  
Value: vb_release  

Key  : WER.OS.Timestamp  
Value: 2019-12-06T14:06:00Z  

Key  : WER.OS.Version  
Value: 10.0.19041.1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffcd8d33003028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 8100402

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb8004b55b908 fffff804790b440a : 0000000000000124 0000000000000000 ffffcd8d33003028 00000000b2000000 : nt!KeBugCheckEx
ffffb8004b55b910 fffff804770715b0 : 0000000000000000 ffffcd8d33003028 ffffcd8d2d547c20 ffffcd8d33003028 : nt!HalBugCheckSystem+0xca
ffffb8004b55b950 fffff804791b61ee : 0000000000000000 ffffb8004b55b9f9 ffffcd8d33003028 ffffcd8d2d547c20 : PSHED!PshedBugCheckSystem+0x10
ffffb8004b55b980 fffff804790b5d31 : ffffcd8d4aa12800 ffffcd8d4aa12800 ffffcd8d2d547c70 ffffcd8d2d547c20 : nt!WheaReportHwError+0x46e
ffffb8004b55ba60 fffff804790b60a3 : 0000000000000007 ffffcd8d2d547c70 ffffcd8d2d547c20 0000000000000007 : nt!HalpMcaReportError+0xb1
ffffb8004b55bbd0 fffff804790b5f80 : ffffcd8d2cefdab8 0000000000000001 0000000000000000 6574746f67726f66 : nt!HalpMceHandlerCore+0xef
ffffb8004b55bc20 fffff804790b61d1 : 0000000000000010 0000000000000001 0000000000000000 6772615420656874 : nt!HalpMceHandler+0xe0
ffffb8004b55bc60 fffff804790b543b : 0000000000000000 0000000000000000 ffffb8004b55bef0 6966207265626d75 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffb8004b55bc90 fffff804790b7c85 : ffffcd8d2cefdab8 7473207365697469 2065727574637572 6575712061206e69 : nt!HalpHandleMachineCheck+0x5f
ffffb8004b55bcc0 fffff8047910d519 : 2073617720505249 706f727020746f6e 696e6920796c7265 64657a696c616974 : nt!HalHandleMcheck+0x35
ffffb8004b55bcf0 fffff80479005cfa : 7264646120656854 6c65696620737365 65687420666f2064 6320797265757120 : nt!KiHandleMcheck+0x9
ffffb8004b55bd20 fffff804790059b7 : 0000000000000000 fffff804790058ec 0000000000000002 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffb8004b55be60 fffff8049831138f : fffff8049831f23e 0000000000000000 fffff80479161e43 00000027dc29b9c0 : nt!KiMcheckAbort+0x277
ffffdd835c08ef98 fffff8049831f23e : 0000000000000000 fffff80479161e43 00000027dc29b9c0 ffffb8004b4eb180 : intelppm!MWaitIdle+0x1f
ffffdd835c08efa0 fffff80478e184b6 : 00000000000139bc 0000000000000025 0000000000000000 0000000000000000 : intelppm!PepIdleExecute+0x2e
ffffdd835c08eff0 fffff80478e17274 : 0000000000000000 00001f800000000c 0000000000000003 0000000000000002 : nt!PpmIdleExecuteTransition+0x10c6
ffffdd835c08f3f0 fffff80478ffa744 : ffffffff00000000 ffffb8004b4f6440 ffffcd8d5655a080 0000000000000650 : nt!PoIdle+0x374
ffffdd835c08f560 0000000000000000 : ffffdd835c090000 ffffdd835c089000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_UNCLASSIFIED_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0c89b0a6-a484-2a19-c58d-5c6f112e065b}

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

7: kd> !analyze -v

**

Bugcheck Analysis

**

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffcd8d33003028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000008100402, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

------------------

KEY_VALUES_STRING: 1 

Key  : Analysis.CPU.mSec  
Value: 2812  

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 2812  

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

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

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

Key  : WER.OS.Branch  
Value: vb_release  

Key  : WER.OS.Timestamp  
Value: 2019-12-06T14:06:00Z  

Key  : WER.OS.Version  
Value: 10.0.19041.1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffcd8d33003028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 8100402

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: System

STACK_TEXT:
ffffb8004b55b908 fffff804790b440a : 0000000000000124 0000000000000000 ffffcd8d33003028 00000000b2000000 : nt!KeBugCheckEx
ffffb8004b55b910 fffff804770715b0 : 0000000000000000 ffffcd8d33003028 ffffcd8d2d547c20 ffffcd8d33003028 : nt!HalBugCheckSystem+0xca
ffffb8004b55b950 fffff804791b61ee : 0000000000000000 ffffb8004b55b9f9 ffffcd8d33003028 ffffcd8d2d547c20 : PSHED!PshedBugCheckSystem+0x10
ffffb8004b55b980 fffff804790b5d31 : ffffcd8d4aa12800 ffffcd8d4aa12800 ffffcd8d2d547c70 ffffcd8d2d547c20 : nt!WheaReportHwError+0x46e
ffffb8004b55ba60 fffff804790b60a3 : 0000000000000007 ffffcd8d2d547c70 ffffcd8d2d547c20 0000000000000007 : nt!HalpMcaReportError+0xb1
ffffb8004b55bbd0 fffff804790b5f80 : ffffcd8d2cefdab8 0000000000000001 0000000000000000 6574746f67726f66 : nt!HalpMceHandlerCore+0xef
ffffb8004b55bc20 fffff804790b61d1 : 0000000000000010 0000000000000001 0000000000000000 6772615420656874 : nt!HalpMceHandler+0xe0
ffffb8004b55bc60 fffff804790b543b : 0000000000000000 0000000000000000 ffffb8004b55bef0 6966207265626d75 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffb8004b55bc90 fffff804790b7c85 : ffffcd8d2cefdab8 7473207365697469 2065727574637572 6575712061206e69 : nt!HalpHandleMachineCheck+0x5f
ffffb8004b55bcc0 fffff8047910d519 : 2073617720505249 706f727020746f6e 696e6920796c7265 64657a696c616974 : nt!HalHandleMcheck+0x35
ffffb8004b55bcf0 fffff80479005cfa : 7264646120656854 6c65696620737365 65687420666f2064 6320797265757120 : nt!KiHandleMcheck+0x9
ffffb8004b55bd20 fffff804790059b7 : 0000000000000000 fffff804790058ec 0000000000000002 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffb8004b55be60 fffff8049831138f : fffff8049831f23e 0000000000000000 fffff80479161e43 00000027dc29b9c0 : nt!KiMcheckAbort+0x277
ffffdd835c08ef98 fffff8049831f23e : 0000000000000000 fffff80479161e43 00000027dc29b9c0 ffffb8004b4eb180 : intelppm!MWaitIdle+0x1f
ffffdd835c08efa0 fffff80478e184b6 : 00000000000139bc 0000000000000025 0000000000000000 0000000000000000 : intelppm!PepIdleExecute+0x2e
ffffdd835c08eff0 fffff80478e17274 : 0000000000000000 00001f800000000c 0000000000000003 0000000000000002 : nt!PpmIdleExecuteTransition+0x10c6
ffffdd835c08f3f0 fffff80478ffa744 : ffffffff00000000 ffffb8004b4f6440 ffffcd8d5655a080 0000000000000650 : nt!PoIdle+0x374
ffffdd835c08f560 0000000000000000 : ffffdd835c090000 ffffdd835c089000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR_MAE_INTERNAL_UNCLASSIFIED_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0c89b0a6-a484-2a19-c58d-5c6f112e065b}

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

attached is the system info file export in txt file.
Please, help107391-info.txt

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Docs 15,846 Reputation points
    2021-06-20T20:42:57.347+00:00

    New laptops should not have BSOD.

    WHEA 0x124 are typically malfunctioning hardware.

    Contact the computer manufacturer or vendor for Return Merchandise Authorization (RMA).

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post: Vote = a helpful post
    .
    .
    .
    .
    .

    0 comments
  2. Carl Fan 6,881 Reputation points
    2021-06-21T07:55:32.34+00:00

    Hi,
    Whea 0x124 bugchecks are often related to hardware problems. However other software can cause these bugchecks.
    So firstly I suggest that you could check your intel driver below.
    https://www.thewindowsclub.com/fix-intelppm-sys-blue-screen-error-on-windows-10
    Also you have this new laptop few days, have you checked for update to install the new security update?
    After updating the system version, download the intel, Motherboard and video card driver from the manufacturer's official website to install.
    STOP 0x124 errors are errors that the CPU detects and sends to Windows. So check CPU temperature, whether there is CPU overclocking. Then you could try to return it to the seller.
    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.