Çözüldü KMODE_EXCEPTION_NOT_HANDLED Mavi Ekran

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Durum
Mesaj gönderimine kapalı.

Tolgahan5

Hectopat
Katılım
30 Ocak 2019
Mesajlar
55
Çözümler
1
Mavi ekran hatası alıyorum. Minidump dosyalarını inceleyebilir misiniz? @Murat5038


  • M5A97 R2.0 Anakart
  • Nvidia GTX650 GPU
  • AMD-FX 8120 CPU
  • Hyperx Fury 2x4 GB DDR3 1600Mhz RAM
 
Son düzenleyen: Moderatör:
Kolay gelsin dosyadan anladığım kadarıyla driver veya özellikler ile ilgili sorun oluşmuş çok çıkan BSOD'lardanmış.
 
Öncelikle bütün konularınızı birleştirip size bir gün uyarı veriyorum.

Buradaki konuda bellekleriniz arızalı çıkmış: [Çözüm] Windows 10 Mavi Ekran Hatası | PAGE FAULT IN NONPAGED AREA - Technopat Sosyal

Bellekleri değiştirdiğinizi söylemişsiniz.

Şimdi adım adım gidelim:
  • Arızalı belleklerin marka/modeli neydi, yeni taktıklarınızın marka/modeli ne?
  • Ekran kartınızı OCCT ile test ettiniz mi?
  • Memtest86'yı ne kadar süre çalıştırdınız?
  • Yeni bellekleri test ettiniz mi? Etmediyseniz edip sonucu paylaşın.
  • PSU modeliniz nedir?
  • CPU soğutucunuz nedir?
  • En son ne zaman soğutucu temizliği ve macun değişimi yaptınız?
Ve bir daha yeni konu açmayın. Bu konudan devam edeceğiz.
 

1- Eskiler: Corsair XMS3 2x4GB DDR3 1066mhz
Yeniler: Hyperx Fury Black 2x4GB DDR3 1600mhz

2- OCCT bilgisayarı aşırı kastırdı tam olarak anlayamadım programı.

3- Tüm işlem bitene kadar ben dokunmadım kendisi işini bitirince resetledi.

4- Ettim.

5- AeroCool VP-550 550W

6- İşlemciyle beraber gelen soğutucu. Modelini bilmiyorum.

7- Kasa temiz ve termal macun da yeni.
 

Dosya Ekleri

  • Screenshot_20191028-234402_Gallery.jpg
    Screenshot_20191028-234402_Gallery.jpg
    59,3 KB · Görüntüleme: 32
  • Screenshot_20191028-234334_Gallery.jpg
    Screenshot_20191028-234334_Gallery.jpg
    142,5 KB · Görüntüleme: 28
  • Screenshot_20191028-234348_Gallery.jpg
    Screenshot_20191028-234348_Gallery.jpg
    85,1 KB · Görüntüleme: 35
Son düzenleme:
2- OCCT bilgisayarı aşırı kastırdı tam olarak anlayamadım programı.
Normal çünkü sistemi stres testine sokuyorsunuz. Yazılım ne kadar çalıştı, çalışırken mavi ekran aldınız mı?

Gönderdiğiniz dökümlerde ekran kartı hatası var. Kartınızda arıza olabilir.
Kod:
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: 0000000200010018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88011726f2a, address which referenced memory

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800040b4300

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-K01TCKK

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 58

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  d1

BUGCHECK_P1: 200010018

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff88011726f2a

READ_ADDRESS: fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800040b42f0
GetUlongPtrFromAddress: unable to read from fffff800040b44a8
 0000000200010018

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880064457a0 -- (.trap 0xfffff880064457a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000200010000 rbx=0000000000000000 rcx=fffff8801177d2b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011726f2a rsp=fffff88006445938 rbp=fffff88006445a40
 r8=00000000200180c0  r9=0000000000000586 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x726f2a:
fffff880`11726f2a 4c8b5018        mov     r10,qword ptr [rax+18h] ds:00000002`00010018=????????????????
Resetting default scope

STACK_TEXT: 
fffff880`06445658 fffff800`03eb90e9 : 00000000`0000000a 00000002`00010018 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`06445660 fffff800`03eb6ece : 00000000`00000000 00000002`00010018 fffff880`04320000 fffff880`1177d2b0 : nt!KiBugCheckDispatch+0x69
fffff880`064457a0 fffff880`11726f2a : fffff880`11736a0b fffffa80`07bf9218 00000000`00000002 00000001`000b3988 : nt!KiPageFault+0x44e
fffff880`06445938 fffff880`11736a0b : fffffa80`07bf9218 00000000`00000002 00000001`000b3988 00000001`000b3988 : nvlddmkm+0x726f2a
fffff880`06445940 fffffa80`07bf9218 : 00000000`00000002 00000001`000b3988 00000001`000b3988 00000001`000b3988 : nvlddmkm+0x736a0b
fffff880`06445948 00000000`00000002 : 00000001`000b3988 00000001`000b3988 00000001`000b3988 fffff880`04347c01 : 0xfffffa80`07bf9218
fffff880`06445950 00000001`000b3988 : 00000001`000b3988 00000001`000b3988 fffff880`04347c01 00000000`00000070 : 0x2
fffff880`06445958 00000001`000b3988 : 00000001`000b3988 fffff880`04347c01 00000000`00000070 00000000`00000000 : 0x00000001`000b3988
fffff880`06445960 00000001`000b3988 : fffff880`04347c01 00000000`00000070 00000000`00000000 00000000`00000000 : 0x00000001`000b3988
fffff880`06445968 fffff880`04347c01 : 00000000`00000070 00000000`00000000 00000000`00000000 fffffa80`0a543008 : 0x00000001`000b3988
fffff880`06445970 00000000`00000070 : 00000000`00000000 00000000`00000000 fffffa80`0a543008 00000001`00000000 : 0xfffff880`04347c01
fffff880`06445978 00000000`00000000 : 00000000`00000000 fffffa80`0a543008 00000001`00000000 00000000`00000002 : 0x70


SYMBOL_NAME:  nvlddmkm+726f2a

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+726f2a

OS_VERSION:  7.1.7601.24520

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {8d509315-4c9c-f5da-6008-c2aae7c38965}

Followup:     MachineOwner
---------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002b60b1e, The address that the exception occurred at
Arg3: fffff88003b4b598, Exception Record Address
Arg4: fffff88003b4ae00, Context Record Address

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

fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800040f3300

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-K01TCKK

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 5

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 60

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff88002b60b1e

BUGCHECK_P3: fffff88003b4b598

BUGCHECK_P4: fffff88003b4ae00

EXCEPTION_RECORD:  fffff88003b4b598 -- (.exr 0xfffff88003b4b598)
ExceptionAddress: fffff88002b60b1e (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x0000000000000eca)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT:  fffff88003b4ae00 -- (.cxr 0xfffff88003b4ae00)
rax=fffff88002a6ba48 rbx=0000000000000000 rcx=000000000000001d
rdx=000000000000002c rsi=fffffa800a4d32c0 rdi=fffffa8009f3d000
rip=fffff88002b60b1e rsp=fffff88003b4b7d0 rbp=fffffa800a3290e8
 r8=00000000000000fd  r9=0000000000000009 r10=0000000000000000
r11=fffffa8009f3e3f0 r12=000000000000001d r13=0000000000000000
r14=fffffa800a4de8e0 r15=000000000000001d
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xeca:
fffff880`02b60b1e 0033            add     byte ptr [rbx],dh ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

WRITE_ADDRESS: fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800040f32f0
GetUlongPtrFromAddress: unable to read from fffff800040f34a8
 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

MISALIGNED_IP:
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+eca
fffff880`02b60b1e 0033            add     byte ptr [rbx],dh

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
fffff880`03b4b7d0 fffff880`02b7a8b1 : 00000000`00000000 fffff8a0`021fe350 fffffa80`00000000 fffffa80`0a4de8e0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xeca
fffff880`03b4b9a0 fffff880`02b7a5ec : fffff880`02b7a014 00000000`00000000 fffffa80`00000000 fffffa80`0000002c : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03b4bb90 fffff880`02b7a0ea : 00000000`00000000 fffffa80`0a7a9850 00000000`00000080 fffffa80`09ee5010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03b4bbc0 fffff800`04196578 : 00000000`01a026a1 fffff800`0403a180 00000000`00000001 fffffa80`09f20060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03b4bc00 fffff800`03eefcc6 : fffff800`0403a180 fffffa80`09f20060 fffff800`0404a1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`03b4bc40 00000000`00000000 : fffff880`03b4c000 fffff880`03b46000 fffff880`03b4b540 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+eca

IMAGE_NAME:  hardware

IMAGE_VERSION:  6.1.7601.24513

STACK_COMMAND:  .cxr 0xfffff88003b4ae00 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

OS_VERSION:  7.1.7601.24520

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {9d092e7f-b602-fc7d-b143-ab40a5d1b66d}

Followup:     MachineOwner
---------
 
Normal çünkü sistemi stres testine sokuyorsunuz. Yazılım ne kadar çalıştı, çalışırken mavi ekran aldınız mı?

Gönderdiğiniz dökümlerde ekran kartı hatası var. Kartınızda arıza olabilir.
Kod:
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: 0000000200010018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88011726f2a, address which referenced memory

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

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800040b4300

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-K01TCKK

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 58

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  d1

BUGCHECK_P1: 200010018

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff88011726f2a

READ_ADDRESS: fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
fffff80003ff90e8: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800040b42f0
GetUlongPtrFromAddress: unable to read from fffff800040b44a8
 0000000200010018

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880064457a0 -- (.trap 0xfffff880064457a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000200010000 rbx=0000000000000000 rcx=fffff8801177d2b0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88011726f2a rsp=fffff88006445938 rbp=fffff88006445a40
 r8=00000000200180c0  r9=0000000000000586 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x726f2a:
fffff880`11726f2a 4c8b5018        mov     r10,qword ptr [rax+18h] ds:00000002`00010018=????????????????
Resetting default scope

STACK_TEXT: 
fffff880`06445658 fffff800`03eb90e9 : 00000000`0000000a 00000002`00010018 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`06445660 fffff800`03eb6ece : 00000000`00000000 00000002`00010018 fffff880`04320000 fffff880`1177d2b0 : nt!KiBugCheckDispatch+0x69
fffff880`064457a0 fffff880`11726f2a : fffff880`11736a0b fffffa80`07bf9218 00000000`00000002 00000001`000b3988 : nt!KiPageFault+0x44e
fffff880`06445938 fffff880`11736a0b : fffffa80`07bf9218 00000000`00000002 00000001`000b3988 00000001`000b3988 : nvlddmkm+0x726f2a
fffff880`06445940 fffffa80`07bf9218 : 00000000`00000002 00000001`000b3988 00000001`000b3988 00000001`000b3988 : nvlddmkm+0x736a0b
fffff880`06445948 00000000`00000002 : 00000001`000b3988 00000001`000b3988 00000001`000b3988 fffff880`04347c01 : 0xfffffa80`07bf9218
fffff880`06445950 00000001`000b3988 : 00000001`000b3988 00000001`000b3988 fffff880`04347c01 00000000`00000070 : 0x2
fffff880`06445958 00000001`000b3988 : 00000001`000b3988 fffff880`04347c01 00000000`00000070 00000000`00000000 : 0x00000001`000b3988
fffff880`06445960 00000001`000b3988 : fffff880`04347c01 00000000`00000070 00000000`00000000 00000000`00000000 : 0x00000001`000b3988
fffff880`06445968 fffff880`04347c01 : 00000000`00000070 00000000`00000000 00000000`00000000 fffffa80`0a543008 : 0x00000001`000b3988
fffff880`06445970 00000000`00000070 : 00000000`00000000 00000000`00000000 fffffa80`0a543008 00000001`00000000 : 0xfffff880`04347c01
fffff880`06445978 00000000`00000000 : 00000000`00000000 fffffa80`0a543008 00000001`00000000 00000000`00000002 : 0x70


SYMBOL_NAME:  nvlddmkm+726f2a

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_0xD1_nvlddmkm+726f2a

OS_VERSION:  7.1.7601.24520

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {8d509315-4c9c-f5da-6008-c2aae7c38965}

Followup:     MachineOwner
---------
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88002b60b1e, The address that the exception occurred at
Arg3: fffff88003b4b598, Exception Record Address
Arg4: fffff88003b4ae00, Context Record Address

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

fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff800040f3300

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Write

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-K01TCKK

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 5

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 60

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff88002b60b1e

BUGCHECK_P3: fffff88003b4b598

BUGCHECK_P4: fffff88003b4ae00

EXCEPTION_RECORD:  fffff88003b4b598 -- (.exr 0xfffff88003b4b598)
ExceptionAddress: fffff88002b60b1e (dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x0000000000000eca)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000

CONTEXT:  fffff88003b4ae00 -- (.cxr 0xfffff88003b4ae00)
rax=fffff88002a6ba48 rbx=0000000000000000 rcx=000000000000001d
rdx=000000000000002c rsi=fffffa800a4d32c0 rdi=fffffa8009f3d000
rip=fffff88002b60b1e rsp=fffff88003b4b7d0 rbp=fffffa800a3290e8
 r8=00000000000000fd  r9=0000000000000009 r10=0000000000000000
r11=fffffa8009f3e3f0 r12=000000000000001d r13=0000000000000000
r14=fffffa800a4de8e0 r15=000000000000001d
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xeca:
fffff880`02b60b1e 0033            add     byte ptr [rbx],dh ds:002b:00000000`00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

WRITE_ADDRESS: fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
fffff800040380e8: Unable to get Flags value from nt!KdVersionBlock
Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff800040f32f0
GetUlongPtrFromAddress: unable to read from fffff800040f34a8
 0000000000000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000000

MISALIGNED_IP:
dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+eca
fffff880`02b60b1e 0033            add     byte ptr [rbx],dh

EXCEPTION_STR:  0xc0000005

STACK_TEXT: 
fffff880`03b4b7d0 fffff880`02b7a8b1 : 00000000`00000000 fffff8a0`021fe350 fffffa80`00000000 fffffa80`0a4de8e0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xeca
fffff880`03b4b9a0 fffff880`02b7a5ec : fffff880`02b7a014 00000000`00000000 fffffa80`00000000 fffffa80`0000002c : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03b4bb90 fffff880`02b7a0ea : 00000000`00000000 fffffa80`0a7a9850 00000000`00000080 fffffa80`09ee5010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03b4bbc0 fffff800`04196578 : 00000000`01a026a1 fffff800`0403a180 00000000`00000001 fffffa80`09f20060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03b4bc00 fffff800`03eefcc6 : fffff800`0403a180 fffffa80`09f20060 fffff800`0404a1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`03b4bc40 00000000`00000000 : fffff880`03b4c000 fffff880`03b46000 fffff880`03b4b540 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+eca

IMAGE_NAME:  hardware

IMAGE_VERSION:  6.1.7601.24513

STACK_COMMAND:  .cxr 0xfffff88003b4ae00 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_dxgmms1.sys

OS_VERSION:  7.1.7601.24520

BUILDLAB_STR:  win7sp1_ldr_escrow

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {9d092e7f-b602-fc7d-b143-ab40a5d1b66d}

Followup:     MachineOwner
---------
OCCT'yi ne kadar süre çalıştırmam gerekiyor?
 
Durum
Mesaj gönderimine kapalı.

Yeni konular

Geri
Yukarı