BSOD memory_management while casual browsing

[xoxojenny]

I've had issues with BSOD for about two months now.

Windows 7 x64, OEM, original installed OS on system
2 months old refurb HP Pavilion dv6
4 GB RAM, 500GB Hard Drive
AMD Turion(tm) II P560 Dual-Core Processor 2.50 GHz

BSOD occurs about once a day, every once in awhile it will occur more. I do light internet browsing and use Microsoft Word for school. The most intensive task I do is streaming a movie or two. I've noticed that often times a Shockwave crash or Aw, Snap! (Chrome crash) will precede the BSOD. Clear of viruses and malware. I took it to a local shop, guy wasn't very helpful and thought it might be a temperature issue; speedfan shows my temperature is well below the recommended 97 F. HP support told me to do system recovery, insisted that my files are corrupt. However, everything I've read about BSOD and the errors I've been seeing points to memory issues. Ran memtest and got some errors (attached a pic of memtest running). I wanted to get a second opinion here before I do system recovery (a lot of work to install programs, customize, etc). Any help is appreciated

 

[zigzag3143]

I've had issues with BSOD for about two months now.

Windows 7 x64, OEM, original installed OS on system
2 months old refurb HP Pavilion dv6
4 GB RAM, 500GB Hard Drive
AMD Turion(tm) II P560 Dual-Core Processor 2.50 GHz

BSOD occurs about once a day, every once in awhile it will occur more. I do light internet browsing and use Microsoft Word for school. The most intensive task I do is streaming a movie or two. I've noticed that often times a Shockwave crash or Aw, Snap! (Chrome crash) will precede the BSOD. Clear of viruses and malware. I took it to a local shop, guy wasn't very helpful and thought it might be a temperature issue; speedfan shows my temperature is well below the recommended 97 F. HP support told me to do system recovery, insisted that my files are corrupt. However, everything I've read about BSOD and the errors I've been seeing points to memory issues. Ran memtest and got some errors (attached a pic of memtest running). I wanted to get a second opinion here before I do system recovery (a lot of work to install programs, customize, etc). Any help is appreciated

Virtually all of these blame memory. I would re-run memtest and add driver verifier.

I suspect a driver, and right now my prime candidates are you AVAST and your Symantec. I would remove them and replace with Microsoft Security Essentials.


1-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 or 6 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.

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



2-Driver verifier

I'd suggest that you first backup your data 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[xoxojenny]

Thank you for the reply. I will remove Symantec. However, I'm a little confused with AVAST. I have already uninstalled it some weeks ago- are you seeing evidence that it is still in my system?

Also, if I get my system to crash with Driver Verifier, where do I go from there?

 

[zigzag3143]

Thank you for the reply. I will remove Symantec. However, I'm a little confused with AVAST. I have already uninstalled it some weeks ago- are you seeing evidence that it is still in my system?

Also, if I get my system to crash with Driver Verifier, where do I go from there?

In the most recent one it is no longer there. I happened to pick one when it was still installed. My apologies there were quite a few.
When verifier crashes upload those files.

 

[xoxojenny]

Here are a couple minidump files after running driver verifier. I will do the memtest sometime this week. Another note, I have had various error messages for BSOD. Memory_management pops up often, others include bad pool caller, pfn_list_corrupt, catalyst control centre: host application has stopped working, and page fault in nonpaged area.

 

[xoxojenny]

Anyone.

 

[seth500]

Hi Jenny sry were working as fast we can let me take a look at the dump file and I will make a post of what there saying.

 

[seth500]

Probably caused by : nwifi.sys ( nwifi!Dot11SendCompletion+1e )

Probably caused by : win32k.sys ( win32k!RawInputThread+6ed )

I would update your wifi drivers. Is this happening most under moments when your using the internet?

Plus if your showing any errors in your memory those have to be fixed by replacing the ram that is bad or else you'll never get rid of the bsod's..