Recovered from unexpected shutdown

davsnotn · Jun 7, 2010

I have had an issue twice in the past couple days of my system rebooting on its own. Here is what it says:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA80090BD050
BCP3: FFFFFA80090BD050
BCP4: FFFFFA800D4845C0
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

I have also included the dmp files. Any help is appreciated.

richc46 · Jun 7, 2010

First do an anti virus and malwarbytes scan to make sure these are not virus caused.
Then go to the device manager and reinstall with the most current driver. If you do not have a virus or other malware this driver must be replaced. If you still experience problems, post and a further analyis will be made
You had two dumps both indicated the same problem

A cursory examination indicates that it is a driver problem. mv61xx.sys, Marvel Thor Driver.

Code:

 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Mini060510-01[1].zip\Mini060510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18160.amd64fre.vistasp2_gdr.091208-0542
Machine Name:
Kernel base = 0xfffff800`0224e000 PsLoadedModuleList = 0xfffff800`02412dd0
Debug session time: Sat Jun  5 08:08:43.978 2010 (GMT-4)
System Uptime: 0 days 13:25:25.478
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80065ef050, fffffa80065ef050, fffffa8008eb1700}
*** WARNING: Unable to verify timestamp for mv61xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv61xx.sys
Probably caused by : mv61xx.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80065ef050, Physical Device Object of the stack
Arg3: fffffa80065ef050, Functional Device Object of the stack
Arg4: fffffa8008eb1700, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa8008eb1700
DEVICE_OBJECT: fffffa80065ef050
DRIVER_OBJECT: fffffa8006582690
IMAGE_NAME:  mv61xx.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  498f92c2
MODULE_NAME: mv61xx
FAULTING_MODULE: fffffa6000a03000 mv61xx
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff8000230378d to fffff800022a8450
STACK_TEXT:  
fffff800`0388c9f8 fffff800`0230378d : 00000000`0000009f 00000000`00000003 fffffa80`065ef050 fffffa80`065ef050 : nt!KeBugCheckEx
fffff800`0388ca00 fffff800`022ac0dd : fffff800`0388cad8 00000000`00000000 00000000`00000001 fffffa60`01b9cb01 : nt! ?? ::FNODOBFM::`string'+0x17cec
fffff800`0388ca70 fffff800`022ab818 : fffff800`0388ccd0 fffffa60`00de1702 fffff800`0388ccc8 00000000`00000010 : nt!KiTimerListExpire+0x30d
fffff800`0388cca0 fffff800`022ac72f : 00000a55`d3b3ab80 00000000`00000000 fffffa80`00000010 fffff800`023c4a80 : nt!KiTimerExpiration+0x1d8
fffff800`0388cd10 fffff800`022ac8e2 : fffff800`023c1680 fffff800`023c1680 00000000`00000000 fffff800`023c6b80 : nt!KiRetireDpcList+0x1df
fffff800`0388cd80 fffff800`02479860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`0388cdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_mv61xx.sys
BUCKET_ID:  X64_0x9F_IMAGE_mv61xx.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80065ef050, Physical Device Object of the stack
Arg3: fffffa80065ef050, Functional Device Object of the stack
Arg4: fffffa8008eb1700, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa8008eb1700
DEVICE_OBJECT: fffffa80065ef050
DRIVER_OBJECT: fffffa8006582690
IMAGE_NAME:  mv61xx.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  498f92c2
MODULE_NAME: mv61xx
FAULTING_MODULE: fffffa6000a03000 mv61xx
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff8000230378d to fffff800022a8450
STACK_TEXT:  
fffff800`0388c9f8 fffff800`0230378d : 00000000`0000009f 00000000`00000003 fffffa80`065ef050 fffffa80`065ef050 : nt!KeBugCheckEx
fffff800`0388ca00 fffff800`022ac0dd : fffff800`0388cad8 00000000`00000000 00000000`00000001 fffffa60`01b9cb01 : nt! ?? ::FNODOBFM::`string'+0x17cec
fffff800`0388ca70 fffff800`022ab818 : fffff800`0388ccd0 fffffa60`00de1702 fffff800`0388ccc8 00000000`00000010 : nt!KiTimerListExpire+0x30d
fffff800`0388cca0 fffff800`022ac72f : 00000a55`d3b3ab80 00000000`00000000 fffffa80`00000010 fffff800`023c4a80 : nt!KiTimerExpiration+0x1d8
fffff800`0388cd10 fffff800`022ac8e2 : fffff800`023c1680 fffff800`023c1680 00000000`00000000 fffff800`023c6b80 : nt!KiRetireDpcList+0x1df
fffff800`0388cd80 fffff800`02479860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`0388cdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_mv61xx.sys
BUCKET_ID:  X64_0x9F_IMAGE_mv61xx.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80065ef050, Physical Device Object of the stack
Arg3: fffffa80065ef050, Functional Device Object of the stack
Arg4: fffffa8008eb1700, The blocked IRP
Debugging Details:
------------------
 
