Both dumpfiles are:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {18, 0, ffffd00130c79180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd00130c79180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
As you can read the dump file does not point to something specific.
Usual causes of this bugcheck: Device driver, BIOS bug, hardware defect (see Significant Posts section below)
Bios: you have already the latest version 1.1.4. but it is from 2009!
Drivers:
Looking through your driver modules:
tpg64win7 Wed Nov 23 16:00:40 2011
Driver Description: TP-link Gigabit PCI Express network adapter driver
Driver Update Site:
Support - Welcome to TP-LINK or OEM
ccSetx64 Tue Sep 24 05:58:04 2013
Ironx64 Mon Dec 01 18:53:06 2014
SYMEVENT64x86 Fri Jan 16 03:53:56 2015 (54B87D44)
SYMNETS Fri Oct 03 00:14:05 2014
All drivers related to Norton/symentics but there also drivers from may 2016 from symentec.
Where there recently a install/update of Norton/Symentec products without maybe removing old drivers.
So the installation may become corrupted.
Remove/uninstal with Norton Removal Tool and reinstall.
Hope this will get you starting and hopefully it will stop the BSOD.