Gigabyte EasyTune6 shows different values for memory slots.

[dmavro]

I was looking at EasyTune6 on my system and noticed discrepancies between all of the memory slots. Is it normal for slot#1 ,#2,and #3 to have different frequency's, Ras# to Cas#'s , Ras# precharge, and Tras #'s all under the Timings Table. I also noticed that slot#1 and #3 show max bandwidth as PC3-10700H(667 mhz) and slot #2 shows PC3-17300H(1083 MHZ) and the part number's for each slot are also different. I purchased a 6 gb kit from corsair and assumed all part numbers should be the same. I have not overclocked manually, but i did set performance enhance to Extreme in the Bios. I just want to know if this is normal or if i have some issue somewhere in my bios or even a problem with my actual memory. Thanx in advance.

 

[dmavro]

I set up those settings earlier even though ive only checked one memory stick so far with memtest. I just wanted to get myself familiar with the setup process. The windows System screen is now showing under....

Processor: Intel Core i7 CPU @ 2.80Ghz 3.36Ghz.

Im assuming its showing me the default speed and the Overclocked speed to the right of it.

Also, im seeing next too....

Installed Memory (RAM): 6.00GB (2.00GB usable)

Is something wrong there?

 

[bilbat]

Installed Memory (RAM): 6.00GB (2.00GB usable)

Is something wrong there?

Ummm - that's not good... Here's the first thing I'd try (not likely, but the easiest to eliminate):

Open msconfig (just type it into your searchbar, and hit enter)...

Click on the 'Boot' tab, and the 'Advanced Options' button...

On the upper right, select the "Maximum memory" checkbox, and scroll the value beneath to what it should be...

Click 'OK' to close the page, click 'Apply' on the main page, followed by 'OK' again - then take its suggestion to reboot your system - see if the problem's fixed...

If not, read the i3/i5/i7 'Missing' Memory section, about three-quaters of the way down in the 'sticky'...

 

[dmavro]

If not, read the i3/i5/i7 'Missing' Memory section, about three-quaters of the way down in the 'sticky'...

This doesnt seem to exist anymore.

 

[dmavro]

I dont know how but i cant seem to get settings i had running yest to work with or without the memory problem. Now every time i start up with those settings windows boots with settings that are very close to stock settings and all 6 gigs of ram. I cannot get those higher CPU speeds now. I did a load optimized yest to run memtest again last night. Today when i loaded your settings that are stored i keep halting on mobo code c1, which i believe is 'Detect memory -Auto-detection of DRAM size, type and ECC'

 

[bilbat]

They just changed the URL on me; sorry...

 

[dmavro]

I figured it out. I can boot into windows with your 'stock settings' and your 'gentle overclock' settings, only if i leave "virtualization" enabled in "Advanced CPU Features". But when i do that 4098mb of ram is Hardware Reserved by windows. If i shut off virtualization then mobo halts on code c1 as i mentioned earlier.

Im going to check out that post now. i appreciate it.

 

[bilbat]

Jeez - that's really strange! I'll have to fiddle around a bit here with toggling 'virtual', and explore a bit with a debugger to see what appears to be going on... I think I've got the VM SDK sitting around somewhre too - maybe it's got a clue for us?

Where'bouts are you 'seeing' this 'Hardware Reserved' thing?

 

[dmavro]

in windows resource monitor under the memory tab

its also says this about.... Hardware Reserved: Memory that is reserved for use by the bios and some drivers for other peripherals

 

[bilbat]

I'm hunting - seems to be a pretty common problem, and likely to be memory compatibility issues. I still think the most expedient course is, while I hunt around for 'commonalities' in the problems, you should take a crack at the 'Missimg Memory' procedure in the 'sticky'...

I always hate to be the 'bearer of bad tidings', and this seems to be one of the 'hardest to bear'! But, I can't tell you how many times, here, I've gone back and forth with someone, four, five, six posts, who is just resistant to the idea of 'unplugging' that ^%$# CPU - and they come back and, sheepishly, report "oops - a bent pin!" (or two, or, sometimes, a row!) My guess, it's the problem, nineteen out of twenty times...

 

[dmavro]

I ran memtest on all 3 memory sticks and no errors at all. I did over 45 passes on all of them. I noticed on the memtest screen near the middle of the page it says..... settings: 539 MHz(DDR3-1079)/CAS: 8-8-8-20/ Single channel......is single channel correct. Im only asking because the memory is triple channel isnt it?

 

[dmavro]

I'm hunting - seems to be a pretty common problem, and likely to be memory compatibility issues. I still think the most expedient course is, while I hunt around for 'commonalities' in the problems, you should take a crack at the 'Missimg Memory' procedure in the 'sticky'...

I always hate to be the 'bearer of bad tidings', and this seems to be one of the 'hardest to bear'! But, I can't tell you how many times, here, I've gone back and forth with someone, four, five, six posts, who is just resistant to the idea of 'unplugging' that ^%$# CPU - and they come back and, sheepishly, report "oops - a bent pin!" (or two, or, sometimes, a row!) My guess, it's the problem, nineteen out of twenty times...

