PC randomly BSODs with Access Violation error
I only have the dump file
C:\Windows\System32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
92 Replies
You still getting bsod ?
whats your ingame name with tag ?
once a day
mia#2711
oay
@junimo when you have free time :633658072245469195:
You gotta wait for the dev when she have free time she might look
usually I just disable vanguard when it happens, I did restore my PC from a veem backup (full system image copy) which was when I started to notice having this issue.
I have Docker Desktop (Virtualization enabled) + Core isolation Memory Intergity enabled + Secure Boot
Disable vanguard ? You mean you play without vanguard ?
uh no, when I crash I just kill the service via the quick menu
Okay
i rarely play so i don't really care if the service is not running (especially if its crashing my PC), I'd just reboot my PC to re-open it
yea best thing you do wait for dev when she got free time she will let you know
Upload the last dump file have been created
Upload it to google drive
And keep the link of upload ready
i think they can use this one?
This work aswell
Is it the newest?
two from today
Perfect
Now we wait for dev
@Mia Do you have an antivirus? Like AVG?
no
just windows one
You sure?
yup
There wouldn't be any software that would potentially be blocking Vanguard?
hmm, there shouldn't be any, i figured it might be the memory Intergity
Please ZIP and send your Vanguard logs here
its not running, let me check where its stored
Zip.
but I guess that's fine
w.e works for them lol
@Mia Have you tried reinstalling Vanguard?
,.
when does it happen? does it happen when you are not playing valorant
when I dont play valorant at all
I could just be idling with discord/chrome etc open and one of them will trigger it sometimes
I haven't tried a fresh reinstall yet but it started when I did a full system restore from a image.
i can play valorant fine without any issues as well
do you have a intel 13/14th gen by chance
Intel(R) Core(TM) i9-14900HX, 14th gen yeah
I assume you're pointing to https://support-valorant.riotgames.com/hc/en-us/articles/30677093498515-vgk-sys-Error-Troubleshooting-13th-and-14th-Generation-Intel-CPUs
VALORANT Support
vgk.sys Error Troubleshooting (13th and 14th Generation Intel CPUs)
Hardware Recall
If the below steps don't work, this may be a hardware issue that can only be resolved by contacting Intel for a replacement CPU. Check Intel's Site for more details.
If you're expe...
Yup, have you done those steps
doing them now
Open advanced tuning rq
It says OC is disabled :val_SusgeNoted:
Core
Scroll down rq
Yeah those on the left, does it let you lower it
Go down by 2 if you can
nope, MSI locks those :p
(no under/over volting)
Hmm, then alternatively you can check if you have option to lower from bios
can give that a try, any clue why its always the vanguard driver?
wondering if i'll still see issues if i remove vanguard/valorant/league
It’s the issue with the CPU in general
does vanguard happen to trigger it more then
maybe*
wouldn't be shocked if its a CPU issue, usually closing vanguard leaves it without issues, think I only really had 5 "BSODs" this month so im not super concerned
other games such as siege and warframe seem to work ok
the crash dumps show a lot of data corruption that makes me think it's a fried cpu
hmmm
I wouldn't jump to CPU right off the bat. Normally with weird issues like this it's always RAM. I had some wacky things when I had bad RAM.
I would like to try disabling virtualization first.
and then also running a memory test
Open cmd as admin
Enter
press the windows key and search for
when you open it press restart now.
@Mia hey could you enable complete memory dump and try to reproduce the crash again? the minidump doesn't contian enough information for us to diagnose this unfortunately
:Nodd:
I set this, I used to have it on. Guess it wasn't persistent.
No errors reported, I've ran a bunch of memory/cpu tests before to help debug some other issues i had with bad thermal paste.
CPU could be fried as the temps have been hot lately until I got it fixed
this issue happens like once in a while so I'll come back if I see it again but i'm glad it doesn't completely impact me
when you crash again please provide the memory dump files
Hopefully this time the complete memory dump, will show something pointing to a cause
do you need the whole 30GB dump file or what windbg gives when you run
!analyze -v?
i'm disabling hyperv since I can move my docker workloads to a server instead.Can’t even upload 30gb to any free cloud storage :val_HUH:
just asking since the errors seem to point to hyperv and some memory access
@junimo any idea? I got another BSOD for "unverified driver signature" or something but no dump was made for it
will likely reinstall valorant see if that fixes it
i think this related to ethernet adapter
or wifi adapter
i remember my realtek one did cause some issues with valorant before in the past it would just kill the adapter entirely and I would have to restart the PC...
Killer(TM) Wi-Fi 7 BE1750x 320MHz is disabled (wifi)
I use Realtek Gaming 2.5GbE Family Controller (Cable)
for now I've completely deleted riot stuff to see if it continues
the analysis should be fine
can you run verifier on the all drivers
@junimo has the vanguard logs provided anything useful? or any idea? it would be helpful to know if this definitely is not a vanguard issue. or any clue that may point to a conflict with another service
i did last night and no issues
can you send the log
from that
i uninstall vanguard so 🥹
is it worth running again
that's completely up to you
gonna wait on junimo, but i uninstalled everything so im gonna see if it happens in the next few days
battle eye seems to work fine etc
you're on 14th gen right?
@Mia
ok yeah
you're out of luck, your cpu is fried
only thing you can do is get a replacement CPU by RMAing your CPU, but you'll still get bsods after a few months of usage
its not fixable, even the updated microcode wont fix it. Only thing it can do is make it last a bit longer
and if you're already facing bsods, it wont do anything because the damage is already done
honestly, I recommend just getting a new CPU which isnt intel 13th or 14th gen. It's just not worth dealing with the whole RMA process and having to do it every few months
yeah I plan to replace and not get a 13th/14th gen CPU
but can you let me know how came to the conclusion its fried?
figured so, high temps 😔
your bsod dump is pretty much nonsense which is a symptom of that instability
thanks
should've went with an i5 lmao
nah
would've happened there too
it affects all cpus under 13th-14th gen
what CPU should i go for
I would look for a AMD cpu, but if you're into intel then the latest ultra 200x processors are good too (just worse perf than 14th gen)
yeah i previously used AMD
i thought intel would be better for the perf on single threaded
my next build will probs go AMD and not have high temps XD
intel is the worst in this part
intel is work station
it is, but intel is just doing bad decisions upon bad decisions in the past few years
Amd for gamingg
like 10% price hike on 13/14th gen cpus, then the whole 13/14th gen instability, then dropping support for igpu updates from 10-14th gen
Sorry for interrupting. There is guy with issue we cannot find fix for wanna take look ?
im hoping they dont screw up with the next gen (nova lake), they are cooking big from the leaks. Chip has 52 cores
ping me there pls
yeah I don't know how they fucked these gens so much. AMD really has taken advantage of their stupidness