The screen of death

fightin irish

Sometimes when im running a few applications at the same time i.e dc++, firefox, and maybe playinf an mp3 i get what a friend jokingly called 'the blue screen of death' .

This all blue screen comes up and say something like ''PFN_LIST_CORRUPT''
And down the bottom it says''dumpin physical memory in 'x' seconds'', so i just hit the restart button and she boots up again and no probs.

Anyone any ideas??

Thanks

Mutant_Fruit

dodgy ram? If its completely random, it's probably dodgy ram. My advise, grab memtester (i think its called) and run that at least one full cycle to test the ram.

Wertz

It's a crash or what windows does to avoid a hard lock just before the comp crashes.

There should be an error code generated when this happens. It'll tell you where the app failed and what caused it. Trouble is, it's in code.
Usually software clashes or a poor;y installed driver cuase the fault but it can also be hardware-based or something as simple as overheating or badly seated RAM...

ando

did you install any new hardware or programs lately? do they run at system startup? or do they run in the background all the time

the_syco

Next time it happens, post up the First 5 lines of the code, and I'll decipher it for you. Its actually very good, IMHO. Although it took me a while to figure it out, if and when it does happen, I'm sometimes able to find out the problem (soundcard, etc).

So get the first few lines, and post up the code, and I'll see what I can do.

maxheadroom

fightin irish wrote:

Sometimes when im running a few applications at the same time i.e dc++, firefox, and maybe playinf an mp3 i get what a friend jokingly called 'the blue screen of death' .

This all blue screen comes up and say something like ''PFN_LIST_CORRUPT''
And down the bottom it says''dumpin physical memory in 'x' seconds'', so i just hit the restart button and she boots up again and no probs.

Anyone any ideas??

Thanks

Yes. Try google. Then try the first result for PFN_LIST_CORRUPT.

fightin irish

thanks a bunch lads...i'll do a google and i'll grab the first 5 lines syco thanks all

byte

Having similar issues myself. XP Pro SP2 is the OS.

I'm getting BSOD with "Bad_Pool_Header"

Then
STOP: 0x00000019 (0x00000020, 0x0xE2049280, 0xE2049300, 0x0C100416)

I'm Googling now though I'm getting too many results! Turning off MS Indexing Service seems to be one of many "fixes"

HungryJoey

well generally its to do with new PC's burning in , happened to me for aobut 1 month and then it kind of disapere gradually and i never had 1 since unless i had a dodgey digital camera plugged in with bad drivers...


It can also be bad RAM, some Motherboards will not accept certain memory chips without causing trouble, also if it is matched with different RAM it can cause troubles...

To be honest , i would just check your Drivers and see what u got plugged in ...really make sure all of your drivers are installed correctly cos drivers sometimes give me BSOD's if they arent compatible with my system of just aren't installed correctly...