Wątek zamknięty

BSOD: problem związany z plikiem ntoskrnl.exe

 
thermalfake
Ostatni Mohikanin

Liczba postów: 13.580
Post: #10

RE: BSOD: problem związany z plikiem ntoskrnl.exe


Zbyt krótki memtest.

To nie jest problem sterownika grafiki bo problem pokazuje się przy innych driverach choćby nvstor64 (nvidia storage driver - chipset). Albo masz uszkodzoną pamięć czego memtest wcale nie musi wykryć albo masz jakiegoś krecika w systemie który odwala taką robotę, że odwołanie konkretnego sterownika do pamięci ram (ramki w konkretnym segmencie w którym wcześniej jakieś informacje zapisał) jest już niewłaściwe.
Sprawdź przede wszystkim czy sterowniki są podpisane (w wierszu poleceń -> Sigverif.exe) w dalszej kolejności uaktualnij wszystkie i pozbądź się tego programu AV.

nvlddmkm


Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1:  fffff880024da818, memory referenced
Arg2:  0000000000000005, IRQL
Arg3:  0000000000000000, value 0 = read operation, 1 = write operation
Arg4:  fffff8800f28a40a, address which referenced memory

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


READ_ADDRESS:   fffff880024da818

CURRENT_IRQL:   5

FAULTING_IP:  
nvlddmkm+1ca40a
fffff880`0f28a40a ff9718180000    call    qword ptr [rdi+1818h]

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xD1

PROCESS_NAME:   System

TRAP_FRAME:   fffff88002f1b620 -- (.trap 0xfffff88002f1b620)
NOTE:  The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003da6000 rbx=0000000000000000 rcx=fffff880024d9000
rdx=0000000000000003 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800f28a40a rsp=fffff88002f1b7b0 rbp=fffff88002f1b7d0
r8=0000000000000000  r9=0000000000000000 r10=0000000000000002
r11=fffffa8003da6000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nvlddmkm+0x1ca40a:
fffff880`0f28a40a ff9718180000    call    qword ptr [rdi+1818h] ds: 9000: 00000000`00001818=?
Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff80002ac2b29 to fffff80002ac35c0

STACK_TEXT:  
fffff880`02f1b4d8 fffff800`02ac2b29 :  00000000`0000000a fffff880`024da818 00000000`00000005 00000000`00000000 :  nt!KeBugCheckEx
fffff880`02f1b4e0 fffff800`02ac17a0 :  fffffa80`04edb000 fffffa80`03da6000 fffff880`00000001 fffff880`02f1b8d0 :  nt!KiBugCheckDispatch+0x69
fffff880`02f1b620 fffff880`0f28a40a :  fffffa80`024d9000 00000000`00000001 fffffa80`024d9000 fffffa80`03866000 :  nt!KiPageFault+0x260
fffff880`02f1b7b0 fffffa80`024d9000 :  00000000`00000001 fffffa80`024d9000 fffffa80`03866000 fffff880`02f1b800 :  nvlddmkm+0x1ca40a
fffff880`02f1b7b8 00000000`00000001 :  fffffa80`024d9000 fffffa80`03866000 fffff880`02f1b800 fffff880`0f2fca59 :  0xfffffa80`024d9000
fffff880`02f1b7c0 fffffa80`024d9000 :  fffffa80`03866000 fffff880`02f1b800 fffff880`0f2fca59 fffffa80`024d9000 :  0x1
fffff880`02f1b7c8 fffffa80`03866000 :  fffff880`02f1b800 fffff880`0f2fca59 fffffa80`024d9000 fffffa80`024d9000 :  0xfffffa80`024d9000
fffff880`02f1b7d0 fffff880`02f1b800 :  fffff880`0f2fca59 fffffa80`024d9000 fffffa80`024d9000 fffffa80`024d9000 :  0xfffffa80`03866000
fffff880`02f1b7d8 fffff880`0f2fca59 :  fffffa80`024d9000 fffffa80`024d9000 fffffa80`024d9000 fffffa80`03866000 :  0xfffff880`02f1b800
fffff880`02f1b7e0 fffffa80`024d9000 :  fffffa80`024d9000 fffffa80`024d9000 fffffa80`03866000 fffff880`02f1b920 :  nvlddmkm+0x23ca59
fffff880`02f1b7e8 fffffa80`024d9000 :  fffffa80`024d9000 fffffa80`03866000 fffff880`02f1b920 fffff880`0f2641af :  0xfffffa80`024d9000
fffff880`02f1b7f0 fffffa80`024d9000 :  fffffa80`03866000 fffff880`02f1b920 fffff880`0f2641af fffffa80`024d9000 :  0xfffffa80`024d9000
fffff880`02f1b7f8 fffffa80`03866000 :  fffff880`02f1b920 fffff880`0f2641af fffffa80`024d9000 fffffa80`024d9000 :  0xfffffa80`024d9000
fffff880`02f1b800 fffff880`02f1b920 :  fffff880`0f2641af fffffa80`024d9000 fffffa80`024d9000 fffffa80`03cfc010 :  0xfffffa80`03866000
fffff880`02f1b808 fffff880`0f2641af :  fffffa80`024d9000 fffffa80`024d9000 fffffa80`03cfc010 00000000`00000000 :  0xfffff880`02f1b920
fffff880`02f1b810 fffffa80`024d9000 :  fffffa80`024d9000 fffffa80`03cfc010 00000000`00000000 00000000`00000000 :  nvlddmkm+0x1a41af
fffff880`02f1b818 fffffa80`024d9000 :  fffffa80`03cfc010 00000000`00000000 00000000`00000000 00000000`00000000 :  0xfffffa80`024d9000
fffff880`02f1b820 fffffa80`03cfc010 :  00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`024da818 :  0xfffffa80`024d9000
fffff880`02f1b828 00000000`00000000 :  00000000`00000000 00000000`00000000 fffffa80`024da818 fffffa80`024da9a8 :  0xfffffa80`03cfc010


STACK_COMMAND:   kb

FOLLOWUP_IP:  
nvlddmkm+1ca40a
fffff880`0f28a40a ff9718180000    call    qword ptr [rdi+1818h]

SYMBOL_STACK_INDEX:   3

SYMBOL_NAME:   nvlddmkm+1ca40a

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nvlddmkm

IMAGE_NAME:   nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   506b3099

FAILURE_BUCKET_ID:   X64_0xD1_nvlddmkm+1ca40a

BUCKET_ID:   X64_0xD1_nvlddmkm+1ca40a

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

Kod:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1:  fffff88068c17c10, memory referenced
Arg2:  0000000000000006, IRQL
Arg3:  0000000000000000, value 0 = read operation, 1 = write operation
Arg4:  fffff88001161c8c, address which referenced memory

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


READ_ADDRESS:  GetPointerFromAddress:  unable to read from fffff80002cf80e0
fffff88068c17c10

CURRENT_IRQL:   6

FAULTING_IP:  
nvstor64+1cc8c
fffff880`01161c8c 448b440c2c      mov     r8d,dword ptr [rsp+rcx+2Ch]

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xD1

PROCESS_NAME:   System

TRAP_FRAME:   fffff88002f1b770 -- (.trap 0xfffff88002f1b770)
NOTE:  The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000005173025 rbx=0000000000000000 rcx=0000000065cfc2e4
rdx=0000000005173025 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001161c8c rsp=fffff88002f1b900 rbp=0000000005173021
r8=00000000ffffffff  r9=fffffa8003392008 r10=fffffa8003392008
r11=fffff880031e5000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nvstor64+0x1cc8c:
fffff880`01161c8c 448b440c2c      mov     r8d,dword ptr [rsp+rcx+2Ch] ss: 0018: fffff880`68c17c10=?
Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff80002ac0b29 to fffff80002ac15c0

STACK_TEXT:  
fffff880`02f1b628 fffff800`02ac0b29 :  00000000`0000000a fffff880`68c17c10 00000000`00000006 00000000`00000000 :  nt!KeBugCheckEx
fffff880`02f1b630 fffff800`02abf7a0 :  00000000`00000000 fffffa80`03392008 00000000`00000000 00000000`00000000 :  nt!KiBugCheckDispatch+0x69
fffff880`02f1b770 fffff880`01161c8c :  00000008`00000008 00000003`00000008 0000000c`00000040 ffffffff`0000000c :  nt!KiPageFault+0x260
fffff880`02f1b900 00000008`00000008 :  00000003`00000008 0000000c`00000040 ffffffff`0000000c 00000040`00000000 :  nvstor64+0x1cc8c
fffff880`02f1b908 00000003`00000008 :  0000000c`00000040 ffffffff`0000000c 00000040`00000000 00000000`00000000 :  0x8`00000008
fffff880`02f1b910 0000000c`00000040 :  ffffffff`0000000c 00000040`00000000 00000000`00000000 00000001`00000000 :  0x3`00000008
fffff880`02f1b918 ffffffff`0000000c :  00000040`00000000 00000000`00000000 00000001`00000000 00000004`00000040 :  0xc`00000040
fffff880`02f1b920 00000040`00000000 :  00000000`00000000 00000001`00000000 00000004`00000040 00000004`00000004 :  0xffffffff`0000000c
fffff880`02f1b928 00000000`00000000 :  00000001`00000000 00000004`00000040 00000004`00000004 00000040`00000002 :  0x40`00000000


STACK_COMMAND:   kb

FOLLOWUP_IP:  
nvstor64+1cc8c
fffff880`01161c8c 448b440c2c      mov     r8d,dword ptr [rsp+rcx+2Ch]

SYMBOL_STACK_INDEX:   3

SYMBOL_NAME:   nvstor64+1cc8c

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nvstor64

IMAGE_NAME:   nvstor64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   48aa27a3

FAILURE_BUCKET_ID:   X64_0xD1_nvstor64+1cc8c

BUCKET_ID:   X64_0xD1_nvstor64+1cc8c

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

[Obrazek: 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.

15.12.2012 13:03

Znajdź wszystkie posty użytkownika
Wątek zamknięty


Wiadomości w tym wątku
RE: Blue Screen ntoskrnl.exe - obitoo - 11.12.2012, 15:55
RE: BSOD: problem związany z plikiem ntoskrnl.exe - thermalfake - 15.12.2012 13:03
Podobne wątki
Wątek: Autor Odpowiedzi: Wyświetleń: Ostatni post
BSOD Moloch4 0 692 05.07.2019 11:29
Ostatni post: Moloch4
BSOD Windows 7 luzbluzoner 0 1.181 17.12.2016 20:25
Ostatni post: luzbluzoner
Błąd związany z wydajnością Windowsa-dotyczy wuaueng.dll (1036) SUS20ClientDataStore dalback 0 890 16.11.2016 08:56
Ostatni post: dalback
Częsty ekrad BSOD kubajed 0 1.155 03.10.2016 17:46
Ostatni post: kubajed
problem z ntoskrnl.exe Arek101 0 1.473 26.05.2016 20:03
Ostatni post: Arek101
Rozwiązany -Windows 7 64-bit Problem z bluescreen'ami (BSOD) jacob776 6 3.586 04.12.2015 17:45
Ostatni post: jacob776
« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 1 głosów.