[SOLVED] Continuous Blue Screen of Deaths

Aug 27, 2019
3
0
20
1
Hello,

I'm in desperate need of help with my gaming PC. I bought it back in December 2016, with excellent performance until a few weeks ago. Below are my specs.

PC Core Core i7 Skylake 6700 up to 4.0Ghz Quad Core with Windows 10, 16GB RAM (2x8GB) 2133Mhz, 4TB HDD, 2TB HDD, NVIDIA GTX1070 w/8GB DDR5 RAM Video Card .

I don't remember what I did before all of this started happening, but it seems like every time I try to do something, the PC crashes with a blue screen saying something about "MEMORY_MANAGEMENT." Before the crash, I would normally watch some videos and the tabs start to mess up saying "Page cannot be displayed" and the Mozilla Crash Reporter comes up and then the BSOD. This happens in Chrome and a few apps that I run. I thought my OS was just getting corrupted after a while because the dump file said something about the NTkernel messing up and people having to reinstall their OS for the issue to go away.

I ran Windows Memory Diagnostic with no issues to report. I REINSTALLED my Windows 10 and the problem came back while I was installing STEAM. I made sure I downloaded the video drivers straight from the NVIDIA website instead of Windows Updates. I noticed my PC has been running ok when I'm not around, I come home from work and my login screen is still there. BlueScreenView does not help much so I kept looking and found another program called WINDBG Preview and seems to generate a whole bunch of codes. I will post the results at the bottom to see if it helps with the troubleshooting. The last couple of BSOD codes were different. Most of them were MEMORY_MANAGEMENT then I get the PAGE_FAULT_IN_NONPAGED_AREA, then PFN_LIST_CORRUPT. I don't remember the other one much, but it was driver equal or less or something...

SFC /scannow reported no issues. DISM restorehealth command didn't help. Again, I reinstalled my Win10 and it's still getting the BSOD.

I'm really at a loss here and this is getting out of hand and very frustrating. It just crashed while I was transferring files from my old hard drive to the new (thinking that my HDD was going bad). PC cost me about $1,500 and I can't figure out if the RAM is going bad or my graphics card. If anyone can assist me with how to track down the issue, I would GREATLY appreciate it. I really don't want to buy a component just to find out it didn't work.

Thank you in advance


This is what I got from WINDBG Preview:

Microsoft (R) Windows Debugger Version 10.0.18914.1001 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*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff8036e200000 PsLoadedModuleList = 0xfffff8036e646490
Debug session time: Tue Aug 27 18:30:20.330 2019 (UTC - 4:00)
System Uptime: 0 days 0:16:58.982
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000000020f018). Type ".hh dbgerr001" for details
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803
6e3bfcc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbe019a075c40=000000000000003b
5: kd> !analyze -v
*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 5

Key : Analysis.Elapsed.Sec
Value: 6

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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7996

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.60

BIOS_DATE: 03/16/2016

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: B150M PRO-VD (MS-7996)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8036e24cd5f

BUGCHECK_P3: ffffbe019a076570

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!MiMakePageAvoidRead+ff
fffff803
6e24cd5f 0fb74a3c movzx ecx,word ptr [rdx+3Ch]

CONTEXT: ffffbe019a076570 -- (.cxr 0xffffbe019a076570)
rax=ffffdfffffffffff rbx=ffffbe019a077174 rcx=ffffbe019a0770b8
rdx=0000000000000000 rsi=0000000000001000 rdi=0000000000000000
rip=fffff8036e24cd5f rsp=ffffbe019a076f60 rbp=ffffda857add48d0
r8=0000000000000000 r9=0000000000000000 r10=0000000000000003
r11=ffffc58b7d931000 r12=ffffda858a073750 r13=0000000006717040
r14=ffffbe019a077190 r15=fffffcfe7f3f97f8
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nt!MiMakePageAvoidRead+0xff:
fffff8036e24cd5f 0fb74a3c movzx ecx,word ptr [rdx+3Ch] ds:002b:000000000000003c=????
Resetting default scope

BUGCHECK_STR: 0x3B_c0000005

CPU_COUNT: 8

CPU_MHZ: d50

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

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

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: ELMIGUEL-PC

