Windows problem ... not sure where to start



Heath
07-10-2005, 12:22 AM
I originally thought my new HD was failing, but after buying a new one and
reinstalling Windows I plugged in the HD I thought was bad and didn't find
any errors when I ran a disc check.

So, I am guessing my problem was in my Windows install on the first HD. Is
there anyway that I can repair the Windows install on the original HD so I
don't loose all my contacts, schedule, and e-mails?

I am a novice at this, so thanks for your patience!

S.Sengupta
07-10-2005, 12:22 AM
Repair install keeps everything intact.
see:-
http://www.michaelstevenstech.com/XPrepairinstall.htm

regards,
ssg MS-MVP

Heath wrote:

> I originally thought my new HD was failing, but after buying a new one and
> reinstalling Windows I plugged in the HD I thought was bad and didn't find
> any errors when I ran a disc check.
>
> So, I am guessing my problem was in my Windows install on the first HD. Is
> there anyway that I can repair the Windows install on the original HD so I
> don't loose all my contacts, schedule, and e-mails?
>
> I am a novice at this, so thanks for your patience!

brianb
07-10-2005, 12:22 AM
You have two options actually...

Option #1
To start Recovery Console from the Windows XP Professional operating system CD

Insert the Windows XP Professional operating system CD into the CD-ROM
drive, and restart the computer. When prompted, press a key to start Setup.
At the Setup Notification screen, press ENTER.
After the Welcome to Setup screen appears, select To repair a Windows XP
installation using Recovery Console by pressing R.
A menu that lists one or more Windows XP Professional installations appears.

Type the number corresponding to the installation that you want to use, and
then press ENTER.
At the prompt, enter the password for the local Administrator account to
access the contents of the local hard disk. Recovery Console accepts only the
local Administrator account password.

Next, at the command prompt, type 'chkdsk /f' without the quotes and hit
enter. That will scan your HD for errors and fix them.

Option #2
http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
Scroll down and follow the directions in Method #2. This will replace all
system files, but leave all other files intact.

"Heath" wrote:

> I originally thought my new HD was failing, but after buying a new one and
> reinstalling Windows I plugged in the HD I thought was bad and didn't find
> any errors when I ran a disc check.
>
> So, I am guessing my problem was in my Windows install on the first HD. Is
> there anyway that I can repair the Windows install on the original HD so I
> don't loose all my contacts, schedule, and e-mails?
>
> I am a novice at this, so thanks for your patience!

Heath
07-10-2005, 12:22 AM
Thank you. Because the XP Pro is an upgrade do i use the Pro orhome edition
CD for the repair?

"brianb" wrote:

> You have two options actually...
>
> Option #1
> To start Recovery Console from the Windows XP Professional operating system CD
>
> Insert the Windows XP Professional operating system CD into the CD-ROM
> drive, and restart the computer. When prompted, press a key to start Setup.
> At the Setup Notification screen, press ENTER.
> After the Welcome to Setup screen appears, select To repair a Windows XP
> installation using Recovery Console by pressing R.
> A menu that lists one or more Windows XP Professional installations appears.
>
> Type the number corresponding to the installation that you want to use, and
> then press ENTER.
> At the prompt, enter the password for the local Administrator account to
> access the contents of the local hard disk. Recovery Console accepts only the
> local Administrator account password.
>
> Next, at the command prompt, type 'chkdsk /f' without the quotes and hit
> enter. That will scan your HD for errors and fix them.
>
> Option #2
> http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
> Scroll down and follow the directions in Method #2. This will replace all
> system files, but leave all other files intact.
>
> "Heath" wrote:
>
> > I originally thought my new HD was failing, but after buying a new one and
> > reinstalling Windows I plugged in the HD I thought was bad and didn't find
> > any errors when I ran a disc check.
> >
> > So, I am guessing my problem was in my Windows install on the first HD. Is
> > there anyway that I can repair the Windows install on the original HD so I
> > don't loose all my contacts, schedule, and e-mails?
> >
> > I am a novice at this, so thanks for your patience!

Steve N.
07-10-2005, 12:22 AM
Heath wrote:
> I originally thought my new HD was failing, but after buying a new one and
> reinstalling Windows I plugged in the HD I thought was bad and didn't find
> any errors when I ran a disc check.
>
> So, I am guessing my problem was in my Windows install on the first HD. Is
> there anyway that I can repair the Windows install on the original HD so I
> don't loose all my contacts, schedule, and e-mails?
>
> I am a novice at this, so thanks for your patience!

Please give details about exactly what's going on when trying to run the
original installation, such as detailed error messages, conditions, etc.
What exactly happens?

Steve

Steve N.
07-10-2005, 12:22 AM
S.Sengupta wrote:
> Repair install keeps everything intact.
> see:-
> http://www.michaelstevenstech.com/XPrepairinstall.htm
>
> regards,
> ssg MS-MVP

Including any software or driver problems. My opinion is the OP has not
supplied enough information to warrant advising a repair install, which
is always the next to last resort.

Steve

>
> Heath wrote:
>
>> I originally thought my new HD was failing, but after buying a new one
>> and reinstalling Windows I plugged in the HD I thought was bad and
>> didn't find any errors when I ran a disc check.
>>
>> So, I am guessing my problem was in my Windows install on the first
>> HD. Is there anyway that I can repair the Windows install on the
>> original HD so I don't loose all my contacts, schedule, and e-mails?
>>
>> I am a novice at this, so thanks for your patience!

Steve N.
07-10-2005, 12:22 AM
brianb wrote:

> You have two options actually...
>
> Option #1
> To start Recovery Console from the Windows XP Professional operating system CD
>
> Insert the Windows XP Professional operating system CD into the CD-ROM
> drive, and restart the computer. When prompted, press a key to start Setup.
> At the Setup Notification screen, press ENTER.
> After the Welcome to Setup screen appears, select To repair a Windows XP
> installation using Recovery Console by pressing R.
> A menu that lists one or more Windows XP Professional installations appears.
>
> Type the number corresponding to the installation that you want to use, and
> then press ENTER.
> At the prompt, enter the password for the local Administrator account to
> access the contents of the local hard disk. Recovery Console accepts only the
> local Administrator account password.

Which in the case of XP Home is blank by default.

>
> Next, at the command prompt, type 'chkdsk /f' without the quotes and hit
> enter. That will scan your HD for errors and fix them.

From Recovery Console it is CHKDSK /P not /F.

>
> Option #2
> http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
> Scroll down and follow the directions in Method #2. This will replace all
> system files, but leave all other files intact.

A repair install is a next to last resort and the OP has not supplied
enough information to warrant this recommendation IMO. That is not to
say that is not what is needed, just to say it's be better to get more
details about what has happened to the system, errors, conditions, etc.,
before recommending a repair installation of the OS.

Steve

>
> "Heath" wrote:
>
>
>>I originally thought my new HD was failing, but after buying a new one and
>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
>>any errors when I ran a disc check.
>>
>>So, I am guessing my problem was in my Windows install on the first HD. Is
>>there anyway that I can repair the Windows install on the original HD so I
>>don't loose all my contacts, schedule, and e-mails?
>>
>>I am a novice at this, so thanks for your patience!

j-d
07-10-2005, 12:22 AM
And what do you do if there is no repair option listed?

"brianb" wrote:

> You have two options actually...
>
> Option #1
> To start Recovery Console from the Windows XP Professional operating system CD
>
> Insert the Windows XP Professional operating system CD into the CD-ROM
> drive, and restart the computer. When prompted, press a key to start Setup.
> At the Setup Notification screen, press ENTER.
> After the Welcome to Setup screen appears, select To repair a Windows XP
> installation using Recovery Console by pressing R.
> A menu that lists one or more Windows XP Professional installations appears.
>
> Type the number corresponding to the installation that you want to use, and
> then press ENTER.
> At the prompt, enter the password for the local Administrator account to
> access the contents of the local hard disk. Recovery Console accepts only the
> local Administrator account password.
>
> Next, at the command prompt, type 'chkdsk /f' without the quotes and hit
> enter. That will scan your HD for errors and fix them.
>
> Option #2
> http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
> Scroll down and follow the directions in Method #2. This will replace all
> system files, but leave all other files intact.
>
> "Heath" wrote:
>
> > I originally thought my new HD was failing, but after buying a new one and
> > reinstalling Windows I plugged in the HD I thought was bad and didn't find
> > any errors when I ran a disc check.
> >
> > So, I am guessing my problem was in my Windows install on the first HD. Is
> > there anyway that I can repair the Windows install on the original HD so I
> > don't loose all my contacts, schedule, and e-mails?
> >
> > I am a novice at this, so thanks for your patience!

Curmudgeon
07-10-2005, 12:22 AM
Steve N. wrote:

> A repair install is a next to last resort [snip]

The guy is a self-proclaimed "novice" and a repair installation is
easy, painless and takes only about a half an hour to complete.

Your way could take days.

brianb
07-10-2005, 12:22 AM
I do agree with what you say...it could be a driver problem, or possibly
hardware, but I am just working with the info at hand...
If the repair install does not fix it, then the OP hasn't lost
anything...except for maybe a little time.

"Steve N." wrote:

> S.Sengupta wrote:
> > Repair install keeps everything intact.
> > see:-
> > http://www.michaelstevenstech.com/XPrepairinstall.htm
> >
> > regards,
> > ssg MS-MVP
>
> Including any software or driver problems. My opinion is the OP has not
> supplied enough information to warrant advising a repair install, which
> is always the next to last resort.
>
> Steve
>
> >
> > Heath wrote:
> >
> >> I originally thought my new HD was failing, but after buying a new one
> >> and reinstalling Windows I plugged in the HD I thought was bad and
> >> didn't find any errors when I ran a disc check.
> >>
> >> So, I am guessing my problem was in my Windows install on the first
> >> HD. Is there anyway that I can repair the Windows install on the
> >> original HD so I don't loose all my contacts, schedule, and e-mails?
> >>
> >> I am a novice at this, so thanks for your patience!
>
>

brianb
07-10-2005, 12:22 AM
You should be able to use the Pro CD to boot from and perform the repair
installation.

"Heath" wrote:

> Thank you. Because the XP Pro is an upgrade do i use the Pro orhome edition
> CD for the repair?
>
> "brianb" wrote:
>
> > You have two options actually...
> >
> > Option #1
> > To start Recovery Console from the Windows XP Professional operating system CD
> >
> > Insert the Windows XP Professional operating system CD into the CD-ROM
> > drive, and restart the computer. When prompted, press a key to start Setup.
> > At the Setup Notification screen, press ENTER.
> > After the Welcome to Setup screen appears, select To repair a Windows XP
> > installation using Recovery Console by pressing R.
> > A menu that lists one or more Windows XP Professional installations appears.
> >
> > Type the number corresponding to the installation that you want to use, and
> > then press ENTER.
> > At the prompt, enter the password for the local Administrator account to
> > access the contents of the local hard disk. Recovery Console accepts only the
> > local Administrator account password.
> >
> > Next, at the command prompt, type 'chkdsk /f' without the quotes and hit
> > enter. That will scan your HD for errors and fix them.
> >
> > Option #2
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
> > Scroll down and follow the directions in Method #2. This will replace all
> > system files, but leave all other files intact.
> >
> > "Heath" wrote:
> >
> > > I originally thought my new HD was failing, but after buying a new one and
> > > reinstalling Windows I plugged in the HD I thought was bad and didn't find
> > > any errors when I ran a disc check.
> > >
> > > So, I am guessing my problem was in my Windows install on the first HD. Is
> > > there anyway that I can repair the Windows install on the original HD so I
> > > don't loose all my contacts, schedule, and e-mails?
> > >
> > > I am a novice at this, so thanks for your patience!

Heath
07-10-2005, 12:22 AM
Ok, here goes.

Originally my problem started when the computer would just up and reboot.
The error message that came up asked me if I wanted to report the error to
MS. After I reported the error I got a screen saying the problem resulted
from an unknown driver problem.

I started uninstalling non-essential programs and drivers to pin down the
problem. After uninstalling several I got a message that popped up saying
some windows feature was missing and that the computer rebooted.

From that point I would be able to start up windows but it was only a minute
or two before it would reboot on its own.

After this happened several times I an "error-check" to be run the next time
I rebooted. That done, I restarted windows and away the error check went. I
kept getting several "error reading" messages and during the 5th step it
would just lock up ... I forget what the message was.

Now, after I installed windows on a new HD I was able to complete the error
check on the original HD and didn't get any eror messages, I assume that
means it was able to correct any errors?

Now I just disconnected the new HD and plugged the old back in. Onbn reboot
I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
reboot.

"Steve N." wrote:

