Question help me pls, this problem already 1 year :'(

[Cattor]

Microsoft (R) Windows Debugger Version 10.0.18362.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072319-7046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff80471c00000 PsLoadedModuleList = 0xfffff804720432f0
Debug session time: Tue Jul 23 12:40:47.716 2019 (UTC + 8:00)
System Uptime: 0 days 18:14:42.484
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
2: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: ffff9801b9ccccd0
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9801b9ccccd0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x9C_GenuineIntel

CPU_COUNT: 6

CPU_MHZ: af8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-URO3LD3

ANALYSIS_SESSION_TIME: 07-25-2019 10:04:59.0678

ANALYSIS_VERSION: 10.0.18362.1 x86fre

BAD_STACK_POINTER: ffff9801b9cccc98

LAST_CONTROL_TRANSFER: from fffff80471ba61f1 to fffff80471dbc900

STACK_TEXT:
ffff9801b9cccc98 fffff80471ba61f1 : 000000000000009c 0000000000000000 ffff9801b9ccccd0 0000000000000000 : nt!KeBugCheckEx
ffff9801b9cccca0 fffff80471ba677d : 0000000000000006 ffff9801b9ccd010 0000000000000000 0000000000000000 : hal!HalpMcaReportError+0x11d
ffff9801b9ccce00 fffff80471ba57c8 : 0000000000000000 ffff9801b9ccd090 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0x131
ffff9801b9ccce30 fffff80471ba69a7 : ffffde03e0cd8ae0 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
ffff9801b9ccce60 fffff80471ea1e60 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
ffff9801b9ccce90 fffff80471dcb8ba : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x10
ffff9801b9cccec0 fffff80471dcb571 : ffff980100000000 fffff80471dcb4ae ffff9801b9cc0180 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff9801b9ccd000 fffff8048f34138f : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x271
fffff40441c3f6a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : intelppm!MWaitIdle+0x1f


THREAD_SHA1_HASH_MOD_FUNC: 7c5c59ad39e6527cb43445b5353a8a9ae211ef69

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 508569533680281e900705b003e24f391a869693

THREAD_SHA1_HASH_MOD: 017fb57dd2c8bb08a42a859207056f83b9fd79be

FOLLOWUP_IP:
intelppm!MWaitIdle+1f
fffff804`8f34138f 4585c9 test r9d,r9d

FAULT_INSTR_CODE: 75c98545

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: intelppm!MWaitIdle+1f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.18362.1083

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1f

FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

PRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_intelppm!MWaitIdle

TARGET_TIME: 2019-07-23T04:40:47.000Z

OSBUILD: 18362

OSSERVICEPACK: 239

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1972-02-02 16:33:06

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 5241

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_intelppm!mwaitidle

FAILURE_ID_HASH: {d82f1232-e6fd-ac41-d01e-ddeec73b684b}

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

 

[Colif]

Can you do the 2 steps in the 1st post here and we see what we can do to help

https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/

Try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

Machine Check Exceptions, otherwise known as WHEA errors are errors called by the CPU but not necessarily caused by it.
They can be caused by any hardware
They can be caused by overclocking so remove any that you may have.
Can be caused by overclocking software so remove things like Intel Extreme Overclocking utility, MSI Afterburner, AI Suite or GPU Tweak 2 - if you have any Asus hardware
Can be caused by over heating so make sure PC is clean inside.
Updating BIOS can help fix these errors

The dump files will tell us if any of those things might be cause.

 

[Cattor]

Can you do the 2 steps in the 1st post here and we see what we can do to help

https://forums.tomshardware.com/thr...nclude-in-blue-screen-of-death-posts.3468965/

Try running this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

Machine Check Exceptions, otherwise known as WHEA errors are errors called by the CPU but not necessarily caused by it.
They can be caused by any hardware
They can be caused by overclocking so remove any that you may have.
Can be caused by overclocking software so remove things like Intel Extreme Overclocking utility, MSI Afterburner, AI Suite or GPU Tweak 2 - if you have any Asus hardware
Can be caused by over heating so make sure PC is clean inside.
Updating BIOS can help fix these errors

The dump files will tell us if any of those things might be cause.

i switch off the Gpu oc , need some time to figure out work or not. And my ram is oc to 2666 in bios that will cause this error?

 

[Colif]

Not sure about ram, it might

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

if you can get the dumps out of c:/windows/minidump (I see its set up already)
copy the files to another folder
upload copies to a file sharing website and show a link here

and do other tests, i can send the dump files to a friend who will convert them into a format I can read