BSOD - stop: 0x0000001E - Windows 7

Hi all Well last month i had to have a new motherboard fitted to my 2 yr old Window 7 Home Essentials 64 bit pc (which i thought weird given how "new" it is). Anyway when i got the pc back the hdmi sound settings in playback had gone, so i took it back to the shop again, where they said they had "fixed" it, but they hadnt. All they did was remove my avg & spybot search and destroy and replace it with windows home essentials & they updated Explorer to 9 (which i hate & swiftly reverted back to 8). I can watch films & the kids can play games in HDMI, BUT we cant listen to sounds via the monitor or tv, as we previously could (sound settings - playback devices only showing our speakers now, no spfdi (or whatever its called lol) or hdmi device)..i thought i could live without this, so just left it. However over the past 2 wks i have been getting more and more BSOD's (this only ever happened once before, then the new m.b got fitted) and im constantly getting the stop error 0x0000001E followed by other numbers (all 0's). Thursday night i had 4 BSOD's within a matter of 20 mins!! So i left the pc alone till the next day (y'day).
Y'day I did a search on this forum and some one had a similar problem, and they were advised it had something to do with Windows Home Essentials. I unistalled and reinstalled both java and flash, but the problem persisted, so i disabled W.H.E and the problem seemed to have disappeared, wooohooo all day with no problems,kids played their games ,i browsed net etc, until last night when i got a BSOD again & again upon start up this morning, when i initially came onto the forum (so no video was playing, but im assuming flash/java would be needed somewhere) so now im at a loss. As W.H.E still not running (as far as im aware) & i have updated flash etc....all drivers etc are showing as up to date, but the only other thing i can surmise is maybe its my graphics card, which worked fine before, but now has no hdmi sound settings. The shop i got it repaired at said the motherboard was a like for like one, but im beginning to wonder now. It cost me a pretty penny so dont want to fork out more cash, moreso if its the fault of the shop i got it "fixed" at lol...any help in my ramblings would be greatly appreciated...have attached a minidump zip & attached pc spec info that i got from HWiNFO32 if that helps :)

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Let us know the results, with the subsequent crash dumps, if any.

It is your audio driver.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {40, 2, 1, fffff800036a9668}

Unable to load image \SystemRoot\system32\drivers\MBfilt64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : MBfilt64.sys ( MBfilt64+1817 )

Followup: MachineOwner
---------

It is very old. Installed driver's date is in 2009. Update the audio driver immidiately.

Here is what I am seeing : MBfilt64.sys

Code:

 kd> lmvm MBfilt64
start             end                 module name
fffff880`05600000 fffff880`0560e000   MBfilt64 T (no symbols)           
    Loaded symbol image file: MBfilt64.sys
    Image path: \SystemRoot\system32\drivers\MBfilt64.sys
    Image name: MBfilt64.sys
    Timestamp:        Fri Jul 31 09:10:32 2009 (4A7267B0)
    CheckSum:         0000FF02
    ImageSize:        0000E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your dump says :

Code:

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc50000178
Arg3: 92a00000991f1880
Arg4: f7fff6fc50000179

This particular Arg1 means A page table entry (PTE) has been corrupted.
You are suggested to test your RAM modules, each module at each slot, differently.
RAM - Test with Memtest86+

Run it at least 8 passes, preferably overnight, for a module a slot.

Let us know the results.