[Bug 221828] New: Windows 11 blue screen 0xc0000185 when using disk cache none on newer kernels

[Bug 221828] New: Windows 11 blue screen 0xc0000185 when using disk cache none on newer kernels

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=221828

            Bug ID: 221828
           Summary: Windows 11 blue screen 0xc0000185 when using disk
                    cache none on newer kernels
           Product: Virtualization
           Version: unspecified
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: kvm
          Assignee: virtualization_kvm@kernel-bugs.osdl.org
          Reporter: samuilsgames@protonmail.com
        Regression: No

Dear Linux developers,

I have noticed an odd bug that makes Windows 11 crash early during boot with
error code 0xc0000185:
1. Create a QEMU/KVM guest with the Windows 11 preset
2. Change cache mode to none for the the virtual disk the guest OS is installed
to
3. Install the OS
4. On the first, the error code appears.

Changing the cache mode back to writeback (QEMU's default), the blue screens
don't happen anymore. I kept virt-manager's defaults everywhere else. Another
workaround was downgrading Linux from 6.18.41 to 6.12.100. The problem also
happens on Linux 7.1.5. NixOS makes it hard to install EOL kernels, so I
haven't tested which minor release actually added the regression. Lastly,
Windows 10 doesn't seem to be affected and GNU/Linux distros for that matter.

My setup is this:
CPU: AMD Ryzen 7 3700X
Host OS: NixOS unstable
Host Kernel: Linux 6.18.41
Host FS: F2FS
QEMU: 11.0.2
Guest OS: Windows 11 Pro (25H2), Windows 11 IoT Enterprise LTSC (24H2)


Is this a known issue? I couldn't find anything on it. Are there any logs I can
post? Thanks in advance!

Best regards,
Samuil

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 221828] Windows 11 blue screen 0xc0000185 when using disk cache none on newer kernels

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=221828

Samuil P. (samuilsgames@protonmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Regression|No                          |Yes

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 221828] Windows 11 blue screen 0xc0000185 when using disk cache none on newer kernels

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=221828

Samuil P. (samuilsgames@protonmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|                            |6.18+

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

[Bug 221828] Windows 11 blue screen 0xc0000185 when using disk cache none on newer kernels

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=221828

The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |regressions@leemhuis.info

--- Comment #1 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@leemhuis.info) ---
(In reply to Samuil P. from comment #0)
> Is this a known issue?

Hard to say. Wonder if it might be the problems this fixes:
https://lore.kernel.org/all/20260720201057.1862857-1-kbusch@meta.com/

Or just a timing issue.

Maybe a developer will show up with an idea what's wrong. But if that doesn't
happen in the next few days you most likely will have to run a git bisection to
see where the problem is coming from:
https://docs.kernel.org/admin-guide/bug-bisect.html

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.