Unsolved
7 Practitioner
•
2.6K Posts
•
9.6K Points
2
1712
January 28th, 2023 16:00
XPS8940, Nvidia/BIOS Lock up FINALLY captured....
Well, today, at 9:58AM I locked up after 3 days running fine on BIOS V2.10.0. I did have over 20 days once on this BIOS.
Anyway, I was trying some programs to see if it could find anything. One was WHOCRASHED... and POOF, it found the cause:
===============================================================
Welcome to WhoCrashed (Home Edition) v 6.70
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.
PLEASE NOTE THAT THIS VERSION OF WHOCRASHED IS NOT LICENSED FOR USE BY PROFESSIONAL SUPPORT ENGINEERS.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
System Information (local)
Computer name: IRVXPS8940
Windows version: Windows 10, 10.0, version 2009, build: 22621
Windows dir: C:\WINDOWS
Hardware: XPS 8940, Dell Inc., 0427JK
CPU: GenuineIntel 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz 8664, level: 6
16 logical processors, active mask: 65535
RAM: 33912258560 bytes (31.6GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
C:\Windows\LiveKernelReports
On Sat 1/28/2023 9:59:14 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230128-0959.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF8008C3FCF70)
Bugcheck code: 0x141 (0xFFFF838D12DA5010, 0xFFFFF8008C3FCF70, 0x0, 0x0)
Error: VIDEO_ENGINE_TIMEOUT_DETECTED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nvddi.inf_amd64_52d9834be3be904c\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 528.24
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 528.24
Bug check description: This indicates that one of the display engines failed to respond in timely fashion.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 528.24 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_ENGINE_TIMEOUT_DETECTED
Conclusion
One crash dump has been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 528.24 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
======================
Now if one GOOGLES "Nvidia nvidia tdr" you'll find a lot of hits for this.
So it seems to be a timing issue it seems...
I checked, none is specified in the Nvidia Control Center OR in the Registry! So I assume it is at the default value.
There are links to create values to stop this. Not sure I want to go there.
If you had the Lock ups or freezes, you can get the program @ https://www.resplendence.com/main if you want to give it try on your PC.
Still, doesn't explain why only after BIOS V2.3.0 version though?
ishmael
1 Rookie
•
85 Posts
0
January 31st, 2023 06:00
I suspect I got that using Dell's Support Assist, which for better or worse is what I typically use for finding updates.
ispalten
7 Practitioner
•
2.6K Posts
•
9.6K Points
0
January 31st, 2023 07:00
@ishmael,
I removed Support Assist a long time ago. That stops me from even using the Dell Support site to look for updates for me unless I enter the Service Tag for the list.
However today Dell Update which I guess runs once a month showed I needed 2 updates:
Possible SA ran DU under the covers to find needed updates and showed that to you?
To make matters worse, today, with the Dell Requested NVidia driver be installed from OCT. which DU found had a newer one, I had 2 lock ups! Now Dell basically 'threw up their hands' and said I should use whatever driver works best...
WhoCrashed didn't find any data for either of those lock ups either.
This is a total fiasco and Dell has no clue and no way to handle this.
Since I did capture some data with NVidia's latest driver, I'll use that. I suspect NVidia has some Debug stuff in the driver as this crash is not a Dell only problem but on many different PC's.
ishmael
1 Rookie
•
85 Posts
0
January 31st, 2023 10:00
I ran the SA check for updates this morning, and installed those updates that brought the Nvidia driver up to v526.98. So far no issues. Have you reached out to see if Nvidia can be of any help?
ispalten
7 Practitioner
•
2.6K Posts
•
9.6K Points
0
January 31st, 2023 11:00
@ishmael
Yeah, that Dell one is still old compared to the V528.24 that NVidia released on 1/24/2023.
I've decided to use that one.
There is something else besides the driver that causes the issue I suspect? I would not expect you to have a problem if you never did. Something in the BIOS that changed on V2.4.0 caused the problem and remains in the present versions of the BIOS.
May never figure this out I'm afraid. Dell 'blew this off' as I captured the data with a program they can't use and on a driver they did not test. Once one they tested failed and didn't produce any data, washed their hands of it it seems.
RoHe
12 Elder
•
45.2K Posts
•
172.6K Points
0
January 31st, 2023 12:00
FWIW, Windows Update offered me the NVidia v526.98 driver as an optional update today for Win 10 22H2 on my XPS 8930. Didn't install it...
@ispalten - As for why WC doesn't see any info for latest crash, it's possible the PC just seized up before the OS had a chance to log the failure, and I'm assuming nothing in Event Viewer either.
This sounds like two very different types of crash, one that still allowed the OS to capture the details, but the other one didn't. So the one where info was captured may be irrelevant to whatever is going because, from the very beginning, that other type of crash never got logged...
ispalten
7 Practitioner
•
2.6K Posts
•
9.6K Points
0
January 31st, 2023 13:00
Ron,
I agree, I for one have seen 3 different types of lock ups:
As it was as I recall, that second one was the only one where WhoCrashed found data.
Yes, processes happen in specific order and times. I really believe the OS never got a chance to write data almost all these times.
It has happened to too many people, and under too many Nvidia drivers, as well as both under Windows and Linux, for this to be anything else but some h/w operational problem specific to Nvidia cards caused by a code change in the BIOS from V2.3.0 to V2.4.0 that is still functionally operational in today's BIOS.
Yes, there are some that do not have this problem. Sort of leads one to assume the basic h/w involved is somehow different. Maybe someday it might be discovered, who knows.
Now, what one can't say is of the two data points of some data and no data is that maybe ONLY partial data was captured? The rest was not. That is what was captured was the beginning of the process, and due to timing it completed before the lock up took place.
Dell not being able to create this (nor anyone being able to define how to do it either) only makes it harder to solve, if not impossible to solve.
I wish Dell would step up and fix this the only way probably that it could be now, swap out the Nvidia cards for AMD cards. I'd do it even if a nominal 'processing charge' were applied? Doesn't seem that after a year of misery that Dell has any desire to do that or FIX the problem. It is shame...
RoHe
12 Elder
•
45.2K Posts
•
172.6K Points
0
January 31st, 2023 17:00
Pity they haven't fixed this, so just find an OS config and driver combination that gives you the longest time between crashes and stick with it, regardless of how many new (failing) NVidia drivers, etc. etc are released...
ispalten
7 Practitioner
•
2.6K Posts
•
9.6K Points
0
February 1st, 2023 02:00
Ron, maybe I'm an eternal optimist, I'll try any new BIOS or NVidia driver hoping (against all odds probably) that it will be fixed 'automagically', just like it was broken 'automagically'.
So far though, with out making any OS changes or cutting back Turbo, there is no one combination that is guaranteed to run the same length of time between lock ups, all Random when it can happen, hours, days, or weeks each combo seems to have for when it will happen. Disappointing.