Share via

Random computer freezing - Lenovo Legion T5 28IMB05

Anonymous
2024-01-19T04:10:06+00:00

Hello,

I have a Lenovo Legion tower desktop computer with the following specs:

CPU - Intel i5-10400

RAM - DDR4 16GB 2666
GPU - NVIDIA RTX 1660 SUPER

When playing games or even at idle on Google chrome, the computer will randomly fully freeze (once a day), audio will cut out, and all applications will cease to run, followed by a long wait and automatic shutoff (usually I power off manually). Could someone please take a look at the minidump and see what the error might be? I think it may be related to the RAM, or to NVIDIA drivers, but I'm not sure.

It seems to be very similar to this previous issue, though the solution has since been deleted - https://answers.microsoft.com/en-us/windows/forum/all/computer-crashing/d8b26684-0ddf-4fd4-844b-8a056870ffba

Here is the latest crash minidump - https://drive.google.com/file/d/1d1afdjd178ALmog_BmyVTlyP_V83lGhE/view?usp=drive_linkMinidump in plaintext below. Thank you!!

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

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8013851d340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging 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: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x20b809, File: 0x20b875 - C:\ProgramData\Dbg\sym\BTHport.sys\C546C699202000\BTHport.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2530

    Key  : Analysis.Elapsed.mSec
    Value: 3483

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    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: 0x133_ISR_ACPI!ACPIReadGpeStatusRegister

    Key  : Failure.Hash
    Value: {9524459d-2f22-efe5-b0c9-f824c586f42c}

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8013851d340

BUGCHECK_P4: 0

FILE_IN_CAB:  011824-7296-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  TM5.exe

STACK_TEXT:  
fffff801`39c90988 fffff801`37a12bb9     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`3851d340 : nt!KeBugCheckEx
fffff801`39c90990 fffff801`37a12421     : 00000702`36270a1c ffffc081`ccb05000 00000000`000298a3 00000000`00000000 : nt!KeAccumulateTicks+0x239
fffff801`39c909f0 fffff801`37a104b1     : 00000000`00000000 ffffaa81`885f3e00 fffff801`32ff4180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
fffff801`39c90ba0 fffff801`37a0feda     : fffff801`38460070 ffffaa81`885f3e70 ffffaa81`885f3e70 00000000`0000000b : nt!KeClockInterruptNotify+0xc1
fffff801`39c90c40 fffff801`37b24b2c     : 00000006`30c021d3 fffff801`3850d5b0 fffff801`3850d660 fffff801`37a0bfc3 : nt!HalpTimerClockInterrupt+0x10a
fffff801`39c90c70 fffff801`37c18cba     : fffff801`39c90d80 fffff801`3850d5b0 fffff801`38460140 ffffc081`c7697000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff801`39c90cb0 fffff801`37c19567     : 00000702`36252853 00000000`00000001 ffffc081`c7697000 ffffaa81`8ba50780 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`39c90d00 fffff801`37ba183a     : fffff801`37b9e1d9 00000000`00000008 ffffc081`be4f5000 00000000`00000001 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`39c90e98 fffff801`37b9e1d9     : 00000000`00000008 ffffc081`be4f5000 00000000`00000001 00000000`00000002 : nt!HalpAcpiPmRegisterReadPort+0xa
fffff801`39c90ea0 fffff801`3a368a91     : 00000000`00000008 fffff801`39c90fa8 00000000`00000008 fffff801`39c90f50 : nt!HalpAcpiPmRegisterRead+0x39
fffff801`39c90ed0 fffff801`3a333d80     : 00000000`00000000 ffffaa81`885f3dc0 000006ae`fd407102 fffff801`39c893f0 : ACPI!ACPIReadGpeStatusRegister+0x85
fffff801`39c90f10 fffff801`37b24bfd     : ffffaa81`885f3dc0 ffffaa81`8ba50830 ffffaa81`885f3e70 ffffaa81`885f3dc0 : ACPI!ACPIInterruptServiceRoutine+0x50
fffff801`39c90f50 fffff801`37c18a3f     : fffff801`39c893f0 ffffaa81`885f3dc0 ffffc081`c756d030 00000702`3625873b : nt!KiCallInterruptServiceRoutine+0x16d
fffff801`39c90f90 fffff801`37c18d07     : 00000000`00000000 ffffc081`c750e4b0 00000000`00000001 fffff801`5d21b4e6 : nt!KiInterruptSubDispatch+0x11f
fffff801`39c89370 fffff801`50f33199     : 00000000`00000000 fffff801`3854c250 00000000`00000000 fffff801`37b2af5a : nt!KiInterruptDispatch+0x37
fffff801`39c89500 fffff801`5db51cc5     : ffffc081`c756d030 00000000`00000000 ffffc081`c756d030 e6f80000`e9700000 : dxgkrnl!DxgNotifyDpcCB+0x79
fffff801`39c895e0 ffffc081`c756d030     : 00000000`00000000 ffffc081`c756d030 e6f80000`e9700000 fffff801`5db51c4a : nvlddmkm+0x9e1cc5
fffff801`39c895e8 00000000`00000000     : ffffc081`c756d030 e6f80000`e9700000 fffff801`5db51c4a ffffc081`c7697000 : 0xffffc081`c756d030

SYMBOL_NAME:  ACPI!ACPIReadGpeStatusRegister+85

MODULE_NAME: ACPI

IMAGE_NAME:  ACPI.sys

IMAGE_VERSION:  10.0.22621.3061

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  85

FAILURE_BUCKET_ID:  0x133_ISR_ACPI!ACPIReadGpeStatusRegister

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9524459d-2f22-efe5-b0c9-f824c586f42c}

Followup:     MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2024-05-30T00:12:03+00:00

    Same problem as well :( I had this problem for months already

    0 comments No comments
  2. Anonymous
    2024-03-26T16:44:49+00:00

    I noticed mine would freeze if didn't have the rgb cables plugged in.. if one wasn't plugged in the controls for lightning will not show up in app unless all are hooked up too

    0 comments No comments
  3. Anonymous
    2024-02-10T17:36:36+00:00

    I have the same problem .. any solution!

    Legion 5 i7 11800H Rtx 3060

    0 comments No comments
  4. Anonymous
    2024-01-21T23:45:42+00:00

    Hello,

    I entered the BIOS (Lenovo motherboard) using F1 and there were no ACPI settings. I made sure to check every page and subpage. The Lenovo BIOS is quite sparse with few options. Any other ideas?

    Thank you!

    0 comments No comments
  5. Sakiko 38,625 Reputation points Independent Advisor
    2024-01-19T05:05:01+00:00

    Hello, I'm A&K, here to help.

    Based on the information you provided, it seems to be an issue with power management. Please try to press DEL or F12 to enter the BIOS menu when booting up (it may be other buttons, depending on the computer, please refer to the device manual for details). Find the ACPI option and try it on and off separately.

    0 comments No comments