BSOD's on a 3 month-old system, already re-installed Windows once.

[bodomi12345]

I've had this computer for a little over 3 months now, and about 2 or 3 weeks ago I started getting a ton of bluescreens, at the start I was able to get into Windows after the computer restarted, but giving me very little time before another bluescreen happened, and eventually I was stuck in a BSOD loop where my computer would bluescreen before the Windows 10 log-in screen loaded with the error "CRITICAL_PROCESS_DIED".

Nothing in the Windows 10 recovery/repair screen worked, every CMD command came back with "Windows Resource Protection could not perform the requested operation", or simply telling me that whatever command I wrote wasn't recognized --The only command that worked was the command to bring up Windows Memory Diagnostic(which came back with 0 errors by the way).

I couldn't even re-install Windows, it simply came back with "We could not reset this PC." or something very similar.

That was 2 weeks ago, and now the bluescreens are happening again after a re-install and wipe of my drives, and games(specifically only World of Warcraft) is crashing after being open for 30 minutes to 1 hour.

I contacted Blizzard Support about that, mentioned the BSOD's and they said "I'm sorry to hear about your crashes, and it's pretty clear that there's something going on with your hard disk or memory, which is only reinforced by the crash dump you provided, as it states a memory location and claims it can't be read."

I would be eternally greatful if anyone is able to help me with this issue.

BSOD Dump File Nr 1:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8076726e114, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000010000000018, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1401

BIOS_DATE: 05/21/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG STRIX X299-E GAMING

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8076726e114

BUGCHECK_P3: 0

BUGCHECK_P4: 10000000018

READ_ADDRESS: fffff803da8f9388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000010000000018

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

