Announcement

Collapse
No announcement yet.

Windows XP memory dump PROBLEM

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows XP memory dump PROBLEM

    These are the pics of what I'm seeing...and it happens upon boot up. Once XP starts...it basically dumps me on that screen. I have been able to get the computer running in safe mode but can't figure out what is causing this issue...any thoughts???



    http://memimage.cardomain.net/member_images/2/web/170000-170999/170063_221.jpg

  • #2
    Too blurry to read the details
    Dr. Ron Paul for President 2008

    Hope for America - http://www.ronpaul2008.com

    Who is Ron Paul? - Why do we need Ron Paul?

    __________________
    CarPC Newbs Start Here: All your questions answered, as if by E.S.P.

    Comment


    • #3
      try booting into the xp recovery console from the original cd and type "fdisk /mbr"0 at the prompt
      4G64 5 SPEED
      MY CAR - MY 5SPD - MY CARPUTER - MY GARAGE SALE

      Comment


      • #4
        Your pic must be blurry, cause I haven't opened a bottle today and I can't read it.

        Post what it says, paticularly from the technical specifications onwards
        Caputer Mk. II
        '02 VX Holden Commodore Series II Executive
        MII12000, 512MB RAM, 60GB HDD (5400rpm), 16X DVD, TS200V
        Morex 60W DC-DC, Custom S/SDC
        OS/Software: Developing...

        Comment


        • #5
          STOP Code

          On that screen, there is one line like this:

          STOP 0x0000 (0x0000, 0x0000, 0x0000, 0x0000)


          Tell me what those numbers are, and I can tell you where your problem is.

          Comment


          • #6
            Originally posted by Giuliano
            On that screen, there is one line like this:

            STOP 0x0000 (0x0000, 0x0000, 0x0000, 0x0000)


            Tell me what those numbers are, and I can tell you where your problem is.


            That was the funniest thing I've read all day.

            Never will a stop error like this (my experience now damn it!) tell you anything really about your specific problem. MS usually points at the ram first. That's what I usually point at first too. BUT, it could be ram, video, power supply, f*ed drivers, bad sectors on your hdd, anything really. I've even had a screwy prob with a floppy drive that caused stop errors when it was plugged in. Try the basic stuff first. Replace your ram, try a diff power source/supply, run an XP repair, remove devices from safe mode and try to boot... Ya know man. Maybe even try a different hard drive with a new install of XP on it.

            Take no offense Giuliano, I do not mean to degrade you or anything. MS just doesn't program the troubleshooting side of things to tell you anything about your STOP errors...
            Tidder

            Try RevFE
            The best resurrected frontend I've ever used, period.


            I Wish I could ban people

            Comment


            • #7
              Originally posted by Tidder
              That was the funniest thing I've read all day.
              I'm happy you were amused, but I was serious.

              Originally posted by Tidder
              Never will a stop error (my experience now damn it!) tell you anything really about your specific problem.
              I disagree - I work on high-end Windows server platforms for a living, and have had to occasionally debug a STOP error.


              In any case, I was saying that I could usually tell from the STOP code where the problem was, not what the specific problem was.

              Such as a bad driver, a corrupt filesystem, or a hardware error.

              The five numbers from a STOP code can mean a lot.. to those who know how to interpret it.

              Comment


              • #8
                Originally posted by Giuliano
                The five numbers from a STOP code can mean a lot.. to those who know how to interpret it.
                HAHA!!

                I just it man. C'mon now, I'm not gonna sit here and try to interpret ANYTHING! I just hope that someone else out there isn't as lazy as I, and has the answer.
                Tidder

                Try RevFE
                The best resurrected frontend I've ever used, period.


                I Wish I could ban people

                Comment


                • #9
                  Well, I appreciate all the input thus far folks. Below is what it says after Technical info:

                  STOP: 0x0000008E (0xc0000005,0x8059231E,..........., 0x000000000)

                  I didn't copy the last 2 sections but I recall the last one being all 0's...

                  Giuliano or anyone...any help would be greatly appreciated.
                  http://memimage.cardomain.net/member_images/2/web/170000-170999/170063_221.jpg

                  Comment


                  • #10
                    When I was young, I found a beauty of Google tool:

                    http://www.google.com/search?hl=cs&q=0x0000008E&lr=

                    first hit:
                    http://support.microsoft.com/default...;EN-US;Q315335

                    man....

                    Comment


                    • #11
                      Originally posted by oekundar
                      Well, I appreciate all the input thus far folks. Below is what it says after Technical info:

                      STOP: 0x0000008E (0xc0000005,0x8059231E,..........., 0x000000000)

                      I didn't copy the last 2 sections but I recall the last one being all 0's...

                      Giuliano or anyone...any help would be greatly appreciated.
                      The first number tells me that the crash is what's called a Kernel Mode Exception, and the second number tells me that the problem is related to memory, and / or drivers.


                      A good description of the bug check code:
                      http://msdn.microsoft.com/library/de...b81455.xml.asp

                      I would check your RAM sticks, and remove and re-seat them in their sockets.
                      If you have more than one stick of RAM, try running with only one stick, and then add the rest until you get the problem again.

                      If that doesn't fix it, you may have a dodgy driver that is causing the crash.

                      If you're able to boot up in safe mode, chances are that driver was disabled while you were in safe mode, making the system run stable, but only in safe mode.

                      Comment


                      • #12
                        Thanks for all the assistance gents...btw Giuliano...Lawrenceville is ok with me...I've got family that lives off of 316 down in that area
                        http://memimage.cardomain.net/member_images/2/web/170000-170999/170063_221.jpg

                        Comment

                        Working...
                        X