Random reboots, error 7023

Outdated and problematic drivers:

zntport.sys Sat Dec 22 14:35:56 2007
NTPort Library
Driver Reference Table - zntport.sys

ASACPI.sys Thu Jul 16 09:31:29 2009
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

cpudrv64.sys Tue Aug 11 22:39:13 2009
Driver Description: Likely a component of SystemRequirementsLabs CanYouRunIt
Driver Reference Table - cpudrv64.sys

AODDriver2.sys Thu Apr 5 15:23:37 2012
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard. Known BSOD issues in Win7
Driver Reference Table - AODDriver2.sys

(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 Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page) Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

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.

   Information

• Download and install Revo Uninstaller free from here:
  
  Download Revo Uninstaller Freeware
  Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Avast! is a frequent cause of BSOD's. Please remove it and use Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Help protect your PC with Microsoft Security Essentials

Malwarebytes Free

• Do not start the trial version of MalwareBytes
  

You may also take a look at:

Good & Free System Security Combination

Make scans with -

TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

Online Virus Scanner Eset

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7

Your Antivirus software is basically whats just needed there.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall Daemon Tools.

DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:

Piriform - Speccy

CPUID - HWMonitor

Let us know the results.

BSOD SUMMARY

Code:

Debug session time: Thu Aug  1 04:13:16.190 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:08:24.814
*** WARNING: Unable to verify timestamp for cpudrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpudrv64.sys
Probably caused by : cpudrv64.sys ( cpudrv64+1912 )
BugCheck 1E, {ffffffffc0000096, fffff8800afc6912, 0, 0}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8800afc6912, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000096
PROCESS_NAME:  inteldriver.ex
FAILURE_BUCKET_ID:  X64_0x1E_c0000096_cpudrv64+1912
BiosVersion = 2103   
BiosReleaseDate = 06/18/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Aug  1 04:04:01.110 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:23:48.359
*** WARNING: Unable to verify timestamp for cpudrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpudrv64.sys
Probably caused by : cpudrv64.sys ( cpudrv64+1912 )
BugCheck 1E, {ffffffffc0000096, fffff8800c93d912, 0, 0}
BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
Bugcheck code 0000001E
Arguments: 
Arg1: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8800c93d912, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000096
PROCESS_NAME:  inteldriver.ex
FAILURE_BUCKET_ID:  X64_0x1E_c0000096_cpudrv64+1912
BiosVersion = 2103   
BiosReleaseDate = 06/18/2010
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

All the best.