Windows Vista Beta | WinVistaBeta.com - Message | Strange problem

September 06, 2008  
Subject: Strange problem
Group: microsoft.public.windows.vista.general
Date: 7/24/2008 9:02:13 PM
From: brahmasoccer09 [Email Address Protection]


*System Specs*
AMD 4200+ X2
WinFast nForce 570 SLI mobo with Jmicron controller
250GB Seagate Barracuda
Standard Dell CD/DVD drive
EVGA 7600GT
SoundBlaster Audigy
Vista 32-bit
3.25 GB RAM (assorted brands)

*Problems:*
Okay, here's my problem: I'll successfully install Vista after a clean
format of the entire hard drive. I'll get all my programs installed, and
everything nice and personalized. Then, for some reason, I'll be forced
(due to a lock-up) to do the hard reset (pushing the reset button on the
front of the case). When the system reboots, the "Windows Boot Manager"
will say "A registry file is missing, or corrupt" with the status
0xc0000011. So I'll be forced to boot with the installation CD and then
"Repair". So after a while, it'll fix itself declaring that chkdsk (Root
cause found: System volume is corrupt, Repair action: File System Repair
(chkdsk) Result: Completed sucessfully: Error code = 0x0) solved the
problem.
Following that, the system will restart and give me the Boot Manager
error again, (Status, however is now 0xc000000f). So then I'll re-enter
the Install CD and repair again, this time cancelling System Restore (as
it never works, I've tried) and letting it complete, finishing with a
Registry Roll Back. It'll restart and YAY, THE DESKTOP!
But, this is not to be, as after a few seconds, the system locks up and
then I'll be forced to hard reset, which starts the process all over
again.

*Solutions Tried:
*Well, I've formatted and retried the install several times, and the
same issue pops up within 24 hours. Sometimes, I'll not install anything
and the problems will still occur.
Linux Live CD works fine.
I've sent the HD back to Seagate (as my first suspicion was a bad HD)
and got a new one, with the same issue occuring.
I've used different Vista install disks, same result.

Can anyone help? Is this a hardware problem as I suspect? But which
piece of hardware could it be?

Any help would be greatly appreciated! Thanks!


--
brahmasoccer09

Back
Subject: Re: Strange problem
Group: microsoft.public.windows.vista.general
Date: 7/25/2008 12:39:40 AM
From: "Roberto le Corneille" [Email Address Protection]

"brahmasoccer09" <guest@unknown-email.com> wrote in message
news:48bc26bc63094515c63db03b647c6177@nntp-gateway.com...
>
> *System Specs*
> AMD 4200+ X2
> WinFast nForce 570 SLI mobo with Jmicron controller
> 250GB Seagate Barracuda
> Standard Dell CD/DVD drive
> EVGA 7600GT
> SoundBlaster Audigy
> Vista 32-bit
> 3.25 GB RAM (assorted brands)
>
> *Problems:*
> Okay, here's my problem: I'll successfully install Vista after a clean
> format of the entire hard drive. I'll get all my programs installed, and
> everything nice and personalized. Then, for some reason, I'll be forced
> (due to a lock-up) to do the hard reset (pushing the reset button on the
> front of the case). When the system reboots, the "Windows Boot Manager"
> will say "A registry file is missing, or corrupt" with the status
> 0xc0000011. So I'll be forced to boot with the installation CD and then
> "Repair". So after a while, it'll fix itself declaring that chkdsk (Root
> cause found: System volume is corrupt, Repair action: File System Repair
> (chkdsk) Result: Completed sucessfully: Error code = 0x0) solved the
> problem.
> Following that, the system will restart and give me the Boot Manager
> error again, (Status, however is now 0xc000000f). So then I'll re-enter
> the Install CD and repair again, this time cancelling System Restore (as
> it never works, I've tried) and letting it complete, finishing with a
> Registry Roll Back. It'll restart and YAY, THE DESKTOP!
> But, this is not to be, as after a few seconds, the system locks up and
> then I'll be forced to hard reset, which starts the process all over
> again.
>
> *Solutions Tried:
> *Well, I've formatted and retried the install several times, and the
> same issue pops up within 24 hours. Sometimes, I'll not install anything
> and the problems will still occur.
> Linux Live CD works fine.
> I've sent the HD back to Seagate (as my first suspicion was a bad HD)
> and got a new one, with the same issue occuring.
> I've used different Vista install disks, same result.
>
> Can anyone help? Is this a hardware problem as I suspect? But which
> piece of hardware could it be?
>
> Any help would be greatly appreciated! Thanks!

> brahmasoccer09

3.25 GB RAM (assorted brands) *may* be your problem, do some testing I
like memtest86
D/L and create a bootable CD http://www.memtest86.com/
rgds
Roberto


Back
Subject: Re: Strange problem
Group: microsoft.public.windows.vista.general
Date: 7/25/2008 2:30:46 AM
From: "Steve Thackery" [Email Address Protection]

I'd be looking at the temperature of the CPU (although this normally causes
a shut down rather than a freeze). The next most obvious thing would be the
memory. I bet that's the problem.

Third choice would be to remove and reseat all the connectors and cards
(this works surprisingly often).

Fourth choice would be to swap the power supply.

SteveT


Back
Subject: Re: Strange problem
Group: microsoft.public.windows.vista.general
Date: 7/25/2008 5:05:06 PM
From: Bruce Chambers [Email Address Protection]

brahmasoccer09 wrote:
> *System Specs*
> Snipped....

> 3.25 GB RAM (assorted brands)
>

The most likely cause of the symptoms you describe.

It is absolutely essential that all RAM module(s) be fully
compatible with both the motherboard and/or any other RAM module(s)
already in the system. Additionally, there are sometimes jumper
switches on older motherboards that need to be reset for new RAM
configurations. Consult your motherboard's manual or the manufacturer's
web site for specific instructions and compatibility requirements.

If you cannot lay your hands upon the computer's manual and the
manufacturer doesn't provide a support web site, you can use these
utilities to help determine the correct type of RAM needed:

SiSoft's Sandra
http://www.sisoftware.co.uk/index.php?dir=&location=sware_dl&lang=en

Belarc Advisor
http://www.belarc.com/free_download.html

Unlimited Possibilities' AIDA32
http://forum.aumha.org/overflow/aida32.zip

Also, Crucial Memory's web site (www.crucial.com) has a database to
help to find the right RAM for your specific make and model computer
and/or motherboard. (Incidentally, Crucial is the only company from
which I ever buy RAM. I've never been disappointed.)

Beyond that, this KB Article, although written for WinXP, should
provide you guidance in finding just what is corrupting your registry:

How to Troubleshoot Registry Corruption Issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;822705

> *Problems:*
> Okay, here's my problem: I'll successfully install Vista after a clean
> format of the entire hard drive. I'll get all my programs installed, and
> everything nice and personalized. Then, for some reason, I'll be forced
> (due to a lock-up) to do the hard reset (pushing the reset button on the
> front of the case). When the system reboots, the "Windows Boot Manager"
> will say "A registry file is missing, or corrupt" with the status
> 0xc0000011. So I'll be forced to boot with the installation CD and then
> "Repair". So after a while, it'll fix itself declaring that chkdsk (Root
> cause found: System volume is corrupt, Repair action: File System Repair
> (chkdsk) Result: Completed sucessfully: Error code = 0x0) solved the
> problem.
> Following that, the system will restart and give me the Boot Manager
> error again, (Status, however is now 0xc000000f). So then I'll re-enter
> the Install CD and repair again, this time cancelling System Restore (as
> it never works, I've tried) and letting it complete, finishing with a
> Registry Roll Back. It'll restart and YAY, THE DESKTOP!
> But, this is not to be, as after a few seconds, the system locks up and
> then I'll be forced to hard reset, which starts the process all over
> again.
>
> *Solutions Tried:
> *Well, I've formatted and retried the install several times, and the
> same issue pops up within 24 hours. Sometimes, I'll not install anything
> and the problems will still occur.


Repeatedly repairing or re-installing the OS does nothing to address
the underlying hardware problem that you have.


> Linux Live CD works fine.


Not relevant.


> I've sent the HD back to Seagate (as my first suspicion was a bad HD)
> and got a new one, with the same issue occuring.


Making it more likely to be a RAM issue.




--

Bruce Chambers

Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html

http://support.microsoft.com/default.aspx/kb/555375

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. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot

Back
Subject: Re: Strange problem
Group: microsoft.public.windows.vista.general
Date: 7/25/2008 5:06:17 PM
From: Bruce Chambers [Email Address Protection]

brahmasoccer09 wrote:
> Okay, thanks for the tip.s I'm running Memtest86 v1.7 off a Linux CD.
> It's going on 8 hours now, does that mean there's a problem? No errors
> yet, but just 5 PASS.
>
>


That only means that the RAM is not defective. It doesn't necessarily
need that all modules are compatible with the motherboard or one another.


--

Bruce Chambers

Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html

http://support.microsoft.com/default.aspx/kb/555375

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. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot

Back
Subject: Re: Strange problem
Group: microsoft.public.windows.vista.general
Date: 7/25/2008 5:20:42 PM
From: Hobbes [Email Address Protection]

Roberto le Corneille wrote:
> "brahmasoccer09" <guest@unknown-email.com> wrote in message
> news:48bc26bc63094515c63db03b647c6177@nntp-gateway.com...
>>
>> *System Specs*
>> AMD 4200+ X2
>> WinFast nForce 570 SLI mobo with Jmicron controller
>> 250GB Seagate Barracuda
>> Standard Dell CD/DVD drive
>> EVGA 7600GT
>> SoundBlaster Audigy
>> Vista 32-bit
>> 3.25 GB RAM (assorted brands)
>>
>> *Problems:*
>> Okay, here's my problem: I'll successfully install Vista after a clean
>> format of the entire hard drive. I'll get all my programs installed, and
>> everything nice and personalized. Then, for some reason, I'll be forced
>> (due to a lock-up) to do the hard reset (pushing the reset button on the
>> front of the case). When the system reboots, the "Windows Boot Manager"
>> will say "A registry file is missing, or corrupt" with the status
>> 0xc0000011. So I'll be forced to boot with the installation CD and then
>> "Repair". So after a while, it'll fix itself declaring that chkdsk (Root
>> cause found: System volume is corrupt, Repair action: File System Repair
>> (chkdsk) Result: Completed sucessfully: Error code = 0x0) solved the
>> problem.
>> Following that, the system will restart and give me the Boot Manager
>> error again, (Status, however is now 0xc000000f). So then I'll re-enter
>> the Install CD and repair again, this time cancelling System Restore (as
>> it never works, I've tried) and letting it complete, finishing with a
>> Registry Roll Back. It'll restart and YAY, THE DESKTOP!
>> But, this is not to be, as after a few seconds, the system locks up and
>> then I'll be forced to hard reset, which starts the process all over
>> again.
>>
>> *Solutions Tried:
>> *Well, I've formatted and retried the install several times, and the
>> same issue pops up within 24 hours. Sometimes, I'll not install anything
>> and the problems will still occur.
>> Linux Live CD works fine.
>> I've sent the HD back to Seagate (as my first suspicion was a bad HD)
>> and got a new one, with the same issue occuring.
>> I've used different Vista install disks, same result.
>>
>> Can anyone help? Is this a hardware problem as I suspect? But which
>> piece of hardware could it be?
>>
>> Any help would be greatly appreciated! Thanks!
>
>> brahmasoccer09
>
> 3.25 GB RAM (assorted brands) *may* be your problem, do some testing
> I like memtest86
> D/L and create a bootable CD http://www.memtest86.com/
> rgds
> Roberto

Since you have a Dell CD/DVD, is it a Dell system ?
If so, buy your RAM from Dell.

non-Dell RAM causes all kinds of problems....I had 1 GB Dell ram mixed
with 1 GB purchased locally...non-stop crashes.
Pulled the non-Dell ram, bought a GB of RAM from Dell...good to go.

Back
Subject: Re: Strange problem
Group: microsoft.public.windows.vista.general
Date: 7/26/2008 12:48:20 AM
From: Charlie Tame [Email Address Protection]

brahmasoccer09 wrote:
> Thanks for your input. I'm a bit weary to stop the Memtest (now that
> it's in its 12th hour), but I will try that tomorrow morning after I let
> it run overnight. The memory's worked fine in that system since I built
> it 6 months ago (the problem is only three weeks). They also worked in
> the Dell E510 together. They're 'this, '
> (http://www.newegg.com/Product/Product.aspx?Item=N82E16820144038)'this'
> (http://www.newegg.com/Product/Product.aspx?Item=N82E16820146055), and
> 'this' (http://www.newegg.com/Product/Product.aspx?Item=N82E16820145525)
> one as well as a 256MB stick from the old E510 (which is a Samsung dunno
> what specs). So technically it's not 3.25GB its 3,328 MB. If it's any of
> the sticks, I'm guessing its that 6-year-old Samsung one.
>
>

Don't forget that the memory test is the CPU reading and writing memory
and nothing much else is going on. During real use you have DMA,
interrupts and other stuff happening more or less at random (random is
not the right word but you know what I mean). Therefore timing issues
may come into the calculation that will not show up in a straight memory
test.

Timing changes could come from a new device, a hardware failure, updated
drivers etc.

Back