> Heath wrote:
> > I originally thought my new HD was failing, but after buying a new one and
> > reinstalling Windows I plugged in the HD I thought was bad and didn't find
> > any errors when I ran a disc check.
> >
> > So, I am guessing my problem was in my Windows install on the first HD. Is
> > there anyway that I can repair the Windows install on the original HD so I
> > don't loose all my contacts, schedule, and e-mails?
> >
> > I am a novice at this, so thanks for your patience!
>
> Please give details about exactly what's going on when trying to run the
> original installation, such as detailed error messages, conditions, etc.
> What exactly happens?
>
> Steve
>
>

Steve N.
07-10-2005, 12:22 AM
brianb wrote:

> I do agree with what you say...it could be a driver problem, or possibly
> hardware, but I am just working with the info at hand...
> If the repair install does not fix it, then the OP hasn't lost
> anything...except for maybe a little time.
>

Unless the repair install can't complete and then you're probably
looking at needing a clean install. Still, it all depends on the
specifics we don't know yet.

Steve

> "Steve N." wrote:
>
>
>>S.Sengupta wrote:
>>
>>>Repair install keeps everything intact.
>>>see:-
>>>http://www.michaelstevenstech.com/XPrepairinstall.htm
>>>
>>>regards,
>>>ssg MS-MVP
>>
>>Including any software or driver problems. My opinion is the OP has not
>>supplied enough information to warrant advising a repair install, which
>>is always the next to last resort.
>>
>>Steve
>>
>>
>>>Heath wrote:
>>>
>>>
>>>>I originally thought my new HD was failing, but after buying a new one
>>>>and reinstalling Windows I plugged in the HD I thought was bad and
>>>>didn't find any errors when I ran a disc check.
>>>>
>>>>So, I am guessing my problem was in my Windows install on the first
>>>>HD. Is there anyway that I can repair the Windows install on the
>>>>original HD so I don't loose all my contacts, schedule, and e-mails?
>>>>
>>>>I am a novice at this, so thanks for your patience!
>>
>>

Steve N.
07-10-2005, 12:22 AM
Curmudgeon wrote:

> Steve N. wrote:
>
>
>>A repair install is a next to last resort [snip]
>
>
> The guy is a self-proclaimed "novice"

He's not *that* much of a novice if he can install a new hard drive,
install the OS to it, slave the old drive and test it.

> and a repair installation is
> easy, painless and takes only about a half an hour to complete.
>

Unless it blows up in his face. Ever seen a failed repair install? I
know he specifically asked how to do a repair install but he might not
have to and if that's the case there'd be no need to take the risk.

> Your way could take days.
>

Maybe. It also might only take an hour. He's already spent a bit of time
troubleshooting, what's a little more going to hurt? Without details
that only the OP can supply we may as well be shooting at ghosts with
rubber bands.

Steve

Steve N.
07-10-2005, 12:22 AM
Heath wrote:

> Ok, here goes.
>
> Originally my problem started when the computer would just up and reboot.
> The error message that came up asked me if I wanted to report the error to
> MS. After I reported the error I got a screen saying the problem resulted
> from an unknown driver problem.
>
> I started uninstalling non-essential programs and drivers to pin down the
> problem. After uninstalling several I got a message that popped up saying
> some windows feature was missing and that the computer rebooted.
>
> From that point I would be able to start up windows but it was only a minute
> or two before it would reboot on its own.
>
> After this happened several times I an "error-check" to be run the next time
> I rebooted. That done, I restarted windows and away the error check went. I
> kept getting several "error reading" messages and during the 5th step it
> would just lock up ... I forget what the message was.
>
> Now, after I installed windows on a new HD I was able to complete the error
> check on the original HD and didn't get any eror messages, I assume that
> means it was able to correct any errors?
>
> Now I just disconnected the new HD and plugged the old back in. Onbn reboot
> I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
> reboot.
>

Thanks for the details.

First, make sure there isn't a disk in the floppy drive (very common
cause of NTLDR missing error if the floppy drive is set as 1st boot device).

If there isn't a floppy in the drive then try "Method 2: Use the
Recovery Console" listed here (it's for Win2K but will work for XP and
MS doesn't appear to have a seperate instructions specifically for XP
that I can find):

How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
http://support.microsoft.com/kb/318728/#7

While in Recovery Console I would also run CHKDSK /R /V. I'd also
download the hard drive manufacturer's diagnostic utility and test the
drive using it.

