Unsolved
7 Posts
0
2565
January 15th, 2022 12:00
Aurora R7, freezing due 0x00000116
Heya,
Im running into a problem with my out of warranty Aurora R7. Lately it has been freezing random whenever any media type is loading in. (atleast it feels like this, gif on web whatsapp, youtube video, rendering software) As I am not the most techy guy i've been trying to find the problem atleast. What I have done so far:
- Clean install of W10
- Updated every driver as far as I can tell
- Opened my desktop and check if no connections were loose
- Ran some stresstests for CPU/RAM/GPU
- Only time it actually crashed was once during a GPU stresstest. Trying to reproduce after it did not (it really feels random).
With SupportAssist I found out the error it is causing is the following:
Errorcode:
0x00000116
Parameters for errorcode:
0xffffe00ac2dad010,
0xfffff80563576350,
0xffffffffc000009a,
0x0000000000000004
Device name
DirectX Graphics Kernel
My dump file gives me the following:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe00ac2dad010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80563576350, 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.
Debugging Details:
------------------
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvddi.inf_amd64_21286f2484bb9003\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4311
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 8031
Key : Analysis.Init.CPU.mSec
Value: 343
Key : Analysis.Init.Elapsed.mSec
Value: 4177
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
FILE_IN_CAB: 011322-6109-01.dmp
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffe00ac2dad010
BUGCHECK_P2: fffff80563576350
BUGCHECK_P3: ffffffffc000009a
BUGCHECK_P4: 4
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe00ac2dad010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000004
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff380`7de32918 fffff805`5e66653e : 00000000`00000116 ffffe00a`c2dad010 fffff805`63576350 ffffffff`c000009a : nt!KeBugCheckEx
fffff380`7de32920 fffff805`5e616cb4 : fffff805`63576350 ffffe00a`c8262010 00000000`00002000 ffffe00a`c82620d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffff380`7de32960 fffff805`5e60f7ec : ffffe00a`c8257000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
fffff380`7de32990 fffff805`5e665c65 : 00000000`00000100 ffffe00a`c8257a70 00000000`cd611080 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
fffff380`7de32a10 fffff805`5e665dd7 : fffff805`4b925440 00000000`00000000 00000000`00000000 00000000`00000100 : dxgkrnl!TdrResetFromTimeout+0x15
fffff380`7de32a40 fffff805`4aeb85f5 : ffffe00a`d545a540 fffff805`5e665db0 ffffe00a`a84e1ce0 ffffe00a`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
fffff380`7de32a70 fffff805`4af55935 : ffffe00a`d545a540 00000000`00000080 ffffe00a`a84d7080 00000000`00000001 : nt!ExpWorkerThread+0x105
fffff380`7de32b10 fffff805`4affe728 : ffff8d81`44d80180 ffffe00a`d545a540 fffff805`4af558e0 01d80887`934aaf4f : nt!PspSystemThreadStartup+0x55
fffff380`7de32b60 00000000`00000000 : fffff380`7de33000 fffff380`7de2c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nvlddmkm+df6350
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
---------
I hope this is somewhat of enough information to help me out. This is getting slightly frustrating :(
Cheers,
Shane
No Events found!
JOcean
9 Legend
•
12.6K Posts
0
January 15th, 2022 12:00
That error does indicate a GPU problem and nvlddmkm.sys is an Nvidia driver file. Run diagnostics (tap F12 immediately at boot) and watch for an GPU errors. But it is very possible that your GPU card is giving you trouble. I assume you have already tried to update to the latest Nvidia drivers from Dell though you could try the drivers at the Nvidia web site. However if you have the GPU from Dell when you ordered the system the Nvidia drivers from their site may not recognize the card and will not install.
Enyahs
7 Posts
0
January 16th, 2022 04:00
Thanks! I just found out GF experience said I had the latest drivers. When checking the Gefore website itself I found I had an 3 month old driver. I have now installed the latest driver through the Geforce website. Hoping this will be the solution. Else I will try the driver that Dell offers. Didnt know there was a difference actually!
Vanadiel
6 Professor
•
7K Posts
0
January 16th, 2022 14:00
There technically speaking is no difference. There are 2 main branches of Nvidia drivers:
- Game Ready Drivers.
- Studio Drivers.
The game ready drivers are the latest available and support the latest games.
The studio drivers are the most stable available, and do not necessarily support the latest games.
The Dell OEM drivers are somewhere in between, a few revisions older but not as old as the studio drivers.
Enyahs
7 Posts
0
January 17th, 2022 00:00
Ahh that makes sense. Unfortunately, even with the new drivers I still run into the issue. I have ran the diagnostics after booting. That resolved a memory issue. Not sure if this is going to be the fix. I´ll keep this thread updated!
Enyahs
7 Posts
0
January 17th, 2022 01:00
Resolved memory issue also is not the solution. Problem still here. Driving me mad.
Maybe the next step would to be to have an expert take a look at it?
Vanadiel
6 Professor
•
7K Posts
0
January 17th, 2022 03:00
Could also be a hardware issue. I would contact dell cares for warranty request:
Please do not post your private Service Tag in public. Click the blue DELL-Cares username. Their profile page will appear. On the right click, "Send this user a private message". They will need the private PC Service Tag to check your purchased warranty status, components, etc.
22GREEN
2 Intern
•
239 Posts
0
January 17th, 2022 17:00
Maybe the card is toast.. I Googled the error code and there where a lot of threads on it. Maybe someone posted a fix. Just another avenue to try.
Tesla1856
8 Wizard
•
17.1K Posts
0
January 17th, 2022 20:00
Unless I missed it, you don't say what Nvidia card you have.
The latest drivers are not always the best (most stable) for older cards.
Clean-installing Windows-10 is good. But get it from Microsoft.com. All drivers should come from Windows-Update. Load NO Intel-RST or any Dell stuff . Get an old/stable driver from Nvidia.com. Keep it very lean until it's been working fine for a while. After it's not crashing any more, you can finally load AW-CC (the old one, validated for your machine).
OCCT (using it's power-supply test) is good for stress-testing.
Enyahs
7 Posts
0
January 18th, 2022 00:00
I am using a 1080TI. All things I´ve tried so far:
- Clean install
- Only updated windows, and used GeForce Experience after to install latest driver
- Multiple stresstests using different software, also using OCCT. Nothing happened
- Ran diagnostics through booth, resolved a memory issue
- Ran SFC/scannow through cmd, found corrupted files, resolved
- Found out latest GPU driver was in fact not the latest driver (installed a driver from november 2021)
- Updated driver to latest, problem still insisted
- Downgraded to driver from july (a period I was certain the problem was not there yet)
- Problem still insists.
What i find weird is that after a clean install I immediately find corrupted files and a memory issue.
Also, it is hard to find out exactly when the problem occurs. I can play high end games no problem, but I have the feeling the problem does occur random whenever I am browsing (especially pages like youtube or autoplay embedded videos) For instance a Dutch news site https://www.ad.nl/ has a video play during the morning with the latest news. This almost 100% of the time triggers it.
Maybe far fetched, but could the problem occur due to working with 2 screens with for example different refresh rates? I have a feeling that it happens more often when I am opening these pages on my 2nd screen. Maybe I am just imagining things though.
Enyahs
7 Posts
0
January 18th, 2022 14:00
I might have found a solution, still testing though. This morning I could no enter https://www.dell.com/support/kbdoc/en-us/000124211/dell-bios-updates
The video would instantly freeze my desktop. A friend of mine suggested unplugging my 2nd screen. (plugged into the HDMI port, main screen is plugged in display port). I can now freely browse without running into the freeze (yet, hopefully gone). Before I get to happy, could this be a cause for this problem?
Tesla1856
8 Wizard
•
17.1K Posts
0
January 19th, 2022 21:00
1. Oh. If it was GTX-1070 or 1080, I was going to see what driver-package I'm running on my Auroras (I have 1070's in both). Here, on one machine, it is Driver v456.71-DCH
2. From Microsoft.com I hope. Not Dell as you will then likely end-up with Intel-RST, SupportAssist, heavy driver suites, etc.
3. Have never-ever used GeForce (Beta Tester) Experience.
4. Nothing happened? What does that mean? In OCCT, the "Power Supply Test" is what I use.
5. Please explain. There should not be ANY memory errors, ever.
6. THIS IS YOUR MAIN PROBLEM. If SFC finds anything wrong, you likely have a hardware problem. Especially if you just clean-installed Windows.
7. Only thing I've ever seen 2 monitors attached do is ... it won't let video-card fall-back to low-power mode on easy stuff like just running the Windows Desktop.
Dark_Wraith
1 Message
0
February 5th, 2022 13:00
Hello! I have a similar issue like this. Any updates on this? Did you manage to resolve the issue?
Enyahs
7 Posts
0
February 6th, 2022 04:00
Hi Dark,
Unfortunately not. I thought I found the issue by disconnecting my 2nd monitor. But that also didnt help. I've installed a Nvidia driver from March 2021 and the problem does occur way less. It is at a state which I can live with for now. I was already looking at getting a new desktop soon but this has speed that up.
Sorry that i cant be of any more help.