@DC_Darkling
Finally got around to playing after doing what you said, still freezing a bit, feels more jittery now, or maybe it was coincidence, will post the log soon.
DC_DarklingJoin Date: 2003-07-10Member: 18068Members, Constellation, Squad Five Blue, Squad Five Silver
If you do not have caching enabled then it can be a bit more jittery, especially on writes. Cache is ment to speed stuff up.
its just that if there is a problem with the cache, you want to test it. hence disabled.
As my ns2 is on my data disk and I always want to be assured it writes my data I have it disabled also. I need new disk for gaming.
So see my suggestions more to find the changing files problem, and not the freeze problem. Although as stated before... if your disk has paging errors, it will slow down a lot and thus cause freeze issues.
What I find odd however is that you have a page error on your harddisk which isnt the OS disk.. Did you set multiple page files?
Windows will always page, regardless of free physical memory.. (it just pages more if you have less free physical memory). But naturally it pages to any page file.
I have an 8gb page file on my system drive (lol recommends 12gb).
EDIT: The problem with catching the file changing issue that throws a consistency failure is there's no way to know when/if it'll come up. So I figure diagnose the freezing problem which ironhorse thinks is the same thing.
EDIT2: Omg, I chose to not bother monitoring tonight as it's late, went fade, got kicked 30s later for ambient.fsb failing consistency check -.-. Well, write caching was not the problem.
EDIT3: Also I was able to rejoin the server and play without verifying...weird. Also maybe this means nothing as though I unchecked the box for write caching, and was never prompted to reboot when hitting ok, I haven't rebooted, do you need to for it to take effect?\
DC_DarklingJoin Date: 2003-07-10Member: 18068Members, Constellation, Squad Five Blue, Squad Five Silver
No, changing caching should be live unless it asks specificly for a reboot. (cant remember completely to be honest, been a while).
Pagefile size is not a problem aslong as you are above 256mb. If you do not run out of physical memory anytime soon, a smaller pagefile will function just fine.
IronHorseDeveloper, QA Manager, Technical Support & contributorJoin Date: 2010-05-08Member: 71669Members, Super Administrators, Forum Admins, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Blue, Subnautica Playtester, Subnautica PT Lead, Pistachionauts
Honestly... Hard drives are So cheap lately.. But even then you don't need to pay for it, just buy one, install it, install ns2 on it, play lots.. If it still happens then you know it's not your hard drive and can taken return this new drive back to the store.
If you don't have that issue.. Well then you already have bought the solution, or can return it still and buy a better one online.
Total time including driving to any nearby crap tech store (Frys, best buy) and install =less than one hour.
I wager you've spent more time than that already diagnosing/pulling your hair out ...
:-P
DC_DarklingJoin Date: 2003-07-10Member: 18068Members, Constellation, Squad Five Blue, Squad Five Silver
on a side note.
im waiting for seagate's desktop SSHD and i hope they work in raid1 as they are technicly not supported.
be released ow shiny hybrid drive...
In more related advice.. I would just install NS2 on a different drive as you seem to have plenty.
Obviously the RAM has pooped (within the last 2 months -.-) but because of the location of the failings, can I just remove the second stick of RAM (for now) and the problem will be gone? I am unable to get more RAM at this time is all.
EDIT: To be more clear, without running the test on each stick individually, can I tell which is the stick that is failing and remove it.
DC_DarklingJoin Date: 2003-07-10Member: 18068Members, Constellation, Squad Five Blue, Squad Five Silver
last I checked you infact can count which ram module it is. Atleast, whats the harm trying?
But yes, do test when you yank it out.
Best way:
* count which module is around the 7th GB.
* yank it out. (if you use modules in pair, yank out the other module until you have a working situation)
* test.
* if no problems exist, move modules so you have a working module in the nonworking modules slot.
* test again to see if the slot itself isnt broken. (unlikely, but why not)
2x4gb so I only have to remove one stick and that's it, it'd just be nice to know which it is without another 9 hour test.
EDIT: Also I'm redoing the memtest only with test #5 as all 3 errors occurred on that test. The test is "Block Move" this IS probably the cause of all my issues right?
EDIT2: 10 passes on just test 5 showed nothing on both sticks...gonna run full tests /wrists.
EDIT3: Is it also possible that it's not either stick it's the slot? If both sticks come back clean after 9 full passes then I'm calling bad slot. If so, are you able to use the other pair of slots without using the first two, or MUST the first two be in use before using the other two?
EDIT4: Doing some research it turns out I've been using the "wrong" slots anyway. Apparently it is recommended to first use slots A2 and B2 (Blue slots) THEN A1 and B1 (Black slots), because you know, that makes sense. So I'm hoping that B1 is shot and I can just use the A2 & B2 slots.
EDIT5: I've put both sticks back in but in the "correct" slots this time, running a test til I wake up (had got to pass 4 on the stick I figured was the one with the failing addresses on it but no dice). IF it doesn't fail after 9 passes like this, I'm either super unlucky or the slot was bad.
DC_DarklingJoin Date: 2003-07-10Member: 18068Members, Constellation, Squad Five Blue, Squad Five Silver
*slaps Ghosthree3*
Yes you use blueblue or blackblack you git.
That way your modules can work in dual channel and if you put them blue/black you will get weird issues. This may very well be the cause of all your weird issues.
So shove em in the blue slots and do a x amount of passes to be sure. 7 atleast.
And yes it is possible a slot is broken, although rare.
@DC_Darkling
I was using blackblack, I'm not that stupid, I'm saying the "correct" way is to use the blueblue slots BEFORE using the blackblack ones (I was using blackblack). Also Got an error at the same location as 2 of the other errors after only 10 minutes of testing with both in the blueblue slots. Would have been nice for that error to show up on just one stick earlier...
IF I get a replacement I will make sure (or I'll just buy 2 more sticks and run 3x4gb with one not in dual). However I'm not sure when I'll be able to get one.
Also, takes 5 minutes to error when I had both in, still hasn't errored for one yet zzzzzz.
Ok, one of the sticks finally errored, removed it, will update as to if the problem is solved.
EDIT: You've got to be kidding me, I don't know about the file changing problem, but I still get freezes all the time when playing.
EDIT2: Also I updated my bios (didn't realise it was already up to date) which reset all my bios settings, no longer able to run it stable at 5.0ghz, no idea what setting I must have changed (or if the chip has degraded, but odd coincidence of time). Couldn't be bothered finding a working group of settings for 4.8 so I'm now at 4.6ghz with mostly auto settings and it seems stable.
Update: Just bumping to say a problem that some thought were related (micro freezing thread) has been resolved (see thread for details), unsure if the issue this thread addresses has been fixed (but it hasn't happened since), if it does happen again I'll bump.
Comments
Finally got around to playing after doing what you said, still freezing a bit, feels more jittery now, or maybe it was coincidence, will post the log soon.
EDIT: Btw @ironhorse thinks this is related forums.unknownworlds.com/discussion/130471/micro-freezing
its just that if there is a problem with the cache, you want to test it. hence disabled.
As my ns2 is on my data disk and I always want to be assured it writes my data I have it disabled also. I need new disk for gaming.
So see my suggestions more to find the changing files problem, and not the freeze problem. Although as stated before... if your disk has paging errors, it will slow down a lot and thus cause freeze issues.
What I find odd however is that you have a page error on your harddisk which isnt the OS disk.. Did you set multiple page files?
Windows will always page, regardless of free physical memory.. (it just pages more if you have less free physical memory). But naturally it pages to any page file.
EDIT: The problem with catching the file changing issue that throws a consistency failure is there's no way to know when/if it'll come up. So I figure diagnose the freezing problem which ironhorse thinks is the same thing.
EDIT2: Omg, I chose to not bother monitoring tonight as it's late, went fade, got kicked 30s later for ambient.fsb failing consistency check -.-. Well, write caching was not the problem.
EDIT3: Also I was able to rejoin the server and play without verifying...weird. Also maybe this means nothing as though I unchecked the box for write caching, and was never prompted to reboot when hitting ok, I haven't rebooted, do you need to for it to take effect?\
EDIT4: Running memtest tonight.
Pagefile size is not a problem aslong as you are above 256mb. If you do not run out of physical memory anytime soon, a smaller pagefile will function just fine.
If you don't have that issue.. Well then you already have bought the solution, or can return it still and buy a better one online.
Total time including driving to any nearby crap tech store (Frys, best buy) and install =less than one hour.
I wager you've spent more time than that already diagnosing/pulling your hair out ...
:-P
im waiting for seagate's desktop SSHD and i hope they work in raid1 as they are technicly not supported.
be released ow shiny hybrid drive...
In more related advice.. I would just install NS2 on a different drive as you seem to have plenty.
Obviously the RAM has pooped (within the last 2 months -.-) but because of the location of the failings, can I just remove the second stick of RAM (for now) and the problem will be gone? I am unable to get more RAM at this time is all.
EDIT: To be more clear, without running the test on each stick individually, can I tell which is the stick that is failing and remove it.
If you got the right your problem should be gone
EDIT: Screw that, too hard.
But yes, do test when you yank it out.
Best way:
* count which module is around the 7th GB.
* yank it out. (if you use modules in pair, yank out the other module until you have a working situation)
* test.
* if no problems exist, move modules so you have a working module in the nonworking modules slot.
* test again to see if the slot itself isnt broken. (unlikely, but why not)
EDIT: Also I'm redoing the memtest only with test #5 as all 3 errors occurred on that test. The test is "Block Move" this IS probably the cause of all my issues right?
EDIT2: 10 passes on just test 5 showed nothing on both sticks...gonna run full tests /wrists.
EDIT3: Is it also possible that it's not either stick it's the slot? If both sticks come back clean after 9 full passes then I'm calling bad slot. If so, are you able to use the other pair of slots without using the first two, or MUST the first two be in use before using the other two?
EDIT4: Doing some research it turns out I've been using the "wrong" slots anyway. Apparently it is recommended to first use slots A2 and B2 (Blue slots) THEN A1 and B1 (Black slots), because you know, that makes sense. So I'm hoping that B1 is shot and I can just use the A2 & B2 slots.
EDIT5: I've put both sticks back in but in the "correct" slots this time, running a test til I wake up (had got to pass 4 on the stick I figured was the one with the failing addresses on it but no dice). IF it doesn't fail after 9 passes like this, I'm either super unlucky or the slot was bad.
Yes you use blueblue or blackblack you git.
That way your modules can work in dual channel and if you put them blue/black you will get weird issues. This may very well be the cause of all your weird issues.
So shove em in the blue slots and do a x amount of passes to be sure. 7 atleast.
And yes it is possible a slot is broken, although rare.
I was using blackblack, I'm not that stupid, I'm saying the "correct" way is to use the blueblue slots BEFORE using the blackblack ones (I was using blackblack). Also Got an error at the same location as 2 of the other errors after only 10 minutes of testing with both in the blueblue slots. Would have been nice for that error to show up on just one stick earlier...
tldr; Yep a RAM stick is def busted.
When you get a replacement be sure it matches the one you have.
Also, takes 5 minutes to error when I had both in, still hasn't errored for one yet zzzzzz.
EDIT: You've got to be kidding me, I don't know about the file changing problem, but I still get freezes all the time when playing.
EDIT2: Also I updated my bios (didn't realise it was already up to date) which reset all my bios settings, no longer able to run it stable at 5.0ghz, no idea what setting I must have changed (or if the chip has degraded, but odd coincidence of time). Couldn't be bothered finding a working group of settings for 4.8 so I'm now at 4.6ghz with mostly auto settings and it seems stable.
EDIT3: RAM put back in, see other thread.