BSOD errors - file attached

I was only getting a bsod every few days but the frequency has increased to about 1 - 2 times a day. I tried removing Firefox as it was going slow too, and also had errors in Pegasus e-mail. So... here are the details.

I have an Acer X1200 with Athlon dual core 64 / 4400+ at 2.3 GHz. 2GB memory.
WIN 7 Professional 32-bit, SP1

I started getting occasional bsod messages a few weeks back, and my attempts to fix it have made things worse (grin.) So I am really hoping some kind person will look at the attached files in af4k_bsod.zip
I was unable to upload it from the Acer because I installed some Microsoft security product and now the Firewall is turned on (Advanced Firewall) and will not allow me to turn it off. Yes, I turned it on, but regret it now. Now when I try to click to turn ADV Firewall on or off, it only goes to some useless info about Recommended Settings. I wonder if my Master Boot Record or perhaps System Files are screwed up?

I thought I had uploaded this request (sans file) earlier but now it says that I have not made any previous posts, so I truly hope this is not a duplicate. Once again, many thanks in advance for any helpful ideas here.

af4k

These crashes were caused by memory corruption 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 a 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.

RAM - Test with Memtest86+






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.

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"IRP Logging and Force Pending I/O Requests. and click "Next"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

After running MEMTESTx86 for a number of hours and 10 passes, I have zero errors. Now on to the more complex "iffy" test. I will make some backups first, and a startup repair disk. I DO have access to another computer here, no problem. MY restore points seem to be in short supply. I have only one that is from 2010, and I am fairly sure I made others since then. I can make another one now, but I realize the computer has problems so that's not ideal. Many thanks for your help, Wanikiya & Dyami.

Doing a backup - three hours out of 6 and all of a sudden - BSOD crash. I think it was because I ran another program that keeps giving trouble - Pegasus Mail. I think that program or possibly a lot memory use may very well be the culprit, although Firefox seems to crash it a lot too. I will keep trying to do a backup here, and not use the computer.

af4k said:

Doing a backup - three hours out of 6 and all of a sudden - BSOD crash. I think it was because I ran another program that keeps giving trouble - Pegasus Mail. I think that program or possibly a lot memory use may very well be the culprit, although Firefox seems to crash it a lot too. I will keep trying to do a backup here, and not use the computer.

You are welcome (J/K) Please upload the most recent DMP

It became interesting. I couldn't make a recovery disk - it no longer thinks it has a dvd-rw drive (!) I could not initialize a cd disk.
So I did the best I could with making back-ups of my data to external drives which took a while.
When I followed all of the other instructions. It would no longer boot at all. It would no longer recover or anything. So I took it back to a restore point, and now it works again.

Please see latest minidump data attached. Any clues? This particular time it looks like klmspad.sys may have been an issue but it's the first time I have seen that one show up. (older CASIO label maker.)

The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error.

I would run a disk check to be certain.
Disk Check

Code:

BugCheck 7A, {c0444be8, c0000185, 6241b860, 8897d9e8}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7A, {c0444998, c0000185, 530cd860, 889339e8}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7A, {c041aeb0, c0000185, 65c96860, 835d6e5f}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7A, {c0444990, c0000185, 583d860, 889329e8}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7A, {c0444cc0, c0000185, 2b5a6860, 889989e8}
Probably caused by : memory_corruption
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 7A, {c0413df0, c0000185, 2dc02820, 827be30c}
Probably caused by : memory_corruption ( nt!MiWaitForInPageComplete+302 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``