Game crashes and blue screen

Ok that misaligned instruction pointer suggest more of board and cpu now. Tho now this is telling you your network driver is causing some trouble, probably unrelated

Thank you for responding

Yes I did test my ram individually This is what happens

Both ram sticks in : I get Bsod almost every 10 to 60 mins

Individually: Dont get Bsod but game crashes with the same error like (Unhandled Exception: EXCEPTION_ACCESS_VIOLATION)

Moreover I replaced both ram sticks with new ones and still same thing happens individually and 2 rams together.

My question is can it be processor memory controller or does graphics cards vram?

The above error report were with 1 ram stick. Now ill paste error report when there were 2 sticks installed tell me if there is any difference

I can see memory involved in every crash report or event viewer but memory can also be other hardware right?

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff801`5ce00000 PsLoadedModuleList = 0xfffff801`5da2a2d0
Debug session time: Fri Jul 28 02:57:50.618 2023 (UTC + 5:30)
System Uptime: 0 days 0:07:09.203
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`5d1fc0c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc107`ab106d90=000000000000000a
9: 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: 000000000000fdd1, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 0000000000000031, 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: fffff8015d0df798, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2156

    Key  : Analysis.Elapsed.mSec
    Value: 12772

    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: 233

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_mtkwl6ex!unknown_function

    Key  : Failure.Hash
    Value: {7fbea1c0-2ec4-7d26-2ed6-cb151c611289}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  a

BUGCHECK_P1: fdd1

BUGCHECK_P2: ff

BUGCHECK_P3: 31

BUGCHECK_P4: fffff8015d0df798

FILE_IN_CAB:  072823-10203-01.dmp

