Seemingly random BSODs, often during shutdown

Okay, you may disable verifier now.
Let us know if more BSODs occur.

Hi,
Did the BSoDs reoccur?

Code:

1: kd> lmvm Lycosa
start             end                 module name
fffff880`05e74000 fffff880`05e7b100   Lycosa   T (no symbols)           
    Loaded symbol image file: Lycosa.sys
    Image path: \SystemRoot\system32\drivers\Lycosa.sys
    Image name: Lycosa.sys
    Timestamp:        Wed Sep 08 09:01:26 2010 (4C86FC86)
    CheckSum:         0001462D
    ImageSize:        00007100
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Caused by the same lycosa driver 2010. Were you able to update it?

Update it from here please
Driver Reference Table - Lycosa.sys

I think you have to delete it.
Do you have another keyboard?

What's connected to the USB ports?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {fffff80003861cc0, fffffa800a6f5b50, 0, 0}

*** WARNING: Unable to verify timestamp for iusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for iusb3xhc.sys
Probably caused by : iusb3xhc.sys ( iusb3xhc+5e81 )

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

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

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffff80003861cc0, Original thread which is the cause of the failure
Arg2: fffffa800a6f5b50, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


FAULTING_THREAD:  fffff80003861cc0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xB8

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF800051B4FB0

LAST_CONTROL_TRANSFER:  from fffff800036d6a32 to fffff800036e3e7a

STACK_TEXT:  
fffff800`051ae480 fffff800`036d6a32 : fffffa80`0d562ea0 fffffa80`0a4d4b30 fffffa80`09b506e0 fffff880`04a6b5e0 : nt!KiSwapContext+0x7a
fffff800`051ae5c0 fffff800`036e7d8f : 00000000`00000020 fffff880`058bedaf fffffa80`00000000 fffffa80`0aa9d750 : nt!KiCommitThreadWait+0x1d2
fffff800`051ae650 fffff800`036b2d2e : fffffa80`0a6ce800 fffff880`00000022 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff800`051ae6f0 fffff800`036f2685 : fffffa80`0d0a0910 fffffa80`0a453001 00000000`000000c0 00000000`000007ff : nt!KiAcquireFastMutex+0x4e
fffff800`051ae730 fffff880`04a05e81 : fffff880`04a7ae80 fffff800`051ae7e8 fffffa80`0a453000 fffff880`04a7ae80 : nt!ExAcquireFastMutex+0x45
fffff800`051ae760 fffff880`04a7ae80 : fffff800`051ae7e8 fffffa80`0a453000 fffff880`04a7ae80 fffff800`051ae890 : iusb3xhc+0x5e81
fffff800`051ae768 fffff800`051ae7e8 : fffffa80`0a453000 fffff880`04a7ae80 fffff800`051ae890 fffff880`04a28901 : iusb3xhc+0x7ae80
fffff800`051ae770 fffffa80`0a453000 : fffff880`04a7ae80 fffff800`051ae890 fffff880`04a28901 fffff880`04a37524 : 0xfffff800`051ae7e8
fffff800`051ae778 fffff880`04a7ae80 : fffff800`051ae890 fffff880`04a28901 fffff880`04a37524 00000000`00000002 : 0xfffffa80`0a453000
fffff800`051ae780 fffff800`051ae890 : fffff880`04a28901 fffff880`04a37524 00000000`00000002 fffffa80`0af90840 : iusb3xhc+0x7ae80
fffff800`051ae788 fffff880`04a28901 : fffff880`04a37524 00000000`00000002 fffffa80`0af90840 fffff880`04a492c2 : 0xfffff800`051ae890
fffff800`051ae790 fffff880`04a37524 : 00000000`00000002 fffffa80`0af90840 fffff880`04a492c2 fffffa80`0a453000 : iusb3xhc+0x28901
fffff800`051ae798 00000000`00000002 : fffffa80`0af90840 fffff880`04a492c2 fffffa80`0a453000 fffff800`051ae8f0 : iusb3xhc+0x37524
fffff800`051ae7a0 fffffa80`0af90840 : fffff880`04a492c2 fffffa80`0a453000 fffff800`051ae8f0 fffffa80`0a6ce8d0 : 0x2
fffff800`051ae7a8 fffff880`04a492c2 : fffffa80`0a453000 fffff800`051ae8f0 fffffa80`0a6ce8d0 fffffa80`0af90840 : 0xfffffa80`0af90840
fffff800`051ae7b0 fffffa80`0a453000 : fffff800`051ae8f0 fffffa80`0a6ce8d0 fffffa80`0af90840 fffffa80`0d0a0910 : iusb3xhc+0x492c2
fffff800`051ae7b8 fffff800`051ae8f0 : fffffa80`0a6ce8d0 fffffa80`0af90840 fffffa80`0d0a0910 fffffa80`0719e010 : 0xfffffa80`0a453000
fffff800`051ae7c0 fffffa80`0a6ce8d0 : fffffa80`0af90840 fffffa80`0d0a0910 fffffa80`0719e010 00000000`00000000 : 0xfffff800`051ae8f0
fffff800`051ae7c8 fffffa80`0af90840 : fffffa80`0d0a0910 fffffa80`0719e010 00000000`00000000 fffff880`04a07d7f : 0xfffffa80`0a6ce8d0
fffff800`051ae7d0 fffffa80`0d0a0910 : fffffa80`0719e010 00000000`00000000 fffff880`04a07d7f fffffa80`0a6ce8d0 : 0xfffffa80`0af90840
fffff800`051ae7d8 fffffa80`0719e010 : 00000000`00000000 fffff880`04a07d7f fffffa80`0a6ce8d0 fffffa80`0d0a0910 : 0xfffffa80`0d0a0910
fffff800`051ae7e0 00000000`00000000 : fffff880`04a07d7f fffffa80`0a6ce8d0 fffffa80`0d0a0910 fffffa80`0a453002 : 0xfffffa80`0719e010


