A BSOD everyday :(

Hi -

Recommendations:

• Avira is often a cause of BSOD's. Please remove it using its removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

• Replace with Microsoft Security Essentials and Malwarebytes which are recommended from a strict BSOD perspective. Run a full scan with both (separately) once downloaded, installed and updated. Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

Good and Free system security combination

   Information

DO NOT start the free trial of MalwareBytes. Unselect the option when prompted.

• Scan your system with the following:
  
  • Kaspersky TDSSKiller How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)
  • ESET online scanner One-time virus scanner free with ESET online scanner
  • Run the scanners listed here: How to Scan Suspicious Files using Online Scanners

• Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

Startup Programs - Change

Troubleshoot Application Conflicts by Performing a Clean Startup

• Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 . The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. SFC /SCANNOW Command - System File Checker

• Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition
  How to Upload and Post a Screenshot and File in Seven Forums

• Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

• Run disk check for errors on your Hard Drive(s) Disk Check

The following is for information purposes only. Any drivers in red should be updated/replaced/removed.

WinRing0x64.sys Sat Jul 26 19:29:37 2008 (488B26C1)
many different programs that center around the using of the WinRing libraries (RealTemp, Corsair Link2 (known BSOD issues w/Win8), Razer GameBooster, etc)
http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys

FNETURPX.SYS Sat Oct 4 08:27:02 2008 (48E6D476)
FNet Turbo HDD USB Driver - Also part of AsRock XFastUSB package
http://www.carrona.org/drivers/driver.php?id=FNETURPX.SYS

hamachi.sys Thu Feb 19 16:36:41 2009 (499D3639)
LogMeIn Hamachi Virtual network interface driver
http://www.carrona.org/drivers/driver.php?id=hamachi.sys

AsrAppCharger.sys Tue May 10 14:28:46 2011 (4DC8F73E)
ASRock App Charger Likely BSOD cause - haven't seen recently (15Jan2013)
http://www.carrona.org/drivers/driver.php?id=AsrAppCharger.sys

AODDriver2.sys Thu Apr 5 15:23:37 2012 (4F7D6499)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=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 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.

sptd.sys Sun Aug 19 03:05:38 2012 (503003A2)
SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win7)
http://www.carrona.org/drivers/driver.php?id=sptd.sys

• Uninstall DAEMON Tools and any Alcohol % software. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7. Uninstall the software using Add/Remove Programs. Reboot the system. Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.

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

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

Debug session time: Tue Apr 23 13:31:42.509 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042313-23587-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 12:48:42.273
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : cfosspeed6.sys ( cfosspeed6+a7b90 )
BugCheck D1, {44, 2, 0, fffff88001619919}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001619919, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_cfosspeed6+a7b90
BiosVersion = P1.70
BiosReleaseDate = 10/12/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Tue Apr 23 00:42:26.364 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042213-24382-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 7:05:07.029
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : cfosspeed6.sys ( cfosspeed6+a7b90 )
BugCheck D1, {44, 2, 0, fffff880014a4919}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880014a4919, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_cfosspeed6+a7b90
BiosVersion = P1.70
BiosReleaseDate = 10/12/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Mon Apr 22 17:36:48.654 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042213-25318-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 16:52:52.434
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )
BugCheck C5, {8, 2, 0, fffff8000300da9b}
BugCheck Info: DRIVER_CORRUPTED_EXPOOL (c5)
Bugcheck code 000000c5
Arguments: 
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8000300da9b, address which referenced memory
BUGCHECK_STR:  0xC5_2
PROCESS_NAME:  pythonw.exe
FAILURE_BUCKET_ID:  X64_0xC5_2_nt!ExDeferredFreePool+1df
BiosVersion = P1.70
BiosReleaseDate = 10/12/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Apr 21 19:00:33.708 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042113-37377-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 16:27:37.472
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : cfosspeed6.sys ( cfosspeed6+457a )
BugCheck D1, {c, 2, 0, fffff8800426657a}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 000000000000000c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800426657a, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
FAILURE_BUCKET_ID:  X64_0xD1_cfosspeed6+457a
BiosVersion = P1.70
BiosReleaseDate = 10/12/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sun Apr 21 02:32:26.717 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042013-27409-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 22:40:49.146
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : cfosspeed6.sys ( cfosspeed6+a7b90 )
BugCheck D1, {44, 2, 0, fffff880014c3919}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880014c3919, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  scummvm.exe
FAILURE_BUCKET_ID:  X64_0xD1_cfosspeed6+a7b90
BiosVersion = P1.70
BiosReleaseDate = 10/12/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Apr 19 08:03:30.892 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\041913-27674-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 13:39:11.282
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : cfosspeed6.sys ( cfosspeed6+a7b90 )
BugCheck D1, {44, 2, 0, fffff880016bb919}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016bb919, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_cfosspeed6+a7b90
BiosVersion = P1.70
BiosReleaseDate = 10/12/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Apr 17 16:04:37.002 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\041713-27471-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
System Uptime: 0 days 23:03:18.922
*** WARNING: Unable to verify timestamp for cfosspeed6.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed6.sys
Probably caused by : cfosspeed6.sys ( cfosspeed6+a7b90 )
BugCheck D1, {44, 2, 0, fffff88001432919}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Bugcheck code 000000d1
Arguments: 
Arg1: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001432919, address which referenced memory
BUGCHECK_STR:  0xD1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_cfosspeed6+a7b90
BiosVersion = P1.70
BiosReleaseDate = 10/12/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Code:

