After staring at the .dmp file,  looking at with bluescreen view, and remembering that i uninstalled web of trust for avst webrep, i had enough to begin searching for a solution to the BSOD.

Turns out that the problem was between Online Armor and Avast Webrep ie x64 plugin.  My uninstallation of WoT and the enabling of the webrep plugins did occur on the same day of the first BSOD.  Well I disabled webrep an now for over a day,  I have yet to recieve any BSOD, when i would normally get 2 - 4 BSODs a day.

I am not computer illiterate, but I'm not a pro with computers either.    I can't upload a .dmp file because it requires Java. I took advice from Ashrafs article and uninstalled it.  Anywys I'll post the results here in text form and maybe anyone of you can figure it out.  This is my first time actually opening up a dmp file. 

What i have done so far;

- Ran scndsk (good)

- performed windows memory diagnostic (good)

- ran Avast & Malwarebytes for any malware (good)

- Checked RAM to see if they worked (good)

******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa80041cc6c0, fffffa80041cc9f0, 4330003}

Unable to load image \??\C:\Windows\SysWow64\Drivers\OADriver.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for OADriver.sys

*** ERROR: Module load completed but symbols could not be loaded for OADriver.sys Probably caused by : OADriver.sys ( OADriver+5bc7 )

Followup: MachineOwner

---------

0: kd> !analyze -v

******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************

BAD_POOL_HEADER (19)

The pool is already corrupt at the time of the current request.

This may or may not be due to the caller.

The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver.

Arguments:

Arg1: 0000000000000020, a pool block header size is corrupt.

Arg2: fffffa80041cc6c0, The pool entry we were looking for within the page.

Arg3: fffffa80041cc9f0, The next pool entry.

Arg4: 0000000004330003, (reserved)

Debugging Details:

------------------

BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cba100  fffffa80041cc6c0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002bb5cae to fffff80002a8afc0

STACK_TEXT: 

fffff880`08f417a8 fffff800`02bb5cae : 00000000`00000019 00000000`00000020 fffffa80`041cc6c0 fffffa80`041cc9f0 : nt!KeBugCheckEx

fffff880`08f417b0 fffff880`04005bc7 : fffffa80`041cc6d0 00000000`00000318 00000000`656e6f4e 00000000`000007ff : nt!ExDeferredFreePool+0x12da

fffff880`08f41860 fffffa80`041cc6d0 : 00000000`00000318 00000000`656e6f4e 00000000`000007ff fffffa80`041cc6d0 : OADriver+0x5bc7

fffff880`08f41868 00000000`00000318 : 00000000`656e6f4e 00000000`000007ff fffffa80`041cc6d0 fffff880`08f41930 : 0xfffffa80`041cc6d0

fffff880`08f41870 00000000`656e6f4e : 00000000`000007ff fffffa80`041cc6d0 fffff880`08f41930 fffffa80`00000000 : 0x318

fffff880`08f41878 00000000`000007ff : fffffa80`041cc6d0 fffff880`08f41930 fffffa80`00000000 00000000`00000000 : 0x656e6f4e

fffff880`08f41880 fffffa80`041cc6d0 : fffff880`08f41930 fffffa80`00000000 00000000`00000000 00000000`00000000 : 0x7ff

fffff880`08f41888 fffff880`08f41930 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffff880`00000000 : 0xfffffa80`041cc6d0

fffff880`08f41890 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffff880`00000000 000001c6`00000001 : 0xfffff880`08f41930

fffff880`08f41898 00000000`00000000 : 00000000`00000000 fffff880`00000000 000001c6`00000001 fffffa80`041cc6d0 : 0xfffffa80`00000000

STACK_COMMAND:  kb

FOLLOWUP_IP: OADriver+5bc7 fffff880`04005bc7 ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  OADriver+5bc7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: OADriver

IMAGE_NAME:  OADriver.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  506ae5bf

FAILURE_BUCKET_ID:  X64_0x19_20_OADriver+5bc7

BUCKET_ID:  X64_0x19_20_OADriver+5bc7

Followup: MachineOwner

---------

0: kd> lmvm OADriver

start             end                 module name

fffff880`04000000 fffff880`04023000   OADriver T (no symbols)              

     Loaded symbol image file: OADriver.sys    

     Image path: \??\C:\Windows\SysWow64\Drivers\OADriver.sys    

     Image name: OADriver.sys    

     Timestamp:        Tue Oct 02 06:01:51 2012 (506AE5BF)    

     CheckSum:         0001086B     ImageSize:        00023000    

     Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Again if anyone can help with this report, that would be great, but if no one can't, any suggestions to websites to visit in order to get help would be great.  I could go to Microsoft, but there are times they lag in responding.