Fresh install of Win8.1 BSOD after installing first batch of Security Updates

Discussion in 'Windows 8' started by doveman, Jan 17, 2015.

  1. doveman

    doveman MDL Member

    Apr 22, 2010
    208
    9
    10
    I've already got Win8.1 Enterprise x64 running on my system but I didn't do a fresh install when I switched from an AMD to Intel motherboard and it's quite cluttered anyway, so I decided to do a fresh install now to see if it clears up a few problems.

    I've only got one SSD and can't face running from HDD again but there's sufficient space on my SSD's 2nd partition (which I use for games) to create a VHD and install Windows in that, so that's what I did.

    I've installed the drivers from the Asus site for my Z97-A and all drivers that Windows Update finds and it boots fine after that but if I then install just the Security updates (as opposed to the Updates for Windows) it BSOD on the next boot.

    It's a pain using system restore to get it working again as well, as there doesn't seem to be anyway to access that from the Windows Boot Menu. I think I managed to once by pressing Shift+F11 but even after attaching the VHD with diskpart, it said it was unable to find the boot/recovery store (something like that anyway), so the only way I've found to do it is to use Virtualbox to attach the VHD and Windows DVD.

    It's also a bit annoying that whenever I select the VHD from the Windows Boot Menu it has to reboot my PC and then it boots into the VHD. It doesn't have to reboot when I select the 'normal' Windows. I don't know if it's because I boot into grub4dos first and then load the Windows Boot Menu with this:

    titleWin8.1 (SSD)
    unhide (hd0,0)
    root(hd0,0)
    chainloader/bootmgr

    but I don't really see how that could cause it, so I guess it's just how Windows works.

    Anyway, does anyone know if the KMS hack could cause Windows to BSOD after installing the Security Updates? I can't say exactly which hack it is I'm using, just that the ISO I'm using is "Win81AIOFeb2014.iso" and it offers KMS and non-KMS installs for all the versions of Win 8.1 to install.
     
  2. EFA11

    EFA11 Avatar Guru

    Oct 7, 2010
    8,795
    6,762
    270
    although I do not know what KMS solution is being offered with that home brewed iso, KMS solutions such as MTK(Microsoft Toolkit) and KMSpico run an emulated server and neither would have any effect on boot or loading windows as they are run after windows is already started. There are also other KMS solutions for non-windows platforms too.

    Windows Loader for Win7 etc does load into an MBR and then windows loads, but that isn't the case with anything for Win8.x. I would try an untouched ISO of 8.1 Enterprise using one of the above tools to activate after it is installed, just to ensure it isn't something else other than the install itself from that home brewed ISO.
     
  3. doveman

    doveman MDL Member

    Apr 22, 2010
    208
    9
    10
    Having had a look, this was using a server emulator service as well. I've uninstalled it (using the script in Windows/KMS)and will try doing the Security Updates again and then install KMSPico, which is what I'm using on my working install of Win 8.1.

    It did make a minidump, which I looked at with BlueScreenView but it doesn't tell me much other than the bug was CRITICAL_PROCESS_DIED and it was caused by ntoskrnl.exe. I've attached it in case someone else can decipher it further and advise what the problem appears to be though.

    Otherwise I'll try a clean ISO as you suggest but I'd rather try and work out what the problem is if possible, as assuming there's nothing other than the KMS server added to this ISO, which I suspect as it does offer a non-KMS option to install as well, than I'm likely to encounter the same problem after starting from scratch, although I guess if I make a System Image with Macrium Reflect first, then I can just restore that if that happens, so I won't have to waste too much time.
     

    Attached Files:

  4. doveman

    doveman MDL Member

    Apr 22, 2010
    208
    9
    10
    #4 doveman, Jan 19, 2015
    Last edited by a moderator: Apr 20, 2017
    (OP)
  5. doveman

    doveman MDL Member

    Apr 22, 2010
    208
    9
    10
    Hmm, well I did the big 800+MB update and after that Windows fails to boot at all, I think the error referred to system32/cng.sys

    I'll download a clean ISO of the August update and try installing from that next.
     
  6. doveman

    doveman MDL Member

    Apr 22, 2010
    208
    9
    10
    I used the clean ISO of Enterprise to start the install in Virtualbox and then booted the VHD and finished it off, first installing the Security Updates, then the Updates for Windows and then the drivers and it's all working fine now :)