DaleH

Prominent
Mar 24, 2023
469
46
720

DaleH

Prominent
Mar 24, 2023
469
46
720
What is the problem? I couldn't open the dump files. The fact that the RAM is new doesn't exclude it from failure; new things fail all the time. Explain the symptoms. Thx
 
Apr 10, 2024
13
0
10
I've tried 3 different ram sets, at different speeds. My pc works fine until it randomly blue screens, usually when I put it under too much load.
I have my cpu at 4.7 with an avx offset of 1 @ 1.25v
Fresh install of windows, how would I send dump files? Temps are good, great even, I have no clue what's happening
 
Last edited:
Apr 10, 2024
13
0
10
I've tried 3 different ram sets, at different speeds. My pc works fine until it randomly blue screens, usually when I put it under too much load.
I have my cpu at 4.7 with an avx offset of 1 @ 1.25v
Fresh install of windows, how would I send dump files? Temps are good, great even, I have no clue what's happening
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: ffffb5814725a2fc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff803736aa631, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2124

Key : Analysis.Elapsed.mSec
Value: 2153

Key : Analysis.IO.Other.Mb
Value: 5

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 24

Key : Analysis.Init.CPU.mSec
Value: 608

Key : Analysis.Init.Elapsed.mSec
Value: 6892

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Failure.Bucket
Value: AV_nt!RtlInitializeExtendedContext2

Key : Failure.Hash
Value: {f6cfaab0-5ba1-e08f-7f3d-2832ec4d2572}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: a

BUGCHECK_P1: ffffb5814725a2fc

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff803736aa631

FILE_IN_CAB: 050324-10609-01.dmp

WRITE_ADDRESS: fffff803740fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffb5814725a2fc

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: HorizonForbiddenWest.exe

