[SOLVED] BSODs

[MDarko88]

Sometimes I get BSOD sometimes just hard freeze. I had basic dump set up, but figured full dump would be more useful to you guys however last time it said something like "contextstatefailed". Im in safe mode right now, so cant check. Been going on over a month now, to the point I cant make it past 5 minutes without freezing or getting BSOD. If you need any info please let me know and I'll get what I can ASAP.

Gigabyte 1070 ti
msi z-370 a-pro
T-Force 16 gb 3000mhz
i7-8700k

 

[MDarko88]

Most recent dump:

Spoiler: Dump file

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Full address space is available


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff8041d800000 PsLoadedModuleList = 0xfffff8041e42a2b0
Debug session time: Thu Dec 17 22:24:42.658 2020 (UTC - 8:00)
System Uptime: 0 days 0:06:30.313
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
Unable to read KLDR_DATA_TABLE_ENTRY at 0000000000000000 - NTSTATUS 0xC0000147 WARNING: .reload failed, module list may be incomplete GetContextState failed, 0xD0000147 CS descriptor lookup failed GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 For analysis of this file, run !analyze -v GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 Unable to get current machine context, NTSTATUS 0xC0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 Unable to get program counter GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 fffff8041dbf5780 48894c2408 mov qword ptr [rsp+8],rcx ss:00000000`00000008=????????????????
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
0: kd> !analyze -v
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
***

• *
• Bugcheck Analysis *
• *

***

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffa480af4c4180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.

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

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

[ Errors clipped out. ]

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 15

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 32

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

Key : Analysis.System
Value: CreateObject

Key : WER.CorruptModuleList
Value: 1

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffa480af4c4180

BUGCHECK_P4: 7

STACK_TEXT:
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_CLOCK_WATCHDOG_TIMEOUT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {505a7e83-2b57-2f1c-5666-16c4a774a5e4}

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

WARNING: Unable to reset page directories
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147

Mod Edit: Cleaned up huge log file by placing it in a spoiler. - gardenman

 

[MDarko88]

And after having switched it back to automatic dump - I get same contextstate failed thing - even though 30 minutes earlier I had gotten actual read outs. Most recent on automatic dump file.

Spoiler: Dump file

Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80026000000 PsLoadedModuleList = 0xfffff80026c2a2b0
Debug session time: Thu Dec 17 22:50:15.812 2020 (UTC - 8:00)
System Uptime: 0 days 0:10:23.467
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
Unable to read KLDR_DATA_TABLE_ENTRY at 0000000000000000 - HRESULT 0x80004002 Loading unloaded module list ......... WARNING: .reload failed, module list may be incomplete GetContextState failed, 0xD0000147 CS descriptor lookup failed GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 For analysis of this file, run !analyze -v GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 Unable to get current machine context, NTSTATUS 0xC0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 Unable to get program counter GetContextState failed, 0xD0000147 GetContextState failed, 0xD0000147 fffff800263f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:00000000`00000008=????????????????
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
0: kd> !analyze -v
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
***

• *
• Bugcheck Analysis *
• *

***

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd3818c1ca180, The PRCB address of the hung processor.
Arg4: 0000000000000006, The index of the hung processor.

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

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

[ Errors clipped out ]

GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 15

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 60

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

Key : Analysis.System
Value: CreateObject

Key : WER.CorruptModuleList
Value: 1

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 101

BUGCHECK_P1: 10

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd3818c1ca180

BUGCHECK_P4: 6

STACK_TEXT:
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_CLOCK_WATCHDOG_TIMEOUT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {505a7e83-2b57-2f1c-5666-16c4a774a5e4}

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

WARNING: Unable to reset page directories
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147

Mod Edit: Cleaned up huge log file by placing it in a spoiler. - gardenman

 

[MDarko88]

I will not that I have replaced RAM, PSU - as well as having done multiple clean installs of Win10 on each of my 3 drives to see if it was a drive issue. I've reseated and repasted cpu multiple times as well.

 

[johnbl]

I will not that I have replaced RAM, PSU - as well as having done multiple clean installs of Win10 on each of my 3 drives to see if it was a drive issue. I've reseated and repasted cpu multiple times as well.

you are getting a hung CPU core
one core is trying to talk to another core and it is not getting a response and figures that the CPU is hung so it calls a bugcheck.

it looks like you have the kernel memory dump C:\Windows\MEMORY.DMP
you should put it on a server like microsoft onedrive, share the file for public access and let me take a quick look.

the most common cause for this would be overclocking drivers, overheating, and plug and play issues.
ie things like a USB network driver being installed on one core while another core tries to run a network function. if the install fails and retries over and over then the second CPU core will not be able to run the network function and it would call a bugcheck thinking that the first core is hung. (even when it is not and just trying the install over and over)

each bugcheck showed a different hung core.

in the debugger with a kernel memory dump
(this command will show what is running on each core)
!running -ti

(this command will show if you have plug and play issues)
!pnptriage

 

[MDarko88]

you are getting a hung CPU core
one core is trying to talk to another core and it is not getting a response and figures that the CPU is hung so it calls a bugcheck.

it looks like you have the kernel memory dump C:\Windows\MEMORY.DMP
you should put it on a server like microsoft onedrive, share the file for public access and let me take a quick look.

the most common cause for this would be overclocking drivers, overheating, and plug and play issues.
ie things like a USB network driver being installed on one core while another core tries to run a network function. if the install fails and retries over and over then the second CPU core will not be able to run the network function and it would call a bugcheck thinking that the first core is hung. (even when it is not and just trying the install over and over)

each bugcheck showed a different hung core.

in the debugger with a kernel memory dump
(this command will show what is running on each core)
!running -ti

(this command will show if you have plug and play issues)
!pnptriage

I hope I've uploaded this correctly, but here is the link to the most recent memdump I have.
https://1drv.ms/u/s!AoRQc05jva1uhxfEH2uDUxX5_D8d?e=XRsxUe

Thanks!

 

[johnbl]

looking at the memory dump:
the system bugchecked because of a error in the CPU displayed as:
severity : Fatal
Error Type : Micro-Architectural Error
Error : Internal timer (Proc 1 Bank 4)

your plug and play devices have a error

DevNode 0xffff938933a70c30 for PDO 0xffff9389355ba120
InstancePath is "HID\VID_0951&PID_16A4&MI_03&Col02\7&1c94fa2&0&0001"
ServiceName is "WUDFRd"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_DISABLED
Problem Status = 0x00000000

I am guessing it it your HyperX Virtual Surround Sound Speed
and it is not working but still trying to start up.
you might want to check to see if you can get a firmware update for your device.
Cloud Virtual 7.1 Surround Sound | HyperX (hyperxgaming.com)
or go into control panel device manager, select view, show hidden devices. see if you find the device and remove the software for it. I think it is on usb 3 port 11

try to fix this device or get it totally removed and reboot.

i will try to look further in the memory dump to see if I can find anything more useful.

 

[MDarko88]

looking at the memory dump:
the system bugchecked because of a error in the CPU displayed as:
severity : Fatal
Error Type : Micro-Architectural Error
Error : Internal timer (Proc 1 Bank 4)

your plug and play devices have a error

DevNode 0xffff938933a70c30 for PDO 0xffff9389355ba120
InstancePath is "HID\VID_0951&PID_16A4&MI_03&Col02\7&1c94fa2&0&0001"
ServiceName is "WUDFRd"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_DISABLED
Problem Status = 0x00000000

I am guessing it it your HyperX Virtual Surround Sound Speed
and it is not working but still trying to start up.
you might want to check to see if you can get a firmware update for your device.
Cloud Virtual 7.1 Surround Sound | HyperX (hyperxgaming.com)
or go into control panel device manager, select view, show hidden devices. see if you find the device and remove the software for it. I think it is on usb 3 port 11

try to fix this device or get it totally removed and reboot.

i will try to look further in the memory dump to see if I can find anything more useful.

Thank you. Yes I've looked at event viewer, and seen HID compliant headset errors before, I've tried uninstalling, and disabling it in the past.

 

[johnbl]

I would go into bios and disable intel turbo boost (or intel speed step) and see if you still get this problem. (if you know the cpu is not overheated)

• also check your temps. I was thinking of overheating because your clock rate was
• 4 Mhz below the 3.7GHz base frequency of the CPU. (could be down throttling due to overheating)
• it could also be a graphics card pulling too much power and causing partial power failure to the CPU.

looking at the memory dump:
the system bugchecked because of a error in the CPU displayed as:
severity : Fatal
Error Type : Micro-Architectural Error
Error : Internal timer (Proc 1 Bank 4)

your plug and play devices have a error

