1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Help with Dump Files

Discussion in 'Windows XP' started by Squintz, 2004/12/03.

Thread Status:
Not open for further replies.
  1. 2004/12/03
    Squintz

    Squintz Inactive Thread Starter

    Joined:
    2004/12/03
    Messages:
    5
    Likes Received:
    0
    I know there are some sites around describing how do analyze dump files to figure out why my PC keeps crashing so maybe you guys could give me a few links to those for starters. If anyone wants to be a pal and help me one on one that would be much apreciated. I have never even knew dump files existed until today so i don't have a clue what to do with them.

    I have figured out for myself that i can use windows support tools to analyze the dump files but again i dont have a clue how to use the tools to quickly and simply identify my problem

    Here is my problem... My PC has been crashing atleast once a night. It usually happens while im not looking but there have been a few times it has crashed and i had been a witness to the crash. When it does crash the blue screen comes up and starts a dump. Then my PC automatically reboots and ask me if i want to send the error to Microsoft. I click yes to send the info but im not so sure the info ever reaches them. Imediatley after i send it and it says its done i get a dialog box with an URL address saying it couldnt contact the site.

    I viewed the data that was to be sent to microsoft and found two files... A XML file and a dump file. When i tried to view the dump file it was all garbage which led me to think there was a tool that i needed to use to view the file. Thats when i found windows support tools.

    Now... I have several mini dump files from the last few crashes and im sure that its going to crash again tonight since its done it every night since the middle of november. So i can change the settings to make a larger dump file if i need to but im not sure where or what to set the setting to. Sure i could look it up via google but i wouldnt feel confident that i knew what i was doing.

    Can you guys please help me. Tell me what files you need or what commands i need to perform to provide you all with the data you need to solve my problem.
     
  2. 2004/12/03
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Arie,
    #2

  3. to hide this advert.

  4. 2004/12/03
    Squintz

    Squintz Inactive Thread Starter

    Joined:
    2004/12/03
    Messages:
    5
    Likes Received:
    0
    Thanx for the warm welcome i have a feeling you will be seeing me here alot more often now.

    Here is what my latest dump file produced when i followed JoeHobarts instructions

     
  5. 2004/12/03
    Squintz

    Squintz Inactive Thread Starter

    Joined:
    2004/12/03
    Messages:
    5
    Likes Received:
    0
    Looks like its caused by USBPORT.SYS Now how do i go about fixing it? It would make since that that is the problem since i have also been having one of my USB devices flake out on me everynow and then. I ended up buying a PCI USB 2.0 Externder card but this started happening nearly a few months after i have had that card installed. Which leads me to believe that maybe its not that card but the onboard USB ports from my ASUS p4p800-E motherboard. Since its probably the USBPORT.SYS thats currupt or something how do i know where to get a good copy of that file and do i need to do anything special while replacing that file.

    Is there only one USBPORT.SYS or is there two because i have two usb controllers. I can check for myself right now because im at work and the problem is at home :)
     
  6. 2004/12/03
    Squintz

    Squintz Inactive Thread Starter

    Joined:
    2004/12/03
    Messages:
    5
    Likes Received:
    0
    This next dmp file was from 11/19/04 and the previous was from 12/03/04


     
  7. 2004/12/03
    Squintz

    Squintz Inactive Thread Starter

    Joined:
    2004/12/03
    Messages:
    5
    Likes Received:
    0
    Dump2 says thats its something related to FTD2XX.sys. That driver is a USB device driver. I think at the time this dump accured is around the same time that i was having problems with that device and switched the device over to a PCI USB Card. I have since only have minor problems with the USB device but it is currently working fine.

    The USB device that i am talking about is a RF Z-Wave Transmitter that i use to control the lights and other apliances in my home via a software application called HomeSeer. I think the recent problems with this device were due to the HomeSeer software and not the driver itself.
     
  8. 2004/12/03
    JoeHobart

    JoeHobart Inactive Alumni

    Joined:
    2004/05/19
    Messages:
    919
    Likes Received:
    1
    Both of these dumps are caused by pool corruption. This is a phenomenon where a kernel mode driver is using someone elses memory.

    You need to run your memory inside a "sandbox" so that you can catch someone with thier hand in the cookie jar.

    1) Start->Run-->Verifier
    2) 'Create custom settings'
    3) Select individual settings from a full list
    4) check the 'Special Pool' checkbox

    Now, its get sketchy.. We need to test various drivers under the settings to see which one is doing it. I like to do it over several passes, first with the 'Auto select unsigned drivers'. Another approach is to 'Select drivers from a list', sort by company name, and check everything that is not from microsoft.

    Make your choice and reboot, wait for it to bluescreen. I would expect you to receive a STOP 0x000000C1 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION This is expected, and when run through the analysis tool, it will show us which driver did the bad thing. If you get different stop codes, please consult us here with the data that looks like this: BugCheck C5, {0, 2, 1, 80552ae5} for instructions. Probably if its not a C1, then its a miss on the sandbox, and we have to try again. This process is frequently a drawn out affair, taking lots of tries and time to identify the bad guy. (also note that you use the same tool to undo the settings once we are done)

    Its also not without risk. This can go badly, basically crashing your machine as soon as it powers up. If you are not comfortable with recovery from catestrophic software failure, do not do this, or seek professional help from microsoft. Also, make a solid backup before beginning.
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.