Hi!
I'm having some issues lately, I've been playing Alien Isolation for some time now and changed my graphic card this past Christmas.
So, now, when I play the game, it just randomly reboot the computer (sometimes after a few seconds, sometimes after a couple of hours).
I tried a lot of things:
- Properly removing my drivers and re-installing them
- Ran several benchmarks: furmark, heavenly, memtest86: no problems detected, the temperature of the card are fine (max 70C after ~40 minutes of furmark)
- Ran a chkdsk on both my system drive and the drive where the game is located
- Did an antivirus scan (with avast free) and anti-malware scan (with malwarebytes)
I don't know if the crashes are related but my girlfriend used my computer a couple of weeks ago and installed by mistake a whole lot of crap (a couple of viruses and tons of malware, she basically clicked on one of these false "download" links and installed what came from that >_<).
I also have been playing another game quite a lot the past two weeks, but one that is very low on the graphic requirements and had no issues whatsoever.
Here are my specs:
MB: ASRocks Z97 Pro3
Proc: i5 4690
GC: GIGABYTE GV-N970IXOC-4GD GeForce GTX 970 4GB 256-B
Psu: Corsair Professional Series Gold AX750
OS: Windows 7 ultimate
Here is a copy/paste of the crash dump I get after the bsod:
Would any of you have any idea of where this could come from? I don't think it's related to the hardware because the benchmarks and stress tests ran fine, but I tried a lot of stuff to fix the software end with no chance (I'm not yet thinking of reformatting but that might happen sooner than later).
I'm having some issues lately, I've been playing Alien Isolation for some time now and changed my graphic card this past Christmas.
So, now, when I play the game, it just randomly reboot the computer (sometimes after a few seconds, sometimes after a couple of hours).
I tried a lot of things:
- Properly removing my drivers and re-installing them
- Ran several benchmarks: furmark, heavenly, memtest86: no problems detected, the temperature of the card are fine (max 70C after ~40 minutes of furmark)
- Ran a chkdsk on both my system drive and the drive where the game is located
- Did an antivirus scan (with avast free) and anti-malware scan (with malwarebytes)
I don't know if the crashes are related but my girlfriend used my computer a couple of weeks ago and installed by mistake a whole lot of crap (a couple of viruses and tons of malware, she basically clicked on one of these false "download" links and installed what came from that >_<).
I also have been playing another game quite a lot the past two weeks, but one that is very low on the graphic requirements and had no issues whatsoever.
Here are my specs:
MB: ASRocks Z97 Pro3
Proc: i5 4690
GC: GIGABYTE GV-N970IXOC-4GD GeForce GTX 970 4GB 256-B
Psu: Corsair Professional Series Gold AX750
OS: Windows 7 ultimate
Here is a copy/paste of the crash dump I get after the bsod:
JavaScript:
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+7a2dc0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8018a6b190, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005203dc0, 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:
------------------
FAULTING_IP:
nvlddmkm+7a2dc0
fffff880`05203dc0 48ff251996edff jmp qword ptr [nvlddmkm+0x67c3e0 (fffff880`050dd3e0)]
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`05ec6a48 fffff880`054cc134 : 00000000`00000116 fffffa80`18a6b190 fffff880`05203dc0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`05ec6a50 fffff880`0549f867 : fffff880`05203dc0 fffffa80`106c9000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05ec6a90 fffff880`054cbf43 : fffffa80`ffffd846 00000000`00000000 fffffa80`18a6b190 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`05ec6b40 fffff880`0559c03d : fffffa80`1ad201e0 00000000`00000080 00000000`00000000 fffffa80`106be410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`05ec6bc0 fffff800`0312f0ca : 00000000`0103906e fffffa80`103a7b50 fffffa80`0c6e19e0 fffffa80`103a7b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`05ec6c00 fffff800`02e83be6 : fffff880`03165180 fffffa80`103a7b50 fffff880`0316ffc0 fffffa80`0f201da0 : nt!PspSystemThreadStartup+0x5a
fffff880`05ec6c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+7a2dc0
fffff880`05203dc0 48ff251996edff jmp qword ptr [nvlddmkm+0x67c3e0 (fffff880`050dd3e0)]
SYMBOL_NAME: nvlddmkm+7a2dc0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54b0548e
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: MachineOwnerWould any of you have any idea of where this could come from? I don't think it's related to the hardware because the benchmarks and stress tests ran fine, but I tried a lot of stuff to fix the software end with no chance (I'm not yet thinking of reformatting but that might happen sooner than later).
Facebook
Twitter
Instagram