Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: my desktop pc suddenly freezes everything, while staying on.  (Read 2138 times)

0 Members and 1 Guest are viewing this topic.

nicco123

    Topic Starter


    Newbie

    • Experience: Beginner
    • OS: Unknown
    my desktop pc suddenly freezes everything, while staying on.
    « on: December 24, 2017, 02:39:26 AM »
    Hdtune trial pro test passed.
    prime95 for 1-2h passed, no anything bad happened.
    memtest86 on 16gb ram 6 full passes no errors.
    fumark stress about 1h nothing.

    I have this in watchdog, but im not sure of time, is it same when freeze or not because it shows utc wrong, and error logs are screwed with utc too in event log.
    Anyway here they are and what they say...


    Windows 8 Kernel Version 10586 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10586.338.amd64fre.th2_release.160517-1918 Machine Name: Kernel base = 0xfffff802`78c7a000 PsLoadedModuleList = 0xfffff802`78f58cf0 Debug session time: Sat Dec 23 07:33:55.502 2017 (UTC - 5:00) System Uptime: 1 days 1:15:18.540 ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the the display engines failed to respond in timely fashion. (This code can never be used for real bugcheck). Arguments: Arg1: ffffe0019f52e4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8016db27e80, The pointer into responsible device driver module (e.g owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000000000, 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+167e80 fffff801`6db27e80 ??              ??? DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_ENGINE_TIMEOUT TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b BUGCHECK_STR:  0x141 PROCESS_NAME:  System CURRENT_IRQL:  0 STACK_TEXT: ffffd000`2c74a450 fffff801`6b4a686c : ffffe001`9f52e4c0 ffffd000`2c74a5b9 00000000`00000020 00000000`00000000 : watchdog!WdDbgReportRecreate+0x104 ffffd000`2c74a4a0 fffff801`6b4a531a : ffffc002`00000000 ffffc002`0021a6f0 00000000`00000010 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xec ffffd000`2c74a4f0 fffff801`6cbe14f9 : ffffe001`94fc4058 ffffe001`94fc4058 ffffe001`9f52e4c0 ffffe001`94fc4000 : dxgkrnl!TdrCollectDbgInfoStage1+0x26a ffffd000`2c74a620 fffff801`6cc4a9d8 : ffffe001`94fc4000 00000000`00000000 00000000`00000001 ffffe001`94fc4001 : dxgmms2!VidSchiResetEngine+0x265 ffffd000`2c74a900 fffff801`6cbfa7d0 : ffffe001`945a9000 00000000`00000000 00000000`00000000 ffffe001`94fc4000 : dxgmms2!VidSchiResetEngines+0x84 ffffd000`2c74a940 fffff801`6cbfa576 : 00000000`00000002 00000000`0058c8eb 00000000`003701c9 2d7c3492`626c1b00 : dxgmms2!VidSchiCheckHwProgress+0x1c0 ffffd000`2c74a9b0 fffff801`6cbcb324 : 00000000`00000000 00000000`00000000 00000000`c0000000 2d7bf571`de308880 : dxgmms2!VidSchiWaitForSchedulerEvents+0x2e6 ffffd000`2c74aa80 fffff801`6cc2a75d : ffffe001`94ff0910 ffffd000`2c74abd0 ffffe001`94ff0900 ffffe001`945a9000 : dxgmms2!VidSchiScheduleCommandToRun+0x5a4 ffffd000`2c74ab80 fffff801`6cc2a720 : ffffe001`945a9500 ffffe001`945a9000 00000000`00000080 ffffe001`916a9000 : dxgmms2!VidSchiRun_PriorityTable+0x2d ffffd000`2c74abd0 fffff802`78d67b75 : 00000005`b59bbfff fffff802`78dc180f c6ce8b48`00010023 00000000`02af003a : dxgmms2!VidSchiWorkerThread+0x80 ffffd000`2c74ac10 fffff802`78dc1946 : ffffd000`2a260180 ffffe001`94e29840 fffff802`78d67b34 41f0348b`4c00000e : nt!PspSystemThreadStartup+0x41 ffffd000`2c74ac60 00000000`00000000 : ffffd000`2c74b000 ffffd000`2c745000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND:  .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+167e80 fffff801`6db27e80 ??              ??? SYMBOL_NAME:  nvlddmkm+167e80 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME:  nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP:  554fa593 FAILURE_BUCKET_ID:  X64_0x141_IMAGE_nvlddmkm.sys BUCKET_ID:  X64_0x141_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------
    Windows 8 Kernel Version 10586 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10586.338.amd64fre.th2_release.160517-1918 Machine Name: Kernel base = 0xfffff802`5f411000 PsLoadedModuleList = 0xfffff802`5f6efcf0 Debug session time: Wed Dec 20 01:05:57.086 2017 (UTC - 5:00) System Uptime: 7 days 13:07:26.302 ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* VIDEO_TDR_TIMEOUT_DETECTED (117) The display driver failed to respond in timely fashion. (This code can never be used for real bugcheck). Arguments: Arg1: ffffe001c25cc4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff800054f7e80, The pointer into responsible device driver module (e.g owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 0000000000001760, 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+167e80 fffff800`054f7e80 ??              ??? DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b CUSTOMER_CRASH_COUNT:  2 BUGCHECK_STR:  0x117 PROCESS_NAME:  System CURRENT_IRQL:  0 STACK_TEXT: ffffd000`9caf0a00 fffff800`0340686c : ffffe001`c25cc4c0 00000000`80000000 ffffe001`c25cc4c0 ffffe001`c07da870 : watchdog!WdDbgReportRecreate+0x104 ffffd000`9caf0a50 fffff800`03405dcf : ffffc001`00000000 ffffc001`8d5c60d0 ffffe001`c25cc4c0 ffffe001`bdbfc408 : dxgkrnl!TdrUpdateDbgReport+0xec ffffd000`9caf0aa0 fffff800`033f28c5 : ffffc001`a961c5e1 ffffe001`bdbfc3a0 ffffe001`bdbfc3a0 ffffe001`bdbfc408 : dxgkrnl!TdrCollectDbgInfoStage2+0x1df ffffd000`9caf0ad0 fffff800`034064d5 : 00000000`00000100 00000000`00000000 ffff743d`00000000 ffffe001`baec11d0 : dxgkrnl!DXGADAPTER::Reset+0x21d ffffd000`9caf0b20 fffff800`0340662b : 00000000`00000200 fffff802`5f7a4340 ffffe001`ba84d1e0 fffff800`02b30880 : dxgkrnl!TdrResetFromTimeout+0x15 ffffd000`9caf0b50 fffff802`5f453c59 : ffffe001`bea42440 fffff800`034065d0 ffffe001`c2564290 ffffe001`59706e50 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x5b ffffd000`9caf0b80 fffff802`5f4feb75 : 00000000`00000000 00000000`00000080 ffffe001`ba8a8040 ffffe001`bea42440 : nt!ExpWorkerThread+0xe9 ffffd000`9caf0c10 fffff802`5f558946 : ffffd000`4ad88180 ffffe001`bea42440 fffff802`5f4feb34 00000000`00000000 : nt!PspSystemThreadStartup+0x41 ffffd000`9caf0c60 00000000`00000000 : ffffd000`9caf1000 ffffd000`9caeb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND:  .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+167e80 fffff800`054f7e80 ??              ??? SYMBOL_NAME:  nvlddmkm+167e80 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME:  nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP:  554fa593 FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------

    Windows 8 Kernel Version 10586 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10586.338.amd64fre.th2_release.160517-1918 Machine Name: Kernel base = 0xfffff802`5f411000 PsLoadedModuleList = 0xfffff802`5f6efcf0 Debug session time: Wed Dec 20 01:05:50.094 2017 (UTC - 5:00) System Uptime: 7 days 13:07:19.310 ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * ******************************************************************************* VIDEO_TDR_TIMEOUT_DETECTED (117) The display driver failed to respond in timely fashion. (This code can never be used for real bugcheck). Arguments: Arg1: ffffe001c25cc4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff800054f7e80, The pointer into responsible device driver module (e.g owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: 00000000000027c8, 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+167e80 fffff800`054f7e80 ??              ??? DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b CUSTOMER_CRASH_COUNT:  1 BUGCHECK_STR:  0x117 PROCESS_NAME:  System CURRENT_IRQL:  0 STACK_TEXT: ffffd000`5133fa00 fffff800`0340686c : ffffe001`c25cc4c0 00000000`80000000 ffffe001`c25cc4c0 ffffe001`bf5d7830 : watchdog!WdDbgReportRecreate+0x104 ffffd000`5133fa50 fffff800`03405dcf : ffffc001`00000000 ffffc001`8a9aa610 ffffe001`c25cc4c0 ffffe001`bdbfc408 : dxgkrnl!TdrUpdateDbgReport+0xec ffffd000`5133faa0 fffff800`033f28c5 : ffffc001`a961c56c ffffe001`bdbfc3a0 ffffe001`bdbfc3a0 ffffe001`bdbfc408 : dxgkrnl!TdrCollectDbgInfoStage2+0x1df ffffd000`5133fad0 fffff800`034064d5 : ffffe001`be8a01b0 00000000`00000000 ffff743d`00000000 fffff802`5f4df664 : dxgkrnl!DXGADAPTER::Reset+0x21d ffffd000`5133fb20 fffff800`0340662b : 00000000`00000300 fffff802`5f7a4340 ffffe001`ba84d1e0 fffff800`02b30880 : dxgkrnl!TdrResetFromTimeout+0x15 ffffd000`5133fb50 fffff802`5f453c59 : ffffe001`c4c313c0 fffff800`034065d0 ffffe001`bb694b40 fffff802`5f7a4340 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x5b ffffd000`5133fb80 fffff802`5f4feb75 : 03e0c03d`3b0303a0 00000000`00000080 ffffe001`ba8a8040 ffffe001`c4c313c0 : nt!ExpWorkerThread+0xe9 ffffd000`5133fc10 fffff802`5f558946 : ffffd000`4ae80180 ffffe001`c4c313c0 fffff802`5f4feb34 30d1d621`130cc962 : nt!PspSystemThreadStartup+0x41 ffffd000`5133fc60 00000000`00000000 : ffffd000`51340000 ffffd000`5133a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND:  .bugcheck ; kb FOLLOWUP_IP: nvlddmkm+167e80 fffff800`054f7e80 ??              ??? SYMBOL_NAME:  nvlddmkm+167e80 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: nvlddmkm IMAGE_NAME:  nvlddmkm.sys DEBUG_FLR_IMAGE_TIMESTAMP:  554fa593 FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys Followup: MachineOwner ---------