Question BSOD while playing Rocket League

[RaduTheMan]

Hello. I had a BSOD while I was playing Rocket League: KMODE_EXCEPTION_NOT_HANDLED. I also had Discord opened with a stream. I suspect that maybe it's something with the cpu driver, but I am not sure.
Can you guys help me interpret this dump file?

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\092620-12500-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80457200000 PsLoadedModuleList = 0xfffff80457e2a310
Debug session time: Sat Sep 26 23:26:33.171 2020 (UTC + 3:00)
System Uptime: 3 days 23:40:07.088
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804575f3ea0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc40e2481ac80=000000000000001e
6: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff80466c74f0a, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000000000000003f, Parameter 1 of the exception

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4483

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-UB71BSI

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 43819

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

Key : Analysis.System
Value: CreateObject

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


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff80466c74f0a

BUGCHECK_P3: 0

BUGCHECK_P4: 3f

EXCEPTION_PARAMETER2: 000000000000003f

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffc40e2481ac78 fffff8045764e5b9 : 000000000000001e ffffffff80000003 fffff80466c74f0a 0000000000000000 : nt!KeBugCheckEx
ffffc40e2481ac80 fffff80457605fac : ffffc40e2481b620 ffffc40e2481b8e0 ffffc40e2481b918 ffffc40e2481ba10 : nt!KiDispatchException+0x1caa59
ffffc40e2481b340 fffff804575ff916 : 0000000000000000 00000000000001b0 ffffda0194c84340 ffffb40835ab1040 : nt!KiExceptionDispatch+0x12c
ffffc40e2481b520 fffff80466c74f0b : fffff80325840000 0000000000000001 fffff804659c79cc ffffda0194c79180 : nt!KiBreakpointTrap+0x316
ffffc40e2481b6b0 fffff80325840000 : 0000000000000001 fffff804659c79cc ffffda0194c79180 0000000000000001 : rt640x64+0x84f0b
ffffc40e2481b6b8 0000000000000001 : fffff804659c79cc ffffda0194c79180 0000000000000001 0000000000000008 : 0xfffff80325840000 ffffc40e2481b6c0 fffff804659c79cc : ffffda0194c79180 0000000000000001 0000000000000008 0000000000000000 : 0x1 ffffc40e2481b6c8 ffffda0194c79180 : 0000000000000001 0000000000000008 0000000000000000 01fff80465b7d78a : vgk+0x1879cc ffffc40e2481b6d0 0000000000000001 : 0000000000000008 0000000000000000 01fff80465b7d78a ffffffda0194f620 : 0xffffda0194c79180
ffffc40e2481b6d8 0000000000000008 : 0000000000000000 01fff80465b7d78a ffffffda0194f620 0000000000000001 : 0x1
ffffc40e2481b6e0 0000000000000000 : 01fff80465b7d78a ffffffda0194f620 0000000000000001 0000000000000000 : 0x8


SYMBOL_NAME: rt640x64+84f0a

MODULE_NAME: rt640x64

IMAGE_NAME: rt640x64.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 84f0a

FAILURE_BUCKET_ID: 0x1E_80000003_rt640x64!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {12149e68-e4c3-d591-0f4f-f6aa2d6a193b}

Followup: MachineOwner
---------

 

[gardenman]

Hi, these lines show the likely cause:

Spoiler

MODULE_NAME: rt640x64
IMAGE_NAME: rt640x64.sys

Update the rt640x64.sys driver. My description for that file is:

Realtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/

So look for an update there, or better yet, look for an update on your motherboard's website.

After updating, if you have additional crashes, upload the minidump files from C:\Windows\minidump to a file sharing service like Google Drive or MS OneDrive and provide a link to them here.

 

[RaduTheMan]

I've also asked on another forum, and one guy also said about the realtek driver.However, he also mentioned that Riot Vanguard may conflict with Easy Anticheat and cause BSOD's.
I already have the latest version of the realtek driver, so I will try to update Riot Vanguard or uninstall it if no new version is available and see how it goes.
Thank you for your help.

 

[Colif]

Valorant is mentioned in the dump text above so i can see why its blamed

ffffc40e2481b6c8 ffffda0194c79180 : 0000000000000001 0000000000000008 0000000000000000 01fff80465b7d78a : vgk+0x1879cc

Realtek was the victim, not the cause...

 

[PC Tailor]

Valorant is mentioned in the dump text above so i can see why its blamed

Realtek was the victim, not the cause...

When is Valorant NOT the cause? 😉