question

angeldimitrov-5779 avatar image
0 Votes"
angeldimitrov-5779 asked CarlFan-MSFT answered

laptop wake up/power on issues dmp.file

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 = 0xfffff804`78c00000 PsLoadedModuleList = 0xfffff804`7982a230
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:
fffff804`78ff6c20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb800`4b55b910=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:
ffffb800`4b55b908 fffff804`790b440a : 00000000`00000124 00000000`00000000 ffffcd8d`33003028 00000000`b2000000 : nt!KeBugCheckEx
ffffb800`4b55b910 fffff804`770715b0 : 00000000`00000000 ffffcd8d`33003028 ffffcd8d`2d547c20 ffffcd8d`33003028 : nt!HalBugCheckSystem+0xca
ffffb800`4b55b950 fffff804`791b61ee : 00000000`00000000 ffffb800`4b55b9f9 ffffcd8d`33003028 ffffcd8d`2d547c20 : PSHED!PshedBugCheckSystem+0x10
ffffb800`4b55b980 fffff804`790b5d31 : ffffcd8d`4aa12800 ffffcd8d`4aa12800 ffffcd8d`2d547c70 ffffcd8d`2d547c20 : nt!WheaReportHwError+0x46e
ffffb800`4b55ba60 fffff804`790b60a3 : 00000000`00000007 ffffcd8d`2d547c70 ffffcd8d`2d547c20 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffb800`4b55bbd0 fffff804`790b5f80 : ffffcd8d`2cefdab8 00000000`00000001 00000000`00000000 6574746f`67726f66 : nt!HalpMceHandlerCore+0xef
ffffb800`4b55bc20 fffff804`790b61d1 : 00000000`00000010 00000000`00000001 00000000`00000000 67726154`20656874 : nt!HalpMceHandler+0xe0
ffffb800`4b55bc60 fffff804`790b543b : 00000000`00000000 00000000`00000000 ffffb800`4b55bef0 69662072`65626d75 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffb800`4b55bc90 fffff804`790b7c85 : ffffcd8d`2cefdab8 74732073`65697469 20657275`74637572 65757120`61206e69 : nt!HalpHandleMachineCheck+0x5f
ffffb800`4b55bcc0 fffff804`7910d519 : 20736177`20505249 706f7270`20746f6e 696e6920`796c7265 64657a69`6c616974 : nt!HalHandleMcheck+0x35
ffffb800`4b55bcf0 fffff804`79005cfa : 72646461`20656854 6c656966`20737365 65687420`666f2064 63207972`65757120 : nt!KiHandleMcheck+0x9
ffffb800`4b55bd20 fffff804`790059b7 : 00000000`00000000 fffff804`790058ec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffb800`4b55be60 fffff804`9831138f : fffff804`9831f23e 00000000`00000000 fffff804`79161e43 00000027`dc29b9c0 : nt!KiMcheckAbort+0x277
ffffdd83`5c08ef98 fffff804`9831f23e : 00000000`00000000 fffff804`79161e43 00000027`dc29b9c0 ffffb800`4b4eb180 : intelppm!MWaitIdle+0x1f
ffffdd83`5c08efa0 fffff804`78e184b6 : 00000000`000139bc 00000000`00000025 00000000`00000000 00000000`00000000 : intelppm!PepIdleExecute+0x2e
ffffdd83`5c08eff0 fffff804`78e17274 : 00000000`00000000 00001f80`0000000c 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x10c6
ffffdd83`5c08f3f0 fffff804`78ffa744 : ffffffff`00000000 ffffb800`4b4f6440 ffffcd8d`5655a080 00000000`00000650 : nt!PoIdle+0x374
ffffdd83`5c08f560 00000000`00000000 : ffffdd83`5c090000 ffffdd83`5c089000 00000000`00000000 00000000`00000000 : 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:
ffffb800`4b55b908 fffff804`790b440a : 00000000`00000124 00000000`00000000 ffffcd8d`33003028 00000000`b2000000 : nt!KeBugCheckEx
ffffb800`4b55b910 fffff804`770715b0 : 00000000`00000000 ffffcd8d`33003028 ffffcd8d`2d547c20 ffffcd8d`33003028 : nt!HalBugCheckSystem+0xca
ffffb800`4b55b950 fffff804`791b61ee : 00000000`00000000 ffffb800`4b55b9f9 ffffcd8d`33003028 ffffcd8d`2d547c20 : PSHED!PshedBugCheckSystem+0x10
ffffb800`4b55b980 fffff804`790b5d31 : ffffcd8d`4aa12800 ffffcd8d`4aa12800 ffffcd8d`2d547c70 ffffcd8d`2d547c20 : nt!WheaReportHwError+0x46e
ffffb800`4b55ba60 fffff804`790b60a3 : 00000000`00000007 ffffcd8d`2d547c70 ffffcd8d`2d547c20 00000000`00000007 : nt!HalpMcaReportError+0xb1
ffffb800`4b55bbd0 fffff804`790b5f80 : ffffcd8d`2cefdab8 00000000`00000001 00000000`00000000 6574746f`67726f66 : nt!HalpMceHandlerCore+0xef
ffffb800`4b55bc20 fffff804`790b61d1 : 00000000`00000010 00000000`00000001 00000000`00000000 67726154`20656874 : nt!HalpMceHandler+0xe0
ffffb800`4b55bc60 fffff804`790b543b : 00000000`00000000 00000000`00000000 ffffb800`4b55bef0 69662072`65626d75 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffb800`4b55bc90 fffff804`790b7c85 : ffffcd8d`2cefdab8 74732073`65697469 20657275`74637572 65757120`61206e69 : nt!HalpHandleMachineCheck+0x5f
ffffb800`4b55bcc0 fffff804`7910d519 : 20736177`20505249 706f7270`20746f6e 696e6920`796c7265 64657a69`6c616974 : nt!HalHandleMcheck+0x35
ffffb800`4b55bcf0 fffff804`79005cfa : 72646461`20656854 6c656966`20737365 65687420`666f2064 63207972`65757120 : nt!KiHandleMcheck+0x9
ffffb800`4b55bd20 fffff804`790059b7 : 00000000`00000000 fffff804`790058ec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffb800`4b55be60 fffff804`9831138f : fffff804`9831f23e 00000000`00000000 fffff804`79161e43 00000027`dc29b9c0 : nt!KiMcheckAbort+0x277
ffffdd83`5c08ef98 fffff804`9831f23e : 00000000`00000000 fffff804`79161e43 00000027`dc29b9c0 ffffb800`4b4eb180 : intelppm!MWaitIdle+0x1f
ffffdd83`5c08efa0 fffff804`78e184b6 : 00000000`000139bc 00000000`00000025 00000000`00000000 00000000`00000000 : intelppm!PepIdleExecute+0x2e
ffffdd83`5c08eff0 fffff804`78e17274 : 00000000`00000000 00001f80`0000000c 00000000`00000003 00000000`00000002 : nt!PpmIdleExecuteTransition+0x10c6
ffffdd83`5c08f3f0 fffff804`78ffa744 : ffffffff`00000000 ffffb800`4b4f6440 ffffcd8d`5655a080 00000000`00000650 : nt!PoIdle+0x374
ffffdd83`5c08f560 00000000`00000000 : ffffdd83`5c090000 ffffdd83`5c089000 00000000`00000000 00000000`00000000 : 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-10-general
info.txt (784.4 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Docs-4663 avatar image
0 Votes"
Docs-4663 answered

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
.
.
.
.
.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CarlFan-MSFT avatar image
0 Votes"
CarlFan-MSFT answered

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



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.