Sporadic BSOD WORKER THREAD RETURNED AT BAD IRQL

Welcome

We need all the reports
Please follow Blue Screen of Death (BSOD) Posting Instructions grab all and upload the zip here

Code:

Start Menu\Programs\Spybot - Search & Destroy	Public:Start Menu\Programs\Spybot - Search & Destroy	Public

I have seen various issues with Spybot S&D. Please remove it: How to uninstall | Spybot ©

Avast Antivirus is contributing to your crashes.

Code:

fffff880`0b9c8fd8  fffff880`06d639e4Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
 aswSP+0x129e4
fffff880`0b9c82f8  fffff880`06b0bb6aUnable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
 aswSnx+0x4ab6a

Please remove it using its removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

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 Anti-Malware Free
• 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.

Perform a System File Check to check the integrity of all protected Windows 7 :

1. Click on the start
2. Type CMD on Search
3. Left click and Run as Administrator
4. Type
   Code:

   SFC /scannow

Full tutorial here:

• SFC /Scannow Command - System File Checker

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

• How to run Disk Check on Windows 7

Number down items at start-up. Keep only your anti-virus, this also improves the time for logging into windows.

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

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.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial:

• Memory Diagnostics Tool

Let us know the results.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Wed Mar  6 19:57:30.536 2013 (UTC + 6:00)
System Uptime: 0 days 0:38:55.081
Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!KxWaitForLockOwnerShip+12
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Tue Feb 26 20:50:14.317 2013 (UTC + 6:00)
System Uptime: 0 days 0:55:51.488
Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xE1
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0xE1_nt!IopProcessWorkItem+0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

MartinLHansen said:

May I return if needed be?

Please do.

Look forward to the results.