Question BSODs after latest Windows Update

[GreyFox37]

After Windows recently updated, I've been getting BSODs when I load Final Fantasy 14. I have an i7 9700k, 32 gigs of RAM, and a 1080Ti stock speeds. After I load the game, about 3-5 min in, I get the BSOD. I ran a check. It only happens when I load a game. I've got my own ideas as to what is happening, but figured I'd get some advice. Any ideas and tips greatly appreciated.


ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffeeeb2fa90069, Virtual address for the attempted write.
Arg2: 010000084d010021, PTE contents.
Arg3: ffffd70f82a6f440, (reserved)
Arg4: 000000000000000b, (reserved)

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

Page 148685 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1937

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1977

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

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

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

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: be

BUGCHECK_P1: ffffeeeb2fa90069

BUGCHECK_P2: 10000084d010021

BUGCHECK_P3: ffffd70f82a6f440

BUGCHECK_P4: b

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: csrss.exe

TRAP_FRAME: ffffd70f82a6f440 -- (.trap 0xffffd70f82a6f440)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=0000000000000000 rcx=ffffeeeb2fa90061
rdx=ffffeea342869620 rsi=0000000000000000 rdi=0000000000000000
rip=ffffeeeb2fa5a64e rsp=ffffd70f82a6f5d0 rbp=ffffeea3428a6968
r8=0000000000000000 r9=000000000000002f r10=fffff8005d926f90
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
win32kbase!HMUnlockObjectWorker+0xe:
ffffeeeb2fa5a64e f00fc14108 lock xadd dword ptr [rcx+8],eax ds:ffffeeeb2fa90069=aff90d8b
Resetting default scope

STACK_TEXT:
ffffd70f82a6f198 fffff8005da4aca5 : 00000000000000be ffffeeeb2fa90069 010000084d010021 ffffd70f82a6f440 : nt!KeBugCheckEx
ffffd70f82a6f1a0 fffff8005d89f550 : 0000000000000000 0000000000000003 ffffd70f82a6f4c0 0000000000000000 : nt!MiSystemFault+0x18d735
ffffd70f82a6f2a0 fffff8005da05a5e : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!MmAccessFault+0x400
ffffd70f82a6f440 ffffeeeb2fa5a64e : ffffeea342995174 0000000000013c97 0000000000013c97 ffffeea342995188 : nt!KiPageFault+0x35e
ffffd70f82a6f5d0 ffffeeeb2f40a974 : ffffeeeb2f40a9e2 ffffeeeb2f40a9e2 ffff9e0d7b53c700 ffffeea342995188 : win32kbase!HMUnlockObjectWorker+0xe
ffffd70f82a6f600 0000000000000001 : 0000000000000004 0000200000000000 ffffd70f82a6f7b0 ffffeeeb2f40a546 : win32kfull!TimersProc+0x114
ffffd70f82a6f690 0000000000000004 : 0000200000000000 ffffd70f82a6f7b0 ffffeeeb2f40a546 0000000000000000 : 0x1
ffffd70f82a6f698 0000200000000000 : ffffd70f82a6f7b0 ffffeeeb2f40a546 0000000000000000 00000000000849c3 : 0x4
ffffd70f82a6f6a0 ffffd70f82a6f7b0 : ffffeeeb2f40a546 0000000000000000 00000000000849c3 0000000000000001 : 0x0000200000000000 ffffd70f82a6f6a8 ffffeeeb2f40a546 : 0000000000000000 00000000000849c3 0000000000000001 0000000000000004 : 0xffffd70f82a6f7b0
ffffd70f82a6f6b0 ffffeeeb2facfc14 : ffff9e0d76eef080 ffff9e0d76eef080 0000000000000000 0000000000000005 : win32kfull!RawInputThread+0x7f6
ffffd70f82a6f870 ffffeeeb2f494a21 : ffff9e0d76eef080 0000000000000000 0000000000000005 0000000000000005 : win32kbase!xxxCreateSystemThreads+0xc4
ffffd70f82a6f9a0 ffffeeeb2f35474e : ffff9e0d76eef080 ffff9e0d76eef080 0000000000000000 0000000000000000 : win32kfull!NtUserCallNoParam+0x71
ffffd70f82a6f9d0 fffff8005da092b5 : ffff9e0d00000005 0000000000000005 0000025f22a05280 0000000000000408 : win32k!NtUserCallNoParam+0x16
ffffd70f82a6fa00 00007fff4ff610e4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
0000008a38b3fc78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007fff`4ff610e4


SYMBOL_NAME: win32kbase!HMUnlockObjectWorker+e

MODULE_NAME: win32kbase

IMAGE_NAME: win32kbase.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: e

FAILURE_BUCKET_ID: AV_win32kbase!HMUnlockObjectWorker

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9e952ddc-0b7e-c566-dbb4-78c1e2cdd928}

Followup: MachineOwner

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[GreyFox37]

https://1drv.ms/u/s!AkH08r0Xd3Uti1ZwCbl6zJw0N4E7

Sorry for my delay, just got back from a business trip

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://jsfiddle.net/tjhf02do/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	042522-10609-01.dmp (Apr 26 2022 - 00:14:49)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process running at time of crash: csrss.exe)
Uptime:	0 Day(s), 20 Hour(s), 44 Min(s), and 28 Sec(s)

Comment: VERIFIER flags are turned on.

Possible Motherboard page: https://www.msi.com/Motherboard/Z390-A-PRO
There is a BIOS update available for your system. You are using version 1.8 and the latest stable version is 1.D. I recommend avoiding the latest BETA version. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[GreyFox37]

I figured it had to be that and yes, that is the correct mobo, thanks. I'll wait for additional info, thanks

Update: I updated the BIOS, non beta version, it went without a hitch. I'm gonna monitor closely. Fingers crossed

 

[Colif]

remove these, they are too old

Jul 12 2011	SASKUTIL64.SYS	SUPERAntiSpyware driver http://www.superantispyware.com/
Jul 21 2011	SASDIFSV64.SYS	SUPERAntiSpyware driver http://www.superantispyware.com/

i would update tunnelbear as well

cause could be GPU drivers.

 

[GreyFox37]

I deleted TunnelBear, forgot I had it, no need for it anymore. I got the latest Nvidia drivers and got rid of those old anti-sw drivers too. Thanks for the extra tips

 

[GreyFox37]

Okay, looks like it resolved everything. No BSODs since. Thanks for the assistance!

 

[gardenman]

If you haven't reset VERIFIER, you should.