BSOD's in driver verifier, BSOD's on C:/ disk check (os hdd) & more.

Security App

Crashes indicate Symantec being a possible cause. Remove Symantec and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows

Malwarebytes Anti-Malware Free

   Information

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

Hard Drive/Storage

Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition

How to Upload and Post a Screenshot and File in Seven Forums


Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - Disk Check
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Heat:
-Only use the laptop on a hard surface with nothing blocking any of the vents.
-Use a laptop cooling pad if possible
-Blow out all vents with canned air (DO NOT use a vacuum cleaner or an air compressor, they can damage the components).
-Ensure that the fan comes on and is blowing air out of the vent (may not happen at startup, but should happen after using it for a while).

Temperature

For monitoring heat of the system, use Speccy or HWMonitor:
Speccy System Information

HWMonitor

---

This is for information purposes only. The drivers in red should be updated. If updating does not help, remove them.

xusb21.sys Fri Aug 14 04:10:17 2009 (4A848F49)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
http://www.carrona.org/drivers/driver.php?id=xusb21.sys

AppleCharger.sys Tue Apr 27 09:54:05 2010 (4BD65FDD)
GIGABYTE On/Off Charge driver. See here for details - GIGABYTE ON/OFF Charge [br] May cause BSOD on Win7/8 systems - uninstall to test (haven't seen recently (15Jan2013))
http://www.carrona.org/drivers/driver.php?id=AppleCharger.sys

nusb3hub.sys Thu Feb 10 11:52:32 2011 (4D537D20)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
http://www.carrona.org/drivers/driver.php?id=nusb3hub.sys

nusb3xhc.sys Thu Feb 10 11:52:33 2011 (4D537D21)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
http://www.carrona.org/drivers/driver.php?id=nusb3xhc.sys

dtsoftbus01.sys Fri Jan 13 19:45:46 2012 (4F10358A)
Daemon Tools driver [br] Possible BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=dtsoftbus01.sys
Daemon Tools/Alcohol %

Uninstall DAEMON Tools and/or 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

The below is for information purposes only. Contains relevant information from the blue screen analysis:

Code:

Debug session time: Mon Apr 29 02:58:17.131 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042813-96970-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:00:56.019
Probably caused by : ntkrnlmp.exe ( nt!CmBootLastKnownGood+2f )
BugCheck 5A, {1, 1, 0, 0}
BugCheck Info: CRITICAL_SERVICE_FAILED (5a)
Bugcheck code 0000005A
Arguments: 
Arg1: 0000000000000001
Arg2: 0000000000000001
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x5A
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x5A_nt!CmBootLastKnownGood+2f
BiosVersion = F4
BiosReleaseDate = 08/26/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Fri Apr 26 05:57:13.324 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Yusra\SysnativeBSODApps\042513-385696-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:01:12.228
*** WARNING: Unable to verify timestamp for PxHlpa64.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHlpa64.sys
*** WARNING: Unable to verify timestamp for dtsoftbus01.sys
*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1324 )
BugCheck C9, {23e, fffff88001afe324, fffff9804d8e2e10, 0}
BugCheck Info: DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
Bugcheck code 000000c9
Arguments: 
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88001afe324, The address in the driver's code where the error was detected.
Arg3: fffff9804d8e2e10, IRP address.
Arg4: 0000000000000000, Status code.
BUGCHECK_STR:  0xc9_23e
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1324
BiosVersion = F4
BiosReleaseDate = 08/26/2010
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = GA-770T-USB3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``