none
BSOD when computer goes to sleep

    Question

  • my computer is fairly new about 2 months old and i have had this problem since the day that i got it. everytime that my pc goes into sleep mode it shuts down and upon restart i get a message that windows has recovered from a unexpected shutdown but it doesn't say why it shut down and i don't know how to read a dump file. here is my dump file that i got from my most recent shutdown  

    https://skydrive.live.com/redir?resid=748858AE785AAE6%21110

    Wednesday, November 27, 2013 4:08 AM

Answers

  • Ben

    This one crash was Related to mvs91xx.sys magni Windows Driver from Marvell Semiconductor, Inc.  I would re-install the newest driver available.

    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for mvs91xx.sys
    *** ERROR: Module load completed but symbols could not be loaded for mvs91xx.sys
    Probably caused by : mvs91xx.sys ( mvs91xx+3b890 )


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Andre.Ziegler Wednesday, November 27, 2013 5:42 AM
    • Marked as answer by Ben35343 Thursday, November 28, 2013 2:42 AM
    Wednesday, November 27, 2013 5:36 AM
    Moderator
  • Update the Marvell-AHCI driver (mvs91xx.sys):

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  6
    
    EXCEPTION_RECORD:  fffff8800341b918 -- (.exr 0xfffff8800341b918)
    ExceptionAddress: fffff8800104e88f (mvs91xx+0x000000000003b88f)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    
    
    STACK_TEXT:  
    nt!KiKernelCalloutExceptionHandler
    nt!RtlpExecuteHandlerForException
    nt!RtlDispatchException
    nt!KiDispatchException
    nt!KiExceptionDispatch
    nt!KiBreakpointTrap
    mvs91xx
    0x0
    0x0
    0x0
    0x0
    0x0
    0x0
    0x0
    0x0
    
    
    
    IMAGE_NAME:  mvs91xx.sys
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1e_mvs91xx+3b890
    
    
        Image path: \SystemRoot\system32\DRIVERS\mvs91xx.sys
        Image name: mvs91xx.sys
        Timestamp:        Tue Oct 09 10:50:58 2012 


    "A programmer is just a tool which converts caffeine into code"


    • Edited by Andre.Ziegler Wednesday, November 27, 2013 5:39 AM
    • Marked as answer by Ben35343 Thursday, November 28, 2013 2:21 AM
    Wednesday, November 27, 2013 5:38 AM

All replies

  • Hi Ben

    try running SFC /SCANNOW and running chkdsk /r on your drives


    • Edited by britishdhez Wednesday, November 27, 2013 5:13 AM
    Wednesday, November 27, 2013 5:13 AM
  • Ben

    This one crash was Related to mvs91xx.sys magni Windows Driver from Marvell Semiconductor, Inc.  I would re-install the newest driver available.

    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for mvs91xx.sys
    *** ERROR: Module load completed but symbols could not be loaded for mvs91xx.sys
    Probably caused by : mvs91xx.sys ( mvs91xx+3b890 )


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Andre.Ziegler Wednesday, November 27, 2013 5:42 AM
    • Marked as answer by Ben35343 Thursday, November 28, 2013 2:42 AM
    Wednesday, November 27, 2013 5:36 AM
    Moderator
  • Update the Marvell-AHCI driver (mvs91xx.sys):

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: 0000000000000000, The exception code that was not handled
    Arg2: 0000000000000000, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  6
    
    EXCEPTION_RECORD:  fffff8800341b918 -- (.exr 0xfffff8800341b918)
    ExceptionAddress: fffff8800104e88f (mvs91xx+0x000000000003b88f)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00000000
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    
    
    STACK_TEXT:  
    nt!KiKernelCalloutExceptionHandler
    nt!RtlpExecuteHandlerForException
    nt!RtlDispatchException
    nt!KiDispatchException
    nt!KiExceptionDispatch
    nt!KiBreakpointTrap
    mvs91xx
    0x0
    0x0
    0x0
    0x0
    0x0
    0x0
    0x0
    0x0
    
    
    
    IMAGE_NAME:  mvs91xx.sys
    
    FAILURE_ID_HASH_STRING:  km:x64_0x1e_mvs91xx+3b890
    
    
        Image path: \SystemRoot\system32\DRIVERS\mvs91xx.sys
        Image name: mvs91xx.sys
        Timestamp:        Tue Oct 09 10:50:58 2012 


    "A programmer is just a tool which converts caffeine into code"


    • Edited by Andre.Ziegler Wednesday, November 27, 2013 5:39 AM
    • Marked as answer by Ben35343 Thursday, November 28, 2013 2:21 AM
    Wednesday, November 27, 2013 5:38 AM
  • ok i have fixed the error by using drivermax to find the correct driver for my marvell controller so thank you all for your help it is very much appreciated
    Thursday, November 28, 2013 2:21 AM
  • Ben

    Good luck and thanks for letting us know.


    Wanikiya and Dyami--Team Zigzag

    Saturday, November 30, 2013 2:35 AM
    Moderator