Blue screen stop error 0x0000004E

For a couple of days now my system has been blue screening. I ended
up reinstalling the whole system and thought that it was the graphics
adapter since it ran fine until I ran a heavy duty graphics game on it
and it blue screened again. It seems to work fine until I start that
game. I have traced the code and finally understand that with all the
peramiter codes that came up the problem is a page table entry (PTE)
or PFN is corrupt. What I don't understand is how to fix this
problem. I am not knowledgable in fixing things like this and this
has been a total learning experience for the last few days now. Is
this something I, or my husband who DOES know how to fix this stuff,
can do ourselves or is it time to throw in the towel and take it to a
pc repair shop? If it IS fixable by me, what do I need to do to fix
it?......and I don't have a floppy disk drive to copy anything (read
that on another page).
Stop: 0x0000004e (0x00000099, 0x00023ef9, 0x000000x3, 0x00000000)

Extract from: http://aumha.org/a/stop.htm
This indicates that the memory management Page File Number list is
corrupted. Can be caused by corrupt physical RAM, or by drivers passing
bad memory descriptor lists.

From what you describe the problem is most likely a poorly written
driver coming with the game. You could see if there is an updated driver
available from the support website. Otherwise uninstall the game through
Add / Remove Programs.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

wrote:
> For a couple of days now my system has been blue screening. I ended
> up reinstalling the whole system and thought that it was the graphics
> adapter since it ran fine until I ran a heavy duty graphics game on it
> and it blue screened again. It seems to work fine until I start that
> game. I have traced the code and finally understand that with all the
> peramiter codes that came up the problem is a page table entry (PTE)
> or PFN is corrupt. What I don't understand is how to fix this
> problem. I am not knowledgable in fixing things like this and this
> has been a total learning experience for the last few days now. Is
> this something I, or my husband who DOES know how to fix this stuff,
> can do ourselves or is it time to throw in the towel and take it to a
> pc repair shop? If it IS fixable by me, what do I need to do to fix
> it?......and I don't have a floppy disk drive to copy anything (read
> that on another page).
> Stop: 0x0000004e (0x00000099, 0x00023ef9, 0x000000x3, 0x00000000)