Sonuncusu hariç diğerleri aynı dumpların.
@The G.O.A.T @Enes3078 .
Hocam tam olarak anlamadım SFC /scannow yazar mısınız?(Komut İstemcisine)
[CODE title="MiniDumplar"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself. The first argument describes the nature of the
problem, the second argument is the address of the PDO. The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000001, Duplicate PDO
A specific instance of a driver has enumerated multiple PDOs with
identical device id and unique ids.
Arg2: ffffb308190eea70, Newly reported PDO.
Arg3: ffffb30827099a70, PDO of which it is a duplicate.
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for IntcOED.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 16265
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 41041
Key : Analysis.Init.CPU.mSec
Value: 921
Key : Analysis.Init.Elapsed.mSec
Value: 13747
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
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
BUGCHECK_CODE: ca
BUGCHECK_P1: 1
BUGCHECK_P2: ffffb308190eea70
BUGCHECK_P3: ffffb30827099a70
BUGCHECK_P4: 0
DEVICE_OBJECT: ffffb308190eea70
DRIVER_OBJECT: ffffb308215f3c10
IMAGE_NAME: IntcOED.sys
MODULE_NAME: IntcOED
FAULTING_MODULE: fffff8037ad30000 IntcOED
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
LOCK_ADDRESS: fffff8035da44d20 -- (!locks fffff8035da44d20)
Resource @ nt!PiEngineLock (0xfffff8035da44d20) Exclusively owned
Contention Count = 58
NumberOfExclusiveWaiters = 1
Threads: ffffb308134c3040-01<*>
Threads Waiting On Exclusive Access:
ffffb308193c4080
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff8035da44d20
Thread Count : 1
Thread address: 0xffffb308134c3040
Thread wait : 0x4be6
STACK_TEXT:
fffff58b`1d3220b8 fffff803`5d61238d : 00000000`000000ca 00000000`00000001 ffffb308`190eea70 ffffb308`27099a70 : nt!KeBugCheckEx
fffff58b`1d3220c0 fffff803`5d526d64 : ffffb308`28243cb0 ffffb308`28243cb0 00000000`00000001 00000000`00000002 : nt!PiProcessNewDeviceNode+0xe871d
fffff58b`1d322290 fffff803`5d531f2c : ffffb308`19463a00 fffff803`5d060a01 fffff58b`1d3223b0 fffff803`00000002 : nt!PipProcessDevNodeTree+0x380
fffff58b`1d322360 fffff803`5d16c0b6 : 00000001`00000003 ffffb308`283ebcc0 ffffb308`19463a00 ffffb308`19463a00 : nt!PiProcessReenumeration+0x88
fffff58b`1d3223b0 fffff803`5d025975 : ffffb308`134c3040 ffffb308`134a7ce0 fffff803`5da43660 fffff803`00000000 : nt!PnpDeviceActionWorker+0x206
fffff58b`1d322470 fffff803`5d117e85 : ffffb308`134c3040 00000000`00000080 ffffb308`134e5080 001fe4ff`bd9bbfff : nt!ExpWorkerThread+0x105
fffff58b`1d322510 fffff803`5d1fd408 : ffff9a81`41180180 ffffb308`134c3040 fffff803`5d117e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff58b`1d322560 00000000`00000000 : fffff58b`1d323000 fffff58b`1d31c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xCA_1_IMAGE_IntcOED.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7dd178ac-48d1-d0ac-dd77-defde5a6a917}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself. The first argument describes the nature of the
problem, the second argument is the address of the PDO. The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000001, Duplicate PDO
A specific instance of a driver has enumerated multiple PDOs with
identical device id and unique ids.
Arg2: ffffb308190eea70, Newly reported PDO.
Arg3: ffffb30827099a70, PDO of which it is a duplicate.
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for IntcOED.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 16265
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 41041
Key : Analysis.Init.CPU.mSec
Value: 921
Key : Analysis.Init.Elapsed.mSec
Value: 13747
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
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
BUGCHECK_CODE: ca
BUGCHECK_P1: 1
BUGCHECK_P2: ffffb308190eea70
BUGCHECK_P3: ffffb30827099a70
BUGCHECK_P4: 0
DEVICE_OBJECT: ffffb308190eea70
DRIVER_OBJECT: ffffb308215f3c10
IMAGE_NAME: IntcOED.sys
MODULE_NAME: IntcOED
FAULTING_MODULE: fffff8037ad30000 IntcOED
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
LOCK_ADDRESS: fffff8035da44d20 -- (!locks fffff8035da44d20)
Resource @ nt!PiEngineLock (0xfffff8035da44d20) Exclusively owned
Contention Count = 58
NumberOfExclusiveWaiters = 1
Threads: ffffb308134c3040-01<*>
Threads Waiting On Exclusive Access:
ffffb308193c4080
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff8035da44d20
Thread Count : 1
Thread address: 0xffffb308134c3040
Thread wait : 0x4be6
STACK_TEXT:
fffff58b`1d3220b8 fffff803`5d61238d : 00000000`000000ca 00000000`00000001 ffffb308`190eea70 ffffb308`27099a70 : nt!KeBugCheckEx
fffff58b`1d3220c0 fffff803`5d526d64 : ffffb308`28243cb0 ffffb308`28243cb0 00000000`00000001 00000000`00000002 : nt!PiProcessNewDeviceNode+0xe871d
fffff58b`1d322290 fffff803`5d531f2c : ffffb308`19463a00 fffff803`5d060a01 fffff58b`1d3223b0 fffff803`00000002 : nt!PipProcessDevNodeTree+0x380
fffff58b`1d322360 fffff803`5d16c0b6 : 00000001`00000003 ffffb308`283ebcc0 ffffb308`19463a00 ffffb308`19463a00 : nt!PiProcessReenumeration+0x88
fffff58b`1d3223b0 fffff803`5d025975 : ffffb308`134c3040 ffffb308`134a7ce0 fffff803`5da43660 fffff803`00000000 : nt!PnpDeviceActionWorker+0x206
fffff58b`1d322470 fffff803`5d117e85 : ffffb308`134c3040 00000000`00000080 ffffb308`134e5080 001fe4ff`bd9bbfff : nt!ExpWorkerThread+0x105
fffff58b`1d322510 fffff803`5d1fd408 : ffff9a81`41180180 ffffb308`134c3040 fffff803`5d117e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff58b`1d322560 00000000`00000000 : fffff58b`1d323000 fffff58b`1d31c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xCA_1_IMAGE_IntcOED.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7dd178ac-48d1-d0ac-dd77-defde5a6a917}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself. The first argument describes the nature of the
problem, the second argument is the address of the PDO. The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000001, Duplicate PDO
A specific instance of a driver has enumerated multiple PDOs with
identical device id and unique ids.
Arg2: ffffb308190eea70, Newly reported PDO.
Arg3: ffffb30827099a70, PDO of which it is a duplicate.
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for IntcOED.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 16265
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 41041
Key : Analysis.Init.CPU.mSec
Value: 921
Key : Analysis.Init.Elapsed.mSec
Value: 13747
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
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
BUGCHECK_CODE: ca
BUGCHECK_P1: 1
BUGCHECK_P2: ffffb308190eea70
BUGCHECK_P3: ffffb30827099a70
BUGCHECK_P4: 0
DEVICE_OBJECT: ffffb308190eea70
DRIVER_OBJECT: ffffb308215f3c10
IMAGE_NAME: IntcOED.sys
MODULE_NAME: IntcOED
FAULTING_MODULE: fffff8037ad30000 IntcOED
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
LOCK_ADDRESS: fffff8035da44d20 -- (!locks fffff8035da44d20)
Resource @ nt!PiEngineLock (0xfffff8035da44d20) Exclusively owned
Contention Count = 58
NumberOfExclusiveWaiters = 1
Threads: ffffb308134c3040-01<*>
Threads Waiting On Exclusive Access:
ffffb308193c4080
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff8035da44d20
Thread Count : 1
Thread address: 0xffffb308134c3040
Thread wait : 0x4be6
STACK_TEXT:
fffff58b`1d3220b8 fffff803`5d61238d : 00000000`000000ca 00000000`00000001 ffffb308`190eea70 ffffb308`27099a70 : nt!KeBugCheckEx
fffff58b`1d3220c0 fffff803`5d526d64 : ffffb308`28243cb0 ffffb308`28243cb0 00000000`00000001 00000000`00000002 : nt!PiProcessNewDeviceNode+0xe871d
fffff58b`1d322290 fffff803`5d531f2c : ffffb308`19463a00 fffff803`5d060a01 fffff58b`1d3223b0 fffff803`00000002 : nt!PipProcessDevNodeTree+0x380
fffff58b`1d322360 fffff803`5d16c0b6 : 00000001`00000003 ffffb308`283ebcc0 ffffb308`19463a00 ffffb308`19463a00 : nt!PiProcessReenumeration+0x88
fffff58b`1d3223b0 fffff803`5d025975 : ffffb308`134c3040 ffffb308`134a7ce0 fffff803`5da43660 fffff803`00000000 : nt!PnpDeviceActionWorker+0x206
fffff58b`1d322470 fffff803`5d117e85 : ffffb308`134c3040 00000000`00000080 ffffb308`134e5080 001fe4ff`bd9bbfff : nt!ExpWorkerThread+0x105
fffff58b`1d322510 fffff803`5d1fd408 : ffff9a81`41180180 ffffb308`134c3040 fffff803`5d117e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff58b`1d322560 00000000`00000000 : fffff58b`1d323000 fffff58b`1d31c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xCA_1_IMAGE_IntcOED.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7dd178ac-48d1-d0ac-dd77-defde5a6a917}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself. The first argument describes the nature of the
problem, the second argument is the address of the PDO. The other arguments
vary depending on argument 1.
Arguments:
Arg1: 0000000000000001, Duplicate PDO
A specific instance of a driver has enumerated multiple PDOs with
identical device id and unique ids.
Arg2: ffffb308190eea70, Newly reported PDO.
Arg3: ffffb30827099a70, PDO of which it is a duplicate.
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for IntcOED.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 16265
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 41041
Key : Analysis.Init.CPU.mSec
Value: 921
Key : Analysis.Init.Elapsed.mSec
Value: 13747
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
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
BUGCHECK_CODE: ca
BUGCHECK_P1: 1
BUGCHECK_P2: ffffb308190eea70
BUGCHECK_P3: ffffb30827099a70
BUGCHECK_P4: 0
DEVICE_OBJECT: ffffb308190eea70
DRIVER_OBJECT: ffffb308215f3c10
IMAGE_NAME: IntcOED.sys
MODULE_NAME: IntcOED
FAULTING_MODULE: fffff8037ad30000 IntcOED
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
LOCK_ADDRESS: fffff8035da44d20 -- (!locks fffff8035da44d20)
Resource @ nt!PiEngineLock (0xfffff8035da44d20) Exclusively owned
Contention Count = 58
NumberOfExclusiveWaiters = 1
Threads: ffffb308134c3040-01<*>
Threads Waiting On Exclusive Access:
ffffb308193c4080
1 total locks
PNP_TRIAGE_DATA:
Lock address : 0xfffff8035da44d20
Thread Count : 1
Thread address: 0xffffb308134c3040
Thread wait : 0x4be6
STACK_TEXT:
fffff58b`1d3220b8 fffff803`5d61238d : 00000000`000000ca 00000000`00000001 ffffb308`190eea70 ffffb308`27099a70 : nt!KeBugCheckEx
fffff58b`1d3220c0 fffff803`5d526d64 : ffffb308`28243cb0 ffffb308`28243cb0 00000000`00000001 00000000`00000002 : nt!PiProcessNewDeviceNode+0xe871d
fffff58b`1d322290 fffff803`5d531f2c : ffffb308`19463a00 fffff803`5d060a01 fffff58b`1d3223b0 fffff803`00000002 : nt!PipProcessDevNodeTree+0x380
fffff58b`1d322360 fffff803`5d16c0b6 : 00000001`00000003 ffffb308`283ebcc0 ffffb308`19463a00 ffffb308`19463a00 : nt!PiProcessReenumeration+0x88
fffff58b`1d3223b0 fffff803`5d025975 : ffffb308`134c3040 ffffb308`134a7ce0 fffff803`5da43660 fffff803`00000000 : nt!PnpDeviceActionWorker+0x206
fffff58b`1d322470 fffff803`5d117e85 : ffffb308`134c3040 00000000`00000080 ffffb308`134e5080 001fe4ff`bd9bbfff : nt!ExpWorkerThread+0x105
fffff58b`1d322510 fffff803`5d1fd408 : ffff9a81`41180180 ffffb308`134c3040 fffff803`5d117e30 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff58b`1d322560 00000000`00000000 : fffff58b`1d323000 fffff58b`1d31c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0xCA_1_IMAGE_IntcOED.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7dd178ac-48d1-d0ac-dd77-defde5a6a917}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WIN32K_POWER_WATCHDOG_TIMEOUT (19c)
Win32k did not turn the monitor on in a timely manner.
Arguments:
Arg1: 0000000000000050, Calling monitor driver to power on.
Arg2: ffffd3064a80f080, Pointer to the power request worker thread.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6999
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 53521
Key : Analysis.Init.CPU.mSec
Value: 937
Key : Analysis.Init.Elapsed.mSec
Value: 21305
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
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
BUGCHECK_CODE: 19c
BUGCHECK_P1: 50
BUGCHECK_P2: ffffd3064a80f080
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csrss.exe
FAULTING_THREAD: ffffd3064a80f080
STACK_TEXT:
ffff8608`03dbe570 fffff802`32c65850 : ffffd306`0000000b fffff802`ffffffff ffffd306`00000000 ffffd306`4a4a3158 : nt!KiSwapContext+0x76
ffff8608`03dbe6b0 fffff802`32c64d7f : 00000000`00000001 ffff8608`03dbe7d0 ffff8608`03dbe870 ffffd306`44f674b0 : nt!KiSwapThread+0x500
ffff8608`03dbe760 fffff802`32c64623 : ffffd306`00000000 ffff8608`00000000 00000000`00000000 ffffd306`4a80f1c0 : nt!KiCommitThreadWait+0x14f
ffff8608`03dbe800 fffff802`4aacf742 : ffffd306`3cfda178 00000000`00000000 ffffd306`3cfd9100 ffff8608`03dbea00 : nt!KeWaitForSingleObject+0x233
ffff8608`03dbe8f0 fffff802`4ac13d02 : ffffd306`3cfd9180 00000000`00000000 00000000`00000000 ffff8608`03dbeb28 : dxgkrnl!DpiCheckForOutstandingD3Requests+0x6e
ffff8608`03dbe950 fffff802`4abd6c66 : 00000000`00000000 00000000`00000000 ffff8608`03dbee00 fffff802`32fda920 : dxgkrnl!DxgkPowerOnOffMonitor+0x10e
ffff8608`03dbea70 fffff802`4ab9fc80 : ffffd306`ffffffff ffffd306`52c0bcb0 ffffd306`48463e20 fffff802`4aab94b9 : dxgkrnl!DpiGdoDispatchInternalIoctl+0x586
ffff8608`03dbeb20 fffff802`53bc045e : 00000000`c0000002 ffffd306`52c0bd80 00000000`00000000 00000000`c0000225 : dxgkrnl!DpiDispatchInternalIoctl+0x100
ffff8608`03dbec50 00000000`c0000002 : ffffd306`52c0bd80 00000000`00000000 00000000`c0000225 ffff8608`03dbee00 : nvlddmkm+0xd8045e
ffff8608`03dbec58 ffffd306`52c0bd80 : 00000000`00000000 00000000`c0000225 ffff8608`03dbee00 ffffd306`48463cd0 : 0xc0000002
ffff8608`03dbec60 00000000`00000000 : 00000000`c0000225 ffff8608`03dbee00 ffffd306`48463cd0 ffffd306`52c0bcb0 : 0xffffd306`52c0bd80
STACK_COMMAND: .thread 0xffffd3064a80f080 ; kb
SYMBOL_NAME: dxgkrnl!DpiCheckForOutstandingD3Requests+6e
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.906
BUCKET_ID_FUNC_OFFSET: 6e
FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_dxgkrnl!DpiCheckForOutstandingD3Requests
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {b953a24d-00f1-7e05-510d-44334608bc78}
Followup: MachineOwner
---------
[/CODE]
Sonuncusu hariç diğerleri aynı dumpların.
C:\Windows\system32>SFC /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
C:\Windows\system32>SFC /scannow
Beginning System scan. This process will take some time.
Beginning verification phase of System scan.
Verification 100% Complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For Online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
Repairs, details are included in the log file provided by the /OFFLOGFILE flag.
Ses sürücünü güncelle.
USB sürücülerini kesinlikle güncellemen lazım.
Intel sürücülerini güncelle.
SteelSeries yazılımlarını kaldır.
Bilgisayara kamera ve mikrofon bağlıyorsun. Sürücülerini güncelle veya bağlama.
DDU ile Sürücü Kaldırma Rehberi DDU ile ekran kartı sürücünü kaldırıp, WHQL sertifikalı bir sürüm kur.
Bilgisayarı yeni aldım, tüm sürücüleri markanın kendi sitesinden indirdim, sadece Intel SST (ne olduğunu bilmiyorum) ve Intel Thunderbolt sürücülerini kuramadım.
saydığınız maddelerden sadece steelseries yazılımını kaldırdım. Yine indirsem sorun oluşturur mu?Dediğim şeyleri yapın. Eğer yapmışsanız bile donanım sürücüsü ile güncelleyin. Bazen güncel olmayabiliyor.
Diğerlerini de yaptıysanız. Gözlem yapın. Yeni dump dosyası alırsanız paylaşın. Almazsanız da bildirin.
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.