Security App
Code:
BHDrvx64.sys Wed Apr 10 11:39:03 2013 (5164FAF7)
ENG64.SYS Fri Apr 26 12:10:48 2013 (517A1A68)
EX64.SYS Fri Apr 26 12:08:58 2013 (517A19FA)
SRTSP64.SYS Sat Jan 26 03:26:16 2013 (5102F878)
SRTSPX64.SYS Sat Jan 26 03:30:05 2013 (5102F95D)
SYMDS64.SYS Thu Jan 17 07:56:45 2013 (50F75A5D)
SYMEFA64.SYS Sat Jan 19 06:31:37 2013 (50F9E969)
SYMEVENT64x86.SYS Thu May 24 06:52:24 2012 (4FBD8648)
SYMNETS.SYS Sat Jul 21 08:07:07 2012 (500A0ECB)
Crashes indicate Norton being a possible cause. Remove Norton and replace with Microsoft Security Essentials to see if it provides more stability.
Uninstallers (removal tools) for common antivirus software. Microsoft Security Essentials and Malwarebytes are recommended from a strict BSOD perspective. They do not cause blue screens on the system as other AV products do. You may however install Norton back if it not directly the cause of your crashes.
Microsoft Security Essentials, Free antivirus for windows and Malwarebytes Anti-Malware Free
Information
- :warn: Do not start the free trial of MalwareBytes, unselect that option when prompted.
- :tip: Update and make full scans with both separately.
Scan your system with the following:
Kaspersky TDSSKiller -
How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)
ESET online scanner -
One-time virus scanner free with ESET online scanner
Start up
Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.
Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
How to Change, Add, or Remove Startup Programs in Windows 7
Problem Drivers: Please update the below drivers to their latest.
Code:
purendis.sys Thu Jan 3 06:39:32 2008
pnarp.sys Tue Apr 1 14:44:59 2008
Pure Networks, Inc. Network Magic NDIS Relay Driver
Driver Reference Table - purendis.sys
Driver Reference Table - pnarp.sys
SFC /scannow to check windows for corruption:
How to Repair Windows 7 System Files with System File Checker
1. Click Start
2. In the search box, type
Command Prompt
3. In the list that appears, right-click on cmd.exe and choose
Run as administrator
4. In the command window that opens, type
sfc /scannow
and hit enter.
Hard Drive/Storage
Post disk summary using CrystalDiskInfo software:
CrystalDiskInfo Standard Edition
- :info: For how to upload a screenshot or file, read here
Make a hard drive test from the hard drive manufacturers website:
Hard Drive Diagnostic Procedure
For errors on your Hard drive(s):
How to Run Disk Check in Windows 7
This tutorial
http://www.sevenforums.com/tutorials/147369-usb-selective-suspend-turn-off.html may help you:
To Disable Selective Suspend:
Code:
1. open the control panel
2. go to power options (you may have to set view to small icons)
3. click change plan settings
4. in the window that opens:
5. click change plan settings
6. click change advanced power settings, expand usb and ensure usb selective suspend is disabled.
As priority basis, update Texas Instruments USB 3.0 Host Drivers - TI USB3 Hub Drivers to their latest.
Link: Driver Reference Table - tihub3.sys
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80075143b0, fffff80000b9c3d8, fffffa800e55e280}
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80075143b0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800e55e280, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DEVICE_OBJECT: fffffa800b15c5a0
DRIVER_OBJECT: fffffa800b196c30
IMAGE_NAME: tihub3.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d30b39d
MODULE_NAME: tihub3
FAULTING_MODULE: fffff880060e0000 tihub3
IRP_ADDRESS: fffffa800e55e280
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_tihub3.sys
BUCKET_ID: X64_0x9F_3_POWER_DOWN_IMAGE_tihub3.sys
Followup: MachineOwner
---------
0: kd> !irp fffffa800e55e280
Irp is active with 5 stacks 4 is current (= 0xfffffa800e55e428)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 fffffa800b15c5a0 00000000 00000000-00000000 pending
\Driver\tihub3
Args: 00016600 00000001 00000004 00000005
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa800e9beb90
Args: 00000000 00000000 00000000 00000000
0: kd> lmvm tihub3
start end module name
fffff880`060e0000 fffff880`06102000 tihub3 T (no symbols)
Loaded symbol image file: tihub3.sys
Image path: tihub3.sys
Image name: tihub3.sys
Timestamp: Sat Jan 15 02:35:41 2011 (4D30B39D)
CheckSum: 00021E39
ImageSize: 00022000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Memtest86+
Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
How to Test and Diagnose RAM Issues with Memtest86+
Note
Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.
Tip
Do this test overnight.
