New
#21
Boozad, Oh, I understand. I will do it this evening. I am not at home now.
Stern what I meant was that an OEM cannot be transferred without permission from Microsoft but the retail version can. So which version did you have on the original board because it will flag as non valid if it was an OEM and hence your problems will start.
Microsoft are in general very obliging if you explain to the circumstances of the need to transfer the OEM version to another board - as I have done this on a few occasions not just for me but fixes I have had.
So I installed video driver from Nvidia web site and nothing changed. I will install all Windows Updates, but I don't think, that it will help...
In my opinion, problem is between Motherboard and Videocard (maybe I have to change some settings in BIOS?)
Guys, I am still having this problem. Any help?
Well it is still throwing up a graphics driver failure. Now I have seen on the GeForce forum several refs to just uninstalling the NVidia stuff and reinstalling it (which I know you are fed up with but is what I would do until the installed driver does not BSOD) and it might be an idea to start with an older one and work upwards again something I would do.Code:VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: fffffa8005a8e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff880049046c0, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 0000000000000002, Optional internal context dependent data. Debugging Details: ------------------ FAULTING_IP: nvlddmkm+d06c0 fffff880`049046c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`052cd078)],0 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x116 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre STACK_TEXT: fffff880`0370d988 fffff880`03aa9140 : 00000000`00000116 fffffa80`05a8e010 fffff880`049046c0 00000000`00000000 : nt!KeBugCheckEx fffff880`0370d990 fffff880`03aa8e4a : fffff880`049046c0 fffffa80`05a8e010 fffffa80`05aefd50 fffffa80`05aed010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`0370d9d0 fffff880`03b4ff13 : fffffa80`05a8e010 00000000`00000000 fffffa80`05aefd50 fffffa80`05aed010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`0370da00 fffff880`03b79cf1 : 00000000`ffffffff 00000000`000008b9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`0370dae0 fffff880`03b78437 : 00000000`00000102 00000000`00000000 00000000`000008b9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71 fffff880`0370db10 fffff880`03b4b2d2 : ffffffff`ff676980 fffffa80`05aed010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb fffff880`0370dbb0 fffff880`03b77ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`04db3c58 : dxgmms1!VidSchiScheduleCommandToRun+0x1da fffff880`0370dcc0 fffff800`02b5e2ea : 00000000`060baa11 fffffa80`05eedb50 fffffa80`0396d4a0 fffffa80`05eedb50 : dxgmms1!VidSchiWorkerThread+0xba fffff880`0370dd00 fffff800`028b28e6 : fffff800`02a3ce80 fffffa80`05eedb50 fffff800`02a4acc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`0370dd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+d06c0 fffff880`049046c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`052cd078)],0 SYMBOL_NAME: nvlddmkm+d06c0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c8387 FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x116_image_nvlddmkm.sys FAILURE_ID_HASH: {1f9e0448-3238-5868-3678-c8e526bb1edc} Followup: MachineOwner
Hey John. I'm not at my PC at the moment so can't take a look at the dumps, but a 0x116 could well be down to a failing card, the PCI-e slot or mayBe the PSU so if driver replacements aren't working it may be worth giving the GPU itself a test, if all's good try a different PCI-e slot if possible.
I'll be at my PC later so I'll look back in.
Like I said, even after reinstalling Windows, I had the same BSOD (without nVidia drivers installed yet).
- Same card on different motherboard works fine.
- This motherboard with onboard card works fine.
- BSOD is ONLY when I start computer FIRST time after about 10 minutes shutdown (or after changing BIOS settings to default)
Maybe it is PCI-E port problem. I will try to find another videocard to test.
Any other opinions?