ANALYSIS_SESSION_TIME: 08-27-2019 18:36:10.0646

ANALYSIS_VERSION: 10.0.18914.1001 amd64fre

LAST_CONTROL_TRANSFER: from fffff8036e24f0c1 to fffff8036e24cd5f

STACK_TEXT:
ffffbe019a076f60 fffff8036e24f0c1 : ffffda8579c7f020 ffffda857adbe8a0 0000000000000000 0000000000000000 : nt!MiMakePageAvoidRead+0xff
ffffbe019a077130 fffff8036e24e47b : ffffc58b7d931000 0000000006717040 ffffbe0100000000 0000000000001000 : nt!MmCopyToCachedPage+0x281
ffffbe019a077210 fffff8036e250255 : ffffda857adbe8a0 0000000006717040 ffffbe019a0773f0 0000000000000000 : nt!CcMapAndCopyInToCache+0x5fb
ffffbe019a077390 fffff80372cccf56 : ffffa3880b8da170 0000000000000000 ffffa3880b8da170 ffffa38800100000 : nt!CcCopyWriteEx+0x105
ffffbe019a077410 fffff80372115f78 : 0000000000000000 00000000000002c0 ffffda858b088ce0 0000000000000000 : Ntfs!NtfsCopyWriteA+0x456
ffffbe019a077720 fffff80372112fa3 : ffffbe019a077810 0000000000000000 0000000000000000 ffffda85899f86f0 : FLTMGR!FltpPerformFastIoCall+0x198
ffffbe019a077780 fffff8037214c5d5 : da858a68a530fda3 00000000001f0003 0000000000000000 ffffda858b088ce0 : FLTMGR!FltpPassThroughFastIo+0xd3
ffffbe019a0777e0 fffff8036e8433a8 : ffffda858b088ce0 000000001b97c470 000000001b97c470 0000000000000000 : FLTMGR!FltpFastIoWrite+0x165
ffffbe019a077890 fffff8036e3d1515 : 0000000000000000 0000000000002ee0 0000000000000000 00000000427ccd30 : nt!NtWriteFile+0x458
ffffbe019a077990 00007ffeab11c164 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000001b97c3f8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffeab11c164


THREAD_SHA1_HASH_MOD_FUNC: f5a7cec6a8869a43ed1c1977ac01e7e11688d3e9

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 137e2b8e17c3a6b0cd9032e4cbd37749d0366584

THREAD_SHA1_HASH_MOD: 9887b7097b2bdab280ef4beaa6f4c22cc0b3101f

FOLLOWUP_IP:
nt!MiMakePageAvoidRead+ff
fffff803
6e24cd5f 0fb74a3c movzx ecx,word ptr [rdx+3Ch]

FAULT_INSTR_CODE: 3c4ab70f

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!MiMakePageAvoidRead+ff

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 35707659

STACK_COMMAND: .cxr 0xffffbe019a076570 ; kb

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: ff

FAILURE_BUCKET_ID: 0x3B_c0000005_nt!MiMakePageAvoidRead

BUCKET_ID: 0x3B_c0000005_nt!MiMakePageAvoidRead

PRIMARY_PROBLEM_CLASS: 0x3B_c0000005_nt!MiMakePageAvoidRead

TARGET_TIME: 2019-08-27T22:30:20.000Z

OSBUILD: 18362

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: 1998-05-30 17:12:57

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 1aeb

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_c0000005_nt!mimakepageavoidread

FAILURE_ID_HASH: {c8a037ab-0b2a-1923-a859-9f37fb944d97}

Followup: MachineOwner
---------
 
Aug 27, 2019
3
0
20
1
Forget it. It's all set. I figured it out on my own. One of my RAM stick was bad. Tested one stick at a time with Memtestx86 and it detected over 10,000 errors on one RAM and no errors on the other. If this is any help to other users with the same problem.
 
Aug 27, 2019
3
0
20
1
Forget it. It's all set. I figured it out on my own. One of my RAM stick was bad. Tested one stick at a time with Memtestx86 and it detected over 10,000 errors on one RAM and no errors on the other. If this is any help to other users with the same problem.
 

ASK THE COMMUNITY

TRENDING THREADS