How to fix "Failed to create graphics device.Exiting" error? - graphics

Win7(64), nvdia 960.
All of a sudden 90% of my games stopped working. My oldest game (GOC 1998) works using dxwnd. My newest game (For Honor-online 2017) still works, but Total War, Tropico4 and Americas Army doesnt detect my graphics card anymore. Ive reinstalled drivers,games,contacted MSFT and Nvidia support but keep getting graphics errors. I think a recent MSFt update fugged something.
Has anyone else had this error?
Tried to update my BIOS step by step but get the "bad command" error. That's another topic i may start.

Use DDU http://www.guru3d.com/files-details/display-driver-uninstaller-download.html
Install latest Nvidia drivers
Make sure you have latest chipset drivers for your motherboard installed.
If all else fails, open cmd as admin and run sfc /scannow

Fixed it by doing what I was trying to avoid, reinstalled the entire OS.
It appeared to be corrupt or missing windows drivers, possibly msft vc 2008 x64,x86 version(9.0.30729.6161) and msft vc 2010 x64,x86 version(10.0.40219) along with a ton of other drivers during reinstall. It took about 3+ hours.

Related

Can't Deploy React Native to iPhone from Xcode 13 Beta 2 running on Virtual Machine running Big Sur 11.4

I have a Mac running Catalina with Xcode 12. This month, my iPhone upgraded to iOS 14.6, which requires Xcode 13. Xcode 13 requires Big Sur. Unfortunately, I don't have the money right now to upgrade my Mac to one with the hardware the Big Sur requires.
I installed VMWare Fusion 12 on this Mac and created a Virtual Machine running MacOS Big Sur 11.4. Then I installed Xcode 13 Beta 2, installed its dependencies, added the provisioning profile required to deploy, and selected my iPhone in Xcode as the target. When I build and attempt to deploy to the device, there are no errors, though it hangs/stalls right near the end of the process, around the time that Xcode says: "Preparing Editor Functionality". MetroBundler starts correctly and I see no issues in Terminal, Console, or Xcode. It just stops compiling/deploying.
I'm not super savvy when it comes to Xcode or the deployment process. I was hoping someone might be able to give me some tips as to how to figure out what's preventing the app from deploying to the device. Does Xcode have logs somewhere (other than Device Logs) that might help inform what's hanging?
Thank you for your time and I'm happy to provide screenshots or further information upon your suggestions.

Multiple Android Studio lockups with Apple M1 chip

I have the MacBook Pro with the new M1 chip with 8GB ram running Big Sur V11.1 and Android Studio 4.1.2. Over the course of a couple hours of work in Android Studio I can get 4 or so spinning beachballs of death where I need to do a force quit and occasionally Android Studio blinks out of existence all together.
I am not using the emulator. The lockups always seem to occur while I am in the middle of editing code.
I have run the Mac in safe mode and that might have slowed down the frequency of lockups, but not eliminate them. (I am not keeping count.)
I did do a data migration from my old Mac (a 10yr old Intel machine that never had this problem, just got to be too slow). Don't know if that has anything to do with the problem.
The only good aspect is that the machine is fast so I have been submitting a crash report every time!
Just wondering if anyone has any words of wisdom to fix this.
Even with increased memory I faced similar issue. However managed to solve it by changing JDK used by Android Studio to M1 compatible JDK. I used Azul JDK.
Make sure to set both JAVA_HOME & STUDIO_JDK variables. Also change the project sdk to M1 compatible JDK.
I use Azul 15.0.2+7 ARM 64-bit macOS version.
Update 23 May 2021 ******
I've switched to latest intelliJ, which has M1 support and installed all android plugins. So far my experience has been exceptional. Debugging can get slow at times, but rest is just fine.
I had the same problem and after a little search i could fix it very easily...
The problem of crashing comes because is not allocated enough memory to the “JVM”.
Go to: Finder->Applications.
Right click on Android Studio. Select "Show package contents"
Go to : Contents->bin.
Right click on "studio.vmoptions". Select "open with"-> "textEdit".
Copy the Text somewhere for backup, just in case you mess it up.
Just change the numbers as shown on the 3 line below. Leave everything else as it is.
-Xmx6154m
-XX:MaxPermSize=1024m
-XX:ReservedCodeCacheSize=200m
That should fix the crashes.
I was facing the same issue, the way I solved this is I just deleted Android Studio and installed IntelliJ IDEA ultimate.
Jetbrains have an IntelliJ IDEA version special for M1 processor and it works like a charm on my MacBook Air (8gb RAM). The only downside is you can only use IntelliJ IDEA ultimate for free if you're a student, if you're not you'll only get one month of free trial.

macOS Big Sur - Xcode 12.2/12.4 freezing when run any project or .swift file

Problem started after update macOS to Big Sur
First of all, I can't update Xcode via Appstore, so I've downloaded from official site 12.4, and it can't open any project or swift file.
What I've tried:
-remove all devices
-change wifi to ethernet
-remove Derived Data and reboot
I've downloaded Xcode 12.2(which was previos for me and worked fine) and install it, still no luck. It just spin and spin, and finally not responding. I am really stuck with this, please help me solve this.
ok, now I've solved it, so maybe this will help anyone -
based on #dereknahman comment:
The issue for me wound up being to do with iCloud. I turned it off and the problem went away. It's a pain, and I haven't found a way to use both at once yet, but it helped!
I've moved project from iCloud and all works fine (Big Sur + Xcode 12.4).
For me I deleted all devices connected by network.
then the Xcode stop freezing
shift + Command + 2
then delete all connected devices
then try
Yes, it became a continuous pain in 12.3 and 12.4
And thanks God, seems Xcode 12.5 beta fixed this issue

Fingerprint sensor not working after updating to windows 10 1903. (Dell G3 3579)

Goodix Fingerprint sensor not working after windows 10 1903 update on my Dell G3 3579.
It worked while installing windows 10 1903 via iso (which failed to update otherwise), windows hello was all good during setup but after first boot then it just stopped working & driver shows error code 31 on device manager.
I tried updating everything & also tried reinstalling Goodix fingerprint driver but that didn't work either. The fingerprint worked fine on the previous 1809 update of windows 10.
..
images attached showing errors.
Just wanted to update it got fixed, without re-intalling windows.
I did a couple of things with a guy from nearest dell partner who provided me free technical support at their center, He guided me a little and I did a few things on my own. I don't know what fixed it but I'll go on chronologically.
First I downloaded a utility named UsbSafelyRemove and using this I stopped the power to the fingerprint sensor virtually without having to disconnect it, this removed it from devicemanager by preventing it from getting detected for current session. Then I uninstalled the sensor driver software and it was no longer detected aswell. Then I downgraded the bios using Dells Bios Tool, Meanwhile Microsoft or maybe Dell launched an un-logged/unscheduled automatic update and perhaps a possible patch for windows, I don't know if they did it or if it was windows on its own because it wasn't logged. I then restarted the computer, the sensor was detected and appropriate drivers were automatically installed, didn't check for error at this time. Then my antivirus software also found a simple PUP.Optional.OpenCandy malware, which shouldn't likely have any effect. I enabled Microphone for a skype call and just out of the blue the sensor error code 31 which I was checking for frequently, just disappeared. I have now upgraded my bios and the sensor still appears to work. I believe the miracle was due to the windows update most probably, just for reference I was on windows 10v.1909 before and even now, the update was minor a fix perhaps.
I still don't know what caused the error 31, & which particular update fixed the conflict, was it dell support software which was continuously on or windows, but I'm pretty sure its fixed.
Thanks to all those who helped for your time & support.

Screen Flicker after installing HyperV on Windows 10 Dell Laptop

I've got a new Dell Inspiron 17 (7779) laptop with Windows 10 x64 (1703) which was working fine right up until the point where HyperV was installed. Now the host screen flickers like mad even with no Guest VM's created.
Dell are being particularly unhelpful, so I was wondering is anyone else was having the same issue.
Basically is anyone running Hyper V on a dell Inspiron successfully.
I guess it could also be a clash with the display drivers (Intel HD Graphics 620, driver ver 21.20.16.4627)
OK, I think I've resolved this with the latest Intel graphics drivers 21.20.16.4678, however there were a few issues...
So the Intel drivers (21.20.16.4627) installed on the machine were the ones installed via the Dell Driver Detect tool, if you just download the latest drivers from intel and install them, it wont update them....I think there is some versioning issue with the dell drivers, as it seems to think the existing drivers are newer than the ones your trying to install....
In order to make it accept the new drivers you need to uninstall the existing display driver AND delete the install files. Then after a re-boot the display drivers used should be the default Microsoft ones, you can then upgrade the driver (again via computer manager) selecting the location of the downloaded and unzipped intel drivers.
I'd like to be able to thank Dell for there help, but they failed miserably to provide any.
One last thing...
For some reason windows automatically 'upgrade' the display drivers and re-installed a old version (21.20.16.4627) replacing the latest drivers I installed. I then had to rollback the automatic update, which fixed the issue again. Hopefully I won't have to keep doing this...
It looks like someone has made a mess of versioning some of these updates, its difficult to tell whether its an issue with the Intel drivers or the Dell wrapping of them as part of the driver detect tool, but there's definitely an issue.

Resources