cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Ecrook
Paper Tape
Posts: 2
Registered: ‎09-29-2018
Location: DE
Views: 3,015
Message 1 of 11

BSOD P52 Problems

i bought a new P52 a week ago and have some serious issues with BSOD.

 

Wdf01000.sys Wdf01000.sys+32cc5 fffff807`eed20000 fffff807`eee04000 0x000e4000 0xbd4591f4 17.08.2070 00:19:32

 

And the TDR Video Failure.

 

I´m a little bit pissed off. I thougt i bougth a premium product but it seems that Lenovo isn´t able to provide functional drivers. 

All Drivers are up to date and i also reinstalled a clean Windows. Does something else has similiar issues an can provide me a solution.

 

regards

 

 

 

 

 

pjg
802.11n
Posts: 185
Registered: ‎05-30-2009
Location: CA
Views: 2,949
Message 2 of 11

Re: BSOD P52 Problems

Could you provide the specs to your P52 ?  And the versions of the key drivers ? And what version on Windows 10 you have ?

Ecrook
Paper Tape
Posts: 2
Registered: ‎09-29-2018
Location: DE
Views: 2,933
Message 3 of 11

Re: BSOD P52 Problems

I have the 20M9001FGE Modell i7 8750H P1000 upgraded to 16 GB RAM (Lenovo Stock Ram) and a secondary 1TB WD Blue.

 

As i mentioned before the system is up to date. W10 1803 and all drivers are also up to date. ( from the perspective of Lenovo System Update). I did´nt installed some third party drivers till now. 

 

It, seems that the system cannot handle the secondary Monitor, Dell WQHD 34inch and the graphics driver crahes to often. I faced a similiar problem by a customer of mine who is using thinkcenter m710. There were some device who struggled with a specific Dual Monitor Setup and crashed frequently in a BSOD.  
I switched  from hybrid to discrete video mode and until now it seems stable. It seems that i`m not the only persone who has similar Problems with his device.

So come on, i bought a 2000+ € Device and this shouldn’t happen. I also do not want to use the quadro all the time. Especially when i`m on the road.

 

At Work we are using HP ZBooks which are for build for same purposes like the P52 and we didńt faced any of the Problems me and others have. 

madkm
Paper Tape
Posts: 4
Registered: ‎10-09-2018
Location: CA
Views: 2,849
Message 4 of 11

Re: BSOD P52 Problems

I have a P52 with almost the same specs as you... i7-8750H, P1000 video, and 16 GB of stock RAM, but I installed a Samsung 970 EVO SSD and made it the boot drive by cloning the stock 1TB HDD (because Lenovo SSDs are unjustifiably stupid-expensive).

 

I run mostly audio applications that sometimes get all 6 cores of the processor past 90%.

 

I had 3 or 4 BSODs since my laptop was delivered a month ago which lost about 6 hours of irreplicatable work.

 

One crash happened as I was unplugging peripheral devices, which included a USB hub linked to a keyboard, a mouse, and a generic audio interface, and an external monitor linked with an HDMI cable.  I'm guessing it was the video cable unplugging that crashed it.  Last time I had a crash, I analyzed the memory dump, which pointed to a Lenovo pointing device driver setup app, with the most likely cause being listed as corrupt memory. 

 

If it happens again, I will RMA the P52 and buy something with similar specs at 75% the price.  I paid Lenovo a premium for reliability.  The P52 crashed more times than my old HP Envy laptop, since 2012.

K2000
What's DOS?
Posts: 1
Registered: ‎11-08-2018
Location: CA
Views: 2,672
Message 5 of 11

Re: BSOD P52 Problems

Mine crashes over night every night. Win 1803, trsted with and without all the latest updates from Lenovo client app; same bsod. 

And yeah, the HP envy Serie is a junk.

BetaDach
Serial Port
Posts: 14
Registered: ‎08-23-2018
Location: DE
Views: 2,650
Message 6 of 11

Re: BSOD P52 Problems

I wouldn't be surprised if the cause of your BSoD was linked to the touchpad issues other users and I are experiencing. The BSoD appears to be the same; see: https://forums.lenovo.com/t5/ThinkPad-P-and-W-Series-Mobile/P52-ELAN-Touchpad-driver-ETD-sys-issues-...