WRITE_ADDRESS: fffff8015dafb390: 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
 000000000000fdd1 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffc107ab106ed0 -- (.trap 0xffffc107ab106ed0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000042 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000400000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8015d0df798 rsp=ffffc107ab107060 rbp=ffffd6802cb40180
 r8=000000000e1070f6  r9=0000000000000082 r10=0000000008000000
r11=ffffd6802cb48200 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na po nc
nt!KiUpdateSpeculationControl+0x1d8:
fffff801`5d0df798 41808ffd00000002 or      byte ptr [r15+0FDh],2 ds:00000000`000000fd=??
Resetting default scope

STACK_TEXT:  
ffffc107`ab106d88 fffff801`5d210129     : 00000000`0000000a 00000000`0000fdd1 00000000`000000ff 00000000`00000031 : nt!KeBugCheckEx
ffffc107`ab106d90 fffff801`5d20bce3     : ffffc107`ab106f30 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc107`ab106ed0 fffff801`5d0df798     : 00000000`0000000f fffff801`5d01a126 ffffd680`00000000 ffffad83`9efee040 : nt!KiPageFault+0x463
ffffc107`ab107060 fffff801`5d204782     : 001fe067`bcbbbdff 00000000`00000000 ffffd680`00002000 fffff801`00000001 : nt!KiUpdateSpeculationControl+0x1d8
ffffc107`ab1070e0 fffff801`5d2042f6     : 00000000`00000000 fffff801`5d0dbd1b 00000000`00000000 00000000`00000000 : nt!SwapContext+0x1b2
ffffc107`ab107120 fffff801`5d01c9e0     : ffffd680`00000000 00000000`00000000 00000000`0cb80cf0 ffffc107`ab107330 : nt!KiSwapContext+0x76
ffffc107`ab107260 fffff801`5d01bf0f     : ffffad83`00000009 ffffad83`00000011 ffffc107`ab107420 ffffad83`00000000 : nt!KiSwapThread+0x500
ffffc107`ab107310 fffff801`5d01b7b3     : ffffad83`00000000 ffffad83`00000000 ffffad83`a3010000 ffffad83`9efec180 : nt!KiCommitThreadWait+0x14f
ffffc107`ab1073b0 fffff801`5fa18fff     : ffffad83`9df97a30 fffff801`00000000 00000000`00000000 ffffad83`9dc30000 : nt!KeWaitForSingleObject+0x233
ffffc107`ab1074a0 fffff801`9ac4dac2     : 00000000`00000000 fffff801`9ad90728 00000000`00000000 ffffad83`9df977d0 : ndis!NdisWaitEvent+0x3f
ffffc107`ab1074e0 00000000`00000000     : fffff801`9ad90728 00000000`00000000 ffffad83`9df977d0 ffffad83`9ccbcaa8 : mtkwl6ex+0xdac2

SYMBOL_NAME:  mtkwl6ex+dac2

MODULE_NAME: mtkwl6ex

IMAGE_NAME:  mtkwl6ex.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  dac2

FAILURE_BUCKET_ID:  AV_mtkwl6ex!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7fbea1c0-2ec4-7d26-2ed6-cb151c611289}

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8073615f5d2, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1483

    Key  : Analysis.Elapsed.mSec
    Value: 2875

    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: 234

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Failure.Bucket
    Value: IP_MISALIGNED_AuthenticAMD.sys

    Key  : Failure.Hash
    Value: {716d112a-8330-4bbb-160c-ec98297019d2}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  d1

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8073615f5d2

FILE_IN_CAB:  072823-10531-01.dmp

WRITE_ADDRESS: fffff807346fb390: 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
 0000000000000000 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff509582d6600 -- (.trap 0xfffff509582d6600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffaa872562f7c8
rdx=000000000fc084fd rsi=0000000000000000 rdi=0000000000000000
rip=fffff8073615f5d2 rsp=fffff509582d6790 rbp=fffff509582d6890
 r8=0000000000000000  r9=0000000000000000 r10=fffff80733d01430
r11=ffffb1f95aa00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
tcpip!IppFindNextHopAtDpc+0xd22:
fffff807`3615f5d2 2108            and     dword ptr [rax],ecx ds:00000000`00000000=????????
Resetting default scope

MISALIGNED_IP: 
tcpip!IppFindNextHopAtDpc+d22
fffff807`3615f5d2 2108            and     dword ptr [rax],ecx

STACK_TEXT:  
fffff509`582d64b8 fffff807`33e10129     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff509`582d64c0 fffff807`33e0bce3     : fffff807`34650c00 fffff300`de0d30c0 00000000`007c854d 00000000`007c854d : nt!KiBugCheckDispatch+0x69
fffff509`582d6600 fffff807`3615f5d2     : 00000000`e0000001 00000000`e0000001 fffff509`582d6890 00000000`00000000 : nt!KiPageFault+0x463
fffff509`582d6790 fffff807`3615e64c     : 00000000`00000000 fffff807`340bd94f 00000000`e0000001 fffff807`34029e50 : tcpip!IppFindNextHopAtDpc+0xd22
fffff509`582d6a50 fffff807`3615c765     : ffffaa87`21d0a8a0 fffff807`00000000 ffffaa87`32bb84dc 00000000`00000000 : tcpip!IppFindNextHopAtDpcHelper+0xac
fffff509`582d6af0 fffff807`3615c3e8     : 00000000`00000200 fffff807`33c11fe0 00000000`00000000 00000000`7249534e : tcpip!IppGetAllBestRouteParameters+0x369
fffff509`582d6da0 fffff807`35d66276     : ffffaa87`32bb8470 fffff509`582d6ef0 00000000`00000098 ffffaa87`32bb8470 : tcpip!Ipv6GetAllBestRouteParameters+0x68
fffff509`582d6df0 fffff807`661a24f4     : 000000b4`865fe670 ffffaa87`32bb8470 00000000`00000000 000000b4`865fe670 : NETIO!NsiGetParameterEx+0x3a6
fffff509`582d6fa0 fffff807`661a26ce     : 00000000`00000000 ffffaa87`321f8ac0 ffffaa87`321f89f0 000000b4`865fe670 : nsiproxy!NsippGetParameter+0x1e4
fffff509`582d7130 fffff807`33c113a5     : ffffaa87`328ade20 00000000`00000000 00000000`00000000 00000000`00000000 : nsiproxy!NsippDispatch+0x6e
fffff509`582d7180 fffff807`3401121c     : 00000000`00000002 00000000`00000000 ffffaa87`328ade20 00000000`00000050 : nt!IofCallDriver+0x55
fffff509`582d71c0 fffff807`34010e71     : 00000000`00000000 fffff509`582d7500 00000000`00040800 ffffaa87`321f8ac0 : nt!IopSynchronousServiceTail+0x34c
fffff509`582d7260 fffff807`340101e6     : 00000000`00000001 00000000`000009c0 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xc71
fffff509`582d73a0 fffff807`33e0f8f8     : ffffaa87`32a1e080 000000b4`865fe578 fffff509`582d7428 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff509`582d7410 00007fff`82fcd0c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000b4`865fe608 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`82fcd0c4

SYMBOL_NAME:  NETIO!NsiGetParameterEx+3a6

IMAGE_VERSION:  10.0.19041.3205

STACK_COMMAND:  .cxr; .ecxr ; kb

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

FAILURE_BUCKET_ID:  IP_MISALIGNED_AuthenticAMD.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {716d112a-8330-4bbb-160c-ec98297019d2}

Dear IG agar

According to your description, you should first do a RAM isolation test to determine whether there is a RAM problem or a memory channel problem on the motherboard.

Simply put, you can plug in one RAM, do a memory check, test it and if the game and memory check passes, then add a second RAM and continue to test it until there is a problem.

Although there are NVDIA driver errors in the above reports, it doesn't necessarily mean that it is a video card driver abnormality or a video card hardware problem.

Hope the above information can help you.

Best Wish

Shawn Z | Microsoft Community Support Specialist

So it basically got 002b:feffc8832d121ae0but something is wrong hardware wise which changed it toffffffffffffffffcausing an access violation as that addressffffffffffffffff` is invalid, that is the max address space for 64 bit and shud not be used. Update bios to latest if not already, else ram/board issue

Hey I have changed like 4 different ram sticks (used the warrenty and changed both those sticks) So it might be the motherboard? 1 important thing that i have to tell you is my system was bsod every 10 mins when i had 2 ram sticks installed but when i removed 1 stick it was working fine for 3 months but recently was getting game crash and found out the crash report was the same as before. BTW When i had 2 ram sticks installed and tested windows memory diagnostic tool I received errors almost everytime but after i removed 1 stick i stopped receiving that error in windows memory diagnostic

Do you think it might be related to graphics card? cause i was getting this error in event viewer: Graphics Exception: SKEDCHECK02_LOCAL_MEMORY_LOW_SIZE failed and The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer

This was a crash report from a game:

Version: 273254, IsEditor: No, IsPerforceBuild: No, BuildConfiguration: Shipping, Launcher: Epic, NetMode: Listen Server, IsUsingMods: No, IsSaveGameEdited: No

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffffffffffff

FactoryGame_RenderCore_Win64_Shipping!FShaderMapResource::GetShader() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\RenderCore\Public\Shader.h:359]

