How to find source of stuttering in games

[Torn Mind]

Generate your own troubleshooting workflow. You're ignorant and yet you are quick to rebut, as if you already know what to do.

Knowing which games are stuttering is quite relevant because it very well could be a software issue in the game itself that needs fixing. I suspect you have no rational rationale for that question. But rather you're just full of hubris and thought there was no way software could cause the problem

Knowing the system specs is important because good god, isn't it obvious you're trying to find a problem with the hardware you have? It didn't come across your mind that one potential problem of "stuttering" could be due to drivers for the hardware or if the hardware is underspeced. Oh wait, you probably don't want help. You just want a recipe so you figure it out yourself because you already know.

He wants a "method". A recipe. A cookbook. A freaking service manual. Not specific directions. Apparently, he doesn't want help. Well, a cookbook or service manual will not teach you the basics of electricity or how use a particular utensil

Computers run programs. Everything is a program and you are experiencing issues with a program. You want to figure out what is wrong with your programs (games). You either write your own programs or use other programs people have already written to diagnose issues. You run these programs on computer hardware. That hardware varies from system to system and different hardware can cause the software to perform "incorrectly".

Fault isolation involves testing and eliminating variables. You run a game to find the issue. Maybe it is the VRAM. Fire up a tool like Afterburner to monitor VRAM usage. Maybe it is the driver. Google search to see if others have the same issue. File a freaking bug report. The "if" statement is rampant in the troubleshooting workflows. I've seen it myself in the service manuals for electronic products.

If you don't want to learn something new, then don't bother troubleshooting items. You want a methodology? The basic principles behind trouble methodology is TEST AND ISOLATE and make sure you know what the hell you are doing.

 

[Torn Mind]

And yes, you will get and "on-topic" response, just so you don't have an emotional excuse to be irrational and stuck-up like you have been through this entire thread.

General steps to troubleshooting with specific examples.
Step 1. Identify the nature of the problem.
Examples: Gas engine cannot start. TV does not turn on. Faucet leaks.

Step 2. Identify characteristics of thing or whatever causing the problem.
Examples: Briggs and Stratton gas engine. Element TV. Glacier Bay facuet.

Step 3. Research potential causes of failure.
Gas engine example: Carburetor, blown head gasket, etc.
Tv example: Bulged capacitors, failed transformer, etc for a TV.

Step 4. Test to find actual cause of failure, starting with the most basic and least invasive tests if possible.
Gas engine example: Remove and inspect spark plug. Remove and inspect carburetor diaphragm.
TV example: Use multimeter to test components on PCB. Desolder if necessary for other components.

Step 5. Procure parts needed for repair.

Step 6. Install and reassemble components for repair.

Step 7. Attempt to run the system. If it works. problem solved. If it doesn't, repeat the whole process.

 

[Bic]

Thanks for your tirade, but it's not helpful.

 

[Torn Mind]

Thanks for your tirade, but it's not helpful.

Six general steps have been provided. Your question is answered. Figure out the rest yourself. Perhaps by then, you'll realize the extent of your incompetence.

 

[Bic]

Six general steps have been provided. Your question is answered. Figure out the rest yourself. Perhaps by then, you'll realize the extent of your incompetence.

Your six steps have nothing specific to do with the question, gas engines and TV's won't help me locate the source of the hitches. Please stop replying, you're quite obnoxious.

 

[Jaydip]

There is no shortcut for the solution you are seeking, you are tracing a frame across it's entire life cycle, do you believe it's gonna be easy? I already told you about the profiling tools which provides this kind of functionality.

 

[lehtv]

Your six steps have nothing specific to do with the question, gas engines and TV's won't help me locate the source of the hitches. Please stop replying, you're quite obnoxious.

Gas engines and TV's were just examples. The same general ideas apply to all troubleshooting.

 

[VirtualLarry]

Generate your own troubleshooting workflow. You're ignorant and yet you are quick to rebut, as if you already know what to do.

Knowing which games are stuttering is quite relevant because it very well could be a software issue in the game itself that needs fixing. I suspect you have no rational rationale for that question. But rather you're just full of hubris and thought there was no way software could cause the problem

Knowing the system specs is important because good god, isn't it obvious you're trying to find a problem with the hardware you have? It didn't come across your mind that one potential problem of "stuttering" could be due to drivers for the hardware or if the hardware is underspeced. Oh wait, you probably don't want help. You just want a recipe so you figure it out yourself because you already know.

He wants a "method". A recipe. A cookbook. A freaking service manual. Not specific directions. Apparently, he doesn't want help. Well, a cookbook or service manual will not teach you the basics of electricity or how use a particular utensil

Computers run programs. Everything is a program and you are experiencing issues with a program. You want to figure out what is wrong with your programs (games). You either write your own programs or use other programs people have already written to diagnose issues. You run these programs on computer hardware. That hardware varies from system to system and different hardware can cause the software to perform "incorrectly".

Fault isolation involves testing and eliminating variables. You run a game to find the issue. Maybe it is the VRAM. Fire up a tool like Afterburner to monitor VRAM usage. Maybe it is the driver. Google search to see if others have the same issue. File a freaking bug report. The "if" statement is rampant in the troubleshooting workflows. I've seen it myself in the service manuals for electronic products.

If you don't want to learn something new, then don't bother troubleshooting items. You want a methodology? The basic principles behind trouble methodology is TEST AND ISOLATE and make sure you know what the hell you are doing.

I just wanted to comment. My HTPC is a quad-core Llano quad, OCed from 2.7 to 3.0, running Win7 64-bit. I use IE8 to listen to internet radio, through HDMI, to my LCD TV. I also have a browser tab open on these forums.

Well, I decided earlier tonight to do Windows Updates. Last time I did them on this PC, turned out to be Nov 2012. I only did the important updates, didn't update any hardware drivers, or IE9 or IE10. But it did contain updates to IE8.

Anyways, after a few reboots and updates, now my music is skipping when I scroll the screen. Badly, sometimes. Don't know what it is, but it isn't good.

Surely, a 64-bit 3.0Ghz computer with 8GB of RAM and an SSD, should be able to play internet radio in the background, and scroll the screen. (Couldn't you do that with WinAmp years ago?)

Pathetic.

But it proves, sometimes the software environment can be the cause of problems like this, stuttering, lagging, etc. Sometimes it can be hard, to nearly impossible to track down.

 

[Torn Mind]

Your six steps have nothing specific to do with the question, gas engines and TV's won't help me locate the source of the hitches. Please stop replying, you're quite obnoxious.

Do note those were clearly labelled as examples. The principles remain regardless of the specific field they are applied in. Software and/or hardware troubleshooting adheres to the same general principles.

Step 1. Games stutter
Step 2. Identify Software and Hardware
Step 3. Research Software and Hardware
Step 4. Test, or more precisely, Monitor hardware and software.
Step 5. Implement fix.
Step 6. Verify fix is working.

Of course, one can fill each step with more and more detail. Also, there is the hidden assumption that you know on some basic level on software and hardware work with each other.

 

[mfenn]

Gas engines and TV's were just examples. The same general ideas apply to all troubleshooting.

But the OP has clearly stated that he doesn't want to troubleshoot. He wants a perfectly accurate Magic 8-ball for all game performance problems.

Actually nevermind, I figured it out. He's just a pretty good troll.

 

[Essence_of_War]

Actually nevermind, I figured it out. He's just a pretty good troll.

Obvious trolls.

Sometimes not immediately obvious. :awe: