Mr. Patrick Bateman
Hectopat
- Katılım
- 2 Kasım 2019
- Mesajlar
- 2.252
- Çözümler
- 2
Selam dostlar. Bu hatayı aldım masaüstündeyken rica etsem bilgisi olan bir arkadaşımız nedenini açıklayabilir mi?
IMAGE_NAME: sshid.sys
*** WARNING: Unable to verify timestamp for sshid.sys
sshid.sys
= Steelseries Engine yazılımının sürücüsü. Timestamp: Thu Mar 2 23:22:11 2023 (64010573)
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffff80740d27a00, Original thread which is the cause of the failure
Arg2: ffff86065bd7e080, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for sshid.sys
*** WARNING: Check Image - Checksum mismatch - Dump: 0x2c1e2f, File: 0x2c1e23 - C:\ProgramData\Dbg\sym\win32kbase.sys\23B5CE9B2d1000\win32kbase.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1046
Key : Analysis.Elapsed.mSec
Value: 3174
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 46
Key : Analysis.Init.Elapsed.mSec
Value: 1920
Key : Analysis.Memory.CommitPeak.Mb
Value: 143
Key : Bugcheck.Code.LegacyAPI
Value: 0x100000b8
Key : Failure.Bucket
Value: 0xB8_sshid!unknown_function
Key : Failure.Hash
Value: {c5f18334-ba57-3396-ea7f-6e96b216d079}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: b8
BUGCHECK_P1: fffff80740d27a00
BUGCHECK_P2: ffff86065bd7e080
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 071023-8750-01.dmp
FAULTING_THREAD: fffff80740d27a00
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff807`452970c0 fffff807`4021c9c0 : 00000000`00000000 00000000`00000000 00000000`000000e0 ffff8606`4d0c3d00 : nt!KiSwapContext+0x76
fffff807`45297200 fffff807`4021beef : fffff807`40d27a00 ffff8606`54ff19c0 fffff807`452973c0 00000000`00000000 : nt!KiSwapThread+0x500
fffff807`452972b0 fffff807`4021b793 : 00000000`0000007f ffff8606`00000000 00000000`00000000 fffff807`40d27b40 : nt!KiCommitThreadWait+0x14f
fffff807`45297350 fffff807`439b1ef6 : fffff807`45297488 00000000`00000000 fffff807`45297800 00000000`00000000 : nt!KeWaitForSingleObject+0x233
fffff807`45297440 fffff807`43a1b393 : 00000000`00000002 fffff807`45297600 fffff807`00000000 ffff8606`00000000 : Wdf01000!FxIoTarget::SubmitSync+0x1e6 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 1839]
fffff807`45297510 fffff807`aa882fff : ffff8606`5c18ba00 00000000`00000030 ffff8606`581297e0 fffff807`45297899 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x263 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 1056]
fffff807`45297840 ffff8606`5c18ba00 : 00000000`00000030 ffff8606`581297e0 fffff807`45297899 fffff807`45297898 : sshid+0x2fff
fffff807`45297848 00000000`00000030 : ffff8606`581297e0 fffff807`45297899 fffff807`45297898 fffff807`45297880 : 0xffff8606`5c18ba00
fffff807`45297850 ffff8606`581297e0 : fffff807`45297899 fffff807`45297898 fffff807`45297880 00000000`00000000 : 0x30
fffff807`45297858 fffff807`45297899 : fffff807`45297898 fffff807`45297880 00000000`00000000 fffff807`439bbbbe : 0xffff8606`581297e0
fffff807`45297860 fffff807`45297898 : fffff807`45297880 00000000`00000000 fffff807`439bbbbe 00000000`00000001 : 0xfffff807`45297899
fffff807`45297868 fffff807`45297880 : 00000000`00000000 fffff807`439bbbbe 00000000`00000001 ffff8606`5cf09471 : 0xfffff807`45297898
fffff807`45297870 00000000`00000000 : fffff807`439bbbbe 00000000`00000001 ffff8606`5cf09471 00000000`00000001 : 0xfffff807`45297880
SYMBOL_NAME: sshid+2fff
MODULE_NAME: sshid
IMAGE_NAME: sshid.sys
STACK_COMMAND: .process /r /p 0xfffff80740d24a00; .thread 0xfffff80740d27a00 ; kb
BUCKET_ID_FUNC_OFFSET: 2fff
FAILURE_BUCKET_ID: 0xB8_sshid!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {c5f18334-ba57-3396-ea7f-6e96b216d079}
Followup: MachineOwner
---------
Hocam sorunun kaynağı SteelSeries mi? Ve güncel BIOS sorunlu ekran koruyucuya geçince VGA Işığı yakıp EZDebug hatası veriyor o sebepten geçmedim.Rich (BB code):IMAGE_NAME: sshid.sys
Kod:*** WARNING: Unable to verify timestamp for sshid.sys
sshid.sys
= Steelseries Engine yazılımının sürücüsü.
Sürücüsünün tarihi Mart 2023 görünüyor.
Kod:Timestamp: Thu Mar 2 23:22:11 2023 (64010573)
Steelseries aracını tamamen kaldırın.
Çok elzemse tekrar kurun.
Bu sayede sürücüde bir problem varsa veya eskimişse çözülebilir.
- Ayrıca BIOS eskimiş.
- 7C02v3F sürümünü kullanıyorsunuz.
- 7C02v3G'ye güncelleyebilirsiniz.
Döküm:
Kod:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* ATTEMPTED_SWITCH_FROM_DPC (b8) A wait operation, attach process, or yield was attempted from a DPC routine. This is an illegal operation and the stack track will lead to the offending code and original DPC routine. Arguments: Arg1: fffff80740d27a00, Original thread which is the cause of the failure Arg2: ffff86065bd7e080, New thread Arg3: 0000000000000000, Stack address of the original thread Arg4: 0000000000000000 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for sshid.sys *** WARNING: Check Image - Checksum mismatch - Dump: 0x2c1e2f, File: 0x2c1e23 - C:\ProgramData\Dbg\sym\win32kbase.sys\23B5CE9B2d1000\win32kbase.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1046 Key : Analysis.Elapsed.mSec Value: 3174 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 46 Key : Analysis.Init.Elapsed.mSec Value: 1920 Key : Analysis.Memory.CommitPeak.Mb Value: 143 Key : Bugcheck.Code.LegacyAPI Value: 0x100000b8 Key : Failure.Bucket Value: 0xB8_sshid!unknown_function Key : Failure.Hash Value: {c5f18334-ba57-3396-ea7f-6e96b216d079} Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: b8 BUGCHECK_P1: fffff80740d27a00 BUGCHECK_P2: ffff86065bd7e080 BUGCHECK_P3: 0 BUGCHECK_P4: 0 FILE_IN_CAB: 071023-8750-01.dmp FAULTING_THREAD: fffff80740d27a00 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff807`452970c0 fffff807`4021c9c0 : 00000000`00000000 00000000`00000000 00000000`000000e0 ffff8606`4d0c3d00 : nt!KiSwapContext+0x76 fffff807`45297200 fffff807`4021beef : fffff807`40d27a00 ffff8606`54ff19c0 fffff807`452973c0 00000000`00000000 : nt!KiSwapThread+0x500 fffff807`452972b0 fffff807`4021b793 : 00000000`0000007f ffff8606`00000000 00000000`00000000 fffff807`40d27b40 : nt!KiCommitThreadWait+0x14f fffff807`45297350 fffff807`439b1ef6 : fffff807`45297488 00000000`00000000 fffff807`45297800 00000000`00000000 : nt!KeWaitForSingleObject+0x233 fffff807`45297440 fffff807`43a1b393 : 00000000`00000002 fffff807`45297600 fffff807`00000000 ffff8606`00000000 : Wdf01000!FxIoTarget::SubmitSync+0x1e6 [minkernel\wdf\framework\shared\targets\general\fxiotarget.cpp @ 1839] fffff807`45297510 fffff807`aa882fff : ffff8606`5c18ba00 00000000`00000030 ffff8606`581297e0 fffff807`45297899 : Wdf01000!imp_WdfUsbTargetDeviceSendControlTransferSynchronously+0x263 [minkernel\wdf\framework\shared\targets\usb\fxusbdeviceapi.cpp @ 1056] fffff807`45297840 ffff8606`5c18ba00 : 00000000`00000030 ffff8606`581297e0 fffff807`45297899 fffff807`45297898 : sshid+0x2fff fffff807`45297848 00000000`00000030 : ffff8606`581297e0 fffff807`45297899 fffff807`45297898 fffff807`45297880 : 0xffff8606`5c18ba00 fffff807`45297850 ffff8606`581297e0 : fffff807`45297899 fffff807`45297898 fffff807`45297880 00000000`00000000 : 0x30 fffff807`45297858 fffff807`45297899 : fffff807`45297898 fffff807`45297880 00000000`00000000 fffff807`439bbbbe : 0xffff8606`581297e0 fffff807`45297860 fffff807`45297898 : fffff807`45297880 00000000`00000000 fffff807`439bbbbe 00000000`00000001 : 0xfffff807`45297899 fffff807`45297868 fffff807`45297880 : 00000000`00000000 fffff807`439bbbbe 00000000`00000001 ffff8606`5cf09471 : 0xfffff807`45297898 fffff807`45297870 00000000`00000000 : fffff807`439bbbbe 00000000`00000001 ffff8606`5cf09471 00000000`00000001 : 0xfffff807`45297880 SYMBOL_NAME: sshid+2fff MODULE_NAME: sshid IMAGE_NAME: sshid.sys STACK_COMMAND: .process /r /p 0xfffff80740d24a00; .thread 0xfffff80740d27a00 ; kb BUCKET_ID_FUNC_OFFSET: 2fff FAILURE_BUCKET_ID: 0xB8_sshid!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {c5f18334-ba57-3396-ea7f-6e96b216d079} Followup: MachineOwner ---------
Ekran koruyucu derken, mesela Windows 7'de vardı balonlar oluyordu, öyle bir ekran koruyucu mu? Yoksa mesela 10 dk. hareketsizlikten sonra ekranın kapanması, siyah olması mı?Ekran koruyucuya geçince.
Evet hata veren sürücü bu görünüyor.Hocam sorunun kaynağı SteelSeries mi?
Siyah ekran hocam. AMD RX 6600 De bu sorunu yaşadım geri F sürüme döndüm.Ekran koruyucu derken, mesela Windows 7'de vardı balonlar oluyordu, öyle bir ekran koruyucu mu? Yoksa mesela 10 dk. hareketsizlikten sonra ekranın kapanması, siyah olması mı?
Bende de aynı anakart var böyle bir problem yok. Gerçi diğer sistem parçaları farklı olabilir orası ayrı konu.
Evet hata veren sürücü bu görünüyor.
Önemliyse kaldırıp tekrar yükleyin.
Bu sitenin çalışmasını sağlamak için gerekli çerezleri ve deneyiminizi iyileştirmek için isteğe bağlı çerezleri kullanıyoruz.