BSOD - pfn_list_Corrupt. random booting into windows

[lovewin7yea]

hello, i posted a problem a few days ago, but i guess my thread got deleted due to the server database corrpution.

ive received over 16 BSOD in the last 2 days. ive wiped my drive and reinstalled thinking that could be an issue but its not, ive done a memory check and one of my sticks was bad and discoloration on the pins as if it were burnt.

ive dropped down to 2gb to be safe and i still continue to

computer:

HP DV4-2045dx
AMD Turion II 2.2
windows 7 Ultimate 64 bit
4 GB ddr2 800

now ive included the last two memory dumps which are completely different dumps and names


ive gotten bad_pool_header, pfn_list_corrupt, memory_module, and several others.

ive flashed the bios from f.08 that it came with to the new f.18


i need help cause i use this computer all the time and i feel like im going no where. thank you.


dumps are included.

 

[zigzag3143]

If these two DMPS were from 2 gigs of ram I would re-run memtest and verifier.



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.

 

[lovewin7yea]

okay, gonna run memtest now, if its the slot id probably have to replace it, cause i tried diff memory and it BSOD me as well.

 

[lovewin7yea]

heres another BSOD i just got when updating windows 7

it gave me a different message this time.

 

[lovewin7yea]

okay, gonna run memtest now, if its the slot id probably have to replace it, cause i tried diff memory and it BSOD me as well.

This one is inconclusive.

?

what do u mean, i meant replace the motherboard

 

[zigzag3143]

heres another BSOD i just got when updating windows 7

it gave me a different message this time.

This DMP file is inconclusive. We will have to wait for more

 

[lovewin7yea]

okay, i wasnt sure what u were saying lol thanks tho zigzag you are truely a man amongst boys

ive gotten through a pass without any errors, i will update when i get to about 5.

so if this memtest doesnt provide errors, i should go ahead with the driver verifier right?

 

[zigzag3143]

okay, i wasnt sure what u were saying lol thanks tho zigzag you are truely a man amongst boys

ive gotten through a pass without any errors, i will update when i get to about 5.

so if this memtest doesnt provide errors, i should go ahead with the driver verifier right?

Yes. I suspect it isnt your ram but we do need to make sure

 

[lovewin7yea]

Not the ram, when i get home from the office ima go ahead and do the driver verifier and see if that does anything.

 

[lovewin7yea]

okay ive started verifier but it has yet to crash the system or BSOD, so i should wait for 36n hours with this on?

 

[zigzag3143]

okay ive started verifier but it has yet to crash the system or BSOD, so i should wait for 36n hours with this on?

Yes, it probably wont take 36 hours.

 

[lovewin7yea]

okay, cause im installing some updates to see if it will crash it on restart

 

[lovewin7yea]

okay so heres a dump file, i noticed that when i actually pick the laptop up and turn it sideways somewhat it will give me a BSOD

im not sure if this one is inconclusive, but the computer itself BSOD like 4 times once going into safe mode as well.

but it only recorded one dump file.

 

[zigzag3143]

okay so heres a dump file, i noticed that when i actually pick the laptop up and turn it sideways somewhat it will give me a BSOD

im not sure if this one is inconclusive, but the computer itself BSOD like 4 times once going into safe mode as well.

but it only recorded one dump file.

Related to your ataport.sys driver (HD controller). Perhaps the HD is loose. If your are handy, comfortable, and out of warranty, you can reseat it carefully.

 

[lovewin7yea]

hmmm anyway to remove it completely or does it have to stay?

 

[zigzag3143]

hmmm anyway to remove it completely or does it have to stay?

Has to stay for the HD to work, but they do become corrupt and often re-installation cures it.

 

[lovewin7yea]

does it require any soldering?

 

[lovewin7yea]

hmmm anyway to remove it completely or does it have to stay?

Has to stay for the HD to work, but they do become corrupt and often re-installation cures it.

DOUGH, you meant HD as in hard drive

i thought you meant high definition. LOL

 

[lovewin7yea]

would i be better off just buying a new motherboard?

 

[zigzag3143]

hmmm anyway to remove it completely or does it have to stay?

Has to stay for the HD to work, but they do become corrupt and often re-installation cures it.

DOUGH, you meant HD as in hard drive

i thought you meant high definition. LOL

Didnt mean either. The controller (especially in a laptop) is built in. What i meant is the driver can become corrupt and need re-installation