PFN List Corrupt - BSOD'S

Status
Not open for further replies.
Well last night things took a turn fo the worst. Was gta san adreas online when suddenly the pc restarted. The monitor said no signal but the pc itsself was still on, the busy light of the p stayed on. I turned it on and off at the wall, same thing, except it sounded very quiet when i turned it back on, also the power lights to the cd and dvd roms were off and i couldnt eject the disks. i also couldnt hear the hard drives spinning up. There are no beeps when i turn it on. Im probably going to send it back to y oem, i reckon its the psu, maybe the motherboard. Maybe the hard drives have failed aswell. God this sucks argh!
 
Got my pc back, they couldnt find anything wrong with it, which makes me think it must be a driver that is causing these crashes. I have uploaded another dump for inspection, this crash just a few minutes ago.
 

Attachments

  • Mini073007-01.zip
    21.1 KB · Views: 6
Uninstall Panda AV and see if it makes a difference. Someone on another forum has had a few crashes that match your last one. I'm still waiting for a response to see whether Panda was reinstalled after a fresh install of Windows, but his computer hadn't crashed for a while without Panda installed.
 
Damm this is annoying. The memory has passed through memtest with no errors thats what i dont get. I guess i could try uninstalling panda, its just annoying though as i have already paid for a years subscription.
 
Memtest isn't perfect. Some memory can pass it without problem though it's faulty.

I had this error before, 2 times and that was cleared up after i installed the chipset driver.

Maybe you might want to update your chipset driver.

It could also be that your memory is faulty.. try using or borrow someone's else.
 
Brandon said:
Memtest isn't perfect. Some memory can pass it without problem though it's faulty.

I had this error before, 2 times and that was cleared up after i installed the chipset driver.

Maybe you might want to update your chipset driver.

It could also be that your memory is faulty.. try using or borrow someone's else.

How can i find out what is the name of my chipset driver?

p.s one more dump for inspection.
 
the_gas said:
How can i find out what is the name of my chipset driver?

p.s one more dump for inspection.

No matter, i found the drivers i needed, didnt make any difference. However i have found the name of the driver that may be causing the crashes, it has started to appear onscreen.

Aegisp.sys.

I have tried updating the drivers for the wi-fi, i have tried deleting the file, but after the bsod it just reappears. I have searched google, found a few things but nothing worked. How can i stop the file from activating, i read it can be done in control panel and services, but i couldnt see anything there with that name.
 
Your PC is pulling quite a lot of power given your specs. Are you sure you have a good PSU? What's the brand? Crap ones that are insufficient\dying will also cause BSODs. Use the Sensor option in Everest to see the voltage values. All the +3.3V, +5V and +12V values should be stable i.e. they shouldn't fluctuate too much. Also, make sure they're at a minimum of 90% of their total voltage i.e. the +12V voltage shouldn't dip below 11.8V, the +5V voltage shouldn't go below 4.5V etc.
In addition, try removing the OC from the Catalyst Control Center and see if that solves the problem.
 
Rage_3K_Moiz said:
Your PC is pulling quite a lot of power given your specs. Are you sure you have a good PSU? What's the brand? Crap ones that are insufficient\dying will also cause BSODs. Use the Sensor option in Everest to see the voltage values. All the +3.3V, +5V and +12V values should be stable i.e. they shouldn't fluctuate too much. Also, make sure they're at a minimum of 90% of their total voltage i.e. the +12V voltage shouldn't dip below 11.8V, the +5V voltage shouldn't go below 4.5V etc.
In addition, try removing the OC from the Catalyst Control Center and see if that solves the problem.

My psu is here http://www.newegg.com/Product/Product.asp?item=N82E16817104015

Its pretty decent, 700w.

My pc has recently come back from the oem, like a week ago, they couldnt find anything wrong with after putting it through all kinds of tests. Im sure its a driver, but i cant find out what or how. Im close to pulling my hair out.

Going back to my previous post, i solved the aegisp.sys problem, i just uninstalled the wi-fi untill a newer driver comes out, now i just need help on stopping these soul destroying pfn list corrupt messages.
 
Can someone please tell me the name of the offending driver in this dump please, and what could be causing it, if you know.


Thanks
 
ill shed some light on possible problem. It is most likely your ram. One of your sticks may be bad or possibly your ram might need a tad bit more voltage to operate right, Happened to me i raised the voltage and works good. Hope this helps all having this problem.
 
pfn list

I take all of this back.It did it again,so deleted my post...many apologies,but i use xp64 and vista home basic,and it has never done it on vista
 
Everest

two possibilities: Bad memory (ie failure to read correctly a page) or a
bad disk

get a copy of memtest.exe and verify your memory is good

also a copy of Everest Home Ed and access the Sensor data for SMART hds.
every time you BSOD, reboot and monitor the SMART data for an increase in
errors -- if so, it's the HD, else more likely to be the memory.


So when you get a BSOD, does Everest make a note of it, and record it, and if it does, where and what else does it tell you?
 
I'm glad people still post in here. Check this out and tell me what you guys think... Had my Sony Vaio for like 3 years now, no problems. I just recently started to get the Master Disk S.M.A.R.T error on bootup so I decide to buy the same exact HDD, for compatibility and it's been a good HD over the years. Before the HD arrives, I start getting the BsoD mesages and every one of them are different... .... ..... lol lots of periods. So moving on, The HDD comes and I decided today that I'll convert it to a Primary drive and install XP MCE and use the original HD as a temp backup before it craps out. So I'm installing XP all is going well ad blam, another blue screen.. Restart, and try again, gets to the "Savings Settings" part and bam, another blu screen. Ok so now I'm thinking, "The original hd is still plugged in via sata cable, I'll yank the power and sata off the original and try the reinstall again." I try reinstalling XP again, all is good and it happens again... on the new drive... WTF. I just recently had new DDR ram installed yesterday but I know its not the problem because I was getting the errors before hand. I yanked the original ram out, left the new ram in, and I'm going to start over on the new hd xp install and it's currently formatting the drive. I didnt chose the quick format though so it's taking forever. I'm not sure what the differences are between the quick and regualr nstf format (or whatever is) and the quick one. Obviously the quick one is quicker lol. 17% complete woot woot without a blue screen. Anywho, would anyone know why my computer was throwing error codes left andright like that? Could it possibly be my old ram? I'll keep you updated and let you know how the install goes without the old ram. Oh, I also tried to repair o/s with the cd and I got another BsoD while that was running lol. Any help would be greatly appreciated as i just blew 30 bucks on regCure or what ever it is. What a waste of money. It's funny how you run the program and fix all the errors, and you run it again right afterwards and it finds like 15 more errors.

40% complete and no blue screen. I'm crossing my fingers and hoping it was the old ram
 
The motherboard could be going bad from age and heat. This post really doesn't have anything to do with a PFN List corruption
 
sure it does, I've gotten that error like 4 times now lol . 53% and still running strong
 
made it through format without 1 blue screen, windows is copying files now. We'll see what happens during the install
 
Status
Not open for further replies.
Back