BSOD at random, 0x0000003b, 0x000000d1 and other

Welcome to the forum.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

ASACPI.sys Mon Mar 28 08:30:36 2005 (42476C4C)
Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
Driver Reference Table - ASACPI.sys

wdcsam64.sys Wed Apr 16 14:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver [br] 2008 driver version has known BSOD issues in Windows
Driver Reference Table - wdcsam64.sys

adfs.SYS Fri Jun 27 02:52:37 2008 (48640195)
Adobe File System Driver
Driver Reference Table - adfs.SYS

Avira is contributing to your BSOD's. Please remove it for testing purpose. Use Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other security software:

Microsoft Security Essentials - Free Antivirus for Windows

Malwarebytes - Free

Good and Free system security combination.

Daemon Tools/Alchohol is known to cause BSODs:
How to remove sptd.sys from system
Registry and SPTD problems | DAEMON Pro Help

dtsoftbus01.sys Fri Jan 13 19:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
Driver Reference Table - dtsoftbus01.sys

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows leftover registry removal:Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

AODDriver2.sys Wed Nov 21 13:44:04 2012 (50AC8644)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: Screenshots and Files - Upload and Post in Seven Forums

Keep us posted.

BUGCHECK SUMMARY

Code:

Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Fri Jan 24 23:14:15.159 2014 (UTC + 6:00)
System Uptime: 0 days 6:14:34.001
BugCheck D1, {59c0e03, 2, 1, fffff88013da1ad6}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Fri Jan 24 14:17:47.354 2014 (UTC + 6:00)
System Uptime: 0 days 0:04:50.571
BugCheck 3B, {c0000005, fffff800030a3113, fffff88009361c00, 0}
Probably caused by : ntkrnlmp.exe ( nt!IopCheckDeviceAndDriver+43 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  uTorrent.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Fri Jan 24 03:40:06.489 2014 (UTC + 6:00)
System Uptime: 0 days 8:48:44.706
BugCheck 3B, {c0000005, fffff80003094ddc, fffff8800a3e6000, 0}
Probably caused by : ntkrnlmp.exe ( nt!IopDecrementDeviceObjectRef+4c )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Wed Jan 22 18:55:34.299 2014 (UTC + 6:00)
System Uptime: 0 days 2:49:00.516
BugCheck 50, {fffff88023cc8b80, 8, fffff88023cc8b80, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Debug session time: Fri Jan 17 22:31:32.387 2014 (UTC + 6:00)
System Uptime: 0 days 0:01:40.605
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : amdppm.sys ( amdppm+26e7 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``