BSOD just enough knowledge to be Dangerous

First post and I have enough knowledge on my pC to be dangerous, LOL! Well I have been practicing my puter savvy and hope to get my message posted properly without getting too confused but here goes. My BSOD's are getting far too close together and I have exhausted Buddy with trying to figure out what's causing the conflict. He thinks MB but unsure and my funds are getting low these days. Here are some dump files to view, hopefully they make sense. Thanks for the timely response! Here. my system.

AMD Athlon(tm) 11x2 245 processor 2.90 Ghz
2x 2GB DDR2 Ram (1 is Kingston, the other Transcend)
Windows 7 Ultimate 64 bit

BeyondHope said:

First post and I have enough knowledge on my pC to be dangerous, LOL! Well I have been practicing my puter savvy and hope to get my message posted properly without getting too confused but here goes. My BSOD's are getting far too close together and I have exhausted Buddy with trying to figure out what's causing the conflict. He thinks MB but unsure and my funds are getting low these days. Here are some dump files to view, hopefully they make sense. Thanks for the timely response! Here. my system.

AMD Athlon(tm) 11x2 245 processor 2.90 Ghz
2x 2GB DDR2 Ram (1 is Kingston, the other Transcend)
Windows 7 Ultimate 64 bit

We need the actual DMP file

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.

Thanks ZigZag for getting me sorted out. Here is the dmp file from my PC.

BeyondHope said:

Thanks ZigZag for getting me sorted out. Here is the dmp file from my PC.

Memory corruption probably caused by a driver. please run these two tests



1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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



2-Driver verifier

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

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.

Thanks Guys for the advice, I will attempt to try this out once we get settle3d down around here. I'll keep you posted with a question or 2 as follow.