Jump to content

ApolloX

Members
  • Content count

    37
  • Joined

  • Last visited

About ApolloX

  • Rank
    New Member
  1. According to something I was reading in another forum, I've heard its possible the issue could be related to a voltage issue on the DFI motherboard. It would explain the odd behavior to some degree. Anyone hear of this before?
  2. I have an ATI x1950Pro (<9 months old) that a few months ago started booting windows in 4bit color mode (640x480) randomly. I tended to ignore it as after 2-3 boots it would go away. Then I had to reinstall windows for an unrelated issue and now the video is generally hosed. It starts in 4bit mode every time. Here are the symptoms: With ATI drivers Windows starts in 4bit mode 99% of the time. I rarely install the drivers with ccc (Catalyst Command Center) since this just produces errors in 4bit mode that video was not properly detected Using Windows-native startup (no drivers installed) it starts in high resolution (1280x1024x16mill).... but without drivers, animation is practically non-existent If I install the drivers manually using "Update Driver" Windows will sometimes switch to 4bit mode without a restart. (weirdest thing) I got it started once in normal mode with drivers, played a video game for about 2 hours, no problem, then as soon as I exited the game, Windows immediately switched to 4bit mode without a restart I tried moving the card into my other PCIe slot (SLI motherboard) as well as trying the other DVI output. Zero change. Ran Driver Cleaner Pro and Driver Sweeper (in and out of safe mode), tried all sorts of removal/install methods, and tried multiple ATI and Omega versions. It seems like the 4bit issue has occurred before but I haven't found many people who have had it recently. Since its xmas, an ATI's support department is closed for 2 weeks I think I'm stuck buying a new card (RMA would take awhile...) or using the computer without any drivers (no games, no movies, choppy visuals). Any suggestions before I throw the card away?
  3. ApolloX

    Command & Conquer 3 Tiberium Wars - Crashing anyone?

    As a brief update, I did go to EA forums and my god are those people retarded. Most of them didn't read my post and gave me useless advice such as "buy more RAM" and "close more programs". You'd think I was running with no open memory (meanwhile I have >1.6gigs free). I wish all forums were like DIY Street... can't trade the quality.
  4. ApolloX

    Command & Conquer 3 Tiberium Wars - Crashing anyone?

    Tried that all ready, nothing.
  5. So I picked up Command & Conquer 3 Tiberium Wars and for the most part I really like it but on the high level missions it started crashing quite frequently with a Direct3D OUT OF MEMORY error. Since the people on here are way smarter than the EA support people, I thought I'd run a poll to see if anyone playing the game has seen this issue and had a solution. Seems like other people have gotten this but no one posts much in the way of a solution. I tried all the basic stuff like lowing the graphics (nothing like disabling AA and lowering the resolution to crap on a higher level video card) and closing un-needed programs but no change. Here's a screenshot of a guy with the same error:
  6. ApolloX

    Random Crashes

    Yes although there haven't been 'new' nvidia drivers for AMD NF4 in 9 months.
  7. ApolloX

    Random Crashes

    PSU cleanliness is highly over-rated, especially on this forum. That being said I replaced the psu last year so nope, not that.
  8. ApolloX

    Random Crashes

    100,1,Yes The tests run just fine under normal conditions but then at some point (anywhere from 1-40 hours) the video dies, the screen goes black, and the machine shuts down with an nvp BSOD. That's been the consistent shape every time except the last time where the screen went black, but then revived, only to go black every few seconds until I finally restarted. At that point I'm sure directx tests would have failed since I couldn't even run a screensaver normally.
  9. ApolloX

    Random Crashes

    Actually I forgot to change my signature, I'm upgraded my PSU to OCZ 600 awhile ago. I've determined its definitely related to the video although whether its hardware or software I cannot tell. A few minutes ago the screen went black but instead of getting a BSOD it returned to the OS. About 5-10 seconds later the screen went black again. This continued about 20 times before (going black for 1 second then recovering for 5) before I decided it was time to reset. Since the system never fully shut down (mouse/keyboard were responsive) I was able to conduct some ad-hock tests. First off, when I dropped to a dos prompt and full-screened the flickering stopped all together. When I went back windows gui they returned. I tried doing something simple like a screen saver (3d flower box, 3d text) and the results I saw were odd. Aside from the continued shutting down every couple of seconds, the graphics while they were being used were hicupping back and forth. So for the flower box I saw jittery images. Its definitely related to the video card at this point. I got luck in that it did not fully shut down. Did my card go bad or do I need to reinstall windows? I tried switching drivers but no luck.
  10. ApolloX

    Random Crashes

    I should also mention that sometimes after the crash, windows fails to boot with the message "NTLDR is missing". I have to do a cold restart in order to get the system to boot after that. Anyone have any ideas?
  11. ApolloX

    Random Crashes

    Wish I knew. Also wish I knew why this suddenly started happening with some frequency (1-2 a day variable) out of nowwhere. Anyone?
  12. ApolloX

    Random Crashes

    UPDATE: I found it it was the nv4_disp.dll BSOD causing the problem. I assumed by the beeps and black screen there was no BSOD coming but I started waiting 20 seconds and it appeared. Anyone know why this error would suddenly start appearing in normal windows behavior (heck, just using aim) very frequently out of nowwhere? Is it systemic of a hardware failure? I've tried reinstalling the drives but no luck.
  13. Hey Guys, My computer for the last week or two has started crashing for almost no reason. I've run all the basic diagnostic stuff but come up with zip. *DESPERATELY* hoping someone can give me advice on how to resolve it. Symptoms: First, the system locks up but the mouse is still responsive, then 1-2 seconds later mouse locks completely, a few seconds after that the screen goes black and often times (although not always) the computer starts beeping. Most of the time when it does beep its a single beep, although one time it beeped multiple times alternating between high and low pitches. Frequency: Seems like it occurs if I use the computer for more than 20 mins at a time. If I leave it alone for hours it does crash. No specific program seems to be responsible. Sometimes there are days between crashes, other times minutes. Temperatures: All low (30C). I did have the temperature monitor open during 2 of the crahses and nothing was hot. All fans are running and I've checked the seating of the CPU cooler. Testing: I ran MemoryTest86 as well as 2xPrime95 and neither demonstrated any problems. I can't even determine if this is a hardware or software issue. The way its crashing makes me think software but the fact that the computer is beeping and screen goes black, makes me think hardware. Anyone have any ideas as to what I should do next? PS I've turned off all overclocking and using loose timings, but with no change. Also, nothing in the Windows Event Viewer records any errors.
  14. ApolloX

    Isolating Bad Memory

    Umm.. I think you misunderstood, my last paragraph description was with all 4 in, but the bad one (originally unknown) moving around. Once the bad one was located it could only be used in the orange slot furthest from the CPU by itself for individual testing.
  15. ApolloX

    Isolating Bad Memory

    Actually, tried something else. Testing one at a time wasn't producing an immediate error whereas testing 4 at a time got an error in a specific (consistent) bad address location in about 10 seconds... so I alternated 2 sticks repeatadly and recorded if the memory address that failed first changef. After two rotations I had the bad stick isolated and after 20 mins of running the stick by itself (now that I had a likely candidate) produced an error confirming it was the one bad one. I was looking for some knowledge of addressing so that I didn't have to run each stick for hours (at least not without having some idea of which one is bad), so the tip didn't really help. Interestingly, I still don't understand the addressing (but I got the bad stick). When the bad stick was in the orange furthest from the cpu, the bad memory address was around 2500mb, when it was in the yellow furthest from the cpu, the address was around 536mb, and when it was in the orange closest to the cpu, it was around 737mb. Not very consistent to me.
×