FAULTING_IP:
Ntfs!NtfsCreateScb+c54
fffff807`6726e114 8b4018 mov eax,dword ptr [rax+18h]

EXCEPTION_PARAMETER2: 0000010000000018

BUGCHECK_STR: 0x1E_c0000005_R

CPU_COUNT: 14

CPU_MHZ: cf0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 2000043'00000000 (cache) 2000043'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 1

ANALYSIS_SESSION_HOST: DESKTOP-2HLEON1

ANALYSIS_SESSION_TIME: 07-29-2018 02:39:55.0779

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

EXCEPTION_RECORD: ffff910bcec57684 -- (.exr 0xffff910bcec57684)
ExceptionAddress: 0000000000000000
ExceptionCode: 00000000
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: ffff910bcec574c8 -- (.trap 0xffff910bcec574c8)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd609fd140010 rbx=0000000000000000 rcx=ffffd609fd140160
rdx=0000000000000080 rsi=0000000000000000 rdi=0000000000000000
rip=ffff910bcec57a20 rsp=ffffd60a14773600 rbp=0000000000000000
r8=ffffa808ca8d9018 r9=ffffd609fd140048 r10=ffff910bcec578c0
r11=00000000c0000005 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 vip vif nv up di pl zr na pe nc
ffff910b`cec57a20 18908dca08a8 sbb byte ptr [rax-57F73573h],dl ds:ffffd609`a51cca9d=??
Resetting default scope

BAD_STACK_POINTER: ffffd60a14773600

LAST_CONTROL_TRANSFER: from fffff803da4f73dd to fffff803da636560

STACK_TEXT:
ffff910b`cec56d38 fffff803`da4f73dd : 00000000`0000001e ffffffff`c0000005 fffff807`6726e114 00000000`00000000 : nt!KeBugCheckEx
ffff910b`cec56d40 fffff803`da647242 : ffff910b`cec57684 00000000`00000000 ffff910b`cec574c8 00000000`00000000 : nt!KiDispatchException+0x58d
ffff910b`cec573f0 fffff803`da643dbf : 00000000`00000000 00000000`00000080 ffffa808`ca8d9018 ffff910b`cec578c0 : nt!KiExceptionDispatch+0xc2
ffff910b`cec575d0 fffff807`6726e114 : ffff910b`cec76968 ffffb980`00000000 ffffa808`00000000 ffff910b`cec57e70 : nt!KiPageFault+0x3ff
ffff910b`cec57760 fffff807`6726be42 : ffff910b`cec76968 ffffd609`fd140010 ffff910b`cec57e70 ffff910b`cec57e70 : Ntfs!NtfsCreateScb+0xc54
ffff910b`cec57840 fffff807`67264824 : 00000000`00000080 00000000`00000000 00000000`00010201 ffffa808`ca0f0500 : Ntfs!NtfsBreakBatchOplock+0xa2
ffff910b`cec578b0 fffff807`672644de : 00000000`00000080 00000000`00000000 ffffa808`ca8d9018 ffffd609`00000024 : Ntfs!NtfsOpenExistingAttr+0x84
ffff910b`cec57970 fffff807`672628e1 : ffff910b`cec76910 ffffa808`ca0f0500 ffffd609`fd140448 ffffa808`00000024 : Ntfs!NtfsOpenAttributeInExistingFile+0xa7e
ffff910b`cec57b50 fffff807`67274175 : ffffa808`ca8d9018 ffffa808`ca0f0500 ffffd609`fd140448 ffffa808`00000010 : Ntfs!NtfsOpenExistingPrefixFcb+0x1e1
ffff910b`cec57c30 fffff807`672708ee : ffffa808`ca8d9018 ffffa808`ca0f0500 ffffa808`bd41d9e8 ffff910b`cec57e70 : Ntfs!NtfsFindStartingNode+0xd85
ffff910b`cec57cf0 fffff807`6726e26d : ffffa808`ca8d9018 ffffa808`ca0f0500 ffff910b`cec76910 ffffa808`c8481001 : Ntfs!NtfsCommonCreate+0xe7e
ffff910b`cec57f50 fffff803`da639a77 : ffff910b`cec768c0 00000000`00d7e218 00000000`00ef7000 00000000`010fd098 : Ntfs!NtfsCommonCreateCallout+0x1d
ffff910b`cec57f80 fffff803`da639a3d : 00000000`00006000 ffffa808`baf2f700 00000000`00000004 fffff803`da4f653a : nt!KxSwitchKernelStackCallout+0x27
ffff910b`cec76690 fffff803`da4f653a : ffffd609`00000012 00000000`00000012 00000000`ffffffff 00000000`00000000 : nt!KiSwitchKernelStackContinue
ffff910b`cec766b0 fffff803`da4f637e : fffff807`6726e250 00000000`00006000 00000000`00000000 00000000`00000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x12a
ffff910b`cec76730 fffff803`da4f6235 : 00000000`00000008 ffff910b`cec768c0 00000000`00000282 fffff803`da565aad : nt!KiExpandKernelStackAndCalloutSwitchStack+0x9e
ffff910b`cec767a0 fffff803`da4f61ed : fffff807`6726e250 ffff910b`cec768c0 ffffa808`ca8d9018 ffffa808`ca0f0500 : nt!KeExpandKernelStackAndCalloutInternal+0x35
ffff910b`cec76800 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d


THREAD_SHA1_HASH_MOD_FUNC: 7374fe22786a80ca39147e8f93695dc9df472377

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 33ffad6f3d79141046a472bafb6dab4eebf0406a

THREAD_SHA1_HASH_MOD: d2b5373902fc778c46a845155a979cda97f38dd6

FOLLOWUP_IP:
Ntfs!NtfsCreateScb+c54
fffff807`6726e114 8b4018 mov eax,dword ptr [rax+18h]

FAULT_INSTR_CODE: a818408b

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: Ntfs!NtfsCreateScb+c54

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 16eecac5

IMAGE_VERSION: 10.0.17134.191

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: c54

FAILURE_BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_Ntfs!NtfsCreateScb

BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_Ntfs!NtfsCreateScb

PRIMARY_PROBLEM_CLASS: 0x1E_c0000005_R_STACKPTR_ERROR_Ntfs!NtfsCreateScb

TARGET_TIME: 2018-07-28T16:55:45.000Z

OSBUILD: 17134

OSSERVICEPACK: 191

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-07-14 05:53:27

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 1291

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1e_c0000005_r_stackptr_error_ntfs!ntfscreatescb

FAILURE_ID_HASH: {f810018f-ab1d-b4bb-7b47-a326f660ac85}

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



BSOD Dump File Nr. 2:

*******************************************************************************
* *
* 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: fffff80073b6e6d2, Address of the instruction which caused the bugcheck
Arg3: ffffc181e521e040, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1401

BIOS_DATE: 05/21/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: ROG STRIX X299-E GAMING

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80073b6e6d2

BUGCHECK_P3: ffffc181e521e040

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!ObpCaptureHandleInformation+82
fffff800`73b6e6d2 8a4028 mov al,byte ptr [rax+28h]

