Debugger for AMD X64 dual core processor

Discussion in 'Windows Vista Performance' started by CBritton, Jun 27, 2008.

  1. CBritton

    CBritton Guest

    I have had some irritating system lockups with my computer lately and I am
    looking for ways to analyze the problem to see if I can pinpoint the
    offending application or driver. I have several mini dumps on the computer
    but unfortunately I don't have the tool to even open them. My computer uses
    an AMD Athlon dual core 64 bit processor but I'm running 32 bit Vista
    Ultimate. Following Microsoft's instructions I downloaded the x64 debugger
    file for amd processors. When I tried to install it I got a message that it
    is not for use on my system and I'm told to contact my processor vendor (or
    something to that effect).

    I find no info on the AMD site to help me with this issue.

    Has anyone else had such a problem? If so or even if you have an idea I'd
    love to hear from you.
     
    CBritton, Jun 27, 2008
    #1
    1. Advertisements

  2. CBritton

    DevilsPGD Guest

    In message <> CBritton
    With all due respect, if you're running into stumbling blocks here, I
    suspect the correct debugger won't help much anyway.

    That being said, if you're running 32-but Vista, grab the 32-bit/x86
    debugger.
     
    DevilsPGD, Jun 28, 2008
    #2
    1. Advertisements

  3. CBritton

    C. Britton Guest

    I know that my request may have led one to believe that I didn't know what I
    was doing to begin with. Actually the problem is the language on the
    Microsoft download page where it seemed clear that they recommended use of
    the 64 bit debugger for 64 bit processors even if you were debugging a 32 bit
    application. I "simply" followed their apparent recommendation.

    As for the debugger being helpful. You are probably right in your opinion
    that it will not help. I recognize that the debugger requires a fairly broad
    understanding of basic programming concepts and some knowledge of assembler
    language. While I am no longer an active programmer I do have a distant
    recollection of most of these principles. Other than to take this approach I
    can only think to totally reinstall Vista and start reloading applications
    until I stumble across the offending product (assuming that it really is an
    application that is causing the problem).

    Since this problem is totally random (may occur twice in a day or once in a
    week) it could take months to isolate the cause using the reinstall method.

    Thanks again for caring and answering intelligently.
     
    C. Britton, Jun 28, 2008
    #3
  4. The information I see is for 32 Bit Windows. Where is the 64 Bit info?

    http://www.microsoft.com/downloads/...41-c458-46f1-b24d-f60151d875a3&DisplayLang=en

    "Debug Diagnostic Tool v1.1

    Brief Description

    The Debug Diagnostic Tool (DebugDiag) is designed to assist in
    troubleshooting issues such as hangs, slow performance, memory leaks or
    fragmentation, and crashes in any Win32 user-mode process. The tool includes
    additional debugging scripts focused on Internet Information Services (IIS)
    applications, web data access components, COM+ and related Microsoft
    technologies.

    System Requirements

    Supported Operating Systems: Windows Server 2003 R2 (32-Bit x86); Windows
    Server 2003 R2 Datacenter Edition (32-Bit x86); Windows Server 2003 R2
    Enterprise Edition (32-Bit x86); Windows Server 2003 R2 Standard Edition
    (32-bit x86); Windows Server 2003, Datacenter Edition (32-bit x86); Windows
    Server 2003, Enterprise Edition (32-bit x86); Windows Server 2003, Standard
    Edition (32-bit x86); Windows Server 2003, Web Edition; Windows Vista
    Ultimate; Windows XP; Windows XP Professional Edition ; Windows XP Service
    Pack 2
    Internet Explorer"

    m
     
    miss-information, Jun 28, 2008
    #4
  5. CBritton

    DevilsPGD Guest

    In message <> C.
    And here I was thinking I came across as a bit of a dick, although
    didn't really intend to, glad it did not.

    From my own experience, if the whole OS locks solid, I'd look at
    hardware or drivers, applications should not be able to do cause such a
    thing to happen on their own.
     
    DevilsPGD, Jun 29, 2008
    #5
  6. CBritton

    C. Britton Guest

    If your reply was an attempt to embarrass you can be assured that it was a
    failure.

    Try this link for yourself:
    http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx

    Briefly it shows the following:

    Install Debugging Tools for Windows 32-bit Version
    Updated: April 29, 2008

    Debugging Tools and Symbols
    • Overview

    • Getting Started

    • What's New

    • Debugging Tools 32-bit Version

    • Debugging Tools 64-bit Versions

    • Symbol Packages

    • Resources


    References
    • Debugging Tools for Windows (MSDN)

    • Tools for Debugging Drivers (WDK)

    • KB Articles for Drivers

    • Support for Driver Development


    On This Page
    When to Use 32-bit Debugging Tools
    System Requirements
    Download the Debugging Tools for Windows

    When to Use 32-bit Debugging Tools
    The 32-bit version of Debugging Tools for Windows is the best choice, unless
    you are debugging an application on a 64-bit processor. In that case, you
    should use a 64-bit package.




    Please pay attention to the last sentence. I was debugging a 32 bit app on
    a 64 bit processor. To me the indication was and still is that it would be
    advisable to use a 64bit debug package on the basis of what is stated by
    Microsoft.

    Cecil
     
    C. Britton, Jun 29, 2008
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.