DDU freezes my PC while cleaning!

netuser
Posts: 13
Joined: Sat Jan 28, 2017 5:06 am

DDU freezes my PC while cleaning!

Post by netuser »

Hello,
Ever since 376.33 when i try to clean my System with DDU in Safemode it freezes which then leads to a BSOD.
Today i tried to clean 378.57, i ran DDU twice and the second time around it created log files.

Otherwise my System is Stable.
I have two Display's, one is connected through DP the other through DVI.

any idea what's causing this ?
You do not have the required permissions to view the files attached to this post.

DDU freezes my PC while cleaning!

Sponsor

Sponsor
 

User avatar
Wagnard
Site Admin
Posts: 1675
Joined: Sat Jul 04, 2015 5:18 pm
Location: 127.0.0.1
Contact:

Re: DDU freezes my PC while cleaning!

Post by Wagnard »

netuser wrote: Tue Feb 14, 2017 1:52 pm Hello,
Ever since 376.33 when i try to clean my System with DDU in Safemode it freezes which then leads to a BSOD.
Today i tried to clean 378.57, i ran DDU twice and the second time around it created log files.

Otherwise my System is Stable.
I have two Display's, one is connected through DP the other through DVI.

any idea what's causing this ?
also give us the .DMP that was generated for analysis. (C:\windows\memory.dmp or in c:\windows\minidump or c:\windows\LiveKernelReports)

You may have more than 1 , just check the date/time of the .DMP
netuser
Posts: 13
Joined: Sat Jan 28, 2017 5:06 am

Re: DDU freezes my PC while cleaning!

Post by netuser »

So i checked all 3 locations but there is no file named memory.dmp, the only dmp file is named "PdcLockWatchdog-20170209-1741".
Since there was no memory.dmp, i tried generating one.
Fired up DDU (in Safemode), it froze again and BSOD with a "MACHINE_CHECK_EXEPTION" error message.
Checked all 3 locations again, but still no files named memory.dmp.
User avatar
Wagnard
Site Admin
Posts: 1675
Joined: Sat Jul 04, 2015 5:18 pm
Location: 127.0.0.1
Contact:

Re: DDU freezes my PC while cleaning!

Post by Wagnard »

netuser wrote: Wed Feb 15, 2017 3:43 pm So i checked all 3 locations but there is no file named memory.dmp, the only dmp file is named "PdcLockWatchdog-20170209-1741".
Since there was no memory.dmp, i tried generating one.
Fired up DDU (in Safemode), it froze again and BSOD with a "MACHINE_CHECK_EXEPTION" error message.
Checked all 3 locations again, but still no files named memory.dmp.
THe other dmps will do, no need to be exactly named memory.dmp.
just send the one that has the good time/date to be sure its the one related to your bsod.
netuser
Posts: 13
Joined: Sat Jan 28, 2017 5:06 am

Re: DDU freezes my PC while cleaning!

Post by netuser »

tried generating a memory.dmp again, and it seem's even the BSOD freezes.
The part were it's supposed to gather data and reboot just sits at 0% forever, and the only other .dmp file is the one i mentioned earlier.
But that file is 3.6GB in size uncompressed and 680MB compressed. And it might not be related do this because i'am not sure if i did use DDU that Day.
Where should i upload the file ?
User avatar
Wagnard
Site Admin
Posts: 1675
Joined: Sat Jul 04, 2015 5:18 pm
Location: 127.0.0.1
Contact:

Re: DDU freezes my PC while cleaning!

Post by Wagnard »

netuser wrote: Fri Feb 17, 2017 6:58 am tried generating a memory.dmp again, and it seem's even the BSOD freezes.
The part were it's supposed to gather data and reboot just sits at 0% forever, and the only other .dmp file is the one i mentioned earlier.
But that file is 3.6GB in size uncompressed and 680MB compressed. And it might not be related do this because i'am not sure if i did use DDU that Day.
Where should i upload the file ?
Sent you a PM, tell me when it's uploaded.
netuser
Posts: 13
Joined: Sat Jan 28, 2017 5:06 am

Re: DDU freezes my PC while cleaning!

Post by netuser »

Have you had a chance to look at the file ?
User avatar
Wagnard
Site Admin
Posts: 1675
Joined: Sat Jul 04, 2015 5:18 pm
Location: 127.0.0.1
Contact:

Re: DDU freezes my PC while cleaning!

Post by Wagnard »

netuser wrote: Wed Feb 22, 2017 7:50 am Have you had a chance to look at the file ?
Sorry for the delay.
Here is the details of your dmp.

Code: Select all

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ghislain Harvey\Desktop\PdcLockWatchdog-20170209-1741.dmp]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff802`5ba86000 PsLoadedModuleList = 0xfffff802`5bd8b060
Debug session time: Thu Feb  9 11:41:37.425 2017 (UTC - 5:00)
System Uptime: 0 days 7:24:20.155
Loading Kernel Symbols
...............................................................
....Page d0b6d not present in the dump file. Type ".hh dbgerr004" for details
.......Page 5b6a not present in the dump file. Type ".hh dbgerr004" for details
.....................................................
...................................................
Loading User Symbols

Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 17C, {ffffd4057ade0800, 5, 0, 0}

Page 5b6a not present in the dump file. Type ".hh dbgerr004" for details
Page 5b6a not present in the dump file. Type ".hh dbgerr004" for details
Page d0b6d not present in the dump file. Type ".hh dbgerr004" for details
Page d0b6d not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : pdc.sys ( pdc!PdcpLockWatchdogWorkerRoutine+41 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PDC_LOCK_WATCHDOG_LIVEDUMP (17c)
A thread has been holding the PDC lock for too long
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffd4057ade0800, The thread holding the PDC lock.
Arg2: 0000000000000005, pdc!PdcLockWatchdogTimeout [seconds].
Arg3: 0000000000000000, Reserved.
Arg4: 0000000000000000, Reserved.

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  14393.693.amd64fre.rs1_release.161220-1747

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1903

BIOS_DATE:  08/19/2013

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  MAXIMUS V GENE

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

DUMP_FILE_ATTRIBUTES: 0x10
  Live Generated Dump

BUGCHECK_P1: ffffd4057ade0800

BUGCHECK_P2: 5

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CPU_COUNT: 4

CPU_MHZ: d48

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3a

CPU_STEPPING: 9

CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 1B'00000000 (cache) 1B'00000000 (init)

DEFAULT_BUCKET_ID:  WINBLUE_LIVE_KERNEL_DUMP

BUGCHECK_STR:  0x17C

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-2NJ5Q82

ANALYSIS_SESSION_TIME:  02-22-2017 10:20:35.0800

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8025be539f5 to fffff8025be5dd53

STACK_TEXT:  
ffffe601`c044d6e0 fffff802`5be539f5 : ffffffff`ffffffff 00000000`00000001 00000000`0041f000 00000000`00412d90 : nt!IopLiveDumpEndMirroringCallback+0x7b
ffffe601`c044d730 fffff802`5be5da17 : ffffe601`c044d848 fffff802`00000008 ffffd405`00000000 0000003e`00000000 : nt!MmDuplicateMemory+0x775
ffffe601`c044d810 fffff802`5c0af1db : ffffd405`d0e95870 ffffd405`d0e95870 ffffe601`c044dad8 ffffe601`c044dad8 : nt!IopLiveDumpCaptureMemoryPages+0x7f
ffffe601`c044d8d0 fffff802`5c0a5048 : 00000000`00000000 ffffc48d`c19c4910 ffffc48d`c6b6dd30 ffffc48d`c19c4910 : nt!IoCaptureLiveDump+0x28b
ffffe601`c044da70 fffff802`5c0a4ebe : ffffffff`800009ec 00000000`00000000 00000000`00000000 00000000`0000017c : nt!DbgkpWerCaptureLiveFullDump+0x128
ffffe601`c044dad0 fffff80d`5ba61071 : ffffd405`e580b040 fffff80d`5ba61030 fffff80d`5ba58d28 fffff802`5be43280 : nt!DbgkWerCaptureLiveKernelDump+0x19a
ffffe601`c044db20 fffff802`5bb1d1b9 : fffff802`5be43100 fffff802`5bd85460 fffff802`00000000 fffff80d`60de4d10 : pdc!PdcpLockWatchdogWorkerRoutine+0x41
ffffe601`c044db80 fffff802`5ba88729 : 00000000`00000030 00000000`00000080 ffffd405`79ea56c0 ffffd405`e580b040 : nt!ExpWorkerThread+0xe9
ffffe601`c044dc10 fffff802`5bbd5bb6 : fffff802`5bdc8180 ffffd405`e580b040 fffff802`5ba886e8 00000000`00000246 : nt!PspSystemThreadStartup+0x41
ffffe601`c044dc60 00000000`00000000 : ffffe601`c044e000 ffffe601`c0448000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  720c8842ceafa93b7d921485c2dc6e6d1d8cdc9f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3e840955912f851a841ffc3bb473ba693187b31e

THREAD_SHA1_HASH_MOD:  ad9b8ea972bc4b0b5ac34e79d800413937c79a54

FOLLOWUP_IP: 
pdc!PdcpLockWatchdogWorkerRoutine+41
fffff80d`5ba61071 4883c458        add     rsp,58h

FAULT_INSTR_CODE:  58c48348

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  pdc!PdcpLockWatchdogWorkerRoutine+41

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: pdc

IMAGE_NAME:  pdc.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57b7e1d2

BUCKET_ID_FUNC_OFFSET:  41

FAILURE_BUCKET_ID:  LKD_0x17C_pdc!PdcpLockWatchdogWorkerRoutine

BUCKET_ID:  LKD_0x17C_pdc!PdcpLockWatchdogWorkerRoutine

PRIMARY_PROBLEM_CLASS:  LKD_0x17C_pdc!PdcpLockWatchdogWorkerRoutine

TARGET_TIME:  2017-02-09T16:41:37.000Z

OSBUILD:  14393

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-12-21 01:50:57

BUILDDATESTAMP_STR:  161220-1747

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.693.amd64fre.rs1_release.161220-1747

ANALYSIS_SESSION_ELAPSED_TIME: 4a9

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:lkd_0x17c_pdc!pdcplockwatchdogworkerroutine

FAILURE_ID_HASH:  {abbfa659-7794-4fad-eb25-b156cbce98a0}

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

What it means is something around Power. A lock took way longer to activate than normal. I know its not precise, but I would try to remove all unnecessary thing that was plug an try to find the culprit. It could also be something power related, not sure if you are overclocked.
netuser
Posts: 13
Joined: Sat Jan 28, 2017 5:06 am

Re: DDU freezes my PC while cleaning!

Post by netuser »

Unplugged everything expect Mouse&Keyboard, reverted back to stock clocks. Still freezes and crashes with a "Machine_Exception_Code".
No new .dmp files created.
Also used chkdsk and sfc to scan for error's, but no error's were detected. Next i will run mentest.
If everything else does not reveal any error's i will reinstall Windows.
User avatar
Wagnard
Site Admin
Posts: 1675
Joined: Sat Jul 04, 2015 5:18 pm
Location: 127.0.0.1
Contact:

Re: DDU freezes my PC while cleaning!

Post by Wagnard »

netuser wrote: Sat Feb 25, 2017 8:26 am Unplugged everything expect Mouse&Keyboard, reverted back to stock clocks. Still freezes and crashes with a "Machine_Exception_Code".
No new .dmp files created.
Also used chkdsk and sfc to scan for error's, but no error's were detected. Next i will run mentest.
If everything else does not reveal any error's i will reinstall Windows.
Keep up posted!
It could also be due to the recent nvidia driver that bugged when getting removed , who knows...
anyway let us know.
Post Reply