[SOLVED] BSOD on new build

[Alzaraz]

Hi, not sure if this is the right place to post, if not please point me in the right direction.

I built a PC early last week and everything went great. A few days ago I started getting some BSOD crashes. Also around the time I purchased a WMR Unit (Samsung Odyssey +).

Below are the details from the minidump and was hoping someone could provide some insight as I don't know how to read these things.

Since the last crash last night (haven't used the unit since then) I have done the following:

1. Removed an overclock I did on my 9600k using the GIgabyte easytune software. I also removed this software as well as all the other Gigabyte bloatware as I understand it can cause crashes.

2. I've run 4 cycles of memtest without error

3. Checked all drivers to ensure up to date, the raid driver wasn't so that was updated.

Any help would be appreciated.



Loading Dump File [C:\Users\Kyle's PC\Desktop\MiniDumps\022019-8265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff8062b6a9000 PsLoadedModuleList = 0xfffff8062bac4ad0
Debug session time: Wed Feb 20 22:10:33.792 2019 (UTC - 5:00)
System Uptime: 0 days 1:10:33.481
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
...........
***

• *
• Bugcheck Analysis *
• *

***

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff806000056fb, 2, 8, fffff8062b9056fb}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!EtwpLogContextSwapEvent+e357b )

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

1: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff806000056fb, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8062b9056fb, address which referenced memory

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z390 AORUS ELITE

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F3

BIOS_DATE: 08/30/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z390 AORUS ELITE-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: fffff806000056fb

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: fffff8062b9056fb

READ_ADDRESS: fffff8062bbeb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff806000056fb

CURRENT_IRQL: 2

FAULTING_IP:
nt!EtwpLogContextSwapEvent+e357b
fffff8062b9056fb 884a0a mov byte ptr [rdx+0Ah],cl CPU_COUNT: 6 CPU_MHZ: e70 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 9e CPU_STEPPING: c CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: 9C'00000000 (cache) 9C'00000000 (init) BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: System ANALYSIS_SESSION_HOST: DESKTOP-EKVHL8C ANALYSIS_SESSION_TIME: 02-21-2019 14:11:03.0703 ANALYSIS_VERSION: 10.0.17763.1 amd64fre TRAP_FRAME: fffff5837662f8d0 -- (.trap 0xfffff5837662f8d0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffff9880cd440180 rbx=0000000000000000 rcx=0000000000000000 rdx=ffffc60559b879c8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8062b9056fb rsp=fffff5837662fa60 rbp=0000000000000028 r8=00000009db70da64 r9=fffff5837662fae0 r10=fffff8062b720520 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!EtwpLogContextSwapEvent+0xe357b: fffff8062b9056fb 884a0a mov byte ptr [rdx+0Ah],cl ds:ffffc60559b879d2=00 Resetting default scope LAST_CONTROL_TRANSFER: from fffff8062b86dc69 to fffff8062b85c440 STACK_TEXT: fffff5837662f788 fffff8062b86dc69 : 000000000000000a fffff806000056fb 0000000000000002 0000000000000008 : nt!KeBugCheckEx fffff5837662f790 fffff8062b86a08e : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiBugCheckDispatch+0x69 fffff5837662f8d0 fffff8062b9056fb : 0000000000000000 ffffc6054af8d9c0 0000000000000000 fffff5837662fae0 : nt!KiPageFault+0x44e fffff5837662fa60 fffff8062b822122 : 00000009db70da64 0000000000000000 ffffc605587ed080 0000000000000290 : nt!EtwpLogContextSwapEvent+0xe357b fffff5837662fae0 fffff8062b863790 : ffff9880cd440180 000024edbd9bbfff ffff9880cd450180 fffff80600000000 : nt!EtwTraceContextSwap+0xb2 fffff5837662fb20 fffff8062b85ff26 : ffffffff00000000 ffff9880cd440180 ffff9880cd450180 ffffc605587ed080 : nt!SwapContext+0x4d0 fffff5837662fb60 0000000000000000 : fffff58376630000 fffff58376629000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x126 THREAD_SHA1_HASH_MOD_FUNC: 0cf3fd66339164f08049eb8216a4523cfb0d5105 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f2e2a5b2bd3c6dd23c02a9c80ba556826411dfde THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6 FOLLOWUP_IP: nt!EtwpLogContextSwapEvent+e357b fffff8062b9056fb 884a0a mov byte ptr [rdx+0Ah],cl

FAULT_INSTR_CODE: 4d0a4a88

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!EtwpLogContextSwapEvent+e357b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17763.316

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: e357b

FAILURE_BUCKET_ID: AV_nt!EtwpLogContextSwapEvent

BUCKET_ID: AV_nt!EtwpLogContextSwapEvent

PRIMARY_PROBLEM_CLASS: AV_nt!EtwpLogContextSwapEvent

TARGET_TIME: 2019-02-21T03:10:33.000Z

OSBUILD: 17763

OSSERVICEPACK: 316

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: a17

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!etwplogcontextswapevent

FAILURE_ID_HASH: {a247e46e-2a71-233a-f5c4-3ec4529dfaa5}

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

 

[010010]

Most BSOD are driver related and i have no idea what most of the dump is saying but it definitely refers to drivers:

"an attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses."

I would say update all drivers BIOS chipset etc and try again.