Dumping Physical Memory to Disk.....

[FrogDog]

This is the message I get every once and a while for the last month or so (maybe a few times a week actually). My screen goes blue and it says "Dumping Physical Memory To Disk" and counts to 100. Once it gets to 100 my computer restarts. When it happens is completely random; sometimes when I'm playing a game, and sometimes when surfing the net. I'm running Win2k Pro, btw.

My CPU (Celeron 366) is overclocked to 550 (2.2v, 30 degrees). The CPU has never been unstable in the past. I have 256MB of ram.

Is there something that usualy causes this which I can fix or do you think it's a CPU stability problem?

 

[medic]

I would put it back to stock speed first and test it.

Is there any more wording at all with that error message?

 

[FrogDog]

Yeah, at the top of the screen it gives some hexidecimal numbers and some other stuff. I don't exactly what it says but next I get the message I'll copy it down.

 

[StageLeft]

I GET THE EXACT SAME THING. It says:

BAD_POOL_CALLER, then some hexidecimal crap, then it counts up (not sure mine hits 100), then reboots...about every day.

 

[FrogDog]

I'm pretty sure mine doesn't say BAD_POOL_CALLER but it is something similer in that it has 3 words sepertated by '_'s.

 

[FrogDog]

bump

 

[StageLeft]

HELP!

 

[medic]

A few suggestions...(Backup!)

Install the Service Pack

MS Info1

MSInfo2

MSInfo3

If that doesn't work Remove ANY OC'ing then try updating any drivers (MB,video ect.), go into the bios and set PNP OS Installed to YES and if you have an entry for Force Update of ESCD set to YES as well. Try to also determine if one certain program is running just before the error, if so uninstall it and retest.

 

[FrogDog]

I found out what my last one said. PAGE_FAULT_IN_NONPAGED_AREA. Next time I get the message I'm to copy it down word for word.

 

[medic]

FrogDog
From two different pages...

Troubleshooting Windows 2000 - PAGE_FAULT_IN_NONPAGED_AREA

This error means that Windows 2000 went to a location in memory for some data, but found that the data wasn't there. If that data was marked that it had to be there (i.e., it couldn't be paged to disk), then the system knows it has a problem and issues this error.
Possible reasons you'd see this:
Bad RAM; the data was lost because the memory failed and lost it.
Buggy system service; it thought the data was there, but it wasn't really. If you've installed any new services lately, consider disabling them.Antivirus software can sometimes issue this error.

and:

STOP 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA -- faulty RAM on ANY device (secondary RAM Cache, Video RAM, Computers Main RAM, RAM on disk controllers, etc)

 

[dingdongdingdong]

i got that massage than just low down my speed a lite bit 10mhz and everything noth happen again.

 

[FrogDog]

Hmmm...I've installed a new video card and 128MB of ram recently but I got this message before either of them were put in. However, I'm also pretty sure I get a different message that the Page Fault one sometimes. I'll have to wait until I get it again, I guess.

 

[StageLeft]

Can anybody decipher this pig-latin-greek whatever? I am having this exact error (BAD_POOL_CALLER) and error is 0XC2 as mentioned on this page. It says how to fix it but 'i386kd' is not an executable anywhere on my computer that it says you have to use...what do I do? I mean damn... what a hassel!

MS

 

[StageLeft]

Bump!

 

[StageLeft]

^

 

[medic]

Skoorb

Did you install the Service Pack linked above?
This error is claimed to be fixed in the S.P.
Have you installed any printer software besides W2K's generic drivers for your printer?
If so, uninstall it.
If not, look for the latest drivers.

 

[StageLeft]

Yeah i installed SP1 and it didn't fix it...I will check for updated drivers now and see whats up though