Adnane
Paper Tape
Posts: 1
Registered: ‎11-26-2018
Location: CA
Views: 2,461
Message 7 of 11

Re: BSOD P52 Problems

Same problem here. P52 16gb Samsung evo 970.

 

almost one bsod every day with build 1803 and 1809.

 

Only Lenovo drivers are installed.

 

I restored an image backup of build 1803, uninstalled norton antivirus and worked a day without any dock. Got a bsod again!

 

Lenovo replaced my RAM module but I still have bsod.

 

Very disappointed Smiley Sad

 

 

 

 

madkm
Paper Tape
Posts: 4
Registered: ‎10-09-2018
Location: CA
Views: 2,430
Message 8 of 11

Re: BSOD P52 Problems

I haven't had a BSOD in 2 weeks, or since I went on the Lenovo website, downloaded and installed the most recent BIOS firmware update and device drivers.  I'm still using stock Lenovo drivers.

 

However, I have not pushed my computer very hard in that time either.  

 

As another user suggested, I would also consider tracking your crashes by analyzing your memory dump files.  This requires some advanced knowledge of Windows.

 

Yet another user suggested using stock Microsoft drivers for your hardware.  I have not tried it yet.  If, for example, memory dumps reveal that it's the trackpad drivers that cause crashes, I would change to more basic drivers.  Yes, you may use some functionality, but that's like giving up candy to stop seisures, worth it in my opinion.

RadiatorX
Punch Card
Posts: 32
Registered: ‎02-10-2017
Location: DE
Views: 1,215
Message 9 of 11

Re: BSOD P52 Problems

i am pissed of, too. Some bsods, with Wdf01000.sys driver and irq is less or equal...

This is my fifth W/P Series Thinkpad, with other Systems i have no bsods in the last years!,but with this amazing P52 i have some bsods in the month. Is the amount of money for a PSeries System not enough to make a hundret percent quality check.

Andrey-C
What's DOS?
Posts: 1
Registered: ‎01-03-2017
Location: CA
Views: 1,139
Message 10 of 11

Re: BSOD P52 Problems

Debugging team has analyzed the memory dump and provided below information.

 

Analysis Summary (Conclusion)

-------------------------------------------------------------------------------------------------------------------------------------------------

This indicates that an attempt to reset the display driver and recover from a timeout failed. The GPU is taking more time than permitted to display graphics to your monitor.

You may need to install the latest updates for your display driver, so that it properly supports the TDR process.

 

Action Plan

-------------------------------------------------------------------------------------------------------------------------------------------------

The faulty component here is the NVIDIA driver. We recommend you to get in touch with the vendor and have them review the dump as well. If there is any latest version available, then please update the driver to the latest.

 

Module[119] [C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVLTWI.INF_AMD64_C320601607A026AA\NVLDDMKM.SYS]

  Company Name:      NVIDIA Corporation

  File Description:  NVIDIA Windows Kernel Mode Driver, Version 419.17

  Product Version:   (25.21:14.1917)

  File Version:      (25.21:14.1917)

  File Size (bytes): 20726016

  File Date:         Thu Feb 21 06:17:02 2019

    Module TimeDateStamp = 0x5c6d35f0 - Wed Feb 20 06:11:44 2019

    Module Checksum      = 0x013cc888

    Module SizeOfImage   = 0x01425000

  Module Pointer to PDB = [C:\dvs\p4\build\sw\rel\gpu_drv\r418\r419_12\drivers\display\lddm\nvlddmkm\_out\wddm2_amd64_release\nvlddmkm.pdb]

    Module PDB Guid = {F673CD78-9333-411B-A708-9EF8B90C5302}

    Module PDB Age = 0x1

 

Machine Details (Dump Info)

-------------------------------------------------------------------------------------------------------------------------------------------------

Dump Name: MEMORY.DMP

Computer Name: XXX-23

Windows 10 Kernel Version 17763 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 17763.1.amd64fre.rs5_release.180914-1434

Kernel base = 0xfffff806`7b00d000 PsLoadedModuleList = 0xfffff806`7b4289f0

Debug session time: Thu Mar 21 05:46:32.417 2019 (UTC - 7:00)

System Uptime: 0 days 12:39:15.047

SystemManufacturer = LENOVO

