Processors
Processors (Intel® Core™, Intel® Xeon®, etc); processor utilities and programs (Intel® Processor Identification Utility, Intel® Extreme Tuning Utility, Intel® Easy Streaming Wizard, etc.)
12157 Discussions

pc crashing while running programs simultaneously with internet, crash dump file below

eef569
Beginner
347 Views
Hi, 
this is the crash dump file. what is the problem and how can this be resolved


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: ffff9b0cfc303028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000020189, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3686 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 19049 Key : Analysis.Init.CPU.mSec Value: 281 Key : Analysis.Init.Elapsed.mSec Value: 3167 Key : Analysis.Memory.CommitPeak.Mb Value: 86 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: ffff9b0cfc303028 BUGCHECK_P3: be000000 BUGCHECK_P4: 20189 BLACKBOXBSD: 1 (
!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffdb01`fadc68e8 fffff806`63eb450a : 00000000`00000124 00000000`00000000 ffff9b0c`fc303028 00000000`be000000 : nt!KeBugCheckEx ffffdb01`fadc68f0 fffff806`658715b0 : 00000000`00000000 ffff9b0c`fc303028 ffff9b0c`fb0fbce0 ffff9b0c`fc303028 : nt!HalBugCheckSystem+0xca ffffdb01`fadc6930 fffff806`63fb62fe : 00000000`00000000 ffffdb01`fadc69d9 ffff9b0c`fc303028 ffff9b0c`fb0fbce0 : PSHED!PshedBugCheckSystem+0x10 ffffdb01`fadc6960 fffff806`63eb5e31 : ffff9b0d`003dd900 ffff9b0d`003dd900 ffff9b0c`fb0fbd30 ffff9b0c`fb0fbce0 : nt!WheaReportHwError+0x46e ffffdb01`fadc6a40 fffff806`63eb61a3 : 00000000`0000000a ffff9b0c`fb0fbd30 ffff9b0c`fb0fbce0 00000000`0000000a : nt!HalpMcaReportError+0xb1 ffffdb01`fadc6bb0 fffff806`63eb6080 : ffff9b0c`faeea710 001e0148`00000001 00000000`00000000 00246550`001f0e50 : nt!HalpMceHandlerCore+0xef ffffdb01`fadc6c00 fffff806`63eb62d1 : 00000000`0000000c 00000000`00000001 00000000`00000000 00246aa3`0024697c : nt!HalpMceHandler+0xe0 ffffdb01`fadc6c40 fffff806`63eb553b : 00000000`00000000 00000000`00000000 ffffdb01`fadc6ed0 00246d4f`00246ca8 : nt!HalpMceHandlerWithRendezvous+0xc9 ffffdb01`fadc6c70 fffff806`63eb7d85 : ffff9b0c`faeea710 00246e20`001ef9e4 001edfbc`00246eae 00246eeb`00246eb4 : nt!HalpHandleMachineCheck+0x5f ffffdb01`fadc6ca0 fffff806`63f0d619 : 00247064`00246fdc 0024706c`001e0148 001f0e74`00247577 0024759b`00247580 : nt!HalHandleMcheck+0x35 ffffdb01`fadc6cd0 fffff806`63e05dfa : 00247659`00247620 00247660`001dfaec 001f316c`00247683 002476ab`00247690 : nt!KiHandleMcheck+0x9 ffffdb01`fadc6d00 fffff806`63e05ab7 : 00000000`00000000 fffff806`63e059ec 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a ffffdb01`fadc6e40 fffff806`736a138f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277 ffffda0d`7b4bf5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x1f MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .thread ; .cxr ; 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 ---------
0 Kudos
6 Replies
Alberto_R_Intel
Moderator
328 Views

eef569, Thank you for posting in the Intel® Communities Support.

 

In order for us to provide the most accurate assistance on this subject, we just wanted to confirm a few details about your system:

What is the model of the motherboard?

What is the model of the Intel® Procesor?

If this is a laptop, what is the model of it?

Is this a new computer?

Was it working fine before?

When did the issue start?

Did you make any recent hardware/software changes?

Which Windows* version are you using?

Does the problem happen at home or in the work environment?

Please attach the SSU report so we can verify further details about the components in your platform, please check all the options in the report including the one that says "3rd party software logs":
https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-?product=91...

 

Any questions, please let me know.

 

Regards,
Albert R.

 

Intel Customer Support Technician

Alberto_R_Intel
Moderator
318 Views

Hello eef569, I just wanted to check if you saw the information posted previously and if you need further assistance on this matter?


Regards,

Albert R.


Intel Customer Support Technician


eef569
Beginner
311 Views

Hi Albert.

 

Yes i need assistance on this issue.

Pc hardware details

Processor - i7-8700L 3.70GHz

Motherboard - Asus TUF Gaming Z370

Windows10 Pro  20H2 - recently updated

added a new 16gb ram 3 months back, the issue was there even before this.

adding dropbox link of SSU and latest dump file

 

https://www.dropbox.com/s/d5kswhpcb5y8103/SSU.zip?dl=0https://www.dropbox.com/sh/d0pm5d2b6r74vye/AAD...

 

 

Alberto_R_Intel
Moderator
303 Views

Hi eef569, Thank you very much for providing that information and the SSU report.


In order to rule out any hardware problem with the Intel® Core™ i7-8700K, please install and run the Intel® Processor Diagnostic Tool, it does an overall test on the unit and if it passes the test it means it is working properly and the issue is related to another component, once you get the chance, please let us know the results:

https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool


What is the name of the programs that are crashing?

Were they working fine before?


Regards,

Albert R.


Intel Customer Support Technician


eef569
Beginner
292 Views

test.JPG

 Hi Albert,

attached the IPDT test results, the issue is happening when im playing online game (Apex Legends) sometimes while browsing internet, Pcoip client (WFH utility). I have installed and played non online games in pc but this issue doesn't occur at that time.  I tried running driver verifier but the crashes doesnt create a dump file.

Alberto_R_Intel
Moderator
283 Views

Hi eef569, Thank you very much for sharing those results and the picture.


Perfect, excellent, it is great to hear the Intel® Processor passed the test because that means it is working properly and the issue then is related to a different component.


Now, according to the SSU report, the Intel® Graphics controller is not activated in your platform, all the graphics portion of the computer is being supported by AMD Radeon RX 5700 XT.


So, in this case, the next thing to do will be to get in contact directly with AMD to make sure that the latest graphics driver provided by them is currently installed in your system and for further assistance on this matter:

https://www.amd.com/en/support


Regards,

Albert R.


Intel Customer Support Technician



Reply