FactoryGame_Renderer_Win64_Shipping!FGraphicsMinimalPipelineStateInitializer::AsGraphicsPipelineStateInitializer() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Renderer\Public\MeshPassProcessor.h:326]

FactoryGame_Renderer_Win64_Shipping!FMeshDrawCommand::SubmitDrawBegin() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Renderer\Private\MeshPassProcessor.cpp:1357]

FactoryGame_Renderer_Win64_Shipping!FMeshDrawCommand::SubmitDraw() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Renderer\Private\MeshPassProcessor.cpp:1577]

FactoryGame_Renderer_Win64_Shipping!FInstanceCullingContext::SubmitDrawCommands() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Renderer\Private\InstanceCulling\InstanceCullingContext.cpp:1385]

FactoryGame_Renderer_Win64_Shipping!TGraphTask<FDrawVisibleMeshCommandsAnyThreadTask>::ExecuteTask() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Public\Async\TaskGraphInterfaces.h:1310]

FactoryGame_Core_Win64_Shipping!<lambda_17c904c32264d0348d15245fba0e1bff>::operator()() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Public\Async\Fundamental\Task.h:501]

FactoryGame_Core_Win64_Shipping!LowLevelTasks::TTaskDelegate<LowLevelTasks::FTask * __cdecl(bool),48>::TTaskDelegateImpl<<lambda_17c904c32264d0348d15245fba0e1bff>,0>::CallAndMove() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Public\Async\Fundamental\TaskDelegate.h:171]

FactoryGame_Core_Win64_Shipping!LowLevelTasks::FTask::ExecuteTask() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Public\Async\Fundamental\Task.h:627]

FactoryGame_Core_Win64_Shipping!LowLevelTasks::FScheduler::TryExecuteTaskFrom<LowLevelTasks::TLocalQueueRegistry<1024>::TLocalQueue,&LowLevelTasks::TLocalQueueRegistry<1024>::TLocalQueue::DequeueGlobal,0>() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Private\Async\Fundamental\Scheduler.cpp:349]

FactoryGame_Core_Win64_Shipping!LowLevelTasks::FScheduler::WorkerMain() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Private\Async\Fundamental\Scheduler.cpp:378]

FactoryGame_Core_Win64_Shipping!UE::Core::Private::Function::TFunctionRefCaller<<lambda_abf63b4b71b3a09b60c8feab122cedbd>,void __cdecl(void)>::Call() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Public\Templates\Function.h:475]

FactoryGame_Core_Win64_Shipping!FThreadImpl::Run() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Private\HAL\Thread.cpp:69]

FactoryGame_Core_Win64_Shipping!FRunnableThreadWin::Run() [C:\BuildAgent\work\607eee041ab2bfcf\UE4\Engine\Source\Runtime\Core\Private\Windows\WindowsRunnableThread.cpp:149]

BTW the crash report was from recent crash but do you want me to give you more crash report from before for more info?

Thank you for Responding cause my pc maker doesn't even know how to check the problems

So it basically got 002b:feffc8832d121ae0but something is wrong hardware wise which changed it toffffffffffffffffcausing an access violation as that addressffffffffffffffff` is invalid, that is the max address space for 64 bit and shud not be used. Update bios to latest if not already, else ram/board issue