Intel Motherboards - Asrock z68 Pro and Bluescreen VIDEO_TDR

Asrock z68 Pro and Bluescreen VIDEO_TDR_FAILURE

Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=4969
Printed Date: 25 Jul 2025 at 11:12pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Asrock z68 Pro and Bluescreen VIDEO_TDR_FAILURE

Posted By: Jackie
Subject: Asrock z68 Pro and Bluescreen VIDEO_TDR_FAILURE
Date Posted: 27 Apr 2017 at 2:55am

" rel="nofollow -

Hello,

I am running my Z69 Pro for some years now with my not-overclocked Core i5 2500K, and since I have inserted a NVidia 1060GTX board, hibernate under Windows 10 is not working reliably anymore. On the Nvidia forum, they say that this may be caused by a wrong BIOS, which I already upgraded to the latest version available for the Z68 Pro.

Is there any solution how to prevent that BSOD at all? Below you will find the details, feel free to ask any questions.

Thank you.

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Show DivPrimary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`1308b000 PsLoadedModuleList = 0xfffff802`133d75a0
Debug session time: Tue Apr 25 11:26:41.807 2017 (UTC - 4:00)
System Uptime: 2 days 1:20:03.468
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9c8e5c02e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff801e2a092e8, 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:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP: 
nvlddmkm+9d92e8
fffff801`e2a092e8 48ff2501a6e5ff  jmp     qword ptr [nvlddmkm+0x8338f0 (fffff801`e28638f0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

BAD_PAGES_DETECTED: 10074

STACK_TEXT:  
ffff8481`1d3bfa28 fffff801`e0a67cb8 : 00000000`00000116 ffff9c8e`5c02e010 fffff801`e2a092e8 ffffffff`c000009a : nt!KeBugCheckEx
ffff8481`1d3bfa30 fffff801`e0a48177 : fffff801`e2a092e8 ffff9c8e`52aba9e0 00000000`00002000 ffff9c8e`52abaa78 : dxgkrnl!TdrBugcheckOnTimeout+0xec
ffff8481`1d3bfa70 fffff801`e0a43588 : ffff9c8e`52abf010 00000000`04000000 00000000`00000000 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x153
ffff8481`1d3bfaa0 fffff801`e0a67455 : fffff802`13110100 ffff9c8e`5c6037c0 00000000`52f12080 ffff9c8e`5c6037c0 : dxgkrnl!DXGADAPTER::Reset+0x430
ffff8481`1d3bfb20 fffff801`e0a675a7 : 00000000`00000000 fffff802`13483380 fffff802`133d10a0 fffff802`1311e1f0 : dxgkrnl!TdrResetFromTimeout+0x15
ffff8481`1d3bfb50 fffff802`130aa1c8 : ffff9c8e`5c6037c0 fffff801`e0a67580 ffff9c8e`559f9d70 ffff9c8e`56112ee0 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff8481`1d3bfb80 fffff802`13144a37 : ffff9c8e`560857c0 00000000`00000080 ffff9c8e`4da27380 ffff9c8e`5c6037c0 : nt!ExpWorkerThread+0xd8
ffff8481`1d3bfc10 fffff802`131fc3f6 : ffff8481`19b10180 ffff9c8e`5c6037c0 fffff802`131449f0 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff8481`1d3bfc60 00000000`00000000 : ffff8481`1d3c0000 ffff8481`1d3ba000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  PAGE_NOT_ZERO

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO

Followup: MachineOwner
---------

 *** Memory manager detected 65652 instance(s) of page corruption, target is likely to have memory corruption.


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivCrash Code Links

Show DivLoaded Module List

Show DivRaw Stack Contents

Show DivDump Header Information

Show DivStrings

Replies:

Posted By: Xaltar
Date Posted: 27 Apr 2017 at 4:14am

" rel="nofollow - Gigabyte GPU by any chance?

IMO, RMA the GPU. I made the mistake of not RMAing mine believing the issue was driver related. I discovered a driver that stopped the behavior and kept my GPU (GTX 960 G1 Gaming), all seemed well until I updated my drivers again and then the issue returned, even a fresh install with the driver I had thought fixed the issue did not resolve the problem. Now, well out of warranty I can not return the card and the issue has gotten worse.

Don't make my mistake, return it and get another brand/model. If you encounter the same issue with a new different GPU then look at other potential causes. GPUs are one of the most pricey components in a system and I have learned the hard way not to take chances on them.

You can try uninstalling drivers using DDU (display driver uninstaller) then install the latest and see if the issue persists but honestly, TDR issues are a nightmare and usually tied to the GPU's VRMs and boost setup. I can probably "fix" my issues by flashing my GPU to a custom vBIOS that disables boost and voltage variation entirely but I would lose my power saving....

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

Posted By: Jackie
Date Posted: 27 Apr 2017 at 12:08pm

" rel="nofollow - Actually, this is a Gainward GOlden sample, and I have found others having the same problem on the net. People keep saying this only happens when WIndows 10 Quickstart is enabled and/or you are using hibernate, which I regularely do, and that this happens due to BIOS incompatibilities. So I guess I could RMA the card since it is brand new, but I will probably have the same problems again unless:

- Asrock releases a BIOS fix for this issue for the Z68 Pro or

- I do not use Windows 10 quickstart and hibernate anymore, which will be a convenience problem then.

Any chance Asrock will update their BIOS for that board, or at least look into that issue?

see for reference: https://forums.geforce.com/default/topic/980711/geforce-drivers/bsod-quot-overlapped_module-address-regions-for-hiber_iastora-and-nvvad64v-sys-overlap-quot-/

Posted By: Xaltar
Date Posted: 27 Apr 2017 at 2:25pm

Z68 platforms are long past end of life but you could try tech support directly, they have been known to help out with things like this in the past.

http://event.asrock.com/tsd.asp

It can take a while for them to get back to you.

Rereading your post, this issue only happens when coming out of hibernate? If so then it is not the same issue I have with my GPU. If the GPU is stable in every other scenario then don't waste your time with an RMA. In my case the GPU TDRs when it changes power states so when I open a video (not every time) and it jumps from idle to "media" mode or from desktop into a game etc. The issue in my situation is tied to poor handling of the GPUs power saving features.

I felt I should clarify to avoid confusion. TDRs are a common issue that can have a huge number of causes. Most of them stem from a bad/defective GPU or driver issues. Your situation does indeed sound like a configuration issue ,older board, new GPU and lacking BIOS support.

Good luck

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

Posted By: Jackie
Date Posted: 29 Apr 2017 at 1:28am

Actually, I did RMA the card, and with the new one (Gainward Golden Sample) the same happens, so this is definitely a driver/BIOS issue...