Windows Server 2008 R2 Windows Server 2008 crashes and restart suddenlycrashes and restart suddenly

• Thursday, February 21, 2013 8:18 AM

   

   
  

  0
  Hi,

  I'm having some problems on a Windows Web Server 2008 R2 (SP1) Intel Core i5 2.8GHz 8GB (64b)

  Some times it crashes and restarts. I've been debugging the minidump files with Windows Tools Debugging and it seems something related to harddrive but I'm not completly sure.

  Here I attach first the event data from Windows Event Log and the corresponding dump file data.

  I hope you can give me some help about this issue.

  Thanks very much.

  
  

  Event Data

  
  

  - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  - <System>

  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />

  <EventID>41</EventID>

  <Version>2</Version>

  <Level>1</Level>

  <Task>63</Task>

  <Opcode>0</Opcode>

  <Keywords>0x8000000000000002</Keywords>

  <TimeCreated SystemTime="2013-02-19T13:46:08.069209800Z" />

  <EventRecordID>248734</EventRecordID>

  <Correlation />

  <Execution ProcessID="4" ThreadID="8" />

  <Channel>System</Channel>

  <Computer>ns390630</Computer>

  <Security UserID="S-1-5-18" />

  </System>

  - <EventData>

  <Data Name="BugcheckCode">122</Data>

  <Data Name="BugcheckParameter1">0xfffff6fc400073e8</Data>

  <Data Name="BugcheckParameter2">0xffffffffc0000185</Data>

  <Data Name="BugcheckParameter3">0x6d56a880</Data>

  <Data Name="BugcheckParameter4">0xfffff88000e7d000</Data>

  <Data Name="SleepInProgress">false</Data>

  <Data Name="PowerButtonTimestamp">0</Data>

  </EventData>

  </Event>

  Dump file

  Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

  Copyright (c) Microsoft Corporation. All rights reserved.

  Loading Dump File [C:\Windows\Minidump\021913-79841-01.dmp]

  Mini Kernel Dump File: Only registers and stack trace are available

  Symbol search path is: srv*

  Executable search path is: 

  Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

  Product: Server, suite: TerminalServer SingleUserTS Blade

  Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431

  Machine Name:

  Kernel base = 0xfffff800`01815000 PsLoadedModuleList = 0xfffff800`01a59670

  Debug session time: Tue Feb 19 14:44:18.860 2013 (UTC + 1:00)

  System Uptime: 5 days 16:09:39.632

  Loading Kernel Symbols

  ...............................................................

  ............................................................

  Loading User Symbols

  Loading unloaded module list

  ................

  *******************************************************************************

  *                                                                             *

  *                        Bugcheck Analysis                                    *

  *                                                                             *

  *******************************************************************************

  Use !analyze -v to get detailed debugging information.

  BugCheck 7A, {fffff6fc400073e8, ffffffffc0000185, 6d56a880, fffff88000e7d000}

  Probably caused by : volmgr.sys ( volmgr!VmpQueryCapabilities+25 )

  Followup: MachineOwner

  ---------

  1: kd> !analyze -v

  *******************************************************************************

  *                                                                             *

  *                        Bugcheck Analysis                                    *

  *                                                                             *

  *******************************************************************************

  KERNEL_DATA_INPAGE_ERROR (7a)

  The requested page of kernel data could not be read in.  Typically caused by

  a bad block in the paging file or disk controller error. Also see

  KERNEL_STACK_INPAGE_ERROR.

  If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,

  it means the disk subsystem has experienced a failure.

  If the error status is 0xC000009A, then it means the request failed because

  a filesystem failed to make forward progress.

  Arguments:

  Arg1: fffff6fc400073e8, lock type that was held (value 1,2,3, or PTE address)

  Arg2: ffffffffc0000185, error status (normally i/o status code)

  Arg3: 000000006d56a880, current process (virtual address for lock type 3, or PTE)

  Arg4: fffff88000e7d000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

  Debugging Details:

  ------------------

  ERROR_CODE: (NTSTATUS) 0xc0000185 - El dispositivo de E/S ha comunicado un error de E/S.

  DISK_HARDWARE_ERROR: There was error with disk hardware

  BUGCHECK_STR:  0x7a_c0000185

  CUSTOMER_CRASH_COUNT:  1

  DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

  PROCESS_NAME:  vds.exe

  CURRENT_IRQL:  0

  LAST_CONTROL_TRANSFER:  from fffff800018fd812 to fffff8000188ac40

  STACK_TEXT:  

  fffff880`0557d398 fffff800`018fd812 : 00000000`0000007a fffff6fc`400073e8 ffffffff`c0000185 00000000`6d56a880 : nt!KeBugCheckEx

  fffff880`0557d3a0 fffff800`018b1a0f : fffffa80`08705340 fffff880`0557d4d0 fffff800`01ac6540 fffff800`01ac6540 : nt! ?? ::FNODOBFM::`string'+0x36c1a

  fffff880`0557d480 fffff800`018982a9 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b

  fffff880`0557d510 fffff800`018f7cbc : 00000000`00000000 fffff880`00e7d000 00000000`00198e00 fffffa80`0a55e060 : nt!MmAccessFault+0x1399

  fffff880`0557d670 fffff800`01b02a87 : 00000000`00000000 fffff880`00e60240 fffffa80`06f497a0 fffff800`01ac6540 : nt! ?? ::FNODOBFM::`string'+0x2e428

  fffff880`0557d7a0 fffff880`012cb7a5 : 00000000`00000000 00000000`00000000 fffffa80`06f497a0 fffffa80`08ebb700 : nt!MmResetDriverPaging+0x127

  fffff880`0557d7d0 fffff880`012c20f2 : fffffa80`0a5a1f20 fffffa80`08ebb700 00000000`00000101 00000000`00000001 : volmgr!VmpQueryCapabilities+0x25

  fffff880`0557d800 fffff800`01ba9b57 : fffffa80`08ebb860 fffff880`0557dca0 fffffa80`0a5a1f20 fffffa80`08ebb700 : volmgr! ?? ::FNODOBFM::`string'+0x75c

  fffff880`0557da10 fffff800`01baa3b6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607

  fffff880`0557db40 fffff800`01889ed3 : 00000000`00000000 0000007f`ffffffff 00000000`00000000 00000980`00000000 : nt!NtDeviceIoControlFile+0x56

  fffff880`0557dbb0 00000000`77bd138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

  00000000`0113f6b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bd138a

  STACK_COMMAND:  kb

  FOLLOWUP_IP: 

  volmgr!VmpQueryCapabilities+25

  fffff880`012cb7a5 4c8b9e58010000  mov     r11,qword ptr [rsi+158h]

  SYMBOL_STACK_INDEX:  6

  SYMBOL_NAME:  volmgr!VmpQueryCapabilities+25

  FOLLOWUP_NAME:  MachineOwner

  MODULE_NAME: volmgr

  IMAGE_NAME:  volmgr.sys

  DEBUG_FLR_IMAGE_TIMESTAMP:  4ce792a0

  FAILURE_BUCKET_ID:  X64_0x7a_c0000185_volmgr!VmpQueryCapabilities+25

  BUCKET_ID:  X64_0x7a_c0000185_volmgr!VmpQueryCapabilities+25

  Followup: MachineOwner

  ---------
  • Reply
  • Quote