Windows 10: Debugging Tools for Windows 10 Question Solved

Page 4 of 4 FirstFirst ... 234

  1. Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       19 Apr 2015 #31

    I wouldn't know where to start with a Kernel Memory Dump, I tend to fumble my way round in a much less refined manner such as yours John. I enjoy my victories and try to learn from the ones that really make me use my grey matter, but either way the experience itself is excellent. I've learned a hell of a lot in the past ten or so months that I always took for granted was way beyond my comprehension.
      My ComputerSystem Spec


  2. Posts : 1,634
    W7 Pro x64 | W10 IP x64 | Linux Mint VM
       19 Apr 2015 #32

    Golden said: View Post
    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).
    Yeah the Gigabyte SIV (among other Gigabyte crapware) at least has the common decency to show a trace of itself in a 0x124. Always appreciated that is.
      My ComputerSystem Spec


  3. Posts : 1,648
    Microsoft Windows 10 Home
       19 Apr 2015 #33

    usasma said: View Post
    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 have got my answer, John. It feels heavenly good that your (jcgriff2 and you) stand matches with that of me. And I will proudly carry this philosophy till I see you posting something else in this topic.

    usasma said: View Post
    I prefer to state that I am an expert in helping users to fix their BSOD's.
    And I try to follow your footsteps.
      My ComputerSystem Spec


  4. Posts : 1,648
    Microsoft Windows 10 Home
       19 Apr 2015 #34

    Boozad said: View Post
    Yeah the Gigabyte SIV (among other Gigabyte crapware) at least has the common decency to show a trace of itself in a 0x124. Always appreciated that is.
    Double ditto.
      My ComputerSystem Spec

  5.    19 Apr 2015 #35

    I find the process of hunting down a cause of a BSOD rather fun. I'm not entirely sure why but I've taken more interest in BSOD analysis than with a lot of other IT subjects that I delve into. I've learned a lot about BSOD's from all of you and continue to do so.
      My ComputerSystem Spec


 
Page 4 of 4 FirstFirst ... 234

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 13:54.
Find Us