Computing.Net > Forums > Windows NT > NT Physical Memory Dump Error

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

NT Physical Memory Dump Error

Reply to Message Icon

Name: Lou
Date: March 12, 2002 at 15:11:04 Pacific
Comment:

Ok, I've seen stuff like this on this forum before, but I'm hoping some one can help me with my specific problem...

After the blue background with the system info comes up during startup (this is exactly how it happens every time), the log on window starts to come up then the "Blue Death" window comes up and says:

-------

STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of 0x00000080 (0x00000000 0x00000000).
The system has been shut down.

Beginning dump of physical memory
Physical memory dumb complete. Contact your system administrator or technical support group.

------

I would really like to get this fixed without paying anyone! Please help! It is greatly appreciated. I cannot get the system to boot up at all. Email me if you think that would be better than replying on this forum.

Thanks in advance!

-Lou



Sponsored Link
Ads by Google

Response Number 1
Name: Lou
Date: March 12, 2002 at 15:11:46 Pacific
Reply:

PS: I am using NT with service pack 4.00.

-Lou


0

Response Number 2
Name: Roger Evans
Date: March 13, 2002 at 03:07:53 Pacific
Reply:

I get the same message "Beginning dump of physical memory
Physical memory dumb complete. Contact your system administrator or technical support group." But in each case its proceeded with one of three errors; PAGE_FAULT_IN_NON_PAGED_AREA, KMODE_EXCEPTION_NOT_HANDLED, and IRQL_NOT_LESS_OR_EQUAL. These faults happen often and mostly when logging in to my ISP.
After reading extensively on message boards the evidence seems a lead to RAM problem. But I am not sure and hope there is someone more knowledgable out there. I run W2000 prof. on a Sony VAIO notebook.



0

Response Number 3
Name: fritz
Date: March 13, 2002 at 10:08:23 Pacific
Reply:

Oh that wonderful blue screen ! seen that enough times to make me want to smash computers for a living ! OK then, usually a problem with the RAM. easy fix if you can swap mem sticks with known good memory. Also can you get the box to boot in VGA mode?


0

Response Number 4
Name: cpd
Date: March 31, 2002 at 00:28:33 Pacific
Reply:

Don't count on it. I've thought the same thing when 4 of my 5 machines were doing this. They were all bought at the same time so they are identical machines. I've swapped the ram out and it didn't change a thing. After extensive online chat support with the manufacturer of the machine, it was decided that the hardrive has a become corrupted at some particular point. They suggest I dump everything and write zero's to the hardrive then reload the machine and see how that works. I haven't gotten to that part yet but will be soon.
Just a thought.....


0

Response Number 5
Name: Jason
Date: May 1, 2002 at 14:12:16 Pacific
Reply:

I'm experienceing the same problem. It looks to be an error in the registry of some sort. What SP did you install?


0

Related Posts

See More



Response Number 6
Name: josh
Date: May 5, 2002 at 14:39:17 Pacific
Reply:

i am having the EXACT same error. right after the winxp splash screen i get blue screened


0

Response Number 7
Name: Dean
Date: May 9, 2002 at 10:42:23 Pacific
Reply:

I am getting this on multiple machines on my Windows 2k network. All clients are brand new and running XP. I am running group policies on these machines.

Help is urgently needed.


0

Response Number 8
Name: ross
Date: May 10, 2002 at 16:01:32 Pacific
Reply:

