[SOLVED] BDOS Screen while gaming/browsing

[Christian23_23]

I've assembled this pc almost one year ago and these crashes started to happen from a week ago.

CPU: I5 9600k;
Ram: 8GBx2 HyperX Fury;
MTB: MSI z390-a PRO;
PSU: Corsair VS650;
GPU: MSI Nvidia GTX 1660;
SSD Samsung, where Windows 10 is installed;
HD: WD blue 3 TB.

I've already done twice a clean install of Windows 10 and it continue to crash almost every day while browsing using netflix or during gaming.
I've done stress test with Prime95 for about one hour with stable temperature around 70 C and the Memtest for about an hour and it doesn't show me a single error.
The cpu is not overcloked, same as the ram. The XMP profile is not active. Same as the Graphics card.


I attach the dmp file:

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 conditon. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffff9d036159d028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f6100780, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000060010, Low order 32-bits of the MCi_STATUS value.

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

fffff807316283b8: Unable to get Flags value from nt!KdVersionBlock
fffff807316283b8: Unable to get Flags value from nt!KdVersionBlock
fffff807316283b8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4718

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 36104

Key : Analysis.Memory.CommitPeak.Mb
Value: 87

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1

Key : WHEA.MCiStatus.Code
Value: 0xf610078000060010

Key : WHEA.MCiStatus.McaError
Value: 0x0010

Key : WHEA.MCiStatus.ModelError
Value: 0x0006

Key : WHEA.MCiStatus.Reserved
Value: 0x00100780


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9d036159d028

BUGCHECK_P3: f6100780

