Performancetest 2D and 3D test crash 5070 TI - Solved

[David (PassMark)]

In case someone else comes across the same issue:

Hardware:
Intel Core i5-12600K
UHD Graphics 770 + GeForce RTX 5070 Ti video cards
nVidia Driver version: 572.70
Windows 11 Professional Edition build 26100
4 x 16GB RAM.

Symptoms:
Following the upgrade of the video card from an older AMD 6750 XT, to a nVidia 5070 Ti, the system was unstable and crashed running PerformanceTest 2D and 3D tests.
A install of the latest nvidia drivers was done when the 5070TI was installed.

These tests caused a crash.
2D Graphics: Image Rendering
2D Graphics: Direct 2D SVG
3D Graphics: DirectX 10

Crash dumps were produced for each crash. All the crashes were, ExceptionCode: c0000005 (Access violation), which is one of the most vague, but also the most common errors. Access violation can be both a software and hardware fault.

Crash dumps

Detailed analysis of multiple crash dumps & stack traces always showed a crash in d3d11.dll. (The DirectX 11, graphics library DLL)

Example 1:

d3d11!C10and11Resource<ID3D11Texture2D1,ID3D10Texture2D>::GetType
d2d1!DrawingContext::CreateBitmapFromDxgiSurface+0 x48d
d2d1!D2DDeviceContextBase<ID2D1DeviceContext7,ID2D 1DeviceContext7,null_type>::CreateBitmapFromDxgiSurface+0xee
PerformanceTest64+0x25fdef​

Example 2:

d3d11!CLayeredObject<CClassLinkage>::CContainedObject::QueryInterface+0x8
PerformanceTest64+0x29c2c8
0x32f6a2a8
0x23e1ebd8
0x705bbc0
NvPresent64+0x8d86c​

Solution:
Various tests were run. But in the end the solution was deleting the nVidia drivers and doing a second install.
Customer later said the initial driver install was done in parallel with major Windows update. There is no real reason for this not to work, but it seems something was corrupted or inconsistent. Re-installing the video drivers immediately fixed all the various crashes.

[pbaudis]

You are right, the problem occurs whenever there is a graphics card test, both internal and external. A separate test of the processor, RAM, SSD is fine.
Yesterday everything was fine and today there is a problem, I don't understand it, I haven't made any changes since yesterday. Goblin.

Notebook:

AMD Ryzen™ 7 7840HS 5,1 GHz, AMD Radeon(TM) 780M
Hynix 32GB RAM DDR5 5600MHz
NVIDIA GeForce RTX 4050 Laptop
Samsung SSD 990 EVO Plus 2TB (systém)
Samsung SSD 990 EVO Plus 4TB
Microsoft Windows 11 Pro (Win11 25H2 2025 Update)

[David (PassMark)]

Maybe there was an automated video card driver update overnight? Or Windows update?

[David (PassMark)]

Something funny going on.
We went from having 1 report of this issue, 6 months ago, to having 3 reports of the problem in 3 days (but nothing changed in our software).

Latest report was with NVIDIA GeForce RTX 5060 Ti & nVidia driver release 581.57.

One customer claimed that nVidia's "Studio" drivers crash, while the "Game ready" drivers don't crash. BUT we tested this in house with a 5060 TI card and we could not reproduce the problem with either driver. So we are suspecting that the act of re-installing the driver was what fixed it for the customer, and not swapping from Studio to Game Ready drivers.

We also looked at our code around the area where is crashed (just before the call to the driver code). The code looks OK & we know it works on millions of machines in the past. So there must be something special about the ~4 machines that have this error.

[pbaudis]

Interestingly, it crashes when testing the integrated AMD Radeon(TM) 780M graphics and the NVIDIA GeForce RTX 4050.
I reinstalled the laptop, so I'll wait for new graphics card drivers.

[pbaudis]

I performed a clean install of Windows 11 Pro, all apps and drivers. Everything is fine now, I'll probably never know why it happened, and maybe it was just a goblin...

Windows is Windows.

[David (PassMark)]

Thanks for the update. Further confirmation that something got messed up on these systems and re-install corrects it. Given that the crash was in d3d11.dll it really has to be something to do with the video card drivers.
Video card drivers have been a mess as far back as 1985.

[David (PassMark)]

And another report of this issue from another customer with the same problem. The problem occurred after a GPU upgrade. Presumably the GPU was replaced but the drivers were not updated. In this case it was a RTX 4070 Super Eagle to a Gigabyte RTX 5070 ti Gaming upgrade.