Multiple different BSOD. Cannot find reason.

[richc46]

Wait a minute.
If you are not familiar with that driver. Make a full anti virus scan and download and make a full scan with malwarebytes.

 

[Kinru]

^See my edited post on the last page. I was under the impression that my drivers should be realtek, but that driver is what is installed when done through windows update. I already have malwarebytes installed and run a quick scan every day + a full scan once a week.

 

[richc46]

Thats great then. I was afraid that it was a virus, using the name of a driver. Go enjoy your computer and if you have any problems, come back at any time. Thanks for the rep, too.

 

[Kinru]

Well, as of right now I'm unable to get any sound on my computer. That is my audio driver and upon trying to install it, I get a BSOD.

 

[richc46]

Give me the files

 

[Kinru]

Attached are the only MBFILT64 files on my computer after I tried uninstalling my realtek drivers. Even after that I still BSOD when trying to boot into win7. Was thinking I'd simply try reinstalling them from my motherboard's driver site.

 

[richc46]

Dont you have the dump reports from the BSOD?

 

[Kinru]

Oh, I'm sorry. Thought you meant the mbfilt files >.< Here are the dmp files.

 

[richc46]

EDIT: Ok so that was my audio driver. I deleted that file in safe mode and was successfully able to reboot into win7 however I no longer have sound. When I tried to reinstall the driver through windows update, it BSOD. Attached is the dmp file if you're interested. Kinda confused how I'm supposed to get sound on my computer if the driver is failing on installation however.

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_082512-31075-01.zip\082512-31075-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309e670
Debug session time: Sat Aug 25 14:25:07.039 2012 (GMT-4)
System Uptime: 0 days 0:11:06.241
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80002edd915}
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
---------

The last report shows the driver still present.

 

[richc46]

In my post number 6, I instructed you to make a system restore point in case of problems. If you cannot get your sound back, use that system restore it will put you back to where you were.

 

[Kinru]

I am attempting a fresh install of the audio drivers right now. Will restart my system and see what happens.

Update: Reinstalled audio drivers successfully. Am now booted into win7. Here's hoping no more problems come up. I'm a little worried because it is still the same files. Not sure why they would have caused a problem in the first place, nor why it was so sporadic.

 

[richc46]

That driver did cause the last BSOD, it could be it was the correct driver but corrupted. Leave the Verifier on and lets see what happens.

 

[Kinru]

Had another 2 BSOD. First one happened while playing a game with the same IRQL error and then second happened when it tried booting into windows, once again with the same error. First dmp was not created correctly, second one was. Attached both. I'm guessing it's the same error. Have no clue what to do though because that was a completely clean install using the drivers from MSI's site for my motherboard. Would a clean install of Windows 7 fix this?

 

[richc46]

Right now, I dont think that a clean install would help. Try to go to device manager and roll back that driver to previous version.

 

[Kinru]

Ok I rolled back the drivers, is there anything else I can do? Any way to find a reason for why the drivers cause the BSOD?

 

[richc46]

I can only say that most current is not the best, the roll back may not even work. I went to the website and got the most current graphics driver. The outcome was that I needed to use an image to get back up and running.

 

[Kinru]

Well, for now I was able to boot into win7. I'll keep driver verifier on and see what happens. Thank you very much for all the help so far.

 

[richc46]

You are verywelcome. I will give you all the help that I can.

 

[Kinru]

New BSOD Different error this time.

 

[richc46]

Dont worry, verifier is weeding out all the weak drivers. This time
E1c62x64.sys file descriptionProductname:Intel(R) Gigabit Adapter Description:Intel(R) Gigabit Adapter NDIS 6.x driver Company:Intel Corporation
That is how verifer works. Things are going as planned.