Hi Abe-22159
Thanks for updating me.
If your computer encounters another BSOD, please share the newly created minidump files for further analysis.
Regards,
Computer Bluescreens when using Discord and Anything
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Greetings everyone!
I am going to be honest here, I am completely stumped as to what is causing this issue. Everytime I use discord video chat while doing something else, my computer bluescreens with the WHEA Uncorrectable error.
All my drivers are up to date, my Bios is running the latest firmware, Windows is up to date and yet it continues to happen. Nothing else that I do causes this issue, just discord.
Posted below is the recent memdump.
*******************************************************************************
* *
* 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
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: ffffc88713c14028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000070005, 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 timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3296
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 5909
Key : Analysis.Init.CPU.mSec
Value: 937
Key : Analysis.Init.Elapsed.mSec
Value: 14201
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
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: 090422-14593-01.dmp
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffc88713c14028
BUGCHECK_P3: b2000000
BUGCHECK_P4: 70005
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffdb01fc8678e8 fffff8027b0b426a : 0000000000000124 0000000000000000 ffffc88713c14028 00000000b2000000 : nt!KeBugCheckEx
ffffdb01fc8678f0 fffff802787e15b0 : 0000000000000000 ffffc88713c14028 ffffc887101e4660 ffffc88713c14028 : nt!HalBugCheckSystem+0xca
ffffdb01fc867930 fffff8027b1b636e : 0000000000000000 ffffdb01fc8679d9 ffffc88713c14028 ffffc887101e4660 : PSHED!PshedBugCheckSystem+0x10
ffffdb01fc867960 fffff8027b0b5b91 : ffffc8870efe3a80 ffffc8870efe3a80 ffffc887101e46b0 ffffc887101e4660 : nt!WheaReportHwError+0x46e
ffffdb01fc867a40 fffff8027b0b5f03 : 000000000000000d ffffc887101e46b0 ffffc887101e4660 000000000000000d : nt!HalpMcaReportError+0xb1
ffffdb01fc867bb0 fffff8027b0b5de0 : ffffc8870eed4958 0000001100000001 0000000000000000 0000040000000268 : nt!HalpMceHandlerCore+0xef
ffffdb01fc867c00 fffff8027b0b6031 : 0000000000000010 0000000000000001 0000000000000000 01d8971d77e75d5f : nt!HalpMceHandler+0xe0
ffffdb01fc867c40 fffff8027b0b529b : 0000000000000000 0000000000000000 ffffdb01fc867ed0 0000000000000000 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffdb01fc867c70 fffff8027b0b7ae5 : ffffc8870eed4958 0000001800000138 1a00002000000010 0000000000000000 : nt!HalpHandleMachineCheck+0x5f
ffffdb01fc867ca0 fffff8027b10d529 : 1a00002000000030 0000000000000000 00010000000c6b57 0000000000000007 : nt!HalHandleMcheck+0x35
ffffdb01fc867cd0 fffff8027b0079fa : 000c00000002f642 0000000000000000 1a00002000000030 0000000000000000 : nt!KiHandleMcheck+0x9
ffffdb01fc867d00 fffff8027b0076b7 : 0000000000000000 fffff8027b0075ec 0000000000000000 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffdb01fc867e40 fffff80295ad138f : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
fffffc00df0eef78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : intelppm!MWaitIdle+0x1f
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
The Memory is in XMP mode and I do have Sync all cores enabled but other than that, i have no overclock on the system (unless those are considered)
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
5 answers
Sort by: Most helpful
-
Anonymous
2022-09-05T09:11:12+00:00 Thank you for the reply!
I have done most of the things mentioned above without results. I used DDU and nvidia Geforce experience to uninstall and reinstall the drivers. I did the command prompts and still nothing.
I did try running Prime95 as I did not do that test (I used Intel software to validate and test CPU) and boy was I surprised. It immediately crashed when trying to run it with sync all cores enabled. Went into Bios and put it back into auto. Was able to run the test and this was the results after maybe 10 minutes.
FATAL ERROR: Rounding was 0.4992494512, expected less than 0.4
Hardware failure detected running 240K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected running 240K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected running 240K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.4982804795, expected less than 0.4
Hardware failure detected running 240K FFT size, consult stress.txt file.
Edit: I ran Prime95 after resetting the Bios and it was fine. Set back xmp and ran it again, It was fine.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 7.000000000000001%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
DYARI BARHAM 34,356 Reputation points Independent Advisor2022-09-05T08:51:55+00:00 Hi Abe-22159,
Thanks for sharing the minidump files.
The minidump files indicate GenuineIntel.sys. Usually, the error is caused if you are overclocking the CPU or the hardware is faulty.
Since it happens only with Discord, try the steps below:
1-Uninstall the graphics card driver completely using the DDU free tool:
https://www.guru3d.com/files-details/display-dr...
Then, install the latest driver provided on the manufacturer's website.
2-Uninstall any third-party security software and scan for viruses & malware with the free Malwarebytes:
https://www.malwarebytes.com/mwb-download
3-Run Command Prompt as administrator. Type this command and hit enter:
dism.exe /online /cleanup-image /restorehealth
Then, type this command and hit enter:
sfc /scannow
If the issue still persists, try the steps below to fix the issue (Skip a step that you have already tried):
1-If you are overclocking your PC, try running everything (CPU, GPU, system memory) at their stock speeds. See if the issue is still reproducible. Or, turn off XMP profile or set it to Auto.
2-Download then install the latest version of BIOS & Chipset drivers from the manufacturer's website.
3-Test the RAM with the free utility MemTest86, then run a full 8 pass scan to test your RAM for physical errors:
https://www.tenforums.com/tutorials/14201-memte...
4-Check that all the cooling systems such as fan if it is working properly.
5-You can test the CPU with Prime95:
https://www.tenforums.com/tutorials/16474-prime...
Please let me know if you need further assistance and keep me updated.
____________________________________________________________
Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.
-
Anonymous
2022-09-05T07:57:19+00:00 Here are the links to the minidump files as requested!
https://drive.google.com/file/d/18ipMlYdizZrtTLivhUHh8rVOche1sM0c/view?usp=sharing https://drive.google.com/file/d/1NwN81BTqkcx8E5wR10jQ0I9tU0OtiqOQ/view?usp=sharing
https://drive.google.com/file/d/10GdqVItfCNDU4hzFksNyimJBruXEdWo_/view?usp=sharing
https://drive.google.com/file/d/1dTia6WzskZ92-GccUJd6aYllQnYYksVo/view?usp=sharing https://drive.google.com/file/d/18ipMlYdizZrtTLivhUHh8rVOche1sM0c/view?usp=sharing
These all happened within a span of an hour or so
-
DYARI BARHAM 34,356 Reputation points Independent Advisor
2022-09-05T06:40:58+00:00 Hi Abe-22159,
I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.
Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.
Regards,