It happened to me when I tried to dual boot with win2k and redhat7.2. First time i turned the computer on it said that. (I tried formatting the second drive (that didnt work) so Im now going to format the first drive and see what happens...


0

Response Number 9
Name: shawn cole
Date: May 11, 2002 at 06:15:58 Pacific
Reply:

My boss laptop did the same thing and now after we restarted the the laptop it is real slow


0

Response Number 10
Name: Jeff Dennis
Date: May 13, 2002 at 18:35:15 Pacific
Reply:

I am having the same problem. I thought my computer locked up when the blue screen hit, so I hit reset before it could get to the "completed dumping" part, I guess. Now, either the computer reboots as soon as Win2k starts up, or I can use it (like now) for a short period of time before it crashes... I have a spare stick of RAM, so I'll swap them around to see what's up. I _really_ hope I don't have to wipe clean my harddrive though... :/


0

Response Number 11
Name: Bobby Bradshaw
Date: May 16, 2002 at 10:49:19 Pacific
Reply:

This problem is probably problems with the hard drive. Meaning that either there are missing files that the OS needs or that there are problems in the registry. Most of the time you have to reformat the hard drive if you can't manually repair it in safe mode for example.


0

Response Number 12
Name: Jim Dibb
Date: May 17, 2002 at 06:03:45 Pacific
Reply:

Hi,
I've been tracking instability issues on my machine for a while now. This is the lastest.

Installed winXP twice to 40GB partition on 40 GB drive, with 512MB memory stick installed. Once got PAGE_FAULT..., once got KERNEL_MEMORY_INPAGE_ERROR (or similar).

Then I tried to install to a 14GB partition on a different drive, only swapped the drive and cable. Got the PAGE_FAULT_IN_NON_PAGED_AREA BSOD and another with no code at all.

So two with each drive. Then I swapped out the 512MB stick for a 128 MB stick. XP installed to the 14GB parition on the first try. I'm 90% certain I have a bad DIMM. Anyone know of a good (free) intensive memory diagnostic?


0

Response Number 13
Name: maxchampion
Date: May 20, 2002 at 13:54:02 Pacific
Reply:

I have IRQL LESS or EQUAL error messages and also the PAGEAREA error message. My Vaio is under waranty but Sony doesn't want to hear anything about it. My Laptop is simply unsuseable because it happens systematically when I Use Photoshop 6,01 and I'm a photographer.
Does any one has an idea ? I updated Win Home and the Via 4 in 1 driver but nothing can help. I'm thinking of selling this brand new computer to buy another one from another manufacturer


0

Response Number 14
Name: haslihb
Date: May 21, 2002 at 00:27:59 Pacific
Reply:


I'm on WinNT, SP6 and got the same problem today after pressing the CTRL+ALT+DEL button to login.

Did the following:

1. Replace the existing winlogon.exe file

2. Changed RAM stick

3. Reinstall Service PAck (SP6)

Status: ABle to login with no problems. Not quite sure which actually helped to resolve the problem.


0

Response Number 15
Name: David
Date: May 21, 2002 at 17:23:55 Pacific
Reply:

some boat with you guys! i also had all the same theories of bad ram hd etc. but notice that all our problems are in 2000/xp or nt4. im convinced its an nt thing. ive been scouring the internet for months trying to find an answer to the physical memory dump/kmod/irgl error messages but ive yet to come across the answer.


0

Response Number 16
Name: Tapan Kumar Paul
Date: June 2, 2002 at 00:12:34 Pacific
Reply:

I found "Beginning dump of Physical Memory. Physical Memory dump Complete. Contact your System Administrator or Technical Support Group"

Please send me solution of that kind of messages which I found in Windows NT Workstation.

Tapan


0

Response Number 17
Name: Alvin Kendell
Date: June 4, 2002 at 06:10:11 Pacific
Reply:

That memory dump error is from a bad memory chip. you take out the faulty chip and everthing will be ok


0

Response Number 18
Name: Tom
Date: June 4, 2002 at 10:57:59 Pacific
Reply:

I've got the same problem.
In my case I've narrowed it down to McAfee
VirusScan.
When I install it, it happens.
I reboot in safe mode, remove McAfee and reboot. It's back to normal.


0

Response Number 19
Name: altug
Date: June 6, 2002 at 08:17:58 Pacific
Reply:

There is nothing wrong with the memory. Possibily the system files were corrupted or modified with non compatible ones, because of a software you have installed before the last shutdown.


0

Response Number 20
Name: Paul
Date: June 11, 2002 at 08:47:45 Pacific
Reply:

Had similar problems with win 2k server after installing display drivers. I had to boot into safe mode and uninstall them and then had no probs. It is related to the RAM as I had to reset the RAM chips for the machine to load up it. I also had mega problems with Acrobat and memory dumps particularly with printer from the internet.


0

Response Number 21
Name: Paul
Date: June 11, 2002 at 08:48:18 Pacific
Reply:

Had similar problems with win 2k server after installing display drivers. I had to boot into safe mode and uninstall them and then had no probs. It is related to the RAM as I had to reset the RAM chips for the machine to load up it. I also had mega problems with Acrobat and memory dumps particularly with printing from the internet.


0

Response Number 22
Name: SME
Date: June 15, 2002 at 05:35:29 Pacific
Reply:

normally the error message before the bunch of zeros would mean something. go to support.microsoft.com and type the exact error message. it would normally have 2-3 articles regarding that. it could be a driver, or it could be bad memory.otherwise you would just have to reinstall the os.


0

Response Number 23
Name: RAM
Date: June 17, 2002 at 06:42:34 Pacific
Reply:

This might sound down right stupid...
but give it a try anyway if you're out of options: IT WORKED FOR ME.

When I had the same with Windows 2000 Pro SP2 and Windows XP, I unpluged the hard drive from the mother board (just the bus, not the power) and pluged it back in after few seconds (say 10) the system booted fine with normal settings. I've still to detrmine the cause and why unplging the bus worked.

Keep posting the ideas

eFRIEND


0

Response Number 24
Name: len
Date: June 18, 2002 at 05:07:11 Pacific
Reply:

Same error as above. Changed memory same error. Unplugged hard drive from motherboard. Rebooted fine.

Thanks


0

Response Number 25
Name: Sync
Date: June 18, 2002 at 13:03:53 Pacific
Reply:

I am getting the same error. I have tried everything suggested up there but nothing works, if anyone of you have any ideas , help me out!!


0

Response Number 26
Name: kazi
Date: June 18, 2002 at 14:35:27 Pacific
Reply:

I had the same problem. It appears that the issue is one of what kind of message you get. If the message is one of paging file, try increasing the paging file size. I was using windows NT4 with service pack 6 for quite sometimes. Recently I started facing this "physical memory dump..." problem with the message "IRQ not equal or less...." whenever I am trying to run a big program. I had initially 160 Meg memory in four slots (64-32-32-32) and it was working great so far. I assumed from IRQ problem that two slots are trying to communicating at the same time. I just took off the last 32 meg stick and it is working great with the rest 128 meg. Everytime I fill up the last slot with the 32 meg stick, the system becomes unstable and crashes. I, however, believe that there is some problem with the operating system and I will not have this problem if I reinstall NT. It will work well with 160 meg momeory as it was doing so far. I have ME in another hard drive and it works pretty fine with 160 meg memory. So it is not a hardware problem.


Kazi


0

Response Number 27
Name: Baron Blank
Date: June 20, 2002 at 08:53:29 Pacific
Reply:

A physical memory dump is not necesarrily a sign of bad RAM... Windows default settings dictate that when you get a BSOD, that it dumps the contents of the physical memory to a file for high-level tech support. This is more likely a sign of a device driver conflict... All though it still could be the RAM... Do a search for the DocMemory Program. It is a free program that will do several in depth tests on your RAM and even do a burn in stress test. You will need version 2.0 or higher for the Win2000 system.


0

Response Number 28
Name: Ryan
Date: June 22, 2002 at 06:25:45 Pacific
Reply:

Im getting this aswell ive got 2x 256 ram chips. It only does it after boot or whilst booting its a real bitch wating 2hrs of rebooting for your pc to load. I know that nav screws it up..but ive removed and formated. same with easy cd creator removed and formated. all my drivers are up2date and even with minimum drivers it still screws up :'(

Ive looked around and nobody really seems to know for sure what it is mainly a whole load of guess work. So i guess im just gonna bin this pc and start fresh...its a pretty new 1.4 amd with 512 ram... gutted :(


0

Response Number 29
Name: mmila
Date: June 26, 2002 at 11:06:32 Pacific
Reply:

Read the following MS-Artilces:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q307866

Overwrite the list of files (from NTSP6A)that this articles show.

There is'nt a NT Physical DUMP Error!!
For more information Send me email.

mmila


0

Response Number 30
Name: Jonathan
Date: June 28, 2002 at 03:41:19 Pacific
Reply:

I got the blue memory dump screen also, except when I rebooted my server it kept rebooting and rebooting and rebooting. It would try and load the OS, but then reboot itself. It kept doing this over and over again. After that we got a "no secondary IDE channel. No 80 conductor cable installed" Anyone have any ideas? Thanks!


0

Response Number 31
Name: Luka
Date: June 29, 2002 at 13:48:30 Pacific
Reply:

STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of 0x00000080 (0x00000000 0x00000000).

I have ABIT KG7, 512 ddr,WD 40GB and all that running on XP. It was all ok untill i formated my disc and started installing, all was going fine but when the first boot came i saw this damn BSDE. I tried reinstalling it about 5 times and now i dont know what to do anny more. HELP :)))


