Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue Scree Error


  • Please log in to reply
2 replies to this topic

#1 Shama

Shama

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:10:17 PM

Posted 24 May 2010 - 02:42 PM

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\052410-15506-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols


Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0280c000 PsLoadedModuleList = 0xfffff800`02a49e50
Debug session time: Mon May 24 18:18:53.491 2010 (GMT+6)
System Uptime: 0 days 7:50:01.514
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc40013920, ffffffffc000000e, 977edbe0, fffff88002724000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34c4e )

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

0: 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: fffff6fc40013920, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000000977edbe0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88002724000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800028f10a8 to fffff8000287c600

STACK_TEXT:
fffff880`03140888 fffff800`028f10a8 : 00000000`0000007a fffff6fc`40013920 ffffffff`c000000e 00000000`977edbe0 : nt!KeBugCheckEx
fffff880`03140890 fffff800`0286e42b : fffffa80`0458fb00 fffff880`031409c0 fffff800`02a09440 fffffa80`0458fbf8 : nt! ?? ::FNODOBFM::`string'+0x34c4e
fffff880`03140970 fffff800`028974a4 : 00000000`00000000 00000000`00000001 ffffffff`ffffffff fffff800`00000000 : nt!MiIssueHardFault+0x28b
fffff880`03140a00 fffff800`02870f08 : 00000000`00000001 fffff6fc`400138f8 fffffa80`05ca2b00 fffff880`05f2ecd0 : nt!MmAccessFault+0x11c4
fffff880`03140b60 fffff800`028710f4 : fffffa80`05ca2b60 00000000`00000001 fffffa80`05b36060 fffff800`0286f2fb : nt!MiInPageSingleKernelStack+0x134
fffff880`03140c70 fffff800`0287108f : fffffa80`05b36060 00000000`00000080 fffffa80`03c73b30 fffffa80`05ca2c00 : nt!MmInPageKernelStack+0x40
fffff880`03140cd0 fffff800`02870d2c : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03c73b00 : nt!KiInSwapKernelStacks+0x1f
fffff880`03140d00 fffff800`02b21a86 : 0016bd28`0016bd58 0016bc00`00000000 000100d0`0016bc58 0016bd40`0016bd70 : nt!KeSwapProcessOrStack+0x84
fffff880`03140d40 fffff800`0285ab06 : fffff800`029f6e80 fffffa80`03cff680 fffff800`02a04c40 00740069`0016aeb0 : nt!PspSystemThreadStartup+0x5a
fffff880`03140d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34c4e
fffff800`028f10a8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+34c4e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

BUCKET_ID: X64_0x7a_c000000e_nt!_??_::FNODOBFM::_string_+34c4e

Followup: MachineOwner
---------

BC AdBot (Login to Remove)

 


#2 computerxpds

computerxpds

    Bleepin' Comp


  • Moderator
  • 4,488 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:USA
  • Local time:12:47 PM

Posted 24 May 2010 - 03:26 PM

Download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply. :huh:
sigcomp.png 
If I have replied to a topic and you reply and I haven't gotten back to you within 48 hours (2 days) then send me a P.M.
Some important links: BC Forum Rules | Misplaced Malware Logs | BC Tutorials | BC Downloads |
Follow BleepingComputer on: Facebook! | Twitter! | Google+| Come join us on the BleepingComputer Live Chat on Discord too! |

#3 hamluis

hamluis

    Moderator


  • Moderator
  • 56,124 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:47 AM

Posted 25 May 2010 - 01:37 PM

Well..."DISK_HARDWARE_ERROR: There was error with disk hardware" points to either a hard drive or an optical drive, assuming that flash drives are not in the equation.

"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" points in same direction.

I would check the connections on all...and then run hard drive diagnostics on appropriate drives used.

Louis




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users