Display driver nvlddmkm stopped responding and has successfully recovered

Bz-eonar · July 27, 2019, 12:02pm

Random freezing and these events:

Event 4101: Display driver nvlddmkm stopped responding and has successfully recovered.

AND

Fault bucket 2176052966283781092, type 5

Event Name: D3DDRED2

Response: Not available

Cab Id: 0

Problem signature:

P1: VEN_10DE

P2: 26.21.14.3160

P3: 0x887A0006

P4: 3

P5: Wow.exe

P6: 8.2.0.31229

P7:

P8:

P9:

P10:

Attached files:

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERECF0.tmp.WERInternalMetadata.xml](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WERECF0.tmp.WERInternalMetadata.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED20.tmp.xml](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WERED20.tmp.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED1F.tmp.csv](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WERED1F.tmp.csv)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERED4F.tmp.txt](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WERED4F.tmp.txt)

These files may be available here:

[\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_10DE_6aa1b080f79856ae899190f4f572209ebabd7b9c_00000000_0d764b32-1d34-4450-861c-8214beb413b6](file://%3f/C:/ProgramData/Microsoft/Windows/WER/ReportArchive/NonCritical_VEN_10DE_6aa1b080f79856ae899190f4f572209ebabd7b9c_00000000_0d764b32-1d34-4450-861c-8214beb413b6)

Analysis symbol:

Rechecking for solution: 0

Report Id: 0d764b32-1d34-4450-861c-8214beb413b6

Report Status: 268435456

Hashed bucket: 18a96046d8f879ef8e32e4a4c3c7a3e4

Cab Guid: 0

OR

Fault bucket , type 0

Event Name: LiveKernelEvent

Response: Not available

Cab Id: 0

Problem signature:

P1: 141

P2: ffffd302505ea460

P3: fffff8079eb94710

P4: 0

P5: 2770

P6: 10_0_18362

P7: 0_0

P8: 768_1

P9:

P10:

Attached files:

[\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190727-0630.dmp](file://%3f/C:/WINDOWS/LiveKernelReports/WATCHDOG/WATCHDOG-20190727-0630.dmp)

[\?\C:\WINDOWS\TEMP\WER-122285109-0.sysdata.xml](file://%3f/C:/WINDOWS/TEMP/WER-122285109-0.sysdata.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER134.tmp.WERInternalMetadata.xml](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER134.tmp.WERInternalMetadata.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER154.tmp.xml](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER154.tmp.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER165.tmp.csv](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER165.tmp.csv)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER175.tmp.txt](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER175.tmp.txt)

These files may be available here:

[\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_69d25c3562d2cac4e6a0a46b7412e7a2f13689ec_00000000_cab_28d30ca7-a1b1-4496-96ca-1bd2aebc688b](file://%3f/C:/ProgramData/Microsoft/Windows/WER/ReportQueue/Kernel_141_69d25c3562d2cac4e6a0a46b7412e7a2f13689ec_00000000_cab_28d30ca7-a1b1-4496-96ca-1bd2aebc688b)

Analysis symbol:

Rechecking for solution: 0

Report Id: 28d30ca7-a1b1-4496-96ca-1bd2aebc688b

Report Status: 4

Hashed bucket:

Cab Guid: 0

OR

Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_SCG3D, type 0

Event Name: LiveKernelEvent

Response: Not available

Cab Id: 1648764d-4f5f-4b9e-b58c-888c9e7126e4

Problem signature:

P1: 141

P2: ffffd302505ea460

P3: fffff8079eb94710

P4: 0

P5: 2770

P6: 10_0_18362

P7: 0_0

P8: 768_1

P9:

P10:

Attached files:

[\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20190727-0630.dmp](file://%3f/C:/WINDOWS/LiveKernelReports/WATCHDOG/WATCHDOG-20190727-0630.dmp)

[\?\C:\WINDOWS\TEMP\WER-122285109-0.sysdata.xml](file://%3f/C:/WINDOWS/TEMP/WER-122285109-0.sysdata.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER134.tmp.WERInternalMetadata.xml](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER134.tmp.WERInternalMetadata.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER154.tmp.xml](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER154.tmp.xml)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER165.tmp.csv](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER165.tmp.csv)

[\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER175.tmp.txt](file://%3f/C:/ProgramData/Microsoft/Windows/WER/Temp/WER175.tmp.txt)

[\?\C:\Windows\Temp\WER4E6B.tmp.WERDataCollectionStatus.txt](file://%3f/C:/Windows/Temp/WER4E6B.tmp.WERDataCollectionStatus.txt)

These files may be available here:

[\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_69d25c3562d2cac4e6a0a46b7412e7a2f13689ec_00000000_cab_28d30ca7-a1b1-4496-96ca-1bd2aebc688b](file://%3f/C:/ProgramData/Microsoft/Windows/WER/ReportArchive/Kernel_141_69d25c3562d2cac4e6a0a46b7412e7a2f13689ec_00000000_cab_28d30ca7-a1b1-4496-96ca-1bd2aebc688b)

Analysis symbol:

Rechecking for solution: 0

Report Id: 28d30ca7-a1b1-4496-96ca-1bd2aebc688b

Report Status: 2147483648

Hashed bucket:

Cab Guid: 0

It keeps going….

Tratt-proudmoore · July 27, 2019, 6:09pm

Hi Bz

It is my understanding that the game Devs and Nvidia are working on this D3DDRED2 event issue. I would open a ticket on this - here is the link:

https://us.battle.net/support/en/help/product/wow/158/164/channels

I would put D3DDRED2 error in the header.

Bz-eonar · July 27, 2019, 8:45pm

Submitted. Thx

Tak-blackwater-raiders · July 28, 2019, 7:03am

Same issue! Thanks for posting

Zeralor-illidan · July 31, 2019, 11:30pm

Hey you guys with the issue, may I ask what GPU you’re running? I’ve noticed that most people reporting this issue (myself included) are using GTX 1060 3GB/6GB graphics cards and I’m starting to think that this is more than just coincidence.

Jambrix · August 4, 2020, 1:38am

2 posts were merged into an existing topic: Display driver stopped working and recovered