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.
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
DISK_HARDWARE_ERROR: There was error with disk hardware
Cytat:również sprawdzałem błędy na dysku ale nic nie znalazło.
Nie wiem czym i jak robiłeś diagnostykę dysku twardego ale ten błąd dotyczy właśnie jego lub kontrolera dysku na płycie głównej.
STATUS_DEVICE_NOT_CONNECTED
Może być chwilowy zanik zasilania dla dysku bądź samoistne wyłaczenie, uszkodzony dysk twardy powierzchniowo, złe parametry smart, chwilowe niewykrywanie przez bios, uszkodzona taśma sygnałowa sata/uszkodzone złącze/przejściówka jako, że to lapek.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp22\110211-34663-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`0324c670
Debug session time: Wed Nov 2 23: 01: 46.833 2011 (UTC + 2: 00)
System Uptime: 0 days 11: 17: 57.004
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fb80000000, ffffffffc000009d, 759c7880, fffff70000000000}
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+37bba )
Followup: MachineOwner
---------
2: 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: fffff6fb80000000, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 00000000759c7880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff70000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR: 0x7a_c000009d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff880035a15c0 -- (.trap 0xfffff880035a15c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=fffff880035a1780
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003395fe9 rsp=fffff880035a1750 rbp=000007fffffdffff
r8=fffff70001080040 r9=0000000000000009 r10=8000000000000000
r11=fffffa8003606040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiFindEmptyAddressRange+0xc9:
fffff800`03395fe9 a10000000000f7ffff mov eax,dword ptr [FFFFF70000000000h] ds: fcec: fffff700`00000000=00000000
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800030f4b52 to fffff80003083c40
STACK_TEXT:
fffff880`035a12e8 fffff800`030f4b52 : 00000000`0000007a fffff6fb`80000000 ffffffff`c000009d 00000000`759c7880 : nt!KeBugCheckEx
fffff880`035a12f0 fffff800`030ab6cf : fffffa80`03e3d010 fffff880`035a1420 fffffa80`036063d8 fffff880`05ab8d3b : nt! ? : FNODOBFM: `string'+0x37bba
fffff880`035a13d0 fffff800`0309202a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`0107d010 : nt!MiIssueHardFault+0x28b
fffff880`035a1460 fffff800`03081d6e : 00000000`00000000 fffff700`00000000 00000000`00000000 ffffffff`ffffffff : nt!MmAccessFault+0x146a
fffff880`035a15c0 fffff800`03395fe9 : 00000000`00000006 00000000`00000001 00000000`0065b710 fffff880`05c07256 : nt!KiPageFault+0x16e
fffff880`035a1750 fffff800`0337be25 : ffffffff`ffffffff ffffffff`ffffffff fffff880`035a1a50 00000000`00001000 : nt!MiFindEmptyAddressRange+0xc9
fffff880`035a17c0 fffff800`03082ed3 : ffffffff`ffffffff fffff880`035a1ba0 00000000`00000001 fffff880`035a1ba8 : nt!NtAllocateVirtualMemory+0x6d5
fffff880`035a1960 fffff800`0307f470 : fffff800`034b35b3 00000000`00000000 00000000`00000000 fffff800`032242b8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`035a1b68 fffff800`034b35b3 : 00000000`00000000 00000000`00000000 fffff800`032242b8 00000000`00000000 : nt!KiServiceLinkage
fffff880`035a1b70 fffff800`034b3e23 : fffffa80`c000a082 fffff800`00000001 fffff800`00000001 fffff880`035a1cc0 : nt!ExRaiseHardError+0xe3
fffff880`035a1c70 fffff800`0308e001 : fffff800`034b3db0 fffff800`0337a901 fffffa80`09456518 fffffa80`0361cb60 : nt!IopHardErrorThread+0x73
fffff880`035a1cb0 fffff800`0331efee : 00000000`00000000 fffffa80`0361cb60 00000000`00000080 fffffa80`03606040 : nt!ExpWorkerThread+0x111
fffff880`035a1d40 fffff800`030755e6 : fffff880`033d5180 fffffa80`0361cb60 fffff880`033dffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035a1d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+37bba
fffff800`030f4b52 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+37bba
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_: FNODOBFM: _string_+37bba
BUCKET_ID: X64_0x7a_c000009d_nt!_??_: FNODOBFM: _string_+37bba
Followup: MachineOwner
---------
Drugi
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp22\032811-30576-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap: Add: ignoring zero-sized range at ?fffff800`0472b500?
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Mon Mar 28 20: 02: 21.727 2011 (UTC + 2: 00)
System Uptime: 0 days 3: 54: 11.522
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80087909f0, fffff8000472b518, fffffa8008ae5820}
Probably caused by : swenum.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: fffffa80087909f0, Physical Device Object of the stack
Arg3: fffff8000472b518, Functional Device Object of the stack
Arg4: fffffa8008ae5820, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: swenum.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bca92
MODULE_NAME: swenum
FAULTING_MODULE: fffff8800665f000 swenum
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`0472b4c8 fffff800`02f3a273 : 00000000`0000009f 00000000`00000003 fffffa80`087909f0 fffff800`0472b518 : nt!KeBugCheckEx
fffff800`0472b4d0 fffff800`02ed729e : fffff800`0472b648 fffff800`0472b648 00000000`00000002 00000000`00000000 : nt! ? : FNODOBFM: `string'+0x292b0
fffff800`0472b570 fffff800`02ed6dd6 : fffffa80`089a0768 fffffa80`089a0768 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`0472b5e0 fffff800`02ed74be : 00000020`b75c1c79 fffff800`0472bc58 00000000`000dbe7c fffff800`03049208 : nt!KiProcessExpiredTimerList+0xc6
fffff800`0472bc30 fffff800`02ed6cb7 : 00000007`a6f551c6 00000007`000dbe7c 00000007`a6f5517d 00000000`0000007c : nt!KiTimerExpiration+0x1be
fffff800`0472bcd0 fffff800`02ed3eea : fffff800`03045e80 fffff800`03053c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`0472bd80 00000000`00000000 : fffff800`0472c000 fffff800`04726000 fffff800`0472bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_asyncmac_IMAGE_swenum.sys
BUCKET_ID: X64_0x9F_3_asyncmac_IMAGE_swenum.sys
Followup: MachineOwner
---------
Post: #2![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
