Vista - bugs and limits questions

Hello, I run vista x64 on a pc with nvidia geforce 6800 ultra card
(pci-e) and 4gb of ram, aftes some mins the system slow down and
graphics result corrupted and unrefreshed...
If I use vista x32 all works fine but I see 3gb...
Someone have the same problem with vista x64 ? Any solution ?
The limit of vista x32 is 3gb of ram ?

"c-howdy" <captain.howdy@nospam.libero.it> wrote ...
> Hello, I run vista x64 on a pc with nvidia geforce 6800 ultra card (pci-e)
> and 4gb of ram, aftes some mins the system slow down and graphics result
> corrupted and unrefreshed...
> If I use vista x32 all works fine but I see 3gb...
> Someone have the same problem with vista x64 ? Any solution ?
> The limit of vista x32 is 3gb of ram ?


This was discussed a lot in the newsgroup, just earlier today.

As a starting point, see this Microsoft KnowledgeBase article 929605,
regarding limits on RAM:
http://support.microsoft.com/kb/929605/
Basically, 32 bit Windows will only see ~3GB even when 4Gb is physically
present. This is normal, and by design.

But the graphics corruption problem sounds unusual. What model of computer
and/or mother board, do you have? Your machine may need a BIOS upgrade to
deal with 4GB of RAM.

And of course, make sure you have the latest 64 bit Forceware drivers from
nVidia:
http://www.nvidia.com/object/winvista_x64_158.24.html

--
Andrew McLaren
amclar (at) optusnet dot com dot au

Thankyou Andrew for reply, my motherboard is the intel d955xbk and I've
update with latest bios...
After some mins, around 20 mins, the system slow down and graphics are
corrupted with lines and unrefreshed fields... only with vista x64,
sometimes ago on the same pc hardware config, windows xp x64 work very
well...

Andrew McLaren ha scritto:
> "c-howdy" <captain.howdy@nospam.libero.it> wrote ...
>> Hello, I run vista x64 on a pc with nvidia geforce 6800 ultra card (pci-e)
>> and 4gb of ram, aftes some mins the system slow down and graphics result
>> corrupted and unrefreshed...
>> If I use vista x32 all works fine but I see 3gb...
>> Someone have the same problem with vista x64 ? Any solution ?
>> The limit of vista x32 is 3gb of ram ?
>
>
> This was discussed a lot in the newsgroup, just earlier today.
>
> As a starting point, see this Microsoft KnowledgeBase article 929605,
> regarding limits on RAM:
> http://support.microsoft.com/kb/929605/
> Basically, 32 bit Windows will only see ~3GB even when 4Gb is physically
> present. This is normal, and by design.
>
> But the graphics corruption problem sounds unusual. What model of computer
> and/or mother board, do you have? Your machine may need a BIOS upgrade to
> deal with 4GB of RAM.
>
> And of course, make sure you have the latest 64 bit Forceware drivers from
> nVidia:
> http://www.nvidia.com/object/winvista_x64_158.24.html
>

"c-howdy" <captain.howdy@nospam.libero.it> wrote...
> Thankyou Andrew for reply, my motherboard is the intel d955xbk and I've
> update with latest bios...
> After some mins, around 20 mins, the system slow down and graphics are
> corrupted with lines and unrefreshed fields... only with vista x64,
> sometimes ago on the same pc hardware config, windows xp x64 work very

It certainly sounds like a problem with the 64 bit drivers. Not too
surprising; since 64 bit drivers may tend to be a bit behind in development,
compared to 32 bit drivers.

Make sure you have the lestes nVidia grpahics drivers, as I mentioned
before. Then, make sure all the other drivers on the system are up to date.
Get the Intel-specific drivers from:
http://downloadcenter.intel.com/Filt...ting%20Systems

After you have updated BIOS and drivers, there's not many other
user-configurable things for you to try. The problem doesn't sound like any
common or widespread ones in Vista, itself; it's probably something fairly
specific to the combination of hardware in your machine. If it is a
brand-name machine and still under warrantee, take the issue to the OEM. If
you built the machine yourself ... well, that's the risk you take :-)
(speaking as one who built most of my own PCs :-). Although Windows NT
(including Vista) has process separation, all device drivers run in kernel
mode so share the same address space. Hence it is possible for one driver to
stomp on the memory of another driver. Something is corrupting your video
memory - hence the artifacts on the screen - so you need to find out where
the memory conflict is. Can be solved with a kernel mode debugger, butt
that's not something we can do via newsgroups.

Other folks might have extra ideas, hope this helps a bit.

--
Andrew McLaren
amclar (at) optusnet dot com dot au

Hi,
When I get more time I try the WinDbg :-)
I thankyou very much again Andrew.


Andrew McLaren ha scritto:
> "c-howdy" <captain.howdy@nospam.libero.it> wrote...
>> Thankyou Andrew for reply, my motherboard is the intel d955xbk and I've
>> update with latest bios...
>> After some mins, around 20 mins, the system slow down and graphics are
>> corrupted with lines and unrefreshed fields... only with vista x64,
>> sometimes ago on the same pc hardware config, windows xp x64 work very
>
> It certainly sounds like a problem with the 64 bit drivers. Not too
> surprising; since 64 bit drivers may tend to be a bit behind in development,
> compared to 32 bit drivers.
>
> Make sure you have the lestes nVidia grpahics drivers, as I mentioned
> before. Then, make sure all the other drivers on the system are up to date.
> Get the Intel-specific drivers from:
> http://downloadcenter.intel.com/Filt...ting%20Systems
>
> After you have updated BIOS and drivers, there's not many other
> user-configurable things for you to try. The problem doesn't sound like any
> common or widespread ones in Vista, itself; it's probably something fairly
> specific to the combination of hardware in your machine. If it is a
> brand-name machine and still under warrantee, take the issue to the OEM. If
> you built the machine yourself ... well, that's the risk you take :-)
> (speaking as one who built most of my own PCs :-). Although Windows NT
> (including Vista) has process separation, all device drivers run in kernel
> mode so share the same address space. Hence it is possible for one driver to
> stomp on the memory of another driver. Something is corrupting your video
> memory - hence the artifacts on the screen - so you need to find out where
> the memory conflict is. Can be solved with a kernel mode debugger, butt
> that's not something we can do via newsgroups.
>
> Other folks might have extra ideas, hope this helps a bit.
>