BUGCHECK_P4: 60010

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 2

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffff8d003f7ccad8 fffff807311a4178 : 0000000000000124 0000000000000000 ffff9d036159d028 00000000f6100780 : nt!KeBugCheckEx
ffff8d003f7ccae0 fffff80732981920 : ffff9d035a7e4e70 0000000000000000 ffff9d036159d028 0000000000000000 : hal!HalBugCheckSystem+0xd8
ffff8d003f7ccb20 fffff80731540052 : ffff9d035a7e4e70 ffff8d003f7ccba9 0000000000000000 ffff9d036159d028 : PSHED!PshedBugCheckSystem+0x10
ffff8d003f7ccb50 fffff807311a5ad6 : ffff8d003f7ccc70 0000000000000001 ffff9d035a7e4ec0 ffff9d035a7e4e70 : nt!WheaReportHwError+0x382
ffff8d003f7ccc10 fffff807311a5f6a : 0000000000000010 ffff9d035a7e4ec0 ffff8d003f7ccdc8 ffff8d003f7cd010 : hal!HalpMcaReportError+0x72
ffff8d003f7ccd70 fffff807311a5e44 : ffff9d035a6b69a0 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xf2
ffff8d003f7ccdc0 fffff807311a60b0 : 0000000000000006 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xe0
ffff8d003f7cce00 fffff807311a5158 : 0000000000000000 ffff8d003f7cd090 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffff8d003f7cce30 fffff807311a6337 : ffff9d035a6b69a0 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
ffff8d003f7cce60 fffff807314a42d0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
ffff8d003f7cce90 fffff807313d2afa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x10
ffff8d003f7ccec0 fffff807313d27af : 0000000000000000 0000000000000000 000002934bed5950 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff8d003f7cd000 00007ffc94e1881c : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x26f
000000dd7ae7d400 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`94e1881c


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BANK0_MSCOD0006_MCACOD0010_PCC_UC_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {42c21059-a8a3-ac4c-c29f-5d0f8ab0967b}

Followup: MachineOwner.


The first crash happened in the Windows 10 version: 20H2.

I've noticed that in the dmp file the PROCESS_NAME: dwm.exe and it shows MODULE_NAME: GenuineIntel.
The problem could be CPU related?

 

[Colif]

Most WHEA errors will mention the type of processor you are using in the error text.
WHEA are errors called by CPU but not necessarily caused by it.
Since it survives installs its likely hardware of some kind
DWM.exe could be a clue as its the Windows Desktop Manager and could point you in direction of GPU drivers/card
Its not often I see WHEA errors caused by GPU drivers so I am cautious about that.

and it continue to crash almost every day while browsing using netflix or during gaming.

crashing during gaming is also a sign it could be GPU.

Now you could remove the GPU and run off the Intel HD graphics on CPU and at least watch netflix and see if problem occurs. Would remove gpu as possible cause. if you still crash.

Another way is run benchmarks on GPU and see if you crash, but games act as good benchmarks these days.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. copy that file to documents
2. upload the copy from documents to a file sharing web site,
3. and share the link in your thread so we can help fix the problem

 

[Christian23_23]

Thank you Colif for you answer.
This is the dmp file: https://we.tl/t-SuaoXXMMde

In the mean time, i'll run the GPU benchmark and i'll let you know the results.

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/zf73L62b/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	121720-6703-02.dmp (Dec 17 2020 - 15:27:14)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	memory_corruption (Process: dwm.exe)
Uptime:	0 Day(s), 0 Hour(s), 00 Min(s), and 36 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/Z390-A-PRO
You have the latest BIOS already installed.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Christian23_23]

Thank you for your reply gardenman,
Actually there is an update. Windows 10 crashed again after 2 weeks with different errors. Here the dmp log:



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 conditon. Try !errrec Address of the WHEA_ERROR_RECORD structure to get more details.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffb18dece3c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f611b840, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000060010, Low order 32-bits of the MCi_STATUS value.

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

fffff8003d40f330: Unable to get Flags value from nt!KdVersionBlock
fffff8003d40f330: Unable to get Flags value from nt!KdVersionBlock
*
* *
* *
* 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 *
* *
*
fffff8003d40f330: Unable to get Flags value from nt!KdVersionBlock
*
* *
* *
* 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: 4514

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-H8Q9PU1

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 23053

Key : Analysis.Memory.CommitPeak.Mb
Value: 91

Key : Analysis.System
Value: CreateObject

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

Key : WHEA.MCiStatus.Code
Value: 0xf611b84000060010

Key : WHEA.MCiStatus.McaError
Value: 0x0010

Key : WHEA.MCiStatus.ModelError
Value: 0x0006

Key : WHEA.MCiStatus.Reserved
Value: 0x0011b840


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffb18dece3c028

BUGCHECK_P3: f611b840

BUGCHECK_P4: 60010

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: chrome.exe

STACK_TEXT:
ffffd601af86e8e8 fffff8003ccb37ba : 0000000000000124 0000000000000000 ffffb18dece3c028 00000000f611b840 : nt!KeBugCheckEx
ffffd601af86e8f0 fffff8003a4b15b0 : 0000000000000000 ffffb18dece3c028 ffffb18dec3fee70 ffffb18dece3c028 : nt!HalBugCheckSystem+0xca
ffffd601af86e930 fffff8003cdb532e : 0000000000000000 ffffd601af86e9d9 ffffb18dece3c028 ffffb18dec3fee70 : PSHED!PshedBugCheckSystem+0x10
ffffd601af86e960 fffff8003ccb50e1 : ffffb18dec320a80 ffffb18dec320a80 ffffb18dec3feec0 ffffb18dec3fee70 : nt!WheaReportHwError+0x46e
ffffd601af86ea40 fffff8003ccb5453 : 0000000000000001 ffffb18dec3feec0 ffffb18dec3fee70 0000000000000001 : nt!HalpMcaReportError+0xb1
ffffd601af86ebb0 fffff8003ccb5330 : ffffb18dec2e39a8 48d88b0000000001 0000000000000000 0000091c840fc000 : nt!HalpMceHandlerCore+0xef
ffffd601af86ec00 fffff8003ccb5581 : 0000000000000006 0000000000000001 0000000000000000 8274c98548ff95ee : nt!HalpMceHandler+0xe0
ffffd601af86ec40 fffff8003ccb47eb : 0000000000000000 0000000000000000 ffffd601af86eed0 44894888458d4898 : nt!HalpMceHandlerWithRendezvous+0xc9
ffffd601af86ec70 fffff8003ccb7035 : ffffb18dec2e39a8 880fc085d88b0000 8b10578bffffff5b cf850f02fa83804d : nt!HalpHandleMachineCheck+0x5f
ffffd601af86eca0 fffff8003cd0c769 : 047e052b4808478b af850fc08548ff96 00000007ba000007 0004bc41b0758b4c : nt!HalHandleMcheck+0x35
ffffd601af86ecd0 fffff8003cc048fa : 7f83000009dd820f 00000bb5840f0c10 850f02f88310478b 48078b48000007af : nt!KiHandleMcheck+0x9
ffffd601af86ed00 fffff8003cc045b7 : 0000000000000000 0000000000000000 ffffffffffffff01 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffd601af86ee40 00007ffeb854c274 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x277
00000034c31fec90 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffe`b854c274


MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_0_GenuineIntel_BANK0_MSCOD0006_MCACOD0010_PCC_UC_IMAGE_GenuineIntel.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {42c21059-a8a3-ac4c-c29f-5d0f8ab0967b}

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


What is the cause for these errors?

 

[Colif]

I must have missed this one...

the whea error that occurred on 20th December appears it was caused by LAN drivers. I have never seen LAN drivers cause whea before

Feb 03 2020

e1d68x64.sys

Intel(R) Gigabit Adapter driver

took a while to find it. See the 2nd link here - https://downloadcenter.intel.com/product/82186/Intel-Ethernet-Connection-I219-V

I would think the last one is also likely Ethernet drivers since Chrome crashed.

what BT do you have?

Aug 07 2013

bcbtums.sys

Broadcom Bluetooth Firmware Download Filter driver

this is not a win 10 driver.