Windows 7: PFN List corrupt

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

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

Hey brothers i ran that memory test and it kinda stuck for about an hour at the same point.
It showed the following:

Pass 100%
Test 70%
Test #8[Module 20, Random Pattern]
Testing : 184K-2048M 3957M
Pattern : fb0e1117-4

I also noted the last two table-like rows :

Wall Time Cached RsvdMem MemMap Cache ECC Test Pass Errors ECC Errs
2:31:02 3957M 576K e820 on off Std 3 1019 0

And this row Was in red :

Tst Pass Failing Address Good Bad Err-Bits Count Chan
1 0 000858fab68-2136.9MB 858fab68 85cfab68 00400000 1

I didn't understand any of it -_-(lol)
please explain it.........and why did it stop??

@zigzag i can't see any starforce program installed in control panel which relates to sfhlp02.sys
and about AMDLLD.sys----does this relate to an amd processor because i have intel core i3 3.06 ghz?????