DRVPOWERSTATE_SUBCODE:  3
IRP_ADDRESS:  fffffa8008eb1700
DEVICE_OBJECT: fffffa80065ef050
DRIVER_OBJECT: fffffa8006582690
IMAGE_NAME:  mv61xx.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  498f92c2
MODULE_NAME: mv61xx
FAULTING_MODULE: fffffa6000a03000 mv61xx
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff8000230378d to fffff800022a8450
STACK_TEXT:  
fffff800`0388c9f8 fffff800`0230378d : 00000000`0000009f 00000000`00000003 fffffa80`065ef050 fffffa80`065ef050 : nt!KeBugCheckEx
fffff800`0388ca00 fffff800`022ac0dd : fffff800`0388cad8 00000000`00000000 00000000`00000001 fffffa60`01b9cb01 : nt! ?? ::FNODOBFM::`string'+0x17cec
fffff800`0388ca70 fffff800`022ab818 : fffff800`0388ccd0 fffffa60`00de1702 fffff800`0388ccc8 00000000`00000010 : nt!KiTimerListExpire+0x30d
fffff800`0388cca0 fffff800`022ac72f : 00000a55`d3b3ab80 00000000`00000000 fffffa80`00000010 fffff800`023c4a80 : nt!KiTimerExpiration+0x1d8
fffff800`0388cd10 fffff800`022ac8e2 : fffff800`023c1680 fffff800`023c1680 00000000`00000000 fffff800`023c6b80 : nt!KiRetireDpcList+0x1df
fffff800`0388cd80 fffff800`02479860 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`0388cdb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_mv61xx.sys
BUCKET_ID:  X64_0x9F_IMAGE_mv61xx.sys
Followup: MachineOwner
---------

stoneys-nutz · Jun 8, 2010

Hello davsnotn,
The faulting module is mv61xx.sys.
Marvell SATA RAID Driver
This is your HDD/HDD's setup controller driver, you could try re-installing your chipset drivers and resetting your Bios to its default settings.
This driver will need replacing so i would un-install and re-install with a fresh driver.

Follow Richards advice and you wont go far wrong.

After a BSOD the system files can become corrupt, so i would check them too.
Open a command prompt as administrator and type sfc/scannow press enter and let it scan, if errors are found you will need to scan again until clean.

Also, could you include your system specs in your next post.

Hope this helps, good luck and post your results.

davsnotn · Jun 9, 2010

What program do you use yo read the .dmp files?

richc46 · Jun 9, 2010

http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi

Install that, and then download and extract both of these links to C:\Symbols:

http://download.microsoft.com/download/7/F/B/7FBF7E6A-D0DE-442A-A683-4F9885A96FC9/Windows_Win7.7600.16385.090713-1255.X86FRE.Symbols.msi

http://download.microsoft.com/download/F/1/1/F11206A1-C532-4C9E-86FF-1261A693AA53/Windows_Win7.7600.16385.090713-1255.X64CHK.Symbols.msi

stoneys-nutz · Jun 9, 2010

Here are some sites that helped get me started.

This site is a must have, you will see why when you get there.

BSOD Index

You may find these sites useful, a lot of info and help, also diagnostic tools too.

Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

http://windbg.info/doc/1-common-cmds.html

Windows Debuggers: Part 1: A WinDbg Tutorial - CodeProject

Hope this helps, good luck.

Recovered from unexpected shutdown

davsnotn

New Member

Attachments

My Computer

System One

richc46

My Computer

System One

stoneys-nutz

Gamerholic

My Computer

System One

davsnotn

New Member

My Computer

System One

richc46

My Computer

System One

stoneys-nutz

Gamerholic

My Computer

System One