BSoD froze while when dumping physical memory reachers to 85

Hiya

Just a while ago I updated my adobe flash playing and got a BSoD right away when I just started playing a video on youtube. On the BSoD when it was dumping physical memory it reaches to 85 and stopped, then after like 10 seconds the computer restarted.

Now I'm kinda worried would my computer be ok if the BSoD froze when it was dumping it's physical memory 85? Will it corrupt any files on my windows OS or create any problems? Sorry for all the question and many thanks in advance.

Here's my dump file record

Code:

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

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880030f9180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`08eb9528 fffff800`034deb0a : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`030f9180 : nt!KeBugCheckEx
fffff880`08eb9530 fffff800`034917e7 : fffffa80`00000000 fffff800`00000006 00000000`00002711 fffff880`010c8bcf : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`08eb95c0 fffff800`03a03895 : fffff800`03a29460 fffff880`08eb9770 fffff800`03a29460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`08eb96c0 fffff800`03484193 : 00000000`68dde758 fffff800`03603e80 fffff800`03603e80 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`08eb96f0 fffff800`0348caf6 : fffff800`03603e80 fffff880`00000001 00000000`00000000 fffff880`08eb9978 : nt!KiInterruptDispatchNoLock+0x163
fffff880`08eb9880 fffff800`034cba2c : fffff880`08eb9c58 00000000`00000000 00000000`00000000 fffff800`034c9de1 : nt!KeFlushMultipleRangeTb+0x266
fffff880`08eb9950 fffff800`034c8821 : fffffa80`06bb8790 00000000`00000000 fffff880`08eb9c58 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`08eb9a50 fffff800`034cc1f6 : fffffa80`064ade70 00000000`00000001 fffffa80`00000001 fffffa80`00001000 : nt!CcFlushCache+0x561
fffff880`08eb9b50 fffff800`034ccbb8 : 00000000`00000000 fffff880`08eb9c58 fffffa80`09502ad0 fffff800`0368f8b8 : nt!CcWriteBehind+0x1c6
fffff880`08eb9c00 fffff800`03490ca9 : fffffa80`055827d0 fffff800`03781c01 fffff800`0368f8c0 00000000`00000002 : nt!CcWorkerThread+0x1c8
fffff880`08eb9cb0 fffff800`0372834a : 00000000`00000003 fffffa80`06bb8790 00000000`00000080 fffffa80`054ed040 : nt!ExpWorkerThread+0x111
fffff880`08eb9d40 fffff800`03478946 : fffff880`0316a180 fffffa80`06bb8790 fffff880`031750c0 00000000`b7172000 : nt!PspSystemThreadStartup+0x5a
fffff880`08eb9d80 00000000`00000000 : fffff880`08eba000 fffff880`08eb4000 fffff880`08eb8d30 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE

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

Follow the guide: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

If any clarification is needed, ask for it.