Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa13748.34166\101620-8921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff800`66c00000 PsLoadedModuleList = 0xfffff800`6782a310
Debug session time: Fri Oct 16 07:40:27.884 2020 (UTC + 3:00)
System Uptime: 0 days 0:00:42.897
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`66ff45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff88a`123db830=000000000000000a
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: 0000000000000003, memory referenced
Arg2: 00000000000000ff, 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: fffff80067005d21, address which referenced memory
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2999
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 3030
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: a
BUGCHECK_P1: 3
BUGCHECK_P2: ff
BUGCHECK_P3: 0
BUGCHECK_P4: fffff80067005d21
READ_ADDRESS: fffff800678fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8006780f340: Unable to get Flags value from nt!KdVersionBlock
fffff8006780f340: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000003
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Discord.exe
TRAP_FRAME: fffff88a123db970 -- (.trap 0xfffff88a123db970)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000100000002
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80067005d21 rsp=fffff88a123dbb00 rbp=fffff88a123dbb80
r8=0000000000000000 r9=0000000077a21d2c r10=000000000000058c
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KiSystemServiceUser+0x21:
fffff800`67005d21 807b0300 cmp byte ptr [rbx+3],0 ds:00000000`00000003=??
Resetting default scope
STACK_TEXT:
fffff88a`123db828 fffff800`67006569 : 00000000`0000000a 00000000`00000003 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
fffff88a`123db830 fffff800`67002869 : 00000000`00000000 fffff800`00000000 ffffd100`a0940100 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff88a`123db970 fffff800`67005d21 : ffffe307`8fb83440 ffffe307`8fb7a080 00000000`00000000 fffff88a`123dbb80 : nt!KiPageFault+0x469
fffff88a`123dbb00 00000000`779a1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceUser+0x21
00000000`0fcfeda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779a1cfc
SYMBOL_NAME: nt!KiSystemServiceUser+21
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.572
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 21
FAILURE_BUCKET_ID: AV_nt!KiSystemServiceUser
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {52fb4acd-4941-76da-7d88-ae913a1eb1d9}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa13748.49787\101520-8312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`74800000 PsLoadedModuleList = 0xfffff802`7542a310
Debug session time: Thu Oct 15 19:16:31.356 2020 (UTC + 3:00)
System Uptime: 0 days 21:22:00.132
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`74bf3ea0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb8b`d61a96b0=000000000000003b
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80274ed4953, Address of the instruction which caused the bugcheck
Arg3: fffffb8bd61a9fb0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3202
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-IPC9T25
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 4638
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 3b
BUGCHECK_P1: c0000005
BUGCHECK_P2: fffff80274ed4953
BUGCHECK_P3: fffffb8bd61a9fb0
BUGCHECK_P4: 0
CONTEXT: fffffb8bd61a9fb0 -- (.cxr 0xfffffb8bd61a9fb0)
rax=fffffb8bd61aab18 rbx=ffffb908c08a1640 rcx=0000000000000000
rdx=0000000000000002 rsi=0000000000000a68 rdi=0000000000000000
rip=fffff80274ed4953 rsp=fffffb8bd61aa9b0 rbp=fffffb8bd61aab80
r8=ffffb908c08a1640 r9=0000000000000001 r10=0000fffff80274ea
r11=ffff81fe30a00000 r12=fffffb8bd61aab18 r13=0000000000000000
r14=0000000000000a68 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!ObpReferenceObjectByHandleWithTag+0x43:
fffff802`74ed4953 498bbfb8000000 mov rdi,qword ptr [r15+0B8h] ds:002b:00000000`000000b8=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: KnightOnLine.exe
STACK_TEXT:
fffffb8b`d61aa9b0 fffff802`74ed48fe : 00000000`00000000 00000000`00000002 ffffb908`c08a1640 fffffb8b`d61aab01 : nt!ObpReferenceObjectByHandleWithTag+0x43
fffffb8b`d61aaa40 fffff802`74ea4890 : fffffb8b`d61aab18 00000000`00000000 00000000`0dfcf328 fffffb8b`d61aaaa8 : nt!ObReferenceObjectByHandle+0x2e
fffffb8b`d61aaa90 fffff802`74c058b8 : ffffb908`c896e080 ffffb908`00000000 00000000`00000000 00000000`00000000 : nt!NtSetEvent+0x90
fffffb8b`d61aab00 00000000`777c1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`0dfcf308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777c1cfc
SYMBOL_NAME: nt!ObpReferenceObjectByHandleWithTag+43
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.508
STACK_COMMAND: .cxr 0xfffffb8bd61a9fb0 ; kb
BUCKET_ID_FUNC_OFFSET: 43
FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ObpReferenceObjectByHandleWithTag
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {3d4819ec-af64-be43-ac98-a6e960db3861}
Followup: MachineOwner
---------
Bilgisayara sıfır kurulum yapıp hiçbir oyun yazılım vb. yüklemeden önce aıda64 ile test yaptığım zamanlarda da kapanıyordu oyunlardan dolayı olacağını sanmıyorum şimdi hepsini devre dışı bırakıp tekrar teste alayım bilgisayarı kapanana kadar teste tutayım1- Riot Vanguard'ı kaldırın.
2- Xingcode3'ü kaldırın.
Gördüğüm kadarıyla oyunlarınızın AC'lerinden kaynaklarınıyor sorunlar.
Birde sanırım Bloody'nin ürünlerini kullanıyorsunuz. Çok ihtiyacınız yoksa yazılımını kaldırın.
Bu işlemlerden sonra yeniden hata alırsanız yeni oluşan raporları bizimle paylaşın ancak @Assecreed 'in de dediği gibi daha güvenilir sitelere upload ederek.
Kod:Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa13748.34166\101620-8921-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff800`66c00000 PsLoadedModuleList = 0xfffff800`6782a310 Debug session time: Fri Oct 16 07:40:27.884 2020 (UTC + 3:00) System Uptime: 0 days 0:00:42.897 Loading Kernel Symbols ............................................................... ................................................................ ..................................................... Loading User Symbols Loading unloaded module list ...... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800`66ff45a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff88a`123db830=000000000000000a 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: 0000000000000003, memory referenced Arg2: 00000000000000ff, 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: fffff80067005d21, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2999 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-IPC9T25 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 3030 Key : Analysis.Memory.CommitPeak.Mb Value: 74 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: a BUGCHECK_P1: 3 BUGCHECK_P2: ff BUGCHECK_P3: 0 BUGCHECK_P4: fffff80067005d21 READ_ADDRESS: fffff800678fb390: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd fffff8006780f340: Unable to get Flags value from nt!KdVersionBlock fffff8006780f340: Unable to get Flags value from nt!KdVersionBlock unable to get nt!MmSpecialPagesInUse 0000000000000003 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: Discord.exe TRAP_FRAME: fffff88a123db970 -- (.trap 0xfffff88a123db970) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=0000000100000002 rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80067005d21 rsp=fffff88a123dbb00 rbp=fffff88a123dbb80 r8=0000000000000000 r9=0000000077a21d2c r10=000000000000058c r11=0000000000000246 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up di pl nz na pe nc nt!KiSystemServiceUser+0x21: fffff800`67005d21 807b0300 cmp byte ptr [rbx+3],0 ds:00000000`00000003=?? Resetting default scope STACK_TEXT: fffff88a`123db828 fffff800`67006569 : 00000000`0000000a 00000000`00000003 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx fffff88a`123db830 fffff800`67002869 : 00000000`00000000 fffff800`00000000 ffffd100`a0940100 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff88a`123db970 fffff800`67005d21 : ffffe307`8fb83440 ffffe307`8fb7a080 00000000`00000000 fffff88a`123dbb80 : nt!KiPageFault+0x469 fffff88a`123dbb00 00000000`779a1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceUser+0x21 00000000`0fcfeda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779a1cfc SYMBOL_NAME: nt!KiSystemServiceUser+21 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.572 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 21 FAILURE_BUCKET_ID: AV_nt!KiSystemServiceUser OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {52fb4acd-4941-76da-7d88-ae913a1eb1d9} Followup: MachineOwner --------- Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\CsHay\AppData\Local\Temp\Rar$DIa13748.49787\101520-8312-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff802`74800000 PsLoadedModuleList = 0xfffff802`7542a310 Debug session time: Thu Oct 15 19:16:31.356 2020 (UTC + 3:00) System Uptime: 0 days 21:22:00.132 Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols Loading unloaded module list ................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`74bf3ea0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb8b`d61a96b0=000000000000003b 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80274ed4953, Address of the instruction which caused the bugcheck Arg3: fffffb8bd61a9fb0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3202 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-IPC9T25 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 4638 Key : Analysis.Memory.CommitPeak.Mb Value: 75 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 ADDITIONAL_XML: 1 OS_BUILD_LAYERS: 1 BUGCHECK_CODE: 3b BUGCHECK_P1: c0000005 BUGCHECK_P2: fffff80274ed4953 BUGCHECK_P3: fffffb8bd61a9fb0 BUGCHECK_P4: 0 CONTEXT: fffffb8bd61a9fb0 -- (.cxr 0xfffffb8bd61a9fb0) rax=fffffb8bd61aab18 rbx=ffffb908c08a1640 rcx=0000000000000000 rdx=0000000000000002 rsi=0000000000000a68 rdi=0000000000000000 rip=fffff80274ed4953 rsp=fffffb8bd61aa9b0 rbp=fffffb8bd61aab80 r8=ffffb908c08a1640 r9=0000000000000001 r10=0000fffff80274ea r11=ffff81fe30a00000 r12=fffffb8bd61aab18 r13=0000000000000000 r14=0000000000000a68 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246 nt!ObpReferenceObjectByHandleWithTag+0x43: fffff802`74ed4953 498bbfb8000000 mov rdi,qword ptr [r15+0B8h] ds:002b:00000000`000000b8=???????????????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: KnightOnLine.exe STACK_TEXT: fffffb8b`d61aa9b0 fffff802`74ed48fe : 00000000`00000000 00000000`00000002 ffffb908`c08a1640 fffffb8b`d61aab01 : nt!ObpReferenceObjectByHandleWithTag+0x43 fffffb8b`d61aaa40 fffff802`74ea4890 : fffffb8b`d61aab18 00000000`00000000 00000000`0dfcf328 fffffb8b`d61aaaa8 : nt!ObReferenceObjectByHandle+0x2e fffffb8b`d61aaa90 fffff802`74c058b8 : ffffb908`c896e080 ffffb908`00000000 00000000`00000000 00000000`00000000 : nt!NtSetEvent+0x90 fffffb8b`d61aab00 00000000`777c1cfc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28 00000000`0dfcf308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777c1cfc SYMBOL_NAME: nt!ObpReferenceObjectByHandleWithTag+43 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.508 STACK_COMMAND: .cxr 0xfffffb8bd61a9fb0 ; kb BUCKET_ID_FUNC_OFFSET: 43 FAILURE_BUCKET_ID: 0x3B_c0000005_nt!ObpReferenceObjectByHandleWithTag OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {3d4819ec-af64-be43-ac98-a6e960db3861} Followup: MachineOwner ---------
Dediklerimi bir kaldırın ona göre gidelim en azından kafamızdan yazılımları çıkarmış oluruz. Aldığınız bazı hatalar donanımsal olabilir ama emin olamıyorum bildiğiniz üzere uyumsuz yazılımlarnı etkisi çok oluyor.Kullanım dışı bıraktığım halde yine aynıları çıkmış sanırım. Akşam SSD ye format atıp hiçbir kurulum güncelleme vb yapmadan test edip dump dosyasını paylaşmam daha doğru olacak.
AIDA64 lisanssız kasayı kontol etmesi için bir bilgisayarcıya bırakmıştım oda bu yazılımı kurulu bırakmış.
Sizce şuan ki duruma kadar yazılımsal mı donanımsal mıdır bu sorun? bana donanımsal gibi geliyor
Hatayı almaya başladığım günden itibaren tek değişiklik anakart oldu halen devam etmekte
Değişimden önce ve sonrasında aynı hataları almaya devam etti ben şüphelerim üzerine anakartı sorumlu tutmuştum ama sorun onda değilmiş şuan Quadro marka bir anakart takılı test edemediğim tek bileşenim işlemciDediklerimi bir kaldırın ona göre gidelim en azından kafamızdan yazılımları çıkarmış oluruz. Aldığınız bazı hatalar donanımsal olabilir ama emin olamıyorum bildiğiniz üzere uyumsuz yazılımlarnı etkisi çok oluyor.
Anakart değiştirdikten sonra mı hata almaya başladınız?
Evet gördüm onu BIOS güncellemesi için bakacaktım ama göremedim.Değişimden önce ve sonrasında aynı hataları almaya devam etti ben şüphelerim üzerine anakartı sorumlu tutmuştum ama sorun onda değilmiş şuan Quadro marka bir anakart takılı test edemediğim tek bileşenim işlemci
BaseBoardManufacturer = quadro
BaseBoardProduct = H61-B75U3/V3
BaseBoardVersion = V124
Evet gördüm onu BIOS güncellemesi için bakacaktım ama göremedim.
Kod:BaseBoardManufacturer = quadro BaseBoardProduct = H61-B75U3/V3 BaseBoardVersion = V124