How to fix a win32kfull.sys BSOD error during Windows 10 installation

DAV 1 Reputation point
2022-08-27T20:34:08.68+00:00

I am trying to install Windows 10 on my new system. Motherboard is an MSI B550. The only thing connected is an SSD, a SATA DVD with the install disc, and a video card. When I start by selecting the language and keyboard layout, I get the following failed win32kfull.sys BSOD. Everything I find in support and in forums say to uninstall the problem software, to update drivers, or to reinstall and problem software. Haha. I haven't even installed anything. How can I update the windows driver if I can't install windows?

Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,919 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Docs 15,491 Reputation points
    2022-08-28T04:53:19.353+00:00

    1) Run Memtest86 (free version) for two tests of four passes (total eight passes) and post share links into this thread using one drive, drop box, or google drive.

    https://www.memtest86.com/

    Take pictures and post share links into this thread using one drive, drop box, or google drive.

    Just one error is a test fail and you can abort testing.

    Memtest86 can run overnight.

    Memtest86 has a feature to create text reports.

    If possible, include the text reports with the images in the share links.

    2) Report into this thread

    a) motherboard model and version
    b) CPU
    c) RAM part numbers

    3) Indicate whether the RAM modules are or are not on the Qualified Vendor List (QVL)

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments