Jump to content

siim2200

Member
  • Posts

    25
  • Joined

  • Last visited

Awards

This user doesn't have any awards

About siim2200

  • Birthday August 3

Profile Information

  • Gender
    Male

Recent Profile Visitors

231 profile views

siim2200's Achievements

  1. I first contacted Asus and got them to approve the RMA. Then I contacted LTT Store and forwarded to them my emails with Asus.
  2. Can you try my test I wrote here? I suspect there's a lot of faulty 6800XTs failing the same way. Or have you managed to solve the issue already?
  3. A bit of googling has led me to reports of other AIB models crashing like this as well. I'll try to get some owners of those other faulty cards to try my Halo test to make sure this is an identical issue. Yeah, I've tried forcing both PCIE 3 and 4 but it didn't fix it.
  4. Interesting. For me at least the game audio stops too, only leaving a glitchy stuttering noise playing (like the last millisecond of audio on loop or something). Also any logging software stops logging after the black screen, indicating a complete windows crash. Is it the same for you? I haven't tried the two tips but I'll give it a go soon.
  5. I have. Didn't fix the crashing in the Halo test. But maybe it'll help in other games, let me know how it goes. By the way, update on the RMA situation: LTT Store says that Asus can't provide replacements due to supply constraints and can only give refunds (includes shipping, but not the import duties, which I would have to ask for from my local authorities). I asked and they confirmed that we have until the end of the warranty period (so like over a year) to claim the refund. Currently I'm planning on living with the crashes/playing games that don't crash (Rust is safe to play for example) until GPU prices drop some more so I can get an equivalent or even better card new for the refund money. To be honest, I was naively hoping LTT would take some action and push Asus to get us functioning replacements or market-value refunds under the threat of making a video/WAN show topic about this, but obviously they are under no obligation to do that. I've emailed Gamers Nexus and tweeted at some other folks asking if they'd like to take a look at the card and figure out how Asus/AMD messed it up but haven't got a reply (if others are interested in this, let them know). It's sad how VAG, designed to help alleviate the demand for GPUs, ended up itself becoming victim to declining quality control caused by manufacturers trying to squeeze every penny out of that insane demand. We even paid an increased MSRP for this piece of junk!
  6. Go for it if you have the time. I haven't messed with the C-states yet myself (but considering this happened with a different motherboard from another manufacturer I doubt that's the issue, still worth trying). I haven't found anything in the event viewer at the time of the crash either. I use it in 4.0 but I have tested with 3.0 as well, didn't make a difference. There's no VBIOS update for the TUF 6800 XT, confirmed by Asus. Have you contacted Asus support for an RMA yet? The more reports the get about this the quicker they'll probably look into the issue.
  7. So, Asus got back to me. They said they don't think this is a common issue and they will just RMA the card. Considering one person already got an RMA replacement that is starting to crash again, I doubt this is an actual solution. Let's see if LTTstore has any thoughts about this, we're sending a detailed email about the situation to them. Currently I recommend anyone having this issue contact Asus support for an RMA. EDIT: Here's what Asus wrote to me after I asked them to look deeper into why so many are having issues with this card: "Thank you very much for the feedback and additional information about the problem, we will study them as far as possible - it may take quite a long time until cards with such symptoms reach the R&D department for detailed diagnosis. Nevertheless, we will do all our best and try to understand what exactly the problem is and what options for solving it are possible. Up to this point, we have not encountered anything like this."
  8. Thanks for testing it out! Basically certain it's the same issue at this point. The guy I mentioned who was crashing in Cyberpunk and other games tried it too but he didn't crash, so it might not be a litmus test for 100% of faulty cards but good to know I'm not the only one with this specific crash.
  9. Gave it a try. I set my frequency to 80% in Radeon Software and started reducing voltage by 5%, down to 80%. Still got crashing at every voltage. Doesn't seem like undervolting/clocking is a fix, tho I might try messing with memory voltage in another software. EDIT: Ok looks like the other over/underclocking software requires BIOS flashing, which I'd rather not do.
  10. @Radium_Angel Yesterday I played a couple hours of Cyberpunk on Windows and on Linux. Started new games with the same path on both, same settings. I crashed twice on Windows and 0 times on Linux. If it really is bad hardware, it should crash more often on Linux as it's less tolerant right? On the other hand, I spoke with another VAG 6800XT owner who was having the exact same issues. He started experiencing more and more frequent crashes in the summer. He swapped out his card with his friend's TUF 6800XT, who also bought it from VAG. This fixed the crashing for him and made his friend's pc start crashing - pretty clearly hardware related. He got an RMA and the new card was fine but after about a month he just started getting crashes again. And now his friend is getting crashes too. It really is starting to seem like going Nvidia or alteast some other AIB AMD card is the only solution, but I really want Asus/AMD to make some sort of statement and address the issue.
  11. Did some more testing in Halo Infinite and decided to write up the replication steps for anyone willing to try: 0. Install Halo Infinite on Steam (it's free) 1. In Halo Infinite video settings, press F to restore defaults. 2. Set Resolution Scale to 2560x1440, or close to that if your monitor doesn't scale perfectly. 3. Set Minimum Framerate to Off 3. Turn off Vsync 4. Set Maximum Frame Rate to Unlocked 5. Set Quality Preset to Ultra 6. Make sure Borderless Fullscreen is enabled 7. Return to the main menu (image for reference) 8. Wait 5-30 minutes (longer if you want to be sure). Your PC should crash to a black screen, fans and LEDs stay on. I should note not all of these settings seem to be necessary, but I've included them just in case, as most of my testing was done with them. I've been getting it to crash even at the Low preset, although it takes longer to crash. The resolution and framerate definitely seem to be integral though. Of course, the settings necessary to crash my PC might differ from others based on the other components of the system. If the game doesn't crash, I recommend restarting the pc (sometimes I wouldn't crash for a long time, after a restart crashed immediately) and/or changing the resolution and trying again, just to be sure. @Radium_Angel I spent quite a few hours in GTA5 and Life is Strange: True Colors (a game Ruslanets experienced crashes in) on Linux Mint and I've yet to crash. However, I haven't managed to crash either game reliably on Windows either so it's a bit hard to gather anything from that. If Halo Infinite gets working with Proton that should help clear things up but right now I'm pretty stumped on the Linux thing (aside from playing games on Linux hoping my PC crashes eventually).
  12. Bumping to get some more opinions, giving an update meanwhile: I haven't managed to make any games available on Linux crash yet in Windows (tried Shadow of Tomb Raider demo, Dying Light and GTA5 again). I'll keep looking but no luck so far. AMD support gave me a few more troubleshooting steps, none of which helped. They then told me to submit a driver bug report through Radeon Software. I did it but it seems like they don't respond to tickets so I can only hope a future driver fixes it somehow. Also gave a detailed report to Halo Support, they just said they'll note the issue but have no fix or info about it. I've found other folks here having similar issues with this card, so it would make sense that Asus is shipping out faulty GPUs. I've contacted them to see if we can replicate each-other's crashes. If this was a case of a faulty batch of Asus graphics cards, how should I go about getting this fixed? How do I get Asus to own up to this not being a driver issue? EDIT: Played some RDR2 at 1440p Ultra and got the same black screen crash pretty quickly. I tried to get it running in Mint but I couldn't get it to work yet,
  13. Most of the testing was done with XMP and Asus Performance Enhancement off, no OC on the card (I even set the physical switch to Q mode, which should be less powerful than the P mode). I'll definitely try out the Linux idea, but I'll have to find another game that I can reliably make crash that runs natively on Linux or work through Proton (seems that Halo doesn't). I'll try more fiddling with voltages - one troubleshooting step I did was disabling CPU cores through BIOS and lowering CPU power usage in Windows, but it didn't fix the issue.
  14. Definitely not a cooling issue, you can see it from the logs (use GenericLogViewer for the easiest way to look at the data). I've also set the fans to 100% manually during some tests and nothing changed. If you read my post carefully, you will see that this happened with a completely different GPU of the same model, as well as a different PSU. The fact that two TUF 6800XT's have the same issue makes me think this isn't hardware. Oh, and I should mention I bought this card new from LTT through the Verified Actual Gamer program, so it's definitely a legit card.
  15. As far as I know, yes. At least the Halo menu stopped crashing at 1440p. I doubt the repair technician did any more extensive testing.
×