none
BSOD after running sysprep in Windows server 2008 R2 SP1 if Group policy feature is installed.

    Question

  • On running Sysprep on Windows server 2008 R2 SP1 machine in which Group Policy feature is installed I'm getting BSOD. This is not happening in Windows 2008 R2 without SP1.

    Can anyone please let me know why this is happening and if there is any fix for this?

    Tuesday, August 30, 2016 2:28 PM

All replies

  • Hi,

    Thanks for your post.

    Is it a clean installation?

    What's the detailed BSOD errors?

    Please refer to the following articles to know more information about troubleshooting BSOD issues:

    Troubleshoot "blue screen" or Stop error problems before you contact Microsoft Support

    https://support.microsoft.com/en-us/kb/3106831

    Use debugging tools:

    http://msdn.microsoft.com/en-us/windows/hardware/gg463009.aspx

    How to read the small memory dump file that is created by Windows if a crash occurs

    http://support.microsoft.com/kb/315263/en-us

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, August 31, 2016 8:38 AM
    Moderator
  • Thanks for your reply.

    This is freshly created VM on Hyper-V host. After windows installation I installed group policy feature and ran sysprep on it.

    Boot error is 0x0000007B (0xFFFFF880009A97E8, 0xFFFFFFFFC0000043, 0x0, 0x0). This error does not create any dump.

    After the boot I followed a link in which it is mentioned to change the value of following keys before boot,

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\DisableCDDB
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\DontStartRawDevices

    I did that but no result.

    Let me know if you need any other details

    Friday, September 02, 2016 6:02 AM
  • Hi,

    According to my research, STOP 0x0000007B errors may be caused by device driver issues (especially those related to hard drive and other storage controllers), viruses, data corruption, and sometimes even hardware failures.

    Check the troubleshooting steps mentioned below:

    http://hubpages.com/technology/Fix-0x0000007B-Windows-Stop-Error-BSOD

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best Regards,

    Alvin Wnag


    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, September 05, 2016 8:55 AM
    Moderator
  • Hi,

    This is a newly created machine and before running sysprep it machine was booting up fine.

    I went through the link and this is not helping me as my setup was brand new. Let me know if I'm missing something.

    Could it be possible for you to provide me any other lead?

    Thanks,

    Vikash.

    Tuesday, September 06, 2016 9:46 AM
  • Hi Vikash,

    I did some research about your specific scenario and cannot find any useful information about it.

    To know the root cause of the issue, it usually needs advanced troubleshooting steps to isolate the problem. I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue. In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below:

    Global Customer Service phone numbers 

    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers/en-au?wa=wsignin1.0

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Thursday, September 08, 2016 9:05 AM
    Moderator