DevNode 0xffff938933a70c30 for PDO 0xffff9389355ba120
InstancePath is "HID\VID_0951&PID_16A4&MI_03&Col02\7&1c94fa2&0&0001"
ServiceName is "WUDFRd"
State = DeviceNodeInitialized (0x302)
Previous State = DeviceNodeUninitialized (0x301)
Problem = CM_PROB_DISABLED
Problem Status = 0x00000000

I am guessing it it your HyperX Virtual Surround Sound Speed
and it is not working but still trying to start up.
you might want to check to see if you can get a firmware update for your device.
Cloud Virtual 7.1 Surround Sound | HyperX (hyperxgaming.com)
or go into control panel device manager, select view, show hidden devices. see if you find the device and remove the software for it. I think it is on usb 3 port 11

try to fix this device or get it totally removed and reboot.

i will try to look further in the memory dump to see if I can find anything more useful.

any chance the CPU over heated?
all of your active cpu cores tried to flush info and failed then all called a machine check abort.
system was up for 7 minutes.

I see log entries for a USB 2.0 wireless card, but it looked like network traffic was going thru a wired card.
Are you using both?

 

[MDarko88]

any chance the CPU over heated?
all of your active cpu cores tried to flush info and failed then all called a machine check abort.
system was up for 7 minutes.

I see log entries for a USB 2.0 wireless card, but it looked like network traffic was going thru a wired card.
Are you using both?

I uninstalled headset software, unplugged them, and tried to start out of safe mode and I hard froze after a couple of minutes.

As to your question, Im just barely more than a layman, could you elaborate? You mean like wifi vs ethernet network traffic? I have both, but if I use ethernet, unless theyre both being used.

Also temps on CPU are pretty normal, both during idle - and a few weeks ago when I wasnt freezing/BSOD after a couple of minutes of pc being on, temps were normal under stress tests.

 

[johnbl]

I uninstalled headset software, unplugged them, and tried to start out of safe mode and I hard froze after a couple of minutes.

As to your question, Im just barely more than a layman, could you elaborate? You mean like wifi vs ethernet network traffic? I have both, but if I use ethernet, unless theyre both being used.

Also temps on CPU are pretty normal, both during idle - and a few weeks ago when I wasnt freezing/BSOD after a couple of minutes of pc being on, temps were normal under stress tests.

the ethernet should not be a problem. it was just your device was usb 2 and everything was going to the usb 3 bus and you had one failed audio device on the bus.

something took out all of the cpu cores at one time. I would try going into bios and disable any intel turbo (or what ever it is called) and see if things work better.

 

[MDarko88]

the ethernet should not be a problem. it was just your device was usb 2 and everything was going to the usb 3 bus and you had one failed audio device on the bus.

something took out all of the cpu cores at one time. I would try going into bios and disable any intel turbo (or what ever it is called) and see if things work better.

My bios settings are set to default. Ill reset them again. Do you not see anything else?

 

[MDarko88]

the ethernet should not be a problem. it was just your device was usb 2 and everything was going to the usb 3 bus and you had one failed audio device on the bus.

something took out all of the cpu cores at one time. I would try going into bios and disable any intel turbo (or what ever it is called) and see if things work better.

I reset bios again - opened up hwmonitor and started to download a game to see what temps were at freeze/crash point

Package 36c
#1 34c
#2 31c
#3 36c
#4 31c
#5 33c

 

[johnbl]

My bios settings are set to default. Ill reset them again. Do you not see anything else?

I just saw a lot of usb traffic but it would be expected since you had the usb wireless device running.
you might consider just using the wired network to see if the usb was what was messing things up. Hopefully removing the headset from trying to install will help.
it was getting a error about using too small of a buffer and was not working but still tried to install 40 times. it is pretty rare to see all of the actual cores calling for a bugcheck at the same time. you were using a vpn also correct? not that it would be a problem, i remember the traffic but did not check for the drivers and the versions.

normally, to get all of the cores to stop working at the same time you would look for heating problems. or maybe power for the cpu. heat and power fluctuations tend to cause the CPU to glitch just like overclocking problems. That is why I suggested turning off any turbo like functions in the bios.
for example, if you run a graphic app, then the gpu used more than the max 75w from the PCI bus the motherboard protection might kick in, if it does not then the power to the CPU might drops some and cause issues with some of the logic inside the CPU that transfers data from the memory inside the CPU to the actual cpu. this can cause the CPU to get internal errors and then call a bugcheck. (kind of like a bad overclock) setting the cpu to a fixed frequency (and lower rate) could help determine if this is occurring.