Windows 7: BSOD, randomly happening when playing games or watching a video

Norton can be a frequent cause of BSOD-s. Please uninstall it with the Norton Removal Tool.
You may however, install it back if it was not contributing or the cause of your BSOD-s.

• Norton Removal Tool

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    • Good and Free system security combination.
    • How to Scan Your Computer With Multiple Antivirus Programs - How-To Geek

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

If you are overclocking any hardware, STOP. Reset any changed values back to default.

Please do the following:

   Quote: Originally Posted by writhziden

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

Perform a System File Check:

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

For monitoring the heat/celsius of the system, use Speccy or HWinfo:

• Speccy - System Information - Free Download
• CPUID - System & hardware benchmark, monitoring, reporting

Please check for an update on the following:
Driver Description: ASMedia USB 3.0 Hub driver

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa801b2875c0, fffff800045863d8, fffffa801bfbd910}

Unable to load image \SystemRoot\system32\DRIVERS\asmthub3.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for asmthub3.sys
*** ERROR: Module load completed but symbols could not be loaded for asmthub3.sys
Probably caused by : asmthub3.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: fffffa801b2875c0, Physical Device Object of the stack
Arg3: fffff800045863d8, nt!TRIAGE_9F_POWER on Windows 7, otherwise the Functional Device Object of the stack
Arg4: fffffa801bfbd910, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: fffffa8019fd4550

IMAGE_NAME:  asmthub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f435bae

MODULE_NAME: asmthub3

FAULTING_MODULE: fffff88002c00000 asmthub3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF8000458CFB0

STACK_TEXT:  
fffff800`04586388 fffff800`02f006d2 : 00000000`0000009f 00000000`00000003 fffffa80`1b2875c0 fffff800`045863d8 : nt!KeBugCheckEx
fffff800`04586390 fffff800`02ea0c3c : fffff800`045864c0 fffff800`045864c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`04586430 fffff800`02ea0ad6 : fffff800`0303df20 00000000`00102523 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`045864a0 fffff800`02ea09be : 00000026`6e77ec33 fffff800`04586b18 00000000`00102523 fffff800`0300b6e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04586af0 fffff800`02ea07a7 : 0000000d`831a8cc1 0000000d`00102523 0000000d`831a8ca6 00000000`00000023 : nt!KiTimerExpiration+0x1be
fffff800`04586b90 fffff800`02e8dcca : fffff800`03008e80 fffff800`03016cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04586c40 00000000`00000000 : fffff800`04587000 fffff800`04581000 fffff800`04586c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_asmthub3.sys

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

0: kd> !irp fffffa801bfbd910
Irp is active with 7 stacks 6 is current (= 0xfffffa801bfbdb48)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  Pending has been returned
     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
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 fffffa801b2875c0 00000000 fffff88002c0a35c-fffffa801b293400    
	       \Driver\asmthub3	asmthub3
			Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 fffffa801b288ce0 00000000 00000000-00000000    pending
	       \Driver\asmthub3
			Args: 00041100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa801c14a180    

			Args: 00000000 00000000 00000000 00000000
0: kd> lmvm asmthub3
start             end                 module name
fffff880`02c00000 fffff880`02c24000   asmthub3 T (no symbols)           
    Loaded symbol image file: asmthub3.sys
    Image path: \SystemRoot\system32\DRIVERS\asmthub3.sys
    Image name: asmthub3.sys
    Timestamp:        Tue Feb 21 14:54:06 2012 (4F435BAE)
    CheckSum:         0002E74A
    ImageSize:        00024000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You may also go through the tutorials linked below:

• USB Selective Suspend - Turn On or Off
• USB Driver - General Fix for Problems

Code:

fffff800`045864f0  fffff800`0302ffb0 nt!PpmCheckStartDpc
fffff800`045864f8  fffff800`02f84430 nt!PpmCheckStart
fffff800`04586500  00000000`00000000
fffff800`04586508  fffff880`0197b530 tcpip!endpointLruContext+0x4b0
fffff800`04586510  fffff880`0172a2b0 NETIO!WfpSysTimerCallback
fffff800`04586518  fffff880`0197b4e8 tcpip!endpointLruContext+0x468
fffff800`04586520  fffff880`033e7b50
fffff800`04586528  fffff800`02e9c43c nt!KiScanReadyQueues
fffff800`04586530  fffff880`033e7ae0
fffff800`04586538  fffffa80`195d71c0
fffff800`04586540  fffff880`04365aa0Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NIS_20.2.0.19\Definitions\IPSDefs\20130118.001\IDSvia64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for IDSvia64.sys
*** ERROR: Module load completed but symbols could not be loaded for IDSvia64.sys
 IDSvia64+0x8aa0
fffff800`04586548  fffffa80`195d7170
fffff800`04586550  fffff880`04292400Unable to load image \SystemRoot\System32\Drivers\NISx64\1402010.016\SYMNETS.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
 SYMNETS+0x5c400
fffff800`04586558  fffff880`04243a50 SYMNETS+0xda50
fffff800`04586560  00000000`00000000
fffff800`04586568  fffffa80`1a8c5e20
fffff800`04586570  fffff880`05891d94Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1bad94
fffff800`045868c8  fffff880`04bc41d7*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
 USBPORT+0x2d1d7
fffff800`045868d8  fffff880`04bc4e60 USBPORT+0x2de60
fffff800`045868e0  fffff800`045868f0
fffff800`045868e8  fffff880`04bc41c8 USBPORT+0x2d1c8
fffff800`04586918  fffff880`04b8c35e*** WARNING: Unable to verify timestamp for usbehci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbehci.sys
 usbehci+0x635e

• RAM - Test with Memtest86+

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Code:

lmvm nvlddmkm
start             end                 module name
fffff880`048fa000 fffff880`053a2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Feb 10 05:13:08 2013 (5116D804)
    CheckSum:         00A90CB0
    ImageSize:        00AA8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Sometimes drivers remain, not completely uninstalled. Follow this tutorial for complete removal of drivers of the particular program:

• How to Clean Left Over Driver Files with Driver Sweeper
• NVIDIA DRIVERS 306.23WHQL

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule out the faulty stick.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Outdated firmware on SSD's cause BSOD's with bug check code F4. Check for a firmware (Important!)

Use CrystalDiskInfo to check the health status of the SSD & HDD:

• CrystalDiskInfo Standard Edition
• Check a drive for errors

Check your hard drive(s) for errors by running chkdsk

• Check your hard disk for errors
• Disk Check

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Hardware - Stress Test With Prime95:

• Hardware - Stress Test With Prime95

CPU - Stress Test Using IntelBurnTest:

• CPU - Stress Test Using IntelBurnTest

Video Card - Stress Test with Furmark:

• Video Card - Stress Test with Furmark

Monitor your temps during these tests:

• Speccy System Information
• HWMonitor

**************************Sat Mar 23 02:01:16.470 2013 (UTC + 6:00)**************************
Loading Dump File [C:\Users\Yusra\Downloads\SF_22-03-2013\SF_22-03-2013\032213-10108-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime: 1 days 18:05:42.887
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+165 )
BugCheck BugCheck 3B, {c000001d, fffff80002c865e5, fffff8800d778f60, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Usual causes:  System service, Device driver, graphics driver, ?memory
Arguments: Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80002c865e5, Address of the instruction which caused the bugcheck
Arg3: fffff8800d778f60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR: 0x3B
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME:  bf3.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!KiCommitThreadWait+165
CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
MaxSpeed:     3600
CurrentSpeed: 3600
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``