VRay render mavi ekran problemi

mustafaturunc · 30 Eylül 2019

Renderın yaklaşık 5. dakikasında mavi ekran hatası almaktayız, sorunu çözemedik. Olay gunluk dosyasını ekte veriyorum. İlgilenir misiniz? Tesekkur ederim.

Kod:

Günlük Adı:    Application
Kaynak:        Windows Error Reporting
Tarih:         30.09.2019 13:03:47
Olay Kimliği:  1001
Görev Kategorisi:Yok
Düzey:         Bilgi
Anahtar sözcükler:Klasik
Kullanıcı:     Yok
Bilgisayar:    DESKTOP-43U0RBQ
Açıklama:
Hata demeti 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER, tür 0
Olay Adı: BlueScreen
Yanıt: Kullanılamıyor
Kabin Kimliği: f7e543e8-5fc8-4e76-ba40-99c4ade22962

Sorun imzası:
P1: 124
P2: 0
P3: ffffbc8f286b9028
P4: be000000
P5: 800400
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9:
P10:

İliştirilmiş dosyalar:
\\?\C:\WINDOWS\Minidump\093019-4578-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6109-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2134.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2135.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2153.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER21A2.tmp.txt

Bu dosyalar burada bulunabilir:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_35da2f9645c034e56e35b3b69ab486bd6421a8a6_00000000_cab_891e1038-c0fe-46e6-98eb-671897fe5312

Çözümleme simgesi:
Çözüm için yeniden denetleme: 0
Rapor Kimliği: cfcd5688-2909-4f80-8d9d-1a62799b5b52
Rapor Durumu: 268435456
Karma demeti:
Kabin Guid'i: 0
Olay Xml'si:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-30T10:03:47.927507200Z" />
    <EventRecordID>389</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-43U0RBQ</Computer>
    <Security />
  </System>
  <EventData>
    <Data>0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER</Data>
    <Data>0</Data>
    <Data>BlueScreen</Data>
    <Data>Kullanılamıyor</Data>
    <Data>f7e543e8-5fc8-4e76-ba40-99c4ade22962</Data>
    <Data>124</Data>
    <Data>0</Data>
    <Data>ffffbc8f286b9028</Data>
    <Data>be000000</Data>
    <Data>800400</Data>
    <Data>10_0_18362</Data>
    <Data>0_0</Data>
    <Data>256_1</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
\\?\C:\WINDOWS\Minidump\093019-4578-01.dmp
\\?\C:\WINDOWS\TEMP\WER-6109-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2134.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2135.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2153.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER21A2.tmp.txt</Data>
    <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_35da2f9645c034e56e35b3b69ab486bd6421a8a6_00000000_cab_891e1038-c0fe-46e6-98eb-671897fe5312</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>cfcd5688-2909-4f80-8d9d-1a62799b5b52</Data>
    <Data>268435456</Data>
    <Data>
    </Data>
    <Data>0</Data>
  </EventData>
</Event>

Kod:

Günlük Adı:    Application
Kaynak:        Disc Soft Lite Bus Service
Tarih:         30.09.2019 13:03:39
Olay Kimliği:  0
Görev Kategorisi:Yok
Düzey:         Bilgi
Anahtar sözcükler:Klasik
Kullanıcı:     Yok
Bilgisayar:    DESKTOP-43U0RBQ
Açıklama:
Disc Soft Lite Bus Service kaynağındaki 0 Olay Kimliği'nin açıklaması bulunamıyor. Bu olayı başlatan bileşen yerel bilgisayarınızda yüklü değil veya yükleme bozulmuş. Bileşeni yerel bilgisayara yükleyebilir veya yüklüyse onarabilirsiniz.

Olay başka bir bilgisayardan başlatıldıysa, olayla birlikte görüntüleme bilgileri kaydedilmiş olmalıdır.

Olayla birlikte aşağıdaki bilgiler eklendi:

Service started/resumed

Olay Xml'si:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Disc Soft Lite Bus Service" />
    <EventID Qualifiers="0">0</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-30T10:03:39.994120300Z" />
    <EventRecordID>388</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-43U0RBQ</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Service started/resumed</Data>
  </EventData>
</Event>

Recep Baltaş · 30 Eylül 2019

Minidump Dosyalarını Paylaşın

23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi...

www.technopat.net

mustafaturunc · 3 Ekim 2019

Sabah ofise geçince ilk işim bu dosyayı paylaşmak olacak, sağolun ilginiz için.

Mavi Ekran Hatası

Посмотреть и скачать с Яндекс Диска

yadi.sk

Likteki dosyada belirttiğiniz dosyalar mevcut birde, \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124 dosyasını da ilave ettim işinize yarayabilir. Kolay gelsin.

Recep Baltaş · 5 Ekim 2019

Bellek arızası gibi. Memtest86 ile test eder misiniz?

Memtest86 USB'den Çalışan RAM Test Programı

RAM'lerinizi test etmek için kullanabileceğiniz en kapsamlı yazılım Memtest86'dır. Aracı USB belleğe yazmak için: Bu video rehberde Memtest86 ile belleklerinizi nasıl test edeceğinizi öğrenebilirsiniz: Adım adım: Öncelikle yazılımı buradan indirin. UEFI desteği olmayan eski sistemler...

www.technopat.net

İşlemcinizde OC varsa kaldırın. BIOS güncel değilse güncelleyin.

Kod:

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffd78baa62b010, Virtual address for the attempted execute.
Arg2: 8a00000261e008e3, PTE contents.
Arg3: ffffa98ee815f0a0, (reserved)
Arg4: 0000000000000003, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 2

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

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  fc

BUGCHECK_P1: ffffd78baa62b010

BUGCHECK_P2: 8a00000261e008e3

BUGCHECK_P3: ffffa98ee815f0a0

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  ffffa98ee815f0a0 -- (.trap 0xffffa98ee815f0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffaf8161d8c180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffd78baa62b010 rsp=ffffa98ee815f238 rbp=fffff80305e47f88
 r8=0000000000000001  r9=0000000000000001 r10=ffffd78b988e13c0
r11=ffffd78ba569e9a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ffffd78b`aa62b010 06              ???
Resetting default scope

STACK_TEXT: 
ffffa98e`e815ee78 fffff803`060546a8 : 00000000`000000fc ffffd78b`aa62b010 8a000002`61e008e3 ffffa98e`e815f0a0 : nt!KeBugCheckEx
ffffa98e`e815ee80 fffff803`0604ec81 : 00000000`00000003 00000000`00000001 00000000`00000000 ffffa98e`e815efc0 : nt!MiCheckSystemNxFault+0x12952c
ffffa98e`e815eec0 fffff803`05e731fa : ffffd78b`a63c1d70 00000000`00000011 ffffa98e`e815f000 00000000`00000000 : nt!MiRaisedIrqlFault+0x12e871
ffffa98e`e815ef00 fffff803`05fcf120 : ffffd78b`a569eb90 fffff803`0a113c9d ffffd78b`a569e9a0 ffffd78b`98c159f0 : nt!MmAccessFault+0x48a
ffffa98e`e815f0a0 ffffd78b`aa62b010 : 00000000`00000000 ffffd78b`aa62b010 00000209`9417d0e0 ffffd78b`ad09dc02 : nt!KiPageFault+0x360
ffffa98e`e815f238 00000000`00000000 : ffffd78b`aa62b010 00000209`9417d0e0 ffffd78b`ad09dc02 ffffd78b`a74ef4c0 : 0xffffd78b`aa62b010


SYMBOL_NAME:  nt!MiCheckSystemNxFault+12952c

MODULE_NAME: nt

IMAGE_VERSION:  10.0.18362.356

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  12952c

FAILURE_BUCKET_ID:  0xFC_nt!MiCheckSystemNxFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a6ae5288-6b71-974a-9b09-23f14d998164}

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffbc8f286b9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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

fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock
fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock
fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock
fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock
fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock
fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock
fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock
fffff80611e293b8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 6

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

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffbc8f286b9028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  vrayneui.exe

STACK_TEXT: 
ffffe381`8484cc58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

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

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80015e3d0c3, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 2

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

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  a

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff80015e3d0c3

WRITE_ADDRESS: fffff800163723b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff800162293b8: Unable to get Flags value from nt!KdVersionBlock
fffff800162293b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  YandexDisk2.ex

TRAP_FRAME:  ffffd689ecdc71a0 -- (.trap 0xffffd689ecdc71a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000000c
rdx=00000000fffffffe rsi=0000000000000000 rdi=0000000000000000
rip=fffff80015e3d0c3 rsp=ffffd689ecdc7330 rbp=000000000000000c
 r8=0000000000002000  r9=0000000000000000 r10=000000000000000c
r11=ffffd689ecdc7540 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiSelectReadyThread+0xe3:
fffff800`15e3d0c3 0000            add     byte ptr [rax],al ds:00000000`00000000=??
Resetting default scope

MISALIGNED_IP:
nt!KiSelectReadyThread+e3
fffff800`15e3d0c3 0000            add     byte ptr [rax],al

STACK_TEXT: 
ffffd689`ecdc7058 fffff800`15fd2ee9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd689`ecdc7060 fffff800`15fcf22b : ffffd689`ecdc71b4 fffff800`00000000 00000000`00000000 ffffc3d1`bf861024 : nt!KiBugCheckDispatch+0x69
ffffd689`ecdc71a0 fffff800`15e3d0c3 : 00000000`00000000 00000000`00000000 ffffc3a2`c487b460 00000000`00000000 : nt!KiPageFault+0x46b
ffffd689`ecdc7330 fffff800`15e3e7d3 : 00000000`0000000d 00000000`fffffffe 00000001`ffffffff 00000000`00002000 : nt!KiSelectReadyThread+0xe3
ffffd689`ecdc73c0 fffff800`15e38ac4 : 00000000`00000001 ffffdc01`00000000 00000000`00000000 00000000`00000003 : nt!KiRemoveBoostThread+0x113
ffffd689`ecdc7430 fffff800`15e3869a : ffff9a82`00000000 00000000`00000000 00000000`000009c4 00000000`007da9ea : nt!ExpReleaseResourceExclusiveForThreadLite+0x364
ffffd689`ecdc74f0 ffffc3d1`bfbf433d : 00000000`00000000 00000000`00000001 00000000`00000000 ffffd689`ecdc7a80 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x8a
ffffd689`ecdc7550 ffffc3d1`bf95b18c : ffffc3a2`c487b400 00000000`00000000 ffffc3a2`00000000 00000000`00000001 : win32kbase!UserSessionSwitchLeaveCrit+0x5d
ffffd689`ecdc75d0 ffffc3d1`bf86138a : ffffc3a2`c487b460 ffffc3a2`c487b460 00000000`00000000 00000000`00000000 : win32kfull!LeaveEnterCrit::LeaveEnterCrit+0x10
ffffd689`ecdc7600 ffffc3d1`bf8619f5 : 00000000`00000000 ffffc3a2`c4870040 00000000`00000001 ffffd81d`00000000 : win32kfull!xxxRealSleepThread+0x28a
ffffd689`ecdc7730 ffffc3d1`bf85ae9e : ffffd689`ecdc7a80 00000000`00000000 00000000`00000000 ffffc3a2`c487b460 : win32kfull!xxxSleepThread2+0xb5
ffffd689`ecdc7780 ffffc3d1`bf859792 : ffffd689`ecdc79a8 ffff9a82`a49d8000 00000000`00000000 00000000`00000000 : win32kfull!xxxRealInternalGetMessage+0x135e
ffffd689`ecdc7960 fffff800`15fd2915 : ffff9a82`a49d8080 00007ff6`86d7e9f0 00000000`00000020 ffffd689`ecdc7a80 : win32kfull!NtUserGetMessage+0x92
ffffd689`ecdc7a00 00007ff8`b13c1164 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000c3`b453ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`b13c1164


SYMBOL_NAME:  win32kbase!UserSessionSwitchLeaveCrit+5d

MODULE_NAME: hardware

IMAGE_NAME:  hardware

IMAGE_VERSION:  10.0.18362.356

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  IP_MISALIGNED

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {201b0e5d-db2a-63d2-77be-8ce8ff234750}

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

claus · 6 Ekim 2019

Ek olarak Nvidia GPU güncelle. Deomontools kaldır.

VRay render mavi ekran problemi

Ayrıntılı düzenleme

mustafaturunc

Centipat

Recep Baltaş

Technopat

Minidump Dosyalarını Paylaşın

mustafaturunc

Centipat

Mavi Ekran Hatası

Recep Baltaş

Technopat

Memtest86 USB'den Çalışan RAM Test Programı

claus

Moderasyon Ekibi Üyesi

Benzer konular

Bu konuyu görüntüleyen kullanıcılar