none
BSOD help to analyze the .dmp file. RRS feed

  • Question

  • Hello!

    I am having problems with a pc at work that gets BSOD quiett often, can someone help me with analyzing this dumpfile?

    Edit: 

    Here is the link to my shared SkyDrive folder with 3 .dmp files from the crashing pc.

    https://skydrive.live.com/redir?resid=EB157FCC7AC40BB7!117&authkey=!AKrrRz4cGAZSgwA

    Sorry for late respons!

    /Martin Sterley


    • Edited by MartinS312 Thursday, September 26, 2013 1:10 PM
    Tuesday, September 10, 2013 7:45 AM

Answers

  • Martin,

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    *

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    *

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  

    *

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)

    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

    *

    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.

    * Reboot if changes have been made.

    *

    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.
    *
    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...
    *
    You can read more about BSODS here
    You can learn how to test your memory here
    *


    Advice offered in good faith. It is your decision to implement same.



    Tuesday, September 10, 2013 8:43 AM
  • Hi,

    Did you make any changes on the computer before the issue happen?

    In addition to upload the dmp file as JMH3143 mentioned, I suggest you try the following method to narrow down the issue.

    1.Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.

    2.Try disabling memory caching of the BIOS.

    3.Make sure the latest Service Pack is installed.

    4.Update your software to the latest version and check the result.

    Regard,


    Kelvin_Hsu

    TechNet Community Support

    Thursday, September 12, 2013 12:21 PM
    Moderator

All replies

  • Martin,

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    *

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    *

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  

    *

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)

    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

    *

    Link for how to  upload below.
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.

    * Reboot if changes have been made.

    *

    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.
    *
    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...
    *
    You can read more about BSODS here
    You can learn how to test your memory here
    *


    Advice offered in good faith. It is your decision to implement same.



    Tuesday, September 10, 2013 8:43 AM
  • Hi,

    Did you make any changes on the computer before the issue happen?

    In addition to upload the dmp file as JMH3143 mentioned, I suggest you try the following method to narrow down the issue.

    1.Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.

    2.Try disabling memory caching of the BIOS.

    3.Make sure the latest Service Pack is installed.

    4.Update your software to the latest version and check the result.

    Regard,


    Kelvin_Hsu

    TechNet Community Support

    Thursday, September 12, 2013 12:21 PM
    Moderator
  • Here is the link to my shared SkyDrive folder with 3 .dmp files from the crashing pc.

    https://skydrive.live.com/redir?resid=EB157FCC7AC40BB7!117&authkey=!AKrrRz4cGAZSgwA

    Sorry for late respons!

    /Martin Sterley


    msterley

    Thursday, September 26, 2013 1:10 PM
  • Martin

    The three DMPS have 3 different apparent causes.  I would run verifier to find out which driver is mis-behaving

    Driver verifier
    Using Driver Verifier is an iffy proposition.
    Most times it will crash and it will tell you what the driver is, but sometimes it will crash and won't tell you the driver.
    Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Here is the procedure:

    Go to Start and type in "verifier" (without the quotes) and press Enter
    Select "Create custom settings (for code developers)" and click "Next
    Select "Select individual settings from a full list" and click "Next"
    Select everything EXCEPT FOR "Low Resource Simulation" 
    For Win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"
    Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen.

    Continue to use your system normally, and if you know what causes the crash, do that repeatedly. 
    The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. 
    If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    Further Reading
    http://support.microsoft.com/kb/244617


    Wanikiya & Dyami--Team Zigzag

    Thursday, September 26, 2013 4:32 PM
    Moderator