Random BSOD's (Mixed error codes)

Hey all, I've been trying to diagnose and fix my problems to no avail, I have very frequent BSOD's and I have had no luck with fixing them. Here is my problem (basically)

I randomly get BSOD's while doing simple things such as browsing in Firefox or listening to music on Itunes. Once or twice I have gotten one playing a game (never seen a pattern as to which game). As of today, I receive one EVERY time I restart or shut down.

I had one or two when I first received the computer last year, but never had issues this frequently until very recently. Blue Screen View leads me to believe it is caused by ntoskrnl.exe Any help would be appreciated and any further info on my part will be given as needed. Thanks.

System Specs:

Model: Dell XPS L702X
CPU: Intel Core i7-2630QM 2.00GHz
GPU: Nvidia GeForce GT 555m / Intel HD Graphics Family
RAM: 6.00GB
OS: Windows 7 HP x64 SP1 (Original Install - OEM)
Chipset: Intel 6 Series/C200

Hardware AND OS are 14 months old.
(Laptop purchased 04/2011)

PS: All necessary documents have been attached as requested in posting instructions.

Problem Devices:

Code:

Not Available	ACPI\SMO8800\1	The drivers for this device are not installed.

You are missing your ST Microelectronics Free Fall Sensor drivers. Please install them ASAP.


You have a lot of unneeded software running all the time. I would recommend that you Troubleshoot Application Conflicts by Performing a Clean Startup and only leave Symantec products enabled in startup and services.


Crashes were caused by MagicDisc and Symantec. Uninstall both; make sure to use the Symantec uninstall utilities to uninstall by speaking with one of their support representatives. Download a fresh, up to date copy of Symantec and then re-install with the fresh installer. Do the same with MagicDisc.


Your crashes primarily indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems. There are very suspicious items in your crash reports that likely indicate a virus is on your system!!!!

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run the short and long tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, uninstall it in device manager and see if the system performs better.
  
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Many of your crashes were DirectX/graphics card related. DirectX comes installed with Windows, so this may indicate Windows corruption. It may also be that you have corrupted drivers or a graphics card hardware problem.

• If you are overclocking any hardware, please stop.
  
  
• Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.

I would also highly suggest starting a thread in System Security - Windows 7 Forums