BSOD after image with FOG on Optiplex 9010s

[bc601]

BSOD after image on Optiplex 9010. Happens on every Optiplex 9010 I try and image. Has anyone seen this issue before ?!

[george1421]

What version of fog are you using?
What OS are you deploying?
What mode is the target in (uefi or bios/legacy)?
What mode is operating system?
Did you sysprep the system?
Is the right drivers installed on the master image?

The error is one of those generic, “Oh crap you have a problem” type of errors.

[bc601]

@george1421 said in BSOD after image with FOG on Optiplex 9010s:

m

hat version of fog are you using?Running Version 1.4.4
SVN Revision: 6077
What OS are you deploying? win 7
What mode is the target in (uefi or bios/legacy)? bios/legacy
What mode is operating system?bios/legacy
Did you sysprep the system? yes
Is the right drivers installed on the master image yes

PC has been imaging fine until last week

[george1421]

@bc601

So you haven’t refreshed your master image at all in the last 2 weeks?

When you say “PC has been imaging fine until last week” FOG imaged a 9010 successfully 3 weeks ago?

One thing that comes to mind is firmware. Is it possible that the systems that worked a few weeks ago had a different version of the bios?

When it blue screens, when does it do that? After OOBE, or when windows just starts (just as oobe get started)?

Have you tried different 9010s, or tried a new hard drive in the 9010 (thinking you might have a hard drive with a bad sector, the 9010s are 4 years old [guess]).

[Tom Elliott]

@george1421 another option is the image itself is corrupted, meaning a problem on the fog server, either memory or hdd issue, though I’d expect to see the problem during imaging not when the machine is trying to boot. In the case there is a problem with the image itself, has the machines been watched come back with an error or warning during imaging, potentially the reason the machine is in such a strange state.

I guess I’m trying to say, there’s so many variables in play.

[george1421]

@tom-elliott This is just a general question. If something happened during imaging, would the deploy task still be stuck in the active task list since it never made it to the end of the deploy sequence?

[bc601]

@tom-elliott

Thanks I think the image may be corrupted as well. How did it corrupted without any changes is suspicious

[bc601]

@tom-elliott

Also to note I have more then one image on the FOG machine. Every image that I try on the Optiplex 9010 only goes to BSOD.
When I image the Optiplex9020 the image works without a BSOD

[bc601]

@george1421 said in BSOD after image with FOG on Optiplex 9010s:

windows just starts

When windows just starts is when the BSOD happens I have tried 3 9010s

[bc601]

Found a work around. Found one old image that works. Thanks for you all help