Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Need help anaylzing a windows 7 mini-dump

Answered Need help anaylzing a windows 7 mini-dump

  • Tuesday, October 02, 2012 2:07 AM
     
     
    Sign In to Vote
    0

    Here's the deal: Intel motherboard, 8GB RAM, I-5 CPU, Win7/64 Pro

    We know that the BSD is being caused by a driver - we just can't figure out which one.  We use several USB devices on our system that appear to be causing our grief (The system will NOT BSD if none of these devices are connected).

    My snip of what WhoCrashed, the mini-dump and compressed full memory dump is here:

    https://skydrive.live.com/?ppud=4#cid=1B83EF35C621A41D&id=1B83EF35C621A41D!103

    If someone smarter (and who has more time) than me can take a fast look, I'd be in your debt.  I'm sure I'm missing something dead-obvious


     

All Replies

  • Tuesday, October 02, 2012 7:50 AM
    Moderator
     
     
    Sign In to Vote
    0

    This was related to Fx2Cam64P2.sys.  I can find little information on it in google and that makes me suspicious.  If you know what it is remove it (at least to test) if you dont know what it is I would run Malwarbytes just to be on the safe side.

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    

                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e0 fffffa80093d7060 00000000 fffff88004e07630-fffffa8007f676d0 Success Error Cancel
               \Driver\usbhub    Fx2Cam64P2
                Args: 00016600 00000001 00000004 00000005
     [ 16, 2]   0 e1 fffffa8007f67580 00000000 00000000-00000000    pending
               \Driver\Fx2CamP2

    Please download the free version of Malwarebytes.
    Update it immediately.
    Do a full system scan
    Let us know the results at the end.

    http://www.malwarebytes.org/products

    MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag

     
  • Tuesday, October 02, 2012 12:17 PM
     
     Answered
    Sign In to Vote
    0

    If you're pretty sure it's a USB device, then troubleshoot it by only plugging one in at a time and see what happens. It may not be a single device doing it, but a combination of two or three not playing well together.
    As Zigzag posted, there doesn't seem to be much associated with Fx2Cam64. The only thing I could find on it was that it's part of a SDK Web Installer package:

    http://www.id-reader.com/ftp/applications/sdk/SDK_Web_Installer_Files/drivers/SnapShell/SnapShell%2032%20bit/Windows%20Vista_7/

    Do you have a bar code scanner and/or card swipe reader attached? I'd start with it (them).

     SC Tom

    • Marked As Answer by BigOldHarry Tuesday, October 02, 2012 5:32 PM
    •  
     
  • Tuesday, October 02, 2012 5:25 PM
     
     
    Sign In to Vote
    0

    Yup, Fx2Cam64.sys is a driver file for our USB connected ID reader device which has given us grief in other ways.

    Guys, that REALLY REALLY HELPS!!!

    Oh, and can you point me at what tool you used to read my dumps (man, that sounds awful...) -

    thanks

     
  • Tuesday, October 02, 2012 5:53 PM
     
     
    Sign In to Vote
    0

    I got the file name from Zigzag's reply, but I usually use WhoCrashed (which I believe you have?), and for greater detail, BlueScreenView:

    http://www.nirsoft.net/utils/blue_screen_view.html

    SC Tom

     
  • Tuesday, October 02, 2012 9:43 PM
     
     
    Sign In to Vote
    0

    Hmmm.... I think I haven't learned all the cool tricks of "Whocrashed" - and I actually paid for it!

    Guess I'll dig in a bit more.

    I just installed the whole Windows debugger kit - what a PITA.  Do they go out of their way to make this tricky?

    thanks again

     
  • Wednesday, October 03, 2012 12:48 AM
     
     
    Sign In to Vote
    0

    I never had the patience (or the necessity) to go through all that. I played around with it on my old XP system, but never got it to work correctly. Way too involved for a retired guy :)

     SC Tom

     
  • Wednesday, October 03, 2012 8:58 PM
     
     
    Sign In to Vote
    0

    ZigZag

    I did download "Malware Bytes" and did a system scan - nothing bad found.

    Can you please give me a bit more info -  what tool did you use to find the reference to the file "Fx2Cam64P2" - The system does indeed have that file (it's a driver file for the ID scanner on our system).

    thanks much

     
  • Friday, October 05, 2012 10:46 AM
    Moderator
     
     Answered
    Sign In to Vote
    0
    It is called Win Debugger and is the gold standard for those of us that do BSOD Kernel analysis.  It has a steep learning curve but can be learned if you are interested in doing them.

    MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag

    • Marked As Answer by BigOldHarry Tuesday, November 06, 2012 2:41 AM
    •  
     
  • Tuesday, November 06, 2012 5:37 AM
    Moderator
     
     
    Sign In to Vote
    0

    BigOldHarry

    The problem that Whocrashed and Bluescreenview is that they often erroneously blame an OS file.  WinDBG is more complicated (but not rocket science if you are really interested).

    There are also sites online that will analyze the DMPS for you.

    There is a really good site (disclaimer needed here--  I am also there) for BSOD'S called Sysnative.com http://www.sysnative.com/forums/forum.php  There is quite a collection of experts.

    Let us know if you need more assistance

    ZZ

    MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag