Vista Tutorial - TOP: C0000218 {Registry File Failure): how to fix it in Vista Ulti

Hi,

Just try it. I've seen matched sets fail. If it passes, then you know it's
not the problem, but I'm still thinking that it is.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"cooncheese70" <cooncheese70.2u837g@DoNotSpam.com> wrote in message
news:cooncheese70.2u837g@DoNotSpam.com...
>
> But all my ram is the same brand/ model, and I bought all 4gb at the
> same time.
>
> How does that work??
>
> Rick Rogers;3032264 Wrote:
>> Hi,
>>
>> Install all 4GB, then run the memory diagnostics. While each 2GB may
>> be
>> fine, they may not be compatible with the other 2GB.
>>
>> --
>> Best of Luck,
>>
>> Rick Rogers, aka "Nutcase" - Microsoft MVP
>> http://mvp.support.microsoft.com/
>> Windows help - www.rickrogers.org
>> My thoughts http://rick-mvp.blogspot.com
>>
>> "cooncheese70" <cooncheese70.2u6bbf@DoNotSpam.com> wrote in message
>> news:cooncheese70.2u6bbf@DoNotSpam.com...
>> >
>> > Hey,
>> >
>> > I have tried swapping them around many times with no success.
>> >
>> > I'm sure its not the RAM. My thoughts is either mobo or Vista.
>> >
>> >
>> > --
>> > cooncheese70
>> >
>> ------------------------------------------------------------------------
>> > cooncheese70's Profile:
>> http://forums.techarena.in/member.php?userid=26652
>> > View this thread: http://forums.techarena.in/showthread.php?t=677924
>> >
>> > http://forums.techarena.in
>> >
>
>
> --
> cooncheese70
> ------------------------------------------------------------------------
> cooncheese70's Profile: http://forums.techarena.in/member.php?userid=26652
> View this thread: http://forums.techarena.in/showthread.php?t=677924
>
> http://forums.techarena.in
>

So, should I run 'Memtest86+' (http://www.memtest.org/) to test the
ram??


--
cooncheese70
------------------------------------------------------------------------
cooncheese70's Profile: http://forums.techarena.in/member.php?userid=26652
View this thread: http://forums.techarena.in/showthread.php?t=677924

http://forums.techarena.in

Hi,

You can, but there is now an onboard memory diagnostic tool. Just type
'memory diagnostic' into the search box.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

"cooncheese70" <cooncheese70.2u9bng@DoNotSpam.com> wrote in message
news:cooncheese70.2u9bng@DoNotSpam.com...
>
> So, should I run 'Memtest86+' (http://www.memtest.org/) to test the
> ram??
>
>
> --
> cooncheese70
> ------------------------------------------------------------------------
> cooncheese70's Profile: http://forums.techarena.in/member.php?userid=26652
> View this thread: http://forums.techarena.in/showthread.php?t=677924
>
> http://forums.techarena.in
>

I have tried 3 different makes of memory, I have also run MEM test and the built in Vista memory test countless times and never found an error. Take a look at this forum; I have the BIOS screen shots with timings voltages etc.

GA-965P-DS3 (rev. 3.3) F11 BIOS memory problem - PC Perspective Forums

Mick B

On Wed, 25 Jul 2007 05:47:09 -0400, "Rick Rogers" wrote:

>You can, but there is now an onboard memory diagnostic tool. Just type
>'memory diagnostic' into the search box.

I'd use MemTest86, as it is MUCH safer.

The onboard tool works as follows:
- may require Windows to launch
- writes to the installation so that it runs next boot
- starts to run after the next boot
- does a quick test and then stops, unless you "etc."
- writes results to the HD installation's even log

In contrast, MemTest86:
- boots off the CDR
- repeats tests until stopped by the user
- accumulates test results on screen
- does not write to the HD at all

When RAM is bad, all bets are off. Not only can stuff being written
to disk be corrupted, but where they are written on disk can be
corrupted, too (e.g. you can splat over NTFS's MFT, etc.).

Also, most "read disk" calls are one bit-flip away from being "write
disk" calls, so you don't want an OS that requires thousands of read
operations off HD to boot (not to mention all the automatic write
operations; temp, page file, directory access timestamps, etc.)

When BIOS detects a memory parity error, it halts the system, because
it "knows" this is the only safe thing to do.

Similarly, Windows will halt the system when errors are such that
context loss makes it unsafe to continue; BSoDs in 9x, STOP in NT.

MS is either losing this clue, or is treating us with contempt (e.g.
it's more important to cut support calls than to preserve user's HD
contents) when they move from halting on BSoDs to automatically
restarting the system (effectively, hiding these errors).

So when MS designs a RAM tester specifically for use where RAM quality
is suspect, and this process makes liberal use of both read and write
traffic on HD, one wonders if they've completely lost the plot.



>--------------- ----- ---- --- -- - - -
To one who only has a hammer,
everything looks like a nail
>--------------- ----- ---- --- -- - - -

cquirke
That comment does not make sense. "I'd use MemTest86, as it is MUCH safer" - "In contrast, MemTest86"

Mick

On Wed, 1 Aug 2007 07:28:37 -0500, Mick_B

>cquirke

Hi!

>That comment does not make sense. "I'd use MemTest86, as it is MUCH
>safer" - "In contrast, MemTest86"

Wrong grouping - it's supposed to read as...

I'd use MemTest86, as it is MUCH safer.

The onboard tool works as follows:
<blah blah>
In contrast, MemTest86:
<blee blee>

IOW, the initial assertion does not run into the others (hence ended
as a sentence via . rather than linked forward to one item via : or a
sequence of items via ... )

Sorry if I threw your parser ;-)



>--------------- ---- --- -- - - - -
Saws are too hard to use.
Be easier to use!
>--------------- ---- --- -- - - - -

I have the exact same MB with the same memory setup and am experiencing
the same problems as every one here. memtest86 runs fine....just get
the BSOD all the time Hope someone finds a solution.


--
tommiy
------------------------------------------------------------------------
tommiy's Profile: http://forums.techarena.in/member.php?userid=29417
View this thread: http://forums.techarena.in/showthread.php?t=677924

http://forums.techarena.in

I have been running with 4GB for 1 week+ with no problems and tonight
when I turn the computer on I got BSOD after BSOD until I coundn't
handle it and ripped out 2GB so I could work.

This is really pissing me off.

Anyone got any other ideas/thoughts???


--
cooncheese70
------------------------------------------------------------------------
cooncheese70's Profile: http://forums.techarena.in/member.php?userid=26652
View this thread: http://forums.techarena.in/showthread.php?t=677924

http://forums.techarena.in

ran memtest all night again...no issues everything passed. before
running memtest everything was fine....after memtest bsod same
crap...this surely has to be a gigabyte issue...what version of bios is
everyone running?


--
tommiy
------------------------------------------------------------------------
tommiy's Profile: http://forums.techarena.in/member.php?userid=29417
View this thread: http://forums.techarena.in/showthread.php?t=677924

http://forums.techarena.in