Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

English Community

ThinkPad NotebooksThinkPad: T400 / T500 and newer T series Laptops
All Forum Topics
Options

11 Posts

07-12-2021

Norway

11 Signins

55 Page Views

  • Posts: 11
  • Registered: ‎07-12-2021
  • Location: Norway
  • Views: 55
  • Message 1 of 16

KB5004945 thinkpad T470s BSOD

2021-07-12, 20:34 PM

Hi. Got, BSOD whea uncorrectable error, after KB5004945 windows 10 update it looks like. Just after I got the update the troubles came non stop. See that I`m not the only one with problems. So did a reinstall to before the update and no problems. So what should I do regarding Windows update, I`m scared !!!!!!!!!!!!!!!!!!!!

Okey. so 10 minutes after writing I`m scared, in the above sentence, it came back after working, for a couple of days. Took the dump file to Windbg, any expert advice on this. Had two crashes just now, pulled the hdmi cable connected to the tv just for fun, stopped the crashes in this writing moment at least. So maybe something with the hdmi.....

Everything is up to date with Lenovo Vantage. Did run a check on the memory two days ago, all good.

 


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


Loading Dump File [C:\Users\xlklx\OneDrive\Skrivebord\071221-6453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`67600000 PsLoadedModuleList = 0xfffff801`6822a230
Debug session time: Mon Jul 12 23:11:50.952 2021 (UTC + 2:00)
System Uptime: 2 days 11:04:56.470
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....................................
For analysis of this file, run !analyze -v
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffd00de3d51028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000008117a, Low order 32-bits of the MCi_STATUS value.

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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 6

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on LENOVO

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 260

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd00de3d51028

BUGCHECK_P3: be000000

BUGCHECK_P4: 8117a

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  PokerStarsBr.exe

STACK_TEXT:  
ffffa601`d4d1d8e8 fffff801`67ab440a : 00000000`00000124 00000000`00000000 ffffd00d`e3d51028 00000000`be000000 : nt!KeBugCheckEx
ffffa601`d4d1d8f0 fffff801`640e15b0 : 00000000`00000000 ffffd00d`e3d51028 ffffd00d`e06dd4f0 ffffd00d`e3d51028 : nt!HalBugCheckSystem+0xca
ffffa601`d4d1d930 fffff801`67bb61ee : 00000000`00000000 ffffa601`d4d1d9d9 ffffd00d`e3d51028 ffffd00d`e06dd4f0 : PSHED!PshedBugCheckSystem+0x10
ffffa601`d4d1d960 fffff801`67ab5d31 : ffffd00d`e350b900 ffffd00d`e350b900 ffffd00d`e06dd540 ffffd00d`e06dd4f0 : nt!WheaReportHwError+0x46e
ffffa601`d4d1da40 fffff801`67ab60a3 : 00000000`00000002 ffffd00d`e06dd540 ffffd00d`e06dd4f0 00000000`00000002 : nt!HalpMcaReportError+0xb1
ffffa601`d4d1dbb0 fffff801`67ab5f80 : ffffd00d`e04e0c70 fff17595`00000001 00000000`00000000 0ffff175`95840f48 : nt!HalpMceHandlerCore+0xef
ffffa601`d4d1dc00 fffff801`67ab61d1 : 00000000`00000004 00000000`00000001 00000000`00000000 b3e9c933`45100409 : nt!HalpMceHandler+0xe0
ffffa601`d4d1dc40 fffff801`67ab543b : 00000000`00000000 00000000`00000000 ffffa601`d4d1ded0 0d89fff1`7627860f : nt!HalpMceHandlerWithRendezvous+0xc9
ffffa601`d4d1dc70 fffff801`67ab7c85 : ffffd00d`e04e0c70 8138c033`ccfff176 7673840f`000001b5 000001b1`8138fff1 : nt!HalpHandleMachineCheck+0x5f
ffffa601`d4d1dca0 fffff801`67b0d519 : 8b48ccc3`01b0fff1 01359be8`ce8b48d5 cd8b4817`74c08400 85f88bff`ef1927e8 : nt!HalHandleMcheck+0x35
ffffa601`d4d1dcd0 fffff801`67a05cfa : 9abf0000`00a2e9c0 00000098`e9c00000 188e8b48`28558b48 000183e0`e8000002 : nt!KiHandleMcheck+0x9
ffffa601`d4d1dd00 fffff801`67a059b7 : 00000000`00000000 00000000`00000000 00000000`0594be10 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffa601`d4d1de40 00000000`5a0aae18 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
00000000`0527f280 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5a0aae18


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel__UNKNOWN

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d4ff8356-accf-463b-abb8-12a20b1a031a}

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

 

The second crash dump:

 


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


Loading Dump File [C:\Users\xlklx\OneDrive\Skrivebord\0001 – Kopi.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`0e800000 PsLoadedModuleList = 0xfffff806`0f42a230
Debug session time: Mon Jul 12 23:16:09.101 2021 (UTC + 2:00)
System Uptime: 0 days 0:03:54.830
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffd006372d0028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000008117a, Low order 32-bits of the MCi_STATUS value.

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

fffff8060f40f388: Unable to get Flags value from nt!KdVersionBlock
fffff8060f40f388: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
fffff8060f40f388: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: hal!_WHEA_MEMORY_ERROR_SECTION                ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on LENOVO

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 40

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd006372d0028

BUGCHECK_P3: be000000

BUGCHECK_P4: 8117a

PROCESS_NAME:  System

STACK_TEXT:  
fffff806`156298e8 fffff806`0ecb440a : 00000000`00000124 00000000`00000000 ffffd006`372d0028 00000000`be000000 : nt!KeBugCheckEx
fffff806`156298f0 fffff806`0dba15b0 : 00000000`00000000 ffffd006`372d0028 ffffd006`3522d350 ffffd006`372d0028 : nt!HalBugCheckSystem+0xca
fffff806`15629930 fffff806`0edb61ee : 00000000`00000000 fffff806`156299d9 ffffd006`372d0028 ffffd006`3522d350 : PSHED!PshedBugCheckSystem+0x10
fffff806`15629960 fffff806`0ecb5d31 : ffffd006`372edbd0 ffffd006`372edbd0 ffffd006`3522d3a0 ffffd006`3522d350 : nt!WheaReportHwError+0x46e
fffff806`15629a40 fffff806`0ecb60a3 : 00000000`00000000 ffffd006`3522d3a0 ffffd006`3522d350 00000000`00000000 : nt!HalpMcaReportError+0xb1
fffff806`15629bb0 fffff806`0ecb5f80 : ffffd006`338dfb00 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandlerCore+0xef
fffff806`15629c00 fffff806`0ecb61d1 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
fffff806`15629c40 fffff806`0ecb543b : 00000000`00000000 00000000`00000000 fffff806`15629ed0 00000000`00000000 : nt!HalpMceHandlerWithRendezvous+0xc9
fffff806`15629c70 fffff806`0ecb7c85 : ffffd006`338dfb00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x5f
fffff806`15629ca0 fffff806`0ed0d519 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
fffff806`15629cd0 fffff806`0ec05cfa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
fffff806`15629d00 fffff806`0ec059b7 : 00000000`00000000 fffff806`0ec058ec ffffd006`35eef060 00000000`00000000 : nt!KxMcheckAbort+0x7a
fffff806`15629e40 fffff806`135ad5f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
fffff806`155fe5f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Wdf01000!FxTimer::Stop+0x2e [minkernel\wdf\framework\shared\core\fxtimer.cpp @ 797] 


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_MEMORY__UNKNOWN_FATAL

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fbe3664c-d382-45ce-74c8-3bd9bd7fd3d7}

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

 

 

 

 

Reply
Answer
Options

11 Posts

07-12-2021

Norway

11 Signins

55 Page Views

  • Posts: 11
  • Registered: ‎07-12-2021
  • Location: Norway
  • Views: 55

Re:KB5004945 thinkpad T470s BSOD

2021-07-20, 17:01 PM

So don`t accept my solution because there is no solution so going to click accept solution because that will end this with no solution and.....Will say thanks to my sponsor for all the support if I had one, thanks to my family if I had one and thanks to my friends if I had some......now where is that gun________________________

Reply

Replies(15)
Options

5679 Posts

08-02-2018

Philippines

929 Signins

28899 Page Views

  • Posts: 5679
  • Registered: ‎08-02-2018
  • Location: Philippines
  • Views: 28899
  • Message 2 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-12, 21:45 PM

Hello Hardingen KL!


Welcome to community forums

 

 

You might want to run the Windows troubleshooter and check if that helps.


Some users have reported having trouble with this update from Microsoft. This is regardless of the brand from 3rd party forums sites and you can check this sample post from the Microsoft forum site: https://docs.microsoft.com/en-us/answers/questions/472002/security-update-kb5004945-causing-bsod.html

 

For now, do not install this update and wait for advice from MS since this is something that Lenovo does not have any control over.

 

Regards

 

 

Jwes_Lenovo



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 mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.


Using Browser Search to find your answers in Lenovo and Moto Community

Reply
Options

11 Posts

07-12-2021

Norway

11 Signins

55 Page Views

  • Posts: 11
  • Registered: ‎07-12-2021
  • Location: Norway
  • Views: 55
  • Message 3 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-12, 23:19 PM

Thanks for trying to help. Did an edit of the problem after your first respond after more crashes today.

Reply
Options

11 Posts

07-12-2021

Norway

11 Signins

55 Page Views

  • Posts: 11
  • Registered: ‎07-12-2021
  • Location: Norway
  • Views: 55
  • Message 4 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-13, 14:47 PM

Trying to click tumbs up for you but that seems to be difficult. Anyway, today I`m leaning towards heating issues as cause......lets see how long that thought lasts.

