Tirant

Intel 12700k

My friend bought a prebuilt Alienware Aurora R11 that came with an EVGA manufactured 3080 that was having issues outside of the warranty window. I hooked it up and got into Windows, temps on the card looked fine, however after a few minutes the screen would flicker to black (sometimes come back for a sec) and then remain black but still outputting some kind of signal to my monitor. Windows looks to have lost the graphics device and could not reinitialize (and is completely unresponsive unless I hold the power button) gpu_crash.evtx. Once this happened, I could no longer successfully boot or even get into my BIOS (screen would just show a black signal). When I booted my PC using my integrated GPU and looked at the data for the 3080 using GPU-Z, it was detected as a 3080, but tons of info could not be read from the chip. At this time, I decided to reflash the GPU using a compatible one online and double check the drivers and everything were up-to-date. I also use a 3080 normally (albeit a much nicer ASUS one), so I was confident my system could handle the card and any issues would be with the card itself. So I took it apart to see if there was anything visually wrong with it using my eyes, and it looked fine. I don't have a microscope, so I could have missed something. I assumed at this time it might be a power/clock issue, like the clock is dropping too much, but I don't know enough about it and couldn't reliably boot to change settings and see if I could finagle it. I did take the pictures of the back of the 8-pin connectors, they are discolored but should be fine. When I removed the heat spreader covering the RAM, the thermal pads got ruined and needed to be replaced. There isn't a lot of info online about this model, so I guessed 2mm which ended up being too thick. I know this because when I reassembled it, it actually booted and worked just fine for a while playing games. I was able to view it in GPU-Z and was otherwise a perfectly functional card. The problem I had though was that the heatsink wasn't making good contact with the GPU based on the temps -- we're talking about huge fluctuations up to 70-80-90-100C, so I decided to go down to 1mm pads. When I removed the heatsink, the paste did not completely spread, so looks like it was a few hairs short of contact. After doing all this with the new pads, the card wouldn't boot again at all (same black screen issue as before). I thought, huh, all that changed was the contact with the heatsink, so I started loosing the heatsink thinking it was a mounting pressure thing. Sure enough, after basically completely removing the heatsink, it worked again. So, I'm assuming there is an issue with the mounting pressure on the GPU die. I think either the GPU die is toast, or there is an issue with some of the solder balls affixing it. I'm assuming this is because Dell cheaped out. I'm considering getting it reballed -- I'd try it myself since the card is broken anyways, but reballing a GPU die takes soldering expertise I lack. I could probably try and reflow it myself, but I wanted to look into options first since reflowing isn't as reliable as reballing. Is this a reasonable conclusion? Sorry if this was long-winded, I'm just trying to explain everything in case someone has ideas. Thank you for any help! tldr GPU only shows a black screen if there is basically any mounting pressure.

I noticed this problem a while ago with my XB270HU, and it's getting there in age. I'm just wondering what exactly is wrong with it, and if anyone has any idea how long until it fails (I assume something is failing). It hasn't gotten noticeably worse, but it can be distracting. I describe it as the bottom corners of the screen have a sort of cloudy overlay with some pixels being darker/dimmer. Sorry for the picture, it can be hard for a camera to capture exactly what I'm seeing, you might need to play with the image size to see it better. https://imgur.com/4bdmGuI

I made the changes and we'll see if the behavior changes, but... I'm looking through his event logs for the past month, and I noticed quite a few crashes (BSODs), all except the second 0x3b were when he was gaming with me. I also wanted to add that the past few nights we've been playing Diablo 2 when this has happened, so hardly a demanding game graphically and memory-wise. It looks like it could be either RAM or a driver issue (based on the errors), so I can test the RAM (I originally tested it when I put it in, but you never know). I'll also run DDU and wipe his GPU drivers, but I'm not sure if this is caused by another driver, because the dump reference some USB drivers (see screenshot below). 0xfc 0x7f 0x3b (twice) 0xd1

Buddy has been working, so I'll try today.

I'll give it a shot. I tried that with the other card and it didn't work, so I'll see if it at least helps with the replacement one.

That's what we tried a couple weeks ago. Brand new EVGA 500W, same problem

Yea, I did all of that when originally debugging it. I will have to double check it next time I go over to his house for the specific errors, but I recall seeing graphics device stopped working messages. One message I saw specifically:

Hi All! I built my buddy a PC back in Novemberish (parts list) and he's been having trouble with it since it was first built. Basically, after playing 3D-intensive games for an indeterminant amount of time (sometimes hours, sometimes a few minutes), the game will crash (hard crash with no errors, crash with errors, or BSOD). So far we have tried many games: BF1, Overwatch, GR: Wildlands, Diablo 3, etc., and the story remains the same: game runs great when all the sudden the GPU jumps to 100% usage and crashes. Other than gaming, the machine seems to be rock solid with no crashes that I am aware of, and none of his parts are OC'd, minus the factory OC on the GPU. One specific thing we tried was limiting Overwatch to ~75FPS, and this seems to have fixed that specific game, but not with others. I verified his Windows 10 x64 install using chkdisk and also troubleshooted his GPU drivers multiple times during the RMA process. I originally thought this was an issue with his GPU (all the errors pointed to "graphics card stopped working", etc), or something related to power draw since he was using a used 530ishW PSU (some off-brand thing I had lying around), but the GPU RMA instructions indicated that it was working correctly (basically just checked voltage jumps are within certain thresholds, so I did my best to verify and it looked fine). When the GPU was RMA'd, the new one was still having the same issues, so a couple weeks ago we put in a new 500W PSU and we're still seeing the same behavior. Anyways, the only obvious things I haven't done at this point are reinstall the OS and replace the CPU/MB/RAM, but those are all trickier to do, so I wanted to ask here first before diving into that hornet's nest. Maybe there's something I'm missing? Thanks for any help/suggestions! -- I had also considered that if the PSU was bad for some reason (I got it from a buddy who upgraded to a modular one, and he didn't say anything about having problems with it), that maybe it damaged the first GPU and maybe now has damaged the replacement, but I don't really know. The machine turns on fine, and runs fine, and only has issues when gaming, and the PSU load should be well within limits (6500 CPU /w 10 series GPU) I also tried using his original GPU in my PC, and had a few of the same "graphics card stopped working" errors, something that I don't experience with my own card.

Wait, you are sure that you have correct bitnesses of Android Studio and java right? They both should be the same (64-bit). Here's what I would do, make sure java is installed, preferable with a path without spaces (e.g., C:\java). Set the environment variables like how I told you earlier. Add %JAVA_HOME%\bin to your PATH. Now when you log out and back in or restart your machine, you should be able to open cmd and type java -version and get something like: java version "1.8.0_60" Java(TM) SE Runtime Environment (build 1.8.0_60-b27) Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) Once you have done this, you have verified that java is installed and working, and that JAVA_HOME is set correctly. If everything works correctly, try Android Studio again, and if it still doesn't work, you can try installing IntelliJ and using Android Studio as a plugin until you get this fixed.

How are you setting JAVA_HOME? If you open cmd and type echo %JAVA_HOME%, what shows up? Also, you may need to restart your PC (or log out and back in) to refresh env vars. Also keep in mind, paths with spaces need to be quoted This is what my env vars look like in Win 10: JAVA_HOME=C:\java\jdk8 JRE_HOME=%JAVA_HOME%\jre

Are you getting any error messages? I cannot see your screenshots. Check the error logs (google where they are). Android studio will use a different JDK than the one you added to your path.

I think android studio comes packaged with its own JDK (at least the github distro does). What's the problem you're seeing exactly? Have you already installed the android SDKs through the android SDK manager? If you're trying to set a JDK, you can add them through android studio.

50% is actually like 1.15 times your screen resolution. You want that at 42%. Open your console and type: Render.ResolutionScale 1.000000 Render.DrawScreenInfo 1 Ideally "Internal Resolution" should match screen resolution (this is resolution scale). Setting it to 1.0 in the console should make it near-perfect. I had to set mine in a user.cfg within the game folder because it was a bit off and would reset to like 0.98. Other than that, you can try increasing the priority of BF1's threads to try and get improvements in your CPU. I saw a couple videos online of people making changes to the thread priorities specifically.

50% is actually like 1.15 times your screen resolution. You want that at 42%. Open your console and type: Render.ResolutionScale 1.000000 Render.DrawScreenInfo 1 Ideally "Internal Resolution" should match screen resolution (this is resolution scale). Setting it to 1.0 in the console should make it near-perfect. I had to set mine in a user.cfg within the game folder because it was a bit off and would reset to like 0.98. Other than that, you can try increasing the priority of BF1's threads to try and get improvements in your CPU. I saw a couple videos online of people making changes to the thread priorities specifically.