1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XP machine exception

Discussion in 'Windows - General discussion' started by ZippyDSM, Sep 20, 2006.

  1. ZippyDSM

    ZippyDSM Active member

    Joined:
    Aug 3, 2005
    Messages:
    1,723
    Likes Received:
    0
    Trophy Points:
    66
    I am getting this error once every few days I want to track down what hardware is screwing with me I have a thought tis that damn SB Sound card could be the ram and no I don't have the code on me right now need to write it down when it crashes.
    BUT can you tell me where the best place to look up codes and such are?
     
  2. DoubleDwn

    DoubleDwn Regular member

    Joined:
    Sep 27, 2005
    Messages:
    877
    Likes Received:
    0
    Trophy Points:
    26
  3. ZippyDSM

    ZippyDSM Active member

    Joined:
    Aug 3, 2005
    Messages:
    1,723
    Likes Received:
    0
    Trophy Points:
    66
    Had my first BSOD in acouple days or so

    0X00000004,0x805366f0,oxB2000000,0x0007f0f


    from what little I could find on the net so are it seems ram related.


     
  4. Niobis

    Niobis Active member

    Joined:
    Jan 30, 2005
    Messages:
    2,326
    Likes Received:
    0
    Trophy Points:
    66
    Last edited: Sep 21, 2006
  5. ZippyDSM

    ZippyDSM Active member

    Joined:
    Aug 3, 2005
    Messages:
    1,723
    Likes Received:
    0
    Trophy Points:
    66
    theres more numbers tha that? 0_o
    *eyes bug out from all the numbers and fall off* LOL
     
  6. DoubleDwn

    DoubleDwn Regular member

    Joined:
    Sep 27, 2005
    Messages:
    877
    Likes Received:
    0
    Trophy Points:
    26
    Yeah, your actual stop code would look something like this :

    STOP: 0X0000009C (0X00000004, 0X805366F0, 0XB2000000, 0X00070F0F)

    This could be due to using non-ecc memory when the mobo wants ecc memory, or vice versa. Or it could just be a bad stick. How many sticks do you have? If more than one, only run one at a time and try to duplicate the BSOD. If you cant do it, switch to another memory card. Keep trying each card.....when you get the BSOD, you have found the bad card (assuming that it is a bad memory chip, not the incorrect memory). Are all the sticks the same brand/speed/timings???

    ~Rich
     
  7. ZippyDSM

    ZippyDSM Active member

    Joined:
    Aug 3, 2005
    Messages:
    1,723
    Likes Received:
    0
    Trophy Points:
    66
    Funny becuse it started with the 0x00000004 code 0-o

    I have 2 and have done more than 8 hours of mem test X86 on them,my mobo is a DFI nf3 ultra D the sticks are Hyundai Electronics 2 512 400 Mhz running at least than 400. (320)

    I knwo thsi mobo is VERY ram sensitive I ahve 2 other 512 sticks 1 inronynx and one consiar value and neither of them work at all.
    I really need to put 100-200 for 1-2GB of good ramm....but its running all thats most important right now...


    Meh it takes 1-3 days for the BOSD to pop up,I'll get the whole code then ,then go from there...
     
    Last edited: Sep 22, 2006
  8. ddp

    ddp Moderator Staff Member

    Joined:
    Oct 15, 2004
    Messages:
    39,158
    Likes Received:
    134
    Trophy Points:
    143
    use a pencil eraser on the gold contacts on the ram sticks & reseat the stick.
     
  9. ZippyDSM

    ZippyDSM Active member

    Joined:
    Aug 3, 2005
    Messages:
    1,723
    Likes Received:
    0
    Trophy Points:
    66
    ddp
    I'll try that next crash.

    I have been playing with the ramm timings a little to smooth out performance its not crashed in 3 days so I think its behaving *L*
     

Share This Page