I have dual booted windows 7 and ubuntu 14.04 on my PC.
I have a recurring problem with windows.
The screen frequently becomes blank for a few seconds, showing an error message in a popup menu:
"Display driver stopped responding and has recovered. Display driver NVIDIA windows kernel mode driver version 266.58 stopped responding and has successfully recovered."
Here are my computer specifications:
Intel core i5 processor,
4gb ram,
Nvidia GeForce 210 graphics card.
I updated the drivers on my computer.
I also formatted my PC, but the problem still persists.
Now the problem is worse and windows shuts down within a few minutes of starting.
Today, Ubuntu also started randomly freezing, a symptom which had not presented itself until now.
As Astor139 said:
Honestly, this particular question doesn't fit stack overflow, since it isn't strictly programming related. (As far as I can tell, you have a hardware issue.) Since it persists across two different OS, with very different arch, I would say you need a new gpu. A Nvidia GT 730 is under $50 USD and would be a suitable replacement/upgrade for your 200.
Posted as his comment is really a suitable answer.
Related
I installed the latest version of the HoloLens 2 Emulator (10.0.20348.1501) on my Windows 10 Pro machine. I have 32GB of RAM, 11th Gen Intel 8 Core CPU, Nvidia 3080 (mobile) graphics card.
Initially I thought that the HoloLens emulator was super slow (an input such as trying to move the pointer can take 10, 20, 30 seconds to show up and sometimes doesn't even show up).
But upon testing some more, I've realized that my inputs are going through immediately (as I can tell from the sound feedback), it's just the visual feedback which is not updating. This testing is just inside the OS (without trying to launch an app I developed).
Any ideas what could be going on? In the performance monitoring tool, everything looks fine.
In the end, the only way to fix it, was to disable graphics switching in the BIOS, and set to Discrete only - despite the fact that the Nvidia GPU Activity shows that the GPU turns on when I launch the emulator.
If the emulator takes 10 seconds to update the graphic, there should be configurations issues. Based on my test, though I cannot say it works fluently in my PC, the HoloLens 2 emulator runs at around 15 fps. There is delay but should be work fine for testing. (I am running it with Nvidia 1080 (mobile), with a much older CPU than yours.)
Please check the document on Using the HoloLens Emulator - Mixed Reality | Microsoft Docs and make sure you have configured your computer properly.
In BIOS
Intel VT -> enabled
Intel VT-d -> disabled
Hardware-based Data Execution Prevention (DEP) (or any Intel data protection related feature, display name could be varied) -> disabled
In Windows
After BIOS configuration is done, completely shut down your PC, then boot. (Directly reboot may not apply changes).
Run dxdiag to check:
DirectX 11.0 or later (12.0 in my PC)
WDDM 2.5 graphics driver or later (3.0 in my PC)
Hyper-V Checking
Enable it if it is not. Reboot is required.
If it is already enabled. Disable it -> reboot the PC -> enable it again -> reboot
Others
For the laptop, make sure the power supply is plug-in and it is not in power-save mode. Check the GPU payload (around 36% in Nvidia 1080 mobile)
Then you may run the emulator again to see if this issue still exists.
I recently installed the Linux Pop! _OS 20.04 LTS distribution to develop in flutter. Everything works very well, except the AVD emulator, which is extremely slow. What could it be?
I have a 16gb dell of ram, i5 8th generation and 256 of ssd.
im on POP OS 21.10 (Intel® Pentium(R) Gold G5420 CPU # 3.80GHz × 4, 8 single channel ram ), first i need to applied this following instruction https://developer.android.com/studio/run/emulator-acceleration?utm_source=android-studio#vm-linux , for my use case(flutter) i increased the ram to 3gb and VM heap to 512mb , chose Hardware GLES 2.0 on graphics option, then it runs smoothly, if u are using genymotion u can increase the VRAM on virtual box.enter image description here
In case anyone else runs into this, I had to change quick boot to cold boot, as mentioned in this redit post. No idea why quick boot doesn't work, and my system was not spiking in any way but the whole OS was completely unusable until I killed the emulator. I'm on Pop! OS 22.04.
What I've done in the past is simply Dual boot, but I would like to not have to reboot my computer in order to switch OS's. Specifically, what I'd like is:
Computer would mainly run Linux,
When I want to play a Windows only game I can switch over to Windows, for that period of time then return to Linux.
Both Linux and Windows need to run up to native in speed.
I'm looking for suggestions in setting this up.
I've looked into Xen, however, I hear that Xen doesn't support 3D graphics? is this accurate. I've also looked into WineD3D and VMGL. However, Wine won't play every game, so I'd still need the Windows VM, and VMGL doesn't seem to work universally either.
I'm running two different machines that I plan to put this setup on:
Laptop:
Intel i7 4720HQ
16GB Ram
NVIDIA GeForce GTX 965M
Desktop:
AMD FX-8350
16GB Ram
EVGA GeForce GTX 960
I just joined and the "Tour" said, don't ask questions that could lead to a discussion than an answer. Anyway, If gaming is your primary goal, have windows as primary boot & dive into linux as VM. Otherwise you need to find a hyper-visor that provides 3D services or pass-through to your actual GPU.
There is a discussion here
Android studio's emulator takes like ages to start and also crashes sometimes and at times does not show output, is very very slow.
OS X Yosemite
version 10.10.1
MacBook Pro (15-inc, late 2008)
Processor 2.4 GHz Intel core 2 Duo
Memory 8 GB 1333 MHz DDR3
Startup Disk Untitled
Graphics NVIDIA GeForce 9600M GT 256MB
If i remember correcly your MacBook do not support Hardware Accelerated Execution Manager becouse the cpu is quite old :-( (mine is too) so the default android emulator will be so so slow and there is no way to fix it
Yes you can tweek some parameters and maybe gain a second but it would be very marginal gain.
I use Genymotion is realy fast and run well on ald machines, give it a try. Is commercial product. It han the big disadvantage that there is no images with google play services.
Otherwise there is a way to run android images on "Oracle VM VirtualBox" but this way is not so easy, is hard to find a good android image and setup the envirnoment. install Android in VirtualBox
ps. if you haven't done this already upgrade hd to an ssd , it helps a lot
I've noticed a big performance hit when I run my CUDA application in Windows 7 (versus Linux). I think I may know where the slowdown occurs: For whatever reason, the Windows Nvidia driver (version 331.65) does not immediately dispatch a CUDA kernel when invoked via the runtime API.
To illustrate the problem I profiled the mergeSort application (from the examples that ship with CUDA 5.5).
Consider first the kernel launch time when running in Linux:
Next, consider the launch time when running in Windows:
This post suggests the problem might have something to do with the windows driver batching the kernel launches. Is there anyway I can disable this batching?
I am running with a GTX 690 GPU, Windows 7, and version 331.65 of the Nvidia driver.
There is a fair amount of overhead in sending GPU hardware commands through the WDDM stack.
As you've discovered, this means that under WDDM (only) GPU commands can get "batched" to amortize this overhead. The batching process may (probably will) introduce some latency, which can be variable, depending on what else is going on.
The best solution under windows is to switch the operating mode of the GPU from WDDM to TCC, which can be done via the nvidia-smi command, but it is only supported on Tesla GPUs and certain members of the Quadro family of GPUs -- i.e. not GeForce. (It also has the side effect of preventing the device from being used as a windows accelerated display adapter, which might be relevant for a Quadro device or a few specific older Fermi Tesla GPUs.)
AFAIK there is no officially documented method to circumvent or affect the WDDM batching process in the driver, but unofficially I've heard , according to Greg#NV in this link the command to issue after the cuda kernel call is cudaEventQuery(0); which may/should cause the WDDM batch queue to "flush" to the GPU.
As Greg points out, extensive use of this mechanism will wipe out the amortization benefit, and may do more harm than good.
EDIT: moving forward to 2016, a newer recommendation for a "low-impact" flush of the WDDM command queue would be cudaStreamQuery(stream);
EDIT2: Using recent drivers on windows, you should be able to place Titan family GPUs in TCC mode, assuming you have some other GPU set up for primary display. The nvidia-smi tool will allow you to switch modes (using nvidia-smi --help for more info).
Additional info about the TCC driver model can be found in the windows install guide, including that it may reduce the latency of kernel launches.
The statement about TCC support is a general one. Not all Quadro GPUs are supported. The final determinant of support for TCC (or not) on a particular GPU is the nvidia-smi tool. Nothing here should be construed as a guarantee of support for TCC on your particular GPU.
Even it's been almost 3 years since the issue has been active, I still consider it necesssary to provide my findings.
I've been in the same situation: the same cuda programme elapsed for 5ms in Ubuntu cuda 8.0 while over 30ms in Windows 10 cuda 10.1. Both with GTX 1080Ti.
However, in Windows when I changed the compiler from VS Studio to cmd's nvcc compiler suddenly the programme was boosted to the same speed as the Linux one.
This suggests that maybe the problem comes from Visual Studio.