Still getting bsod

[Tattooz]

I had replied to the answer given on my previous thread but got no further advice. This is what it said

Ok I updated the [COLOR=#0072BC ! important][COLOR=#0072BC ! important]drivers[/COLOR][/COLOR] and for a couple days I did not get any bsod. Then I think there were 2 or 3 in one day after that. My brother suggested to me to move my memory stick to the second slot and again for a couple days I did not get bsod. But have gotten some since then as well. I have run memtest with my stick in slot 1 and slot 2. After 6 passes in each slot it showed no errors. So the [COLOR=#0072BC ! important][COLOR=#0072BC ! important]blue [COLOR=#0072BC ! important]screens[/COLOR][/COLOR][/COLOR]
seem to be less frequent but I am still getting them.

I have attached the new zip folder with my info in it, but it was from about a week ago or so. I have gotten 5 or 6 more blue screens at least since then. Last night I got 2 within one hour and another first thing this morning. Is there any further advice?

 

[zigzag3143]

I had replied to the answer given on my previous thread but got no further advice. This is what it said

Ok I updated the [COLOR=#0072BC ! important][COLOR=#0072BC ! important]drivers[/COLOR][/COLOR] and for a couple days I did not get any bsod. Then I think there were 2 or 3 in one day after that. My brother suggested to me to move my memory stick to the second slot and again for a couple days I did not get bsod. But have gotten some since then as well. I have run memtest with my stick in slot 1 and slot 2. After 6 passes in each slot it showed no errors. So the [COLOR=#0072BC ! important][COLOR=#0072BC ! important]blue [COLOR=#0072BC ! important]screens[/COLOR][/COLOR][/COLOR]
seem to be less frequent but I am still getting them.

I have attached the new zip folder with my info in it, but it was from about a week ago or so. I have gotten 5 or 6 more blue screens at least since then. Last night I got 2 within one hour and another first thing this morning. Is there any further advice?

Even the newest of these crashes still says Memory and PFN_LIST.

what that means is This error is typically caused by a driver passing a bad memory descriptor list. For example, the driver might have called MmUnlockPages twice with the same list.

To identify what driver is causing this you should run driver verifier.

Beyond that, please run Verifier with these settings:

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 "Low Resource Simulation" 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.

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

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

Let us know if you need further assistance

The analysis still says memory corruption so I have to ask how many passes of memtest? did you test the mobo slots one at a time with known good ram?



Ken J

 

[Tattooz]

I ran memtest with my memory stick in slot 1 and slot 2, I did 6 passes in each with no errors reported. Thanks for getting back to me so quickly, I will try this next step.

 

[Tattooz]

Ok I ran driver verifier until I got 3 blue screens. Now where do I find the dump files?