Multiple BSOD's. Latest Bugcheck code: 0xF4

Dan,

Go to your installed Windows Updates: Control Panel\All Control Panel Items\Windows Update\ Click on Installed Updates in the lower left panel.

In the search box at upper right corner where it says Search for Installed Updates, enter: KB2670838 If it comes up, right click on it and uninstall it, let Windows do its thing then close out gracefully. Restart your machine.

Run to test. Report back any results. If running well, and it shows up again in Updates Hide It!

There is a problem with KB2670838 where a mix of Intel and AMD like you have will cause intermittent BSOD's.

Your .dmp today was: STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Verifier might well be causing the slowdowns, freezes, crashes. It stress tests the driver..

The information in post# 9 pointed you to the Driver Verifier - Enable and Disable tutorial which begins with:

   Information

Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

and Arc put in extra effort by boxing some important points.

What was not emphasized, but perhaps should be:
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Note

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

Leave verifier disabled unless a member requests more testing.

Bill
.

Code:

fffff880`03777b38  fffff880`0122e588*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
 MpFilter+0x2e588

Driver Reference Table - MpFilter.sys

The above stands out in one the latest .dmp files. Is Windows 7 updated?

danohall said:

.....
The thing I didn't understand with verifier running, was I thought if my system crashed it'd be recordable. The two lockups I had just totally scrambled the screen and the only way around it was to do a hard reset. No crashes were recorded. I'd of thought if it stressed the drivers it would record which driver caused the crash.

Thanks for the clarifying what you expected with verifier. As far as I understand it, the dump is the record.

I had requested a MGADIAG report in a previous post, but.... I forgot to give you the link to the tutorial.
Here it is: Windows Genuine and Activation Issue Posting Instructions
Please follow those instructions and that might give members a little more to work on.

Bill
.

Thanks dano,

Could you edit the post with the MGADIAG,
select all of the text and
click the # icon on the post menu?

Code:

This wraps the test in a code box
and keeps the thread from 
pushing out the sides

I should have mentioned that before.

Thanks,

Bill
.

Apologies for not being around, I'm a bit under the weather.....

Slartybart said:

   Note

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

Leave verifier disabled unless a member requests more testing.
Bill
.

Agreed.

Golden said:

danohall said:

Code:

fffff880`03777b38  fffff880`0122e588*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
 MpFilter+0x2e588

Driver Reference Table - MpFilter.sys

The above stands out in one the latest .dmp files. Is Windows 7 updated?

Yes, all updates have been installed through windows update. I think the last security essentials update was earlier today but I'll go and check again. The thing I didn't understand with verifier running, was I thought if my system crashed it'd be recordable. The two lockups I had just totally scrambled the screen and the only way around it was to do a hard reset. No crashes were recorded.

A Quote within a Quote to add emphasis:

I'd of thought if it stressed the drivers it would record which driver caused the crash.

From Anak:It will, but, one needs to have a debugger machine hooked up to the problematic machine in order to record it. It will only record the first 20 instances, and when the machine is restarted those are lost and you start over again.

Source: Using Driver Verifier to identify issues with Drivers, and: Using Driver Verifier to identify issues with Drivers

I have seen the MpFilter.sys *** ERROR in earlier .dmp's. but discounted it because Dan said he was up to date, it still bothers me though.

danohall said:

Ok, another crash. Happened when Malwarebytes was scanning. Uploaded results.

I have also seen the mbam.exe fault in earlier .dmps's it showed in this latest round of .dmp's.

Code:

SYSTEM_SERVICE_EXCEPTION (3b) PROCESS_NAME:  mbam.exeUsual causes:   System service, Device driver, graphics driver, ?memory

My recent concerns,

You misinfo32 report under Problem Devices shows your USB3.0 controller as not having the drivers installed and your extra HDD's finally showed they suffered because of it.

Code:

H:\    WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_USB3.0_CRW-SM#XD&REV_1.00#201006010301&1#    Failure using the VxD loader.

G:\    WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_USB3.0_CRW-CF#MD&REV_1.00#201006010301&0#    Failure using the VxD loader.

K:\    WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_USB3.0_CRW-MS&REV_1.00#201006010301&3#    Failure using the VxD loader.

I:\    WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_USB3.0_CRW-SD#MS&REV_1.00#201006010301&4#    Failure using the VxD loader.

J:\    WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_GENERIC-&PROD_USB3.0_CRW-SD&REV_1.00#201006010301&2#    Failure using the VxD loader.

Universal Serial Bus (USB) Controller    PCI\VEN_8086&DEV_8C31&SUBSYS_50071458&REV_04\3&11583659&0&A0    The drivers for this device are not installed.

You can either:

• Check here: Code 19 Failure loading Using the VxD Loader? - Norton Community to see if this helps. The secondary link in the first answer deals with CD/DVD drives, but a drive is a drive, right?

• A bigger question I have is why you are running Norton along with MSE? Remove one of the other: Norton Removal Tool Download or: Microsoft Security Essentials Removal Tool Download

• Or Install the USB3 drivers and test.
• Disconnect the extra HDD's and test.
• Remove then reinstall the HDD's drivers.

I also have concerns about the 32GB of RAM you're using, can you supply the make/model of it, and did you check to see if it is on the compatible list for your Gbyte MB?
Here is the list: GIGABYTE - Motherboard - Socket 1150 - GA-Z87X-D3H (rev. 1.x)

The CPU looks okay, but is the MB Bios the F7version or later? GIGABYTE - Motherboard - Socket 1150 - GA-Z87X-D3H (rev. 1.x)

And you would be doing everyone a great service if you included your M, ahh I see Bill asked what I was going to. Thanks Bill, Dan.

Steve