Solved BSOD occasionally whilst using IE9

[Wowdude]

Dear Forum,

I have for the past few weeks been getting BSOD on and off again for no apparent reason that I can find Once they hit, my computer will not start back into Windows 7 normally and Safe Mode is required. I know my way around a computer but I've haven't had many dealings with BSOD so any help would be very appreciated. The requested item is attached.

Thanks!

Wowdude

 

[Arc]

Hello Wowdude !

Event[209]:
Log Name: System
Source: Microsoft Antimalware
Date: 2012-02-08T18:40:59.000
Event ID: 3002
Task: N/A
Level: Error
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Ben-PC
Description:
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
Feature: Behavior Monitoring
Error Code: 0x80004005
Error description: Unspecified error
Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

So, start with updating the definition of MSE.

Next, pay attention to upgrade the network driver.
First, download the network card driver from manufactuer's website.
Then reinstall the driver:

1. Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
2. Double click to expand "Network adaptors".
3. Right click your network card and click Uninstall.
4. Check "Delete driver software for this device" check box, click OK.
5. Restart the computer
6. If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.

And then, try to recover the error that is saying to be ntfs.sys.

1. Reseat the sata and power.
2. Run chkdsk /f/r, following the option two of the tutorial http://www.sevenforums.com/tutorials/433-disk-check.html
3. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Let us know the results please.

 

[Wowdude]

Dear Arc,

Thank you for the fast and very detailed reply. I shall put into place the suggestions you have given ASAP over the nexct few days and get back to you with what I find.

Thanks,

Wowdude

P.S. I'm pretty sure that Driver Magician installed the Network Adaptor driver. My own fault, i've been burnt by this software before but thought i'd give it the benefit of the doubt. Obviously a bad idea.

 

[Arc]

You are welcome! Let us know the results

 

[Wowdude]

Dear Arc,

Followign your suggestions I conducted the series of analyses and here's the results for each one:

I reseated the SATA and power cable to the master HDD.

I installed the wireless usb adapter driver from the manufacturer website after removing the previous driver. I also removed the network driver and let windows install it again upon bootup.

Running chkdsk /f/r from the safe mode cmd took 4 hours but passed all 5 stages with no fixes.

I ran the [Long Test] from the seatools HDD analysis (burnt to a dvd) and both short and long tests were completed and the HDD "Passed without error".

However, saying this, I have had 2 more BSOD's whilst attempting to use the computer during this analysis period. According to BlueScreenView, both occurences of BSOD's were due to ntoskrnl.exe and another file.

Any other suggestions/next steps in diagnosis?

Thanks

Wowdude

 

[Arc]

Can you post those dumps for us, to be analyzed?

 

[Wowdude]

Sure thing.

 

[Arc]

Both of your current dumps showing no specific causes.

I think it is the time for enabling driver verifier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[Wowdude]

Ok Verifier.exe is enabled. Time to brace for incoming BSOD's!

Thanks again Arc, will post back as/when/if I get BSOD/s and will upload more dump files.

Wowdude

 

[Wowdude]

Hey Arc,

As soon as I booted after enabling Verifier the windows 7 loading screen (the windows logo glow) took longer than usual, my mouse appeared on a black screen with no desktop then hit BSOD. In safe mode atm. Dump is attached.

Thanks,

Wowdude

 

[Wowdude]

After reading some other accounts of Memory management on the internet I will also try taking out 1 of my 2 RAM sticks and swapping them through the different ports to see if that makes a difference.

A lil bit of extra info. The BSOD's only ocurred when I moved my PC to my new desk at home. I also replaced my h60 CPU cooler with another of the same series as it was defective, and changed the power chord for the tower. I will try changing the power chord again to rule out the posibility of a power problem (600W PSU).

 

[Wowdude]

Interesting and intrigueing news Arc! I booted my PC with 1 RAM stick in slot 2, copmuter booted, windows logo loaded to a black screen and nothing happened. After a reboot moving the single stick of RAm to slot 1 the computer took a while but booted past the windows logo onto my desktop.

My desktop seems fully functional at the moment but very sluggish. It is taking a long time to do the simplest tasks. I think I may try taking the OC off my processor too.

I forgo9t to mention that when I bought the first h60 (defective one) I also bought another stick of Corsair XMS3 4Gb RAM and installed it with the cooler. My computer wasn't functional for very long as I needed to change the cooler, but as soon as the new cooler arrived, I moved my PC. Could the culprit be a dodgey RAM slot on my mobo?

Also is the Verified state of my PC what's making it sluggish?

Thanks

Wowdude

 

[Wowdude]

Ok time to embarrass myself here with the RAM changing.

With just RAM stick A in slot 2 windows failed to load, but with stick 1 in slot A windows booted to the desktop with no BSOD but was extremely slow!

To further the diagnostic I took RAM stick A out of slot 1 and put RAM stick B into slot 2 to be sure. Windows failed to load. I then tried it in slot 1, windows failed again. Just to be sure, I put RAM stick A back into slot 1 again and booted and nothing. Seems I just got lucky with the one time boot.

Still stumped. I'm tempted for a complete reinstall, would this help?

 

[Arc]

Wowdude, first go to that RAM-Slot combination that booted your PC nicely. Then boot into safe mode and disable driver verifier here. Reboot and boot normally. See it it works or not.

If it is a hardware issue, apparently as it is seen, a clean install will not be of much more help.

Checking your latest dumps now.

EDIT: After checking those, It is seen that it is being caused by Memory. I wish you will be able to find out which one is corrupted.

And, haven't you updated MSE? You may disable MSE for some times, to see if it is placing any impact on the crashes.

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fcc006f080, ba0000196bcd8c2, 48fff6fcc006f081}

Unable to load image \SystemRoot\system32\DRIVERS\MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
[COLOR=Red][B]Probably caused by : MpFilter.sys[/B][/COLOR] ( MpFilter+1fee1 )

 

[Wowdude]

Thanks Arc,

Just disabled Verifier.exe in safe mode with RAM stick A in slot 1 and windows has booted to the desktop at normal speed. Maybe it is the mobo then. My 1st BSOD happened when I put my PC to sleep and then woke it up an hour later. But I don't know how the kernels are anything to do specifically with the RAM.

Wowdude

 

[Arc]

Now, try the RAM stick 1 in other slots, and see if it works normally or not.

Similarly, Use RAM stick 2 in the same way.

If both the sticks work in slot A only, then it is mobo, as you think. One slot might have been damaged.

But the RAM stick 2 gets problem is slot A, then the problem is associated with that RAM module.

Best of your luck!

 

[Wowdude]

Heya Arc!

Just to keep you up to speed, tried each stick singularly in each slot with no problems. Atm i'm using stick B in slot 2 and no problems. Could it be a problem with the motherboard on how it handles both sticks of RAM simultaneously and is there any way to check for it?

Thanks

Wowdude

 

[Arc]

Apparently, just make it sure that both the RAM modules are of same FSB. See the lebel, it will look like ---MHz.

 

[Wowdude]

Yeah I bought 1 stick of RAM with case, CPU and Mobo all in one. I bought the same stick of RAM so they would match perfectly. Both 9-9-9-24 @ 1.50V.

Still no crashes with stick B in slot 2.

 

[Wowdude]

Ok, here's a bit of an update.

Had RAM stick B in Slot 2 since my last post with no consequences. However I just tried replacing the stick and adding 2 other sticks of RAM of the same size and timing (996768 - 4GB (2x2GB) DDR3 PC3-10666 9-9-9-24 Silverline (Dual Kit)). My PC wouldn't even boot. I then tried to boot the computer with 1 stick of the Mushkin RAM in slot 1 and it booted to the desktop, again taking longer than usual to load and then blue screened again. I'm now back to my previous configuration of stick B in Slot 2 abd computer seems fine again. I can only assume a problem with the mobo. Thoughts?

Will upload the BSOD data as usual.

Thanks,

Wowdude

P.S Should RAm get warm whilst in use, because mine seems to. Even just from booting, although it could be my corsair H60 cooler bringing air in through the radiator.