Windows 10: bsod

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


Loading Dump File [C:\Windows\Minidump\022719-12093-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 17134 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`b7c17000 PsLoadedModuleList = 0xfffff802`b7fc5150
Debug session time: Wed Feb 27 11:58:55.084 2019 (UTC + 2:00)
System Uptime: 0 days 3:20:40.771
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffffefe4157d308, ffffffffc0000185, 8eb6abe0, fffffc82afa61000}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+738 )

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffffefe4157d308, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 000000008eb6abe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffffc82afa61000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: AB350-Gaming

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F23

BIOS_DATE: 08/08/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: AB350-Gaming-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: fffffefe4157d308

BUGCHECK_P2: ffffffffc0000185

BUGCHECK_P3: 8eb6abe0

BUGCHECK_P4: fffffc82afa61000

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c0000185_DUMP_STORAHCIDUMP_STORPORT

CPU_COUNT: 4

CPU_MHZ: da5

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-9QG17CU

ANALYSIS_SESSION_TIME: 02-27-2019 12:18:34.0580

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER: from fffff802b7c8e1e8 to fffff802b7dc10c0

STACK_TEXT:
fffffc****
fffffc82`ade9e6f0 fffff802`b7c7****efd97d8 00000000`00000000 : nt!MiInPageSingleKernelStack+0x2****2972040 fffff802`b7d472b0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
fffffc82`ade9ec60 00000000`00000000 : fffffc82`ade9f000 fffffc82`ade99000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 3033062ed9b1b68c332576eeeecce57621371b73

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 516dded5607****dad8

FOLLOWUP_IP:
nt!MiWaitForInPageComplete+738
fffff802`b7c8e1e8 cc int 3

FAULT_INSTR_CODE: 448b48cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiWaitForInPageComplete+738

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5c5a45ab

IMAGE_VERSION: 10.0.17134.590

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 738

FAILURE_BUCKET_ID: 0x7a_c0000185_DUMP_STORAHCIDUMP_STORPORT_nt!MiWaitForInPageComplete

BUCKET_ID: 0x7a_c0000185_DUMP_STORAHCIDUMP_STORPORT_nt!MiWaitForInPageComplete

PRIMARY_PROBLEM_CLASS: 0x7a_c0000185_DUMP_STORAHCIDUMP_STORPORT_nt!MiWaitForInPageComplete

TARGET_TIME: 2019-02-27T09:58:55.000Z

OSBUILD: 17134

OSSERVICEPACK: 590

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-02-06 04:25:47

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 104b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x7a_c0000185_dump_storahcidump_storport_nt!miwaitforinpagecomplete

FAILURE_ID_HASH: {97923d45-c202-97ea-1c85-bbe737949657}

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

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

7 different BSoD

Hey guys,

I have a serious problem. I make it as short as possible:

• system runs 100 % fine with the 10.12
• updatet to Catalyst 11.1 -> BSoD
• updatet to 11.1 Hotfix -> BSoD
• rollback to 10.12 -> BSoD
• removed ALL AMD files manually, installed 10.12 -> BSoD

• Temps are fine
• no sfc /scannow errors
• no chkdsk errors
• Prime, Furmark all fine
• regardless what driver I install -> BSoD
• I did no hw changes, no OC

Here are my BSoDs I receive:

• 0x0000010e
• 0x1000007e
• 0x0000007e
• 0x0000004e
• 0x0000003b
• dxgmms1.sys
• PFN_LIST_CORRUPT

They all refer to the GPU of course ...

From now on I receive a BSoD every time I try to play a game (especially BC2 and SC II) even if I completely remove the old driver and make a clean install.
Apparently the 11.1 damaged my system irreparable.

Any advice or info would be very much appreciated *Smile

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.