• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

BSOD after image with FOG on Optiplex 9010s

Scheduled Pinned Locked Moved
Windows Problems
3
10
1.5k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B
    bc601
    last edited by May 8, 2018, 7:25 PM

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

    0_1525807472847_c671eec8-9d8e-441a-8f9a-921b48e59156-image.png

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by May 8, 2018, 7:33 PM

      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.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 1
      • B
        bc601
        last edited by May 8, 2018, 7:35 PM

        @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

        G 1 Reply Last reply May 8, 2018, 7:39 PM Reply Quote 0
        • G
          george1421 Moderator @bc601
          last edited by george1421 May 8, 2018, 1:40 PM May 8, 2018, 7:39 PM

          @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]).

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          T B 2 Replies Last reply May 8, 2018, 7:42 PM Reply Quote 1
          • T
            Tom Elliott @george1421
            last edited by May 8, 2018, 7:42 PM

            @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.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

            G B 3 Replies Last reply May 8, 2018, 7:44 PM Reply Quote 0
            • G
              george1421 Moderator @Tom Elliott
              last edited by george1421 May 8, 2018, 1:45 PM May 8, 2018, 7:44 PM

              @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?

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              1 Reply Last reply Reply Quote 0
              • B
                bc601 @Tom Elliott
                last edited by May 8, 2018, 7:45 PM

                @tom-elliott

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

                1 Reply Last reply Reply Quote 0
                • B
                  bc601 @Tom Elliott
                  last edited by May 8, 2018, 7:53 PM

                  @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

                  1 Reply Last reply Reply Quote 0
                  • B
                    bc601 @george1421
                    last edited by May 8, 2018, 7:59 PM

                    @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

                    1 Reply Last reply Reply Quote 0
                    • B
                      bc601
                      last edited by May 9, 2018, 2:37 PM

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

                      1 Reply Last reply Reply Quote 0
                      • 1 / 1
                      1 / 1
                      • First post
                        7/10
                        Last post

                      160

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project