BSOD at random times while doing random things

MSINFO32:

• Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter.
• Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
• Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

Code:

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSSIKAT\Downloads\BSOD\060815-88421-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.18839.amd64fre.win7sp1_gdr.150427-0707
Machine Name:
Kernel base = 0xfffff800`03014000 PsLoadedModuleList = 0xfffff800`0325b730
Debug session time: Tue Jun  9 06:58:03.636 2015 (UTC + 6:00)
System Uptime: 3 days 1:50:56.466
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 7F, {8, 80050033, 406f8, fffff88023a324e2}

Unable to load image \SystemRoot\system32\DRIVERS\5U877.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for 5U877.sys
Probably caused by : 5U877.sys ( 5U877+4e2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff88023a324e2

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  CommOSD.exe

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff80003087e69 to fffff800030888c0

STACK_TEXT:  
fffff800`00ba2d28 fffff800`03087e69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba2d30 fffff800`03086332 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2e70 fffff880`23a324e2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0efaffe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 5U877+0x4e2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
5U877+4e2
fffff880`23a324e2 e869ffffff      call    5U877+0x450 (fffff880`23a32450)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  5U877+4e2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 5U877

IMAGE_NAME:  5U877.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d70ae71

FAILURE_BUCKET_ID:  X64_0x7f_8_5U877+4e2

BUCKET_ID:  X64_0x7f_8_5U877+4e2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_5u877+4e2

FAILURE_ID_HASH:  {22692655-f655-4f1f-ba04-2bd07b42dbf6}

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

0: kd> lmvm 5U877
start             end                 module name
fffff880`23a32000 fffff880`23a5a880   5U877      (no symbols)           
    Loaded symbol image file: 5U877.sys
    Image path: \SystemRoot\system32\DRIVERS\5U877.sys
    Image name: 5U877.sys
    Timestamp:        Fri Mar 04 15:18:41 2011 (4D70AE71)
    CheckSum:         0002ECFD
    ImageSize:        00028880
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the drivers here: Driver Reference Table

Sometimes drivers remain and do not get completely uninstalled.

 Driver Removal Process:

• Download Driver Sweeper to the desired location.
• Extract the files from the zip.
• Uninstall the driver Program & Features - Control Panel.
• Run Driver Sweeper, check the drivers you want to uninstall or clean registry leftovers of.

Link to full tutorial: Drivers - Clean Left over Files after Uninstalling

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
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Simply update the driver from the link given.

 Clean boot

• Troubleshoot Application Conflicts by Performing a Clean Startup

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

The only error in the SFC scan is this...

Code:

 Line 15386: 2015-06-14 18:15:58, Info                  CSI    00000354 [SR] Repairing 1 components
 Line 15387: 2015-06-14 18:15:58, Info                  CSI    00000355 [SR] Beginning Verify and Repair transaction
 Line 15390: 2015-06-14 18:15:58, Info                  CSI    00000357 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 15393: 2015-06-14 18:15:58, Info                  CSI    00000359 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

It's an artificial one induced by an MS coding error - relating to KB3068708.
You can either ignore it, or uninstall it and hide it until MS get around to fixing and updating the update.

Uninstall Tweakbit and ignore it.