MSI GL65 Leopard 10SCXR volmgr.sys mavi ekran hatası

Persseus

Kilopat
Katılım
30 Temmuz 2018
Mesajlar
1.799
Makaleler
3
Çözümler
7
Yer
Konya veya İstanbul
Daha fazla  
Cinsiyet
Erkek
Meslek
Öğrenci
Bu hafta 2. kez mavi ekran hatası aldım. Mavi ekran hatasını alırken BalenaEtcher ile HiveOS madencilik yazılımını laptopumun USB 3.2 portundan USB 3.0 SanDisk Flash belleğe yazdırırken aldım. Flash bellek sıfır yeni ürün. Sorun neden kaynaklı acaba?
  • Laptopum MSI GL65 Leopard 10SCXR:
  • i5 10300H işlemci
  • 2x8GB DDR4 RAM
  • GTX1650 GPU
  • 500GB 970 EVO SSD ve 500GB 860 EVO SSD
DMP dosyaları: Minidumplar - Google Drive

WhatsApp Image 2021-03-01 at 15.47.11 (1).jpeg

WhatsApp Image 2021-03-01 at 15.47.11.jpeg
 
Bu hafta 2. kez mavi ekran hatası aldım. Mavi ekran hatasını alırken BalenaEtcher ile HiveOS madencilik yazılımını laptopumun USB 3.2 portundan USB 3.0 SanDisk Flash belleğe yazdırırken aldım. Flash bellek sıfır yeni ürün. Sorun neden kaynaklı acaba?
  • Laptopum MSI GL65 Leopard 10SCXR:
  • i5 10300H işlemci
  • 2x8GB DDR4 RAM
  • GTX1650 GPU
  • 500GB 970 EVO SSD ve 500GB 860 EVO SSD
DMP dosyaları: Minidumplar - Google Drive

Eki Görüntüle 901416

Eki Görüntüle 901417

Sanırım siz mining sisteme yükleyecektiniz. Pardon.
Microsoft Windows volume Manager extension driver olarak geçiyor dosya. Sistem dosyalarında bozukluk olabilir ya da eksik güncelleme olabilir. Bu komutla dosyaları taratın bozuk olan varsa onarılacak:

Kod:
sfc/scannow

Bunu uygula.

Sürüm nedir?
2. Hata aynı... Ses sürücüsü ile alakalı.
 
Son düzenleme:
1) Vanguard kaldırın.

2) MSI Afterburner kaldırın.

3) Sandisk USB aygıtınızı çıkartın ve farklı bir USB portuna takarak kullanın.

[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8042a58f403, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000040, Parameter 1 of the exception

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 14905

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 38573

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

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: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8042a58f403

BUGCHECK_P3: 0

BUGCHECK_P4: 40

READ_ADDRESS: fffff804288fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8042880f330: Unable to get Flags value from nt!KdVersionBlock
fffff8042880f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000040

EXCEPTION_PARAMETER2: 0000000000000040

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
ffffa682`7ee8ef48 fffff804`280914d3 : 00000000`0000001e ffffffff`c0000005 fffff804`2a58f403 00000000`00000000 : nt!KeBugCheckEx
ffffa682`7ee8ef50 fffff804`28007bac : 00000000`00001000 ffffa682`7ee8f7f0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x166ad3
ffffa682`7ee8f610 fffff804`28003d43 : 00000000`00000000 ffffab00`0801a040 00000000`00000000 ffffbb81`735d7180 : nt!KiExceptionDispatch+0x12c
ffffa682`7ee8f7f0 fffff804`2a58f403 : ffffab00`05758e00 ffffab00`0801a100 00000000`00000000 ffffab00`05758e18 : nt!KiPageFault+0x443
ffffa682`7ee8f980 fffff804`2a58fe7e : ffffab00`05758d90 00000000`00000000 ffffa682`7ee8fad0 00000000`03e00000 : volmgr!VmpQueryUniqueIdInternal+0x37
ffffa682`7ee8f9b0 fffff804`2a59087f : ffffab00`05758d90 ffffab00`0f79e010 ffffab00`05758d90 fffff804`27e50cb9 : volmgr!VmpSetPartitionInformation+0x2d6a
ffffa682`7ee8faa0 fffff804`2a5818a2 : ffffab00`05758d90 ffffa682`7ee8fbc0 ffffab00`0f79e010 00000000`00000cc4 : volmgr!VmpGetLengthInfo+0x4877
ffffa682`7ee8fb80 fffff804`27e52f55 : ffffab00`0f79e010 ffffab00`0f79e010 ffffffff`ffffffff fffff804`2b16f000 : volmgr!VmDeviceControl+0x332
ffffa682`7ee8fbe0 fffff804`27f0ee6e : ffffab0f`f6006c80 025000a0`000000a0 ffffab00`00000000 fffff804`27e63bf0 : nt!IofCallDriver+0x55
ffffa682`7ee8fc20 fffff804`282d3ec1 : ffffab0f`f6002100 00000000`00000000 ffffab0f`f6002340 ffffab00`05758dff : nt!IoSynchronousCallDriver+0x4e
ffffa682`7ee8fc80 fffff804`2b1b2082 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`2a5818fd : nt!IoForwardIrpSynchronously+0x41
ffffa682`7ee8fcb0 fffff804`2b153212 : ffffab00`0f79e010 ffffa682`7ec07001 ffffab00`0e2ab180 00000000`00000000 : fvevol+0x72082
ffffa682`7ee8fda0 fffff804`27e52f55 : 00000000`00000004 00000000`00000000 ffffa682`7ec07000 ffffa682`7fb361e8 : fvevol+0x13212
ffffa682`7ee8fea0 fffff804`2b211033 : 00007fff`08f51200 00007fff`08e56d60 ffffa682`7fb36002 00007fff`08e56c20 : nt!IofCallDriver+0x55
ffffa682`7ee8fee0 fffff804`27e52f55 : 00000000`18bab83a 00000000`00000000 00000000`00000000 00000000`00000000 : volume!VolumePassThrough+0x23
ffffa682`7ee8ff10 fffff804`2a87322c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x55
ffffa682`7ee8ff50 fffff804`27ff935e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`1737d710 : Ntfs!NtfsStorageDriverCallout+0x1c
ffffa682`7ee8ff80 fffff804`27ff931c : ffffa682`7ee8ffd0 ffffab00`0801a040 ffffa682`7ee90000 fffff804`27f547ed : nt!KxSwitchKernelStackCallout+0x2e
ffffa682`7ec06fa0 fffff804`27f547ed : ffffa682`7ee8ffd0 ffffab00`0801a040 ffffa682`7ec07000 00000010`00000001 : nt!KiSwitchKernelStackContinue
ffffa682`7ec06fc0 fffff804`27f545e2 : fffff804`2a873210 ffffa682`7ec071b0 00000000`00000002 00000000`00000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x19d
ffffa682`7ec07060 fffff804`27f54443 : ffffa682`7ec07270 ffffab00`0d5f9d78 00000000`00000000 ffffa682`7ec0746f : nt!KiExpandKernelStackAndCalloutSwitchStack+0xf2
ffffa682`7ec070d0 fffff804`27f543fd : fffff804`2a873210 ffffa682`7ec071b0 00000000`0007405c 00000000`03e00000 : nt!KeExpandKernelStackAndCalloutInternal+0x33
ffffa682`7ec07140 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x1d


SYMBOL_NAME: volmgr!VmpQueryUniqueIdInternal+37

MODULE_NAME: volmgr

IMAGE_NAME: volmgr.sys

IMAGE_VERSION: 10.0.19041.1134

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 37

FAILURE_BUCKET_ID: 0x1E_c0000005_R_volmgr!VmpQueryUniqueIdInternal

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {515c07ee-d3f8-30ee-6541-262110c9e06e}

Followup: MachineOwner
---------[/CODE]
 
Sanırım siz mining sisteme yükleyecektiniz. Pardon.
Microsoft Windows volume Manager extension driver olarak geçiyor dosya. Sistem dosyalarında bozukluk olabilir ya da eksik güncelleme olabilir. Bu komutla dosyaları taratın bozuk olan varsa onarılacak:

Kod:
sfc/scannow

Bunu uygula.

Sürüm nedir?
2. Hata aynı... Ses sürücüsü ile alakalı.
1614607980464.png
Ekstra bir şey yapmam lazım mı?
Sürüm 20H2.
 

Yeni konular

Geri
Yukarı