System hang with some BSOD

[ribtor]

Windows 7 is stalling during general use for around 30 seconds every 10 mins.

There have been about 4-5 BSOD following the stalls.

Windows is on an SSD that is about 4 years old and reports 45% life remaining.

Any help is appreciated.

Windows 7 64
MSI 790FX-GD70
AMD 965BE @ 3400 MHz OC off
XFX4890 x2 crossfire
OCZ vertex SSD 60GB
2x4GB Mushkin 1600 9-9-9-24
XFX 750 PSU

 

[koolkat77]

Is the firmware of the SSD up to date?

[FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\debug-MASTER-Tue_01_06_2015_125044_41\010515-33883-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`0344a890
Debug session time: Tue Jan  6 07:38:00.943 2015 (UTC + 6:00)
System Uptime: 0 days 0:22:55.441
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8008816b30, fffffa8008816e10, fffff80003582270}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

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

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8008816b30, Terminating object
Arg3: fffffa8008816e10, Process image file name
Arg4: fffff80003582270, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa8008816b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

STACK_TEXT:  
fffff880`0372b0e8 fffff800`0360aab2 : 00000000`000000f4 00000000`00000003 fffffa80`08816b30 fffffa80`08816e10 : nt!KeBugCheckEx
fffff880`0372b0f0 fffff800`035b5abb : ffffffff`ffffffff fffffa80`0a538060 fffffa80`08816b30 fffffa80`08816b30 : nt!PspCatchCriticalBreak+0x92
fffff880`0372b130 fffff800`03534f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`08816b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0372b180 fffff800`0327be53 : fffffa80`08816b30 fffff800`c0000005 fffffa80`0a538060 00000000`01130700 : nt!NtTerminateProcess+0xf4
fffff880`0372b200 fffff800`03278410 : fffff800`032c782f fffff880`0372bb78 fffff880`0372b8d0 fffff880`0372bc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0372b398 fffff800`032c782f : fffff880`0372bb78 fffff880`0372b8d0 fffff880`0372bc20 00000000`01131f40 : nt!KiServiceLinkage
fffff880`0372b3a0 fffff800`0327c242 : fffff880`0372bb78 00000000`0000ec6c fffff880`0372bc20 00000000`01131a18 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`0372ba40 fffff800`0327adba : 00000000`00000001 00000000`01130cb8 00000000`00000001 00000000`0000ec6c : nt!KiExceptionDispatch+0xc2
fffff880`0372bc20 00000000`77738e5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`01130cc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77738e5d


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_c0000005_IMAGE_wininit.exe

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xf4_c0000005_image_wininit.exe

FAILURE_ID_HASH:  {a2dbcacb-935a-5ba8-e51d-9f8a30f04f43}

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

[/FONT]

Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

 SPTD Removal:

• 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.
• DuplexSecure - Downloads

As an alternative, many people recommend the use of Total Mounter or Magic ISO

 Clean boot

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

 

[ribtor]

Thanks for the help.
Checked SSD Firmware and its good.
Removed Daemon tools and used the removal tool.
Did a clean boot - just running security essentials
Installed newest vid drivers - Legacy and probably the ones that were already on here, I didn't check.

Memtest reports no errors - should I under clock the ram?

I'm still getting system stalling or long loading idle maybe 20 times a day followed by normal function, some lockups and some blue screens. After the blue screen the system will only boot into windows with a full power down. Windows is also failing to load 25% of the time and requires a reboot or two to get past the win logo. Desktop will sometimes start with the pointer showing loading but noting in the task bar will load and the system will not move passed this point without a rest.

POST and BIOS are normal

This seems to be getting worse rapidly.

The page keeps locking up when I try and add a new log. Had to type this twice. Copy and paste twice more.

 

[Laith]

Have you tried running a scan with Malwarebytes?
http://www.sevenforums.com/tutorials/338716-malwarebytes-anti-malware-free.html
This could also be a failing Harddrive.
http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html