BSOD while Playing Team Fortress 2 and using mumble, error 0x00000044

The crash dump is not very informative about the failure. There is a hint of storage controller failure which may not be the right cause.

I would suggest you 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.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

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

Ok, I enabled driver verifier and it immediately bsod on startup. Error code is x0A Irq_not_less_or_equal.

Here's a pic in case the dump didn't create anything. I'll post a dump in a few moments.

Edit, because of that particular blue screen, it didn't create a mini dump. When I'm trying to create a dump file, the only last known mini dump was a 3b error last night. Sorry I couldn't find the last dump.

After that, Id used system restore to restore it to the point where I manually created a restore point before enabling driver verifier.

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Sorry mate, I cannot be more specific without checking the crash dump.

• MSE is the virus scanner here, so it can remain out of the possibilities.
• If you have any backup-restore tool installed, uninstall it.
• If any hardware/software has compatibility issue, let it go, too.
• Run SFC /SCANNOW Command - System File Checker to check the system services.
• If there is a scope of BIOS update, plan to apply it.
  
     Warning

  Please note that the BIOS update is a risky process. If you dont have any prior experience with it, dont go for it. Ask a technician to do it for you. A little mistake in teh process may ruin the motherboard permanently.

We havent got to check for any possible driver that might be failing.

See how it goes. Let us know.

ill put the pagefile to system managed and ill try enable driver verifier again. If that fails to create a minidump, then ill try your other suggestions.

Give it a try. :) Let us see what it yields.

Code:

BugCheck A, {1f0, 2, 0, fffff80001e7cf35}

*** WARNING: Unable to verify timestamp for MBfilt64.sys
*** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
Probably caused by : MBfilt64.sys ( MBfilt64+1817 )

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

Code:

    Image name: MBfilt64.sys
    Timestamp:        Fri Jul 31 09:10:32 2009 (4A7267B0)

Its Realtek audio, but I dont know what it does over rtkvhd64.sys. I have never got any more realtek audio driver than trkvhd64. But I have seen it in many people's system.

As you can see, the driver's date is old, and apparently it will not be updated if you update the audio driver. Still have a try: Realtek

If needed, you may rename MBfilt64.sys to MBfilt64.bak .... to see if it can change anything.