Newview.exe

Ok I have a technical issue that is driving me nuts.

I have spent the last 8hrs trying to stay in sl for more than 3 mins at a time.

I Crash with the newview.exe which is a SL file.

For almost one year I ran SL with a Celeron 1.1 with 680 megs of Mem with a Nvida 32meg card untll mid October.

I then upgraded to a Nvida 128 meg vid card. No problems from Oct. till Today.

Three days ago I switched to a Anthlon XP2000 system with 865 meg mem till the 2700 chip and the other 512 chip came in and added a 160 Meg Hard drive. In the process of the Hard drive I had to switch operating systems from XP Pro to XP Home. Essencialy the same operating systems.

Now I cannot stay in SL more than 3 mins till I crash because of newview.exe.

It does mention something about Offset and gives a page frame location but for the life of me it makes no sense because the hard drive with the old operating system workedlast night no new updates nothing except adding the 512 mem to bring it up to 865 and now I crash.

I have so far this evening done the following.
Updated the Motherboard drivers.
Updated the vid card drivers
Updated the hardrive drivers
Updated windows to SP1
So at this point I am at a loss and very flustrated.

Can anyone help based on the information that I have gven thus far.

The File causing the crash is newview.exe

if you can help I would greatly appreciate it.

Sincerely, Shadow

Did you have to change the board out to change chips? Im guessing its the AGP driver on the board maybe?

Have you reinstalled SL?

Yes to both responces. The mother board is completely new in a New tower with fully up todate drivers except for the bios. everthing else has been updated. Second Life I have reinstalled 3 times after doing a complete wipe of the game from my system to included searching the Register and deleteing all keys there. Then Reinstalling.

Sounds like you've got a bad set of memory. Memory does that. Return it, get new.

Sorry to double post, but this is several hours later...

To verify that it's truely bad memory, find another game with insane system requirements, ramp the graphics settings to their max, or get a benchmarking program and ramp it's settings to the max. If any of those crash, it's the memory.

Here's a memory diagnostic program. It's free, just download it and follow the instructions.

http://www.memtest86.com/

Also, what combination of RAM do you actually have in there?

I'm going to assume you mean 768 megs of RAM -- a 512 and a 256?

What happens when you run with only one DIMM?

Do you know which chipset your motherboard is using? Recent versions of the nVidia drivers trigger a bug in the AMD chipset silicon which will cause SL to crash in short order. The only sure fix seems to be to roll back your driver to something pre-53.03.

The problem is tied to texture memory usage, so you could also try reducing your texture memory setting to 64 or 32MB, this may reduce or eliminate the problem... we haven't tested for it with >64MB cards.

Update...Ok after fussing and fighting with my system for two days I was playing PS2 with my son and it dawned on me the only thing that I hadnt checked was the new memory chip that I had put in on friday.

I ran a data tool that spits out all the information about every component in my system.

The Crucis Memory that I orginally got was 256 and 128 meg ddr sticks of mem SL run fine with them. Then Friday I went and got Kbyte memory from "Staples" of 512MB PC2700 (note all my mem is PC2700) the only difference in the data between the Curcis Mem and the Kbyte mem was one header for Precharge. Apparently this was an Issue because with that memory in there I would crash repeatedly when I took he 512 out I was fine. I was in world last night for 6 hrs running on 384MB of memory. Laggy but running.

When the 512 Mem was in the system would go unstable when I entered SL while having the diagnostic up.

When I pulled the mem the system was stable and ran sl fine.

Thats where I am at today. I am taking the memory back to Staples and Going to get my money back. I have 512 Crucis Memory on order from my local supplier and pray that solves the problem if and when I install the new memory and the system goes into shock and crashes again I will be back for more support and help.

I do thank all of you for your help so far keep your fingers crossed and pray for me that was the solution.

Sincerely, Shadow Weaver

I R t3h psychic!

Have you tried running SL without the 256 and 128MB modules? It's possible that it's not an individual DIMM, but the combination of the three together.

Catherine I ran another diagnostics program I had gotten online and there is a 70ms timeslice difference between the Kbyte and the Crucis memory so it was incompatible from one to the other. That would also explain why it kept comming up with an Offset error with a page fault location on the crash report. The CPU was trying to execute an instruction with one memory at one speed but when it queried the other the speed difference sent a fault and thus killed SL for me.


I took the memory back to "Staples" and got a refund I have a stick of 512 and 256 on the way from Crucis so that should solve that problem when it gets here. I just have to twiddle my thumbs and live with lag until wednesday or thursday when the other memory arrives.

Oh well win some you loose some.

This was my first time in 14yrs of building and rebuilding systems I have ever had a memory problem and the way it was acting was not like anything I had encountered in the past and all the typical fixes I would normaly do would not work.

Again Thank each of your for your help Wed. or Thurs. will be the tell tale days when I get the other memory here. Meanwhile back at the ranch I will mosey my way through SL till the memory arrives.

Shadow.

one thing shadow, chances are yer new system is running in dual channel memory mode, or at least trying to, this doubles yer memory bandwidth, which is good, but it REALLY requires higher end memory, that you only use TWO sticks of memory, not three, and that they be as closely matched as possible.

Higher end memory suppliers now like corsair have made a bit of a cottage industry out of selecting and selling matching sticks together.

In general, it would be better to get two matched 256's and run 512 than to use a mishmash of 768 or however many megs, be stuck in single channel mode *HALVING* yer memory throughput, and not being stable bcause of the potential for conflicts.

in modern ram more is not always better, but better quality is definately more

A board will only switch into dual-channel mode if:

1) There are exactly two sticks of memory installed
2) The memory sticks are of the same size.
and depending on the board
3) The sticks are rated for the same speed.

Otherwise, it'll stay in single-channel mode. Most likely, the new memory's timings weren't being detected properly, and since it was cheap memory, it couldn't handle the faster timings it was being run at.