1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Random Restarts [DUMP DATA]

Discussion in 'Windows XP' started by DJRob, 2006/03/03.

  1. 2006/03/03
    DJRob

    DJRob Inactive Thread Starter

    Joined:
    2006/03/01
    Messages:
    6
    Likes Received:
    0
    Hi,

    I've been experiencing lots of random restarts and am clueless as to why. You can see my specs here.

    I don't know if it's hardware... software or what, but I made a log of the dump file created by my latest restart. It's greek to me but does it make sense to anybody???

    Here is the log

    Thanks a lot,
    Douglas
     
  2. 2006/03/03
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Well, I'm no expert in reading these, but

    Suggests you may want to check out either a newer or older driver for your graphics card (I say older because that DLL shows a date of Jan 24 2006, so you may check out to see if an older version is more stable).
     
    Arie,
    #2

  3. to hide this advert.

  4. 2006/03/04
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Hi,

    According to "Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors "

    Your problem occurs at data read at L2 cache memory. I believe that it is hardware error L2 cache memory of the AMD processor. Forward the problem to AMD and ask for RMA.

    - Bios and Kernel Developers Guid for AMD Athlon(r) 64 and AMD Opteron(r) Processors
    Bit Mask:

    MA Model Specific MCA
    O ID Other Information Error Code Error Code
    VV SDP ___________|____________ _______|_______ _______|______
    AEUECRC| | | |
    LRCNVVC| | | |
    ^^^^^^^| | | |
    6 5 4 3 2 1
    3210987654321098765432109876543210987654321098765432109876543210
    ----------------------------------------------------------------
    1100010000001000010000000000000000000000000000000000000100110110

    MEMHIRERR - Memory Hierarchy Error {TT}CACHE{LL}_{RRRR}_ERR
    These errors match the format 0000 0001 RRRR TTLL

    Concatenated Error Code:
    --------------------------
    _VAL_OVER_ADDRV_MEMHIRERR_36

    This error code can be reported back to the manufacturer.
    They may be able to provide additional information based upon
    this error. All questions regarding STOP 0x9C should be
    directed to the hardware manufacturer.


    Table 21. Memory Transaction Type Bits (RRRR)
    0000b Generic error (GEN)
    0001b Generic read (RD)
    0010b Generic write (WR)
    0011b Data read (DRD) <--
    0100b Data write (DRW)
    0101b Instruction fetch (IRD)
    0110b Prefetch
    0111b Evict
    1000b Snoop (probe)

    Table 19. Transaction Type Bits (TT)
    00b Instruction
    01b Data <--
    10b Generic
    11b reserved

    Table 20. Cache Level Bits (LL)
    00b Level 0 (L0)
    01b Level 1 (L1)
    10b Level 2 (L2) <--
    11b Generic (LG)
     
    Last edited: 2006/03/04
  5. 2006/03/04
    giles

    giles Inactive

    Joined:
    2002/01/08
    Messages:
    270
    Likes Received:
    0
    Hi DJRob.

    You appear to have more than 1 memory stick. I would remove all but one and see if it restarts again. If it does, swap the remaining memory stick with one of the ones removed and see what happens. I suspect a memory problem. You also might check the memory settings in the bios.

    One further comment. I suspect a problem with the external hard disk. Your post in the other thread says "This error was reported by the CPU via Interrupt 18." Interrupt 18 is a USB interrupt and that is probably tied to the external hard disk. You might change USB ports and see if that has an effect. You might have another device on one of the USB ports that might be causing a problem tho but it's probably the hard disk drive. You might just mount that external hard disk internally for a while and see if the problem goes away.

    Also, the next time it happens, immediately check your CPU temperature.

    Giles
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.