That's not very specific.
You are still not using the latest graphics drivers:
http://www.geforce.com/drivers
Also, your motherboard seems to have several updates:
https://www.msi.com/Motherboard/support/Z370-TOMAHAWK#down-driver&Win10%2064
Community ManagerHey @Nesrae
Let's find out if it's a specific program running in the background that's conflicting with Battlefield V. Can you try a clean boot for me and then immediately launch Origin/BFV when the PC starts back up. See if you're getting that memory leak. If not, try opening one other program at a time (like Discord) to see what happens when that other program is also launched.
A clean boot will temporarily disable all programs that aren't necessary to start up a PC. This way we can narrow down the possibility of it being related to a certain program.
May have found the problem which was also giving me Bsod, Glasswire drivers was leaking on everything, had to use verifier & check each drivers.
So all good, sorry 😉
i'll reply to myself; Not fixed, Battlefield 5 keep giving me bsod
Probably a driver since "ntoskrnl.exe+1a9490" is giving me hard time, but only with bf5.
CLean Windows, not much installed.
I'll link my minidump or rather copy paste since i can't upload it looks like :P
"
Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt!RtlSidHashLookup+ca fffff800`c0ccf89a 420fb60400 movzx eax,byte ptr [rax+r8] CONTEXT: ffffb70523cf63a0 -- (.cxr 0xffffb70523cf63a0) rax=0000000000000010 rbx=ffffdc0dd10027e0 rcx=ffffdc0de1b5adf0 rdx=0000000000000000 rsi=0000000000000010 rdi=ffffdc0de1b5aa48 rip=fffff800c0ccf89a rsp=ffffb70523cf6d90 rbp=0000000000000000 r8=00000000c0f97d8f r9=0000000000000000 r10=0000000000000000 r11=00000000000000e8 r12=0000000000000010 r13=0000000000000010 r14=0000000000000201 r15=ffffb70523cf7168 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!RtlSidHashLookup+0xca: fffff800`c0ccf89a 420fb60400 movzx eax,byte ptr [rax+r8] ds:002b:00000000`c0f97d9f=?? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: bfv.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800c0ccf748 to fffff800c0ccf89a STACK_TEXT: ffffb705`23cf6d90 fffff800`c0ccf748 : 00000000`00000282 00000000`00000000 ffffdc0d`e1b5adf0 00000000`00000000 : nt!RtlSidHashLookup+0xca ffffb705`23cf6df0 fffff800`c0d1f063 : ffffdc0d`e1b5a960 00000000`00000000 ffffdc0d`d10027e0 fffff800`c0cd466d : nt!SepSidInTokenSidHash+0x48 ffffb705`23cf6e20 fffff800`c119ee4e : ffffba0a`c7dca580 fffff800`c12218a4 00000000`00000000 00000000`00000000 : nt!SepSidInToken+0x3f ffffb705`23cf6e70 fffff804`3f2ce89f : ffffdc0d`e1b5a960 00000000`00000000 00000000`00000000 ffffba0a`c9d68080 : nt!SeTokenIsAdmin+0x4e ffffb705`23cf6ec0 ffffdc0d`e1b5a960 : 00000000`00000000 00000000`00000000 ffffba0a`c9d68080 ffffba0a`c3020000 : nvlddmkm+0xbbe89f ffffb705`23cf6ec8 00000000`00000000 : 00000000`00000000 ffffba0a`c9d68080 ffffba0a`c3020000 ffffb705`23cf7770 : 0xffffdc0d`e1b5a960 FOLLOWUP_IP: nvlddmkm+bbe89f fffff804`3f2ce89f 400fb6fd movzx edi,bpl SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nvlddmkm+bbe89f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5bd2fd8a STACK_COMMAND: .cxr 0xffffb70523cf63a0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+bbe89f BUCKET_ID: X64_0x3B_nvlddmkm+bbe89f
Let's just wait until tomorrow where a 27GB patch arrives, hopefully, that fixes most stability and crashing issues. If it still happens after tomorrow please come back and tell us 🙂
Well, at it again after the new bf5 update, bsod
Debugging Details: ------------------ TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". FAULTING_IP: nt!KiExecuteAllDpcs+257 fffff800`6ad87297 448bf0 mov r14d,eax EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPagedPoolEnd unable to get nt!MmNonPagedPoolStart unable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". BUGCHECK_STR: 0x1e_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: bfv.exe CURRENT_IRQL: 2 EXCEPTION_RECORD: ffffc58200000001 -- (.exr 0xffffc58200000001) Cannot read Exception record @ ffffc58200000001 TRAP_FRAME: ffffc582488be8e0 -- (.trap 0xffffc582488be8e0) Unable to read trap frame at ffffc582`488be8e0 LAST_CONTROL_TRANSFER: from fffff8006aeeb91a to fffff8006ae53690 CONTEXT: 48038941c6ff49c0 -- (.cxr 0x48038941c6ff49c0) Unable to read context, Win32 error 0n30 STACK_TEXT: fffff20d`bba36ad8 fffff800`6aeeb91a : 00000000`0000001e ffffffff`c0000005 fffff800`6ad87297 00000000`00000000 : nt!KeBugCheckEx fffff20d`bba36ae0 fffff800`6ae5bf3d : fffff800`6b09b000 fffff800`6acaa000 00058560`00953000 00000000`00000000 : nt!KiFatalExceptionHandler+0x22 fffff20d`bba36b20 fffff800`6ad09e46 : fffff20d`bba36c50 fffff20d`bba37110 00000000`00000000 fffff20d`bba37a28 : nt!RtlpExecuteHandlerForException+0xd fffff20d`bba36b50 fffff800`6ad0b943 : fffff20d`bba37a28 fffff20d`bba37770 fffff20d`bba37a28 ffffdf81`663a0180 : nt!RtlDispatchException+0x416 fffff20d`bba37240 fffff800`6ae64342 : ffffc582`00000001 fffff20d`bba37970 ffffc582`488be8e0 fffff801`dbd1a23f : nt!KiDispatchException+0x1f3 fffff20d`bba378f0 fffff800`6ae60a9c : 00000000`00000000 00000000`00000000 00000022`00000001 00000000`00000000 : nt!KiExceptionDispatch+0xc2 fffff20d`bba37ad0 fffff800`6ad87297 : fffff801`dbc7ec41 ffffdf81`663a2f80 ffffc582`489d7980 ffffdf81`663a0180 : nt!KiGeneralProtectionFault+0x2dc fffff20d`bba37c60 fffff800`6ad8697b : ffffdf81`663a0180 08c2a9fc`00000000 00000000`00000002 00000000`00000004 : nt!KiExecuteAllDpcs+0x257 fffff20d`bba37da0 fffff800`6ae5a5e5 : 7401ffd8`527675f3 ffffdf81`663a0180 fffff20d`c10c7a80 ffffdf81`6630dc80 : nt!KiRetireDpcList+0x1db fffff20d`bba37fb0 fffff800`6ae5a3e0 : 00000001`0465a8d8 fffff800`6ac214e6 00000000`0098967f 00000000`f9c5f000 : nt!KxRetireDpcList+0x5 fffff20d`c10c79c0 fffff800`6ae59d15 : 00000000`000000b7 fffff800`6ae55011 00000000`f9c5be40 ffffdf81`6630dc80 : nt!KiDispatchInterruptContinue fffff20d`c10c79f0 fffff800`6ae55011 : 00000000`f9c5be40 ffffdf81`6630dc80 00000000`00000001 00000001`04602440 : nt!KiDpcInterruptBypass+0x25 fffff20d`c10c7a00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0xb1 FOLLOWUP_IP: nt!KiExecuteAllDpcs+257 fffff800`6ad87297 448bf0 mov r14d,eax SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: nt!KiExecuteAllDpcs+257 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5bdaa393 STACK_COMMAND: .cxr 0x48038941c6ff49c0 ; kb FAILURE_BUCKET_ID: X64_0x1e_c0000005_nt!KiExecuteAllDpcs+257 BUCKET_ID: X64_0x1e_c0000005_nt!KiExecuteAllDpcs+257 Followup: MachineOwner
WIN8_DRIVER_FAULT
Would suggest you might want to update all your system drivers, also there's a new graphics driver out you might want to give a go.
Also, some more information would be nice, if you can post at least the dxdiag that mentioned in https://answers.ea.com/t5/Technical-Issues/How-To-Write-amp-Get-Responses-for-Your-Technical-Issue/m-p/7160970#M360 that would help.
