-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabled DUP PROFILE btrfs cause BSoD #15
Comments
Thank you, I'll look into it. |
Getting the same thread error, corrupted my partition of Mageia 5, didn't have anything important on there, so it isn't a problem. New to Window however, but how would I go about uninstalling the driver from the recovery command prompt? |
Does this work for you? reg add HKLM\SYSTEM\CurrentControlSet\Services\btrfs /v DebugLogLevel /d 4 /f |
I believe I've fixed the crash: 9473ef7 There's another issue, which is that it's not letting you create files longer than one chunk, which I'm working on. |
I've just released version 0.5, can you please see if it fixes your problem? |
Thank you for fixing. |
Fantastic. Thank you for reporting it. |
Using Linux: SystemRescueCd 4.7.2(Linux sysresccd 3.18.29-std472-amd64)
Using Windows: Windows 10 1511 x86, Windows 7 SP1 x64
BSoD has occurred in a high probability the following procedure.
Then, repeat copy file to btrfs volume or above fsutil.
Windows died with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED or BAD_POOL_CALLER.
btrfs.log(10 x86, DebugLogLevel=2, I could not set DebugLogLevel=3, because cause KMODE_EXCEPTION_NOT_HANDLED at loading driver.)
btrfs.log(7 x64, DebugLogLevel=3)
The text was updated successfully, but these errors were encountered: