BSOD During Online Gaming Session.

Hello Tenforums:

The BSOD happened during a few hour gaming session in GTA Online. The BSOD showed "KERNEL_SECURITY_CHECK_FAILURE" and then hung at 100% before I forced the machine to shut down after a lengthy wait. The only two leads are that I have are that there is (probably was by now) a windows 10 pro insider preview update pending to install during inactive hours. (Maybe it tried to initiate the install while in-game which went wrong?) The other thing is that the drivers for my Nvidia GTX 760 just updated. As of late, there have been a lot problems with their drivers, but I haven't been affected by any issues so far.



Thanks,

Quickdraw996.

Hi,

Look here & see if it is related to your problems: -

Runtimebroker.exe issues

I don't believe it is. Just curious though, what made you think of this? I glanced briefly at the dump and noticed that there were many mentions of memory corruption.

Also, out of habit, I ran chkdsk /scan in an elevated command prompt and saw this:

Code:

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Local Disk.


Stage 1: Examining basic file system structure ...
  648448 file records processed.
File verification completed.
  10084 large file records processed.
  0 bad file records processed.


Stage 2: Examining file name linkage ...
    Found corrupt basic file structure for "\Boot\Fonts\segmono_boot.ttf <0x5,0x4029>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\bootvhd.dll <0x4,0x402b>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\cs-CZ\memtest.exe.mui <0x4,0x4030>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\da-DK\memtest.exe.mui <0x5,0x4031>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\de-DE\memtest.exe.mui <0x5,0x4033>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\el-GR\memtest.exe.mui <0x5,0x4034>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\en-US\bootmgr.exe.mui <0x4,0x4037>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\en-US\memtest.exe.mui <0x4,0x4038>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\es-ES\memtest.exe.mui <0x4,0x4039>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\fi-FI\memtest.exe.mui <0x4,0x403a>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\fr-FR\memtest.exe.mui <0x4,0x403b>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\hu-HU\memtest.exe.mui <0x4,0x403c>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\it-IT\memtest.exe.mui <0x4,0x403d>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\ja-JP\memtest.exe.mui <0x4,0x403e>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\ko-KR\memtest.exe.mui <0x4,0x403f>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\memtest.exe <0x4,0x4041>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\nb-NO\memtest.exe.mui <0x4,0x4042>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\nl-NL\memtest.exe.mui <0x4,0x4043>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\pl-PL\memtest.exe.mui <0x4,0x4044>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\pt-BR\memtest.exe.mui <0x4,0x4045>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\pt-PT\memtest.exe.mui <0x4,0x4046>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\qps-ploc\memtest.exe.mui <0x4,0x4047>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\ru-RU\memtest.exe.mui <0x4,0x4048>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\sr-Latn-CS\memtest.exe.mui <0x4,0x4049>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\sv-SE\memtest.exe.mui <0x4,0x404a>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\tr-TR\memtest.exe.mui <0x4,0x404b>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\zh-CN\memtest.exe.mui <0x4,0x404c>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\zh-HK\memtest.exe.mui <0x4,0x404d>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\zh-TW\memtest.exe.mui <0x4,0x404e>"
        ... repaired online.
    Found corrupt basic file structure for "\bootmgr <0x4,0x404f>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\Fonts\segoen_slboot.ttf <0x4,0x4050>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\Fonts\segoe_slboot.ttf <0x5,0x40b1>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\Fonts\wgl4_boot.ttf <0x4,0x40bb>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\Resources\bootres.dll <0x4,0x40be>"
        ... repaired online.
    Found corrupt basic file structure for "\Boot\Resources\en-US\bootres.dll.mui <0x4,0x40cc>"
        ... repaired online.
  775134 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  63344 data files processed.
CHKDSK is verifying Usn Journal...
  41376608 USN bytes processed.
Usn Journal verification completed.
Windows has found problems and they were all fixed online.
No further action is required.


 975837374 KB total disk space.
 342349476 KB in 398357 files.
    201984 KB in 63345 indexes.
         0 KB in bad sectors.
    788938 KB in use by the system.
     65536 KB occupied by the log file.
 632496976 KB available on disk.


      4096 bytes in each allocation unit.
 243959343 total allocation units on disk.
 158124244 allocation units available on disk.


C:\WINDOWS\system32>

What is: Found corrupt basic file structure for "\x\y\z.abc <0x?, 0x????>"?
I have personally never seen (probably seen but not actually noticed) this before.

Edit: Some of this may be due to the fact that I had to force the system to shut down after it hung at 100% at the BSOD screen.

It scanned my c: drive. "c:\boot" is a directory, but only shows if you show hidden files and protected operating system files. I also don't have any other drives besides my HDD formatted in NTFS. So far this has been a one off BSOD, but I want to stem it now before it (possibly) becomes a bigger problem. What utility do you recommend to check for driver problems?

axe0 said:

That directory shows in my Windows Explorer when I have hidden files enabled, but it doesn't contain anything. Show protected operating system files doesn't show more. This is conflicting with what I said earlier, but I didn't quite specify properly what I meant, though it isn't relevant to explain it.

I don't recommend any utility, a 1time BSOD is resolved by Windows so you would have to do nothing but a proper reboot after the BSOD.

I am not quite sure, but on system there are a bunch of folders named as if they are referring to language-country i.e. en-us.
Anyways, I guess that's it, unless this happens again. I know that the benefit will be marginal or even nonexistent, but I want to know what caused it. I am starting to suspect the Nvidia driver update that installed in the last twenty four to forty eight hours.

Again thanks. Now I get to sleep for three ish hours before I start my day. YAY! :)

axe0 said:

There are calls made to a Xbox driver, these drivers can be the cause unless you didn't use a Xbox driver while playing games.

Code:

0: kd> k
 # Child-SP          RetAddr           Call Site
00 fffff801`ff5d7568 fffff801`fdd57629 nt!KeBugCheckEx
01 fffff801`ff5d7570 fffff801`fdd57990 nt!KiBugCheckDispatch+0x69
02 fffff801`ff5d76b0 fffff801`fdd56973 nt!KiFastFailDispatch+0xd0
03 fffff801`ff5d7890 fffff803`1c551766 nt!KiRaiseSecurityCheckFailure+0xf3
04 fffff801`ff5d7a20 fffff803`1c553504 dc1_controller!DccRemoveRequestQueue+0x7e
05 fffff801`ff5d7a50 fffff803`1c553d77 dc1_controller!DccIsoQueueReadRequests+0x48
06 fffff801`ff5d7b50 fffff803`1960bd58 dc1_controller!DccIsoTimerFunc+0x57
07 fffff801`ff5d7b80 fffff803`1960bc5f Wdf01000!FxTimer::TimerHandler+0x84 [d:\rs1\minkernel\wdf\framework\shared\core\fxtimer.cpp @ 324]
08 fffff801`ff5d7bc0 fffff801`fdc55454 Wdf01000!FxTimer::_FxTimerDpcThunk+0xef [d:\rs1\minkernel\wdf\framework\shared\core\fxtimer.cpp @ 372]
09 fffff801`ff5d7c00 fffff801`fdc56470 nt!KiProcessExpiredTimerList+0x254
0a fffff801`ff5d7cf0 fffff801`fdc562c5 nt!KiExpireTimerTable+0x110
0b fffff801`ff5d7d90 fffff801`fdc5039a nt!KiTimerExpiration+0xf5
0c fffff801`ff5d7e40 fffff801`fdd514f5 nt!KiRetireDpcList+0x1da
0d fffff801`ff5d7fb0 fffff801`fdd51300 nt!KxRetireDpcList+0x5
0e ffffdd80`9af59c00 00000000`00000000 nt!KiDispatchInterruptContinue

I was using my Xbox One controller, so that seems very plausible.