Causing a bluescreen
Opened this issue · 3 comments
HarukaB commented
My pc won't start if any ext4 drive is plugged in. Additionally if I plugged the drive in after the system has booted. the system will bluescreen within a minute(I guess this happens on any I/O requests to the drive)
WinDbg Analyze report:
19: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CACHE_MANAGER (34)
See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000000ffb
Arg2: ffffffffc0000420
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1514
Key : Analysis.Elapsed.mSec
Value: 8141
Key : Analysis.IO.Other.Mb
Value: 3
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 23
Key : Analysis.Init.CPU.mSec
Value: 483
Key : Analysis.Init.Elapsed.mSec
Value: 75083
Key : Analysis.Memory.CommitPeak.Mb
Value: 89
Key : Bugcheck.Code.LegacyAPI
Value: 0x34
Key : Bugcheck.Code.TargetModel
Value: 0x34
Key : Failure.Bucket
Value: 0x34_Ext2Fsd!unknown_function
Key : Failure.Hash
Value: {d6b02b24-f817-028e-a9ae-bedd31d4eaf2}
Key : Hypervisor.Enlightenments.ValueHex
Value: 7417df84
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 55185662
Key : Hypervisor.Flags.ValueHex
Value: 34a10fe
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 3f7
Key : WER.OS.Branch
Value: ge_release
Key : WER.OS.Version
Value: 10.0.26100.1
BUGCHECK_CODE: 34
BUGCHECK_P1: ffb
BUGCHECK_P2: ffffffffc0000420
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 070124-25718-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
EXCEPTION_RECORD: ffffffffc0000420 -- (.exr 0xffffffffc0000420)
Cannot read Exception record @ ffffffffc0000420
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
STACK_TEXT:
fffff688`fe71eb18 fffff804`9c91b74f : 00000000`00000034 00000000`00000ffb ffffffff`c0000420 00000000`00000000 : nt!KeBugCheckEx
fffff688`fe71eb20 fffff804`9c852df5 : ffffce88`f3475630 fffff688`fe71ec78 ffffce88`f37b0010 ffffce88`f34755d0 : nt!CcDeleteBcbs+0x147
fffff688`fe71eb90 fffff804`9c8526b0 : ffffce88`dc9cd820 ffffce88`f34755d0 fffff688`fe71ecc0 ffffce88`dc9cd820 : nt!CcDeleteSharedCacheMap+0x155
fffff688`fe71ec40 fffff804`319520a0 : ffffce88`f376c500 fffff688`fe71ed68 ffffce88`f376c500 00000000`00000000 : nt!CcUninitializeCacheMap+0x3a0
fffff688`fe71ed00 ffffce88`f376c500 : fffff688`fe71ed68 ffffce88`f376c500 00000000`00000000 ffffce88`f37a41b0 : Ext2Fsd+0xc20a0
fffff688`fe71ed08 fffff688`fe71ed68 : ffffce88`f376c500 00000000`00000000 ffffce88`f37a41b0 fffff804`9ca13a0a : 0xffffce88`f376c500
fffff688`fe71ed10 ffffce88`f376c500 : 00000000`00000000 ffffce88`f37a41b0 fffff804`9ca13a0a 00000000`00000000 : 0xfffff688`fe71ed68
fffff688`fe71ed18 00000000`00000000 : ffffce88`f37a41b0 fffff804`9ca13a0a 00000000`00000000 00000000`f3060001 : 0xffffce88`f376c500
SYMBOL_NAME: Ext2Fsd+c20a0
MODULE_NAME: Ext2Fsd
IMAGE_NAME: Ext2Fsd.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: c20a0
FAILURE_BUCKET_ID: 0x34_Ext2Fsd!unknown_function
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {d6b02b24-f817-028e-a9ae-bedd31d4eaf2}
Followup: MachineOwner
---------
HarukaB commented
i suspect the problem is because of a broken partition table, because i tried to adjust the partitions on the disk but somehow that software crashed, before that the issue does not exist.
bobranten commented
Can you send the dump file so I can try it in WinDbg.
Bo Branten
HarukaB commented
Sure, Here:
070124-25718-01.dmp