SystemProductName = 20M9000FUS

Processor: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz

Bugcheck: 116 (FFFFB504177F3010, FFFFF80019550720, FFFFFFFFC000009A, 4)

Kernel Complete Dump File: Full address space is available.

 

Bugcheck details

-------------------------------------------------------------------------------------------------------------------------------------------------

VIDEO_TDR_FAILURE (116)

Attempt to reset the display driver and recover from timeout failed.

Arguments:

Arg1: ffffb504177f3010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

Arg2: fffff80019550720, The pointer into responsible device driver module (e.g. owner tag).

Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

Arg4: 0000000000000004, Optional internal context dependent data.

 

Crashing Stack

-------------------------------------------------------------------------------------------------------------------------------------------------

# Child-SP          RetAddr           Call Site

00 ffff8705`c7047918 fffff800`15590a11 nt!KeBugCheckEx

01 ffff8705`c7047920 fffff800`1554c348 dxgkrnl!TdrBugcheckOnTimeout+0xf5

02 ffff8705`c7047960 fffff800`15544876 dxgkrnl!ADAPTER_RENDER::Reset+0x174

03 ffff8705`c7047990 fffff800`15590155 dxgkrnl!DXGADAPTER::Reset+0x4da

04 ffff8705`c7047a10 fffff800`155902b7 dxgkrnl!TdrResetFromTimeout+0x15

05 ffff8705`c7047a40 fffff806`7b0c11ea dxgkrnl!TdrResetFromTimeoutWorkItem+0x27

06 ffff8705`c7047a70 fffff806`7b093bc5 nt!ExpWorkerThread+0x16a

07 ffff8705`c7047b10 fffff806`7b1c7a3c nt!PspSystemThreadStartup+0x55

08 ffff8705`c7047b60 00000000`00000000 nt!KiStartSystemThread+0x1c

 

Debug Notes (Analysis)

-------------------------------------------------------------------------------------------------------------------------------------------------

Bug Check 0x116: VIDEO_TDR_FAILURE

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x116---video-tdr-failu...

 

10: kd> !dumptime

Event        Times (UTC - 7:00)

============ ==========================

System Start 03/20/2019 05:07:17.370 PM

Dump Start   03/21/2019 05:46:32.417 AM

 

Stat          Duration

============= =============

System Uptime 12h:39:15.047

 

10: kd> !t

Process                   Thread           CID       UserTime KernelTime ContextSwitches Wait Reason   Time State

System (ffffb503ffcca300) ffffb504160d1040 4.2f00          0s     2s.734          111046 Executive   1s.812 Running on CPU 10

 

Priority:

    Current Base UB FB IO Page

    15      13   0  0  2  5

 

# Child-SP         Return           Call Site

0 ffff8705c7047918 fffff80015590a11 nt!KeBugCheckEx+0x0

1 ffff8705c7047920 fffff8001554c348 dxgkrnl!TdrBugcheckOnTimeout+0xf5

2 ffff8705c7047960 fffff80015544876 dxgkrnl!ADAPTER_RENDER::Reset+0x174

3 ffff8705c7047990 fffff80015590155 dxgkrnl!DXGADAPTER::Reset+0x4da

4 ffff8705c7047a10 fffff800155902b7 dxgkrnl!TdrResetFromTimeout+0x15

5 ffff8705c7047a40 fffff8067b0c11ea dxgkrnl!TdrResetFromTimeoutWorkItem+0x27

6 ffff8705c7047a70 fffff8067b093bc5 nt!ExpWorkerThread+0x16a

7 ffff8705c7047b10 fffff8067b1c7a3c nt!PspSystemThreadStartup+0x55

8 ffff8705c7047b60 0000000000000000 nt!KiStartSystemThread+0x1c

 

This thread is crashing

 

