locked
Blue Screen after coming back from Sleep and Hibernate! RRS feed

  • Question

  • I have a Sony Vaio VPC F13 WFX /b. running Windows 7 64bit. with 8 gig of RAM.
    I'm experiencing this problem recently, and I don't know what really cause this pain.

     

    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7601.2.1.0.768.3
    Locale ID:    1033

    Files that help describe the problem (some files may no longer be available)
    070811-21247-01.dmp
    sysdata.xml

    View a temporary copy of these files
    Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

    Extra information about the problem
    BCCode:    c2
    BCP1:    0000000000000007
    BCP2:    000000000000109B
    BCP3:    0000000004440003
    BCP4:    FFFFFA800A861AD0
    OS Version:    6_1_7601
    Service Pack:    1_0
    Product:    768_1

    Friday, July 8, 2011 2:29 AM

Answers

  • Hi,

    The dump file indicates "Probably caused by : srescan.sys ( srescan+6355 )"

    If you have Zone Alarm, please rename srescan exe file so that it won't inproperly detect it.

    If you have other security software, please disable it to troubleshoot.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Tuesday, July 12, 2011 10:21 AM
    Moderator
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, Attempt to free pool which was already freed
    Arg2: 000000000000109b, (reserved)
    Arg3: 0000000004440003, Memory contents of the pool block
    Arg4: fffffa800a861ad0, Address of the block of pool being deallocated
    Debugging Details:
    ------------------
    Unable to load image \SystemRoot\system32\DRIVERS\HssDrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for HssDrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for HssDrv.sys
    POOL_ADDRESS:  fffffa800a861ad0 
    FREED_POOL_TAG:  aPmI
    BUGCHECK_STR:  0xc2_7_aPmI
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff800033bcbe9 to fffff80003291d00
    STACK_TEXT:  
    fffff880`0357e228 fffff800`033bcbe9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`04440003 : nt!KeBugCheckEx
    fffff880`0357e230 fffff880`016ea195 : 00000000`00000000 00000000`00000000 00000000`6370444e 00000000`00000000 : nt!ExDeferredFreePool+0x1201
    fffff880`0357e2e0 fffff880`02e3ebac : fffff880`0357e520 fffffa80`0a2cb778 fffffa80`0a2cb778 fffffa80`0a2cb778 : ndis!NdisFreeMemory+0x15
    fffff880`0357e310 fffff880`0357e520 : fffffa80`0a2cb778 fffffa80`0a2cb778 fffffa80`0a2cb778 fffff880`02e48100 : HssDrv+0x2bac
    fffff880`0357e318 fffffa80`0a2cb778 : fffffa80`0a2cb778 fffffa80`0a2cb778 fffff880`02e48100 00000000`00000004 : 0xfffff880`0357e520
    fffff880`0357e320 fffffa80`0a2cb778 : fffffa80`0a2cb778 fffff880`02e48100 00000000`00000004 fffffa80`0a2da690 : 0xfffffa80`0a2cb778
    fffff880`0357e328 fffffa80`0a2cb778 : fffff880`02e48100 00000000`00000004 fffffa80`0a2da690 fffffa80`0a861ad0 : 0xfffffa80`0a2cb778
    fffff880`0357e330 fffff880`02e48100 : 00000000`00000004 fffffa80`0a2da690 fffffa80`0a861ad0 fffffa80`0a2cb778 : 0xfffffa80`0a2cb778
    fffff880`0357e338 00000000`00000004 : fffffa80`0a2da690 fffffa80`0a861ad0 fffffa80`0a2cb778 fffffa80`00000000 : HssDrv+0xc100
    fffff880`0357e340 fffffa80`0a2da690 : fffffa80`0a861ad0 fffffa80`0a2cb778 fffffa80`00000000 00000000`00000000 : 0x4
    fffff880`0357e348 fffffa80`0a861ad0 : fffffa80`0a2cb778 fffffa80`00000000 00000000`00000000 fffff880`016e9723 : 0xfffffa80`0a2da690
    fffff880`0357e350 fffffa80`0a2cb778 : fffffa80`00000000 00000000`00000000 fffff880`016e9723 00000000`00000000 : 0xfffffa80`0a861ad0
    fffff880`0357e358 fffffa80`00000000 : 00000000`00000000 fffff880`016e9723 00000000`00000000 fffffa80`0a861ad0 : 0xfffffa80`0a2cb778
    fffff880`0357e360 00000000`00000000 : fffff880`016e9723 00000000`00000000 fffffa80`0a861ad0 fffffa80`0a012938 : 0xfffffa80`00000000
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    HssDrv+2bac
    fffff880`02e3ebac ??              ???
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  HssDrv+2bac
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: HssDrv
    IMAGE_NAME:  HssDrv.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c7fe308
    FAILURE_BUCKET_ID:  X64_0xc2_7_aPmI_HssDrv+2bac
    BUCKET_ID:  X64_0xc2_7_aPmI_HssDrv+2bac
    Followup: MachineOwner
    ---------
    1: kd> lmvm HssDrv
    start             end                 module name
    fffff880`02e3c000 fffff880`02e55000   HssDrv   T (no symbols)           
        Loaded symbol image file: HssDrv.sys
        Image path: \SystemRoot\system32\DRIVERS\HssDrv.sys
        Image name: HssDrv.sys
        Timestamp:        Thu Sep 02 18:46:48 2010 (4C7FE308)
        CheckSum:         00019055
        ImageSize:        00019000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    -------------------------------------------------------------------------------------------------------
    You have to enable Driver Verifier to get more information.
    It is possible that the BSOD was caused by HssDrv.sys which belongs to Hotspot Shield system driver file. Try uninstalling it and check again.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Tuesday, July 12, 2011 10:13 PM