AODDriver2.sys              Thu Apr  5 15:23:37 2012 (4F7D6499)
AsrAppCharger.sys           Tue May 10 14:28:46 2011 (4DC8F73E)
AsrIbDrv.sys                Fri Jun  3 13:33:22 2011 (4DE88E42)
AtihdW76.sys                Wed Nov  7 03:41:51 2012 (5099841F)
AxtuDrv.sys                 Thu May 19 13:42:38 2011 (4DD4C9EE)
EtronHub3.sys               Tue Jul 26 03:30:59 2011 (4E2DE093)
EtronXHCI.sys               Tue Jul 26 03:30:56 2011 (4E2DE090)
FNETURPX.SYS                Sat Oct  4 08:27:02 2008 (48E6D476)
MBfilt64.sys                Fri Jul 31 09:40:32 2009 (4A7267B0)
RTKVHD64.sys                Tue Jun 19 14:50:56 2012 (4FE03D70)
RTKVHD64.sys                Tue May 24 18:32:39 2011 (4DDBA567)
Rt64win7.sys                Fri Apr 22 00:15:33 2011 (4DB07445)
Rt64win7.sys                Thu Jul 14 12:18:47 2011 (4E1E8A47)
TRIXX.sys                   Wed Oct  6 22:14:37 2010 (4CACA06D)
WinRing0x64.sys             Sat Jul 26 19:29:37 2008 (488B26C1)
a1z1s5ry.SYS                Wed Dec 28 04:30:45 2011 (4EFA4715)
ae0qipba.SYS                Wed Dec 28 04:30:45 2011 (4EFA4715)
aff1rm0j.SYS                Wed Dec 28 04:30:45 2011 (4EFA4715)
akodue0p.SYS                Wed Dec 28 04:30:45 2011 (4EFA4715)
amdxata.sys                 Fri Mar 19 22:18:18 2010 (4BA3A3CA)
aqbzfgl6.SYS                Wed Dec 28 04:30:45 2011 (4EFA4715)
atikmdag.sys                Thu Dec 20 02:38:55 2012 (50D225DF)
atikmpag.sys                Thu Dec 20 01:32:55 2012 (50D21667)
avgntflt.sys                Fri Feb 22 15:33:47 2013 (51273B7B)
avipbb.sys                  Fri Feb 22 15:33:53 2013 (51273B81)
avkmgr.sys                  Fri Feb 22 15:33:49 2013 (51273B7D)
axqsfzy7.SYS                Wed Dec 28 04:30:45 2011 (4EFA4715)
cfosspeed6.sys              Mon Jul  4 19:18:51 2011 (4E11BDBB)
dfx11_1x64.sys              Wed Aug 29 01:10:34 2012 (503D17AA)
hamachi.sys                 Thu Feb 19 16:36:41 2009 (499D3639)
idmwfp.sys                  Wed Nov 21 20:42:58 2012 (50ACE872)
pwipf6.sys                  Tue Dec 25 21:05:14 2012 (50D9C0AA)
sptd.sys                    Sun Aug 19 03:05:38 2012 (503003A2)
usbfilter.sys               Wed Oct  7 13:44:08 2009 (4ACC46C8)

Yes but there's a method for doing it: Uninstall Device and Device Driver

Ok..

Any new BSOD?

Yes it still happens. I have been slowly going through this list and I'm stuck at the AMD driver part. I can't find the driver only download, all I can find is the Catalyst Control Center download.

I don't suppose you could link me to it could you?

Edit: Never mind I found the how to, there's so many links it's tricky on the eyes.

Edit 2: Just finished everything on the list. will post again if I get another BSOD.

Edit 3: I enabled something on my motherboard called X-Boost (or something) and it caused boot up errors and a BSOD so I disabled it again. It seems similar to another ASRock feature I'm using called Instant Boot. I have disabled this in case it is contributing to the problem.

I see, good luck!:)

Upload the new crash reports.