0

I have what seems to be a problem with Windows, however it could possibly be the motherboard itself. The reason I post it here is because Windows will not work but Linux will... so at the moment it seems to be a Windows problem...

I recently purchased a Syntax SV266AD motherboard. After installing a working compatible processor (an AMD Athlon XP 2200+) and installing the motherboard in my system with my existing hard drive (a Seagate Barracuda 7200 120GB) and video card (a GeForceFX 5600), I discovered that my computer would not boot into the operating system (Windows XP Pro). When attempting to boot, the computer would give me the message "A Disk Read Error Occurred. Press CTRL+ALT+DEL to restart." I tried booting two other hard drives on the system, but got the same error each time. After checking and rechecking my hardware and IDE cables, I reluctantly used another computer to format my Seagate HD in the hope that I could simply re-install Windows to solve the problem. When attempting to start the Windows XP Setup, however, I received a stop message: UNMOUNTABLE_BOOT_VOLUME, with the stop code: ***STOP: 0x000000ED (0x823Cf030, 0xC0000010, 0x00000000, 0x00000000). This is beyond my level of expertise. Since it only happened after installing my new Syntax motherboard, and since it happens no matter what hard drive I try, I suspect it has something to do with the motherboard itself. Strangely, I am able to install Fedora Linux without a problem onto the hard drive while using the Syntax motherboard... are there any known conflict issues between Windows XP and Syntax motherboards that Linux might not have? If this is a known Windows issue (or even not known,) how might I go about fixing it without a working XP installation? (Note: working XP installations on the hard drives from other computers will not boot... I get the Disk Read Error.)

I have read through Microsoft's official KB article pertaining to the 0x000000ED stop message, and have tried the recommended switch to 80-wire cables, but that did not seem to solve the problem.

I'm at my wit's end trying to solve this problem... (my noisy fan problem seems trivial compared to this!) So any help would be greatly appreciated!!!

Thanks in advance!! (My apologies is this belongs in the hardware forum, but I was unsure...)

6
Contributors
6
Replies
7
Views
13 Years
Discussion Span
Last Post by DMR
0

did you already have the windows xp install on the hard drive then add a new mobo? or the other way round, as windows doesn't like mobo changes, so you'll just have to run the windows XP reinstall thing, which won't loose any of your data so will be safe...

0

microsoft had this to say,

CAUSE
This behavior can occur if either of the following conditions is true:
Your computer uses an Ultra Direct Memory Access (UDMA) hard disk controller, and the following conditions are true:
You use a standard 40-wire connector cable to connect the UDMA drive to the controller instead of the required 80-wire, 40-pin cable.
The basic input/output system (BIOS) settings are configured to force the faster UDMA modes.
The file system is damaged and cannot be mounted.
RESOLUTION
To resolve this behavior, use the appropriate method.
UDMA Controller
If your computer uses a UDMA hard disk controller, use the following procedures:
Replace the 40-wire cable with an 80-wire UDMA cable.
In the BIOS settings for your computer, load the 'Fail-Safe' default settings, and then reactivate the most frequently used options such as USB Support.
Damaged File System
If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then the file system is damaged.

If this is the case, restart the computer to the Recovery Console, and then use the chkdsk /r command to repair the volume. After you repair the volume, check your hardware to isolate the cause of the file system damage.

To do this, use the following steps:

0

eerr..... uummmm.......

It's highly likely that even a reinstall (In-place upgrade) over the top of the existing Windows installation will fix that. A format and fresh install may be inorder.

You could try replacing the drive in the original system to lift off any data files you need to make backups of, beut even then, once the hard drive has been used to try and boot in a new system, it may be gone beyond any reasonable chance of recovery.

Sorry, but that's just the way things are. Windows XP is NOT designed to handle a change of motherboard!

korteena, please stop trying to use hard drives from other PCs. You run the risk of causing damage to the Windows installations on those as well ;)

0

Gentlemen, I also received the same error message "A Disk Read Error Occurred. Press CTRL+ALT+DEL to restart." I installed a new maxtor 160Gb drive and stood up XP Pro SP1. Ran great for 3 weeks (while I was recovering from a crashed W98 Western Digital 100Gb drive failure) when one morning I booted up my PC and received this ugle message on my brand new drive. I had not changed anything in my system. I installed the Maxtor using the supplied IDE cable. My BIOS recognized everthing from the get go. Maxtor has had me run off kinds of disk utilities to verify drive is functioning OK, all checked out fine. Is the boot record damaged? I don't have a clue why it broke since I did not change any hardware or software following my rebuild. Any suggestions out there?

Regards, Chuck

0

I am having the exact same problem with a SeaGate Barracuda 200 MB drive that was installed to replace a failing IBM Deskstar. The system worked fine for about a week, then performance got squirrely and I rebooted. (It had been rebooted multiple times after being put into service as the master drive with no problems of any kind prior to this occurrence) Nothing has worked since. I get the 'A disk read error occurred' and CTRL-ALT-DELETE just repeats the same sequence. Allowing it to boot from the CD gets me a CHECKING HARDWARE CONFIGURATION, followed by a black screen and no visible signs of life. I put a new drive cable on, replaced the master jumper on the drive, etc., nothing has worked. SeaGates Desktop diagnostic shows the drive to be perfectly fine when booting from their floppies. Conversation with them has led me no where. I'd really appreciate some suggestions also.

0

sillsj and cjpitsch,


First of all- welcome to TechTalk :)

We ask that members not tag their questions on to a thread previously started by another member (regardless of how similar your problem might seem). Not only does it divert the focus of the thread away from the original poster's problem, but it also makes it less likely that you yourself will get the individual attention that you need.

Please start your own thread and post your question there. When you do, please try to give us as much specific info as possible regarding the problem (exact error messages, system specs, etc.).

For a full description of our posting guidelines and general rules of conduct, please see this page:

http://www.daniweb.com/techtalkforu...b_faq#faq_rules


Thanks for understanding.

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.