10: kd> dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffb504177f3010

   +0x000 Signature        : 0x52445476

   +0x008 pState           : 0xffffb504`17b06964 2 ( TdrStateRecoveryInProgress )

   +0x010 TimeoutReason    : 3 ( TdrReasonVSyncTimeout )

   +0x018 Tick             : _ULARGE_INTEGER 0x8b

   +0x020 pAdapter         : 0xffffb504`13ad2000 DXGADAPTER

   +0x028 referenceCookie  : 0xffffffff`ffffffff

   +0x030 pVidSchContext   : (null)

   +0x038 GPUTimeoutData   : _TDR_RECOVERY_GPU_DATA

   +0x050 CrtcTimeoutData  : _TDR_RECOVERY_CONTEXT::<unnamed-type-CrtcTimeoutData>

   +0x060 pProcessName     : 0xffffb504`197de8b0  "dwm.exe"

   +0x068 DbgOwnerTag      : 0xfffff800`19550720

   +0x070 PrivateDbgInfo   : _TDR_DEBUG_REPORT_PRIVATE_INFO

   +0xb10 pDbgReport       : 0xffffb504`114f7c00 _WD_DEBUG_REPORT

   +0xb18 pDbgBuffer       : 0xffff8e82`5da70000 Void

   +0xb20 DbgBufferSize    : 0x89954

   +0xb28 pDumpBufferHelper : (null)

   +0xb30 pDbgInfoExtension : 0xffff8e82`7d1ed510 _DXGKARG_COLLECTDBGINFO_EXT

   +0xb38 pDbgBufferUpdatePrivateInfo : 0xffff8e82`5da70140 Void

   +0xb40 ReferenceCount   : 0n2

   +0xb48 pScenarioContext : (null)

   +0xb50 pPowerThread     : (null)

   +0xb58 bReportSubmitted : 0 ''

 

10: kd> ub fffff80019550720

nvlddmkm!nvDumpConfig+0x2359a0:

fffff800`19550700 48ff2569a3e1ff  jmp     qword ptr [nvlddmkm!nvDumpConfig+0x4fd10 (fffff800`1936aa70)]

fffff800`19550707 cc              int     3

fffff800`19550708 48ff25c9a1e1ff  jmp     qword ptr [nvlddmkm!nvDumpConfig+0x4fb78 (fffff800`1936a8d8)]

fffff800`1955070f cc              int     3

fffff800`19550710 48ff25a9a2e1ff  jmp     qword ptr [nvlddmkm!nvDumpConfig+0x4fc60 (fffff800`1936a9c0)]

fffff800`19550717 cc              int     3

fffff800`19550718 48ff25f9a1e1ff  jmp     qword ptr [nvlddmkm!nvDumpConfig+0x4fbb8 (fffff800`1936a918)]

fffff800`1955071f cc              int     3

10: kd> dt 0xffffb504`13ad2000 DXGADAPTER

dxgkrnl!DXGADAPTER

   +0x000 m_NodeListEntry  : _LIST_ENTRY [ 0xffffb504`0f494000 - 0xffffb504`00c761c0 ]

   +0x010 m_pNodeParent    : 0xffffb504`00c76000 DXGGLOBAL

   +0x018 m_ReferenceCount : ReferenceCountWithHistoryTracking

   +0x020 m_WarpAdapterReferenceCookie : 0

   +0x028 m_DdiReferenceCookie : 0xffffffff`ffffffff

   +0x030 m_CoreAccessEvent : _KEVENT

   +0x048 m_PowerStateRequestLock : DXGPUSHLOCK

   +0x060 m_PowerTransitionLock : DXGPUSHLOCK

   +0x078 m_AdapterStopResetLock : DXGPUSHLOCKFAST

   +0x088 m_PowerState     : 0 ( POWERSTATE_REQUESTED_D0 )

   +0x090 m_pCoreResource  : 0xffffb504`16fd9390 _ERESOURCE

   +0x098 m_ExclusiveAccessReason : 2 ( DXGADAPTER_EXCLUSIVEACCESS_FLUSHSCHEDULER )

   +0x0a0 m_pWorkerThreadOfExclusiveOwner : [2] (null)

   +0x0b0 m_ExecutionState : 1 ( EXECUTION_ACTIVE )

   +0x0b4 m_DisableDevicePowerRequired : 0 ''

   +0x0b5 m_bSuspended     : 0 ''

   +0x0b6 m_bHybridDiscrete : 0x1 ''

   +0x0b7 m_bUseSelfRefreshVRAMInS3 : 0 ''

   +0x0b8 m_bInDestruction : 0 ''

   +0x0b9 m_bParavirtualized : 0 ''

   +0x0ba m_bParavirtualizedSecure : 0 ''

   +0x0bb m_bVailSupported : 0 ''

   +0x0bc m_bACGSupported  : 0x1 ''

   +0x0c0 m_pDeviceObject  : 0xffffb504`171d4030 _DEVICE_OBJECT

   +0x0c8 m_DevicePDOBase  : 0xffffb504`17b0f060

   +0x0d0 m_Ordinal        : 3

   +0x0d8 m_DdiAccessEvent : _KEVENT

   +0x0f0 m_pDdiResource   : 0xffffb504`16fd9410 _ERESOURCE

   +0x0f8 m_DxgkInterface  : _DXGK_INTERFACE

