BSOD Dump analysis - please help

Page 2 of 2 FirstFirst 12

  1. Posts : 5,705
    Win7 x64 + x86
       #11

    Error due to unknown image.

    First, Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:
    How To Find Updated Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - some driver links are on this page: http://www.carrona.org/drvrdown.html

    Here's the older drivers:
    Code:
    SaiH0255.sys Fri Feb 15 08:15:05 2008 - Saitek Hid Driver                                                              
    snapman.sys  Fri Jul 13 06:03:12 2007 - Acronis True Image Driver
    tdrpman.sys  Mon Oct 29 08:29:29 2007 - Acronis True Image Driver
    tifsfilt.sys Wed Aug 29 08:37:29 2007 - Acronis True Image Driver
    timntr.sys   Wed Aug 29 08:38:23 2007 - Acronis True Image Driver
    If you cannot locate updated, please uninstall these programs/devices until we're finished troubleshooting.

    If this fixes the BSOD's there's no need to do any more. But, if it doesn't, then try the following:

    Because this is a pool corruption, Driver Verifier is the tool to determine the cause. Please run it using the following directions:
    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.

    So, I'd suggest that you first backup your stuff 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).

    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 (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    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.
    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    Here's a summary of the BSOD:
    Code:
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Debug session time: Tue Jan 26 09:08:27.869 2010 (GMT-5)
    System Uptime: 0 days 0:29:33.900
    BugCheck 19, {3, fffff80003253d90, fffff80023253d90, fffff80003253d90}
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  fsx.exe
      My Computer


  2. Posts : 8
    windows 7 64 bit
    Thread Starter
       #12

    Hello Usasma,
    Thanks again for your continuing help. I disabled the drivers you identified via Autoruns but when I restarted the system, a BSOD occurred during power-up and a message advised me to use the Windows Repair option (I have had to use this option 3 or 4 times over the last few months when the system failed to power-up normally, although this is the first time I've had a BSOD during power-up). Previously the Repair option worked and the system restarted, but this time the Repair failed and the system would not start.

    I have been experiencing BSODs since upgrading to the 64bit Professional retail version. When I was previously running the 32 bit RC version I had no problems with BSODs, so I have replaced the 64bit Professional retail version wth the 32bit Professional retail version to see if that improves the situation. Will post the results!!
      My Computer


  3. Posts : 2
    Windows 7 x64
       #13

    I have the exact same problems. The same 3 BSOD Errors appear over and over again. But unfortunately far more often than on your side. I started with the verifier.exe now. Where does it put the Dumps when I generate my first BSOD with verifier running?
    I'm doing my best to recreate the errors now
      My Computer


  4. Posts : 8
    windows 7 64 bit
    Thread Starter
       #14

    Sorry, Custom, as I explained in my last post, I was not able to go down the Verifier route, but hopefully Usasma will respond to your question.

    Good luck,

    Ken
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #15

    custom - Please start your own topic so that your issue(s) can get the individual attention that they deserve.
      My Computer


  6. Posts : 2
    Windows 7 x64
       #16

    fixed! i did some more restoring and swapped the RAM sticks from slots 2+4 to slots 1+3. system is stable now.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:45.
Find Us