Yakup Kurtulan
Hectopat
- Katılım
- 13 Ocak 2014
- Mesajlar
- 2
[CODE title="3"]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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb88eeeec7028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for intelppm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6843
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 12928
Key : Analysis.Init.CPU.mSec
Value: 531
Key : Analysis.Init.Elapsed.mSec
Value: 4086
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
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
FILE_IN_CAB: 112521-6046-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffb88eeeec7028
BUGCHECK_P3: f2000000
BUGCHECK_P4: 10005
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8800`652e08e8 fffff801`50cb453a : 00000000`00000124 00000000`00000000 ffffb88e`eeec7028 00000000`f2000000 : nt!KeBugCheckEx
ffff8800`652e08f0 fffff801`4dbd15b0 : 00000000`00000000 ffffb88e`eeec7028 ffffb88e`ee0a8670 ffffb88e`eeec7028 : nt!HalBugCheckSystem+0xca
ffff8800`652e0930 fffff801`50db61de : 00000000`00000000 ffff8800`652e09d9 ffffb88e`eeec7028 ffffb88e`ee0a8670 : PSHED!PshedBugCheckSystem+0x10
ffff8800`652e0960 fffff801`50cb5e61 : ffffb88e`eeef4b50 ffffb88e`eeef4b50 ffffb88e`ee0a86c0 ffffb88e`ee0a8670 : nt!WheaReportHwError+0x46e
ffff8800`652e0a40 fffff801`50cb61d3 : 00000000`00000001 ffffb88e`ee0a86c0 ffffb88e`ee0a8670 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffff8800`652e0bb0 fffff801`50cb60b0 : ffffb88e`ee0a7d78 08498b48`00000001 00000000`00000000 ffe43ca0`e8ccc328 : nt!HalpMceHandlerCore+0xef
ffff8800`652e0c00 fffff801`50cb6301 : 00000000`00000004 00000000`00000001 00000000`00000000 cccccccc`cccccccc : nt!HalpMceHandler+0xe0
ffff8800`652e0c40 fffff801`50cb556b : 00000000`00000000 00000000`00000000 ffff8800`652e0ed0 10858948`c4334800 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8800`652e0c70 fffff801`50cb7db5 : ffffb88e`ee0a7d78 000001b0`b8412824 3d3944ff`c483cbe8 0fc0570f`00532bf8 : nt!HalpHandleMachineCheck+0x5f
ffff8800`652e0ca0 fffff801`50d0d4c9 : 4c8d48ff`ab91bbe8 00042098`8b486024 c085fff0`422ae800 8b440000`0146880f : nt!HalHandleMcheck+0x35
ffff8800`652e0cd0 fffff801`50c063fa : d5e86024`7c036024 a67d3944`66ffbaa4 44660000`0119840f 00010e84`0ffa7d39 : nt!KiHandleMcheck+0x9
ffff8800`652e0d00 fffff801`50c060b7 : 00000000`00000000 fffff801`50c05fec 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff8800`652e0e40 fffff801`54e944a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffae0d`896297c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x44a2
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
Followup: MachineOwner
---------
[/CODE]
[CODE title="4"]IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8016377c268, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80172c09c49, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5936
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 7428
Key : Analysis.Init.CPU.mSec
Value: 562
Key : Analysis.Init.Elapsed.mSec
Value: 3674
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
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
FILE_IN_CAB: 112521-6156-01.dmp
BUGCHECK_CODE: a
BUGCHECK_P1: fffff8016377c268
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80172c09c49
READ_ADDRESS: fffff801736fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff8016377c268
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Launcher.exe
TRAP_FRAME: ffffaa8d992fb780 -- (.trap 0xffffaa8d992fb780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffaa8d992fb940 rbx=0000000000000000 rcx=ffff8881b5880180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80172c09c49 rsp=ffffaa8d992fb910 rbp=ffffaa8d992fb979
r8=ffffaf8f03c91810 r9=0000000000000000 r10=0000000000000000
r11=ffff787d85e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ExpAcquireResourceExclusiveLite+0x149:
fffff801`72c09c49 8b05192aaf00 mov eax,dword ptr [nt!KiIrqlFlags (fffff801`736fc668)] ds:fffff801`736fc668=????????
Resetting default scope
STACK_TEXT:
ffffaa8d`992fb638 fffff801`72e09269 : 00000000`0000000a fffff801`6377c268 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffaa8d`992fb640 fffff801`72e05569 : 00000000`00000000 ffffaa8d`992fb831 ffffaf8f`076cf080 fffff801`72c0b5d3 : nt!KiBugCheckDispatch+0x69
ffffaa8d`992fb780 fffff801`72c09c49 : ffffaf8f`01911210 ffffaa8d`992fb970 00000000`00010224 fffff801`72d5fe20 : nt!KiPageFault+0x469
ffffaa8d`992fb910 fffff801`72c0902c : fffff801`72cb8e00 00000000`00000001 00000000`00000000 00000000`00000001 : nt!ExpAcquireResourceExclusiveLite+0x149
ffffaa8d`992fb9e0 ffffeaec`e517e672 : ffffaf8f`088745f0 ffffeabf`45d76660 00000000`00e89000 ffffaf8f`088745f0 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x3c
ffffaa8d`992fba20 ffffeaec`e5ab916b : 00000000`00e89000 00000000`0002032e 00000000`0103e468 00000000`000001f4 : win32kbase!EnterCrit+0x1c2
ffffaa8d`992fbb40 ffffeaec`e4d0825f : fffff801`72d22970 ffffaa8d`992fbcc0 00000000`0103e468 ffffaa8d`992fbbe8 : win32kfull!NtUserSetTimer+0x3b
ffffaa8d`992fbb90 fffff801`72e08cb8 : 00000000`00000000 00000000`00000000 ffffeabf`459d52a0 00000000`0002032e : win32k!NtUserSetTimer+0x1f
ffffaa8d`992fbbd0 00007ffa`b21e0254 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0103e448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`b21e0254
SYMBOL_NAME: win32kbase!EnterCrit+1c2
MODULE_NAME: win32kbase
IMAGE_NAME: win32kbase.sys
IMAGE_VERSION: 10.0.19041.1348
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1c2
FAILURE_BUCKET_ID: AV_win32kbase!EnterCrit
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d56d29ce-2532-972b-bc6d-31106c6c0955}
Followup: MachineOwner
---------
[/CODE]
[CODE title="5"]PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff80460c7b300, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff804709b1184, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Type
Value: Read
Key : Analysis.CPU.mSec
Value: 4702
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 8877
Key : Analysis.Init.CPU.mSec
Value: 484
Key : Analysis.Init.Elapsed.mSec
Value: 2759
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
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
FILE_IN_CAB: 112321-6203-01.dmp
BUGCHECK_CODE: 50
BUGCHECK_P1: fffff80460c7b300
BUGCHECK_P2: 0
BUGCHECK_P3: fffff804709b1184
BUGCHECK_P4: 2
READ_ADDRESS: fffff80470cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff80460c7b300
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffd08dc1ff0880 -- (.trap 0xffffd08dc1ff0880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8046c802180 rbx=0000000000000000 rcx=0000000000000200
rdx=0000000000000028 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804709b1184 rsp=ffffd08dc1ff0a10 rbp=fffff80470d23f50
r8=0000000031526d73 r9=0000000000000000 r10=0000000030526d73
r11=0000000000001001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!ExAllocatePoolWithTag+0x24:
fffff804`709b1184 440fb73d749e3400 movzx r15d,word ptr [nt!KeNumberNodes (fffff804`70cfb000)] ds:fffff804`70cfb000=????
Resetting default scope
STACK_TEXT:
ffffd08d`c1ff05d8 fffff804`7044a56f : 00000000`00000050 fffff804`60c7b300 00000000`00000000 ffffd08d`c1ff0880 : nt!KeBugCheckEx
ffffd08d`c1ff05e0 fffff804`7029f390 : ffffaa81`00000000 00000000`00000000 ffffd08d`c1ff0900 00000000`00000000 : nt!MiSystemFault+0x18d1bf
ffffd08d`c1ff06e0 fffff804`7040545e : 00000000`00000000 00000000`00000020 00000000`00000000 ffff8106`69802000 : nt!MmAccessFault+0x400
ffffd08d`c1ff0880 fffff804`709b1184 : 00000000`00000002 00000000`00000062 00000000`30526d73 00000000`00000000 : nt!KiPageFault+0x35e
ffffd08d`c1ff0a10 fffff804`70304095 : ffff8106`72e04450 fffff804`70d23f50 00000000`00000000 ffffd08d`00000000 : nt!ExAllocatePoolWithTag+0x24
ffffd08d`c1ff0a60 fffff804`70303fb0 : ffff8106`72e04450 ffff8106`31526d73 00000000`00000000 fffff804`702cf4d7 : nt!SmFpAllocate+0x5d
ffffd08d`c1ff0ab0 fffff804`70351fcc : 00000000`00023304 ffffd08d`c1ff0b80 00000000`00000003 00000000`00000003 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmpPageEvict+0xc0
ffffd08d`c1ff0b30 fffff804`703be333 : 00000000`20023304 00000000`20023304 20000000`00023304 00000000`00000002 : nt!MiStoreEvictPageFile+0x154
ffffd08d`c1ff0bc0 fffff804`70355855 : ffff8106`6fd77080 ffff8106`6fd77080 00000000`00000080 00038404`ad1b3ffe : nt!MiStoreEvictThread+0x183
ffffd08d`c1ff0d50 fffff804`703fe8f8 : ffffaa81`e8128180 ffff8106`6fd77080 fffff804`70355800 00051dd0`000001b8 : nt!PspSystemThreadStartup+0x55
ffffd08d`c1ff0da0 00000000`00000000 : ffffd08d`c1ff1000 ffffd08d`c1feb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!ExAllocatePoolWithTag+24
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1348
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 24
FAILURE_BUCKET_ID: AV_R_(null)_nt!ExAllocatePoolWithTag
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea5c51f5-d2ed-6893-0897-91f65c1983ca}
Followup: MachineOwner
---------
[/CODE]
Bu PC mavi ekran veriyordu format atıldı ve SSD takıldı. Daha çok mavi ekran vermeye başladı ve SSD sorun yaşattığı düşüncesiyle yeni ssd takıldı ve sorun çözülmedi . Bu minidump dosyaları 2 gün içerisinde gelenler.
[CODE title="1"]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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffcf8f7dae8028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 23523
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 2642
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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
FILE_IN_CAB: 112421-6031-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffcf8f7dae8028
BUGCHECK_P3: f2000000
BUGCHECK_P4: 10005
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: MixLogicService.exe
STACK_TEXT:
ffffe581`940e08e8 fffff804`2b8b453a : 00000000`00000124 00000000`00000000 ffffcf8f`7dae8028 00000000`f2000000 : nt!KeBugCheckEx
ffffe581`940e08f0 fffff804`2a9115b0 : 00000000`00000000 ffffcf8f`7dae8028 ffffcf8f`7cea7670 ffffcf8f`7dae8028 : nt!HalBugCheckSystem+0xca
ffffe581`940e0930 fffff804`2b9b61de : 00000000`00000000 ffffe581`940e09d9 ffffcf8f`7dae8028 ffffcf8f`7cea7670 : PSHED!PshedBugCheckSystem+0x10
ffffe581`940e0960 fffff804`2b8b5e61 : ffffcf8f`7db0dbd0 ffffcf8f`7db0dbd0 ffffcf8f`7cea76c0 ffffcf8f`7cea7670 : nt!WheaReportHwError+0x46e
ffffe581`940e0a40 fffff804`2b8b61d3 : 00000000`00000001 ffffcf8f`7cea76c0 ffffcf8f`7cea7670 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffffe581`940e0bb0 fffff804`2b8b60b0 : ffffcf8f`7cea6d78 08498b48`00000001 00000000`00000000 ffe43ca0`e8ccc328 : nt!HalpMceHandlerCore+0xef
ffffe581`940e0c00 fffff804`2b8b6301 : 00000000`00000004 00000000`00000001 00000000`00000000 cccccccc`cccccccc : nt!HalpMceHandler+0xe0
ffffe581`940e0c40 fffff804`2b8b556b : 00000000`00000000 00000000`00000000 ffffe581`940e0ed0 10858948`c4334800 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffe581`940e0c70 fffff804`2b8b7db5 : ffffcf8f`7cea6d78 000001b0`b8412824 3d3944ff`c483cbe8 0fc0570f`00532bf8 : nt!HalpHandleMachineCheck+0x5f
ffffe581`940e0ca0 fffff804`2b90d4c9 : 4c8d48ff`ab91bbe8 00042098`8b486024 c085fff0`422ae800 8b440000`0146880f : nt!HalHandleMcheck+0x35
ffffe581`940e0cd0 fffff804`2b8063fa : d5e86024`7c036024 a67d3944`66ffbaa4 44660000`0119840f 00010e84`0ffa7d39 : nt!KiHandleMcheck+0x9
ffffe581`940e0d00 fffff804`2b8060b7 : 00000000`00000000 00000000`00000000 00000000`0b08c044 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffe581`940e0e40 00000000`752c9f7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000000`05d9ec58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752c9f7c
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
Followup: MachineOwner[/CODE]
[CODE title="2"]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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffde0dbad0a028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for intelppm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6062
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10448
Key : Analysis.Init.CPU.mSec
Value: 515
Key : Analysis.Init.Elapsed.mSec
Value: 4596
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
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
FILE_IN_CAB: 112421-6140-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffde0dbad0a028
BUGCHECK_P3: f2000000
BUGCHECK_P4: 10005
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff805`088988e8 fffff805`022b453a : 00000000`00000124 00000000`00000000 ffffde0d`bad0a028 00000000`f2000000 : nt!KeBugCheckEx
fffff805`088988f0 fffff805`01a515b0 : 00000000`00000000 ffffde0d`bad0a028 ffffde0d`baa49300 ffffde0d`bad0a028 : nt!HalBugCheckSystem+0xca
fffff805`08898930 fffff805`023b61de : 00000000`00000000 fffff805`088989d9 ffffde0d`bad0a028 ffffde0d`baa49300 : PSHED!PshedBugCheckSystem+0x10
fffff805`08898960 fffff805`022b5e61 : ffffde0d`bad744f0 ffffde0d`bad744f0 ffffde0d`baa49350 ffffde0d`baa49300 : nt!WheaReportHwError+0x46e
fffff805`08898a40 fffff805`022b61d3 : 00000000`00000000 ffffde0d`baa49350 ffffde0d`baa49300 00000000`00000000 : nt!HalpMcaReportError+0xb1
fffff805`08898bb0 fffff805`022b60b0 : ffffde0d`ba0a6cc0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
fffff805`08898c00 fffff805`022b6301 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
fffff805`08898c40 fffff805`022b556b : 00000000`00000000 00000000`00000000 fffff805`08898ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff805`08898c70 fffff805`022b7db5 : ffffde0d`ba0a6cc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
fffff805`08898ca0 fffff805`0230d4c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
fffff805`08898cd0 fffff805`022063fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
fffff805`08898d00 fffff805`022060b7 : 00000000`00000000 fffff805`02205fec 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff805`08898e40 fffff805`096144a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff805`0886e7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x44a2
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BADMEMREF_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {23d7aafb-892d-c705-e202-d8399d77d4a1}
Followup: MachineOwner
---------
[/CODE]
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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb88eeeec7028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for intelppm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6843
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 12928
Key : Analysis.Init.CPU.mSec
Value: 531
Key : Analysis.Init.Elapsed.mSec
Value: 4086
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
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
FILE_IN_CAB: 112521-6046-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffb88eeeec7028
BUGCHECK_P3: f2000000
BUGCHECK_P4: 10005
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8800`652e08e8 fffff801`50cb453a : 00000000`00000124 00000000`00000000 ffffb88e`eeec7028 00000000`f2000000 : nt!KeBugCheckEx
ffff8800`652e08f0 fffff801`4dbd15b0 : 00000000`00000000 ffffb88e`eeec7028 ffffb88e`ee0a8670 ffffb88e`eeec7028 : nt!HalBugCheckSystem+0xca
ffff8800`652e0930 fffff801`50db61de : 00000000`00000000 ffff8800`652e09d9 ffffb88e`eeec7028 ffffb88e`ee0a8670 : PSHED!PshedBugCheckSystem+0x10
ffff8800`652e0960 fffff801`50cb5e61 : ffffb88e`eeef4b50 ffffb88e`eeef4b50 ffffb88e`ee0a86c0 ffffb88e`ee0a8670 : nt!WheaReportHwError+0x46e
ffff8800`652e0a40 fffff801`50cb61d3 : 00000000`00000001 ffffb88e`ee0a86c0 ffffb88e`ee0a8670 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffff8800`652e0bb0 fffff801`50cb60b0 : ffffb88e`ee0a7d78 08498b48`00000001 00000000`00000000 ffe43ca0`e8ccc328 : nt!HalpMceHandlerCore+0xef
ffff8800`652e0c00 fffff801`50cb6301 : 00000000`00000004 00000000`00000001 00000000`00000000 cccccccc`cccccccc : nt!HalpMceHandler+0xe0
ffff8800`652e0c40 fffff801`50cb556b : 00000000`00000000 00000000`00000000 ffff8800`652e0ed0 10858948`c4334800 : nt!HalpMceHandlerWithRendezvous+0xc9
ffff8800`652e0c70 fffff801`50cb7db5 : ffffb88e`ee0a7d78 000001b0`b8412824 3d3944ff`c483cbe8 0fc0570f`00532bf8 : nt!HalpHandleMachineCheck+0x5f
ffff8800`652e0ca0 fffff801`50d0d4c9 : 4c8d48ff`ab91bbe8 00042098`8b486024 c085fff0`422ae800 8b440000`0146880f : nt!HalHandleMcheck+0x35
ffff8800`652e0cd0 fffff801`50c063fa : d5e86024`7c036024 a67d3944`66ffbaa4 44660000`0119840f 00010e84`0ffa7d39 : nt!KiHandleMcheck+0x9
ffff8800`652e0d00 fffff801`50c060b7 : 00000000`00000000 fffff801`50c05fec 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffff8800`652e0e40 fffff801`54e944a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
ffffae0d`896297c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x44a2
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
Followup: MachineOwner
---------
[/CODE]
[CODE title="4"]IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8016377c268, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80172c09c49, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5936
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 7428
Key : Analysis.Init.CPU.mSec
Value: 562
Key : Analysis.Init.Elapsed.mSec
Value: 3674
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
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
FILE_IN_CAB: 112521-6156-01.dmp
BUGCHECK_CODE: a
BUGCHECK_P1: fffff8016377c268
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80172c09c49
READ_ADDRESS: fffff801736fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff8016377c268
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Launcher.exe
TRAP_FRAME: ffffaa8d992fb780 -- (.trap 0xffffaa8d992fb780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffaa8d992fb940 rbx=0000000000000000 rcx=ffff8881b5880180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80172c09c49 rsp=ffffaa8d992fb910 rbp=ffffaa8d992fb979
r8=ffffaf8f03c91810 r9=0000000000000000 r10=0000000000000000
r11=ffff787d85e00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!ExpAcquireResourceExclusiveLite+0x149:
fffff801`72c09c49 8b05192aaf00 mov eax,dword ptr [nt!KiIrqlFlags (fffff801`736fc668)] ds:fffff801`736fc668=????????
Resetting default scope
STACK_TEXT:
ffffaa8d`992fb638 fffff801`72e09269 : 00000000`0000000a fffff801`6377c268 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffaa8d`992fb640 fffff801`72e05569 : 00000000`00000000 ffffaa8d`992fb831 ffffaf8f`076cf080 fffff801`72c0b5d3 : nt!KiBugCheckDispatch+0x69
ffffaa8d`992fb780 fffff801`72c09c49 : ffffaf8f`01911210 ffffaa8d`992fb970 00000000`00010224 fffff801`72d5fe20 : nt!KiPageFault+0x469
ffffaa8d`992fb910 fffff801`72c0902c : fffff801`72cb8e00 00000000`00000001 00000000`00000000 00000000`00000001 : nt!ExpAcquireResourceExclusiveLite+0x149
ffffaa8d`992fb9e0 ffffeaec`e517e672 : ffffaf8f`088745f0 ffffeabf`45d76660 00000000`00e89000 ffffaf8f`088745f0 : nt!ExEnterCriticalRegionAndAcquireResourceExclusive+0x3c
ffffaa8d`992fba20 ffffeaec`e5ab916b : 00000000`00e89000 00000000`0002032e 00000000`0103e468 00000000`000001f4 : win32kbase!EnterCrit+0x1c2
ffffaa8d`992fbb40 ffffeaec`e4d0825f : fffff801`72d22970 ffffaa8d`992fbcc0 00000000`0103e468 ffffaa8d`992fbbe8 : win32kfull!NtUserSetTimer+0x3b
ffffaa8d`992fbb90 fffff801`72e08cb8 : 00000000`00000000 00000000`00000000 ffffeabf`459d52a0 00000000`0002032e : win32k!NtUserSetTimer+0x1f
ffffaa8d`992fbbd0 00007ffa`b21e0254 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0103e448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`b21e0254
SYMBOL_NAME: win32kbase!EnterCrit+1c2
MODULE_NAME: win32kbase
IMAGE_NAME: win32kbase.sys
IMAGE_VERSION: 10.0.19041.1348
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1c2
FAILURE_BUCKET_ID: AV_win32kbase!EnterCrit
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d56d29ce-2532-972b-bc6d-31106c6c0955}
Followup: MachineOwner
---------
[/CODE]
[CODE title="5"]PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff80460c7b300, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff804709b1184, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : AV.Type
Value: Read
Key : Analysis.CPU.mSec
Value: 4702
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 8877
Key : Analysis.Init.CPU.mSec
Value: 484
Key : Analysis.Init.Elapsed.mSec
Value: 2759
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
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
FILE_IN_CAB: 112321-6203-01.dmp
BUGCHECK_CODE: 50
BUGCHECK_P1: fffff80460c7b300
BUGCHECK_P2: 0
BUGCHECK_P3: fffff804709b1184
BUGCHECK_P4: 2
READ_ADDRESS: fffff80470cfb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
fffff80460c7b300
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: ffffd08dc1ff0880 -- (.trap 0xffffd08dc1ff0880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8046c802180 rbx=0000000000000000 rcx=0000000000000200
rdx=0000000000000028 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804709b1184 rsp=ffffd08dc1ff0a10 rbp=fffff80470d23f50
r8=0000000031526d73 r9=0000000000000000 r10=0000000030526d73
r11=0000000000001001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!ExAllocatePoolWithTag+0x24:
fffff804`709b1184 440fb73d749e3400 movzx r15d,word ptr [nt!KeNumberNodes (fffff804`70cfb000)] ds:fffff804`70cfb000=????
Resetting default scope
STACK_TEXT:
ffffd08d`c1ff05d8 fffff804`7044a56f : 00000000`00000050 fffff804`60c7b300 00000000`00000000 ffffd08d`c1ff0880 : nt!KeBugCheckEx
ffffd08d`c1ff05e0 fffff804`7029f390 : ffffaa81`00000000 00000000`00000000 ffffd08d`c1ff0900 00000000`00000000 : nt!MiSystemFault+0x18d1bf
ffffd08d`c1ff06e0 fffff804`7040545e : 00000000`00000000 00000000`00000020 00000000`00000000 ffff8106`69802000 : nt!MmAccessFault+0x400
ffffd08d`c1ff0880 fffff804`709b1184 : 00000000`00000002 00000000`00000062 00000000`30526d73 00000000`00000000 : nt!KiPageFault+0x35e
ffffd08d`c1ff0a10 fffff804`70304095 : ffff8106`72e04450 fffff804`70d23f50 00000000`00000000 ffffd08d`00000000 : nt!ExAllocatePoolWithTag+0x24
ffffd08d`c1ff0a60 fffff804`70303fb0 : ffff8106`72e04450 ffff8106`31526d73 00000000`00000000 fffff804`702cf4d7 : nt!SmFpAllocate+0x5d
ffffd08d`c1ff0ab0 fffff804`70351fcc : 00000000`00023304 ffffd08d`c1ff0b80 00000000`00000003 00000000`00000003 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmpPageEvict+0xc0
ffffd08d`c1ff0b30 fffff804`703be333 : 00000000`20023304 00000000`20023304 20000000`00023304 00000000`00000002 : nt!MiStoreEvictPageFile+0x154
ffffd08d`c1ff0bc0 fffff804`70355855 : ffff8106`6fd77080 ffff8106`6fd77080 00000000`00000080 00038404`ad1b3ffe : nt!MiStoreEvictThread+0x183
ffffd08d`c1ff0d50 fffff804`703fe8f8 : ffffaa81`e8128180 ffff8106`6fd77080 fffff804`70355800 00051dd0`000001b8 : nt!PspSystemThreadStartup+0x55
ffffd08d`c1ff0da0 00000000`00000000 : ffffd08d`c1ff1000 ffffd08d`c1feb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!ExAllocatePoolWithTag+24
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1348
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 24
FAILURE_BUCKET_ID: AV_R_(null)_nt!ExAllocatePoolWithTag
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea5c51f5-d2ed-6893-0897-91f65c1983ca}
Followup: MachineOwner
---------
[/CODE]
Bu PC mavi ekran veriyordu format atıldı ve SSD takıldı. Daha çok mavi ekran vermeye başladı ve SSD sorun yaşattığı düşüncesiyle yeni ssd takıldı ve sorun çözülmedi . Bu minidump dosyaları 2 gün içerisinde gelenler.
[CODE title="1"]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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffcf8f7dae8028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 23523
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 2642
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
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
FILE_IN_CAB: 112421-6031-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffcf8f7dae8028
BUGCHECK_P3: f2000000
BUGCHECK_P4: 10005
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: MixLogicService.exe
STACK_TEXT:
ffffe581`940e08e8 fffff804`2b8b453a : 00000000`00000124 00000000`00000000 ffffcf8f`7dae8028 00000000`f2000000 : nt!KeBugCheckEx
ffffe581`940e08f0 fffff804`2a9115b0 : 00000000`00000000 ffffcf8f`7dae8028 ffffcf8f`7cea7670 ffffcf8f`7dae8028 : nt!HalBugCheckSystem+0xca
ffffe581`940e0930 fffff804`2b9b61de : 00000000`00000000 ffffe581`940e09d9 ffffcf8f`7dae8028 ffffcf8f`7cea7670 : PSHED!PshedBugCheckSystem+0x10
ffffe581`940e0960 fffff804`2b8b5e61 : ffffcf8f`7db0dbd0 ffffcf8f`7db0dbd0 ffffcf8f`7cea76c0 ffffcf8f`7cea7670 : nt!WheaReportHwError+0x46e
ffffe581`940e0a40 fffff804`2b8b61d3 : 00000000`00000001 ffffcf8f`7cea76c0 ffffcf8f`7cea7670 00000000`00000001 : nt!HalpMcaReportError+0xb1
ffffe581`940e0bb0 fffff804`2b8b60b0 : ffffcf8f`7cea6d78 08498b48`00000001 00000000`00000000 ffe43ca0`e8ccc328 : nt!HalpMceHandlerCore+0xef
ffffe581`940e0c00 fffff804`2b8b6301 : 00000000`00000004 00000000`00000001 00000000`00000000 cccccccc`cccccccc : nt!HalpMceHandler+0xe0
ffffe581`940e0c40 fffff804`2b8b556b : 00000000`00000000 00000000`00000000 ffffe581`940e0ed0 10858948`c4334800 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffe581`940e0c70 fffff804`2b8b7db5 : ffffcf8f`7cea6d78 000001b0`b8412824 3d3944ff`c483cbe8 0fc0570f`00532bf8 : nt!HalpHandleMachineCheck+0x5f
ffffe581`940e0ca0 fffff804`2b90d4c9 : 4c8d48ff`ab91bbe8 00042098`8b486024 c085fff0`422ae800 8b440000`0146880f : nt!HalHandleMcheck+0x35
ffffe581`940e0cd0 fffff804`2b8063fa : d5e86024`7c036024 a67d3944`66ffbaa4 44660000`0119840f 00010e84`0ffa7d39 : nt!KiHandleMcheck+0x9
ffffe581`940e0d00 fffff804`2b8060b7 : 00000000`00000000 00000000`00000000 00000000`0b08c044 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffe581`940e0e40 00000000`752c9f7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000000`05d9ec58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752c9f7c
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_PROCESSOR__UNKNOWN_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5371cb52-c3d9-558e-47d4-d31c09567ca2}
Followup: MachineOwner[/CODE]
[CODE title="2"]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
nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffde0dbad0a028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for intelppm.sys
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6062
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10448
Key : Analysis.Init.CPU.mSec
Value: 515
Key : Analysis.Init.Elapsed.mSec
Value: 4596
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
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
FILE_IN_CAB: 112421-6140-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffde0dbad0a028
BUGCHECK_P3: f2000000
BUGCHECK_P4: 10005
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff805`088988e8 fffff805`022b453a : 00000000`00000124 00000000`00000000 ffffde0d`bad0a028 00000000`f2000000 : nt!KeBugCheckEx
fffff805`088988f0 fffff805`01a515b0 : 00000000`00000000 ffffde0d`bad0a028 ffffde0d`baa49300 ffffde0d`bad0a028 : nt!HalBugCheckSystem+0xca
fffff805`08898930 fffff805`023b61de : 00000000`00000000 fffff805`088989d9 ffffde0d`bad0a028 ffffde0d`baa49300 : PSHED!PshedBugCheckSystem+0x10
fffff805`08898960 fffff805`022b5e61 : ffffde0d`bad744f0 ffffde0d`bad744f0 ffffde0d`baa49350 ffffde0d`baa49300 : nt!WheaReportHwError+0x46e
fffff805`08898a40 fffff805`022b61d3 : 00000000`00000000 ffffde0d`baa49350 ffffde0d`baa49300 00000000`00000000 : nt!HalpMcaReportError+0xb1
fffff805`08898bb0 fffff805`022b60b0 : ffffde0d`ba0a6cc0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
fffff805`08898c00 fffff805`022b6301 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
fffff805`08898c40 fffff805`022b556b : 00000000`00000000 00000000`00000000 fffff805`08898ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff805`08898c70 fffff805`022b7db5 : ffffde0d`ba0a6cc0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
fffff805`08898ca0 fffff805`0230d4c9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
fffff805`08898cd0 fffff805`022063fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
fffff805`08898d00 fffff805`022060b7 : 00000000`00000000 fffff805`02205fec 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff805`08898e40 fffff805`096144a2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff805`0886e7c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x44a2
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BADMEMREF_IMAGE_GenuineIntel.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {23d7aafb-892d-c705-e202-d8399d77d4a1}
Followup: MachineOwner
---------
[/CODE]