Help with BSOD diagnosis


  • Hi,

    I just seemingly randomly started getting BSOD with no changes to hardware or drivers.  Can someone help me diagnose it?

    This far I have updated my BIOS and ran Memtest86+.  I don't know what steps to take next.

    Here is the memory dump


    Montag, 15. Oktober 2012 14:51

Alle Antworten

  • That file is over 700 mb. That's not a memory dump file!
    Montag, 15. Oktober 2012 15:32
  • I'm afraid Windows disagrees with you.  This is the file that was in C:\Windows\MEMORY.DMP after the crash.
    Montag, 15. Oktober 2012 17:57
  • Dan Sell

    It is (of course) a full memory dmp as opposed to a kernel memory DMP.  A pain to upload but just as good (in fact slightly better).  You can configure your system in cpnl to use a small memory dmp to make it easier on both of us.

    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.

     These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem. 

    *Dont forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!   If you dont know what this means you probably arent


    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. 

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    *Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    *But sometimes it'll 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).

    *In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's 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" and 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
    Using Driver Verifier to identify issues with Windows drivers for advanced users

    MS-MVP 2010, 2011, 2012 Team ZigZag

    Montag, 15. Oktober 2012 19:34
  • Thanks for the reply.  I will follow your steps once I get home from work.

    Montag, 15. Oktober 2012 23:52
  • Let us know if you need help with the tests

    Good luck

    MS-MVP 2010, 2011, 2012 Team ZigZag

    Dienstag, 16. Oktober 2012 03:34
  • Apparently I have had this enabled for a while.

    Here is a few days worth of crashes.  Any help is appreciated.



    I'm running memtest again.  So far 2 passes and no errors.  I'll let it run all night.
    • Bearbeitet Dan Sell Dienstag, 16. Oktober 2012 05:57
    Dienstag, 16. Oktober 2012 05:19
  • Ok, this time I got plenty of errors while running memtest - not sure why the previous attempt yielded none.  Do the results tell me which stick is having issues or do I need to now run it one by one...  Also, it seems like test #7 is what consistently fails; does that mean I can only run that test?



    Dienstag, 16. Oktober 2012 15:34
  • I found it odd that all the errors were in pass 1 and nothing had shown up previously, so I ran just test #7 for 5 passes without any error showing up.  Confusing.
    Dienstag, 16. Oktober 2012 18:44
  • Ok.  I screwed around a little more.  I noticed that doing a custom test with Prime95 and allocating 14 gb of memory and pushing start / stop is enough to cause bsod.

    I ran memtest again, and I am getting a lot of test #4 failures in the same memory address range as my post before.  I guess I need to start testing individual sticks now to figure out which one it is.

    Dienstag, 16. Oktober 2012 20:37
  • Hi,

    The dump file indicates that the BSOD is probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 ).

    If an error was detected by memtest, you may replace the faulty RAM or contact your manufacturer Technical Support for assistance.

    Tracy Cai

    TechNet Community Support

    Mittwoch, 17. Oktober 2012 02:53
  • Getting memtest to detect it has, unfortunately, been flaky :(  Trying to isolate which stick it is, but getting memtest to show the errors is not consistent.
    Mittwoch, 17. Oktober 2012 04:36