Windows 10 Regular Blue-screens have begun. WinDB Report 0x80070057

[fuhq11]

I hope I've posted this in the correct location!

I've started getting blue-screens. Have been unsuccessful in finding out what is causing them, and was hoping someone smarter than myself could help me figure out why this is suddenly happening. It's been putting a real damper on my work.

This could be related to networking, as it seems to happen when im connected to the internet and streaming youtube videos.

Let me know if im missing any details

Windows 10 Home (64B)

MSI MS-16h5 (Ghost) Laptop

16gb Ram

i7-5700hq

geforce gtx 970m

killer e2200 & killer 1525 network adapters





Microsoft (R) Windows Debugger Version 10.0.18317.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031019-7296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0
Symbol search path is: srv*
Executable search path is:
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 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff80329898000 PsLoadedModuleList = 0xfffff80329c46150
Debug session time: Sun Mar 10 18:25:58.406 2019 (UTC - 5:00)
System Uptime: 0 days 3:42:39.097
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
.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

Loading User Symbols
For analysis of this file, run !analyze -v
fffff80329a420c0 ?? ??? ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* UCMUCSI_FAILURE (1d8) The UcmUcsi driver has encountered an error. The driver has found settings to trigger a system crash instead of a livedump. Arguments: Arg1: 0000000000000000, A UCSI command has timed out because the firmware did not respond to the command in time. Arg2: 0000000000000000, The UCSI command value. Arg3: 0000000000000000, If non-zero, the pointer to additional information (dt UcmUcsiCx!UCMUCSICX_TRIAGE). Arg4: 0000000000000000 Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. KEY_VALUES_STRING: 1 PROCESSES_ANALYSIS: 1 SERVICE_ANALYSIS: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 400 DUMP_TYPE: 2 BUGCHECK_P1: 0 BUGCHECK_P2: 0 BUGCHECK_P3: 0 BUGCHECK_P4: 0 CPU_COUNT: 8 CPU_MHZ: a86 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 47 CPU_STEPPING: 1 CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x1D8 CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-BFA8PF0 ANALYSIS_SESSION_TIME: 03-10-2019 18:38:57.0314 ANALYSIS_VERSION: 10.0.18317.1001 amd64fre LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80329a420c0 STACK_TEXT: fffff98b02ef68a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0xfffff80329a420c0


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID: CORRUPT_MODULELIST_0x1D8

DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_0x1D8

PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_0x1D8

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0x1D8

TARGET_TIME: 2019-03-10T23:25:58.000Z

OSBUILD: 17134

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

ANALYSIS_SESSION_ELAPSED_TIME: 3f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:corrupt_modulelist_0x1d8

FAILURE_ID_HASH: {6377c082-2b0a-c9e5-8980-2b4703307f45}

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



More...