thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Częste Blue Screen-y
Następny ma wspólny mianownik, problem z PFN (Page Frame Number). Ogólnie dalej problem z zarządzanie pamięci wirtualnej w systemie.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c: \symbols*http: //msdl.microsoft.com/download/symbols;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
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c5ee90
Debug session time: Fri Feb 6 21: 39: 46.606 2015 (UTC + 1: 00)
System Uptime: 0 days 0: 02: 28.027
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa800f77fd80, 2, 0, fffff80002b4125f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
Followup: MachineOwner
---------
1: kd> !analyze -v
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa800f77fd80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002b4125f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cca0e8
fffffa800f77fd80
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiIdentifyPfn+23f
fffff800`02b4125f 4c8b7500 mov r14,qword ptr [rbp]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
TRAP_FRAME: fffff8800b66e4e0 -- (.trap 0xfffff8800b66e4e0)
.trap 0xfffff8800b66e4e0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0800000000000020
rdx=000000000006107d rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002b4125f rsp=fffff8800b66e670 rbp=fffffa800f77fd80
r8=00000000000678be r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MiIdentifyPfn+0x23f:
fffff800`02b4125f 4c8b7500 mov r14,qword ptr [rbp] ss: 0018: fffffa80`0f77fd80=??
.trap
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a98be9 to fffff80002a99640
STACK_TEXT:
fffff880`0b66e398 fffff800`02a98be9 : 00000000`0000000a fffffa80`0f77fd80 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b66e3a0 fffff800`02a97860 : 00000000`42506650 00000000`00000000 00000000`00000000 02000000`000733fd : nt!KiBugCheckDispatch+0x69
fffff880`0b66e4e0 fffff800`02b4125f : 00000000`00000100 02000000`000716db 00000000`42506600 fffff800`02d84c8f : nt!KiPageFault+0x260
fffff880`0b66e670 fffff800`02b41f3b : 00000000`00000000 00000000`00000004 fffffa80`071b5328 fffffa80`071b5000 : nt!MiIdentifyPfn+0x23f
fffff880`0b66e710 fffff800`02ea7c05 : fffffa80`071b5000 fffff880`0b66eca0 fffff880`0b66e7e8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`0b66e750 fffff800`02de9de8 : 00000000`00000006 00000000`00000000 fffffa80`071b5000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`0b66e7a0 fffff800`02da30d3 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`02aa1101 : nt! ? : NNGAKEGL: `string'+0x48fbd
fffff880`0b66e830 fffff800`02da3949 : 00000000`0202b8c8 00000000`0000088e 00000000`0202b920 00000000`070a37b8 : nt!ExpQuerySystemInformation+0x1193
fffff880`0b66ebe0 fffff800`02a988d3 : 00000000`00000000 00000000`07ab2ff8 00000000`04d39e01 00000000`046a6e60 : nt!NtQuerySystemInformation+0x4d
fffff880`0b66ec20 00000000`76df167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0202b7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76df167a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiIdentifyPfn+23f
fffff800`02b4125f 4c8b7500 mov r14,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiIdentifyPfn+23f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
BUCKET_ID: X64_0xA_nt!MiIdentifyPfn+23f
Followup: MachineOwner
Dwa ostatnie bsody mają kody 0x50 czyli ten co na początku więc tylko przejrzałem i są podobne.
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
(Ten post był ostatnio modyfikowany: 07.02.2015 11:06 przez thermalfake.)
07.02.2015 10:52
|
Post: #3