Reply
Options

5679 Posts

08-02-2018

Philippines

929 Signins

28899 Page Views

  • Posts: 5679
  • Registered: ‎08-02-2018
  • Location: Philippines
  • Views: 28899
  • Message 5 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-13, 15:01 PM

 

For the HDMI issue, try installing this critical update; https://support.lenovo.com/us/en/solutions/ht508988

 

Install the driver first then followed by the firmware. Kindly include the recently released BIOS update as well. You can get it here; https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t470s/downloads/driver-list/component?name=BIOS%2FUEFI

 


Update us on how it goes.

 


Jwes_Lenovo



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 mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.


Using Browser Search to find your answers in Lenovo and Moto Community

Reply
Options

11 Posts

07-12-2021

Norway

11 Signins

55 Page Views

  • Posts: 11
  • Registered: ‎07-12-2021
  • Location: Norway
  • Views: 55
  • Message 6 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-13, 17:31 PM

Dont`t really have any problems with hdmi, just a desperate move to see if it helped. Had a new crash today with no hdmi cable so that`s not it. Same error 0x124_GenuineIntel_MEMORY__UNKNOWN_FATAL. All drivers, BIOS should be up to date with Lenovo Vantage. A new clean install of windows maybe......

Reply
Options

5679 Posts

08-02-2018

Philippines

929 Signins

28899 Page Views

  • Posts: 5679
  • Registered: ‎08-02-2018
  • Location: Philippines
  • Views: 28899
  • Message 7 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-14, 13:04 PM


The error message is related to physical hardware failures. It can be heat-related, defective hardware, memory, or even a processor that is beginning to fail or has failed.

Try running a hardware test from the Vantage app or perhaps a memory test.

 

 

Jwes_Lenovo



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 mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.


Using Browser Search to find your answers in Lenovo and Moto Community

Reply
Options

11 Posts

07-12-2021

Norway

11 Signins

55 Page Views

  • Posts: 11
  • Registered: ‎07-12-2021
  • Location: Norway
  • Views: 55
  • Message 8 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-15, 18:51 PM

So have run Memtest86, only 4 runs so far, Passed. Then run Intel cpu diagnostic tool, Passed. (Crashed after one second on first try, passed second time.) Run the Lenovo harware test, Passed the quick test. Tried the long cpu test, but crashed after 5-10 min. So now light surfing is all it can take it looks like, and play some videos usually works, but next crash is right around the corner always. The pc was in service around 6 months ago,( when I had a warranty which I don`t now offcourse,) for sound issues and some other small stuff. Nothing serious, but they did change the motherboard, maybe I got unlucky on that one, so only been used lightly for 6 months. So might just try and wipe everything with a clean install, if the pc can take it, just 4 fun, as a last effort before using it as door stopper.  

Reply
Options

11 Posts

07-12-2021

Norway

11 Signins

55 Page Views

  • Posts: 11
  • Registered: ‎07-12-2021
  • Location: Norway
  • Views: 55
  • Message 9 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-15, 23:52 PM

Wiped everything with new reinstall, crashes on every step, but got it done. But no success, problem remains. Game over I guess. 

Reply
Options

5679 Posts

08-02-2018

Philippines

929 Signins

28899 Page Views

  • Posts: 5679
  • Registered: ‎08-02-2018
  • Location: Philippines
  • Views: 28899
  • Message 10 of 16

Re:KB5004945 thinkpad T470s BSOD

2021-07-16, 14:54 PM


I see. Another option is to bring it to any of our authorized repair centers near your place for further assistance.


You can find the list here; https://pcsupport.lenovo.com/no/nb/partnerlocator

 

Hope everything goes well for you.

 

 


Jwes_Lenovo



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 mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.


Using Browser Search to find your answers in Lenovo and Moto Community

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms