Im having some BSOD and crashes while gaming on Apex Legends

Hi JeffLiew95,

This dump file to me shows a faulty RAM. But this is difficult to actually diagnose since hardware/software uses RAM and it may also be one of those that causes an issue with the memory.

Dump file:

FAULTY_HARDWARE_CORRUPTED_PAGE (12b)

This bugcheck indicates that a single bit error was found in this page. This is a hardware memory error.

Arguments:

Arg1: ffffffffc00002c4, virtual address mapping the corrupted page

Arg2: 00000000000009c2, physical page number

Arg3: 000001d9b4250000, zero

Arg4: ffffa18070db8000, zero

BUGCHECK_P1: ffffffffc00002c4

BUGCHECK_P2: 9c2

BUGCHECK_P3: 1d9b4250000

BUGCHECK_P4: ffffa18070db8000

More info: https://docs.microsoft.com/en-us/windows-hardwa...

This bugcheck can only occur by memory corruption due to physical memory access. The causes for physical memory corruption include:

Defective RAM hardware

A driver or device incorrectly modifying physical pages via an incorrect DMA operation or associated MDL.

Corruption caused by a hardware device or firmware corrupting memory, such as firmware illegally modifying physical pages across a power transition.

Have you tried moving the RAM to a different slot? How many sticks do you have? I would suggest running memtest for each stick (if you have more than one, remove the others first). See this link for a complete step by step: https://www.tenforums.com/tutorials/14201-memte...

Note: This is a non-Microsoft website.

Sometimes it may also be the OS. In this thread a similar bugcheck occurred (yours has different parameters but nevertheless same faulting module) but was repaired by DISM restore: https://answers.microsoft.com/en-us/windows/for...

Hi JeffLiew95,

It will now be located at C:\Windows\Memory. During re-installation of network drivers, make sure to download the new drivers first, then clean uninstall+delete software of drivers > restart the computer, then install the newest drivers downloaded.

Also, type and enter the following in admin command prompt, then share the results in our thread:

wmic recoveros set autoreboot = false

bcdedit /enum {badmemory}

And this may be simple, but can the game be played in safe mode? Have you tried it and see if it still crashes?

I tried updating through device manager the network adapters are all up to date.

NVIDIA surround physx are greyed out and cant be used.

So, Im not sure how to go about it.

I have set it to complete memory dump. Will the dump will still be in the same folder location?

After the full analysis, the faulting module shows as afd.sys. Now this is network related. I would suggest updating network drivers as well.

Hi JeffLiew95,

I reviewed the previous thread as well as run a quick analysis for the dump file. This time, it's a 7E pointing to dxgkrnl.sys. 

Usually this points to a faulty graphics driver. Some forums say that turning off NVIDIA surround also helps (pressing Ctrl + Alt + S or Ctrl + Alt + R), or disabling SLI technology in the NVIDIA control panel. Reinstalling directx, v++,. net framework, and updating BIOS drivers may also help.

You may change the way Windows captures dump files from mini to complete dump files as follows:
1. Go to Control Panel > System and Security > System.
2. Select Advanced system settings > Advanced tab > Startup and Recovery > Settings.
3. Select Complete memory dump.
4. Restart the computer.

[code]
Debugging Details:
------------------

KEY_VALUES_STRING: 1

PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: fffff487ec849280

BUGCHECK_P3: fffff487ec8491d8

BUGCHECK_P4: 0

TRAP_FRAME:  fffff487ec849280 -- (.trap 0xfffff487ec849280)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff9b86c6bc8270 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000010000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80445c49f49 rsp=fffff487ec849410 rbp=0000000000000000
 r8=000000000000006a  r9=0000000000000000 r10=fffff80432e320e0
r11=ffff9b86d01a3200 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
afd!AfdBufferReceiveDatagram+0x6c39:
fffff804`45c49f49 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff487ec8491d8 -- (.exr 0xfffff487ec8491d8)
ExceptionAddress: fffff80445c49f49 (afd!AfdBufferReceiveDatagram+0x0000000000006c39)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

CPU_COUNT: c

CPU_MHZ: a20

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x139

PROCESS_NAME:  AutoConnectHelper.exe

CURRENT_IRQL:  2

DEFAULT_BUCKET_ID:  FAIL_FAST_CORRUPT_LIST_ENTRY

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

ANALYSIS_SESSION_HOST:  A-PC0QG2QD

ANALYSIS_SESSION_TIME:  02-03-2020 22:14:00.0938

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8042d9d32e9 to fffff8042d9c14e0

STACK_TEXT:  
fffff487`ec848f58 fffff804`2d9d32e9 : 00000000`00000139 00000000`00000003 fffff487`ec849280 fffff487`ec8491d8 : nt!KeBugCheckEx
fffff487`ec848f60 fffff804`2d9d3710 : ffff9b86`c99098a0 00000000`00000002 ffff9b86`b0cc10c0 fffff804`32f55c66 : nt!KiBugCheckDispatch+0x69
fffff487`ec8490a0 fffff804`2d9d1aa5 : 00000000`00000000 00000000`00000000 ffff9b86`c4f2fce0 00000000`00000000 : nt!KiFastFailDispatch+0xd0
fffff487`ec849280 fffff804`45c49f49 : ffff9b86`bd213b20 00000000`00001000 ffff9b86`c6bc8200 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x325
fffff487`ec849410 fffff804`45c43a95 : ffff9b86`bd213b20 fffff487`ec849580 00000000`00001008 00000000`00000018 : afd!AfdBufferReceiveDatagram+0x6c39
fffff487`ec849480 fffff804`45c928ad : ffff9b86`bb4fe040 fffff487`00000000 00000000`00000000 00000000`00000000 : afd!AfdReceiveDatagramEventCommonHandler+0x225
fffff487`ec8495f0 fffff804`32f78916 : fffff487`ec8497c0 fffff487`ec849701 fffff487`00000000 ffff9b86`bb4fe040 : afd!AfdTLDgramReceiveEventHandler+0x14d
fffff487`ec8496c0 fffff804`32f77d50 : ffff9b86`b82ff040 ffff9b86`c24d4d40 fffff487`ec849c00 fffff804`00000000 : tcpip!UdpDeliverDatagrams+0x446
fffff487`ec849b00 fffff804`32f77700 : fffff804`32e3c830 fffff804`32f2ccb3 fffff804`330ff908 ffff9b86`c2830540 : tcpip!UdpReceiveDatagrams+0x640
fffff487`ec849ef0 fffff804`32f14643 : ffff9b86`c2830540 fffff804`32e33951 ffff9b86`c2830540 00000000`00000000 : tcpip!UdpNlClientReceiveDatagrams+0x10
fffff487`ec849f20 fffff804`32f5fbc8 : 00000000`00000000 ffff9b86`bb372040 fffff487`ec84a0a9 fffff487`ec84a070 : tcpip!IppProcessDeliverList+0xd3
fffff487`ec84a010 fffff804`32f23737 : 00000000`00000000 00000000`00000000 fffff487`ec84a1f0 fffff487`ec84a1c0 : tcpip!IppReceiveHeaderBatch+0x228
fffff487`ec84a110 fffff804`32f2325d : 00000000`00004800 00000000`00000000 ffff9b86`b04bf830 00000000`00000000 : tcpip!IppLbIndicatePackets+0x30f
fffff487`ec84a1c0 fffff804`2d869e28 : fffff487`ec84a300 ffff9b86`bbb78080 fffff487`ec84a3e0 fffff487`ec84a370 : tcpip!IppLbTransmitStackCallout+0x11d
fffff487`ec84a230 fffff804`2d869d9d : fffff804`32f23140 fffff487`ec84a370 ffff9b86`b0cbe990 fffff804`330ff2e0 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffff487`ec84a2a0 fffff804`32f23ce9 : ffff9b86`b0f02540 ffff9b86`b0cbe990 ffff9b86`bb372040 ffff9b86`be10a720 : nt!KeExpandKernelStackAndCalloutEx+0x1d
fffff487`ec84a2e0 fffff804`32f5e053 : ffff9b86`b0dcd800 fffff487`ec84a501 ffff9b86`b82ff040 00000000`00000000 : tcpip!IppLoopbackEnqueue+0x1fd
fffff487`ec84a540 fffff804`32f5d972 : 00000000`00000000 ffff9b86`badf4584 ffff9b86`bd0ff0f8 fffff487`00000014 : tcpip!IppDispatchSendPacketHelper+0x423
fffff487`ec84a610 fffff804`32f5c0fc : 00000000`00000004 00000000`00000004 ffff9b86`b0dcd9b8 ffff9b86`b0dcd8e8 : tcpip!IppPacketizeDatagrams+0x302
fffff487`ec84a750 fffff804`32f2a730 : ffff9b86`b0e81400 00000000`00000000 fffff804`330ff2e0 ffff9b86`cb126a80 : tcpip!IppSendDatagramsCommon+0x40c
fffff487`ec84a8d0 fffff804`32f20111 : 00000000`c596025e 00000000`00000000 00000000`0000912f 00000000`00000000 : tcpip!IpNlpSendDatagrams+0x40
fffff487`ec84a910 fffff804`32f1ebe2 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9b86`b8b4b8f0 : tcpip!UdpSendMessagesOnPath+0x1041
fffff487`ec84adb0 fffff804`32f1e965 : ffff9b86`c24d6850 fffff487`ec84b370 fffff487`ec84b260 fffff487`ec84b260 : tcpip!UdpSendMessages+0x262
fffff487`ec84b150 fffff804`2d869e28 : 00000000`00000004 00000000`00000000 00000000`00000a98 ffff9b86`c588a030 : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
fffff487`ec84b180 fffff804`2d869d9d : fffff804`32f1e950 fffff487`ec84b260 ffff9b86`b04f7130 fffff804`2d833294 : nt!KeExpandKernelStackAndCalloutInternal+0x78
fffff487`ec84b1f0 fffff804`32f26dc3 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`45c75020 : nt!KeExpandKernelStackAndCalloutEx+0x1d
fffff487`ec84b230 fffff804`45c96030 : ffff9b86`bbea19e0 fffff487`ec84ba80 ffff9b86`d01b37e0 fffff487`ec84ba80 : tcpip!UdpTlProviderSendMessages+0x73
fffff487`ec84b2b0 fffff804`45c74ef3 : ffff9b86`bbea19e0 fffff487`ec84b5d0 00000000`0000006a ffff9b86`c588e660 : afd!AfdFastDatagramSend+0x630
fffff487`ec84b420 fffff804`2dde8efb : 00000000`00000b18 00000000`00000000 00000000`00000000 ffff9b86`ca5967a0 : afd!AfdFastIoDeviceControl+0x1863
fffff487`ec84b800 fffff804`2dde87c6 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`017ebb24 : nt!IopXxxControlFile+0x71b
fffff487`ec84b920 fffff804`2d9d2d15 : ffff9b86`bbb78080 00000000`00cbe518 00000000`00000000 00000000`0000300f : nt!NtDeviceIoControlFile+0x56
fffff487`ec84b990 00000000`77d71cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`00cbee18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d71cbc

