when i was playing a game called Sea of thieves an error popped up saying "video drive crashed and was reset. make sure all of your video drivers are up to date. exiting...". at first i didnt think much of it and loaded back on to the game but then it kept happening again and again. at first it was once every week and then once every day and now it is happening every hour or so. keep in mind my PC dosent have the best specs and it is an all in one built in with the moniter so i dont have the best graphics in game. at first i tried updating my video driver but soon found out that it was already up to date. i next went on to the official Sea of thieves forums and support thinking that it was something to do with the game itself. i had a look on the forums and found people with similar problems but no answers. i then went on to customer support and when i clicked on " video driver " it brought me to the microsoft support page indicating that it wasnt the game but microsoft and the computer itself. i have heard suggestions of uninstalling and reinstalling the driver but i only have one and no back up driver so i am worried about what might happen to my PC. i have also heard about doing a factory reset yet i do not want to attemt it just yet as it is a last resort. i am sorry if these sound like silly questions or descriptions just note i am kind of new to the whole PC thing. Thank you for taking the time to read this and please help me in any way that you can.
Sounds like your graphics card may be overheating? Monitor the temps while playing.
Depending on the age of the card, it may be that you need to blow out the dust or replace the thermal compound.
Related
So i had been making video tutorials for my friends on how to program. On my old computer i had been all ways running simple screen recorder and it recorded fine. But recently i got a new computer. And so when i got a fresh install of arch linux on the box. I set up the environment with every thing i needed to make another video. When i downloaded simple screen recorder using yaourt, and started recording. I had recorded up to a two hour session with out knowing that it was glitching out. When i look at my computer i do not see the same issue as when the final product is done rendering. I think it might be a rendering error or i do not have the right codecs. After a hour or two searching on the web i could find no forum posts on the codec. I took in multiple things that could be wrong with it fps was my first choice but when i had recorded with 25 and even 50 fps it was still glitching out. The next idea i had was that i had the wrong codec H.264. But with searching i could find no solution to that one. Then i thought that i might have been encoding at to high of a speed (23). But still that proved me wrong. so now i am confused with how to get my answer.
Settings Screen shot:
Video Link:
https://www.youtube.com/watch?v=zfyIZiJCDa4
The glitches are often relate to the rendering backend of the window compositor you are using.
Solution 1 - Change the rendering backend of the window compositor
#thouliha reported having issues with compton. In my case I had glitches with openGL (2.0 & 3.1) and resolved the issue by switching to XRender for recording.
On KDE you easily change the rendering backend of the window compositor in the settings .
Solution 2 - Change the Tearing Prevention method
To keep using OpenGL, for example for better performance, you can also tweak the tearing prevention method.
In my case switching from Automatic to Never allowed me to record video with OpenGL compositor without glitches.
Solution 3 - Intel iGPU specific issues
Intel iGPU (Intel graphics) has some rendering issues with some CPUs.
You can check the Troubleshooting section of ArchLinux wiki to check those.
Example of features creating tearing or flickering related issues:
SNA
VSYNC
Panel Self Refresh (PSR)
Check also /etc/X11/xorg.conf.d/20-intel.conf if your system has put tweaks in here.
I'm not exactly sure what you mean by glitching out, especially since the video is down now, but I've found that the video is choppy when using compton, so I had to turn that off.
It's already a long story... I bought my phone sometime in 2013, and found that it's GPS doesn't work, just after the warranty expired. I tired everything to get it function properly without any success, and finally gave up. Up until now I could live without it, but right now I'm really in need of this functionality, and only because of that I'd have to buy a new smartphone now if it can't be fixed.
Here's the issue: I turn on GPS positioning in the OS, and open up some GPS tester application, and this is what happens: After a couple of seconds, it finds the first satellite, and in 1-2 minutes I already have 6-7 or even 8 of them. - So it seems the hardware is OK, the receiver works. But after that, I cannot get a GPS fix. I can wait 10-20-30 minutes, or even waited for an hour...Nothing happens. No position fix, GPS useless. I've tried 10+ GPS apps, the result is always the same. They see the satellites, but never establish a position fix.
What I've done so far: I read on xda-developers that this phone for some reason doesn't have a gps.conf file in system/etc which could cause the problem, so I downloaded one for my country, rooted my phone and pasted it to that folder. Nothing changed. I'm out of ideas, and there's nothing more I could find on the internet. Any ideas here? Or should I get a new phone? It's really annoying because it seems it's not a hardware issue, so it should be able to be fixed somehow...
Btw that's the content of my gps.conf file in system/etc for Austria, the country I live in:
NTP_SERVER=at.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/
xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/
xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/
xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
(I have no idea what it's for.)
Unassisted GPS in a GPS module which has never been turned on, or has to find a new position solution, can actually 2-4 hours at worse. Adding to this, a single processor Android smart phone such as yours likely throttles severely, and is not likely to schedule much resource for non-essential routines.
Be sure to turn on 'Google Location Services' to enable assisted GPS for a faster position solution. If any factory setting has a toggle for location- assistance, make sure it is enabled. Be sure to move away from buildings so the sensors view of the sky is widest.
I've been messing around with programming the old Kinect for a while, and something I've noticed is that whenever I start a program that uses the Kinect sensor, the Kinect will stop sending inputs after 1:30 minutes, no matter what program it is. For example, my game that I made will still have enemies moving around, but the player's rendered skeleton from the Kinect just freezes. I can't find anything about this anywhere online, so is it just mine? Is there a way to fix this?
This is a bug somewhere between the Microsoft SDK and using a Kinect for XBOX on Windows (didn't try the Kinect for Windows).
The Kinect stream freezes after 1 minute 28 seconds. In the Unity editor, you'll also notice once you reach this freeze, you need to quit and restart Unity to be able to play again. If not, you'll get messages like "Device not genuine", etc.
The only way to solve it that I found is to re-initialize whatever Kinect Manager you are using. For instance, Destroy()ing the gameObject holding the manager and re-Instantiate()ting it.
This will effectively halt your Kinect stream (and any gesture/joint reading) for about 4 seconds and then it will work again, so this is something the user will definitely notice.
Now, this may not work for most games, but if you're working on a casual game and you can keep it under 1:28 or you're able to show the user some sort of screen while you restart the Kinect manager every 1:20, you'll be safe.
If you never exceed the 1:28, you'll be able to stop and play in the Unity editor as many times as you want, and keep it running as many times as you want.
Now, this may not be an actual "answer", but may work for someone.
Let me know if you need any help to make this work. I hope this helps someone.
You can test the Kinect with built in programs in this link.programs to check and see if it works smoothly. If not may be something wrong with your program.
I have the same issue. At first I thought it was something related to Unity3d. But I tested with other programas and it's still happening.
Talking to the guy who developed the plugin he said: " two users complained that Kinect tracking stops after a while"
https://www.assetstore.unity3d.com/en/#!/content/7747
Also, I sent him an email and he told me that more and more people are getting this issue.
My friend is currently making a game in gamemaker, but whenever I test it out for him my computer seems to just completely lock up. My PC that I am testing on is no way underpowered, it has a 2500k, Radeon 6950 and 8GB RAM. My RAM, GPU and CPU usage is barely touched during the freeze. If I am playing music at the time of the freeze the speakers just buzz. Whenever is occurs a full system reboot is always required, nothing at all responds. The image of the game stays on the screen, mouse, keyboard and restart button don't respond. This question may be better suited for the Gamemaker forums, but it could be an issue with my computer. I am unsure. I can play MW2 and Crysis for hours without it crashing, so it is either a software problem or something weird. All of my temps are normal. Others have suggested checking while loops, but wouldn't an infinite loop cause the CPU usage to rise?
In any of your loops that have a potential of running infinitely, put io_handle(); (I think thats the command) This command somehow keeps windows from thinking a program has frozen. If that isn't the case... then try to play the music through an extension like fMod or another one. Furthermore, try it on another computer is it just your computer? Your computer doesn't sound underpowered at all... but what about your operating system? If you're using xp it may not support the Directx that GM requires. I believe that its very easy to make gm games very directx intensive, so check that out. Good luck! I love Game Maker!
It's most likely an infinite loop in your code. Try stripping away your code, compile, and test if your computer freezes again. Then build back up to where you started from.
This kind of issue is probably due to something internally in game maker, OR it could be an issue with a listener or script you may have bound to a sprite or object. Begin removing things, one by one, until you find the culprit.
Try to strip out pieces of code part by part and isolate the function / code that is causing the freeze. Then come back here and tell us the status.
I've kind of seen this before on another Gamemaker game. Do you have any infinite loops or shaders in your game? The last game that had this problem was caused by a bad shader.
I have a VB.NET application that crashes on a client's computer with a BSOD error... KERNEL_DATA_INPAGE_ERROR.
This error occurs at a point where my program does two things:
Locks the computer
Plays a sound in BackgroundLoop mode
For locking the work station, I am just using this:
<DllImport("user32")> _
Public Shared Sub LockWorkStation()
End Sub
For playing the sound, I am doing this:
My.Computer.Audio.Play(My.Resources.ResourceManager.GetStream("somesound"), AudioPlayMode.BackgroundLoop)
Now, this sound loops until the user logs back in. My software detects the session state switch and stops playing the sound. Sometimes when I log back in, the sound card plays garbage data for a split second, instead of the rest of the audio buffer. I get the impression that this has something to do with session switching.
Could my client be having an issue where there is memory corruption occurring at the point of locking the computer?
I apologize for the vagueness of this post... I am not sure where to begin as I cannot reproduce the problem myself.
Edit: If the sound is left to play on its own, even without locking the computer, eventually the computer will lock up and then bluescreen. Playing the sound while locking at the same causes it to happen sooner.
Edit #2: So I've seen it fail now. The sound loop starts playing correctly but quickly switches to looping of garbage data. It's as if it is just reading a random location in memory and looping that. Very strange behavior!
Solved!: It was hardware all along afterall. Apparently this particular model of laptop has a problem where the speaker is installed right on top of the hard drive. When playing sounds loudly, it creates all sorts of problems.
A blue screen is almost certainly related to defective hardware or drivers. Softwarewise, there's really not much you can do about this apart from putting together a workaround.
You can perform a memory dump and try to determine what specifically went wrong, or with some clever debugging see where it bombs out in order to try to avoid it.
Otherwise, you're probably talking about doing some maintenance work on the machine in question.