If/when you get it to boot up right click My Computer, Properties,
Advanced, Startup and Recovery and uncheck automatically restart (do it
is Safe Mode if it's still rebooting in Normal Mode). Afterwards when
the error causing the system halt occurs you will see it on screen,
write it down exactly as displayed and post that info here.

Steve

> "Steve N." wrote:
>
>
>>Heath wrote:
>>
>>>I originally thought my new HD was failing, but after buying a new one and
>>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
>>>any errors when I ran a disc check.
>>>
>>>So, I am guessing my problem was in my Windows install on the first HD. Is
>>>there anyway that I can repair the Windows install on the original HD so I
>>>don't loose all my contacts, schedule, and e-mails?
>>>
>>>I am a novice at this, so thanks for your patience!
>>
>>Please give details about exactly what's going on when trying to run the
>>original installation, such as detailed error messages, conditions, etc.
>>What exactly happens?
>>
>>Steve
>>
>>

BNR
07-10-2005, 12:22 AM
Sounds like you mistook that error to mean HD memory, when infact its more
along the lines of DDRAM memory. You've done alot of troubleshooting on
your own to put yourself. Its to be commended. However I'm afraid it put
you deeper into trouble.

Well you have more HD space now.. To look on the bright side. Maybe you
could pickup another HD and try your hand at a RAID array.

The NTLDR error means the bootup sequence in BIOS is wrong. Another words
the PC is attempting to boot from an empty DVD/CD or floppy drive instead of
the HD with Windows on it. This fix is simple and painless. Its found in
the BIOS.

Now onto the underlying problem. I believe the error is in your DDRAM.
I've said this 4x today to 4 different people.. LOL. Try another pair of
DDRAM, maybe some high latency sticks that are in your QVL for the
motherboard, found on their site. Corsair has a memory configuration wizard
on their site, its very useful.

Thank you for allowing me to help. Good Day

"Heath" <Heath@discussions.microsoft.com> wrote in message
news:561D131C-06CC-4C9E-9739-C523CE0CC399@microsoft.com...
> Ok, here goes.
>
> Originally my problem started when the computer would just up and reboot.
> The error message that came up asked me if I wanted to report the error to
> MS. After I reported the error I got a screen saying the problem resulted
> from an unknown driver problem.
>
> I started uninstalling non-essential programs and drivers to pin down the
> problem. After uninstalling several I got a message that popped up saying
> some windows feature was missing and that the computer rebooted.
>
> From that point I would be able to start up windows but it was only a
minute
> or two before it would reboot on its own.
>
> After this happened several times I an "error-check" to be run the next
time
> I rebooted. That done, I restarted windows and away the error check went.
I
> kept getting several "error reading" messages and during the 5th step it
> would just lock up ... I forget what the message was.
>
> Now, after I installed windows on a new HD I was able to complete the
error
> check on the original HD and didn't get any eror messages, I assume that
> means it was able to correct any errors?
>
> Now I just disconnected the new HD and plugged the old back in. Onbn
reboot
> I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
> reboot.
>
> "Steve N." wrote:
>
> > Heath wrote:
> > > I originally thought my new HD was failing, but after buying a new one
and
> > > reinstalling Windows I plugged in the HD I thought was bad and didn't
find
> > > any errors when I ran a disc check.
> > >
> > > So, I am guessing my problem was in my Windows install on the first
HD. Is
> > > there anyway that I can repair the Windows install on the original HD
so I
> > > don't loose all my contacts, schedule, and e-mails?
> > >
> > > I am a novice at this, so thanks for your patience!
> >
> > Please give details about exactly what's going on when trying to run the
> > original installation, such as detailed error messages, conditions, etc.
> > What exactly happens?
> >
> > Steve
> >
> >

Steve N.
07-10-2005, 12:22 AM
BNR wrote:

> Sounds like you mistook that error to mean HD memory, when infact its more
> along the lines of DDRAM memory. You've done alot of troubleshooting on
> your own to put yourself. Its to be commended. However I'm afraid it put
> you deeper into trouble.

If it was bad RAM I would think it would cause the same problem on the
2nd new hard drive he install the OS onto. I think it could be ruled out
but there's no harm in using Memtest86 and the MS Memory Diagnostic just
to be sure. I'd use both as I've found RAM that would pass one but not
the other:

www.memtest86.com

http://oca.microsoft.com/en/windiag.asp

>
> Well you have more HD space now.. To look on the bright side. Maybe you
> could pickup another HD and try your hand at a RAID array.

I think you have misread something here BNR. He already bought another
hard drive, installed the OS on it and it works fine. He just wants to
use the old drive & OS so he can use what's already on it.

>
> The NTLDR error means the bootup sequence in BIOS is wrong. Another words
> the PC is attempting to boot from an empty DVD/CD or floppy drive instead of
> the HD with Windows on it. This fix is simple and painless. Its found in
> the BIOS.

That's certainly one possibility for the error, but since the other new
drive boots fine I think we can rule that out, too.

Steve

Heath
07-10-2005, 12:23 AM
Ok, I just completed the MS memory test and my memory appears intact... all
the tests passed.

There wasn't a floppy in the drive and I've not tried to trouble shoot that
problem yet for the NTLDR problem because it hasnt happened again.

I did uncheck the automatic restarts as you suggested.

The last two times it froze I got these numbers ...

1st -0x00000024 (0x001902FE, 0xAE937438, 0xAE937134, 0x804F954D)

2ND -0x0000007E(0x0000005, 0xF7B7286C, 0xF78C6C20, 0xF78C691C)

ntfs.sys address F7B7286c base at F7B520000, Date stamp 41107eea

"Steve N." wrote:

> Heath wrote:
>
> > Ok, here goes.
> >
> > Originally my problem started when the computer would just up and reboot.
> > The error message that came up asked me if I wanted to report the error to
> > MS. After I reported the error I got a screen saying the problem resulted
> > from an unknown driver problem.
> >
> > I started uninstalling non-essential programs and drivers to pin down the
> > problem. After uninstalling several I got a message that popped up saying
> > some windows feature was missing and that the computer rebooted.
> >
> > From that point I would be able to start up windows but it was only a minute
> > or two before it would reboot on its own.
> >
> > After this happened several times I an "error-check" to be run the next time
> > I rebooted. That done, I restarted windows and away the error check went. I
> > kept getting several "error reading" messages and during the 5th step it
> > would just lock up ... I forget what the message was.
> >
> > Now, after I installed windows on a new HD I was able to complete the error
> > check on the original HD and didn't get any eror messages, I assume that
> > means it was able to correct any errors?
> >
> > Now I just disconnected the new HD and plugged the old back in. Onbn reboot
> > I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
> > reboot.
> >
>
> Thanks for the details.
>
> First, make sure there isn't a disk in the floppy drive (very common
> cause of NTLDR missing error if the floppy drive is set as 1st boot device).
>
> If there isn't a floppy in the drive then try "Method 2: Use the
> Recovery Console" listed here (it's for Win2K but will work for XP and
> MS doesn't appear to have a seperate instructions specifically for XP
> that I can find):
>
> How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
> http://support.microsoft.com/kb/318728/#7
>
> While in Recovery Console I would also run CHKDSK /R /V. I'd also
> download the hard drive manufacturer's diagnostic utility and test the
> drive using it.
>
> If/when you get it to boot up right click My Computer, Properties,
> Advanced, Startup and Recovery and uncheck automatically restart (do it
> is Safe Mode if it's still rebooting in Normal Mode). Afterwards when
> the error causing the system halt occurs you will see it on screen,
> write it down exactly as displayed and post that info here.
>
> Steve
>
> > "Steve N." wrote:
> >
> >
> >>Heath wrote:
> >>
> >>>I originally thought my new HD was failing, but after buying a new one and
> >>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
> >>>any errors when I ran a disc check.
> >>>
> >>>So, I am guessing my problem was in my Windows install on the first HD. Is
> >>>there anyway that I can repair the Windows install on the original HD so I
> >>>don't loose all my contacts, schedule, and e-mails?
> >>>
> >>>I am a novice at this, so thanks for your patience!
> >>
> >>Please give details about exactly what's going on when trying to run the
> >>original installation, such as detailed error messages, conditions, etc.
> >>What exactly happens?
> >>
> >>Steve
> >>
> >>
>
>

Heath
07-10-2005, 12:23 AM
I just ran the diagnostics test from MS on the memory and it all passed teh
extended tests with no errors. Thanks for your help!

"BNR" wrote:

> Sounds like you mistook that error to mean HD memory, when infact its more
> along the lines of DDRAM memory. You've done alot of troubleshooting on
> your own to put yourself. Its to be commended. However I'm afraid it put
> you deeper into trouble.
>
> Well you have more HD space now.. To look on the bright side. Maybe you
> could pickup another HD and try your hand at a RAID array.
>
> The NTLDR error means the bootup sequence in BIOS is wrong. Another words
> the PC is attempting to boot from an empty DVD/CD or floppy drive instead of
> the HD with Windows on it. This fix is simple and painless. Its found in
> the BIOS.
>
> Now onto the underlying problem. I believe the error is in your DDRAM.
> I've said this 4x today to 4 different people.. LOL. Try another pair of
> DDRAM, maybe some high latency sticks that are in your QVL for the
> motherboard, found on their site. Corsair has a memory configuration wizard
> on their site, its very useful.
>
> Thank you for allowing me to help. Good Day
>
> "Heath" <Heath@discussions.microsoft.com> wrote in message
> news:561D131C-06CC-4C9E-9739-C523CE0CC399@microsoft.com...
> > Ok, here goes.
> >
> > Originally my problem started when the computer would just up and reboot.
> > The error message that came up asked me if I wanted to report the error to
> > MS. After I reported the error I got a screen saying the problem resulted
> > from an unknown driver problem.
> >
> > I started uninstalling non-essential programs and drivers to pin down the
> > problem. After uninstalling several I got a message that popped up saying
> > some windows feature was missing and that the computer rebooted.
> >
> > From that point I would be able to start up windows but it was only a
> minute
> > or two before it would reboot on its own.
> >
> > After this happened several times I an "error-check" to be run the next
> time
> > I rebooted. That done, I restarted windows and away the error check went.
> I
> > kept getting several "error reading" messages and during the 5th step it
> > would just lock up ... I forget what the message was.
> >
> > Now, after I installed windows on a new HD I was able to complete the
> error
> > check on the original HD and didn't get any eror messages, I assume that
> > means it was able to correct any errors?
> >
> > Now I just disconnected the new HD and plugged the old back in. Onbn
> reboot
> > I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
> > reboot.
> >
> > "Steve N." wrote:
> >
> > > Heath wrote:
> > > > I originally thought my new HD was failing, but after buying a new one
> and
> > > > reinstalling Windows I plugged in the HD I thought was bad and didn't
> find
> > > > any errors when I ran a disc check.
> > > >
> > > > So, I am guessing my problem was in my Windows install on the first
> HD. Is
> > > > there anyway that I can repair the Windows install on the original HD
> so I
> > > > don't loose all my contacts, schedule, and e-mails?
> > > >
> > > > I am a novice at this, so thanks for your patience!
> > >
> > > Please give details about exactly what's going on when trying to run the
> > > original installation, such as detailed error messages, conditions, etc.
> > > What exactly happens?
> > >
> > > Steve
> > >
> > >
>
>
>

Heath
07-10-2005, 12:23 AM
I just began the Western Digital diagnostics test on this Raptor 74 GB hard
drive and it has a little over 6 hours left until it completes. Hopefully it
stays up long enough for the test to run its course and I will know for sure
in the AM if there are any problems with it.

When y machine does reboot I get the "just recovered from major" crash alert
and am asked to report it to MS. When I do I get a pop up window that tells
me the problem was caused by a driver. I have no idea which one, though.
Any great programs I can run to track down the culprit?

Thanks for your help everyone.

"Steve N." wrote:

> Heath wrote:
>
> > Ok, here goes.
> >
> > Originally my problem started when the computer would just up and reboot.
> > The error message that came up asked me if I wanted to report the error to
> > MS. After I reported the error I got a screen saying the problem resulted
> > from an unknown driver problem.
> >
> > I started uninstalling non-essential programs and drivers to pin down the
> > problem. After uninstalling several I got a message that popped up saying
> > some windows feature was missing and that the computer rebooted.
> >
> > From that point I would be able to start up windows but it was only a minute
> > or two before it would reboot on its own.
> >
> > After this happened several times I an "error-check" to be run the next time
> > I rebooted. That done, I restarted windows and away the error check went. I
> > kept getting several "error reading" messages and during the 5th step it
> > would just lock up ... I forget what the message was.
> >
> > Now, after I installed windows on a new HD I was able to complete the error
> > check on the original HD and didn't get any eror messages, I assume that
> > means it was able to correct any errors?
> >
> > Now I just disconnected the new HD and plugged the old back in. Onbn reboot
> > I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
> > reboot.
> >
>
> Thanks for the details.
>
> First, make sure there isn't a disk in the floppy drive (very common
> cause of NTLDR missing error if the floppy drive is set as 1st boot device).
>
> If there isn't a floppy in the drive then try "Method 2: Use the
> Recovery Console" listed here (it's for Win2K but will work for XP and
> MS doesn't appear to have a seperate instructions specifically for XP
> that I can find):
>
> How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
> http://support.microsoft.com/kb/318728/#7
>
> While in Recovery Console I would also run CHKDSK /R /V. I'd also
> download the hard drive manufacturer's diagnostic utility and test the
> drive using it.
>
> If/when you get it to boot up right click My Computer, Properties,
> Advanced, Startup and Recovery and uncheck automatically restart (do it
> is Safe Mode if it's still rebooting in Normal Mode). Afterwards when
> the error causing the system halt occurs you will see it on screen,
> write it down exactly as displayed and post that info here.
>
> Steve
>
> > "Steve N." wrote:
> >
> >
> >>Heath wrote:
> >>
> >>>I originally thought my new HD was failing, but after buying a new one and
> >>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
> >>>any errors when I ran a disc check.
> >>>
> >>>So, I am guessing my problem was in my Windows install on the first HD. Is
> >>>there anyway that I can repair the Windows install on the original HD so I
> >>>don't loose all my contacts, schedule, and e-mails?
> >>>
> >>>I am a novice at this, so thanks for your patience!
> >>
> >>Please give details about exactly what's going on when trying to run the
> >>original installation, such as detailed error messages, conditions, etc.
> >>What exactly happens?
> >>
> >>Steve
> >>
> >>
>
>

Steve N.
07-10-2005, 12:23 AM
Heath wrote:
> I just began the Western Digital diagnostics test on this Raptor 74 GB hard
> drive and it has a little over 6 hours left until it completes. Hopefully it
> stays up long enough for the test to run its course and I will know for sure
> in the AM if there are any problems with it.
>
> When y machine does reboot I get the "just recovered from major" crash alert
> and am asked to report it to MS. When I do I get a pop up window that tells
> me the problem was caused by a driver. I have no idea which one, though.
> Any great programs I can run to track down the culprit?
>
> Thanks for your help everyone.

Start with motherboard chipset drivers, then video drivers. Update them
from the manufacturer. Video drivers are a common source of problems but
since you've been having trouble with the disk I'd be suspicious of the
disk drivers which are usually part of the MB chipset drivers.

Steve

>
> "Steve N." wrote:
>
>
>>Heath wrote:
>>
>>
>>>Ok, here goes.
>>>
>>>Originally my problem started when the computer would just up and reboot.
>>>The error message that came up asked me if I wanted to report the error to
>>>MS. After I reported the error I got a screen saying the problem resulted
>>>from an unknown driver problem.
>>>
>>>I started uninstalling non-essential programs and drivers to pin down the
>>>problem. After uninstalling several I got a message that popped up saying
>>>some windows feature was missing and that the computer rebooted.
>>>
>>>From that point I would be able to start up windows but it was only a minute
>>>or two before it would reboot on its own.
>>>
>>>After this happened several times I an "error-check" to be run the next time
>>>I rebooted. That done, I restarted windows and away the error check went. I
>>>kept getting several "error reading" messages and during the 5th step it
>>>would just lock up ... I forget what the message was.
>>>
>>>Now, after I installed windows on a new HD I was able to complete the error
>>>check on the original HD and didn't get any eror messages, I assume that
>>>means it was able to correct any errors?
>>>
>>>Now I just disconnected the new HD and plugged the old back in. Onbn reboot
>>>I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
>>>reboot.
>>>
>>
>>Thanks for the details.
>>
>>First, make sure there isn't a disk in the floppy drive (very common
>>cause of NTLDR missing error if the floppy drive is set as 1st boot device).
>>
>>If there isn't a floppy in the drive then try "Method 2: Use the
>>Recovery Console" listed here (it's for Win2K but will work for XP and
>>MS doesn't appear to have a seperate instructions specifically for XP
>>that I can find):
>>
>>How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
>>http://support.microsoft.com/kb/318728/#7
>>
>>While in Recovery Console I would also run CHKDSK /R /V. I'd also
>>download the hard drive manufacturer's diagnostic utility and test the
>>drive using it.
>>
>>If/when you get it to boot up right click My Computer, Properties,
>>Advanced, Startup and Recovery and uncheck automatically restart (do it
>>is Safe Mode if it's still rebooting in Normal Mode). Afterwards when
>>the error causing the system halt occurs you will see it on screen,
>>write it down exactly as displayed and post that info here.
>>
>>Steve
>>
>>
>>>"Steve N." wrote:
>>>
>>>
>>>
>>>>Heath wrote:
>>>>
>>>>
>>>>>I originally thought my new HD was failing, but after buying a new one and
>>>>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
>>>>>any errors when I ran a disc check.
>>>>>
>>>>>So, I am guessing my problem was in my Windows install on the first HD. Is
>>>>>there anyway that I can repair the Windows install on the original HD so I
>>>>>don't loose all my contacts, schedule, and e-mails?
>>>>>
>>>>>I am a novice at this, so thanks for your patience!
>>>>
>>>>Please give details about exactly what's going on when trying to run the
>>>>original installation, such as detailed error messages, conditions, etc.
>>>>What exactly happens?
>>>>
>>>>Steve
>>>>
>>>>
>>
>>

Steve N.
07-10-2005, 12:23 AM
Heath wrote:

> Ok, I just completed the MS memory test and my memory appears intact... all
> the tests passed.

I would also test using memtest86. When running memory tests let it do
several passes of all tests, one pass of the tests may not reveal a
problem. I let them go at least 7 full passes if not more.

>
> There wasn't a floppy in the drive and I've not tried to trouble shoot that
> problem yet for the NTLDR problem because it hasnt happened again.
>
> I did uncheck the automatic restarts as you suggested.
>
> The last two times it froze I got these numbers ...
>
> 1st -0x00000024 (0x001902FE, 0xAE937438, 0xAE937134, 0x804F954D)
>

Looks like might be a disk driver problem:
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_swhw.asp

> 2ND -0x0000007E(0x0000005, 0xF7B7286C, 0xF78C6C20, 0xF78C691C)
>
> ntfs.sys address F7B7286c base at F7B520000, Date stamp 41107eea

Could also be disk drivers, memory or other drivers. This is for an
upgrade situation but still may apply:
http://support.microsoft.com/default.aspx?scid=kb;en-us;330182

You may need to update your BIOS but don't do it unless the
documentation on the BIOS update specifically addresses your issues,
such as disk controller issues under XP.

Steve

>
> "Steve N." wrote:
>
>
>>Heath wrote:
>>
>>
>>>Ok, here goes.
>>>
>>>Originally my problem started when the computer would just up and reboot.
>>>The error message that came up asked me if I wanted to report the error to
>>>MS. After I reported the error I got a screen saying the problem resulted
>>>from an unknown driver problem.
>>>
>>>I started uninstalling non-essential programs and drivers to pin down the
>>>problem. After uninstalling several I got a message that popped up saying
>>>some windows feature was missing and that the computer rebooted.
>>>
>>>From that point I would be able to start up windows but it was only a minute
>>>or two before it would reboot on its own.
>>>
>>>After this happened several times I an "error-check" to be run the next time
>>>I rebooted. That done, I restarted windows and away the error check went. I
>>>kept getting several "error reading" messages and during the 5th step it
>>>would just lock up ... I forget what the message was.
>>>
>>>Now, after I installed windows on a new HD I was able to complete the error
>>>check on the original HD and didn't get any eror messages, I assume that
>>>means it was able to correct any errors?
>>>
>>>Now I just disconnected the new HD and plugged the old back in. Onbn reboot
>>>I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
>>>reboot.
>>>
>>
>>Thanks for the details.
>>
>>First, make sure there isn't a disk in the floppy drive (very common
>>cause of NTLDR missing error if the floppy drive is set as 1st boot device).
>>
>>If there isn't a floppy in the drive then try "Method 2: Use the
>>Recovery Console" listed here (it's for Win2K but will work for XP and
>>MS doesn't appear to have a seperate instructions specifically for XP
>>that I can find):
>>
>>How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
>>http://support.microsoft.com/kb/318728/#7
>>
>>While in Recovery Console I would also run CHKDSK /R /V. I'd also
>>download the hard drive manufacturer's diagnostic utility and test the
>>drive using it.
>>
>>If/when you get it to boot up right click My Computer, Properties,
>>Advanced, Startup and Recovery and uncheck automatically restart (do it
>>is Safe Mode if it's still rebooting in Normal Mode). Afterwards when
>>the error causing the system halt occurs you will see it on screen,
>>write it down exactly as displayed and post that info here.
>>
>>Steve
>>
>>
>>>"Steve N." wrote:
>>>
>>>
>>>
>>>>Heath wrote:
>>>>
>>>>
>>>>>I originally thought my new HD was failing, but after buying a new one and
>>>>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
>>>>>any errors when I ran a disc check.
>>>>>
>>>>>So, I am guessing my problem was in my Windows install on the first HD. Is
>>>>>there anyway that I can repair the Windows install on the original HD so I
>>>>>don't loose all my contacts, schedule, and e-mails?
>>>>>
>>>>>I am a novice at this, so thanks for your patience!
>>>>
>>>>Please give details about exactly what's going on when trying to run the
>>>>original installation, such as detailed error messages, conditions, etc.
>>>>What exactly happens?
>>>>
>>>>Steve
>>>>
>>>>
>>
>>

Heath
07-10-2005, 12:23 AM
Well, the disc diagnostics wrom WD shows several errors on the disc before it
stops running. I have contacted them and am waitng to hear back. I am going
to try the Norton Ghost approach for now and work out the replacement of this
drive as I can.

Thanks againf or all the ehlp.

"Steve N." wrote:

> Heath wrote:
>
> > Ok, I just completed the MS memory test and my memory appears intact... all
> > the tests passed.
>
> I would also test using memtest86. When running memory tests let it do
> several passes of all tests, one pass of the tests may not reveal a
> problem. I let them go at least 7 full passes if not more.
>
> >
> > There wasn't a floppy in the drive and I've not tried to trouble shoot that
> > problem yet for the NTLDR problem because it hasnt happened again.
> >
> > I did uncheck the automatic restarts as you suggested.
> >
> > The last two times it froze I got these numbers ...
> >
> > 1st -0x00000024 (0x001902FE, 0xAE937438, 0xAE937134, 0x804F954D)
> >
>
> Looks like might be a disk driver problem:
> http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_swhw.asp
>
> > 2ND -0x0000007E(0x0000005, 0xF7B7286C, 0xF78C6C20, 0xF78C691C)
> >
> > ntfs.sys address F7B7286c base at F7B520000, Date stamp 41107eea
>
> Could also be disk drivers, memory or other drivers. This is for an
> upgrade situation but still may apply:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;330182
>
> You may need to update your BIOS but don't do it unless the
> documentation on the BIOS update specifically addresses your issues,
> such as disk controller issues under XP.
>
> Steve
>
> >
> > "Steve N." wrote:
> >
> >
> >>Heath wrote:
> >>
> >>
> >>>Ok, here goes.
> >>>
> >>>Originally my problem started when the computer would just up and reboot.
> >>>The error message that came up asked me if I wanted to report the error to
> >>>MS. After I reported the error I got a screen saying the problem resulted
> >>>from an unknown driver problem.
> >>>
> >>>I started uninstalling non-essential programs and drivers to pin down the
> >>>problem. After uninstalling several I got a message that popped up saying
> >>>some windows feature was missing and that the computer rebooted.
> >>>
> >>>From that point I would be able to start up windows but it was only a minute
> >>>or two before it would reboot on its own.
> >>>
> >>>After this happened several times I an "error-check" to be run the next time
> >>>I rebooted. That done, I restarted windows and away the error check went. I
> >>>kept getting several "error reading" messages and during the 5th step it
> >>>would just lock up ... I forget what the message was.
> >>>
> >>>Now, after I installed windows on a new HD I was able to complete the error
> >>>check on the original HD and didn't get any eror messages, I assume that
> >>>means it was able to correct any errors?
> >>>
> >>>Now I just disconnected the new HD and plugged the old back in. Onbn reboot
> >>>I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
> >>>reboot.
> >>>
> >>
> >>Thanks for the details.
> >>
> >>First, make sure there isn't a disk in the floppy drive (very common
> >>cause of NTLDR missing error if the floppy drive is set as 1st boot device).
> >>
> >>If there isn't a floppy in the drive then try "Method 2: Use the
> >>Recovery Console" listed here (it's for Win2K but will work for XP and
> >>MS doesn't appear to have a seperate instructions specifically for XP
> >>that I can find):
> >>
> >>How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
> >>http://support.microsoft.com/kb/318728/#7
> >>
> >>While in Recovery Console I would also run CHKDSK /R /V. I'd also
> >>download the hard drive manufacturer's diagnostic utility and test the
> >>drive using it.
> >>
> >>If/when you get it to boot up right click My Computer, Properties,
> >>Advanced, Startup and Recovery and uncheck automatically restart (do it
> >>is Safe Mode if it's still rebooting in Normal Mode). Afterwards when
> >>the error causing the system halt occurs you will see it on screen,
> >>write it down exactly as displayed and post that info here.
> >>
> >>Steve
> >>
> >>
> >>>"Steve N." wrote:
> >>>
> >>>
> >>>
> >>>>Heath wrote:
> >>>>
> >>>>
> >>>>>I originally thought my new HD was failing, but after buying a new one and
> >>>>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
> >>>>>any errors when I ran a disc check.
> >>>>>
> >>>>>So, I am guessing my problem was in my Windows install on the first HD. Is
> >>>>>there anyway that I can repair the Windows install on the original HD so I
> >>>>>don't loose all my contacts, schedule, and e-mails?
> >>>>>
> >>>>>I am a novice at this, so thanks for your patience!
> >>>>
> >>>>Please give details about exactly what's going on when trying to run the
> >>>>original installation, such as detailed error messages, conditions, etc.
> >>>>What exactly happens?
> >>>>
> >>>>Steve
> >>>>
> >>>>
> >>
> >>
>
>

BNR
07-10-2005, 12:24 AM
My usenet provider hasn't deleted this thread. I'll monitor it as long as
possible.

Thats a Memory problem. Swap em.

Or post the timings your using in the BIOS so we can try and help you
resolve the system's instability. Those are memory registers in that
error.. Minute I saw it refer to an unknown driver, I knew it was Memory.
If Memory had correct timings, you'd have a specific file in the error
message. It won't have that if the controller can't read the DDRAM cuz the
timings are off kilter. Please provide us with make/model of Memory and
Mobo, for further instruction.

Thank you for allowing me to help. Good day.

BNR
07-10-2005, 12:24 AM
Oh! BTW, I didn't ask you to run memtest. It confirms faulty memory. I
believe the other
poster did.

I asked you for info. You know like the make/model of memory and mobo. I'm
glad you
ran memtest. Your having stability problems as a result of incorrect
timings from memory
that has been decom'd.

Thank you for allowing me to Help. Good day.

Heath
07-10-2005, 12:24 AM
The MOBO is a DFI 875P LANPARTY 875P-T and the RAM is 2 Gigs of
TWINX1024-3200C2PT COR RT

"BNR" wrote:

> My usenet provider hasn't deleted this thread. I'll monitor it as long as
> possible.
>
> Thats a Memory problem. Swap em.
>
> Or post the timings your using in the BIOS so we can try and help you
> resolve the system's instability. Those are memory registers in that
> error.. Minute I saw it refer to an unknown driver, I knew it was Memory.
> If Memory had correct timings, you'd have a specific file in the error
> message. It won't have that if the controller can't read the DDRAM cuz the
> timings are off kilter. Please provide us with make/model of Memory and
> Mobo, for further instruction.
>
> Thank you for allowing me to help. Good day.
>
>
>

Steve N.
07-10-2005, 12:25 AM
Heath wrote:

> Well, the disc diagnostics wrom WD shows several errors on the disc before it
> stops running. I have contacted them and am waitng to hear back. I am going
> to try the Norton Ghost approach for now and work out the replacement of this
> drive as I can.
>
> Thanks againf or all the ehlp.
>

You're welcome.

Steve

> "Steve N." wrote:
>
>
>>Heath wrote:
>>
>>
>>>Ok, I just completed the MS memory test and my memory appears intact... all
>>>the tests passed.
>>
>>I would also test using memtest86. When running memory tests let it do
>>several passes of all tests, one pass of the tests may not reveal a
>>problem. I let them go at least 7 full passes if not more.
>>
>>
>>>There wasn't a floppy in the drive and I've not tried to trouble shoot that
>>>problem yet for the NTLDR problem because it hasnt happened again.
>>>
>>>I did uncheck the automatic restarts as you suggested.
>>>
>>>The last two times it froze I got these numbers ...
>>>
>>>1st -0x00000024 (0x001902FE, 0xAE937438, 0xAE937134, 0x804F954D)
>>>
>>
>>Looks like might be a disk driver problem:
>>http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prmd_stp_swhw.asp
>>
>>
>>>2ND -0x0000007E(0x0000005, 0xF7B7286C, 0xF78C6C20, 0xF78C691C)
>>>
>>>ntfs.sys address F7B7286c base at F7B520000, Date stamp 41107eea
>>
>>Could also be disk drivers, memory or other drivers. This is for an
>>upgrade situation but still may apply:
>>http://support.microsoft.com/default.aspx?scid=kb;en-us;330182
>>
>>You may need to update your BIOS but don't do it unless the
>>documentation on the BIOS update specifically addresses your issues,
>>such as disk controller issues under XP.
>>
>>Steve
>>
>>
>>>"Steve N." wrote:
>>>
>>>
>>>
>>>>Heath wrote:
>>>>
>>>>
>>>>
>>>>>Ok, here goes.
>>>>>
>>>>>Originally my problem started when the computer would just up and reboot.
>>>>>The error message that came up asked me if I wanted to report the error to
>>>>>MS. After I reported the error I got a screen saying the problem resulted
>>>>
>>>>>from an unknown driver problem.
>>>>
>>>>>I started uninstalling non-essential programs and drivers to pin down the
>>>>>problem. After uninstalling several I got a message that popped up saying
>>>>>some windows feature was missing and that the computer rebooted.
>>>>>
>>>>
>>>>>From that point I would be able to start up windows but it was only a minute
>>>>
>>>>>or two before it would reboot on its own.
>>>>>
>>>>>After this happened several times I an "error-check" to be run the next time
>>>>>I rebooted. That done, I restarted windows and away the error check went. I
>>>>>kept getting several "error reading" messages and during the 5th step it
>>>>>would just lock up ... I forget what the message was.
>>>>>
>>>>>Now, after I installed windows on a new HD I was able to complete the error
>>>>>check on the original HD and didn't get any eror messages, I assume that
>>>>>means it was able to correct any errors?
>>>>>
>>>>>Now I just disconnected the new HD and plugged the old back in. Onbn reboot
>>>>>I get the message "NTDLR is missing" and told to use CTRL ALT Delete to
>>>>>reboot.
>>>>>
>>>>
>>>>Thanks for the details.
>>>>
>>>>First, make sure there isn't a disk in the floppy drive (very common
>>>>cause of NTLDR missing error if the floppy drive is set as 1st boot device).
>>>>
>>>>If there isn't a floppy in the drive then try "Method 2: Use the
>>>>Recovery Console" listed here (it's for Win2K but will work for XP and
>>>>MS doesn't appear to have a seperate instructions specifically for XP
>>>>that I can find):
>>>>
>>>>How to troubleshoot the "NTLDR Is Missing" error message in Windows 2000
>>>>http://support.microsoft.com/kb/318728/#7
>>>>
>>>>While in Recovery Console I would also run CHKDSK /R /V. I'd also
>>>>download the hard drive manufacturer's diagnostic utility and test the
>>>>drive using it.
>>>>
>>>>If/when you get it to boot up right click My Computer, Properties,
>>>>Advanced, Startup and Recovery and uncheck automatically restart (do it
>>>>is Safe Mode if it's still rebooting in Normal Mode). Afterwards when
>>>>the error causing the system halt occurs you will see it on screen,
>>>>write it down exactly as displayed and post that info here.
>>>>
>>>>Steve
>>>>
>>>>
>>>>
>>>>>"Steve N." wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Heath wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>I originally thought my new HD was failing, but after buying a new one and
>>>>>>>reinstalling Windows I plugged in the HD I thought was bad and didn't find
>>>>>>>any errors when I ran a disc check.
>>>>>>>
>>>>>>>So, I am guessing my problem was in my Windows install on the first HD. Is
>>>>>>>there anyway that I can repair the Windows install on the original HD so I
>>>>>>>don't loose all my contacts, schedule, and e-mails?
>>>>>>>
>>>>>>>I am a novice at this, so thanks for your patience!
>>>>>>
>>>>>>Please give details about exactly what's going on when trying to run the
>>>>>>original installation, such as detailed error messages, conditions, etc.
>>>>>>What exactly happens?
>>>>>>
>>>>>>Steve
>>>>>>
>>>>>>
>>>>
>>>>
>>

BNR
07-10-2005, 12:25 AM
There are 4 sticks in it? I imagine both banks are full and matched with
correct sets.

Are you able to find the timings in the DFI board BIOS? Are they setup to
match the memory specifications for these sticks. Corsair says to use
2-3-3-6

Or another words.
RAS# 2
CAS# 3
RAS to CAS 3

Its interesting to note, your BIOS uses the JEDEC standard latencies for
PC3200, which is 3-3-3-8 at bootup.

Thanks for allowing me to help. Good day


Windows problem ... not sure where to start