Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Bluescreen when booting LiteTouchPE_x86.wim

Answered Bluescreen when booting LiteTouchPE_x86.wim

  • Wednesday, October 17, 2012 10:20 AM
     
     
    Sign In to Vote
    0

    Hi, 

    im using MDT 2010 to capture a Windows 7 x86 Pro Installation. I have added several Drivers to my DS since i will be deploying to a number of different Machiene types.

    After PXE booting the Capture TS i get a Bluescreen. Screenshot attached.

    I assume it is a bad driver. If so, how can i find out which one it is?

    Thanks so much!MDT_Bluescreen

     

All Replies

  • Wednesday, October 17, 2012 11:16 AM
     
     Answered
    Sign In to Vote
    0

    By definition:

    Check 0x7F: UNEXPECTED_KERNEL_MODE_TRAP
    0x0000000D -- An exception not covered by some other exception; a protection fault that pertains to access violations for applications

    Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
    A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

    So it sounds like a driver is causing the exception and unfortunately is not raised immediately but caught later perhaps by CPU as protection, therefore nothing is named on the screen as culprit.

    Are you getting this in Windows PE?  You PXE boot the client and before MDT ever runs you can't get that far because of the exception in Windows PE?  If so, I would start but removing driver groups that you have recently added to PE in the Workbench.  Regenerate boot images and try be error until you can identify which driver is the problem.

    It is possible to debug WinPE but its complicated where you would need to customize PE to enable debug feature and attach kernel debugger via serial port. Trial and error may be easiest method to track it down.

    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog

    • Marked As Answer by Ben73s Thursday, October 18, 2012 6:57 AM
    •  
     
  • Wednesday, October 17, 2012 12:13 PM
     
     
    Sign In to Vote
    0
    This happens if u had run the task sequence and stopped abnormaly.

    Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

     
  • Thursday, October 18, 2012 6:57 AM
     
     
    Sign In to Vote
    0
    Thanks! That solved my Problem. It was a faulty Storage Driver causing the Bluescreen. Was able to disable all Storage Drivers for the PE Image. Then the bluescreen was gone. Since there werent that many Storage Drivers i could disable one after the other until i found the bad one.