• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

x64... Problems on top of problems.. What now?

James Bond

James Bond

Diamond Member
I would say that overall, with x64, I have had a geniuinely rough time.

Using stable chipset drivers is a major issue for me, along with constant (or near constant) lock ups or slow usage.

I'm nearing wits end.

My main problem is that I'm not convinced that my hardware is perfect. After running memtest for the past few nights, and encountering tons of errors, I'm not sure if its yet appropriate for me to base all of my anger towards x64.

After having iTunes lock up a few times on me the other day (before this, iTunes was one of my most stable programs), I got pissed and uninstalled just about everything that I didn't 'need', including iTunes itself. I unstalled my software burning apps, my CD emulator, and everything else I could do without... hoping it would improve some performance.

Now, being the next day, I go to re-install iTunes. But oh! I encounter a problem at the very end of installation (this is after its done copying files, even after it 'registers' the program... it seems like everything is finished when i crash). So the installer closes, I attempt to run iTunes, and get an error every single time.

I'm convinced this cannot be a memory problem.

I have installed and reinstalled my chipset drivers over and over, updated my BIOS, reinstalled video drivers, everything.

I don't know what to do.

Is it possible to go back to XP Pro without reformatting?

Any ideas? I would be thankful for much of anything right now.

Sincerely,
Tyler Lucas
 
Errors in MemTest should rule out driver issues. There is almost certainly an issue with your RAM or your motherboard.
 
Definately try Memtest to rule out memory.

Another problem could be the chipset drivers for your DFI Lanparty NF3 250GB. For some wonderful reason, nVidia has left us nForce3 users with Beta drivers instead of the WHQL drivers that nForce4 users enjoy.

The nVidia site indicates that:

Both the operating system and these drivers are still in BETA. Known issues include the following:

* Audio pops and clicks may occur while playing certain games
* Occasional hangs may occur with these drivers.
Click to expand...

Considering that XP-64 is no longer Beta, it would be nice if nVidia would get off their collective rear ends and provide WHQL for both AMD 64 bit platforms :roll: .
 
Originally posted by: Tizyler
"Occasional Hangs"... Exactly what I'm trying to fix.

When the hell will there be stable drivers?
Click to expand...

Good question, sorry I don't have an answer.

nVidia (and other companies) seem to be leap frogging XP-64, and are now writing drivers for Vista (32 & 64). My guess is that nVidia doesn't feel there is a market for nforce3 and XP-64.

Have you tried the nForce4 drivers? I know some 32 bit users are using the nForce4 driver set with their nForce3 boards, with mixed success. I have not idea what the difference is between the drivers (ie. on a code/hardware control level) or if they will work at all with nforce3.

Were you able to rule out memory errors as suggested?
 
My main problem is that I'm not convinced that my hardware is perfect. After running memtest for the past few nights, and encountering tons of errors, I'm not sure if its yet appropriate for me to base all of my anger towards x64.
Click to expand...


A machine with healthy memory will be able to run memtest for WEEKS without a _single_ error.

A big memory place did a study that figured that on average a machine with good ram will experiance a memory error maybe once per year. Caused by a random solar ray or something silly like that.

You absolutely have to get your memory under control before you can expect to even have a remotely stable machine.

Changing drivers to fix a stability issue when your getting memory errors makes about as much sense as changing the drivers in a automobile in order to fix multiple flat tires. It's just never going to work.

Use conservitive timing for your ram, move the ram around. On 754-style AMD64 machines 400mhz ram may only be used in certain slots were otherwise you can only use 333mhz in all of them. Wiggle it and make sure it's seated. Make sure there is no dust.

Underclock your ram.

IF you can't get rid of the memory errors that way, figure out which module is bad and replace it(them). Only be sure buy ram that's been tested by the manufacture with your motherboard.

When booted up into memtest86:

When you experiance problems were only a small amount of ram addressess experiance problem, or a specific range of addresses cause problems then it's bad ram. Find a replace the bad ram module.

When you experiance the same as above, but only have problems in those problem areas once in a blue moon, like it passes the test a dozen times, but fails once. It's bad ram, replace the bad ram module.

When you experiance massive amounts of errors across a seemlingly random address range, then it's a bad motherboard, bad ram/cpu/motherboard combination, overclocking or just running to fast for said combination/conditions. The solution is to underclock ram till it works, move ram around till it works, try a different motherboard till it works, or try different brand memory till it works. Most motherboard makers have a list of tested and certified ram types that they know will work.
 
Drag thank you so much for all of your help, that really helps me out.

Ill underclock my RAM tonight and begin testing one stick at a time. I remember seeing the same addresses over and over, like 000000000010 each time.. So that makes me happy (that it most likely isn't my M/B). Ill tell you how it goes
 
UPDATE:
Everything was completely stock. I then lowered my RAM Mhz to the lowest setting (100?). I took out stick 2.

I ran memtest for a night with 1 Stick in DIMM1. Pass
I ran memtest for 5 hours with 1 Stick in DIMM2. Pass
I ran memtest for 5 hours with Stick 2 in DIMM1. Pass

I remember seeing the errors I was getting and they were pretty much all on the same in the same range of addresses.. So I was convinced it was the RAM. Was it generating thousands of errors because it was at stock speeds? How is this possible? I'll run it again tonight with both sticks in at once, underclocked, again.

Any more ideas?
 
There is definately something wrong going on. I am leaning towards the motherboard right now, but it's hard to say.

If you can get ahold of another board that can handle that ram type/speed then try it out on that board at correct full speed and see if you get any errors with any of those ram modules.

If you don't have problems with those ram modules on a different board, then the suspect is either the motherboard or the cpu itself, since the memory controller is built into the cpu on those AMD64 setups.

At this point it may end up being expensive or at least very time consuming though.. If your RMA the board and it turns out the be the CPU or the RAM then you'd be sunk.

Maybe there is a store or a something like that nearbye were you can pay them 50 bucks or so to help you figure out which componate is the problem. They'll have different systems to try out the parts in and tools to help figure out voltages and such.

Also be sure to go online and see if you can find forums or whatnot that are setup by the motherboard manufacturer to try to figure out common problems with the motherboard that your using. Could be a common problem and if you find other people with similar issues with similar hardware then it can make things so much easier.
 
Originally posted by: Tizyler
UPDATE:
Everything was completely stock. I then lowered my RAM Mhz to the lowest setting (100?). I took out stick 2.

I ran memtest for a night with 1 Stick in DIMM1. Pass
I ran memtest for 5 hours with 1 Stick in DIMM2. Pass
I ran memtest for 5 hours with Stick 2 in DIMM1. Pass

I remember seeing the errors I was getting and they were pretty much all on the same in the same range of addresses.. So I was convinced it was the RAM. Was it generating thousands of errors because it was at stock speeds? How is this possible? I'll run it again tonight with both sticks in at once, underclocked, again.

Any more ideas?
Click to expand...


Ram errors are a pain to find.

Run the ram at the stock clock (rated spec & voltage) and run memtest86+ (use the new version 1.65??). Test the ram:

1) One stick at a time
2) Both sticks in, in single channel mode
3) Both sticks in, in dual channel mode

I had some OCZ premier (2x512) that ran perfect in single sticks, but would not work together (single or dual). Apparently, the Ram sticks didn't get along. I was able to replicate the errors in another system, so I was able to RMA the ram.

If you can't find RAM errors, it could be the nForce3 drivers or your board. Have you tried the DFI-Street forum? That is an awesome resource for DFI users.
 
Thanks to both of you.
Yeah, I have been at DFI-Street a bunch. My main problem is that I ran into the fact that there are still no good drivers for NF3 on x64... They are Beta drivers.

I was convinced my problem was the RAM, then I found out that the drivers were still Beta and could have "occasional hangs" (which was my main problem. At that point I was convinced it was my drivers. Then I ran memtest and got tons of errors and was convinced it was my ram. Now I'm not getting any errors when It's stock/underclocked. Now I'm clueless. I guess I'll start testing the RAM at stock speeds again in single and dual channel and take it from there.

Any more opinions?
 
So your memory failed at stock (200MHz) speeds? In your sig you have RAM at 220MHz so I assume that failed too?
 
First of all, eliminate any overclocking you have going on.

Second, run the RAM at stock speeds but up your RAM voltage to 2.7 V.

Run MemTest overnight and see if you get any errors.
 
You don't have to use Beta drivers for NF3. There are WHQL drivers for NF4 that work perfectly well w/ NF3 boards.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top