Windows 7: Random BSODs on Asus G53JW

I'm getting random BSOD's usually after many hours and after hybernating(closing lid).
Have run Memtest, no errors.
Reinstalled Atheros LAN Driver.
Ran verifier for 4 hours(had to stop it because I could'nt play decently, was slower than usual)
Uninstalled Daemon Tools and SPTD.

Still getting BSOD's...




Is Windows 7 . . .
- x86 (32-bit) or x64 ?

x64

- the original installed OS on the system?

Yes

- an OEM or full retail version?

OEM

- What is the age of system (hardware)?

6 Months

- What is the age of OS installation (have you re-installed the OS?)

6 Months, No

Might be your ESET. I would replace it with Microsoft Security Essentials, at least to test it.

http://download.eset.com/special/ESETUninstaller.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials

Replaced ESET for Microsoft Security Essentials. (If I decide to reinstall ESET can I use the same serial I had?)
Waiting for the much appreciated BSOD to appear, maybe after 2-3 days.

You can re-use the same legit serial number.

While you are waiting for the BSOD can you check event viewer?

There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Event viewer (local) and look for the critical errors listed in the last day, week, etc. Then go to the windows log>application tab. Finally the windows Logs>system tabs.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

Great, here is another BSOD, now it seems to be the wireless card driver, happened after a suspension.
Even though it's the latest driver it's crashing

Edit: OMG found sptd installed, removed...Waiting for next BSOD

On Fri 28/10/2011 5:42:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-58188-01.dmp
uptime: 13:47:41
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F4DA)
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA8005500680, 0xFFFFF80000B9C510)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 28/10/2011 5:42:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 13:47:41
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x4, 0x258, 0xFFFFFA8005500680, 0xFFFFF80000B9C510)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 22/10/2011 4:24:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102111-24757-01.dmp
uptime: 12:58:47
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x424000C, 0xFFFFFA800BAEDB40)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


I'm using netsh command to create wireless access points for my iphone, can it be causing the wireless card to produce bsods after long periods of usage?

On Sun 30/10/2011 17:56:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103011-35646-01.dmp
uptime: 02:00:16
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A4C38D8, 0xFFFFF8800A4C3130, 0xFFFFF880016D6027)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Well, this time I didn't turn on the wireless access point, so it can't be the wireless card on my laptop

On Tue 01/11/2011 0:50:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103111-62696-01.dmp
uptime: 12:02:48
This was probably caused by the following module: athrx.sys (athrx+0x6108A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800DA6108A, 0xFFFFF8800A528090, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.).
Google query: athrx.sys Atheros Communications, Inc. SYSTEM_SERVICE_EXCEPTION

Ok I'm downgrading my wireless card driver

Decided that it must be heating issues.