BSOD with multiple error codes.

[Catheadbiscuit]

I have been having the following problems with my system at different times of use. I play Star Wars the Old Republic and use my PC for email, facebook, and other small tasks.

System Specs:

Windows 7 Home Premium x64 (OEM)
AMD Phenom II X4 820 (2.8 GHz)
Nvidia Geforce GTS 450 (EVGA)
6 GB RAM (3 x 2GB) DDR3 PC3-10600 MB/Sec
500w Thermaltake PS

The System was purchased from Best Buy in December of 2010. The model is HP p6674y.

Here is what I have done so far:

I installed the after market video card and power supply in mid January of this year. It ran fine for three weeks then the blue screens started. I tracked the stop codes and tried to isolate whether or not it was hardware or software related. I found some threads with HP printers being an issue so I removed my new printers drivers. AVG was also showing up so I installed Avast.

None of this worked and my comprehension is limited. I performed a system recovery to avoid any more hassle but it still blue screened. I also removed my video card to see if that was the cause but it still crashed.

Next I thought my system was overheating. I do not know the legitimacy of system temp programs and the acceptable temp range for a CPU to run at. Knowing that, I pulled the side of my tower off and used a small desk fan to cool it. I also used compressed air to clean the heat sinks on my CPU and all other parts of the motherboard. It still went to blue screens with the cooling steps taken.

I followed the instructions and have attached the necessary zipped files. Hopefully they work.

Thanks.

Ben

 

[JMH]

> I note you have Avast.
Avast can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

http://files.avast.com/files/eng/aswclear5.exe

Microsoft Security Essentials - Free Antivirus for Windows


> I suggest you run the update readiness tool and then update to SP-1

Ensure you install the correct 64 or 32 bit option for your system)

Download the System Update Readiness Tool (64bit)
Download the System Update Readiness Tool (32bit)

Now update to SP-1

Learn how to install Windows 7 Service Pack 1 (SP1)

 

[Catheadbiscuit]

I will try that as soon as I get home. Thank you.

 

[JMH]

You are welcome.
Let us know how it goes.

 

[Catheadbiscuit]

I followed all the steps described in the post. I successfully installed MSE, already had the update readiness tool, and installed the service pack 1. I guess time will be the factor in knowing the effectiveness.

Thanks again

 

[Catheadbiscuit]

I received another blue screen

 

[JMH]

It is much easier to find patterns, etc, when there is more than one crash.

We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.

Then......
We do need the DMP files to analyse as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Catheadbiscuit]

The folder is attached. I used the paperclip and did not get a message for it being too large.

 

[JMH]

> SP1 has not been installed.
See snip...
Please do it. {Refer instructions my Post 2}

View attachment 198548

> These crashes were caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.

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 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.

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.

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Catheadbiscuit]

I am running the memtest on my desktop now. I finished installing SP1. I do not know what happened with the install last time.

 

[JMH]

Good luck!

 

[Catheadbiscuit]

Memory test ran 5 passes with zero errors. I am going to try the driver verifier. Not sure if my computer skills with suffice.

 

[JMH]

Tis a learning curve you will master.

 

[Catheadbiscuit]

Alright. I have been running driver verification for the past 10 or so hours. I finally got a blue screen when I ran peerblock. Which I thought was a good idea to avoid web-crawlers. I am pretty sure the blue screen verified the driver route as peerblock.

Also, I had zero problems using my PC all day. I am attaching the single dump file if you could please verify it.

 

[zigzag3143]

Related to pbfilter.sys PeerBlock lets you control who your computer "talks to" on the Internet.

It has known problems with win 7. I would remove it at least to test.

 

[Catheadbiscuit]

More Blue screens

I am still getting blue screens even though Peerblock is off my pc. I attached the dump files. What are the chances it is my after market power supply or video card?

 

[zigzag3143]

I am still getting blue screens even though Peerblock is off my pc. I attached the dump files. What are the chances it is my after market power supply or video card?

Could be anything. Please run a system file check to verify and repair your system files.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

 

[Catheadbiscuit]

I had ran the system file checker. It found non parsed files, I think. After the file checker and everything I still received blue screens.

 

[zigzag3143]

I had ran the system file checker. It found non parsed files, I think. After the file checker and everything I still received blue screens.

Did you run it three times?

There are three things it can say at the end

Found no integrity violations--good
found error and fixed them--good
found but could not fix---bad