Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: beginning dump of physical memory  (Read 4103 times)

0 Members and 1 Guest are viewing this topic.

myrtle_arnele

    Topic Starter


    Greenhorn

    beginning dump of physical memory
    « on: June 29, 2009, 05:22:49 AM »
     i just received this message appeared in blue screen, it says" STOP 0X0000007E (0X000005, 0XF796013B, 0XF89882E8, 0XF8987F34) PLEASE HELP TO FIX THIS PROBLEM

    Quantos



      Guru
    • Veni, Vidi, Vici
    • Thanked: 170
      • Yes
      • Yes
    • Computer: Specs
    • Experience: Guru
    • OS: Linux variant
    Re: beginning dump of physical memory
    « Reply #1 on: June 29, 2009, 10:39:35 AM »
    What OS and service pack are you running?
    Evil is an exact science.

    paudashlake



      Hopeful

      Thanked: 6
      • Experience: Experienced
      • OS: Windows 7
      Re: beginning dump of physical memory
      « Reply #2 on: June 29, 2009, 10:50:46 AM »
      For windows xp it usually tells you to use safe mode and uninstall any recently installed programs, because one may not be cooperating with your system.  What were you doing at the time that this occured?
      Hinkle Finkle Dinkle Doo.  AMEN!! 


      Quantos



        Guru
      • Veni, Vidi, Vici
      • Thanked: 170
        • Yes
        • Yes
      • Computer: Specs
      • Experience: Guru
      • OS: Linux variant
      Re: beginning dump of physical memory
      « Reply #3 on: June 29, 2009, 11:00:18 AM »
      Quote
      For windows xp it usually tells you to use safe mode and uninstall any recently installed programs, because one may not be cooperating with your system.  What were you doing at the time that this occured?

      That's not what those codes are referencing.

      Each of those codes actually means something.

      Quote
      0X000005
      This code is also associated with Exchange Server.
      Evil is an exact science.

      paudashlake



        Hopeful

        Thanked: 6
        • Experience: Experienced
        • OS: Windows 7
        Re: beginning dump of physical memory
        « Reply #4 on: June 29, 2009, 11:04:11 AM »
        Oh woops I never read the codes....my bad.   :'(
        Hinkle Finkle Dinkle Doo.  AMEN!! 


        Quantos



          Guru
        • Veni, Vidi, Vici
        • Thanked: 170
          • Yes
          • Yes
        • Computer: Specs
        • Experience: Guru
        • OS: Linux variant
        Re: beginning dump of physical memory
        « Reply #5 on: June 29, 2009, 11:06:55 AM »
        Quote
        Oh woops I never read the codes....my bad.   


        We all make mistakes, part of the 'Human Condition' and 'stuff'.
        Evil is an exact science.

        paudashlake



          Hopeful

          Thanked: 6
          • Experience: Experienced
          • OS: Windows 7
          Re: beginning dump of physical memory
          « Reply #6 on: June 29, 2009, 08:33:32 PM »
          I'd imagine so.  'Live and learn'  ;)
          Hinkle Finkle Dinkle Doo.  AMEN!! 


          BC_Programmer


            Mastermind
          • Typing is no substitute for thinking.
          • Thanked: 1140
            • Yes
            • Yes
            • BC-Programming.com
          • Certifications: List
          • Computer: Specs
          • Experience: Beginner
          • OS: Windows 11
          Re: beginning dump of physical memory
          « Reply #7 on: June 29, 2009, 08:42:06 PM »


          We all make mistakes, part of the 'Human Condition' and 'stuff'.


          for example- saying it was code 0x00005 when in fact it was

          Quote
          STOP 0X0000007E

          0x5 was the first argument passed to keBugCheckEx()... oops, Too much information!  ;)


          There is a KB article about this STOP code (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED)

          http://support.microsoft.com/kb/330182


          Almost surely a bad driver or hardware, depending on the file that is causing the STOP code.
          I was trying to dereference Null Pointers before it was cool.

          Quantos



            Guru
          • Veni, Vidi, Vici
          • Thanked: 170
            • Yes
            • Yes
          • Computer: Specs
          • Experience: Guru
          • OS: Linux variant
          Re: beginning dump of physical memory
          « Reply #8 on: June 30, 2009, 09:08:09 PM »
          Good catch BC.

          myrtle_arnele, let us know if that article helps.
          Evil is an exact science.

          myrtle_arnele

            Topic Starter


            Greenhorn

            Re: beginning dump of physical memory
            « Reply #9 on: August 22, 2009, 05:20:46 AM »
            hi guys,  sorry for the late reply..


             i just get back from long journey...
             
            all your suggestions help to solve my problems..

            thank you very much.

            myrtle_arnele

              Topic Starter


              Greenhorn

              Re: beginning dump of physical memory
              « Reply #10 on: January 10, 2010, 08:23:28 PM »
              i just received this message appeared in blue screen, it says" STOP 0X0000007E (0X000005, 0XF796013B, 0XF89882E8, 0XF8987F34) PLEASE HELP TO FIX THIS PROBLEM

              furious_22



                Rookie

                Re: beginning dump of physical memory
                « Reply #11 on: January 18, 2010, 10:21:52 PM »
                I think you has at least two memory slots...try to disconnect your RAM and reconnect it to other slots