Dumping Physical Memory To Disk ?

Discussion in 'Hardware' started by URX111, Apr 18, 2005.

  1. URX111

    URX111 Private E-2

    I hope this is the right forum to get infomation on this, I don't know what it is.
    While playing games or online, I sometimes get a blue screen and it says a bunch of letters, numbers and lines. Then at the bottom it says "Dumping Physical Memory To Disk" then theres numbers that count up to about 90 or so. Then my computor re-boots. What is and is a fix (simple I hope).

    P4 2.4
    Win 2000
    Memory 512
    HD 10 & 40
    G-Force FX 5200
     
  2. ~Pyrate~

    ~Pyrate~ MajorGeek

    what you are seeing is a stop error ... and posting that number might help us troubleshoot the problem .. it will look something like 0x0000009C MACHINE_CHECK_EXCEPTION ... write that down then post it ... sometimes if you do a search at microsoft.com you will get a tut on how to fix it

    most likely you have a driver problem and make sure your drivers are all up to date and installed correctly .. worst case scenario is one one your components has bit the dust and will have to be replaced

    also a little more onfo would be helpful ... as when does this happen? does it always happen at a specific time? only when playing a certain game? can you make it happen on purpose or is it completely random?

    also check your event log and take note of any errors that occur at the time it crashes
     
  3. URX111

    URX111 Private E-2

    TNX for your reply Pryate, It happens about every other day, but today it happened twice. It's randome, Next time it happens I'll try to write down as much info. as I can. How do I acess event log, I've seen it before but can't remember how to bring it up? Your help is much apreacited.
     
  4. maistrucfp

    maistrucfp Private E-2

    i have that same problem to....sometimes!
    what type of motherboard do you have?
    it can be the motherboard.......80%
     
  5. Lanfear

    Lanfear Private First Class

    it can sometimes happen when you have a bad ram stick and it hits a chunk that is corrupt
     
  6. URX111

    URX111 Private E-2

    TNX for your replys: I have a ASUS P4S533 MB. It happened again last night.
    This is all I got copyed.
    Stop: 0X0000001E (0XC0000005,0XA0002356,0X00000000,0XA01E6A89)
    Address A000

    There was more but my computor rebooted. I'll try to get more when it happens again. How do I test the ram stick to see if that is it?
     
  7. URX111

    URX111 Private E-2

    TNX for your replys: I have a ASUS P4S533 MB. It happened again last night.
    This is all I got copyed.
    Stop: 0X0000001E (0XC0000005,0XA0002356,0X00000000,0XA01E6A89)
    Address A000

    There was more but my computor rebooted. I'll try to get more when it happens again. How do I test the ram stick to see if that is it? How would I tell if its the mother board and is there a fix?
     
  8. Insomniac

    Insomniac Billy Ray Cyrus #1 Fan

    Diagnosing stop errors can be a challenge.

    As Pyrate said, it's normally drivers but it can be a Bios setting or failing hardware etc.

    HERE is some information.

    A lot of it is for technical support, but there is some info there that may help.
     
  9. da chicken

    da chicken MajorGeek

    0x1E means KMODE_EXCEPTION_NOT_HANDLED (kernel mode exception not handled).
    0xc0000005 usually refers to a memory access error.

    In general, there are only two kinds of programs that run in kernel mode: 1) The kernel, 2) Device drivers. Everything else runs in "protected mode", which allows the system to recover from a crash. The system can't recover from a crash (aka, an unhandled exception) from a kernel mode program. The "blue screen error" you see is the result of the kernel panicking and telling you why it stopped.

    You should be able to see the full message error in event viewer. Go Start --> Run --> "eventvwr.msc". Look under the System log for an Error (big red X) that occurred around the same time as your last crash. Hopefully (but not always) the event viewer lists a filename, which tells you which file caused the problem. Google the file (or post it here) and you know what driver (and therefore what device) caused the problem.

    This error is generally caused by a few things:
    1) Faulty device drivers. Either the files have been damaged, or there's a bug in the files. Download the most recent driver files and reinstall them. This is the most common cause.

    2) System is overclocked. Overclocking causes synchronization errors if you push the system too far. The system tries to read something it can't or write something it can't, and throws an exception. If you didn't overclock yourself, you probably don't need to worry about it. This is a common error if you overclock your system.

    3) System is overheating. Over time, dust can build up in a system. Dust not only can clog the air intakes, it can deposit on components inside and act as insulation. If the system seems to reboot while playing graphics intensive games, this is a possibility. Get a can of static-free air and blow the dust from your system. This is not a very common problem (dust buildup is common, but dust buildup causing overheat is not) however it is easy to check for and fix.

    4) A device or the system RAM is physically damaged. RAM can be tested overnight with MemTest86 or similar. Testing a damaged device is more difficult.
     
  10. URX111

    URX111 Private E-2

    TNX da Chicken: I went into event viewer and there was nothing red but when I clicked the last Memory Dump line I got this.
    The Computor has rebooted From Bugcheck. The bugcheck was:
    0x0000001e (0x0000005,0xa0002356,0x00000000,0xa01e6a89).
    Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\
    MEMORY.DMP

    I checked others, they had different numbers but saved in the same place.
    I'll get a can of that air and blow it out. What is MenTest86 how do I get it?
    It dumped three times yesterday and none today. I don't know whats going on, it just bugs me.
     
  11. URX111

    URX111 Private E-2

    Insomniac: TNX for the link. It looks like a 0x1e code, which meens a driver or BIOS. It may be to technical for me. I don't know if I can't solve it (I'll read more later) and it gets to bad I'll probley bring it in. TNX
     
  12. Insomniac

    Insomniac Billy Ray Cyrus #1 Fan

    You can read memory dumps with the correct debugging tools which you can download from Micro$$oft, but again it's really designed more for tech support and is far from conclusive.

    You can download Memtest from HERE.
     
  13. mors_crudelis

    mors_crudelis Private E-2

    is it possible that physical memory dumps occur due to an electric current ?(excuse me for my english i'm from belgium)

    e.g.:

    my printer (hp deskjet 930c) blocked (paper got stuck, started making funny/scary noises) and immeadiatly i got this message.
    my dad thinks he knows everything and says it's because of stuff related to electricy (he's an engeneer electronics so i guess he knows something about it..)

    but then again i see only 4 reasons here and none of them really is to be applied on my errors.

    it's definitly something fysical i guess...



    as for the regular stop messages... isn't it enough to update your windows with latest sec. packs and other available updates + drivers of graph/mobo/whatever ?

    :)
     
  14. URX111

    URX111 Private E-2

  15. maistrucfp

    maistrucfp Private E-2

    no printer.....no physikal.......it is your RAM try to mount more RAM......higher then 256........512 minimum......no printer ore something else.....pushapse is your RAM performance weake.....try 512 DDR 400MHz GEIL -- lifetime waranty
     
  16. kadavill

    kadavill MajorGeek

    Did you update your Graphic card driver.

    Check for device conflicts,
    Control panel>display>settings>advanced>adapter>properties>resources.
     
  17. URX111

    URX111 Private E-2

    :eek: I have 512 memery allready. I just went into display and it said no conflict, and I just updated my grafics driver two weeks ago. I wanted to see if I needed to update my M/B drivers but when I went The Asus site they had 4or5 different P4S533 M/Bs. So I either got to take my cover off or go by the computor shop and ask them what they put in, I got a feeling they might not know. So in the next couple of days I'll find out.
    TNX
     
  18. Olive Salsa

    Olive Salsa Private E-2

    Just for the record, I got this same error message and it was definitely from my pc being overclocked. I had just dl'ed/installed a pretty hefty online casino software and shortly thereafter I got the physical mem dump. Uninstalled the software, never seen the prob since.

    For the record...
     
  19. ~Pyrate~

    ~Pyrate~ MajorGeek

  20. URX111

    URX111 Private E-2

    TNX Pyrate: Thats a good program to have. My tempatures are
    MB 86*F, CPU 93*F, WDC 102*
    I went to the Asus site to down load updated drivers, then I read that if I don't know for sure that, that would fix a pacific problem, it might cause me more problems. Anyway it seems to be behaveing its self better lately. I deleated my online temp files and defraged my HD. I'll see what that does. It might be Alians takeing over my computor, I keep beating them at FPS, they'er sore losers. I read on the MSN site it might have to do with remote control or somethin-or-ether.
    TNX again
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds