PC going backwards never gets to the same place with this disc

Discussion in 'DIY Computers' started by dave, Jul 16, 2011.

  1. dave

    dave Guest

    The problem is best descibed as a list of events I think:-

    PC A boot & works ok.
    Removed disc and put in in PC B
    PC B boots & works fine.

    Put same disc back in PC A - BSOD!

    Put disc back in PC B again - boots and works fine

    Put disc back in PC A - BSOD (again)

    Restored images (verified as ok) onto disc.
    PC A *still* bsods!!

    Restored track zero and MFT
    PC A still BSODs

    Looks to me like PC A has developed a fault?
    Do you think that is a good bet as to the fault?

    ps These are not my machines - trying to help someone out but have run
    out of idea.
    dave, Jul 16, 2011
    1. Advertisements

  2. dave

    > Guest

    The problem would be better described if sufficient information was given

    Are both PC's hardware identical
    Are they new builds
    What error code is given with the BSOD's
    Did both PC's ever work
    >, Jul 16, 2011
    1. Advertisements

  3. Can you run PC A from any sort of 'live' disk, e.g. MemTest86+, UBCD4W or
    Puppy Linux?

    Phil, London
    Philip Herlihy, Jul 16, 2011
  4. dave

    dave Guest

    There is always "more information".
    Not really relevant to problem as described
    Not really relevant to problem as described
    (sigh) do you know much about bsods? Anyway Not really relevant to
    problem as described.
    Yes - would have mentioned it otherwise
    I see you have no idea either then,.

    PC A has blue case PC B a white one

    dave, Jul 16, 2011
  5. dave

    dave Guest

    Good suggestion there Phil - will pass that on for him to try. I have
    linux Live CD already.
    dave, Jul 16, 2011
  6. Although this isn't the fault, it's somewhat dodgy doing this with
    Windows disks - Windows tries to adapt to the hardware it's in, albeit
    not enough to be useful, but enough to trip up the hardware
    re-activation flag and sometimes to smoosh the boot sequence. Which is
    nice. So the disk may have been changed enough while in B, to not boot
    PC A is having some trouble.
    Yes. I should first unplug+replug everything inside A, in case you
    joggled something while moving the HD around.

    Then tear A down to minimal setup - motherboard, no disks, one stick
    of RAM, video card - and see whether it's happy in the bios. Then add
    the RAM, CD, and boot off a Linux liveCD or memtest86 CD.

    By the way, what were you trying to diagnose with the original disk

    Cheers - Jaimie
    Jaimie Vandenbergh, Jul 16, 2011
  7. It is totally relevant. The STOP message that comes with the BSOD is a
    vital clue as to might be wrong.

    If you won't proved that info, there is little anyone can do to help.
    Mike Tomlinson, Jul 16, 2011
  8. dave

    Adrian C Guest

    STOP 7B AKA inaccessible boot volume I suggest?

    Is this a SATA drive?

    If so, set the failing PC BIOS 'SATA Mode' to IDE or Emulation, or the
    other way(?). Too many variables past that to guess. Need more information.
    Adrian C, Jul 16, 2011
  9. dave

    > Guest

    I don't even see where he's said what the op. system is.
    Anyway can't be bothered now.
    >, Jul 16, 2011
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.