PC crashing *R-R-R-R-R*
Go to solution
Solved by ionbasa,
So all of the dump files point to the nvidia driver. You mentioned you were running 344.16, can you please try updating to this driver here: http://www.nvidia.com/download/driverResults.aspx/79891/en-us
The driver I linked to is version 344.75.
The dump file pretty much point out one issues: VIDEO_TDR_FAILURE.
Here is the a debug output for informational purposes:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506Machine Name:Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328c890Debug session time: Fri Nov 21 16:01:49.223 2014 (UTC - 5:00)System Uptime: 0 days 0:39:38.410******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************VIDEO_TDR_FAILURE (116)Attempt to reset the display driver and recover from timeout failed.Arguments:Arg1: fffffa800a5914e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).Arg2: fffff8800f940828, 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 2FAULTING_IP: nvlddmkm+921828fffff880`0f940828 48ff2591bbecff jmp qword ptr [nvlddmkm+0x7ed3c0 (fffff880`0f80c3c0)]DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULTCUSTOMER_CRASH_COUNT: 1BUGCHECK_STR: 0x116PROCESS_NAME: SystemCURRENT_IRQL: 0STACK_TEXT: fffff880`04f46a48 fffff880`0fd5c134 : 00000000`00000116 fffffa80`0a5914e0 fffff880`0f940828 ffffffff`c000009a : nt!KeBugCheckExfffff880`04f46a50 fffff880`0fd2f867 : fffff880`0f940828 fffffa80`094fb000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xecfffff880`04f46a90 fffff880`0fd5bf43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0a5914e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3fffff880`04f46b40 fffff880`03a3803d : fffffa80`07914010 00000000`00000080 00000000`00000000 fffffa80`09484410 : dxgkrnl!TdrResetFromTimeout+0x23fffff880`04f46bc0 fffff800`0335a73a : 00000000`00f369c3 fffffa80`091a6b50 fffffa80`066e4990 fffffa80`091a6b50 : dxgmms1!VidSchiWorkerThread+0x101fffff880`04f46c00 fffff800`030af8e6 : fffff800`03239e80 fffffa80`091a6b50 fffff800`03247cc0 00000000`00000040 : nt!PspSystemThreadStartup+0x5afffff880`04f46c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP: nvlddmkm+921828fffff880`0f940828 48ff2591bbecff jmp qword ptr [nvlddmkm+0x7ed3c0 (fffff880`0f80c3c0)]SYMBOL_NAME: nvlddmkm+921828FOLLOWUP_NAME: MachineOwnerMODULE_NAME: nvlddmkmIMAGE_NAME: nvlddmkm.sysDEBUG_FLR_IMAGE_TIMESTAMP: 5463c853FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sysBUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sysFollowup: MachineOwner
If even after updating the driver, and still experience these crashes, try rolling back to a previous driver version. If that still does not work, it may possibly be a bad GPU, and I would recommend getting it RMA'd.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now