0

Response Number 32
Name: Harbinger of BlueScr
Date: July 1, 2002 at 21:01:28 Pacific
Reply:

I have 3 Dell powerhouses, two are dual PIII's and one is a dual Xeon. I'm running Win2k on all of them with the same devices and software installed. I'm getting the "Pysical Memory Dump 0x0000x00...etc" bluescreen on all of them and they happen at the most random times. Sometimes I'll be tooling away in 3d software, other times it'll be hitting the back button on IE5." I don't have a CLUE why this happens but I can confidently say it's NOT A RAM ISSUE.


0

Response Number 33
Name: DethZ
Date: July 10, 2002 at 04:28:51 Pacific
Reply:

in reply to #31

I'm having the same pc as you do , and I'm haveing the same error. I'm searching a solution right now.

- It's not the RAM !! (tested it with DOCTESTER)

It might be an issue with a networkcard, though I'm not sure about that. I'll keep ya updated :-)


0

Response Number 34
Name: Landon
Date: July 13, 2002 at 08:14:59 Pacific
Reply:

Heres something Right Click My Computer,
Left Click Properties, Left Click the Advanced TAB. Under the "Sartup and Recovery" Field Click on Settings. In the Start up and Recovery Properties under the "Write Debugging Information Information" Field, change the memory Dump to None. Click OK, OK, Done. Reboot the Unit.


0

Response Number 35
Name: dpp
Date: July 19, 2002 at 20:45:40 Pacific
Reply:

Memory Dump Error is a Microsoft error.
The engineers that were developing NT left the company, and now they do not know how to fix the problem.
If you want to solve the problem, change from Microsoft.
The problem is the OS.
good luck and keep debugging that BSOD!


0

Sponsored Link
Ads by Google
Reply to Message Icon

Logon Box Gone shut down choices



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows NT Forum Home


Sponsored links

Ads by Google


Results for: NT Physical Memory Dump Error

Physical Memory Dump Error www.computing.net/answers/windows-nt/physical-memory-dump-error/15268.html

Windows NT/Physical Memory Dump www.computing.net/answers/windows-nt/windows-ntphysical-memory-dump/12783.html

Physical Memory Dump after CD install www.computing.net/answers/windows-nt/physical-memory-dump-after-cd-install/7956.html