What is beginning dump of phisical memory?

August 29, 2010 at 03:13:54
Specs: Windows XP, CPU
What is beginning dump of physical memory? When I am working with my computer, My computer shut down suddenly and there is blue screen death. What is the troubleshoot?

See More: What is beginning dump of phisical memory?

Report •

August 29, 2010 at 03:44:09
mmm This can be caused by a few things... Typically it "can" be the hard-drive starting to fail; or at least exhibit a few damaged clusters - leading to file corruption or mis-read data etc... A chkdsk routine is usually the first thing to run with regard to this... That util will report what is finds etc... and you have the option report and do nothing - without your input; or find and fix errors... As windows is very dependant on core files to run..., any loss or corruption of data on the drive can result in errors; and the physical dump is one symptom. If one is adept and knows how... one can read/interpet exactly what it says; and this can ofer on occasion a clue aso what/why etc. system crashed.

RAM starting to fail can also produce similar effects; and again physical dump...

Either of the above can indicate the OS installation is now compromised...; and it wise at this stage to at least safeguard data etc. by copyng to external media. Even better of course is to have data regularly duplicated elsewhere (again external media) at all times...

If you have not copied data safely elsewhere... - and if system will stay up long enough to allow it - then do so immediately. If system will not stay up long enough... then use a linux variant on a CD/DVD to boot system; and then access/copy data that way...

knoppix.com and ubuntu.com have free ISO to download; save to hard-drive; burn to DVD; boot with that DVD and then access/save data...

Overall my experience is a drive starting to fail (serious high number of bad clusters) is the more comon cause of the dump. Possibly others will have other thoughts too...

These two references (from same site) discuss it too...



I have known an installation seriously damaged/crippled (by a virus atack) to produce the same effects... 3 of the 5 keys/hives had been erased from within the registry collection...; and the installation would not boot (dump screen). It had to be restored to delivery status (being a branded system with recovery disks etc - no full version CD).

Report •

August 30, 2010 at 03:33:08
How about the reinstall of windows as its treatment?

Report •

August 30, 2010 at 05:28:34
There occasions when that will work...; often apparently for a very long time too... But from my (fortunately limited personal) experience with that acutal issue -although have seen it more than a few times nonetheless at work - it is often wiser to byte the bullet... and take steps for the worst.

Safeguard all data etc. immediately; ensure you have fequent updates to those copies too - all off the system entirely (external HD and/or optical media).

Then if you decide to go a re-install all your data etc. is safe...

Otherwise try RAM tests (reduce to a single stick (min of 128Meg for XP); test with each stick in turn... Even borrow a know to be good stick too to test with? If all is well with one stick and not another... then likely that latter stick is suspect?

Equally if a chkdsk routine finds and fixes errors... and all is then OK (possibly for a while...) I'd still be inclined to replace the HD... And if it doesn't resolve it all - then seriously/definitely try another HD... (And again safeguard data at all times...)

At work whenever we haver had a dump screen.. it's been due either RAM or the HD starting to fail. IT dept. ovbviously find it easier/more cost effective to replace the HD and see how it goes. If that doesn't work the replace RAM (again with new/good sticks).

I have know a brand new HP/Compaq fail completely within a week of going into service; the HD produced a dump-screen. Subesquent effortst to resolve it (with aaan XP boot-disk and also the Winternals ERD Commander approach merely resulted in the system locking itself down... such that it wouldn't even boot...

Replaced the HD - and later as it happend the MoBo also - and system was OK (obviously).

But once you have safeguarded your files etc... no harm to try a re-install; even a repair install (as in links ealier above)?

Report •

Related Solutions

Ask Question