Help

Discussion in 'General Hardware' started by klicki, Jul 30, 2003.

  1. klicki

    klicki Guest

    For about 2 weeks now my new computer has been crashing usually once a day with stop errors:
    0x00000050 (0xd8e4ce38, 0x00000000, 0xf76fcf2a, 0x00000000)

    0x1000008e (0xc0000005, 0xbf876bed, 0xa9e9a1b0, 0x00000000)

    0x00000024 (0x001902f8, 0xaa15a5d8, 0xaa15a2d8, 0xf7706922)

    0x1000008e (0xc0000005, 0x805368a0, 0xf7a4e7d0, 0x00000000)

    0x1000008e (0xc0000005, 0x804ed3e0, 0xf7f11b04, 0x00000000)

    0x0000000a (0x00000000, 0x00000002, 0x00000001, 0x804eaa70)

    0x0000000a (0x00000004, 0x00000002, 0x00000001, 0x804dca98)

    They are just a few of them. I was advised that the problem may be RAM. I have 2 512MB sticks of DDR3200 RAM installed and have tried removing each stick to try and identify the defective one but I still get the stop errors with either stick and I know that its unlikely that both sticks are faulty.

    The errors began about a week after I bought it so i don't think its device drivers that are causing the problem because I haven't updated or changed any driver or added any new hardware for that matter.

    Thanks in advance.

    System Specs:
    Motherbaord: Soltek 75FRN2-L
    CPU: AMD Athlon XP 2600
    RAM: 2x 512MB PC3200 DDR
    HDD: Seagate 120GB Barracuda
    CD-ROM: Lite-On 52x CDROM
    CD-RW: Sony 8x/4x/32x
    Video Card: Leadtek Winfast A310 MyViVo 256MB GeForce FX5600 8x AGP
    NICs: 2 Realtek 10/100
     
  2. TheBlueRaja

    TheBlueRaja BR to Some

    Messages:
    766
    Location:
    Fawkirk!
    Does it mention a file name like nv4disp.dll or something similar?
     
  3. Hipster Doofus

    Hipster Doofus Good grief Charlie Brown

    Messages:
    5,920
    Location:
    Melbourne Australia
    Welcome to the forums klicki. :)

    What operating system are you using?
     
  4. klicki

    klicki Guest

    Thx Hipster. Windows XP Pro.
     
  5. Hipster Doofus

    Hipster Doofus Good grief Charlie Brown

    Messages:
    5,920
    Location:
    Melbourne Australia
    Two of those numbers get mentioned here but it is discussing XP setup. Seems to be pointing to bad ram. It could be an incompatability problem.

    Try a memory tester from here. Look around for the free one.
     
  6. Erbmaster

    Erbmaster Moderator Folding Team

    Messages:
    1,195
    Location:
    Middle Of Nowhere - UK
    Try running with 1 stick of RAM then try using the other.
    This way you should be able to pinpoint the bad stick of RAM.

    (provided they aren't both shot :eek: )
     
  7. Zedric

    Zedric NTFS Guru Folding Team

    Messages:
    4,006
    Location:
    Sweden
    Try Memtest x86. http://www.memtest86.com/
    It runs from a boot disk so it won't be affected by the Windows environment. Also it's completely free. :)
     
  8. Petros

    Petros Thief IV

    Messages:
    3,038
    Location:
    Pacific Northwest
    Does the density of your RAM match what the motherboard manufacturer specifies? Some newer motherboards don't play well with high-density RAM.
     
  9. klicki

    klicki Guest

    Thx for all the replies guys. I think the problem was the pagefile. I may have been corrupt. I tired disabling it yesterday and i haven't had a single crash.

    Thx again.
     
  10. Hipster Doofus

    Hipster Doofus Good grief Charlie Brown

    Messages:
    5,920
    Location:
    Melbourne Australia
    Thanx for the feedback. :)

    Have to make a note of that. How did you go about disabling the pagefile?
     
  11. Erbmaster

    Erbmaster Moderator Folding Team

    Messages:
    1,195
    Location:
    Middle Of Nowhere - UK
    This used to work for NT 2K etc. Not tried it on XP tho...

    Prevent Windows from paging the executive portions of the
    operating system to the pagefile on the hard disk. Open Regedit and enter the following>>

    HKey Local Machine>System>Current Control Set>Control>Session Manager>Memory Management

    Value= DisablePagingExecutive

    Data Type= REG_DWORD

    Data = 1

    Then Reboot
    ;)