bsdsysadmin
asked on
System Thread Exeption not handled error occurs after reboot when I run the SCCM image capture wizard.
I'm trying to capture an image of 32-bit Windows 7. My prepared machine is on a VMware Workstation VM using VMware version 7.1.6. The host machine is a Dell Presision 7810 with 2 Intel Xeon E-2603 v3 processors, 24Gb of ram, running 64-bit Windows 7. After running the Image Capture Wizard and the machine reboots, I get the error "System_Thread_Exeption_no
<iframe width="420" height="315" src="https://www.youtube.com/embed/3Bkim24yn2s" frameborder="0" allowfullscreen></iframe>ASKER
Adam,
Thank you for replying. Tried both suggestions in your post. The first suggestion changing the VM to a 64 bit machine in the settings did not work. The only difference with it was that the error change to "UNEXPECTED_KERNEL_MODE_TR
Thank you for replying. Tried both suggestions in your post. The first suggestion changing the VM to a 64 bit machine in the settings did not work. The only difference with it was that the error change to "UNEXPECTED_KERNEL_MODE_TR
How much memory is allocated to the VM? 4GB should be a safe bet.
Also, are you leaving the VM integration tools in the image before capture? If so, trying removing them before the capture.
Also, are you leaving the VM integration tools in the image before capture? If so, trying removing them before the capture.
ASKER
Adam,
Thank you for responding. I've had the VM set at 2GB and later at 4GB. I've tried removing the integration tools without any luck there either. I've included a smsts.log file and a screenshot of the contents of the C:\ drive.
root-of-C-on-capture-machine.jpg
smsts.log.txt
Thank you for responding. I've had the VM set at 2GB and later at 4GB. I've tried removing the integration tools without any luck there either. I've included a smsts.log file and a screenshot of the contents of the C:\ drive.
root-of-C-on-capture-machine.jpg
smsts.log.txt
I'm out of ideas. I do have a base image based on Windows 7 x86 that I've successfully captured/sysprepped using HyperV. Nothing fancy...just the standard fare of Office, ESET, 7zip, etc.
ASKER
Thanks for trying.
I've requested that this question be deleted for the following reason:
The question has either no comments or not enough useful information to be called an "answer".
The question has either no comments or not enough useful information to be called an "answer".
ASKER
Please reinstate this thread. I found the answer and wish to share it.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found the solution without any help from the Experts Exhange community.
Could be of some use?
The other thing you can try is when WinPE is booting, it should dump all logs of its actions to C:\MININT\SMSOSD\OSDLOGS. Try getting to the C drive (may have to use another WinPE disc to do this) and see if you can copy off the logs and inspect them. Then you can open them with Trace32 from SCCM or notepad (Trace32 will be easier to read).