TRAP_FRAME: ffffb58147259c20 -- (.trap 0xffffb58147259c20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000004d0 rbx=0000000000000000 rcx=ffffb58147259e20
rdx=000000000010001f rsi=0000000000000000 rdi=0000000000000000
rip=fffff803736aa631 rsp=ffffb58147259db0 rbp=ffffb58147259e20
r8=0000000000000001 r9=fffff780000003d8 r10=ffffb58147259e20
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!RtlInitializeExtendedContext2+0x91:
fffff803`736aa631 89430c mov dword ptr [rbx+0Ch],eax ds:00000000`0000000c=????????
Resetting default scope

STACK_TEXT:
ffffb581`47259ad8 fffff803`73812269 : 00000000`0000000a ffffb581`4725a2fc 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffb581`47259ae0 fffff803`7380dc34 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffb581`47259c20 fffff803`736aa631 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x474
ffffb581`47259db0 fffff803`736a8948 : ffffc70e`bdd66eb8 ffffda05`d5e926b8 ffffda05`d5e926a8 00000000`000004d0 : nt!RtlInitializeExtendedContext2+0x91
ffffb581`47259df0 fffff803`737fec52 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x118
ffffb581`47259fb0 fffff803`737fec20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffc70e`bdd66d78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue


SYMBOL_NAME: nt!RtlInitializeExtendedContext2+91

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.4355

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 91

FAILURE_BUCKET_ID: AV_nt!RtlInitializeExtendedContext2

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f6cfaab0-5ba1-e08f-7f3d-2832ec4d2572}

Followup: MachineOwner
---------
 
Apr 10, 2024
13
0
10
*******************************************************************************
* *
* 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: fffff805540b2962, Address of the instruction which caused the BugCheck
Arg3: ffffaf08bcbe7b00, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2140

Key : Analysis.Elapsed.mSec
Value: 2655

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 453

Key : Analysis.Init.Elapsed.mSec
Value: 3325

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Bugcheck.Code.TargetModel
Value: 0x3b

Key : Failure.Bucket
Value: AV_nt!MiValidateExistingImage

Key : Failure.Hash
Value: {56151630-5054-55ee-45b1-864537ed20d2}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff805540b2962

BUGCHECK_P3: ffffaf08bcbe7b00

BUGCHECK_P4: 0

FILE_IN_CAB: 050324-8921-01.dmp

CONTEXT: ffffaf08bcbe7b00 -- (.cxr 0xffffaf08bcbe7b00)
rax=ffffaf08bcbe85a0 rbx=ffffaf08bcbe8740 rcx=ffff820193298080
rdx=0000000000000000 rsi=0000000000000039 rdi=0000000000000000
rip=fffff805540b2962 rsp=ffffaf08bcbe8500 rbp=fffedc80c502a2a0
r8=0000000000000006 r9=7fffdc80c6bd9328 r10=7ffffffffffffffc
r11=ffffaf08bcbe8570 r12=ffffaf08bcbe8800 r13=0000000000000000
r14=0000000000000000 r15=ffff82019288fa20
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!MiValidateExistingImage+0x116:
fffff805`540b2962 448a4d0f mov r9b,byte ptr [rbp+0Fh] ss:0018:fffedc80`c502a2af=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: backgroundTaskHost.exe

STACK_TEXT:
ffffaf08`bcbe8500 fffff805`540b233f : 00000000`00000002 ffffaf08`00000000 ffff8201`95767b60 ffffaf08`bcbe8740 : nt!MiValidateExistingImage+0x116
ffffaf08`bcbe85a0 fffff805`5400660d : 00000000`00000000 ffffaf08`bcbe8740 ffff8201`9005a080 ffff8201`95767b60 : nt!MiShareExistingControlArea+0xc7
ffffaf08`bcbe85d0 fffff805`54007984 : ffff8201`9288fa20 00000000`00000000 ffff8201`95767b60 00000000`00000000 : nt!MiCreateImageOrDataSection+0x1ad
ffffaf08`bcbe86c0 fffff805`54006227 : 00000000`01000000 ffffaf08`bcbe8a80 00000000`00000001 00000000`00000010 : nt!MiCreateSection+0xf4
ffffaf08`bcbe8840 fffff805`54005fac : 00000019`4c87f478 00000000`0000000d 00000000`00000000 00000000`00000001 : nt!MiCreateSectionCommon+0x207
ffffaf08`bcbe8920 fffff805`53e119c5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateSection+0x5c
ffffaf08`bcbe8990 00007ffd`a854d9f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000019`4c87f428 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`a854d9f4


SYMBOL_NAME: nt!MiValidateExistingImage+116

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.4355

STACK_COMMAND: .cxr 0xffffaf08bcbe7b00 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 116

FAILURE_BUCKET_ID: AV_nt!MiValidateExistingImage

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {56151630-5054-55ee-45b1-864537ed20d2}

Followup: MachineOwner
---------
a new crash i just got system service exception which doesn't explain much to me
 
I would first look at the ram speed and timings as that BSOD can be caused by an unstable memory overclock. Your I7 9700kf supports DDR4 at 2666Mhz anything faster is overclocking the memory controller so 3600Mhz may be too fast for your CPU.

I just saw you are overclocking your CPU, so I would assume your overclock is unstable.
 

ubuysa

Distinguished
It doesn't help posting the analyze -v text. In any case the two dumps suggest that RAM is indeed the problem here. You know that you can't just install any RAM you fancy? You need to ensure that the RAM is on the QVL for the motherboard. The RAM QVL for your board is here.
 
Apr 10, 2024
13
0
10
It doesn't help posting the analyze -v text. In any case the two dumps suggest that RAM is indeed the problem here. You know that you can't just install any RAM you fancy? You need to ensure that the RAM is on the QVL for the motherboard. The RAM QVL for your board is here.
i swear it was on there, i checked g.skills website too, but ive also tried other ram non xmp same issue and it wasnt happening before this just started
 
Last edited:
Apr 10, 2024
13
0
10
I would first look at the ram speed and timings as that BSOD can be caused by an unstable memory overclock. Your I7 9700kf supports DDR4 at 2666Mhz anything faster is overclocking the memory controller so 3600Mhz may be too fast for your CPU.

I just saw you are overclocking your CPU, so I would assume your overclock is unstable.
I've tried default bios settings and it still crashes. I've tried 3 sets of memory all with different speeds and still crashes. I've tried 2133mhz, 2666, 2933. It worked before but overtime its just failed more and more. I'm taking it to a tech who can diagnose for me.
 
I've tried default bios settings and it still crashes. I've tried 3 sets of memory all with different speeds and still crashes. I've tried 2133mhz, 2666, 2933. It worked before but overtime its just failed more and more. I'm taking it to a tech who can diagnose for me.
Do you get the BSOD when your computer is running at stock speeds?