.

.

.

 

10: kd> dt 0xffffb504`171d4030 _DEVICE_OBJECT

dxgkrnl!_DEVICE_OBJECT

   +0x000 Type             : 0n3

   +0x002 Size             : 0x16f0

   +0x004 ReferenceCount   : 0n0

   +0x008 DriverObject     : 0xffffb504`16198e30 _DRIVER_OBJECT

   +0x010 NextDevice       : 0xffffb504`1675adf0 _DEVICE_OBJECT

   +0x018 AttachedDevice   : (null)

   +0x020 CurrentIrp       : (null)

   +0x028 Timer            : (null)

   +0x030 Flags            : 0x2004

   +0x034 Characteristics  : 0x100

   +0x038 Vpb              : (null)

   +0x040 DeviceExtension  : 0xffffb504`171d4180 Void

   +0x048 DeviceType       : 0x23

   +0x04c StackSize        : 3 ''

   +0x050 Queue            : _DEVICE_OBJECT::<unnamed-type-Queue>

   +0x098 AlignmentRequirement : 0

   +0x0a0 DeviceQueue      : _KDEVICE_QUEUE

   +0x0c8 Dpc              : _KDPC

   +0x108 ActiveThreadCount : 0

   +0x110 SecurityDescriptor : 0xffff8e82`60ef7e60 Void

   +0x118 DeviceLock       : _KEVENT

   +0x130 SectorSize       : 0

   +0x132 Spare1           : 0

   +0x138 DeviceObjectExtension : 0xffffb504`171d5720 _DEVOBJ_EXTENSION

   +0x140 Reserved         : (null)

10: kd> dt 0xffffb504`16198e30 _DRIVER_OBJECT

dxgkrnl!_DRIVER_OBJECT

   +0x000 Type             : 0n4

   +0x002 Size             : 0n336

   +0x008 DeviceObject     : 0xffffb504`17e249f0 _DEVICE_OBJECT

   +0x010 Flags            : 0x412

   +0x018 DriverStart      : 0xfffff800`189e0000 Void

   +0x020 DriverSize       : 0x1425000

   +0x028 DriverSection    : 0xffffb504`12310510 Void

   +0x030 DriverExtension  : 0xffffb504`16198f80 _DRIVER_EXTENSION

   +0x038 DriverName       : _UNICODE_STRING "\Driver\nvlddmkm"

   +0x048 HardwareDatabase : 0xfffff806`7b97b888 _UNICODE_STRING "\REGISTRY\MACHINE\HARDWARE\DESCRIPTION\SYSTEM"

   +0x050 FastIoDispatch   : (null)

   +0x058 DriverInit       : 0xfffff800`19dd40b4     long  nvlddmkm!nvDumpConfig+0

   +0x060 DriverStartIo    : (null)

   +0x068 DriverUnload     : 0xfffff800`18b7ba18     void  +0

   +0x070 MajorFunction    : [28] 0xfffff800`18b79520     long  +0

 

10: kd> lmvm nvlddmkm

Browse full module list

start             end                 module name

fffff800`189e0000 fffff800`19e05000   nvlddmkm   (export symbols)       nvlddmkm.sys

    Loaded symbol image file: nvlddmkm.sys

    Image path: \SystemRoot\System32\DriverStore\FileRepository\nvltwi.inf_amd64_c320601607a026aa\nvlddmkm.sys

    Image name: nvlddmkm.sys

    Browse all global symbols  functions  data

    Timestamp:        Wed Feb 20 03:11:44 2019 (5C6D35F0)

Check out current deals!


Shop current deals

Top Kudoed Authors