Solved BSOD while browsing with Windows Explorer and using Flash

[Hotsandwich]

So basically I booted up today started browsing the web and was listening to a youtube video when internet explorer seizes up and stops working and then BSOD. I attempted to browse the web using ie. but this time i just played a music video while i was surfing then BSOD. I searched some forums and uninstalled flash and surfed with ie. BSOD after 5-10 minutes. Then afterwards I decided to test the integrity of the hard drives one after another.

1st drive is os so i had to reboot

2nd drive is 1tb western digital black BSOD

3rd drive is 2 tb samsung eco drive BSOD

i went right click properties tools and then error checking with both boxes it works for a minute then BSOD i tried again two more times with the same result.

any help would be appreciated i checked the BSOD posting guide and put up my BSOD Dump & System File Collection but i dont know how to put up my
system help report. any help would be appreciated.

ie9 version 9.0.8112.16421

 

[zigzag3143]

Several different flavors of memory management, Probably a driver. Please run these two


* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created. You did create a restore point didnt you?

Using Driver Verifier (Windows Drivers)

 

[Hotsandwich]

Thanks i will try both today and see what happens

 

[zigzag3143]

Thanks i will try both today and see what happens

Let us know if you need help

 

[Hotsandwich]

tested slot 0 had 8 runs no errors i started windows up again with only 1 4 gig stick in slot 0 no bsod yet and even started browsing with ie 9 and checking the integrity of one of the hard drives. could it be a memory slot or even memory problem causing bsod?

btw i know this sounds probably like a newb question and i've googled it thank you but what does dllhost.exe do? it's eating up all my ram 3.77 averaging right now while i check my hd COM Surrogate?

 

[zigzag3143]

tested slot 0 had 8 runs no errors i started windows up again with only 1 4 gig stick in slot 0 no bsod yet and even started browsing with ie 9 and checking the integrity of one of the hard drives. could it be a memory slot or even memory problem causing bsod?

btw i know this sounds probably like a newb question and i've googled it thank you but what does dllhost.exe do? it's eating up all my ram 3.77 averaging right now while i check my hd COM Surrogate?

Could be either but we wont know till you are done. I assume you have run verifier.

Did yoiu search here at SF?

http://www.sevenforums.com/general-discussion/18106-dllhost-exe-uses-enormous-quantity-ram.html

 

[Hotsandwich]

Okay so basically i used MEM86+ to test My four Memory sticks with
Slot 0
stick 1 8 passes no errors
stick 2 7 passes no errors
stick 4 10 passes no errors

stick 3 3 seconds over 10k errors!

so basically with only the three working stick i put them in ran a hdd test and watched flash and browsed ie 9 all worked flawlessly.
i could only guess that when i tested hard drives for functionality and revved up the memory usage the third memory stick (the bad one) would get used and then crap out and get a bsod. so i removed said memory stick and now its been working 8 hours straight no hick ups as of yet.

ps. i havn't used the driver verifier having to back up all my data is a daunting task plus i just dont have the funds to pay for all the storage since prices of hdd has double or increased by 1.5 so that has to wait till prices die down. and yeah since i think i found out my problem as well i think

thanks mr.zigzag3143 for all the help and support