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

[RyougaLolakie]

Here is the complete list of devices that contain that chip: https://www.atheros.cz/atheros-wireless-download.php?chipset=61&system=6

Gotcha! I'll see what I can find available for that chip. Thanks, Arc!

I was thinking if there's such a network card that I can plug my Ethernet cable in. If not, then I'll get the wireless adaptor. I always use the Ethernet port for Internet stability, therefore I'm asking if such thing exist.

 

[RyougaLolakie]

And here's another bsod, by the error name 3b.

I wonder what this caused it?

 

[Arc]

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.

 

[RyougaLolakie]

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.

Storage controller failure? I hope it's not my primary drives. Last time I'd check, both of those drives are in good condition using crystaldisk.

I'll create a system restore point and enable driver verifier right now.

 

[RyougaLolakie]

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.

 

[Arc]

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.

 

[RyougaLolakie]

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.

Yeah. I wish that bsod wouldve create a minidump at startup, but for some reason it didnt. I dont know if that counts, I set the pagefile at 400mb with max page size of 2gb. Was that the reason why it caused a bugcheck when driver verifier is enabled and didnt create a minidump? If so, 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.

I may upgrade a new motherboard, cpu, and ram soon but we'll see.

 

[Arc]

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.

 

[RyougaLolakie]

Crap, I just realized that my pagefile was not enabled. So, with that said, I set it to system managed and I enabled driver verifier to see if it creates a minidump and it did. Same error. Here's the dump, arc.

 

[Arc]

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
[COLOR=Red]Probably caused by : MBfilt64.sys[/COLOR] ( MBfilt64+1817 )

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

    Image name: MBfilt64.sys
[COLOR=Red]    Timestamp:        Fri Jul 31 09:10:32 2009 [/COLOR](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.

 

[RyougaLolakie]

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
[COLOR=Red]Probably caused by : MBfilt64.sys[/COLOR] ( MBfilt64+1817 )

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

    Image name: MBfilt64.sys
[COLOR=Red]    Timestamp:        Fri Jul 31 09:10:32 2009 [/COLOR](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.

I checked the site and the latest update was from may 2014. Will that update will work with my realtek hd onboard sound? If so, I'll update it right now. Afterwards, do I have to enable driver verifier again for the error 3b bugcheck or no?

 

[Arc]

Your realtek audio itself is backdated, of 2011. So if you think, you may update it. Generally rtkvhd64.sys does not cause a BSOD, but updating will be a good call.

 

[RyougaLolakie]

Alright, I updated Realtek drivers and it seems it's working. Am I going to use my PC normally now or do I have to enable driver verifier again?

 

[Arc]

Let it run normally for now. If it BSODs again in the same line, enable DV.

 

[RyougaLolakie]

Let it run normally for now. If it BSODs again in the same line, enable DV.

Alrighty then. Thank you very much, Arc!

 

[Arc]

Most welcome.