M
MXG.
Guest
Hi,
I built this computer back in the middle of September (2019) and have been getting random BSOD events ever since a few days after it was finished. However I can't pinpoint the problem. They seem to happen randomly and the errors have been mostly "page fault in non paged area" with a couple "memory_management" and "kernel exception not handled" sprinkled in there. The mini dumps either don't display any drivers responsible, or say "Could not read faulting driver name". All drivers are up to date. I resulted to using driver verifier but during both of the crashes during that period the BSOD was left overnight staying at 0% complete when attempting to record data, and both errors being the standard "page fault in non paged area" and of course no dump recorded. Earlier this month I took everything out, blew out the case and parts w/ air and reconnected everything but still no improvements. I've also done a disk check and memory test. Another BSOD happened today with it being the first time I got the "kernel exception not handled". Once again no driver was identified. I now have no idea what to do thus why I'm here. Below I'll post the latest minidump info and hardware specs.
Thanks in advance for any help.
Hardware:
AMD Ryzen 7 3700x
ASRock x570M Pro4
G.Skill Ripjaws 64GB DDR4-3200
Western Digital Blue 1 TB m.2 SSD
MSI Radeon RX570 8GB
Ubit Gigabit AC 1200Mbps Bluetooth 4.2 Wireless Network Card
Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101819-10062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`3ea00000 PsLoadedModuleList = 0xfffff804`3ee48210
Debug session time: Fri Oct 18 16:09:06.735 2019 (UTC - 7:00)
System Uptime: 0 days 3:58:40.414
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`3ebc1220 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc06`0ba6e5f0=000000000000001e
6: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8043ea453b0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffff93040736dd58, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-FSE29BQ
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 2
Key : Analysis.Memory.CommitPeak.Mb
Value: 69
Key : Analysis.System
Value: CreateObject
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8043ea453b0
BUGCHECK_P3: 0
BUGCHECK_P4: ffff93040736dd58
READ_ADDRESS: fffff8043ef733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8043ee2a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8043ee2a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffff93040736dd58
EXCEPTION_PARAMETER2: ffff93040736dd58
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffc06`0ba6e5e8 fffff804`3eca678e : 00000000`0000001e ffffffff`c0000005 fffff804`3ea453b0 00000000`00000000 : nt!KeBugCheckEx
fffffc06`0ba6e5f0 fffff804`3ebca052 : fffff804`3ef11000 fffff804`3ea00000 0005e56c`00ab6000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffffc06`0ba6e630 fffff804`3eac3375 : 00000000`00000000 00000000`00000000 fffffc06`0ba6eba0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
fffffc06`0ba6e660 fffff804`3eac790e : fffffc06`0ba6f598 fffffc06`0ba6f2e0 fffffc06`0ba6f598 00000000`00000001 : nt!RtlDispatchException+0x4a5
fffffc06`0ba6edb0 fffff804`3ebd321d : 00000000`00000003 00000000`00000001 00000000`00000000 fffffc06`0ba6f560 : nt!KiDispatchException+0x16e
fffffc06`0ba6f460 fffff804`3ebcf405 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
fffffc06`0ba6f640 fffff804`3ea453b0 : 00000000`00000000 fffff804`3eb02909 ffff9304`8c549ed8 00000000`00000000 : nt!KiPageFault+0x445
fffffc06`0ba6f7d0 fffff804`3eb02909 : ffff9304`8c549ed8 00000000`00000000 ffff9304`8c549ef0 fffff804`3ee4fa40 : nt!RtlRbInsertNodeEx+0x90
fffffc06`0ba6f7e0 fffff804`3eb027c8 : fffffc06`0ba6f893 ffff9304`8c0d6000 fffffc06`0ba6f909 ffff9304`8c549ed8 : nt!KiInsertTimer2WithCollectionLockHeld+0x109
fffffc06`0ba6f830 fffff804`3ea680fa : ffff9304`8c549ed8 00000000`00000000 ffff8001`390c0100 fffffc06`0ba6fb00 : nt!KiInsertTimer2+0x3c
fffffc06`0ba6f860 fffff804`3ea688c3 : fffffc06`0ba6f9a8 ffff9304`8c549ef0 fffffc06`0ba6f9a8 00000000`00000000 : nt!KiExpireTimer2+0x22a
fffffc06`0ba6f970 fffff804`3ea6a9b7 : 00000000`00000012 00000000`00989680 fffffc06`0ba6fb30 00000000`00000000 : nt!KiTimer2Expiration+0x163
fffffc06`0ba6fa30 fffff804`3ebc4d64 : ffffffff`00000000 ffff8001`390c0180 ffff8001`390d1440 ffff9304`8ab49300 : nt!KiRetireDpcList+0x6c7
fffffc06`0ba6fc60 00000000`00000000 : fffffc06`0ba70000 fffffc06`0ba6a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84
SYMBOL_NAME: nt!RtlRbInsertNodeEx+90
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.418
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 90
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!RtlRbInsertNodeEx
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {279be157-e7e6-edf7-b957-b27b72a11ccf}
Followup: MachineOwner
---------
Continue reading...
I built this computer back in the middle of September (2019) and have been getting random BSOD events ever since a few days after it was finished. However I can't pinpoint the problem. They seem to happen randomly and the errors have been mostly "page fault in non paged area" with a couple "memory_management" and "kernel exception not handled" sprinkled in there. The mini dumps either don't display any drivers responsible, or say "Could not read faulting driver name". All drivers are up to date. I resulted to using driver verifier but during both of the crashes during that period the BSOD was left overnight staying at 0% complete when attempting to record data, and both errors being the standard "page fault in non paged area" and of course no dump recorded. Earlier this month I took everything out, blew out the case and parts w/ air and reconnected everything but still no improvements. I've also done a disk check and memory test. Another BSOD happened today with it being the first time I got the "kernel exception not handled". Once again no driver was identified. I now have no idea what to do thus why I'm here. Below I'll post the latest minidump info and hardware specs.
Thanks in advance for any help.
Hardware:
AMD Ryzen 7 3700x
ASRock x570M Pro4
G.Skill Ripjaws 64GB DDR4-3200
Western Digital Blue 1 TB m.2 SSD
MSI Radeon RX570 8GB
Ubit Gigabit AC 1200Mbps Bluetooth 4.2 Wireless Network Card
Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\101819-10062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`3ea00000 PsLoadedModuleList = 0xfffff804`3ee48210
Debug session time: Fri Oct 18 16:09:06.735 2019 (UTC - 7:00)
System Uptime: 0 days 3:58:40.414
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`3ebc1220 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc06`0ba6e5f0=000000000000001e
6: kd> !analyze -v
*******************************************************************************
* *
* 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: fffff8043ea453b0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffff93040736dd58, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-FSE29BQ
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 2
Key : Analysis.Memory.CommitPeak.Mb
Value: 69
Key : Analysis.System
Value: CreateObject
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8043ea453b0
BUGCHECK_P3: 0
BUGCHECK_P4: ffff93040736dd58
READ_ADDRESS: fffff8043ef733b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8043ee2a3c8: Unable to get Flags value from nt!KdVersionBlock
fffff8043ee2a3c8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
ffff93040736dd58
EXCEPTION_PARAMETER2: ffff93040736dd58
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffc06`0ba6e5e8 fffff804`3eca678e : 00000000`0000001e ffffffff`c0000005 fffff804`3ea453b0 00000000`00000000 : nt!KeBugCheckEx
fffffc06`0ba6e5f0 fffff804`3ebca052 : fffff804`3ef11000 fffff804`3ea00000 0005e56c`00ab6000 00000000`0010001f : nt!KiFatalExceptionHandler+0x22
fffffc06`0ba6e630 fffff804`3eac3375 : 00000000`00000000 00000000`00000000 fffffc06`0ba6eba0 00007fff`ffff0000 : nt!RtlpExecuteHandlerForException+0x12
fffffc06`0ba6e660 fffff804`3eac790e : fffffc06`0ba6f598 fffffc06`0ba6f2e0 fffffc06`0ba6f598 00000000`00000001 : nt!RtlDispatchException+0x4a5
fffffc06`0ba6edb0 fffff804`3ebd321d : 00000000`00000003 00000000`00000001 00000000`00000000 fffffc06`0ba6f560 : nt!KiDispatchException+0x16e
fffffc06`0ba6f460 fffff804`3ebcf405 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x11d
fffffc06`0ba6f640 fffff804`3ea453b0 : 00000000`00000000 fffff804`3eb02909 ffff9304`8c549ed8 00000000`00000000 : nt!KiPageFault+0x445
fffffc06`0ba6f7d0 fffff804`3eb02909 : ffff9304`8c549ed8 00000000`00000000 ffff9304`8c549ef0 fffff804`3ee4fa40 : nt!RtlRbInsertNodeEx+0x90
fffffc06`0ba6f7e0 fffff804`3eb027c8 : fffffc06`0ba6f893 ffff9304`8c0d6000 fffffc06`0ba6f909 ffff9304`8c549ed8 : nt!KiInsertTimer2WithCollectionLockHeld+0x109
fffffc06`0ba6f830 fffff804`3ea680fa : ffff9304`8c549ed8 00000000`00000000 ffff8001`390c0100 fffffc06`0ba6fb00 : nt!KiInsertTimer2+0x3c
fffffc06`0ba6f860 fffff804`3ea688c3 : fffffc06`0ba6f9a8 ffff9304`8c549ef0 fffffc06`0ba6f9a8 00000000`00000000 : nt!KiExpireTimer2+0x22a
fffffc06`0ba6f970 fffff804`3ea6a9b7 : 00000000`00000012 00000000`00989680 fffffc06`0ba6fb30 00000000`00000000 : nt!KiTimer2Expiration+0x163
fffffc06`0ba6fa30 fffff804`3ebc4d64 : ffffffff`00000000 ffff8001`390c0180 ffff8001`390d1440 ffff9304`8ab49300 : nt!KiRetireDpcList+0x6c7
fffffc06`0ba6fc60 00000000`00000000 : fffffc06`0ba70000 fffffc06`0ba6a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84
SYMBOL_NAME: nt!RtlRbInsertNodeEx+90
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.418
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 90
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!RtlRbInsertNodeEx
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {279be157-e7e6-edf7-b957-b27b72a11ccf}
Followup: MachineOwner
---------
Continue reading...