begining dump of physical memory

[Simon barnes]

At the moment my computer is forever getting blue screen
errors stating that it's begining dump of physical
memory. then rebooting. I can't play games or surf the
web for too long before it happens. It's making my pc
almost unusable.

 

[Jim Eshelman]

At the moment my computer is forever getting blue screen
errors stating that it's begining dump of physical
memory. then rebooting. I can't play games or surf the
web for too long before it happens. It's making my pc
almost unusable.

We need to know what specific errors you are getting. Win XP "stop errors"
are given either as an 8-digit hex number - e.g., 0x0000000A - or as
A_NAME_WRITTEN_LIKE_THIS. Either or both would be helpful. Also, after the
number, there often are parameters in parentheses - these are sometimes
useful. Also, if a specific file is mentioned as the problem.

You can investigate these yourself on my Stop Messages page:
http://aumha.org/win5/kbestop.htm

If you post back here with the information, we'll help you through the
situation. It would also help to have some history of when this appeared,
etc. - some good troubleshooting questions are on
http://aumha.org/a/tshoot.htm - all the background information you can
provide (especially about recent changes to the system) could be useful.

--
Jim Eshelman, MS-MVP Windows http://aumha.org/
AumHa Forums: http://forum.aumha.org/
The Parasite Fight: http://aumha.org/a/parasite.htm
Computer Health: http://aumha.org/a/health.htm
Troubleshooting: http://aumha.org/a/tshoot.htm

 

[Guest]

Right here's the error message I've been getting.
PAGE_FAULT_IN_NONPAGED_AREA
STOP 0X00000050 (0XF7F7FFFF, 0X00000000, 0XF7F7FFFF,
0X00000000)

hope this helps. I'll try looking on your page now.

cheers

 

[Guest]

go to control pane
administrative tool
event viewe
syste
find save dum
post what it says: exampl

Event Type: Informatio
Event Source: Save Dum
Event Category: Non
Event ID: 100
Date: 4/4/200
Time: 10:35:11 A
User: N/
Computer: DAVIDTEYON
Description
The computer has rebooted from a bugcheck. The bugcheck was: 0x10000050 (0xb440600f, 0x00000001, 0xbf86394d, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini040404-02.dmp

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

Check the application with the RED X : exampl

Event Type: Erro
Event Source: Application Erro
Event Category: Non
Event ID: 100
Date: 4/6/200
Time: 7:17:39 A
User: N/
Computer: DAVIDTEYON
Description
Faulting application ad-aware.exe, version 6.0.1.181, faulting module ad-aware.exe, version 6.0.1.181, fault address 0x0002e1b5

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
Data
0000: 41 70 70 6c 69 63 61 74 Applica
0008: 69 6f 6e 20 46 61 69 6c ion Fai
0010: 75 72 65 20 20 61 64 2d ure ad
0018: 61 77 61 72 65 2e 65 78 aware.e
0020: 65 20 36 2e 30 2e 31 2e e 6.0.1
0028: 31 38 31 20 69 6e 20 61 181 in
0030: 64 2d 61 77 61 72 65 2e d-aware
0038: 65 78 65 20 36 2e 30 2e exe 6.0
0040: 31 2e 31 38 31 20 61 74 1.181 a
0048: 20 6f 66 66 73 65 74 20 offset
0050: 30 30 30 32 65 31 62 35 0002e1b
0058: 0d 0a ..

Most of the time a .dll is the problem and in my case trying to access the wrong area. It took a couple of weeks to get some control back. I found that a lot of my event logs were showing:

Faulting application iexplore.exe, version 6.0.2800.1106, faulting module mshtml.dll, version 6.0.2800.1400, fault address 0x0017a555

I ran a sreach for mshtml.dll and found three of them - download the dll - and replaced them all - now things are much smoother. Hope this helps you find your problem and I may have been lucky

David