CONTEXT: ffffc181e521e040 -- (.cxr 0xffffc181e521e040)
rax=0000000000000000 rbx=00000000000010dc rcx=ffffd9010d0dc438
rdx=ffff9c047d446720 rsi=ffff870731aa1370 rdi=0000000000000000
rip=fffff80073b6e6d2 rsp=ffffc181e521ea38 rbp=ffff87073154ba80
r8=ffff870731aa1370 r9=00000000000010dc r10=ffffc181e521ea80
r11=0000000000001cc4 r12=ffffd9010d000050 r13=ffffc181e521eb30
r14=fffff80073b6e650 r15=000000000017fffc
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!ObpCaptureHandleInformation+0x82:
fffff800`73b6e6d2 8a4028 mov al,byte ptr [rax+28h] ds:002b:00000000`00000028=??
Resetting default scope

CPU_COUNT: 14

CPU_MHZ: cf0

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 2000043'00000000 (cache) 2000043'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: Steam.exe

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-2HLEON1

ANALYSIS_SESSION_TIME: 07-29-2018 02:27:37.0268

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

LAST_CONTROL_TRANSFER: from fffff80073bd29d9 to fffff80073b6e6d2

STACK_TEXT:
ffffc181`e521ea38 fffff800`73bd29d9 : 00000000`000010dc 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpCaptureHandleInformation+0x82
ffffc181`e521ea40 fffff800`73bd02fd : fffff800`73b6e650 ffff8707`3154ba98 ffffc181`0017fffc 00000000`0017fffc : nt!ExpSnapShotHandleTables+0x131
ffffc181`e521ead0 fffff800`73a96c98 : 00000000`00000000 00000000`00020000 ffffaf7b`000dc400 ffffd901`0d000050 : nt!ExpGetHandleInformation+0x71
ffffc181`e521eb20 fffff800`73911c2b : 00000000`00080a14 ffffc181`e521f440 00000000`00000002 00000000`0000f000 : nt!ExpQuerySystemInformation+0x184f58
ffffc181`e521f380 fffff800`735aec43 : ffff9c04`73859080 00000000`00000001 00000000`00018002 00000000`00180010 : nt!NtQuerySystemInformation+0x2b
ffffc181`e521f3c0 00007ffb`3a0aa574 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0adddf98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`3a0aa574


THREAD_SHA1_HASH_MOD_FUNC: 20654208cc7e34b6bf534b6083db1b7ca9d50f43

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0c1789527c7480631b8b72be9491a2497fbfe9bb

THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_IP:
nt!ObpCaptureHandleInformation+82
fffff800`73b6e6d2 8a4028 mov al,byte ptr [rax+28h]

FAULT_INSTR_CODE: 8828408a

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ObpCaptureHandleInformation+82

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5b4973b7

IMAGE_VERSION: 10.0.17134.191

STACK_COMMAND: .cxr 0xffffc181e521e040 ; kb

BUCKET_ID_FUNC_OFFSET: 82

FAILURE_BUCKET_ID: 0x3B_nt!ObpCaptureHandleInformation

BUCKET_ID: 0x3B_nt!ObpCaptureHandleInformation

PRIMARY_PROBLEM_CLASS: 0x3B_nt!ObpCaptureHandleInformation

TARGET_TIME: 2018-07-28T18:30:54.000Z

OSBUILD: 17134

OSSERVICEPACK: 191

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-07-14 05:53:27

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 5455

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x3b_nt!obpcapturehandleinformation

FAILURE_ID_HASH: {a8099bb9-8a37-c3fc-a57a-50539451905f}

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



Here are the things I've tried, but probably non if it matters as Blizzard Support(I did tell them about the BSOD's) seem to be very certain it's either a drive or RAM issue.

Unlike the last time I started getting BSOD's my computer isn't unusable, and I'm not constantly getting BSOD's, it has 'only' happened twice so far.

I have right-clicked my main drive and done the "Error Checking" scan, I've done a "chkdsk" and ran a "sfc /scannow" scan, all of which came back with no errors and the need to repair no files.

I've checked my main drive(Samsung 960 PRO) read/write speed with Samsung Magician, and the results are a little under what is advertised, "Drive condition" shows up as "GOOD" and it has the latest firmware.

Windows Update has no updates for me to install.

I've ran numerous virus scans, all of which come back clean.

Windows Memeory Diagnostic came back with 0 errors(I ran the Standard scan, not Basic or Extended).

I have updated my BIOS(I did that the last time this happened when my computer became unusable, no new BIOS update has been released since).

I have disabled Intel Turbo Boost Max Technology 3.0 and I haven't used MSI Afterburner since the last BSOD I got in case any overclocking was a contributor to the bluescreens.

I have extensively checked my drives for folders, files, programs, etc. that I do not need and have deleted anything I can. The only things I found that could be deleted were temp files, log files(I didn't delete the BSOD minidumps) and some random folders in AppData that were left over from some uninstalled games.

I have checked some BIOS settings to see if there was anything disabled/enabled that should be enabled/disabled.

I do not use Java or Adobe, in case that is of interest.

I have checked all my drivers, everything is up-to-date, except that I'm unsure if every firmware on my motherboard(WiFi, Bluetooth, etc) is updated because as described below, the driver install process confuses me, and I also don't know how to check current driver versions for those modules of the motherboard.

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

Another thing that may be useful information is that my built-in WiFi adapter in my ASUS x299 E-Gaming motherboard has ever since I got the motherboard been randomly disconnecting itself from the internet, or turning itself off.
I downloaded the latest driver and simply ran the installer exe inside the folder called "W10"(under W7), the installer showed up for 1-2 seconds in my startbar, went away, my WiFi was disconnected and turned off, then it turned back on after 3-4 seconds and I had to manually connect back to the internet.
I'm unsure if it actually updated or not, I have to contact ASUS support to ask if I did something wrong, or if they designed the driver update process to be like that.

 

[Colif]

Can you follow option one on the following link - here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

always handy the WiFi doesn't show who actually makes the chip. it could be realtek or Intel - https://www.asus.com/au/Motherboards/ROG-STRIX-X299-E-GAMING/specifications/

what are specs of PC? Is WOW on the SSD?

 

[johnbl]

you should also provide access to the actual memory dump files. the automated debugging does not provide the proper info to determine the actual cause of the problem.

both case indicate a bad memory address used by a driver.
often in cases with a bad stack pointer you will find overheating, overclocking, or power fluctuations to the cpu as a root cause.

here are some things you might do:

run malwarebytes scan, (removes malware that infects storage drivers)
run dism.exe /online /cleanup-image /restorehealth (remove hacked drivers)

remove any cpu and gpu overclock drivers (gpu overclock can cause a brown out to the cpu in certain cases)

sometimes you need to underclock a factory overclocked GPU if your system overheats while playing a game. (crank up the GPU fan speeds if you can)

provide info on the PSU, make sure the GPU is getting proper power. check gpu power cables and make sure they are not on a shared power connection (splitter)

monitor temps of the system, crank up the fan.


since one of the failures was in the file system you should update the BIOS if it is out of date, then update the cpu chipset drivers and the motherboard sata 3 drivers from the motherboard vendors website.

if you have a ssd you should run crystal disk info and check the drives firmware version and see if you need a update to the firmware. for hdd you can check the drive health (not likely problem in this case)

consider changing the sata port and controller that the drive drive data cable is connected to.
often windows will update the slower sata driver directly supported by the cpu but you have to update the sata 3 driver from your motherboard vendor. This means there tends to be less bugs in the slower cpu supported driver.

if you are running any special drivers for your drive you should update them or remove them.
(some people use defrag driver, and 3 party tools)

most of these problems can be identified if you provide the actual memory dump file.

 

[smorizio]

start with making sure the ram is installed. make a bootable memtest usb stick run it overnight see if the ram has any isssues. if the ram passes download hardware info run it see if your power supply not holding within atx spec. also if you have an intel cpu run the intel cpu tests make sure the cpu cache is fine. if it not the cpu it could be bad vrm under load.