STACK_COMMAND:  .thread 0xfffff80003861cc0 ; kb

FOLLOWUP_IP: 
iusb3xhc+5e81
fffff880`04a05e81 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  iusb3xhc+5e81

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iusb3xhc

IMAGE_NAME:  iusb3xhc.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f226fe0

FAILURE_BUCKET_ID:  X64_0xB8_iusb3xhc+5e81

BUCKET_ID:  X64_0xB8_iusb3xhc+5e81

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

0: kd> lmvm iusb3xhc
start             end                 module name
fffff880`04a00000 fffff880`04ac4000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Fri Jan 27 15:35:28 2012 (4F226FE0)
    CheckSum:         000C193B
    ImageSize:        000C4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Code:

fffff800`051ae5e0  00000000`00000103
fffff800`051ae5e8  fffff880`07447598Unable to load image \SystemRoot\system32\drivers\PLTGC.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PLTGC.sys
*** ERROR: Module load completed but symbols could not be loaded for PLTGC.sys
 PLTGC+0x20598

fffff800`051ae658  fffff880`058bedafUnable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
 athrx+0x8edaf

Update these drivers:

Code:

lmvm PLTGC
start             end                 module name
fffff880`07427000 fffff880`075b7000   PLTGC    T (no symbols)           
    Loaded symbol image file: PLTGC.sys
    Image path: \SystemRoot\system32\drivers\PLTGC.sys
    Image name: PLTGC.sys
    Timestamp:        Fri Nov 04 14:47:57 2011 (4EB3A6BD)
    CheckSum:         0015352D
    ImageSize:        00190000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Description and link here: Driver Reference Table - PLTGC.sys

Code:

lmvm athrx
start             end                 module name
fffff880`05830000 fffff880`059b6000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Wed Nov 24 06:11:58 2010 (4CEC584E)
    CheckSum:         00187FE1
    ImageSize:        00186000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

If its wireless, match your device from here:

• ATHEROS Wireless drivers for Windows

If its not a wireless, match your device from here:

• ATHEROS Network drivers for Windows

Uninstall and install latest drivers in the following method:

Click on the Start ► Control Panel ► Programs ► Uninstall a program ► Uninstall everything related to "C-Media USB Audio Driver (WDM) & Atheros". Reboot the system. Delete remnants of its drivers/older drivers using Driver Sweeper.

Drivers - Clean Left over Files after Uninstalling

Norton tends to cause BSOD-s and several other issues. I would recommend uninstalling it with the Norton Removal Tool and replace with Microsoft Security Essentials To Test.

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

   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.

Reduce items at start-up. Nothing except anti-virus is required:

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup