Çözüldü DRIVER_VERIFIER_DMA_VIOLATION mavi ekran hatası

tanil gozdemir · 13 Aralık 2022

Genshin Impact oyunun ortasındayken DRIVER_VERIFIER_DMA_VIOLATION mavi ekran hatasını aldım. Ayrıca bu mavi ekran hatasını daha önce 2-3 kerede almıştım.

Minidump dosyası: 121322-15500-01.dmp

Sistemim: MSI GE67hx 12ugs.


Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Primary dump contents written successfully
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22000 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff806`4b600000 PsLoadedModuleList = 0xfffff806`4c229b00
Debug session time: Tue Dec 13 14:26:20.289 2022 (UTC + 3:00)
System Uptime: 0 days 2:15:03.897
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`4ba1afd0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff806`5175fed0=00000000000000e6
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: 0000000000000000, Device Object of faulting device.
Arg3: 00000000408abd79, Faulting information (usually faulting physical address).
Arg4: 0000000000000004, Fault type (hardware specific).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1468
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1500
Key : Analysis.IO.Other.Mb
Value: 3
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 3
Key : Analysis.Init.CPU.mSec
Value: 686
Key : Analysis.Init.Elapsed.mSec
Value: 23346
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Bugcheck.Code.DumpHeader
Value: 0xe6
Key : Bugcheck.Code.KiBugCheckData
Value: 0xe6
Key : Bugcheck.Code.Register
Value: 0xe6
Key : Dump.Attributes.AsUlong
Value: 1000
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 100
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
FILE_IN_CAB: MEMORY.DMP
DUMP_FILE_ATTRIBUTES: 0x1000
BUGCHECK_CODE: e6
BUGCHECK_P1: 26
BUGCHECK_P2: 0
BUGCHECK_P3: 408abd79
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
fffff806`5175fec8 fffff806`4bb2d581 : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`408abd79 : nt!KeBugCheckEx
fffff806`5175fed0 fffff806`4bb16a8b : fffff806`4c24bce0 fffff806`4c24bce0 00000000`00000000 fffff806`4b82f476 : nt!IvtHandleInterrupt+0x1d1
fffff806`5175ff20 fffff806`4b814600 : fffff806`4c2f80d0 fffff806`4c2f8180 00000000`00000001 fffff806`4b814600 : nt!HalpIommuInterruptRoutine+0x4b
fffff806`5175ff50 fffff806`4ba1cfec : fffff806`51750a70 fffff806`4c2f80d0 0000020f`00000000 fffff806`51744000 : nt!KiCallInterruptServiceRoutine+0xa0
fffff806`5175ff90 fffff806`4ba1d577 : 00000002`00000001 00000000`ffffffff 00000012`de641d9c ffffb681`00000000 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff806`517509f0 fffff806`4ba1fd4a : 00000000`00000000 fffff806`4c335bc0 ffffd78f`cc93b080 00000000`0000108c : nt!KiInterruptDispatchNoLock+0x37
fffff806`51750b80 00000000`00000000 : fffff806`51751000 fffff806`5174a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: nt!IvtHandleInterrupt+1d1
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1d1
FAILURE_BUCKET_ID: 0xE6_26_nt!IvtHandleInterrupt
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {11608481-d56e-58cc-4b64-17c92254d2f4}
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: 0000000000000000, Device Object of faulting device.
Arg3: 00000000408abd79, Faulting information (usually faulting physical address).
Arg4: 0000000000000004, Fault type (hardware specific).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1280
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1279
Key : Analysis.IO.Other.Mb
Value: 3
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 3
Key : Analysis.Init.CPU.mSec
Value: 2155
Key : Analysis.Init.Elapsed.mSec
Value: 24848
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Bugcheck.Code.DumpHeader
Value: 0xe6
Key : Bugcheck.Code.KiBugCheckData
Value: 0xe6
Key : Bugcheck.Code.Register
Value: 0xe6
Key : Dump.Attributes.AsUlong
Value: 1000
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 100
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
FILE_IN_CAB: MEMORY.DMP
DUMP_FILE_ATTRIBUTES: 0x1000
BUGCHECK_CODE: e6
BUGCHECK_P1: 26
BUGCHECK_P2: 0
BUGCHECK_P3: 408abd79
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
fffff806`5175fec8 fffff806`4bb2d581 : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`408abd79 : nt!KeBugCheckEx
fffff806`5175fed0 fffff806`4bb16a8b : fffff806`4c24bce0 fffff806`4c24bce0 00000000`00000000 fffff806`4b82f476 : nt!IvtHandleInterrupt+0x1d1
fffff806`5175ff20 fffff806`4b814600 : fffff806`4c2f80d0 fffff806`4c2f8180 00000000`00000001 fffff806`4b814600 : nt!HalpIommuInterruptRoutine+0x4b
fffff806`5175ff50 fffff806`4ba1cfec : fffff806`51750a70 fffff806`4c2f80d0 0000020f`00000000 fffff806`51744000 : nt!KiCallInterruptServiceRoutine+0xa0
fffff806`5175ff90 fffff806`4ba1d577 : 00000002`00000001 00000000`ffffffff 00000012`de641d9c ffffb681`00000000 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff806`517509f0 fffff806`4ba1fd4a : 00000000`00000000 fffff806`4c335bc0 ffffd78f`cc93b080 00000000`0000108c : nt!KiInterruptDispatchNoLock+0x37
fffff806`51750b80 00000000`00000000 : fffff806`51751000 fffff806`5174a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: nt!IvtHandleInterrupt+1d1
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1d1
FAILURE_BUCKET_ID: 0xE6_26_nt!IvtHandleInterrupt
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {11608481-d56e-58cc-4b64-17c92254d2f4}
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DMA_VIOLATION (e6)
An illegal DMA operation was attempted by a driver being verified.
Arguments:
Arg1: 0000000000000026, IOMMU detected DMA violation.
Arg2: 0000000000000000, Device Object of faulting device.
Arg3: 00000000408abd79, Faulting information (usually faulting physical address).
Arg4: 0000000000000004, Fault type (hardware specific).
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1250
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1254
Key : Analysis.IO.Other.Mb
Value: 3
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 3
Key : Analysis.Init.CPU.mSec
Value: 3437
Key : Analysis.Init.Elapsed.mSec
Value: 26128
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Bugcheck.Code.DumpHeader
Value: 0xe6
Key : Bugcheck.Code.KiBugCheckData
Value: 0xe6
Key : Bugcheck.Code.Register
Value: 0xe6
Key : Dump.Attributes.AsUlong
Value: 1000
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 100
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
FILE_IN_CAB: MEMORY.DMP
DUMP_FILE_ATTRIBUTES: 0x1000
BUGCHECK_CODE: e6
BUGCHECK_P1: 26
BUGCHECK_P2: 0
BUGCHECK_P3: 408abd79
BUGCHECK_P4: 4
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
fffff806`5175fec8 fffff806`4bb2d581 : 00000000`000000e6 00000000`00000026 00000000`00000000 00000000`408abd79 : nt!KeBugCheckEx
fffff806`5175fed0 fffff806`4bb16a8b : fffff806`4c24bce0 fffff806`4c24bce0 00000000`00000000 fffff806`4b82f476 : nt!IvtHandleInterrupt+0x1d1
fffff806`5175ff20 fffff806`4b814600 : fffff806`4c2f80d0 fffff806`4c2f8180 00000000`00000001 fffff806`4b814600 : nt!HalpIommuInterruptRoutine+0x4b
fffff806`5175ff50 fffff806`4ba1cfec : fffff806`51750a70 fffff806`4c2f80d0 0000020f`00000000 fffff806`51744000 : nt!KiCallInterruptServiceRoutine+0xa0
fffff806`5175ff90 fffff806`4ba1d577 : 00000002`00000001 00000000`ffffffff 00000012`de641d9c ffffb681`00000000 : nt!KiInterruptSubDispatchNoLock+0x11c
fffff806`517509f0 fffff806`4ba1fd4a : 00000000`00000000 fffff806`4c335bc0 ffffd78f`cc93b080 00000000`0000108c : nt!KiInterruptDispatchNoLock+0x37
fffff806`51750b80 00000000`00000000 : fffff806`51751000 fffff806`5174a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: nt!IvtHandleInterrupt+1d1
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1d1
FAILURE_BUCKET_ID: 0xE6_26_nt!IvtHandleInterrupt
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {11608481-d56e-58cc-4b64-17c92254d2f4}
Followup: MachineOwner
---------

