If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#16
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
All tests from WD come back with no Errors. I am currently doing a
full erase on the drive using the WD Utility. I am going to try to format it using another computer and see what happens. wrote: I swapped in a Seagate HD from a Dell that I am working on. It immediately gives a Blue Screen 0x00000007B. I am running a WD Hard Drive Test on it right now. |
Ads |
#17
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
|
#18
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
wrote:
All tests from WD come back with no Errors. I am currently doing a full erase on the drive using the WD Utility. I am going to try to format it using another computer and see what happens. I hate to rain or your parade, but testing a Seagate hard drive with a Western Digital diagnostic is nothing more than an exercise in futility. You need to use a Seagate diagnostic tool on a Seagate drive. -- Bruce Chambers Help us help you: http://dts-l.org/goodpost.htm http://www.catb.org/~esr/faqs/smart-questions.html They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin Many people would rather die than think; in fact, most do. -Bertrum Russell |
#19
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
It is a WD Hard Drive. If you read back you will find that I
temporarily swapped in a Seagate Drive from a Dell to see what errors came up. I hate to rain or your parade, but testing a Seagate hard drive with a Western Digital diagnostic is nothing more than an exercise in futility. You need to use a Seagate diagnostic tool on a Seagate drive. |
#20
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
I ignored your first post because 95% of that stuff had been covered
previously. I have used the recovery console, I have used FDISK, I have replaced the PS. fixboot, bootcfg, and fixmbr have been done. The partition is active. Please read through the other posts.......it sucks to repeat the same things over and over. It does not get to the point that I can go step-by-step unless a bootable CD is in the drive, and when that is the case it boots without problems, so that would be pointless. w_tom wrote: You are doing undesireable hardware swapping. WD diagnostic says drive hardware and computer interface hardware is OK. No reason to do any more hardware changes. None. CPU swapping could never be associated with this problem. WD diagnostic says drive is OK. So we move on to other usual suspects. In that other post were a long list of things to verify confirm without doing any changes. For example, since OS CD-Rom boots, then use the Recovery Console. Also use Disk Manager (remember the question about making the partition active that is set in Disk Manager)? Become familiar with Windows programs such as fixboot, bootcfg, and fixmbr. What is in the file BOOT.INI located in the root directory? Did you single step through the boot process by pressing F8 when boot first starts? Those voltage measurements with a 3.5 digit multipmeter are informative - can identify what creates strange unexplained problems even though disk diagnostic says OK. |
#21
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
Another thing I noticed is that it booted much faster with the Seagate
Drive. Typically it takes 30+seconds for the WD HD to detect, then another 30+ seconds for it to try to boot. It took about 5 seconds for both with the Seagate Drive. |
#22
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
Hi abright52,
You would not have gotten that Blue Screen, if the Seagate did not boot up. So, now after you finish formatting the WD Drive on another system and install the operating system on the Hard Drive and boot up the Hard Drive using the computer, you need to replace the CPU Processor. You already replaced the Motherboard. The CPU controls what gets written to the Hard Drive, thru programs. And the Boot Record recorded using that CPU Processor, could be corrupt, that the computer could not boot and you get the "Disk Boot Failure". Note, you will get the Blue Screen again, using the WD Hard Drive with a different motherboard, if it boots, when putting it back into the computer that was hit by lightning, just like the Seagate. You will need to reformat and reinstall the operating system using the motherboard and CPU Processor that the WD Hard Drive is going to run in. Question: Did you test the Memory / Ram Sticks using a different Motherboard that takes the same Memory Cards? -- thecreator wrote in message ps.com... All tests from WD come back with no Errors. I am currently doing a full erase on the drive using the WD Utility. I am going to try to format it using another computer and see what happens. wrote: I swapped in a Seagate HD from a Dell that I am working on. It immediately gives a Blue Screen 0x00000007B. I am running a WD Hard Drive Test on it right now. |
#23
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
These posts are not just for abright52. Posts are for all who also
have same problem. A little over half of those steps were already performed by abright52. But others were not executed - such as Disk Manager and contents of Boot.ini . There is no hardware problem. So the list of steps after a successful disk diagnostic is now shorter. Bios program loads a boot program from hard drive's first sector. This program then loads NTLDR, NTDETECT.COM, and BOOT.INI on root directly of that active partition. So either program on boot sector is defective, or those root directory files are missing, defective, etc, or data in BOOT.INI is wrong, or a CMOS parameter problem (not previously mentioned) exists. Of course others in the same situation would start with Recovery Console to fix these problems. Curious that Recovery Console did not do same on your WD disk. Disk Manager does fix some things including confirm that partition is active. And then additional suggestions are below. If FDISK wrote to the WD disk, then boot sector will be contaminated; must be overwritten. Another problem previously not mentioned is using wrong disk parameters in CMOS. CMOS parameters are only used during boot. Forgot the different names. However some may partially read the drive correctly and therefore not see every file. Meanwhile, booting from CD-Rom would correct that BIOS setting and read all files properly. Therefore a wrongly loaded CMOS parameter would only cause problems when booting from hard disk. Notice how many earlier tests (such as reading disk using DOS) are made unnecessary and no longer mentioned if using manufacturer's diagnostic. Diagnostic does not say CMOS parameters are correct, nor say that boot sector program and those root directory files are proper. Diagnostic does not even verify that BOOT.INI is correct. We only know that disk hardware is OK. What you have already done is listed not for you. What you have already done was listed so that all others will learn from this experience - those steps (unlike swapping a CPU) are useful. Also listed are other tasks you do not say were done (ie Disk Manager and Boot.ini contents). Listed was a voltage measurements on yellow and red wire - whether you did it or not - because it identifies another reason for this type of failure. Above is a checklist of what should have been done now that disk drive passes WD diagnostics. In some cases, tasks from that 'checklist' may need be repeated. wrote: I ignored your first post because 95% of that stuff had been covered previously. I have used the recovery console, I have used FDISK, I have replaced the PS. fixboot, bootcfg, and fixmbr have been done. The partition is active. Please read through the other posts.......it sucks to repeat the same things over and over. It does not get to the point that I can go step-by-step unless a bootable CD is in the drive, and when that is the case it boots without problems, so that would be pointless. |
#24
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
Swapped the processor out with a P4 out of the Dell that I just started
working on. Went through the whole process again.......same result. If it IS hardware related, something is bad that I already replaced. thecreator wrote: Hi abright52, You would not have gotten that Blue Screen, if the Seagate did not boot up. So, now after you finish formatting the WD Drive on another system and install the operating system on the Hard Drive and boot up the Hard Drive using the computer, you need to replace the CPU Processor. You already replaced the Motherboard. The CPU controls what gets written to the Hard Drive, thru programs. And the Boot Record recorded using that CPU Processor, could be corrupt, that the computer could not boot and you get the "Disk Boot Failure". Note, you will get the Blue Screen again, using the WD Hard Drive with a different motherboard, if it boots, when putting it back into the computer that was hit by lightning, just like the Seagate. You will need to reformat and reinstall the operating system using the motherboard and CPU Processor that the WD Hard Drive is going to run in. Question: Did you test the Memory / Ram Sticks using a different Motherboard that takes the same Memory Cards? -- thecreator |
#25
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
-Disk Manager: Are you talking about the Disk Management tools within
Windows? -Boot.ini Contents: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /fastdetect -PS Voltages: 12V: 11.85V 5V: 5.13V 3.3V: 3.39V Anything else? w_tom wrote: What you have already done is listed not for you. What you have already done was listed so that all others will learn from this experience - those steps (unlike swapping a CPU) are useful. Also listed are other tasks you do not say were done (ie Disk Manager and Boot.ini contents). Listed was a voltage measurements on yellow and red wire - whether you did it or not - because it identifies another reason for this type of failure. Above is a checklist of what should have been done now that disk drive passes WD diagnostics. In some cases, tasks from that 'checklist' may need be repeated. |
#26
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
Hi abright52,
Take the Floppy Drive and CD-Rom Drive out of the equation. Change the boot order after you install the operating system onto the Hard Drive, by booting to the Hard Drive first, floppy 2nd and CD 3rd. Or something bad that you haven't replaced, yet. Like the CD-Rom Drive and its cable. And look carefully at where the Memory Cards are seated. Make sure no pinched wires. I mentioned pinched wire, because I did it, thru experience. You said that you believed the system was hit by lightning. And you had replaced the motherboard. Is it possible, if that motherboard you installed, wasn't new, but defective and no one believed the former End User, the Company may have repackaged the Motherboard and you got it. Just thoughts. Also if the computer was hit by lightning, would not it leave snorching in the Case? -- thecreator wrote in message ups.com... Swapped the processor out with a P4 out of the Dell that I just started working on. Went through the whole process again.......same result. If it IS hardware related, something is bad that I already replaced. thecreator wrote: Hi abright52, You would not have gotten that Blue Screen, if the Seagate did not boot up. So, now after you finish formatting the WD Drive on another system and install the operating system on the Hard Drive and boot up the Hard Drive using the computer, you need to replace the CPU Processor. You already replaced the Motherboard. The CPU controls what gets written to the Hard Drive, thru programs. And the Boot Record recorded using that CPU Processor, could be corrupt, that the computer could not boot and you get the "Disk Boot Failure". Note, you will get the Blue Screen again, using the WD Hard Drive with a different motherboard, if it boots, when putting it back into the computer that was hit by lightning, just like the Seagate. You will need to reformat and reinstall the operating system using the motherboard and CPU Processor that the WD Hard Drive is going to run in. Question: Did you test the Memory / Ram Sticks using a different Motherboard that takes the same Memory Cards? -- thecreator |
#27
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
Disk Manager (from Windows NT and 2000) is now called Disk
Management. It is part of Computer Management. A quick way to load Computer Management: enter in StartRun the command compmgmt.msc . This provides a check list of what actually exists. Confirm what you thought with what the computer says exists. That partition (the only partition and should be NTFS) should be the active partition, healthy, etc Other information that, in your case should not report anything useful (but worth checking) is System Log of Event Viewer. Your boot.ini file is would also tell boot loader program to load those other files from first partition - reads correctly. But apparently (from what I understand), you are not even getting the boot loader to read boot.ini file; meaning again that the boot loader is not finding and loading any files from the root directory. If boot.ini file was read, then the text (WINDOWS="Microsoft Windows XP Home) would be seen on screen. If necessary files NTLDR, NTDETECT.COM, Boot.ini exist and the boot loader is confirmed OK (overwritten) by the Recover Console and that partition is marked active, then only reason left for boot loader not able to find those root directory files is a CMOS setting that is not quite right for that drive. For example, words such as LBA or Normal if mis-selected in CMOS would cause only part of the drive to be readable during boot. A changed selection can mean that some files in the root directory cannot be found by boot loader. When booted from CD-Rom, the configuration setting may be ignored which is why booting from CD-Rom can see same hard drive files just fine. Although those voltages would cause me to perform further testing (because 12 volts is so low while 5 volts is high), still, those voltages are sufficient and would not cause a boot failure. Sometime later, when system is accessing multiple peripherals simultaneously (multitasking programs accessing hard drive, CD-Rom, floppy, network and doing graphics), I would check those voltages again just to be sure. Meanwhile, no reason to do any hardware changes. CPU will either work - execute the WD diagnostic - or completely fail. Swapping hardware may only complicate problems. (BTW the Seagate with error code 78? means the XP on the Seagate is for hardware different from what your motherboard contains. A HAL layer in NT make NT unique for each computer chipset.) We know files exist on root directory. We know boot.ini has correct information. We know the boot loader does not read those root directory files. That is the point where failure is happening. We know disk hardware is OK. Question is why boot loader will not see those files. (I believe the wording for the 'not booting' message is directly from the Boot Loader meaning the boot loader did execute.) Either CMOS setting for drive is not correct, or boot loader is not properly written with parameters unique to that drive (maybe written before CMOS setting somehow changed?), or disk is not active so that boot loader does not know what partition to look for a root directory. Hardware is working just fine. Something in your setup or parameters written uniquely for the boot loader are causing boot loader to not find root directory files. Try booting with different CMOS selections for that drive. Confirm for active partition. Rewrite boot loader program to disk boot sector using Recovery Console. wrote: -Disk Manager: Are you talking about the Disk Management tools within Windows? -Boot.ini Contents: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /fastdetect -PS Voltages: 12V: 11.85V 5V: 5.13V 3.3V: 3.39V Anything else? |
#28
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
I tried that long ago, I disconnected both the floppy and the CDRom
Drive. Same Result, those are not to blame. No pinched wires.....everything is new, as far as that goes, also. The new motherboard came from NewEgg in the factory sealed packaging. Could it still be defective?.....I'm sure it could be just a factory reject. I have worked on many computers that have gotten hit by lightning, I don't remember a single one that scorched the case in anyway. Typically it will roast whichever part it comes in through, be it the modem or the power supply, then it may continue on far enough to fry the motherboard. I believe it came through the PS in this case, which took out the PS and MB. I don't think the original HD was bad from the lighting strike, but it did have some problems that came up in my original HD Scan. thecreator wrote: Hi abright52, Take the Floppy Drive and CD-Rom Drive out of the equation. Change the boot order after you install the operating system onto the Hard Drive, by booting to the Hard Drive first, floppy 2nd and CD 3rd. Or something bad that you haven't replaced, yet. Like the CD-Rom Drive and its cable. And look carefully at where the Memory Cards are seated. Make sure no pinched wires. I mentioned pinched wire, because I did it, thru experience. You said that you believed the system was hit by lightning. And you had replaced the motherboard. Is it possible, if that motherboard you installed, wasn't new, but defective and no one believed the former End User, the Company may have repackaged the Motherboard and you got it. Just thoughts. Also if the computer was hit by lightning, would not it leave snorching in the Case? -- thecreator wrote in message ups.com... Swapped the processor out with a P4 out of the Dell that I just started working on. Went through the whole process again.......same result. If it IS hardware related, something is bad that I already replaced. thecreator wrote: Hi abright52, You would not have gotten that Blue Screen, if the Seagate did not boot up. So, now after you finish formatting the WD Drive on another system and install the operating system on the Hard Drive and boot up the Hard Drive using the computer, you need to replace the CPU Processor. You already replaced the Motherboard. The CPU controls what gets written to the Hard Drive, thru programs. And the Boot Record recorded using that CPU Processor, could be corrupt, that the computer could not boot and you get the "Disk Boot Failure". Note, you will get the Blue Screen again, using the WD Hard Drive with a different motherboard, if it boots, when putting it back into the computer that was hit by lightning, just like the Seagate. You will need to reformat and reinstall the operating system using the motherboard and CPU Processor that the WD Hard Drive is going to run in. Question: Did you test the Memory / Ram Sticks using a different Motherboard that takes the same Memory Cards? -- thecreator |
#29
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
I will start with the BIOS settings.
It has been set to Auto through all of this. I tried all of the following settings: CHA LBA Large Other Auto detected settings: Capacity: 40016 MB Cylinder: 1277 Head: 240 Precomp: 0 Landing Zone: 19157 Sector: 255 After each change, I booted into the Recovery Console and ran fixmbr and fixboot, then restarted and removed the Windows CD. Still got the same error with all three settings. The error comes after it shows either: Building DMI Pool..... Verifiying DMI Pool Data............Update Success The computer would not boot with the CD until I set it back to Auto. Disk Management: Volume: (C Layout: Partition Type: Basic File System: NTFS Status: Healthy (System) Capacity: 37.26 GB Free Space: 35.95 GB % Free: 96% Fault Tolerance: No Overhead: 0% Status: Online Partition Style: Master Boot Record (MBR) Nothing notable in the System Log. System Files on the C: Drive: AUTOEXEC.BAT boot.ini CONFIG.SYS IO.SYS MSDOS.SYS NTDETECT.COM ntldr pagefile.sys Anything else? w_tom wrote: Disk Manager (from Windows NT and 2000) is now called Disk Management. It is part of Computer Management. A quick way to load Computer Management: enter in StartRun the command compmgmt.msc . This provides a check list of what actually exists. Confirm what you thought with what the computer says exists. That partition (the only partition and should be NTFS) should be the active partition, healthy, etc Other information that, in your case should not report anything useful (but worth checking) is System Log of Event Viewer. Your boot.ini file is would also tell boot loader program to load those other files from first partition - reads correctly. But apparently (from what I understand), you are not even getting the boot loader to read boot.ini file; meaning again that the boot loader is not finding and loading any files from the root directory. If boot.ini file was read, then the text (WINDOWS="Microsoft Windows XP Home) would be seen on screen. If necessary files NTLDR, NTDETECT.COM, Boot.ini exist and the boot loader is confirmed OK (overwritten) by the Recover Console and that partition is marked active, then only reason left for boot loader not able to find those root directory files is a CMOS setting that is not quite right for that drive. For example, words such as LBA or Normal if mis-selected in CMOS would cause only part of the drive to be readable during boot. A changed selection can mean that some files in the root directory cannot be found by boot loader. When booted from CD-Rom, the configuration setting may be ignored which is why booting from CD-Rom can see same hard drive files just fine. Although those voltages would cause me to perform further testing (because 12 volts is so low while 5 volts is high), still, those voltages are sufficient and would not cause a boot failure. Sometime later, when system is accessing multiple peripherals simultaneously (multitasking programs accessing hard drive, CD-Rom, floppy, network and doing graphics), I would check those voltages again just to be sure. Meanwhile, no reason to do any hardware changes. CPU will either work - execute the WD diagnostic - or completely fail. Swapping hardware may only complicate problems. (BTW the Seagate with error code 78? means the XP on the Seagate is for hardware different from what your motherboard contains. A HAL layer in NT make NT unique for each computer chipset.) We know files exist on root directory. We know boot.ini has correct information. We know the boot loader does not read those root directory files. That is the point where failure is happening. We know disk hardware is OK. Question is why boot loader will not see those files. (I believe the wording for the 'not booting' message is directly from the Boot Loader meaning the boot loader did execute.) Either CMOS setting for drive is not correct, or boot loader is not properly written with parameters unique to that drive (maybe written before CMOS setting somehow changed?), or disk is not active so that boot loader does not know what partition to look for a root directory. Hardware is working just fine. Something in your setup or parameters written uniquely for the boot loader are causing boot loader to not find root directory files. Try booting with different CMOS selections for that drive. Confirm for active partition. Rewrite boot loader program to disk boot sector using Recovery Console. wrote: -Disk Manager: Are you talking about the Disk Management tools within Windows? -Boot.ini Contents: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Home Edition" /fastdetect -PS Voltages: 12V: 11.85V 5V: 5.13V 3.3V: 3.39V Anything else? |
#30
|
|||
|
|||
Disk Boot Failure, but Hard Drive is fine.
Hi abright52,
Disk Boot Failure! Don't disconnect, just change the boot order in Computer BIOS. Anyway, is the motherboard installed, a new modern motherboard, for support for Large Hard Drives? You have used the new motherboard to format and install Windows XP? Recheck your Jumper settings on the Hard Drive and reformat and reinstall Windows XP. Have you seen the below information? http://wdc.custhelp.com/cgi-bin/wdc....1cmU%2A&p_li=# a.. Incorrect Jumper Settings will also prevent the BIOS from detecting your drive. The most common incorrect jumper setting used is for a drive that is alone on the data cable. Keep in mind that the concept of Master/Slave applies to a given EIDE channel. If there are two drives on the data cable, one must be Master and one designated as Slave. If the drive is the only device on the cable, it should be jumpered as a Single drive, NOT a Master. To do this, place a jumper shunt on pins 4 & 6, or remove the jumper shunt completely to set the drive as a Single drive. BIOS Limitations a.. If you have an older computer system, the BIOS may hang or freeze while auto detecting the drive. You may need to use the Alternate Jumper Settings. See Answer ID 83 for details. b.. If the system BIOS is only recognizing 528MB, 2.1GB, 8.4GB, 32GB, 64GB of the drive, or something significantly less then the actual capacity of the drive, your motherboard may not support large capacity drives. If this is the case, you may need to use Data Lifeguard Tools 11 for Windows as part of your installation. Windows NT/2000/XP Do not use the Alternate Jumper Settings. Consider either a BIOS upgrade, an EIDE controller card, or setting up the drive with Data Lifeguard Tools 11 for Windows to provide support for the drive. Windows 95/98/ME you can follow the instructions below to configure your drive. 1.. Enter the system BIOS. Typically, a message is displayed on the screen after the memory count of the boot process telling you how to enter Setup (Systems BIOS). We have listed several common access methods in Answer ID 536. 2.. Select User or User defined drive type and enter 1023 cylinders, 16 heads, and 63 sectors for the drive parameters. 3.. If your BIOS has additional settings other than Cylinders, Heads, and Sectors, enter 0 for them. 4.. Next, you will have one of two Mode options, LBA Mode or IDE Translation Mode. You will need to set this to Normal, Standard CHS, or LBA Disabled. You may not see all three options. Once the above is completed, the BIOS will report a drive capacity of either 504MB or 528MB. This is normal. The above settings simply trick your BIOS into thinking the drive is smaller then it really is, allowing the computer to boot with the drive connected. The full capacity of the drive will be available once the Data Lifeguard Tools disk is used to install, partition, and format the drive. -- thecreator wrote in message ups.com... I tried that long ago, I disconnected both the floppy and the CDRom Drive. Same Result, those are not to blame. No pinched wires.....everything is new, as far as that goes, also. The new motherboard came from NewEgg in the factory sealed packaging. Could it still be defective?.....I'm sure it could be just a factory reject. I have worked on many computers that have gotten hit by lightning, I don't remember a single one that scorched the case in anyway. Typically it will roast whichever part it comes in through, be it the modem or the power supply, then it may continue on far enough to fry the motherboard. I believe it came through the PS in this case, which took out the PS and MB. I don't think the original HD was bad from the lighting strike, but it did have some problems that came up in my original HD Scan. thecreator wrote: Hi abright52, Take the Floppy Drive and CD-Rom Drive out of the equation. Change the boot order after you install the operating system onto the Hard Drive, by booting to the Hard Drive first, floppy 2nd and CD 3rd. Or something bad that you haven't replaced, yet. Like the CD-Rom Drive and its cable. And look carefully at where the Memory Cards are seated. Make sure no pinched wires. I mentioned pinched wire, because I did it, thru experience. You said that you believed the system was hit by lightning. And you had replaced the motherboard. Is it possible, if that motherboard you installed, wasn't new, but defective and no one believed the former End User, the Company may have repackaged the Motherboard and you got it. Just thoughts. Also if the computer was hit by lightning, would not it leave snorching in the Case? -- thecreator wrote in message ups.com... Swapped the processor out with a P4 out of the Dell that I just started working on. Went through the whole process again.......same result. If it IS hardware related, something is bad that I already replaced. thecreator wrote: Hi abright52, You would not have gotten that Blue Screen, if the Seagate did not boot up. So, now after you finish formatting the WD Drive on another system and install the operating system on the Hard Drive and boot up the Hard Drive using the computer, you need to replace the CPU Processor. You already replaced the Motherboard. The CPU controls what gets written to the Hard Drive, thru programs. And the Boot Record recorded using that CPU Processor, could be corrupt, that the computer could not boot and you get the "Disk Boot Failure". Note, you will get the Blue Screen again, using the WD Hard Drive with a different motherboard, if it boots, when putting it back into the computer that was hit by lightning, just like the Seagate. You will need to reformat and reinstall the operating system using the motherboard and CPU Processor that the WD Hard Drive is going to run in. Question: Did you test the Memory / Ram Sticks using a different Motherboard that takes the same Memory Cards? -- thecreator |
Thread Tools | |
Display Modes | |
|
|