BSOD Help needed, any input would be appreciated

necronikka

Reputable
Mar 14, 2014
16
0
4,510
I have been dealing with a kernel 41 issue for many months. I formatted my drive finally (been avoiding it cause eh)

But i've never gotten a dump file before, just a restart. So here goes nothing... I hope someone has insight as to what the root cause to this BSOD is.

-----------------------


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 16299 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff803`d521a000 PsLoadedModuleList = 0xfffff803`d5581110
Debug session time: Fri Mar 9 13:58:40.040 2018 (UTC - 5:00)
System Uptime: 2 days 18:19:37.750
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00327018). Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80300000000, 10, fffff80300000000, 2}

Probably caused by : memory_corruption ( nt!MiSystemFault+142feb )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff80300000000, memory referenced.
Arg2: 0000000000000010, value 0 = read operation, 1 = write operation.
Arg3: fffff80300000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7A59

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.90

BIOS_DATE: 01/30/2018

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z270 SLI PLUS (MS-7A59)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: fffff80300000000

BUGCHECK_P2: 10

BUGCHECK_P3: fffff80300000000

BUGCHECK_P4: 2

READ_ADDRESS: fffff80300000000

FAULTING_IP:
+0
fffff803`00000000 ?? ???

MM_INTERNAL_CODE: 2

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 70'00000000 (cache) 70'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: MSIAfterburner.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-LIEMFR6

ANALYSIS_SESSION_TIME: 03-10-2018 03:50:01.0731

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

TRAP_FRAME: ffffaa0c642ce6e0 -- (.trap 0xffffaa0c642ce6e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000011
rdx=ffffd982701f9880 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80300000000 rsp=ffffaa0c642ce870 rbp=ffffd982701f9860
r8=ffffaa0c642ce878 r9=7fffd9823a28f2e8 r10=7ffffffffffffffc
r11=ffffaa0c642ce8e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff803`00000000 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff803d53c55db to fffff803d538f430

FAILED_INSTRUCTION_ADDRESS:
+0
fffff803`00000000 ?? ???

STACK_TEXT:
ffffaa0c`642ce468 fffff803`d53c55db : 00000000`00000050 fffff803`00000000 00000000`00000010 ffffaa0c`642ce6e0 : nt!KeBugCheckEx
ffffaa0c`642ce470 fffff803`d5283fad : 00000000`00000010 fffff803`00000000 ffffaa0c`642ce6e0 ffffaa0c`642ce610 : nt!MiSystemFault+0x142feb
ffffaa0c`642ce510 fffff803`d539e54e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x23d
ffffaa0c`642ce6e0 fffff803`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x40e
ffffaa0c`642ce870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff803`00000000


THREAD_SHA1_HASH_MOD_FUNC: 35852f70c1fb96d682b5bd0e931cc10c7b9fe1fe

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8ad769b8d9deb49e62404f38e2d95fc17d23cc75

THREAD_SHA1_HASH_MOD: d084f7dfa548ce4e51810e4fd5914176ebc66791

FOLLOWUP_IP:
nt!MiSystemFault+142feb
fffff803`d53c55db cc int 3

FAULT_INSTR_CODE: 8a8d4dcc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiSystemFault+142feb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5a8e0c50

STACK_COMMAND: .thread ; .cxr ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: 142feb

FAILURE_BUCKET_ID: AV_INVALID_BAD_IP_nt!MiSystemFault

BUCKET_ID: AV_INVALID_BAD_IP_nt!MiSystemFault

PRIMARY_PROBLEM_CLASS: AV_INVALID_BAD_IP_nt!MiSystemFault

TARGET_TIME: 2018-03-09T18:58:40.000Z

OSBUILD: 16299

OSSERVICEPACK: 0

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: 2018-02-21 19:18:24

BUILDDATESTAMP_STR: 170928-1534

BUILDLAB_STR: rs3_release

BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME: a40

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_invalid_bad_ip_nt!misystemfault

FAILURE_ID_HASH: {48ad9531-e3f8-1044-fc5f-d917677674c7}

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

 
Solution
event 41 is the result of a report windows runs at startup after an unexpected shutdown. its not the cause, its just a reaction. so Pc has been restarting without BSOD?

MSI Afterburner is what crashed, which is funny as I normally blame it for crashing other things.Are you using it to overclock card as that might cause BSOD.

PAGE_FAULT_IN_NONPAGED_AREA is normally a driver error. Nonpaged area is ram, but generally the problem is a driver.

I would go to the MSI web site for motherboard and in the utilities page, download and run MSI Live update 6. It will scan motherboard for driver updates. I would link to it from here but web site giving errors currently.
event 41 is the result of a report windows runs at startup after an unexpected shutdown. its not the cause, its just a reaction. so Pc has been restarting without BSOD?

MSI Afterburner is what crashed, which is funny as I normally blame it for crashing other things.Are you using it to overclock card as that might cause BSOD.

PAGE_FAULT_IN_NONPAGED_AREA is normally a driver error. Nonpaged area is ram, but generally the problem is a driver.

I would go to the MSI web site for motherboard and in the utilities page, download and run MSI Live update 6. It will scan motherboard for driver updates. I would link to it from here but web site giving errors currently.
 
Solution