Timeline for How do I troubleshoot a Windows freeze or slowness?
Current License: CC BY-SA 4.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2018 at 21:49 | history | edited | Nick Craver | CC BY-SA 4.0 |
Update WPA link to current download
|
| Mar 20, 2017 at 10:17 | history | edited | CommunityBot |
replaced http://superuser.com/ with https://superuser.com/
|
|
| Jul 3, 2013 at 12:13 | comment | added | Tamara Wijsman |
@CamJackson: superuser.com/a/224499/9666 then run it through WinDBG and follow msdn.microsoft.com/en-us/library/windows/hardware/… (make sure you set the symbols first and use the !analyze -v command for additional details)
|
|
| Jul 3, 2013 at 1:20 | comment | added | Cam Jackson | What about if the system hangs and doesn't come back? My computer is hanging and either stays like that indefinitely, or eventually restarts itself. | |
| Dec 30, 2012 at 23:12 | comment | added | Tamara Wijsman | The link to WPAT above has not expired, updated to new link. Since the MSI's are signed, they have not been tampered with; other ways to obtain them is through the Windows ADK or Windows SDK. | |
| Dec 30, 2012 at 23:11 | history | edited | Tamara Wijsman | CC BY-SA 3.0 |
added 14 characters in body
|
| Dec 30, 2012 at 22:56 | comment | added | Steve | The link to WPAT above has expired. Go here instead: blogs.msdn.com/b/jimmymay/archive/2009/11/24/… | |
| Sep 18, 2012 at 17:46 | history | made wiki | Post Made Community Wiki by slhck | ||
| Sep 18, 2012 at 17:32 | history | post merged (destination) | |||
| Jan 5, 2012 at 11:42 | comment | added | Tamara Wijsman | However, feel free to ask a question on the actual use of XPerf as well as a community wiki that summarizes what to do when specific cases arise. It might help as a start for beginners that don't have a clue what they are doing. However, I currently don't have the time and willingness to do this here and now.... Excuse me for the length of my comments, but I thought a single comment is insufficient to get the idea. | |
| Jan 5, 2012 at 11:40 | comment | added | Tamara Wijsman | Also, it depends from case from case what you have to look for. One time, I'm walking down the stack tree of a process to find out that a firewall is messing up my Visual Studio debugger. Another time, I just look at the DPC calls for someone that send me a dump through a mail, another time I look for the biggest I/O consumer for someone on the SU chat. You need an understanding to actually know what you need to look for, if I need to cover most of these cases I would have the longest post on SU. Although most of that can otherwise be reached by simply researching and learning. | |
| Jan 5, 2012 at 11:34 | history | edited | Tamara Wijsman | CC BY-SA 3.0 |
added 139 characters in body
|
| Jan 5, 2012 at 11:30 | comment | added | Tamara Wijsman | But in general, you are on your own. Writing a complete guide on how to use XPerf would detriment away from the intention of this post, which is to get the actual problem resolved. Please note that a compressed Xperf trace is very small, so it does scale very well compared to crash dumps. And oh well, those would even be harder to explain how to debug them (it requires a good understanding of the internals of a computer). Google is your friend, if you read documentation you can even access it from a Memory window. | |
| Jan 5, 2012 at 11:24 | comment | added | Tamara Wijsman | @nhinkle: This outlines the program out in a bit of detail, however it boils down to just opening the trace and looking around. If a person isn't smart enough of actually doing some self study on the things seen there, he should probably not be debugging traces. Debugging is really something you should use Google extensively for. When a program crashed, I can see the data that was on the stack. Can you? Of course one can ask how a specific thing exactly works or what a specific things means. | |
| Jan 5, 2012 at 6:24 | comment | added | nhinkle | This doesn't scale very well, having people just upload an xperf trace. Is there any way you could edit this to include some info on how people can use that information to debug the system themselves? | |
| Sep 17, 2011 at 20:30 | history | edited | Tamara Wijsman | CC BY-SA 3.0 |
added 1 characters in body
|
| Oct 30, 2010 at 23:12 | history | edited | Tamara Wijsman | CC BY-SA 2.5 |
deleted 152 characters in body; added 4 characters in body; added 4 characters in body
|
| Oct 30, 2010 at 23:01 | history | answered | Tamara Wijsman | CC BY-SA 2.5 |