What does this debug mean, and is there anyway to fix it? (Black Screen Crashing)

Foxyyl

Prominent
Jul 13, 2017
5
0
510
Since built my new PC I've come up with countless crashing issues...
I've tried:

  • Drivers
    Possible Overheating
    Windows Validation
    Many Other fixes
But the problem still stands
I began to debug to see what the issue is, please tell me what does this mean and is it a possible fix or do I have or need new hardware?
===========================================

Microsoft (R) Windows Debugger Version 10.0.16299.15 X86
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:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`83602000 PsLoadedModuleList = 0xfffff801`8394e5c0
Debug session time: Fri Oct 20 17:53:24.010 2017 (UTC + 1:00)
System Uptime: 2 days 20:56:17.001
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000ea`1c2b9018). Type ".hh dbgerr001" for details
Loading unloaded module list
......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80183b2f2ae, ffffdb015cb10c60, 0}

Probably caused by : memory_corruption ( nt!MiFindEmptyAddressRangeDownTree+be )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80183b2f2ae, Address of the instruction which caused the bugcheck
Arg3: ffffdb015cb10c60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z170X-Ultra Gaming

SYSTEM_SKU: To be filled by O.E.M.

SYSTEM_VERSION: To be filled by O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F2

BIOS_DATE: 05/29/2016

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z170X-Ultra Gaming-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 1

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80183b2f2ae

BUGCHECK_P3: ffffdb015cb10c60

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
nt!MiFindEmptyAddressRangeDownTree+be
fffff801`83b2f2ae 48395008 cmp qword ptr [rax+8],rdx

CONTEXT: ffffdb015cb10c60 -- (.cxr 0xffffdb015cb10c60)
rax=7fffca0f4f357a80 rbx=00000007ff790a20 rcx=0000000000000000
rdx=ffffca0f516f7850 rsi=0000024d44c70000 rdi=0000000000000010
rip=fffff80183b2f2ae rsp=ffffdb015cb11650 rbp=0000000000010000
r8=00000007ff7711d0 r9=ffffca0f4ba263e0 r10=ffffca0f4ba263e0
r11=0000000000000000 r12=00000007ff790a30 r13=ffffdb015cb11818
r14=00007ff790a30000 r15=ffffffffffff0000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MiFindEmptyAddressRangeDownTree+0xbe:
fffff801`83b2f2ae 48395008 cmp qword ptr [rax+8],rdx ds:002b:7fffca0f`4f357a88=????????????????
Resetting default scope

CPU_COUNT: 8

CPU_MHZ: fa8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: DOOMx64vk.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: LUKEPC

ANALYSIS_SESSION_TIME: 10-26-2017 18:03:26.0191

ANALYSIS_VERSION: 10.0.16299.15 x86fre

LAST_CONTROL_TRANSFER: from fffff80183b2f1b4 to fffff80183b2f2ae

STACK_TEXT:
ffffdb01`5cb11650 fffff801`83b2f1b4 : 00007ff7`90a30000 ffffca0f`566fc8e8 00000000`00010000 00000000`000000c7 : nt!MiFindEmptyAddressRangeDownTree+0xbe
ffffdb01`5cb116b0 fffff801`83a8c5c6 : 00000000`00100000 00000000`00000004 00000000`00010000 ffffca0f`566fc628 : nt!MiFindEmptyAddressRangeDown+0x84
ffffdb01`5cb11710 fffff801`83ab8a6a : 00000000`00000000 00000000`00000000 00000000`00010000 00000000`00000000 : nt!MiSelectUserAddress+0x136
ffffdb01`5cb11790 fffff801`83ab83d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiAllocateVirtualMemory+0x68a
ffffdb01`5cb119b0 fffff801`83779413 : 00000000`746c6644 ffffdb01`5cb11a00 00000000`00000000 ffffa10f`a253d580 : nt!NtAllocateVirtualMemory+0x40
ffffdb01`5cb11a10 00007fff`492056a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000ea`209ff768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`492056a4


THREAD_SHA1_HASH_MOD_FUNC: 1086bf8166a5440ed75e68d632aa3ee9ea7b4cbe

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: df3dadd4c83ebd413082c7db5aca0edb681f98d8

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!MiFindEmptyAddressRangeDownTree+be
fffff801`83b2f2ae 48395008 cmp qword ptr [rax+8],rdx

FAULT_INSTR_CODE: 8503948

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiFindEmptyAddressRangeDownTree+be

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 59cdf43a

STACK_COMMAND: .cxr 0xffffdb015cb10c60 ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: be

FAILURE_BUCKET_ID: 0x3B_nt!MiFindEmptyAddressRangeDownTree

BUCKET_ID: 0x3B_nt!MiFindEmptyAddressRangeDownTree

PRIMARY_PROBLEM_CLASS: 0x3B_nt!MiFindEmptyAddressRangeDownTree

TARGET_TIME: 2017-10-20T16:53:24.000Z

OSBUILD: 15063

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: 2017-09-29 08:20:26

BUILDDATESTAMP_STR: 170317-1834

BUILDLAB_STR: rs2_release

BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME: 738

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_nt!mifindemptyaddressrangedowntree

FAILURE_ID_HASH: {7345e4d5-9514-bb84-d6e6-484081ff7e3a}
 
Solution
This means the crash is caused due to a memory related hardware failure (mostly faulty rams or GPU memory).
Just check if the rams are inserted properly and clean the RAM slots and re-insert them. Also, do the same for your GPU. Let BIOS load the optimum values (F10 in most mobos).
Carry out MEM test or check with other ram sticks (if extra are around or a friends Ram), to be sure your RAM s are not faulty.

serioussamik17

Distinguished
This means the crash is caused due to a memory related hardware failure (mostly faulty rams or GPU memory).
Just check if the rams are inserted properly and clean the RAM slots and re-insert them. Also, do the same for your GPU. Let BIOS load the optimum values (F10 in most mobos).
Carry out MEM test or check with other ram sticks (if extra are around or a friends Ram), to be sure your RAM s are not faulty.
 
Solution

TRENDING THREADS