claus · 13 Aralık 2022

Dosyaya baktım. Donanımsal bir sorun görünmüyor. NVIDIA sürücüleri sorunlu bu aralar. Test amaçlı 2-3 eski sürücü sürümü ile dener misin?

tanil gozdemir · 14 Aralık 2022

Deneyip yine bir mavi ekran hatasıyla karşılaşırsam yazarım.

claus · 14 Aralık 2022

Karşılaşmazsanızda yazın

Her durumda son durumu mutlaka bildirin.

tanil gozdemir · 17 Aralık 2022

Şu anlık bir sorun yok ama bu aralar finaller yaklaştığı için pek oyun oynayamadığım için son durumu yazmamıştım.

claus · 17 Aralık 2022

O halde çözüldü olarak işaretleyin konuyu

talhaberk55 · 22 Ağustos 2023

Claus benim Windows açılmıyor sonra otomatik onarım hazırlanırken bu konuda ki mavi ekranı veriyor yani pc açılmıyor.

claus · 22 Ağustos 2023

talhaberk55 dedi:
Claus benim Windows açılmıyor sonra otomatik onarım hazırlanırken bu konuda ki mavi ekranı veriyor yani pc açılmıyor.

Yeni konu aç ve beni etiketle inceleylim.

Abdullah1369 · 15 Eylül 2023

claus dedi:
Yeni konu aç ve beni etiketle inceleylim.

Merhaba, bende de yeniden başlatıyor kısmında ekran gelmiyor, aynı hata, bir çözüm bulabiliriz mi acaba?

claus · 16 Eylül 2023

Abdullah1369 dedi:
Merhaba, bende de yeniden başlatıyor kısmında ekran gelmiyor, aynı hata, bir çözüm bulabiliriz mi acaba?

Yeni konu açmalısın.

Çözüldü DRIVER_VERIFIER_DMA_VIOLATION mavi ekran hatası

Ayrıntılı düzenleme

tanil gozdemir

Kilopat

claus

claus

Zettapat

tanil gozdemir

Kilopat

claus

Zettapat

tanil gozdemir

Kilopat

claus

Zettapat

talhaberk55

Centipat

claus

Zettapat

Abdullah1369

Zeptopat

claus

Zettapat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz