locked
BSOD with minidump file RRS feed

  • Question

  • https://skydrive.live.com/redir?resid=36DEF99EE09BB12F!502&authkey=!ABrM5b5mNBSmdR0&ithint=file%2c.dmp

    Hi everyone, this isn't for my computers, for a family members. They have experienced the BSOD at random times, and can't re-create it by opening any particular software program. The suspect is USB tethering of an iPhone for internet access. Could someone please help by examining the minidump and assisting me with identifying the problem :)

    Thanks heaps everyone!!

    Monday, December 30, 2013 1:29 AM

Answers

  • Benny

    Two drivers need re-installing

    *

    1-Related to igdpmd64.sys Graphics Kernel Mode Drive from Intel Corporation

    2-Related to SynTP.sys Synaptics Touchpad Driver. (SynTP.sys)

    *

    If they continue to crash I would remove AVG and replace with MSE

    AVG  can be a contributing cause of BSOD'S.
    Please remove and replace with Microsoft Security Essentials at least to test.
     

    http://www.microsoft.com/security_essentials/"]Microsoft Security Essentials - Free Antivirus for Windows

    BugCheck 50, {fffff880a81303a0, 0, fffff88005aaec75, 5}
    
    *** WARNING: Unable to verify timestamp for igdpmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdpmd64.sys
    
    Probably caused by : igdpmd64.sys ( igdpmd64+a7c75 )
    
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff880a81303a0, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff88005aaec75, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fc100
    GetUlongFromAddress: unable to read from fffff800032fc1c0
     fffff880a81303a0 Nonpaged pool
    
    FAULTING_IP: 
    igdpmd64+a7c75
    fffff880`05aaec75 8b0401          mov     eax,dword ptr [rcx+rax]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    
    LAST_CONTROL_TRANSFER:  from fffff800031415b3 to fffff800030c4bc0
    
    FOLLOWUP_IP: 
    igdpmd64+a7c75
    fffff880`05aaec75 8b0401          mov     eax,dword ptr [rcx+rax]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  igdpmd64+a7c75
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: igdpmd64
    
    IMAGE_NAME:  igdpmd64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4da88994
    
    FAILURE_BUCKET_ID:  X64_0x50_igdpmd64+a7c75
    
    BUCKET_ID:  X64_0x50_igdpmd64+a7c75
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x50_igdpmd64+a7c75
    
    FAILURE_ID_HASH:  {af29e5b6-54b8-014d-d52f-ea0944be5b7a}
    
    Followup: MachineOwner
    ---------
    


    Wanikiya and Dyami--Team Zigzag


    • Edited by ZigZag3143x Monday, December 30, 2013 1:55 AM
    • Proposed as answer by blair deng Monday, December 30, 2013 8:26 AM
    • Marked as answer by ZigZag3143x Saturday, January 4, 2014 2:00 AM
    Monday, December 30, 2013 1:50 AM