Only 130 Windows Updates installed. Most windows 8 systems have 160 or more. Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
The BSOD of your Dumpfiles is a BugCheck 51, {1, fffff8a000982010, 955040b7, 1c0} Probably caused by : ntkrnlmp.exe
When a Windows/system driver like ntkrnlmp.exe is blamed when experiencing a BSO
it's most likely not the problem. Most of the time further analysis is needed to determine the actual cause.
Code:
BugCheck 51, {1, fffff8a000882010, 955040b7, 1c0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+11bdc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry. If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.
Arguments:
Arg1: 0000000000000001, (reserved)
Arg2: fffff8a000882010, (reserved)
Arg3: 00000000955040b7, depends on where Windows bugchecked, may be pointer to hive
Arg4: 00000000000001c0, depends on where Windows bugchecked, may be return code of
HvCheckHive if the hive is corrupt.
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x51
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from fffff8034ae5629c to fffff8034a8d6440
STACK_TEXT:
fffff880`09daa918 fffff803`4ae5629c : 00000000`00000051 00000000`00000001 fffff8a0`00882010 00000000`955040b7 : nt!KeBugCheckEx
fffff880`09daa920 fffff803`4ac75e65 : fffff8a0`0b03afd0 00000000`04939fe8 fffff8a0`0b03a000 fffff8a0`0b03afd0 : nt! ?? ::NNGAKEGL::`string'+0x11bdc
fffff880`09daa970 fffff803`4ac76d9f : 00000000`00000000 fffff8a0`00882010 fffff8a0`00882670 00000000`00000000 : nt!HvFreeCell+0x179
fffff880`09daa9f0 fffff803`4ac6c691 : 00000000`00000000 fffff8a0`0ae6751c fffff8a0`00882010 fffff8a0`00882670 : nt!CmpFreeValueData+0x3f
fffff880`09daaa20 fffff803`4ac52e80 : 01cf4864`7a5d05a7 fffff880`09daaad9 00000000`04766518 fffff8a0`0ae6751c : nt!CmpFreeKeyByCell+0xf1
fffff880`09daaa70 fffff803`4ac53997 : fffff8a0`01a56e50 fffff880`09daab01 00000000`00000001 00000000`0000000f : nt!CmDeleteKey+0x200
fffff880`09daab40 fffff803`4a8d5453 : fffffa80`06fa7400 fffffa80`06fa7400 00000000`0000018c 00000000`00000000 : nt!NtDeleteKey+0x2a3
fffff880`09daac40 000007fa`23ef380b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000055`5cdbcf68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fa`23ef380b
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+11bdc
fffff803`4ae5629c cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::NNGAKEGL::`string'+11bdc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51a966cd
IMAGE_VERSION: 6.2.9200.16628
BUCKET_ID_FUNC_OFFSET: 11bdc
FAILURE_BUCKET_ID: 0x51_nt!_??_::NNGAKEGL::_string_
BUCKET_ID: 0x51_nt!_??_::NNGAKEGL::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x51_nt!_??_::nngakegl::_string_
FAILURE_ID_HASH: {e5bde1d4-9584-25e7-f283-f0bca450261c}
Followup: MachineOwner
---------
Your registry has problems, try repairing your registry with Ccleaner you can download a free version from here
https://www.piriform.com/ccleaner/download
There are many WER(= Windows Error Report) with mention of APPcrashes with Ntdll.dll and Wmp.dll errors.
The causes of these errors are diverce.
Run the
http://www.eightforums.com/tutorials/3047-sfc-scannow-command-run-windows-8-a.html to replace a missing or corrupt copy of the wmp.dll file or Ntdll.dll. If this DLL file is provided my Microsoft, the System File Checkertool should restore it.
Test your memory with and then test your hard drive Computer's memory and harddrive are easy to test and are the most likely components that might cause ntdll.dll or wmp.dll errors as they fail.
The tests can be found here
Diagnostics on John Caronna great site with info about BSOD.
Update your (hardware )drivers to windows 8 compatible.
Your PC HP Pavilion Slimline s5310y Desktop PC has no windows 8 compatible drivers on the HPsite.
Also i could not find a updated BIOS on the site, your BIOS is from 01/07/2010.
So you must try to find these windows 8 compatible drivers elsewhere, manufacturer sites like Intel, Nvidia, etc.
Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :
nvmf6264 Thu Apr 21 00:49:36 2011 (4daf6300) 00057d34 nvmf6264.sys
Driver Description: nVidia Ethernet Networking Driver (nForce chipset driver)
Driver Update Site: Drivers - Download NVIDIA Drivers
nvstor Tue Sep 13 01:53:04 2011 (4e6e9b60) 00036507 nvstor.sys
Driver Description: nVidia Storage Drivers
Driver Update Site: Drivers - Download NVIDIA Drivers
dump_nvstor Tue Sep 13 01:53:04 2011 (4e6e9b60) 00036507 dump_nvstor.sys
Driver Description: driver created to provide disk access during crash dump file generation
Driver Update Site: Windows Update or 3rd party driver manufacturer, depending on the source driver
tunnel Thu Jul 26 04:23:04 2012 (5010aa08) 000296f2 tunnel.sys
Driver Description: Microsoft Tunnel Interface Driver
Driver Update Site: Windows Update
If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:
Driver Verifier Settings