Windows 10: Debugging Tools for Windows 10 Question Solved

Page 3 of 4 FirstFirst 1234 LastLast
  1. Boozad's Avatar
    Posts : 1,628
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       18 Apr 2015 #21

    I don't even know what version I have, I only have it installed on 7 at the moment. May be time for an update.
      My ComputerSystem Spec

  2.    18 Apr 2015 #22

    At the top of the debugger window to the right of the file path it has Windbg x.x.x.x and thats your versionAttachment 17056
      My ComputerSystem Spec

  3. Boozad's Avatar
    Posts : 1,628
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       18 Apr 2015 #23

    Nice one Moe. Funnily enough I never look at that top left corner...

    I've just written a Driver Verifier tutorial for W10. I think it's fully covered so if you ever need to reference it feel free. Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums
      My ComputerSystem Spec

  4.    18 Apr 2015 #24

    Really good work. Its probably like 1 point but I repped you. I want to do some tutorials on a few things but making them is so much work and unless there is a new way of doing it, takes some skill to make it not look like a hot mess.
      My ComputerSystem Spec

  5. Boozad's Avatar
    Posts : 1,628
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       18 Apr 2015 #25

    There were quite a few differences between the 7 tut and what's present in W10. I only came across the idea thanks to @Kari when we started messing around with BSODs for Kari's videos, I looked into the settings and recovery options and there was a massive difference. At least it's done and out of the way, it should last for years hopefully before any more major changes.

    Thanks for the rep Moe, it's very much appreciated mate.
      My ComputerSystem Spec

  6.    18 Apr 2015 #26

    You're welcome.

    Im going to need a link to Kari's videos or are they a work in progress?
      My ComputerSystem Spec

  7. Boozad's Avatar
    Posts : 1,628
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       18 Apr 2015 #27
      My ComputerSystem Spec

  8.    18 Apr 2015 #28

    Wow great work bookmarked that as well.
      My ComputerSystem Spec

  9.    19 Apr 2015 #29

    You can install the WinDbg tools from the Tools "beta" from here: Windows 10 Technical Preview tools

    I haven't done this on my latest Windows installation - but AFAIK it's not an upgrade. Rather it'll be another version installed into a directory on your system (so you can use different versions and can compare them). So, if you use scripts (as I do), you may have to change some paths in order to get it to work with your scripts.

    Back in the old days (Win2k/XP) there weren't any BSOD experts for everyday users. The only "experts" were either developers helping out users (cpc2004) or self-taught people (Bill Castner) - and there weren't very many of them. When I started studying BSOD's, I worked at learning how to analyze memory dumps. It was difficult, and took away from me looking for patterns that emerged in the analysis.

    In-depth analysis of memory dumps is harder than just using a few commands, and it often doesn't result in any additional information. Long ago we had problems with ASACPI.sys; Daemon Tools, internet security/antivirus/firewall tools/STOP 0x124 errors that didn't show up in the memory dumps. While working on them I determined (for my own use) that I was more able to help if I looked for patterns rather than looking for evidence in the depths of a memory dump. Also, it's harder to get a full memory dump from a user than it is to get a minidump - and back then it was even harder because of storage limits.

    So, I stuck with looking for patterns, and have refined that over the years. One pattern that I have noted is that there are 2 types of BSOD topics. Those that are solved in 2 pages or less - and those that go to 4 pages or more. I tend to think that the shorter one's are a result of simple (relatively) problems most often involving a single driver - and that the longer one's are complicated and often are the result of several drivers conflicting.

    As for the STOP 0x124 errors - jcgriff2 and I argued with developers for a long time about this. Please note that the STOP 0x124 was never accepted as solely a CPU error, rather it's an error that the CPU sees and then reports to Windows. Unfortunately, the CPU's ability to analyze errors isn't as good as Windows - so the reports are rather cryptic.

    But, back in the day (early Vista), it was the majority opinion that the STOP 0x124 error was a hardware error - and only a hardware error. For a long time we (jcgriff2 and I) insisted that the STOP 0x124 error could be caused by things other than hardware. Around the same time the ASACPI.sys driver became a problem in BSOD's. And, through this, we were able to show that drivers could cause this error - not just hardware. After a long time arguing this, it was finally accepted by the community as a whole.

    I prefer to state that I am an expert in helping users to fix their BSOD's. And that I am totally unqualified (and unable) to assist developers in fixing BSOD's with their products. The point here is that we're not involved in fixing drivers, but rather we're involved in replacing (or removing) problem drivers with versions that don't cause problems.

    EDIT: The downside to the methodology that I use is that it requires a lot of experience. I notice a trend in BSOD analysts towards more memory dump analysis, but that's sorta like doctors/veterinarians doing more tests these days. The tests are more available and can help.
      My ComputerSystem Spec

  10. Golden's Avatar
    Posts : 761
    macOS High Sierra
       19 Apr 2015 #30

    Interesting John, we have seen lots of 0x124's caused by software recently over at SF.....predominantly through running beta-Chrome browsers and Gigabyte applications (System Information Viewer and Thermal Monitoring Software).
      My ComputersSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
WinDBG - The Basics for Debugging Crash Dumps in Windows 10 WinDBG (Windows DeBuGger) is an analytic tool used for analysing and debugging Windows crash dumps, also known as BSODs (Blue Screens of Death). It is part of the Windows Developer Kit...
Source: Announcing the latest improvements for the F12 developer tools in Windows 10 | Microsoft Edge Dev Blog
Still installing on my VM - takes forever!!! Had to create a new VM as the old VM's hard drive wasn't big enough. Had to install Visual Studio 2015 CTP6 before installing the tools Also, the update to 10046 didn't load at first, so I had to...
Source: Updates for the F12 developer tools in the Windows 10 January Technical Preview - IEBlog - Site Home - MSDN Blogs
Read more... See also: Prepare your PC to get Windows Technical Preview
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 17:53.
Find Us