Windows 7 Please help me with my BSOD

You have a TP-LINK 150Mbps Wireless Lite N USB Adapter:
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

HotSpotShield is a known cause of BSOD's in some Windows systems. Please un-install it to see if it is the cause of the BSOD's on your system.

These devices have problems:
Not Available ROOT\SIDESHOW\0000 The drivers for this device are not installed.

TP-LINK 450Mbps Wireless N Adapter PCI\VEN_168C&DEV_0030&SUBSYS_3112168C&REV_01\4&1D7623A1&0&00E2 This device is disabled.
As the TP-LINK adapter is disabled, I'd strongly suggest that you uninstall it's software and physically remove the device from your system.

I suspect that the SIDESHOW item is associated with some Logitech G-Series devices. If you have these devices, please un-install the software for these devices and see if that stops the problem. If so, then download and install a fresh copy of the latest drivers for this device if you wish to continue using it.

There are no errors listed in the WER section of MSINFO32. Have you turned error reporting off? If so, why?

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions).
Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): [DEL] DuplexSecure - FAQ [/DEL] Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

The memory dump blames your wireless drivers (this is NOT the USB device). Please update these drivers from the manufacturer's website.

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! :

se64a.sys Thu May 3 01:50:31 2007 (46397827)
EnTech softEngine x64 kernel-mode driver.[br]Most likely a component of EnTech's MonInfo - which is a part of the Monitor Asset Manager software.

The following is for informational purposes only.
[FONT=lucida console]**************************Thu Apr 11 00:12:31.457 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\041113-18766-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18044.amd64fre.win7sp1_gdr.130104-1431
System Uptime:[B]0 days 5:05:37.957[/B]
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
Probably caused by :[B]athurx.sys ( athurx+30be )[/B]
BugCheck [B]D1, {20, 2, 0, fffff88008c0e0be}[/B]
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88008c0e0be, address which referenced memory
FAILURE_BUCKET_ID: [B]X64_0xD1_athurx+30be[/B]
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: [B]3300[/B]
  BIOS Version                  3201
  BIOS Release Date             02/15/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
[FONT=lucida console]**************************Thu Apr 11 00:12:31.457 2013 (UTC - 4:00)**************************
[COLOR=RED][B]se64a.sys                     Thu May  3 01:50:31 2007 (46397827)[/B][/COLOR]
intelppm.sys                  Mon Jul 13 19:19:25 2009 (4A5BC0FD)
[COLOR=RED][B]taphss.sys                    Tue Sep 15 15:58:23 2009 (4AAFF1DF)[/B][/COLOR]
TuneUpUtilitiesDriver64.sys   Thu Sep 17 07:54:52 2009 (4AB2238C)
athurx.sys                    Mon Jan  4 22:23:16 2010 (4B42B0A4)
amdxata.sys                   Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WmBEnum.sys                   Tue Apr 27 16:10:19 2010 (4BD744AB)
btath_rcp.sys                 Thu Jun 24 02:17:21 2010 (4C22F871)
btath_flt.sys                 Thu Jun 24 02:17:38 2010 (4C22F882)
btath_bus.sys                 Thu Jun 24 02:17:43 2010 (4C22F887)
btath_hcrp.sys                Tue Jun 29 05:30:43 2010 (4C29BD43)
jraid.sys                     Tue Aug 10 05:28:44 2010 (4C611BCC)
[COLOR=RED][B]HssDrv.sys                    Thu Sep  2 13:46:48 2010 (4C7FE308)[/B][/COLOR]
btath_lwflt.sys               Mon Sep 13 04:26:54 2010 (4C8DE04E)
HECIx64.sys                   Tue Oct 19 19:33:43 2010 (4CBE2AD7)
RTKVHD64.sys                  Tue Nov 23 05:14:08 2010 (4CEB93F0)
btath_a2dp.sys                Mon Feb 14 20:47:47 2011 (4D59DB43)
btfilter.sys                  Tue Mar  8 01:15:22 2011 (4D75C97A)
iaStor.sys                    Fri May 20 12:52:24 2011 (4DD69C48)
RimSerial_AMD64.sys           Wed Jul  6 19:20:01 2011 (4E14EDA1)
e1c62x64.sys                  Wed Jul 20 12:37:53 2011 (4E270461)
asmtxhci.sys                  Wed Sep 14 03:36:09 2011 (4E705969)
asmthub3.sys                  Wed Sep 14 03:36:19 2011 (4E705973)
cpuz135_x64.sys               Wed Sep 21 04:23:41 2011 (4E799F0D)
[COLOR=RED][B]dtsoftbus01.sys               Mon Oct 17 08:12:30 2011 (4E9C1BAE)[/B][/COLOR]
SCDEmu.SYS                    Thu Feb  9 00:59:50 2012 (4F3360D6)
MpFilter.sys                  Thu Aug 23 19:03:14 2012 (5036B6B2)
vjoy.sys                      Sun Oct 14 05:55:54 2012 (507A8C2A)
AtihdW76.sys                  Tue Nov  6 16:41:51 2012 (5099841F)
atikmpag.sys                  Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys                  Wed Dec 19 15:38:55 2012 (50D225DF)
avgntflt.sys                  Fri Feb 22 04:33:47 2013 (51273B7B)
avkmgr.sys                    Fri Feb 22 04:33:49 2013 (51273B7D)
avipbb.sys                    Fri Feb 22 04:33:53 2013 (51273B81)
vjoy.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.