BSOD with Kernel Security Check failure (while Gaming)

[anarchinine]

Hello,

Need some help here. Whenever I fire up a game, I get random crashes. The timing varies from one game to another. Cyberpunk 2077 would crash within 5 minutes of load, Far Cry 6 about half an hour. Rocket League sometimes works for hours, sometimes crashes after an hour and a half. Every time the frame freezes, the music goes on and eventually, crash to desktop.

Recently, however, I've started getting BSODs with the error mentioned in the post title. The funny thing is, while the game runs, it runs perfectly fine. There is no artifacting, no random freeze and plays (except before crash) and no stutters to speak of. it's all smooth sailing until the ship drowns suddenly (metaphorically speaking).

I haven't changed much. Recently got a Colorful RTX 3070, swapping out my old RTX 2060. The thing is, the crashes used to take place on the 2060 as well, but never got this weird BSOD before. I've stress tested the GPU with Furmark for about 20 minutes at a stretch. Steady temps of 69-70 degrees. Cinebench works perfectly. GPU Stability test was completed up to 37 minutes, no issues whatsoever.

Oh, and I installed Windows 11 about a month ago. These errors have increased substantially since the new OS was installed.

 

I've attached the dump files. The latest dump files shows the following - 

 

[0x0]   nt!KeBugCheckEx   
[0x1]   nt!KiBugCheckDispatch + 0x69   
[0x2]   nt!KiFastFailDispatch + 0xb2   
[0x3]   nt!KiRaiseSecurityCheckFailure + 0x312   
[0x4]   dxgmms2!VIDMM_PROCESS::RemoveCommitment + 0x187   
[0x5]   dxgmms2!VIDMM_DEVICE::RemoveCommitment + 0xba   
[0x6]   dxgmms2!VIDMM_GLOBAL::NotifyAllocationEviction + 0x4a   
[0x7]   dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand + 0x25a   
[0x8]   dxgmms2!VIDMM_WORKER_THREAD::Run + 0x171c   
[0x9]   dxgmms2!VidMmWorkerThreadProc + 0x9   
[0xa]   nt!PspSystemThreadStartup + 0x55   
[0xb]   nt!KiStartSystemThread + 0x34   

 

There is an older one from a crash yesterday. It reads - 

 

[0x0]   nt!KeBugCheckEx   
[0x1]   nt!KiBugCheckDispatch + 0x69   
[0x2]   nt!KiFastFailDispatch + 0xb2   
[0x3]   nt!KiRaiseSecurityCheckFailure + 0x312   
[0x4]   nt!KiTryUnwaitThread + 0x11509a   
[0x5]   nt!KiTimerWaitTest + 0x1fa   
[0x6]   nt!KiProcessExpiredTimerList + 0xda   
[0x7]   nt!KiRetireDpcList + 0x714   
[0x8]   nt!KiIdleLoop + 0x9e   
 

I have no idea what these mean. 

 

My setup is 

Ryzen 5 2600 

Colorful RTX 3070 Ultra White OC

32 GB (8x4GB) XPG 3000Mhz RAM 

Asrock B450 Steel Legend Motherboard 

Windows 11

 

Any help would be appreciated. 

Minidump.zip

[Frizz]

2 hours ago, anarchinine said:

Hello,

Need some help here. Whenever I fire up a game, I get random crashes. The timing varies from one game to another. Cyberpunk 2077 would crash within 5 minutes of load, Far Cry 6 about half an hour. Rocket League sometimes works for hours, sometimes crashes after an hour and a half. Every time the frame freezes, the music goes on and eventually, crash to desktop.

Recently, however, I've started getting BSODs with the error mentioned in the post title. The funny thing is, while the game runs, it runs perfectly fine. There is no artifacting, no random freeze and plays (except before crash) and no stutters to speak of. it's all smooth sailing until the ship drowns suddenly (metaphorically speaking).

I haven't changed much. Recently got a Colorful RTX 3070, swapping out my old RTX 2060. The thing is, the crashes used to take place on the 2060 as well, but never got this weird BSOD before. I've stress tested the GPU with Furmark for about 20 minutes at a stretch. Steady temps of 69-70 degrees. Cinebench works perfectly. GPU Stability test was completed up to 37 minutes, no issues whatsoever.

Oh, and I installed Windows 11 about a month ago. These errors have increased substantially since the new OS was installed.

 

I've attached the dump files. The latest dump files shows the following - 

 

[0x0]   nt!KeBugCheckEx   
[0x1]   nt!KiBugCheckDispatch + 0x69   
[0x2]   nt!KiFastFailDispatch + 0xb2   
[0x3]   nt!KiRaiseSecurityCheckFailure + 0x312   
[0x4]   dxgmms2!VIDMM_PROCESS::RemoveCommitment + 0x187   
[0x5]   dxgmms2!VIDMM_DEVICE::RemoveCommitment + 0xba   
[0x6]   dxgmms2!VIDMM_GLOBAL::NotifyAllocationEviction + 0x4a   
[0x7]   dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand + 0x25a   
[0x8]   dxgmms2!VIDMM_WORKER_THREAD::Run + 0x171c   
[0x9]   dxgmms2!VidMmWorkerThreadProc + 0x9   
[0xa]   nt!PspSystemThreadStartup + 0x55   
[0xb]   nt!KiStartSystemThread + 0x34   

 

There is an older one from a crash yesterday. It reads - 

 

[0x0]   nt!KeBugCheckEx   
[0x1]   nt!KiBugCheckDispatch + 0x69   
[0x2]   nt!KiFastFailDispatch + 0xb2   
[0x3]   nt!KiRaiseSecurityCheckFailure + 0x312   
[0x4]   nt!KiTryUnwaitThread + 0x11509a   
[0x5]   nt!KiTimerWaitTest + 0x1fa   
[0x6]   nt!KiProcessExpiredTimerList + 0xda   
[0x7]   nt!KiRetireDpcList + 0x714   
[0x8]   nt!KiIdleLoop + 0x9e   
 

I have no idea what these mean. 

 

My setup is 

Ryzen 5 2600 

Colorful RTX 3070 Ultra White OC

32 GB (8x4GB) XPG 3000Mhz RAM 

Asrock B450 Steel Legend Motherboard 

Windows 11

 

Any help would be appreciated. 

Minidump.zip 461.14 kB · 0 downloads

Interesting one.

Can you check event viewer-> windows logs -> system? Any non information logs around the crash time? As those logs are easier to read

Have you cleared your CMOS?

Do you have the newest stable BIOS that supports that CPU?

[anarchinine]

18 hours ago, Frizz said:

Interesting one.

Can you check event viewer-> windows logs -> system? Any non information logs around the crash time? As those logs are easier to read

Have you cleared your CMOS?

Do you have the newest stable BIOS that supports that CPU?

Found this event - 

 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffb10feeacd4d0, 0xffffb10feeacd428, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d2b27329-5940-4eac-9db2-895d0cb624c7.

 

param1

0x00000139 (0x0000000000000003, 0xffffb10feeacd4d0, 0xffffb10feeacd428, 0x0000000000000000)

param2

C:\WINDOWS\MEMORY.DMP

param3

d2b27329-5940-4eac-9db2-895d0cb624c7

 

-----------------------------------------------------

The Razer Synapse Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 0 milliseconds: Run the configured recovery program.

 

param1

Razer Synapse Service

param2

1

param3

0

param4

3

param5

Run the configured recovery program

520061007A00650072002000530079006E006100700073006500200053006500720076006900630065000000

 

-----------------------------------------------------

 

The Razer Synapse error and the Memory dump occurred at 01:26:10 and 01:26:11 respectively, hence included both. 

 

Another Error log at 01:25:15 reads thus - 

 

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

