English Community

  • 1
  • 2
  • 3
  • 4
Go to page

Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

I got my Yoga 9i Pro 2023 IRP8 (i7 13705h, 32GB, 1TB, RTX4050) one week ago. Since then, I have experienced multiple bugs and instability issues. I will post all of them here one by one to see if there is any solution.

 

Many times when I open Lenovo Vantage and check different items, I get BSoD. I had thought it was an Intel Driver Issues, until I checked the dump file and realised that it is a Lenovo Vantage issue. 

 

The forum does not allow me to upload a dump file here, so please see the analysis below by WINDbg.

 

Can someone please help me? This should not be happening to a brand new laptop.

 

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000004b8268634c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8035e6ba150, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1390

    Key  : Analysis.Elapsed.mSec
    Value: 15585

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_TcnPeripheral64!unknown_function

    Key  : Failure.Hash
    Value: {ba43bd4d-c8e9-9d9c-b808-55f45660118c}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: 4b8268634c

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8035e6ba150

FILE_IN_CAB:  070523-17953-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8035ed1c468: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 0000004b8268634c 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  LenovoVantage.

DPC_STACK_BASE:  FFFFFB804EC3FFB0

TRAP_FRAME:  fffffb804ec3e5f0 -- (.trap 0xfffffb804ec3e5f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff828f3ac06080 rbx=0000000000000000 rcx=0000004b82686000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8035e6ba150 rsp=fffffb804ec3e780 rbp=fffffb804ec3e940
 r8=000000000000fde9  r9=fffffb804ec3e870 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlpIsUtf8Process+0x50:
fffff803`5e6ba150 664439814c030000 cmp     word ptr [rcx+34Ch],r8w ds:0000004b`8268634c=04e4
Resetting default scope

STACK_TEXT:  
fffffb80`4ec3e4a8 fffff803`5e4442a9     : 00000000`0000000a 0000004b`8268634c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffb80`4ec3e4b0 fffff803`5e43f934     : 02030405`00000500 00000000`00010006 fffff231`e4dafa51 00000004`00000004 : nt!KiBugCheckDispatch+0x69
fffffb80`4ec3e5f0 fffff803`5e6ba150     : 00000000`00000000 fffff803`5e2ac5c7 ffffc481`39ad6180 00000000`00000000 : nt!KiPageFault+0x474
fffffb80`4ec3e780 fffff803`5e6b9ff0     : 00000000`00000000 fffffb80`4ec3e928 fffffb80`4ec3e7f0 fffff803`5e3f3c38 : nt!RtlpIsUtf8Process+0x50
fffffb80`4ec3e7c0 fffff803`5e3f1229     : 00000000`00000020 00000000`00000000 fffffb80`4ec3eacf ffff828f`464a2000 : nt!RtlAnsiCharToUnicodeChar+0x20
fffffb80`4ec3e810 fffff803`5e3f389d     : fffffb80`4ec3eacf fffffb80`4ec3eacf fffffb80`4ec3ed50 fffff803`5e23ea57 : nt!safecrt_mbtowc+0x39
fffffb80`4ec3e840 fffff803`5e3ef98c     : 00000000`00000007 00000000`00000000 fffffb80`4ec3ef60 00000000`00000000 : nt!woutput_l+0x5dd
fffffb80`4ec3ed20 fffff803`5e3ef901     : 00000000`00000010 00000000`00000011 00000000`00000000 00000000`00000000 : nt!vsnwprintf_l+0x7c
fffffb80`4ec3ed90 fffff803`a13c1d3f     : 00000000`00000010 00000000`00000002 fffffb80`4ec3ef30 00000000`00000002 : nt!vsnwprintf+0x11
fffffb80`4ec3edd0 00000000`00000010     : 00000000`00000002 fffffb80`4ec3ef30 00000000`00000002 00007d70`c1217618 : TcnPeripheral64+0x1d3f
fffffb80`4ec3edd8 00000000`00000002     : fffffb80`4ec3ef30 00000000`00000002 00007d70`c1217618 00000000`00000000 : 0x10
fffffb80`4ec3ede0 fffffb80`4ec3ef30     : 00000000`00000002 00007d70`c1217618 00000000`00000000 00000000`00000000 : 0x2
fffffb80`4ec3ede8 00000000`00000002     : 00007d70`c1217618 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffb80`4ec3ef30
fffffb80`4ec3edf0 00007d70`c1217618     : 00000000`00000000 00000000`00000000 00000000`00000000 00007d70`c1217618 : 0x2
fffffb80`4ec3edf8 00000000`00000000     : 00000000`00000000 00000000`00000000 00007d70`c1217618 00000000`00000000 : 0x00007d70`c1217618


SYMBOL_NAME:  TcnPeripheral64+1d3f

MODULE_NAME: TcnPeripheral64

IMAGE_NAME:  TcnPeripheral64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1d3f

FAILURE_BUCKET_ID:  AV_TcnPeripheral64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ba43bd4d-c8e9-9d9c-b808-55f45660118c}

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

0
0
Solution

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

@Jiraiya06  ,

You could try to import the registry I attached in this post if BSOD issue is fixed.

There would be a new version of driver to be released to fix this issue.

If you like to try. I could provide the beta for you to test. Or you could wait for new driver to be public released.

To install the test driver,

1) Download the driver from link below and extract to computer

https://www.dropbox.com/scl/fi/wrzkxi43g97w29razat1o/TCNDriver_20230719.zip?rlkey=5bwgngxeb5jee5tnrls1asr4j&dl=0

2) Go to window Settings-> Windows update->Recovery->Advanced Reboot, and select Reboot Now

3) When WINRE is booted, Go to troubleshooting->Advanced Options->StartUp settings and select Restart

4) Press Key 7 to allow windows to disable driver signature checking

5) Go to device manager

6) And select this driver and re-install the driver by locate the download file

7) double click smartdisplay-setup and it would reboot system automatically and check if system will still BSOD.

 

 

 

 

0
0

Was this solution helpful?

Your feedback helps us improve!
Replies

Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

Greetings, EvanTXZ!

Welcome to the Community!

Go to BIOS and load default settings by pressing Fn+F9, then go to Configuration tab and disable Intel(R) Virtualization Technology. Press Fn+F10 / F10 to save changes, and check if the error will appear.

If its still the same, uninstall Lenovo Vantage from Settings > Apps, as well as the System Interface Foundation. Reinstall Vantage to test further.

Regards,

Hector_Lenovo

   
We're here to help troubleshoot and investigate your issue, but know that you can always open a warranty service case here.
Get 10% Discount on Warranty & Services Upgrades Now!
Find original parts and upgrades on the Parts Lookup site.
Batteries, AC Adapters, Memory, Storage, Displays, Cables and much more.

Did someone help you today? Press the thumbs-up icon below to thank them!
If you find a post helpful and it answers your question, please click the "Accept Solution" button!

0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

May I know how your idenitfy it is from Vantage from crash dump analyze? Is it AV_TcnPeripheral64 could be located from your system? And what is the path?
0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

Hi, Hector, I will try that as a last resort. If I try this approach I will let you know how it goes. I am using Windows Subsystems for Android, and if I disable Intel VT I will not be able to use it anymore.

0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

Hi, hzfdbd @hzfdbd, thanks for noticing this and pointing it out. I think you have a point. It might not be Vantage code itself. However, I have done some digging and found that TcnPeripheral64.sys is part of the TCON board driver (apparently for colour management?) that is used in the display panel of Yoga Pro 9i.

All BDoS crushes currently are to do with this particular driver. But it seems like this is a very essential driver that cannot be deleted and has not been updated. I have attached all the screenshots below. Additionally, this driver can be found in Lenovo's support website for Yoga Pro 9i 2023 IRP8.

https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/yoga-series/yoga-pro-9-14irp8/downloads/ds561423-sunia-spb-peripheral-t-con-color-management-driver-for-windows-11-64-bit-yoga-pro-9-14irp8-lenovo-slim-pro-9-14irp8?category=Software%20and%20Utilities

 

Please see below for the driver INF file. (I cannot upload so I copied everything.)

EDIT: Actually I can. I made a zip file with all the driver files. Please see the attachments.

 

; Module Name: TcnPeripheral64.inf
; Install information file for SPB Peripheral Driver Frameworks
;
; Copyright (c) 2006-2023, Sunia Electronics Technology Limited
;
;---------------------------------------------------

[Version]
Signature="$WINDOWS NT$"
Class=System
ClassGuid={4d36e97d-e325-11ce-bfc1-08002be10318}
Provider=%ProviderString%
CatalogFile=TcnPeripheral64.cat
DriverVer = 02/07/2023,1.0.7.1

[SourceDisksNames]
1 = %DiskName%,,,""

[SourceDisksFiles]
TcnPeripheral64.sys  = 1,,

[DestinationDirs]
DefaultDestDir = 12
Drivers_Dir  = 12            ;%windir%\system32\drivers

;--------------------------------------
[Manufacturer]
%ProviderString%=SUNIA,NTamd64

[SUNIA.NTamd64]
%Peripheral.DeviceDesc_LTCN0001%=SPB_Device_Install, ACPI\LTCN0001
%Peripheral.DeviceDesc_LTCN0002%=SPB_Device_Install, ACPI\LTCN0002

[SPB_Device_Install.NT]
CopyFiles=Drivers_Dir

[SPB_Device_Install.NT.HW]
AddReg=SPB_AddReg_Inst

[SPB_AddReg_Inst]
; Set to 1 to connect the first interrupt resource found, 0 to leave disconnected
HKR,Settings,"ConnectInterrupt",0x00010001,0
HKR,"WDF","WdfDirectedPowerTransitionEnable",0x00010001,1

[SPB_Device_Install.NT.Services]
AddService = TcnPeripheral,%SPSVCINST_ASSOCSERVICE%, SPB_Service_Inst

[SPB_Service_Inst]
DisplayName    = %Peripheral.SVCDESC%
ServiceType    = 1               ; SERVICE_KERNEL_DRIVER
StartType      = 3               ; SERVICE_DEMAND_START
ErrorControl   = 1               ; SERVICE_ERROR_NORMAL
ServiceBinary  = %12%\TcnPeripheral64.sys

[Drivers_Dir]
TcnPeripheral64.sys

;--------------------------------------
[Strings]
ProviderString="Sunia Electronics"
DiskName = "Sunia SPB Peripheral Driver Installation Disk"
Peripheral.DeviceDesc_LTCN0001 = "Sunia SPB Peripheral Driver - LTCN0001"
Peripheral.DeviceDesc_LTCN0002 = "Sunia SPB Peripheral Driver - LTCN0002"
Peripheral.SVCDESC = "Sunia SPB Peripheral Service"
SPSVCINST_ASSOCSERVICE= 0x00000002

Screenshot 2023-07-06 134104.png Screenshot 2023-07-06 134300.png Screenshot 2023-07-06 134721.png Screenshot 2023-07-06 134903.png TcnPeripheral64.zip
0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

The vantage contains a driver which is from hardware scan.

And it caused BSOD before.

But it has been fixed.

Could you try if you run the below command and BSOD will still occured?

C:\ProgramData\Lenovo\Vantage\Addins\LenovoHardwareScanAddin\2.7.0.6\LDiagsLegacy\LenovoDiagnosticsCLI.exe --run-all

This will load hardware scan driver and see if it will cause the same BSOD

 

0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

Hi Hzfdbd,

I ran the command in CMD and it did not cause BSOD.

 

I also found another dump file that does not involve Vantage, but with the same TcnPeripheral64.sys mentioned in the dump file.

I have attached the file along with the one with Vantage in a zip file.

 

Also, please see below the analysis of the dump file without Vantage mentioned:

 

18: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 000000604913834c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8016d2ba150, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1483

    Key  : Analysis.Elapsed.mSec
    Value: 3241

    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: 327

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_TcnPeripheral64!unknown_function

    Key  : Failure.Hash
    Value: {ba43bd4d-c8e9-9d9c-b808-55f45660118c}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    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: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  a

BUGCHECK_P1: 604913834c

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8016d2ba150

FILE_IN_CAB:  070123-18156-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8016d91c468: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 000000604913834c 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

DPC_STACK_BASE:  FFFF808E1FDD7FB0

TRAP_FRAME:  ffff808e1fdd65f0 -- (.trap 0xffff808e1fdd65f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffac03dbac20c0 rbx=0000000000000000 rcx=0000006049138000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8016d2ba150 rsp=ffff808e1fdd6780 rbp=ffff808e1fdd6940
 r8=000000000000fde9  r9=ffff808e1fdd6870 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlpIsUtf8Process+0x50:
fffff801`6d2ba150 664439814c030000 cmp     word ptr [rcx+34Ch],r8w ds:00000060`4913834c=04e4
Resetting default scope

STACK_TEXT:  
ffff808e`1fdd64a8 fffff801`6d0442a9     : 00000000`0000000a 00000060`4913834c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff808e`1fdd64b0 fffff801`6d03f934     : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff808e`1fdd65f0 fffff801`6d2ba150     : ffff8801`51597180 fffff801`6ceac5c7 ffff8801`5084c180 00000000`00000000 : nt!KiPageFault+0x474
ffff808e`1fdd6780 fffff801`6d2b9ff0     : 00000000`00000008 00000000`00000000 ffff808e`1fdd67f0 fffff801`6cff3c38 : nt!RtlpIsUtf8Process+0x50
ffff808e`1fdd67c0 fffff801`6cff1229     : 00000000`00000020 00000000`000fffff ffff808e`1fdd6acf ffffac03`e76e1000 : nt!RtlAnsiCharToUnicodeChar+0x20
ffff808e`1fdd6810 fffff801`6cff389d     : ffff808e`1fdd6acf ffff808e`1fdd6acf ffff808e`1fdd6d50 fffff801`6ce3ea57 : nt!safecrt_mbtowc+0x39
ffff808e`1fdd6840 fffff801`6cfef98c     : 00000000`00000002 00000000`0000002a ffff808e`1fdd6f60 00000000`00000000 : nt!woutput_l+0x5dd
ffff808e`1fdd6d20 fffff801`6cfef901     : 00000000`00000010 00000000`00000011 fffff801`73151e80 fffff801`6cea410b : nt!vsnwprintf_l+0x7c
ffff808e`1fdd6d90 fffff801`6e021d3f     : ffffac03`e62b4d40 fffff801`73127b7a ffff8801`50fd1180 ffffac03`e7362080 : nt!vsnwprintf+0x11
ffff808e`1fdd6dd0 ffffac03`e62b4d40     : fffff801`73127b7a ffff8801`50fd1180 ffffac03`e7362080 000053fc`29d4dea8 : TcnPeripheral64+0x1d3f
ffff808e`1fdd6dd8 fffff801`73127b7a     : ffff8801`50fd1180 ffffac03`e7362080 000053fc`29d4dea8 00000000`00000000 : 0xffffac03`e62b4d40
ffff808e`1fdd6de0 fffff801`6e0223a8     : ffffac03`d0d0b010 fffff801`73128c02 fffff801`6e0240f0 00000000`00000010 : fvevol!FvepQueueWorkItem+0x16a
ffff808e`1fdd6e80 ffffac03`d0d0b010     : fffff801`73128c02 fffff801`6e0240f0 00000000`00000010 00000000`00000009 : TcnPeripheral64+0x23a8
ffff808e`1fdd6e88 fffff801`73128c02     : fffff801`6e0240f0 00000000`00000010 00000000`00000009 fffff801`73157400 : 0xffffac03`d0d0b010
ffff808e`1fdd6e90 ffffac03`00980000     : ffff808e`1fdd6f90 ffffac03`c8010000 fffff801`6cc00000 ffffac03`e762e4d0 : fvevol!FveLibCryptoPerfEventCallback+0x32
ffff808e`1fdd6ec0 ffff808e`1fdd6f90     : ffffac03`c8010000 fffff801`6cc00000 ffffac03`e762e4d0 ffffac03`c8010140 : 0xffffac03`00980000
ffff808e`1fdd6ec8 ffffac03`c8010000     : fffff801`6cc00000 ffffac03`e762e4d0 ffffac03`c8010140 00000000`00000000 : 0xffff808e`1fdd6f90
ffff808e`1fdd6ed0 fffff801`6cc00000     : ffffac03`e762e4d0 ffffac03`c8010140 00000000`00000000 00000000`00000000 : 0xffffac03`c8010000
ffff808e`1fdd6ed8 ffffac03`e762e4d0     : ffffac03`c8010140 00000000`00000000 00000000`00000000 fffff801`6ce94309 : nt!`_CmDeleteDeviceInterfaceRegKeyWorker'::`2'::HardwareProfilesKeyPrefix (nt+0x0)
ffff808e`1fdd6ee0 ffffac03`c8010140     : 00000000`00000000 00000000`00000000 fffff801`6ce94309 ffffac03`c8010380 : 0xffffac03`e762e4d0
ffff808e`1fdd6ee8 00000000`00000000     : 00000000`00000000 fffff801`6ce94309 ffffac03`c8010380 fffff801`7314eeff : 0xffffac03`c8010140


SYMBOL_NAME:  TcnPeripheral64+1d3f

MODULE_NAME: TcnPeripheral64

IMAGE_NAME:  TcnPeripheral64.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1d3f

FAILURE_BUCKET_ID:  AV_TcnPeripheral64!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ba43bd4d-c8e9-9d9c-b808-55f45660118c}

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

dmpYOGA9IPRO2023IRP8.zip
0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

I analyzed your dump, and do not find any module loaded is from Lenovo.

And this crash is caused by TcnPenripheral driver.

And may I some question below?

1) If vantage is not opened, would this BSOD occur?

2) And when vantage is opened, you do not change page and stay at home page, would this BSOD occur?

3) Do you notice if any special page would cause the BSOD? for example, smart settings.

3)And could you please provide the screenshot of task manager with name "LenovoVantage0(xxAddin).exe

4) If possible, could you export the windows system event log

5) If you disabled the androd system and disable hyper V, would this BSOD occur?

 

Vantage is a UWP, usually it would not cause BSOD and just cause a crash.

Did you enable performance booste ?

0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

Hi hzfdbd,

 

Thank you for your help!

I agree that it is most likely not caused by Vantage. I will try to disable Hyper V and see what happens. I will keep you updated.

Also, TcnPenripheral driver belongs to Sunia Electronics, which should be a supplier of Lenovo right? They made the TCON board of this Yoga 9 Pro laptop. How should I deal with this driver issue? Should I contact warranty?

 

To answer your questions: 

1) If vantage is not opened, would this BSOD occur?

- I tried delete the driver from device manager, and I have turned off the automatic start of Vantage. This does so far stopped BSOD. 

2) And when vantage is opened, you do not change the page and stay at the home page, would this BSOD occur?

BSOD does not happen on the home page. It only happens when I change pages. The last time, it happened when I clicked "battery".

3) Do you notice if any special page would cause the BSOD? for example, smart settings.

No, but it is usually when I change pages.

3)And could you please provide the screenshot of task manager with name "LenovoVantage0(xxAddin).exe

Please see the attached.

4) If possible, could you export the windows system event log

I will try and let you know.

5) If you disabled the androd system and disable hyper V, would this BSOD occur?

I will try this and let you know!

Screenshot 2023-07-06 203615.png
0
0

Re:Lenovo Vantage Frequently Crashes into BSoD on Yoga Pro 9i (2023 IRP8)

We have some functions that related to this driver.

And I attached the registry key to disable those functions.

Could you try to import the registry key and try to launch Vantage.

And let me know if you still see BSOD

DisableSEAddins.reg.txt
0
0
  • 1
  • 2
  • 3
  • 4
Go to page

Identify Your Device

OR

Don't want to provide your serial number? You can also Browse by product

Find your Device

Problem solved or need help? Click here.