THREAD_SHA1_HASH_MOD_FUNC:  3d9847ed2481542dffdcb676783e1abe31e440f3

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ea6809e1037ca8d7b78be221637bf1f38f0576f1

THREAD_SHA1_HASH_MOD:  fdd8625ba6a7c97951923690eee6d433b2f208a8

FOLLOWUP_IP: 
afd!AfdBufferReceiveDatagram+6c39
fffff804`45c49f49 cd29            int     29h

FAULT_INSTR_CODE:  41cc29cd

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  afd!AfdBufferReceiveDatagram+6c39

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  10.0.18362.592

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  6c39

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_afd!AfdBufferReceiveDatagram

BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_afd!AfdBufferReceiveDatagram

PRIMARY_PROBLEM_CLASS:  0x139_3_CORRUPT_LIST_ENTRY_afd!AfdBufferReceiveDatagram

TARGET_TIME:  2020-02-03T12:51:17.000Z

OSBUILD:  18362

OSSERVICEPACK:  592

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:  1972-08-22 08:24:00

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  ea83

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_corrupt_list_entry_afd!afdbufferreceivedatagram

FAILURE_ID_HASH:  {dd2989f1-4260-d404-195b-a56ff0b7bc78}

Followup:     MachineOwner
---------
[/code]

Hope the above helps.