BugcheckCode

313

BugcheckParameter1

0x3

BugcheckParameter2

0xffffb10feeacd4d0

BugcheckParameter3

0xffffb10feeacd428

BugcheckParameter4

0x0

SleepInProgress

0

PowerButtonTimestamp

0

BootAppStatus

0

Checkpoint

0

ConnectedStandbyInProgress

false

SystemSleepTransitionsToOn

0

CsEntryScenarioInstanceId

0

BugcheckInfoFromEFI

false

CheckpointStatus

0

CsEntryScenarioInstanceIdV2

0

LongPowerButtonPressDetected

false

[Frizz]

3 hours ago, anarchinine said:

Found this event - 

 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffb10feeacd4d0, 0xffffb10feeacd428, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d2b27329-5940-4eac-9db2-895d0cb624c7.

 

param1

0x00000139 (0x0000000000000003, 0xffffb10feeacd4d0, 0xffffb10feeacd428, 0x0000000000000000)

param2

C:\WINDOWS\MEMORY.DMP

param3

d2b27329-5940-4eac-9db2-895d0cb624c7

 

-----------------------------------------------------

The Razer Synapse Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 0 milliseconds: Run the configured recovery program.

 

param1

Razer Synapse Service

param2

1

param3

0

param4

3

param5

Run the configured recovery program

520061007A00650072002000530079006E006100700073006500200053006500720076006900630065000000

 

-----------------------------------------------------

 

The Razer Synapse error and the Memory dump occurred at 01:26:10 and 01:26:11 respectively, hence included both. 

 

Another Error log at 01:25:15 reads thus - 

 

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

 

BugcheckCode

313

BugcheckParameter1

0x3

BugcheckParameter2

0xffffb10feeacd4d0

BugcheckParameter3

0xffffb10feeacd428

BugcheckParameter4

0x0

SleepInProgress

0

PowerButtonTimestamp

0

BootAppStatus

0

Checkpoint

0

ConnectedStandbyInProgress

false

SystemSleepTransitionsToOn

0

CsEntryScenarioInstanceId

0

BugcheckInfoFromEFI

false

CheckpointStatus

0

CsEntryScenarioInstanceIdV2

0

LongPowerButtonPressDetected

false

The only thing clear there is razer synapse isn't working right.

 

(Assuming you did the CMOS clear and BIOS update already) Try uninstalling razer synapse on the off chance it is conflicting.

 

Next thing I would do is try DDU in safemode. Might have corrupted drivers.

Then make sure any overclocks on your GPU are removed. Let us know how all that goes

 

[anarchinine]

Figured it out after some trial and errors. As it turns out, I had turned on XMP profile to bump up the RAM to 3000Mhz from its base speeds of 2400MHz. This had been a rather simple change so it escaped my mind when I wrote the post. Since then I've read that using four DIMMs in a single motherboard on XMP can cause stability issues. Perhaps the fact that two of the RAMs were rated for a max 3200Mhz and others for 3000Mhz also led to some mismatch. 

 

Going deep into the rabbit hole of memory voltage configs suggested that I should bump up the voltage to 1.4 or 1.45V. Since I have never tinkered with voltages before (either RAM or GPU), I felt that I should just forego XMP. Having brought down speeds to 2400Mhz, the crashes have disappeared. I can play any AAA game with 100% load on the GPU, 100% memory utilization without any crashes. I have played upwards of 3 hours of Cyberpunk 2077, two hours of Far Cry 6, and other games for lesser durations without encountering any weirdness. (I am getting slight temporary artifacting in the player menu on Cyberpunk but nowhere else. Seems to be an issue specific to Cyberpunk 2077). 

 

All said, I am a bit sad about not being able to use XMP without messing with the voltages. I could remove two RAM sticks and run on 16GB instead of 32GB, but again, that would be leaving memory on the table (literally). On the whole though, the return to stable gaming is something I'd rather have than a few extra MHz.