Wouldnt all the memory not show up even when im using standard bios settings then? i always see 6 gb under normal conditions. And even when i only have 2 gb usable, the system does see 6 gb its just being dedicated to something else by the bios. Ill give that a try next anyway.

 

[bilbat]

What I don't know is how one problem can be responsible for so many (really odd) symptoms - one would think (especially after taking a look at the memory interface ball-outs) that in at least two-thirds of these situations, the machine just wouldn't start in the first place... What I do know: it's the first thing to look at when 'unuseable' memory appears!

Think of it as being like going to a doctor - you don't feel good, and the lower right side of your abdomen hurts. He takes your temperature, and it's 101°F; he lays you on an examining table, presses the flat of his hand on the left side of your abdomen, and as he releases it, you wince. He presses lightly down on your right knee, and asks you to try to lift your right leg - you yelp! Pretty much the next thing is he has a scalpel in his hand, and is fishing for your appendix...

Now you might have a peculiar case of ulcerative colitis - or - you may have a one-in-ten-million genetic disorder that leads to fistulas in the small intestine - or - you could have picked up a rare intestinal parasite on that cruise to Barbados that you forgot to mention to him - but he's gonna go for that appendix, because the last eighteen guys he cut open, who 'presented' with the same symptoms - he cut through the abdominal fascia, fished around for a moment, and there was a large, red-marbled-with-white (or even worse - green!) abcessed appendix! He's also got little choice as he doesn't have 'all the time in the world' - even with today's medical technology, if that baby ruptures, the resultant peritonitis can still kill you!

I'd really prefer that, before we start chasing our tails through a bunch of diagnostics, and a slew of 'attempted fixes', that we verify it's not what it always is: bent pin(s)! The main trouble is: no matter what we try to fix it - if the ounderlying problem is actually a pin, all our 'fixes' will do is repeatedly 'shift' the symptom to something else...

 

[dmavro]

I checked mobo yest and didnt see any bent pins . I printed out the intel article about bent pins and i am going to check again today just to be sure.

 

[dmavro]

What is a good utility to run during the day to track what my system is doing?

 

[bilbat]

I'll hunt around - I just connect another machine, and run it in debug... Definitely - decent magnifying glass and flashlight to do the 'pin check' - from what I've heard, the defects don't have to be gross, to have an effect! ...Long as you've got 'er out, may as well be thorough...

 

[dmavro]

Ive checked pins finally and there are none bent. Is there any kind of utility i can run during the day to try and bring some light to the issue? Also, what did u mean by connecting another machine and running it in debug?

 

[bilbat]

Programming environments allow you to set up a debug port (usually, an old-fashioned serial port) so you can have one system capture messages from the other to give you clues about "what the hell is going ON here?!?" With windows jsut running, the first place to start is by examining log files... To get all the tools possible in one place do this:

Create a new folder on your destop

Rename the folder to
Tools.{ED7BA470-8E54-465E-825C-99712043E01C}

Double-clicking it thereafter should give you a laundry list of every possible win seven tool available...

First stop should be in the first group, 'Action Center', double-click 'View all problem reports', see what she tells 'ya...

Next, go to the next group, 'Administrative Tools', and hit 'View event logs'. There are a bunch of 'em, and you want to scan at least the following:
under 'Windows logs', scan at least 'Application', and 'System';
under 'Applications and services logs, scan 'ACEEventLog' and 'HardwareEvents' (which should, hopefully, be empty!)...

What you are scanning these for is items that are flagged in red as 'errors', or in yellow as 'alerts'; sometimes these will contain a sesible message, sometimes they'll need deciphering; especially important are ones that come up in the list repeatedly...

If you turn out to have a bunch, I'll look around here - somewhere I've got a log parser that I think came from MS, that might make the job a bit easier...

 

[dmavro]

Nothing worth mentioning in the 'Action Center'. But in event logs I have quite a few errors and a ton of warnings under 'Application'. i filtered and in the last 7 days ive had 107 errors and 1792 warnings. Under 'system' i have 51 errors in last 7 days and 4 warnings. Ive had 7 critical warnings since i built the computer in march. and they were all......
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." source was kernel-power and event id 41.

I didnt even know about these. i must of not been at the computer for any of those. Also, I dont have 'ACEEventLog' , and 'HardwareEvents' was empty

 

[dmavro]

I took a week off work and got a chance to relax and by the second day i realized i didnt want to troubleshoot this anymore. I also had a friend take a look at the mobo pins and he thought that a few were bent. So to be safe i went to MicroCenter and used my protection plan. I actually got upgraded in the process. I went from a Rev 1.0 mobo to a Rev2.0 mobo and now 2 other small issues i was having are resolved, but I tried all three of your OC settings and cant get any of them to work. I also tried each variation and tried all the different Load-Line Calibration settings. I even tried using higher CPU Vcore settings than u recommended. No matter what settings i changed, I still couldnt boot into windows. I am so baffled?? Could it just be incompatibility with my RAM? Is there anywhere online i can find the formulas used to set all of the bios settings when overclocking a system?.....Maybe it would help if i had a method to my madness??