Memory not fully detected

balth_dire said:
In the last week it has done it about 5-6 times. On one occasion I left it running overnight, only to return the next morning to discover that very same "checksum bad" message staring me in the face :rolleyes: . What the hell's with that??

checksum bad or (CMOS Checksum bad) usually appears when youve updated a bios and the cmos is storing the settings of ure old bios and trying to use them on ure new bios therefore it usually promts you to load defaults
 
Lan said:
checksum bad or (CMOS Checksum bad) usually appears when youve updated a bios and the cmos is storing the settings of ure old bios and trying to use them on ure new bios therefore it usually promts you to load defaults


Indeed, which is why we've both been puzzled to see the message immediately following a system crash rather than a BIOS update, or for that matter, anything remotely connected with the BIOS :confused:
 
Last edited:
balth_dire said:
Indeed, which is why we've both been puzzled to see the message immediately following a system crash rather then a BIOS update, or for that matter, anything remotely connected with the BIOS :confused:

perhaps the battery need replacing
 
balth_dire said:
Interesting thought, but I really think it far too strange a coincidence that we both have flat CMOS batteries of brand new motherboards ;) .
yer i see ure point, btw u like the way i flash stuff???

EDIT: what mobo sorry??, or bad batch of batteries lol (i seriously doubt tht)
 
Yes, I had a feeling it was something along those lines. I probably would have used my win98 CD to boot into DOS and then burned the BIOS file to a seperate CDR.

Your way is more practical though, I'll remember it.
 
Last edited:
Lan said:
yer i see ure point, btw u like the way i flash stuff???

EDIT: what mobo sorry??, or bad batch of batteries lol (i seriously doubt tht)


:D

Have a look back at some of the posts in this thread and note how many things we've tried, it might save you some thinking time.

We both have the Asus p5n32-sli SE.
 
balth_dire said:
:D

Have a look back at some of the posts in this thread and note how many things we've tried, it might save you some thinking time.

We both have the Asus p5n32-sli SE.

i did look thru the posts :D
 
balth_dire said:
Yes, I had a feeling it was something along those lines. I probably would have used my win98 CD to boot into DOS and then burned the BIOS file to a seperate CDR.

Your way is more practical though, I'll remember it.

o btw the best way to do this is using nero 7 burning rom (not startsmart) beacuse you can set floppy emulation in tht and wen you boot from the disc it loads DR-DOS which is what nero provides already
 
Yea thanks for the help Lan :) that's the way I flashed BIOS last two times. Works nicely.

Also, I doubt it is the batteries Lan. Apart from the fact it happens after a crash, not after a BIOS update, it doesn't even happy after every crash. Just occasionally.

Thanks for the thing about thread optimization balth. I noticed there were a couple of options I had that wern't there in those images.I saw this one, but thought it ebst to leave it on auto. I'l give it a try with it on and off now.

I'm gonna start up rise of legends now. Considering how often it locks up/crashes, it might actually be the easiest way to test if somethings working or not, lol.
 
Dual GX7950 = 2Gb
2Gb ram = total of 4gb


Your past Windows 32 bit 4Gb limit.....

So either get Vista, XP-64 or loose one of the gfx cards, beats me why you have two anyway, what res do you game at?

CR.
 
Sudden said:
I'm gonna start up rise of legends now. Considering how often it locks up/crashes, it might actually be the easiest way to test if somethings working or not, lol.


Yes, assuming that all these crashes are related to the same thing. :D

I may try and "acquire" a copy myself...this 3dmark method doesn't need me to be infront of the system the whole time, but it still takes ages to yeild results.
 
Last edited:
Concorde Rules said:
Dual GX7950 = 2Gb
2Gb ram = total of 4gb


Your past Windows 32 bit 4Gb limit.....

So either get Vista, XP-64 or loose one of the gfx cards, beats me why you have two anyway, what res do you game at?

CR.


Thanks, we've dealt with this issue now, :) BIOS 305 resolves it, the full 2gigs are correctly detected.

I also have a dual boot setup with windows xp x64.

At the moment I run at 1600x1200, usually with high levels of AA and AF, hoping to grab one of those Dells before too long.
 
Small update - not sure if it's completely related, since game may not have had enough time :p but after increasing the voltage and changing those gfx settings, game still crashed, but there were no artifacts at all. Not even a hint. Not sure if it was cause there wasn't enough time or whatnot, but yea.

I'm jsut gonna turn the thread optimization off and try it now, just thought i'd post that first.

Concorde, as balth_dire pointed out, he's using wind x64, but having the exact same problems as me. And others have had these problems as well.

And i'm gaming at 1920x1200. everything full.
 
balth_dire said:
Thanks, we've dealt with this issue now, :) BIOS 305 resolves it, the full 2gigs are correctly detected.

I also have a dual boot setup with windows xp x64.

At the moment I run at 1600x1200, usually with high levels of AA and AF, hoping to grab one of those Dells before too long.


Meh, my X1900XT-X does full AA and AF at 1600x1200 but fair enough :D Im sure it will do more when I get over the overclock limit.

CR. :)
 
Ok, just tried it. Did crash again unfortunately, but it lasted a suprsingly long time! I was considering quitting to say it worked :p Good thing I didn't.

Artifacts started appearing after some time, and got progressivly worse (all flashes though. not the type taht stay on screen until you can't see anything)
but game lasted a suprisingly long time. I'm just gonna try it again, to check if it was a fluke or something. But yea, if it wasn't and this drastically helps, then at least it's a little bit of headway!

yea, forget taht. was a fluke. just ran it again. Lock up after a few min :(
That first time gave me a ray of hope :p
Thanks balth :)
 
Last edited:
Sudden said:
Ok, just tried it. Did crash again unfortunately, but it lasted a suprsingly long time! I was considering quitting to say it worked :p Good thing I didn't.

Artifacts started appearing after some time, and got progressivly worse (all flashes though. not the type taht stay on screen until you can't see anything)
but game lasted a suprisingly long time. I'm just gonna try it again, to check if it was a fluke or something. But yea, if it wasn't and this drastically helps, then at least it's a little bit of headway!

Thanks balth :)


hmmm, the artifacts do confuse me somewhat, do you only notice these in this particular game? Also, are you still using the 91.47 drivers? I'm on 92.91 at the moment.

I set mine off on another prime/3dmark06 combo earlier today - after altering the settings and turning off "threaded optimization" - things still going strong, and I believe prime is running tests in groups of 8 as well, so almost certainly an improvement this end too.
 
Last edited:
balth_dire said:
hmmm, the artifacts do confuse me somewhat, do you only notice these in this particular game?

I set mine off on another prime/3dmark06 combo earlier today - after altering the settings and turning off "threaded optimization" - things still going strong, and I believe prime is running tests in groups of 8 as well, so almost certainly an improvement this end too.

yea, it's wierd. This is the only one. Hitman, aoe3, cod2, oblivion, ut2k4, all run perfectly. This game is the only one which crashes so often and shows artifacts.

edit - oh those drivers are out? I had no idea. I'm on 91.48 right now. I'l update right away.
 
Sudden said:
yea, it's wierd. This is the only one. Hitman, aoe3, cod2, oblivion, ut2k4, all run perfectly. This game is the only one which crashes so often and shows artifacts.

edit - oh those drivers are out? I had no idea. I'm on 91.48 right now. I'l update right away.


:)

Very strange, perhaps the artifacts are the symptom of a bug or shortcoming in that specific game, maybe this isn't directly related to the freezing.


EDIT - ok, I just exited 3dmark, it had been running for over 11 hours....BUT, prime95 had reverted to running its tests in groups of two again, thus, I've not really determined more than we already know.

I'd like to send you a copy of the log file for Prime so you can see exactly what I mean, I'm sure there's a clue somewhere.
 
Last edited:
I'm not sure i'l understand the Prime95 log file, but i'l definatelly take a look at it.

Yea, i'm pretty certain the artifacts have nothing to do with the freezing. Just something that's there as well. As you said, could possibly be specific to this game.
 
Last edited:
Back
Top Bottom