SYSTEM_SERVICE_EXCEPTION booting 11082 from VHDX


  1. Posts : 5,478
    2004
       #1

    SYSTEM_SERVICE_EXCEPTION booting 11082 from VHDX


    I have upgraded 10586 VM to 11082. This worked fine running under hyper-v but the second time booting natively from vhdx it failed with SYSTEM_SERVICE_EXCEPTION BSOD. It will also not boot into safe mode and can not be repaired using the "reset this PC" option at boot

    I therefore did a clean install of 11082 in VHDX. It installs correctly and boots to desktop however first reboot it gives the same error.

    After failing to native boot the same error occurs trying to boot the vhdx in hyper-v

    I mounted the VHDX and no .dmp files have been produced and the only drivers installed were these by the installation.
    Code:
    PS C:\WINDOWS\system32> get-windowsdriver -path f:\
    
    
    Driver           : oem0.inf
    OriginalFileName : f:\Windows\System32\DriverStore\FileRepository\prnms009.inf_amd64_50873edc4c2c7eff\prnms009.inf
    Inbox            : False
    ClassName        : Printer
    BootCritical     : False
    ProviderName     : Microsoft
    Date             : 6/21/2006 12:00:00 AM
    Version          : 10.0.11082.1000
    
    Driver           : oem1.inf
    OriginalFileName : f:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_8f8f9a87b92bfa30\prnms001.inf
    Inbox            : False
    ClassName        : Printer
    BootCritical     : False
    ProviderName     : Microsoft
    Date             : 6/21/2006 12:00:00 AM
    Version          : 10.0.11082.1000
    
    
    
    PS C:\WINDOWS\system32>
    Any idea how to proceed or does 11082 not support native boot of vhdx?

    EDIT: reinstalled 1511 and it works fine so definitely appears to be a 11082 problem. Would be interesting if it works for anyone else.
    Last edited by lx07; 25 Dec 2015 at 07:28. Reason: 1511 works
      My Computer


  2. Posts : 486
    Windows 10x64 17713
       #2

    lx07 said:
    EDIT: reinstalled 1511 and it works fine so definitely appears to be a 11082 problem. Would be interesting if it works for anyone else.
    Version 1511 is 11082 so that's a little confusing. Regardless, I installed 11082 on a vhdx file and booted it up several times without incident. Appears to still be supported.
      My Computer


  3. Posts : 5,478
    2004
    Thread Starter
       #3

    cyberrufus said:
    Version 1511 is 11082 so that's a little confusing. Regardless, I installed 11082 on a vhdx file and booted it up several times without incident. Appears to still be supported.[/
    1511 version is build 10586 released end of November. 11082 is the new insider build released last week.

    Did you native boot it? I'm not talking about running in a VM which works fine.

    If so it is interesting it works for you and not me. What does your vhdx contain? I'm using a hyper-v generation 1 disk containing just a windows partition like in the picture below (I'm running 1511 again now).

    I've not tried making a generation 2 (EFI) disk yet but clean install of 10586 worked when clean install of 11082 didn't using the old mbr style disk.

    SYSTEM_SERVICE_EXCEPTION booting 11082 from VHDX-capture.png
      My Computer


  4. Posts : 486
    Windows 10x64 17713
       #4

    lx07 said:
    1511 version is build 10586 released end of November. 11082 is the new insider build released last week.
    SYSTEM_SERVICE_EXCEPTION booting 11082 from VHDX-1511-1.png SYSTEM_SERVICE_EXCEPTION booting 11082 from VHDX-1511.png

    Both are showing up as 1511 here. I just burned (with DISM) install.wim from 11082 into a .vhdx file and native booted it. I only rebooted twice after the initial installation but didn't have any issue.
      My Computer


  5. Posts : 5,478
    2004
    Thread Starter
       #5

    cyberrufus said:
    Both are showing up as 1511 here. I just burned (with DISM) install.wim from 11082 into a .vhdx file and native booted it. I only rebooted twice after the initial installation but didn't have any issue.
    Ah yes, you are right. Thanks for trying - I'll give it a go with DISM - I was installing on Hyper-V and then native booting the VHDX after it had installed.

    First time it boots (and says getting devices ready), second time it fails....
      My Computer


  6. Posts : 5,478
    2004
    Thread Starter
       #6

    The problem was rdyboost.sys (the.dmp files were under Windows directory on host install not Windows directory in the vhdx for some reason).

    Clean installed, disabled superfetch, installed chipset drivers, rebooted, enabled superfetch again, rebooted and it was OK. Didn't have to do this with previous build though...
      My Computer


  7. Posts : 5,478
    2004
    Thread Starter
       #7

    After upgrade to 11099 the same problem with the same dump produced.

    This time I can't get around it. I can upgrade through VM (obviously you can't upgrade VHDX) but can't boot it - it goes into the same boot loop.

    I have tried so far:

    • Upgrading a Gen 2 vhdx to 11099. Fails on second native boot.
    • Clean installing 11099 in Hyper-V (both gen 1 and 2) and then booting native. In both cases fails on second native boot.
    • Clean installing Windows 7 and upgrading in Hyper-V. Fails on second native boot.
    • Disabling PreFetch and SuperFetch (by updating registry after failure as this worked in last build).
    • checking ahci is set to 0 (in case changing from VM to SSD make a difference at boot time but they were already set to 0)
    • Clean installing 10586 (works fine)

    If possible could someone who has installed 11099 in Hyper-V just see if it boots native as it will stop me wasting more time on this if it really is just a bug. Do note it will (as far as I can tell) stop your hyper-v vm booting at all after so it is quite an ask.

    I do have a theory it might be due to achi (although I'm not at all sure) so please say if you are native booting on ssd or not - I am.

    Also if you can think what else I can try do please say.

    hali

    011516-15515-01.zip
    Last edited by lx07; 15 Jan 2016 at 08:19. Reason: Added dump file
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:28.
Find Us




Windows 10 Forums