New
#1
BSOD PC Crash Possibly Caused by Headset
Greetings,
Recently i had a lot of BSOD errors which restarted in most of these times i was playing a game Dead by Daylight in one of them i was playing another game Rainbow six siege and in one of them i was just browsing chrome
The errors seemed kinda random so i didn't really care to dig it up but the last 3 times where pretty consistent almost like 1 bsod per day and all of them running the same game
i talked with microsoft send them the minidumps and he told me through his research on the minidump he sees the problem relies on a usb device connected on PCI Express Root Complex
so he told me to check the device manager and indeed there was a HID-Headset Device with a yellow flag then he made me update windows and the flag was gone
Now 2 things i wonder, one how did he find that the issue is in the root complex so we found the yellow flag on device manager i tried to dig the minidumps with Windbg but i cannot find such thing
And two why a specific game "Dead by daylight" triggered this bsod consistently im worrying of getting the bsod again so im trying to be ready to battle it
Here is the minidump:
Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\071720-15390-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`78200000 PsLoadedModuleList = 0xfffff804`78648190
Debug session time: Fri Jul 17 21:42:52.628 2020 (UTC + 3:00)
System Uptime: 0 days 6:51:52.392
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
1: kd> !analyze -v
*******************************************************************************
* *
* 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffbf0fda103028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000030005, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8047862a3c8: Unable to get Flags value from nt!KdVersionBlock
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G2PO7NF
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 5
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffbf0fda103028
BUGCHECK_P3: b2000000
BUGCHECK_P4: 30005
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: DeadByDaylight-Win64-Shippi
STACK_TEXT:
ffffd600`269ccb78 fffff804`78cff188 : 00000000`00000124 00000000`00000000 ffffbf0f`da103028 00000000`b2000000 : nt!KeBugCheckEx
ffffd600`269ccb80 fffff804`7bc01920 : ffffbf0f`d963e6f0 00000000`00000000 ffffbf0f`da103028 00000000`00000000 : hal!HalBugCheckSystem+0xd8
ffffd600`269ccbc0 fffff804`785410b2 : ffffbf0f`d963e6f0 ffffd600`269ccc49 00000000`00000000 ffffbf0f`da103028 : PSHED!PshedBugCheckSystem+0x10
ffffd600`269ccbf0 fffff804`78d00ae6 : ffffd600`269ccd10 00000000`00000001 ffffbf0f`d963e740 ffffbf0f`d963e6f0 : nt!WheaReportHwError+0x382
ffffd600`269cccb0 fffff804`78d00f7a : 00000000`00000010 ffffbf0f`d963e740 ffffd600`269cce68 ffffd600`269cd0b0 : hal!HalpMcaReportError+0x72
ffffd600`269cce10 fffff804`78d00e54 : ffffbf0f`d92ddbe0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xf2
ffffd600`269cce60 fffff804`78d010c0 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe0
ffffd600`269ccea0 fffff804`78d00168 : 00000000`00000000 ffffd600`269cd130 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffd600`269cced0 fffff804`78d01347 : ffffbf0f`d92ddbe0 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpHandleMachineCheck+0x5c
ffffd600`269ccf00 fffff804`784a4e50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x37
ffffd600`269ccf30 fffff804`783d13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x10
ffffd600`269ccf60 fffff804`783d106f : 00000000`00000000 00000000`00000000 00000144`98db4360 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffd600`269cd0a0 00007ff6`fe78a50a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x26f
0000000e`014c8d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`fe78a50a
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_PARITY
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ad18667d-e4af-4a49-4062-3121e823755f}
Followup: MachineOwner
---------
Quote