All replies

  • link to the dump file:

     

    https://skydrive.live.com/?cid=c868c15c2e30a245&sc=documents&uc=1&id=C868C15C2E30A245%21106#

    Friday, July 8, 2011 2:38 AM
  • I have a Sony Vaio VPC F13 WFX /b. running Windows 7 64bit. with 8 gig of RAM.
    I'm experiencing this problem recently, and I don't know what really cause this pain.

     

    Problem signature
    Problem Event Name:    BlueScreen
    OS Version:    6.1.7601.2.1.0.768.3
    Locale ID:    1033

    Files that help describe the problem (some files may no longer be available)
    070811-21247-01.dmp
    sysdata.xml

    View a temporary copy of these files
    Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

    Extra information about the problem
    BCCode:    c2
    BCP1:    0000000000000007
    BCP2:    000000000000109B
    BCP3:    0000000004440003
    BCP4:    FFFFFA800A861AD0
    OS Version:    6_1_7601
    Service Pack:    1_0
    Product:    768_1

    i suggest you get latest windows update and also latest VGA drivers from your PC manufacturer's website.
    Tunde Abagun MCP,MCSA,MCTS,MCITP en p "for the love of Computers"
    Saturday, July 9, 2011 8:46 PM
  • Hi,

    The dump file indicates "Probably caused by : srescan.sys ( srescan+6355 )"

    If you have Zone Alarm, please rename srescan exe file so that it won't inproperly detect it.

    If you have other security software, please disable it to troubleshoot.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    Tuesday, July 12, 2011 10:21 AM
    Moderator
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 0000000000000007, Attempt to free pool which was already freed
    Arg2: 000000000000109b, (reserved)
    Arg3: 0000000004440003, Memory contents of the pool block
    Arg4: fffffa800a861ad0, Address of the block of pool being deallocated
    Debugging Details:
    ------------------
    Unable to load image \SystemRoot\system32\DRIVERS\HssDrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for HssDrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for HssDrv.sys
    POOL_ADDRESS:  fffffa800a861ad0 
    FREED_POOL_TAG:  aPmI
    BUGCHECK_STR:  0xc2_7_aPmI
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff800033bcbe9 to fffff80003291d00
    STACK_TEXT:  
    fffff880`0357e228 fffff800`033bcbe9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`04440003 : nt!KeBugCheckEx
    fffff880`0357e230 fffff880`016ea195 : 00000000`00000000 00000000`00000000 00000000`6370444e 00000000`00000000 : nt!ExDeferredFreePool+0x1201
    fffff880`0357e2e0 fffff880`02e3ebac : fffff880`0357e520 fffffa80`0a2cb778 fffffa80`0a2cb778 fffffa80`0a2cb778 : ndis!NdisFreeMemory+0x15
    fffff880`0357e310 fffff880`0357e520 : fffffa80`0a2cb778 fffffa80`0a2cb778 fffffa80`0a2cb778 fffff880`02e48100 : HssDrv+0x2bac
    fffff880`0357e318 fffffa80`0a2cb778 : fffffa80`0a2cb778 fffffa80`0a2cb778 fffff880`02e48100 00000000`00000004 : 0xfffff880`0357e520
    fffff880`0357e320 fffffa80`0a2cb778 : fffffa80`0a2cb778 fffff880`02e48100 00000000`00000004 fffffa80`0a2da690 : 0xfffffa80`0a2cb778
    fffff880`0357e328 fffffa80`0a2cb778 : fffff880`02e48100 00000000`00000004 fffffa80`0a2da690 fffffa80`0a861ad0 : 0xfffffa80`0a2cb778
    fffff880`0357e330 fffff880`02e48100 : 00000000`00000004 fffffa80`0a2da690 fffffa80`0a861ad0 fffffa80`0a2cb778 : 0xfffffa80`0a2cb778
    fffff880`0357e338 00000000`00000004 : fffffa80`0a2da690 fffffa80`0a861ad0 fffffa80`0a2cb778 fffffa80`00000000 : HssDrv+0xc100
    fffff880`0357e340 fffffa80`0a2da690 : fffffa80`0a861ad0 fffffa80`0a2cb778 fffffa80`00000000 00000000`00000000 : 0x4
    fffff880`0357e348 fffffa80`0a861ad0 : fffffa80`0a2cb778 fffffa80`00000000 00000000`00000000 fffff880`016e9723 : 0xfffffa80`0a2da690
    fffff880`0357e350 fffffa80`0a2cb778 : fffffa80`00000000 00000000`00000000 fffff880`016e9723 00000000`00000000 : 0xfffffa80`0a861ad0
    fffff880`0357e358 fffffa80`00000000 : 00000000`00000000 fffff880`016e9723 00000000`00000000 fffffa80`0a861ad0 : 0xfffffa80`0a2cb778
    fffff880`0357e360 00000000`00000000 : fffff880`016e9723 00000000`00000000 fffffa80`0a861ad0 fffffa80`0a012938 : 0xfffffa80`00000000
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    HssDrv+2bac
    fffff880`02e3ebac ??              ???
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  HssDrv+2bac
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: HssDrv
    IMAGE_NAME:  HssDrv.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c7fe308
    FAILURE_BUCKET_ID:  X64_0xc2_7_aPmI_HssDrv+2bac
    BUCKET_ID:  X64_0xc2_7_aPmI_HssDrv+2bac
    Followup: MachineOwner
    ---------
    1: kd> lmvm HssDrv
    start             end                 module name
    fffff880`02e3c000 fffff880`02e55000   HssDrv   T (no symbols)           
        Loaded symbol image file: HssDrv.sys
        Image path: \SystemRoot\system32\DRIVERS\HssDrv.sys
        Image name: HssDrv.sys
        Timestamp:        Thu Sep 02 18:46:48 2010 (4C7FE308)
        CheckSum:         00019055
        ImageSize:        00019000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    -------------------------------------------------------------------------------------------------------
    You have to enable Driver Verifier to get more information.
    It is possible that the BSOD was caused by HssDrv.sys which belongs to Hotspot Shield system driver file. Try uninstalling it and check again.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator

    Tuesday, July 12, 2011 10:13 PM