Frustrating computer problems

  1. #1
    dumediat is offline Newbie

    Frustrating computer problems

    Hello everyone, I'm new to this site, and I hope someone can help me. I just built my first computer this May, but I have been having nothing but problems with it since the day I built it. First, I'll give the specs of my computer:

    HD: Western Digital Caviar SE16 WD2500KS 250GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM
    RAM: OCZ 2GB (2 x 1GB) 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered Dual Channel Platinum System Memory
    Power supply: Antec TRUEPOWERII TPII-550 ATX12V 550W Power Supply - Retail
    Processor: AMD Athlon 64 X2 3800+ Manchester 2000MHz HT Socket 939 Dual Core Processor
    Graphics: eVGA 256-P2-N554-AX Geforce 7600GT 256MB GDDR3 PCI Express x16
    M/B: ASUS A8N-E Socket 939 NVIDIA nForce4 Ultra ATX AMD
    Other drives: ASUS 16X DVD±R DVD Burner With 5X DVD-RAM Write Black E-IDE/ATAPI Model DRW1608P2S - OEM

    I should note that this computer was ordered wholly through NewEgg.com, so everything was check for compatibility. (That I know of) OK, now to the problems I've been having. At first, I was getting BSOD's with the following message...

    STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER

    Also, the computer would lock up periodically with no error messages or anything else. I tested the RAM using Memtest86, with each stick individually for 16+ hours each, and they both passed with no problems. So, I decided it was the graphics card, and I got an RMA from E-VGA. That solved the problem, but then others started showing up. I started getting BSOD's with this message...

    MACHINE_CHECK_EXCEPTION 0x0000009C (0x00000004 0x8054D5F0 0xB2000000 0x00070F0F)

    This was after I updated all of the drivers, so one by one I rolled back the drivers until I stopped getting the error message. (It happened to by the new graphics card driver released by E-VGA) Then, E-VGA recommended that I re-download DirectX 9.0c, which I did. Then, my computer ran fine for a while, but then I started getting more lock-ups. I checked EventViewer, but nothing was wrong there. I gave my graphics card to one of my friends to try to rule that out, and it worked beautifully in his machine. Now, most recently, I have been getting the following BSOD...

    MACHINE_CHECK_EXCEPTION nv4_mini.sys B2000000 Base at B1F18000 DateStamp 43f17114

    I noticed that this BSOD had no hexadecimal memory addresses, but rather gave me a file name. I guess this is related to the m/b, but I have no idea how. I know that my m/b uses the nForce4 chipset and associated drivers, but I have no idea how to find out what is causing the error. I should also say that I have checked all temperatures and voltage rails, and nothing is out of the ordinary.

    Could someone please help! I would very much appreciate it.


  2. #2
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Is this XP SP2?

    Also: Is your RAM set in the proper slots? Most likely 1 & 3 or 2 & 4.

    Also:

    Check your Page File Size:

    Right click My Computer then click Properties

    Advanced > Performance > Settings > Advanced > Virtual memory > Change

    Is this set to System Manage Size?




    http://www.petri.co.il/pagefile_optimization.htm

  3. #3
    dumediat is offline Newbie
    Yes, I am running SP2, and I have quadruple-checked that the RAM is in the proper slots (1&3). Also, my page file size was set at custom, but I did what you said and checked "system manage size." Do you think that was my problem?

    Thanks for the help, BTW.

  4. #4
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    From a brief search of your errors that was a general suggestion.

    Let us know if the errors persist and what they are.

    Also:

    http://support.microsoft.com/?kbid=329284

  5. #5
    dumediat is offline Newbie
    Well, it ran fine for a few days (as it always does whenever I change a setting or update a driver...), but it just crashed on me when I was playing Links 2003. I was simply playing the game, and it froze all of a sudden. I tried control-alt-delete, but it just brought up a blank desktop (like it was trying to bring up the task manager screen). Any other ideas on what might be causing it?

+ Reply to Thread