Leave Mother Alone The T6540 is designed around the NVIDIA GF 6150 mobo which is dual-channel capable and expandable to 2GB. While it is possible to do so, one cause of instability is mixing modules, especially PC5300 modules. My first question: did you install a MATCHED pair of modules? Secondly, why suspect mother if the machine, out of the box, is capable of expansion? Monk
I bought a matching pair which is also dual channel capable. I dont know what happened but everything did match on paper. My friend and i did all kinds of tests from messing with video memory(for some reason we thought of this and please dont ask why) and even reset cmos. none of it worked but we tried putting only one of those 2 in there and it worked. Previously, we also tried a matching pair of pc-4200 rams as well that also was supposed to match specifications but, it also caused freezings.
I can see what you're coming from but, im sure its not drivers as it is the same on linux with these freeze ups. There were no overclocks as he even reset the cmos. we had tried the pc-4200 with 1 gb before and it did not work. I don't think i would be able to shell out more money for the ram just to try a different brand that might work or might not unless someone would love to send them to me. but, heres something odd that i noticed, if this were true, then how come the computer would work with one ram and not two? thats what is puzzling me. i dont know if there is something wrong with the hardware or not but, the bios thing was the last thing i had came up with. what makes this whole situation worst is, the manufacturer of this mobo has erased all traces of old bios and records of them so there is no way to tell if there was a fix or even if this problem ever occured with other people.
Gateway does have the computer model but, no bios. The computer starts up into the os just fine but while you're using it for a while, it just freezes up.
Event Viewer In my experience, the EV ALWAYS reports system failures - which may or may not be understandable depending on one's expertise or the severity of the issue but it's a start. Monk
Sorry EV (I abbreviated it since I used it in the tread)=Event Viewer: via Control Panel, Administrative Tools, Event Viewer. You will see two levels of problems: X in red shield: usually indicates a failure; ! in yellow shield: usually indicates potential problems which may or may not have been overcome during boot or executable. Right-click anywhere on the line you see an error or warning shield then click on Properties. A dialog opens with the log of the event. Of particular interest, select Application and System events from the left-hand pane. Read the help file (or Google; TechNet also has a good article on the EV) for good info on interpretation and use of EV. There is a lot of very good data here. The trick is to understand and track down the specifics that you experience at any given time based on the info given. In a case like yours, when you say my RAM don't work, without further details about machine, drivers, prior flash attempts, applied "patches" or tweaks," etc., etc., offering suggestions is hit and miss. OK, try this. No? OK did you do that? You get the point, and in the end the post eventually contains 53 posts that solved nothing. As I have said elsewhere in these forums, I am old and slow, and the more diagnostic data I have the quicker I can focus my thoughts, hopefully, toward a solution - for you (instead of shutting my computer off and taking my nap - for me ). Monk