Welcome to the forum
Allanwill,
Highly recommend uninstalling the two software below:
Code:
Start Menu\Programs\Advanced SystemCare 7 Public:Start Menu\Programs\Advanced SystemCare 7 Public
Start Menu\Programs\IObit Uninstaller Public:Start Menu\Programs\IObit Uninstaller Public
This software can be cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check
this,
this and
this thread for evidence.
If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of
CCleaner but make sure you back up the registry before making letting ccleaner delete anything.
Code:
Start Menu\Programs\DAEMON Tools Lite Public:Start Menu\Programs\DAEMON Tools Lite Public
Please uninstall
Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.
Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run
sptd.sys uninstaller to remove the
driver from your system.
As an
alternative, many people recommend the use of
Total Mounter or
Magic ISO
Run the System File Checker that scans the of all protected
Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:
- Click on the
rb:
- Type CMD on Search
- Left click and Run as Administrator
- Type SFC /scannow
Full tutorial here:
Check for heating issues using
Speccy or
HWMonitor. Upload a screen shot with either of the tools:
Run
Disk Check on your
Hard Drive for file system errors and bad sectors on it:
Upload a screenshot of your hard disk using
Crystal Disk Info:
Make a hard drive
test from the hard drive manufacturers website:
Test your Hard Drive with
SeaTools:
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\admin\Downloads\PC-14_07_2014_173212,05\071414-30076-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c5d890
Debug session time: Tue Jul 15 01:58:46.749 2014 (UTC + 6:00)
System Uptime: 1 days 16:41:37.325
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88002f63180, 2}
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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0
STACK_TEXT:
fffff800`00b9c5a8 fffff800`02ae6a4a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx
fffff800`00b9c5b0 fffff800`02a996f7 : fffffa80`00000000 fffff800`00000002 00000000`00002710 fffffa80`054fc820 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff800`00b9c640 fffff800`03009895 : fffff800`0302f460 fffff800`00b9c7f0 fffff800`0302f460 fffff880`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`00b9c740 fffff800`02a8c113 : 00000000`00000140 fffff880`0f2c2df0 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff800`00b9c770 fffff800`02a949f0 : fffff800`02c0ae80 fffff880`00000001 00000000`00000000 fffff800`00b9ca28 : nt!KiInterruptDispatchNoLock+0x163
fffff800`00b9c900 fffff800`02a334a9 : 00000000`00000014 fffff880`09aeb000 00000000`00000000 00000000`00000001 : nt!KeFlushMultipleRangeTb+0x260
fffff800`00b9c9d0 fffff800`02b01ca3 : 00000000`00000001 fffff880`09aeb040 fffff6fc`4004d758 fffffa80`00000001 : nt!MiRemoveIoSpaceMap+0xe9
fffff800`00b9cb00 fffff800`03003844 : fffff880`03d2c0b8 00000000`00000040 00000000`00000000 fffffa80`04652e70 : nt! ?? ::FNODOBFM::`string'+0x3609d
fffff800`00b9cb50 fffff880`01113677 : fffff880`03d2c010 fffffa80`037dc1b0 fffffa80`059ef9c8 00000000`00000000 : hal!HalPutScatterGatherList+0xf4
fffff800`00b9cbb0 fffff880`01113443 : fffff800`00000001 fffff880`000000fe 00000000`ffffffed fffffa80`037c9060 : storport!RaidUnitCompleteRequest+0x1b7
fffff800`00b9cc90 fffff800`02a9a30c : fffff800`02c0ae80 00000354`00000000 fffffa80`037c9128 00000000`00000034 : storport!RaidpAdapterDpcRoutine+0x53
fffff800`00b9ccd0 fffff800`02a878ca : fffff800`02c0ae80 fffff800`02c18cc0 00000000`00000000 fffff880`011133f0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
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_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
For more information on the bugcheck, please go through this thread:
