Windows xp home advanced boot menu loop

OK, false alarm on finding the xp home edition cd...still looking....Currently I have attached the vista hdd to my pc via a sata to usb adapter and I am scanning it as a precaution and looking to see if I can find exactly what os in on it and a product key if I am able to.

You'll also need your Dell recovery disks to reinstall Windows. If you don't have them, post back and we'll have some suggestions.

Keeping this in mind in the event the xp home edition cd is not found and at this point I cannot get into vista via booting from the hdd. I am looking at the contents of the vista hdd now as it is hooked to my pc via usb but I do not know if I can retrieve anything of use from it.
 
Ok,

No xp home editions disc available....not 100% if the vista os on the hdd that seems good is home basic or premium or what and even if I found the appropriate disc I cannot read the key on the laptop .........Just completed a scan with mwb on the vista hdd via sata to usb while hooked to my pc and nothing detected.....I can see all the files on the vista hdd but nothing is needed to be saved.

Hey AA see ya lurkin there , hows it going?

4
 
Hello 4,
You didn't tell me you were over here. I just stumbled upon the very familiar username by accident!
You have been getting yourself into more strife, I see.
 
Well, my sister dropped this on me while you and I were working on my nephews win 7 issue.

I figured best not to bog you down with another one while we were doing so, so I started a thread over here for this one. They have about as many machines as I do and they always seem to be breaking down for one reason or another. Usually malware but this time it looks like a bad drive again. Perhaps my nephew brought a bug with him from NewYork...lol
 
Our friend, 4on4off, definitely manages to get around. :D

That doesn't sound so good when you put it like that. lol

I have always been a sucker for a chump in a slump but I find it to be a chance to learn and I find it most interesting for some strange reason.
 
If you keep this up, instead of helping your family & friends, before you know it we'll have you helping others on the forums.
 
If you keep this up, instead of helping your family & friends, before you know it we'll have you helping others on the forums.

That would be something to feel good about.

I use to have to rely on my buddy for the simpliest stuff and that one day I got beat down by a rogue av I started learning how to fend for myself and I can't get enough of it. Every time I turn around someone needs help with something and I feel some kind of enjoyment doing it.

I have come to realize tho that there is so much more to learn and the data recovery that AA helped me with and the issue being worked on here in this thread has opened another door beyond malware that the more I read about the more I want to read about.

Kind of scary really....lol
 
If you keep this up, instead of helping your family & friends, before you know it we'll have you helping others on the forums.
Yes, I anticipate that happening! That's how a lot of forum helpers get started I expect. It was the case with me.

4 has been exhibiting all the signs of being afflicted with a bad case of extreme geeekedness.
 
Have you run a hard drive test on the Vista hard drive? http://www.carrona.org/hddiag.html
If it passes, then the STOP 0x7B error is due to the Vista drivers
If it fails, then the STOP 0x7B error is due to the bad hard drive

It won't hurt (in either case) to try and install XP. But the Dell disks (for this system) will also contain the drivers that you need. BUT, you can also get the drivers from the Dell download site for most of the hardware.

I'd suggest contacting Dell for a copy of the recovery disks for this system.
That's the easiest and cheapest way IME.

If you know someone with a Dell that has XP on it - you can borrow their CD.
 
Last edited:
Rgr Tht,

Yes, I ran the hard drive test and the vista passed both the short and long.

Checking around trying to locate either a xp cd or a vista cd.

I got key for the xp cd as it is visible on the sticker but the vista is not.

Is there by chance a way I can pull this info from the vista hdd without being able to boot into it? I looked around while I had it hooked to my pc via the sata to usb cable but to no avail.

Thank you for your assistance. I will keep you posted as/if things progress from here.

4
 
Is there by chance a way I can pull this info from the vista hdd without being able to boot into it?
Yes, the Windows serial key can be retrieved quite easily from the hard drive without being able to boot to it .... if necessary.

Have you considered the possibility of cloning the bad hard drive to the good hard drive ???

Let's have a closer look at that "bad" hard drive to see what's actually going on there.

  • Boot to the UBCD CD > PartedMagic and open a terminal.
  • At the prompt, type:
  • fdisk -l
  • and press <ENTER>
  • Copy the text in the terminal window and paste in a reply.

Now use PartedMagic > GSmartControl to view the S.M.A.R.T. data and post the complete text of the report (remember to enclose in CODE tags when you paste it) or attach it to a post.

Let me know if you need help with any of that, but I think that you will already know all the details of how to go about it.
 
@ AA:

Rgr Tht,

Just got up from a graveyard shift and I got another tonight in an hour or so. I will see if I can get it done before I leave. If not, I will get it over the next day or two.
 
@usasma:

If it passes, then the STOP 0x7B error is due to the Vista drivers

Just curious, as a noob. If it is the Vista drivers keeping the vista hdd from booting normally do I have any options for resolving this and if so would I be able to get around needing the product key?

Since I do not have a cd for the specific version of Vista would I be able to get the drivers from the Dell website and get them on the Vista hdd somehow? Would it be possible to do that while it is attached via usb to my pc?
 
It's more than just a driver or two - it's all the drivers for hardware on the new system that isn't present in the older system.
While it's possible, it's a long, tedious, difficult process - and I've never done it myself.

What make and model system did the Vista disc come from?
What sort of license (OEM, Retail, etc) is the Vista installation?

Drivers are the least of your worries right now - we can find drivers if they're needed (in most cases).
 
It's more than just a driver or two - it's all the drivers for hardware on the new system that isn't present in the older system.
While it's possible, it's a long, tedious, difficult process - and I've never done it myself.

What make and model system did the Vista disc come from?
What sort of license (OEM, Retail, etc) is the Vista installation?

Drivers are the least of your worries right now - we can find drivers if they're needed (in most cases).



This is the laptop the Vista hdd is out of: http://support.gateway.com/s/Mobile/2007/Oasis/1015043R/1015043Rnv.shtml

This one had an issue with the connection for the power cord as the internal connection is soldered to the mother board. Sparks were flying...lol

Not sure if she bought it off ebay or one of the local stores so I am sure it was retail.
 
Is there by chance a way I can pull this info from the vista hdd without being able to boot into it?
Yes, the Windows serial key can be retrieved quite easily from the hard drive without being able to boot to it .... if necessary.

Have you considered the possibility of cloning the bad hard drive to the good hard drive ???

Let's have a closer look at that "bad" hard drive to see what's actually going on there.

  • Boot to the UBCD CD > PartedMagic and open a terminal.
  • At the prompt, type:
  • fdisk -l
  • and press <ENTER>
  • Copy the text in the terminal window and paste in a reply.

Now use PartedMagic > GSmartControl to view the S.M.A.R.T. data and post the complete text of the report (remember to enclose in CODE tags when you paste it) or attach it to a post.

Let me know if you need help with any of that, but I think that you will already know all the details of how to go about it.


Welcome - Parted Magic (Linux 3.0.0-pmagic)

root@PartedMagic:~# fdisk -l

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd0f4738c

Device Boot Start End Blocks Id System
/dev/sda1 * 63 234420479 117210208+ 7 HPFS/NTFS/exFAT
root@PartedMagic:~#

HTML:
smartctl 5.41 2011-06-09 r3365 [i686-linux-3.0.0-pmagic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     Fujitsu MHY BH
Device Model:     FUJITSU MHY2120BH
Serial Number:    K430T7B2B3EK
LU WWN Device Id: 5 00000e 0412e3d3f
Firmware Version: 0085000B
User Capacity:    120,034,123,776 bytes [120 GB]
Sector Size:      512 bytes logical/physical
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 3f
Local Time is:    Sat Aug 25 05:04:21 2012 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (  73)    The previous self-test completed having
                    a test element that failed and the test
                    element that failed is not known.
Total time to complete Offline 
data collection:         (  487) seconds.
Offline data collection
capabilities:              (0x7b) SMART execute Offline immediate.
                    Auto Offline data collection on/off support.
                    Suspend Offline collection upon new
                    command.
                    Offline surface scan supported.
                    Self-test supported.
                    Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine 
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      (  69) minutes.
Conveyance self-test routine
recommended polling time:      (   2) minutes.
SCT capabilities:            (0x003d)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   100   039   046    Pre-fail  Always   In_the_past 103079362477
  3 Spin_Up_Time            0x0003   100   100   025    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0032   095   095   000    Old_age   Always       -       104420
  5 Reallocated_Sector_Ct   0x0033   100   100   024    Pre-fail  Always       -       1 (1999, 1)
  9 Power_On_Hours          0x0032   093   093   000    Old_age   Always       -       223875
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       2096
191 G-Sense_Error_Rate      0x0012   100   100   000    Old_age   Always       -       557
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       242
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       33 (Min/Max 12/60)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       61142 (0, 2)
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       23245107691523
198 Offline_Uncorrectable   0x0032   100   100   000    Old_age   Always       -       233379432955907
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       18448116
200 Multi_Zone_Error_Rate   0x0032   100   100   000    Old_age   Always       -       71770488

SMART Error Log Version: 1
ATA Error Count: 12312 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 12312 occurred at disk power-on lifetime: 3731 hours (155 days + 11 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 2f 7d fc e6  Error: UNC at LBA = 0x06fc7d2f = 117210415

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c4 00 08 2f 7d fc e6 00      00:05:52.936  READ MULTIPLE
  c4 00 08 27 7d fc e6 00      00:05:52.933  READ MULTIPLE
  c4 00 08 1f 7d fc e6 00      00:05:52.930  READ MULTIPLE
  c4 00 08 17 7d fc e6 00      00:05:52.927  READ MULTIPLE
  c4 00 08 0f 7d fc e6 00      00:05:52.924  READ MULTIPLE

Error 12311 occurred at disk power-on lifetime: 3730 hours (155 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 2f 7d fc e6  Error: UNC 8 sectors at LBA = 0x06fc7d2f = 117210415

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 d8 08 2f 7d fc e6 00      00:01:07.652  READ DMA
  c8 d8 08 27 7d fc e6 00      00:01:07.652  READ DMA
  c8 d8 08 1f 7d fc e6 00      00:01:07.651  READ DMA
  c8 d8 08 17 7d fc e6 00      00:01:07.651  READ DMA
  c8 d8 08 0f 7d fc e6 00      00:01:07.651  READ DMA

Error 12310 occurred at disk power-on lifetime: 3730 hours (155 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 2f 7d fc e6  Error: UNC at LBA = 0x06fc7d2f = 117210415

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c4 d8 08 2f 7d fc e6 00      00:00:32.960  READ MULTIPLE
  c4 d8 08 27 7d fc e6 00      00:00:32.957  READ MULTIPLE
  c4 d8 08 1f 7d fc e6 00      00:00:32.954  READ MULTIPLE
  c4 d8 08 17 7d fc e6 00      00:00:32.951  READ MULTIPLE
  c4 d8 08 0f 7d fc e6 00      00:00:32.948  READ MULTIPLE

Error 12309 occurred at disk power-on lifetime: 3730 hours (155 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 08 2f 7d fc e6  Error: UNC at LBA = 0x06fc7d2f = 117210415

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c4 d8 08 2f 7d fc e6 00      00:00:28.215  READ MULTIPLE
  c4 d8 08 27 7d fc e6 00      00:00:28.212  READ MULTIPLE
  c4 d8 08 1f 7d fc e6 00      00:00:28.209  READ MULTIPLE
  c4 d8 08 17 7d fc e6 00      00:00:28.206  READ MULTIPLE
  c4 d8 08 0f 7d fc e6 00      00:00:28.203  READ MULTIPLE

Error 12308 occurred at disk power-on lifetime: 3730 hours (155 days + 10 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 56 72 70 28 e0  Error: UNC at LBA = 0x00287072 = 2650226

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  42 d0 00 c8 6f 28 e0 00      00:23:29.430  READ VERIFY SECTOR(S) EXT
  42 d0 00 c0 6f 28 e0 00      00:23:23.129  READ VERIFY SECTOR(S) EXT
  42 d0 00 a9 6f 28 e0 00      00:23:14.461  READ VERIFY SECTOR(S) EXT
  42 d0 00 56 6a 28 e0 00      00:23:03.461  READ VERIFY SECTOR(S) EXT
  42 d0 00 56 62 28 e0 00      00:23:03.445  READ VERIFY SECTOR(S) EXT

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: unknown failure    90%      3730         0
# 2  Short offline       Completed: read failure       90%      3713         117210415
# 3  Short offline       Completed without error       00%         1         -
# 4  Extended offline    Completed without error       00%         1         -
# 5  Short offline       Completed without error       00%         0         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

I hope that came out right.

Heading in for a 12 hour night shift.

4
 
Thank you: That will give me something to chew on while you are at work! :thumbsup2:
I am not entirely sure what might be going on with that hard drive .... ???

When you try to view the contents of the XP hard drive using PartedMagic, what do you see/what happens?
 
Back
Top