BSOD installing Windows on empty drive

For this post, no extended post was written because no dump could be provided.
Additionally, for this kind of troubleshooting another computer that can be used for testing is recommended but not required. This is only the case if the DOS tests don’t give any errors.

The problem description:
i just completed a new computer build with a i3-6100 and a gtx760 with an msi h110m mobo and 8gb of gbmicro ddr4 single stick.

Now i need to install windows 10 on a EMPTY hard drive without any os(the hard drive is not brand new but its still very usable), and at like 25% the install crashes every time with a kernel security failure what the heck am i supposed to do ?

i am using a usb drive to boot the windows 10 install

Link: BSOD Kernel security check failure on EMPTY hard drive

For the 0x139 Kernel Security Check Failure BSOD I cannot yet say from my own experience what possible causes could be, because relatevily spoken I haven’t seen this BSOD much.

As many others may do, the first step of troubleshooting I took was ruling out as much as possible causes, like drivers, program issues, setting issues, a.ka. the software.
Even though it is obvious that software may unlikely be a possible cause, I did this to create a list of the most likely possible causes, namely the parts of the hardware.
As most of the hardware was brand new, a first thought would be that either of the parts could be faulty.

So, having in mind that the user cannot use its current system and that some hardware tests are Windows application, I ordened the troubleshooting steps to perform in order of DOS based tests to tests that need to be performed on a different system.

A quick breakdown of the parts with software tests.
1. RAM, built-in Windows Memory test, MemTest86+.
– MemTest86+ is usually better, but from time to time the built-in Windows Memory test is able to find bad RAM.
2. HDD, SeaTools, HDTune and the built-in chkdsk.
3. GPU, Furmark
4. CPU, Prime95 and IntelBurnTest

  • Memory,
    Many will say that MemTest86+ is usually better, but from time to time the built-in Windows Memory test is able to find bad RAM too. Still it is recommmended to run MemTest86+.
  • HDD/SSD,
    – SeaTools is both a Windows application and a DOS based test, it is recommended to use the DOS based version because the test is then capable of scanning the whole drive without any issues due to interference of other software.
    – HDTune is a Windows application, I suggest it due to its capability of checking the SMART, scanning for bad blocks and performing a benchmark. HDTune can be used on both SSD’s and HDD’s.
    – Chkdsk is a DOS based test, it is recommended to run this utility with the command swith /r. Doing so will let chkdsk attempt to fix any corruption it can find in the file system and replace bad sectors if possible.
  •  GPU,
    Furmark is a Windows application, Furmark is a program that stresses the GPU in a way that causes the temperature to rise very quickly. With this program you can identify cooling issues and bad GPU’s.
  •  CPU
    Prime95 is a Windows application that stress tests the CPU, it is similar to Furmark with the only difference that I’ve never seen Furmark giving errors.

These 4 parts can be tested through software, all other parts such as the PSU, motherboard, cabling, etc., can only be tested by replacement.

The troubleshooting steps suggested were only the first 2 of the breakdown, because
– they are (mostly) DOS based tests,
– I didn’t want the user to do too much immediately and lastly
– the memory test showed errors after the first pass.
Fortunately the user ran the test twice in different slots before reporting back the results, but since there was only a single stick another system was required for testing to find out if the single stick or the motherboard itself was bad.
Unfortunately I don’t know if the RAM itself was bad or the motherboard, because the user hasn’t reported back the result of the last troubleshooting steps.

This concludes the blog post.

Leave a Reply

Your email address will not be published. Required fields are marked *