Question I'm experiencing crashes and BSODs on my laptop ?

[fseveco]

Dear community,

Laptop model: Lenovo Legion Y540

I've been experiencing crashes (it stutters, then it restarts) and BSOD's on my laptop.

Apparently it's caused by Riot Vanguard application, but I'm not 100% sure.

Im attaching a dump file from C / Windows / Memory.dmp in hopes someone can spot something.


So far what I've tried:

• Reinstalled League of Legends & Riot Vanguard completely
• Reinstalled NVIDIA graphics drivers (downgraded from latest version to a bit older version)
• Cleaned my laptop with various licensed third party programs: Free Windows Registry Repair, Avast Antivirus, Malwarebytes, Spybot Search &Destroy
• Cleaned temporary files from start menu, such as: temp, %temp%, prefetch
• Changed my battery plan (to default)
• Checked for viruses and malwares via third party programs (Avast, Malwarebytes, Adcleaner - none have been found)
• Checked the state of my GPU, CPU, RAM and SSD's (they are all fine, no errors upon checkup).
• Checked if my SSD's are full (they're not, they have around 30% remaining free space each)
• Tried repairing LoL & Vanguard client (it stated that there was nothing to repair)

Spoiler: Memory Dump File

************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToV8JsProvider : false

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.000 seconds
----> Repository : LocalInstalled, Enabled: true, Packages count: 29
----> Repository : UserExtensions, Enabled: true, Packages count: 0

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


Loading Dump File [C:\Users\Vedran\Desktop\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

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
Kernel base = 0xfffff800`47200000 PsLoadedModuleList = 0xfffff800`47e2a310
Debug session time: Fri May 31 03:56:41.928 2024 (UTC + 2:00)
System Uptime: 0 days 12:26:17.706
Loading Kernel Symbols
...............................................................
................Page 805ddd not present in the dump file. Type ".hh dbgerr004" for details
................................................
................................................................
................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000b3`f3332018). Type ".hh dbgerr001" for details
Loading unloaded module list
.................................
For analysis of this file, run !analyze -v
9: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8006614ca86, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

Unable to load image \??\C:\Program Files\Riot Vanguard\vgk.sys, Win32 error 0n2
Page 184f1c not present in the dump file. Type ".hh dbgerr004" for details
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4984

Key : Analysis.Elapsed.mSec
Value: 9759

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.KiBugCheckData
Value: 0x1e

Key : Bugcheck.Code.LegacyAPI
Value: 0x1e

Key : Failure.Bucket
Value: AV_R_vgk!unknown_function

Key : Failure.Hash
Value: {b93bf423-3535-1218-531c-8c08e172e67f}

Key : Hypervisor.Enlightenments.Value
Value: 0

Key : Hypervisor.Enlightenments.ValueHex
Value: 0

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 0

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 0

Key : Hypervisor.Flags.Phase0InitDone
Value: 0

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 0

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 131072

Key : Hypervisor.Flags.ValueHex
Value: 20000

Key : Hypervisor.Flags.VpAssistPage
Value: 0

Key : Hypervisor.Flags.VsmAvailable
Value: 0

Key : Hypervisor.RootFlags.AccessStats
Value: 0

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 0

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0

Key : Hypervisor.RootFlags.MceEnlightened
Value: 0

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0

Key : Hypervisor.RootFlags.Value
Value: 0

Key : Hypervisor.RootFlags.ValueHex
Value: 0

Key : SecureKernel.HalpHvciEnabled
Value: 0

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8006614ca86

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB: MEMORY.DMP

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: chrome.exe

TRAP_FRAME: fffffffffffbfd7d -- (.trap 0xfffffffffffbfd7d)
Unable to read trap frame at ffffffff`fffbfd7d

STACK_TEXT:
fffffe84`e678e968 fffff800`47630105 : 00000000`0000001e ffffffff`c0000005 fffff800`6614ca86 00000000`00000000 : nt!KeBugCheckEx
fffffe84`e678e970 fffff800`476066ac : dabea5b7`64863620 cbf29b1b`1f20876a ffffffff`fffbfd7d 00003efb`cdf90fd0 : nt!KiDispatchException+0x1de8e5
fffffe84`e678f030 fffff800`476023e0 : 00000000`00000014 00000000`00ec0000 ffffc07f`2b81fc1f 00008250`c66c40a6 : nt!KiExceptionDispatch+0x12c
fffffe84`e678f210 fffff800`6614ca86 : ffff990e`d94f7400 33bb6a08`acff6ab8 fffff800`47efc440 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffffe84`e678f3a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vgk+0x117ca86


SYMBOL_NAME: vgk+117ca86

MODULE_NAME: vgk

IMAGE_NAME: vgk.sys

IMAGE_VERSION: 1.14.8.20

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 117ca86

FAILURE_BUCKET_ID: AV_R_vgk!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b93bf423-3535-1218-531c-8c08e172e67f}

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

 

[Colif]

Apparently it's caused by Riot Vanguard application, but I'm not 100% sure.

IMAGE_NAME: vgk.sys

Yep. it is the cause it would appear. I can't see how to update it so in case its actually tripping over something else,
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 . . .
   

Problem with Vanguard is it thinks it owns your PC.

Is it crashing while playing the games? it seems you were just using chrome when it crashed last time... chrome was victim.

Vanguard shouldn't be running if you not playing games. I did say it thinks it owns your PC but it should only run when playing the game, not all the time. It has too much access as far as I am concerned, more a virus that anything.

 

[fseveco]

Yep. it is the cause it would appear. I can't see how to update it so in case its actually tripping over something else,
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 . . .

Problem with Vanguard is it thinks it owns your PC.

Is it crashing while playing the games? it seems you were just using chrome when it crashed last time... chrome was victim.

Vanguard shouldn't be running if you not playing games. I did say it thinks it owns your PC but it should only run when playing the game, not all the time. It has too much access as far as I am concerned, more a virus that anything.

Thank you very much.

I've followed your instructions and uploaded the mini dump file to one drive: LINK

It crashed few times in the game, but it's not consistent and is very random.

Well I'm not sure when it is running, I only know it's running for sure when I'm playing the game.

 

[Colif]

have you tried automatic update on here?
https://pcsupport.lenovo.com/us/en/...oks/legion-series/legion-y540-15irh/downloads
there is a new BIOS update that could help.

other drivers could as well.

that one was nothing new

File: 053124-21968-01.dmp (May 31 2024 - 11:56:41)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)]
*** WARNING: Unable to verify timestamp for vgk.sys
Probably caused by: memory_corruption (Process: chrome.exe)
Uptime: 0 Day(s), 12 Hour(s), 26 Min(s), and 17 Sec(s)

report - mostly for me

 

[fseveco]

Thing is, I'm using a bit older BIOS cause the newer ones reported higher spikes in laptop temperatures.

Is there any other way than to NOT update BIOS to latest version?

 

[Colif]

We can try, did you look to see if any newer drivers apart from BIOS showing?

 

[fseveco]

We can try, did you look to see if any newer drivers apart from BIOS showing?

The only thing that's new is the Lenovo Vantage service, everything else is last updated on 2022 and that is the latest version for all of my drivers.

However, Lenovo Vantage isn't really a vital program for a laptop as far as I know, but if you want I can update that.

 

[Colif]

Try removing Avast and see if it changes anything.

How did you check ram?
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

If we can't find anything wrong with PC and it keeps blaming the same Driver, have to take its word for it.