What's your memory assessment speed?

[Eblim]

x2 3GB DDR3 @ 1067 MHz. Shouldn't it be a little faster than 6GB a second?

 

[Britton30]

Has anyone seen this on winsat mem?
Specs for this system in the CPU-Z snips. this is my secondary system and IBT won't run, it stops with an error saying to use admin privileges, which I did to no avail.

 

[Hopalong X]

Forget what I posted Gary.. That is why I deleted it.

Googled it and I found a couple of similar issues but no explanations.

 

[Britton30]

Thanks Mike, I read it but came more confused. I've fooled with the HT and NB frequencies and it still shows the RDTSC crap and IBT still won't run. Just odd.

 

[A Guy]

I found some geek

The RDTSC instruction has, until recently, been an excellent high-resolution, low-overhead way of getting CPU timing information. With the advent of multi-core/hyperthreaded CPUs, systems with multiple CPUs, and "hibernating" operating systems, RDTSC often no longer provides reliable results. The issue has two components: rate of tick and whether all cores (processors) have identical values in their time-keeping registers. There is no longer any promise that the timestamp counters of multiple CPUs on a single motherboard will be synchronized. So, you can no longer get reliable timestamp values unless you lock your program to using a single CPU. Even then, the CPU speed may change due to power-saving measures taken by the OS or BIOS, or the system may be hibernated and later resumed (resetting the time stamp counter).

I might be understanding this wrong but... Basically both RDTSC and QPC are used to time code in time-sensitive programs. However, RDTSC might be inaccurate in above described situations. I also might be wrong about this but I believe QPC has something to do with the HPET high precision event timer. Which is a more accurate timer.

So this might explain why RDTSC and QPC has a delta that is too high. And if all of what I said above is true, then this error is benign.

Googling does find people with that error, but usually not accompanied by any performance issues. A Guy

 

[Hopalong X]

Thanks Bill.

Now I'm only 99.9999% confused.

 

[Britton30]

I found some geek
Googling does find people with that error, but usually not accompanied by any performance issues. A Guy

Thanks Bill, I did read that too and it's true I haven't noted any lower performance.
I think Mike cursed me a few months ago when he commented my machine is "quirky"

Thanks Bill.

Now I'm only 99.9999% confused.

I'll go with 100% for myself.

 

[Hopalong X]

Thanks Bill, I did read that too and it's true I haven't noted any lower performance.
I think Mike cursed me a few months ago when he commented my machine is "quirky"

Maybe it is just that the operator is quackers.

 

[Dave76]

x2 3GB DDR3 @ 1067 MHz. Shouldn't it be a little faster than 6GB a second?

Your system should have DDR2 RAM, download CPUZ and check the Memory tab.

This score is normal for DDR2 RAM.

You can also check the CPUZ SPD tab for each motherboard slot to see what RAM cards are installed. There are no 3GB RAM cards, Gateway has either put 4GB and 2GB or 3X2GB cards.
These are not optimal but do work.

 

[Dave76]

Has anyone seen this on winsat mem?
Specs for this system in the CPU-Z snips. this is my secondary system and IBT won't run, it stops with an error saying to use admin privileges, which I did to no avail.
View attachment 218151

Interesting attachment.

Will it run Prime95?

Does the RAM pass memtest86+?

Your NB frequency looks good.

Have you bumped the IMC voltage?
Might need to bump the DRAM voltage a little also.

Just a thought, you might try loosening the RAM timings and set the command Rate to 2T, see if it passes then.

 

[Solarstarshines]

Not bad for 8GB's of DDR2 -800

The back up Rig is just humming along

 

[smarteyeball]

x2 3GB DDR3 @ 1067 MHz. Shouldn't it be a little faster than 6GB a second?



This score is normal for DDR2 RAM.

Yep. 6-8GB's is normal for stock clocked 775 socket systems. It's pretty much on par with what it should be.

 

[Britton30]

Has anyone seen this on winsat mem?
Specs for this system in the CPU-Z snips. this is my secondary system and IBT won't run, it stops with an error saying to use admin privileges, which I did to no avail.
View attachment 218151

Interesting attachment.

Will it run Prime95? It ran for 5+ hours, but one core had error and quit.

Does the RAM pass memtest86+? Yes, passed 7 passes

Your NB frequency looks good.

Have you bumped the IMC voltage? Not sure, it has a VDDBD or some such, no CPU NB.
Might need to bump the DRAM voltage a little also. Did that, 1.525.

Just a thought, you might try loosening the RAM timings and set the command Rate to 2T, see if it passes then. It won't set to 2T, 1T got set automatically. Timings loosened to 9-10-10-26, winsat shows normally now.

However, now IBT and Prime both will cause BSOD with 0X07e or 0X0124 - OR programs will quit responding and Windows is checking for a solution.
Most recent I tried Prime and the one core immediately quit then a BSOD.

 

[Hopalong X]

Gary

Of course this is if you run out of other ideas.

A stick of RAM is bad??? I'm no expert but I would pull them all and then try them one at a time.
You know the routine I'm sure.

If all the RAM is good in one slot then a RAM slot could have a problem. I think that would be rare though.

------------------------------------------------------------------------------------------------------------

I still say it is the quirky quacky operator. :devil:

 

[Hopalong X]

Download this> Tweakers.fr


Under the main CPU listing Timings is on the right.
Default shows both A and B.
Drop the curtain and Select A and B seperately. Make sure the seperate A and B timing lists match.
If there is a mismatch in timings you can match them here but proceed with caution if you do so.


When you open Tweaker there will be a tab at the bottom Sub Time click it.
Proceed with caution and your own peril if you change settings in Sub Time. You can set the timings and everything from here but be careful. I have never used this software for this but many OC'ers do.
I only use it to check settings never to alter them.

 

[Britton30]

Yessir, I had done all the RAM tests before putting the thing in a case. I did find some of the BIOS settings had reverted to something other than I set them to, maybe due to not being on all the time.
I got the Tweaker and will look at it later. Just what I need, software to automatically foul me up.

I'm quacky, but the rigs are ok, or will be. Going to Wal*Mart for a Pc adjuster tool.

 

[Hopalong X]

Yessir, I had done all the RAM tests before putting the thing in a case. I did find some of the BIOS settings had reverted to something other than I set them to, maybe due to not being on all the time.
I got the Tweaker and will look at it later. Just what I need, software to automatically foul me up.

I'm quacky, but the rigs are ok, or will be. Going to Wal*Mart for a Pc adjuster tool.
View attachment 218229

Get the 16 pounder.
--------------------------------------------------------------------------

I would try setting everything back to stock settings if you know what they were. Make sure all the channels have identical timing settings.
At least that gives you a starting point that should work.

Reset to default. Pulling CMOS battery does that if memory serves on some boards.
My ASUS board has a reset button I think.
(If all else fails) Read the manual.

 

[Dave76]

Has anyone seen this on winsat mem?
Specs for this system in the CPU-Z snips. this is my secondary system and IBT won't run, it stops with an error saying to use admin privileges, which I did to no avail.
View attachment 218151

Interesting attachment.

Will it run Prime95? It ran for 5+ hours, but one core had error and quit.

Does the RAM pass memtest86+? Yes, passed 7 passes

Your NB frequency looks good.

Have you bumped the IMC voltage? Not sure, it has a VDDBD or some such, no CPU NB.
Might need to bump the DRAM voltage a little also. Did that, 1.525.

Just a thought, you might try loosening the RAM timings and set the command Rate to 2T, see if it passes then. It won't set to 2T, 1T got set automatically. Timings loosened to 9-10-10-26, winsat shows normally now.

However, now IBT and Prime both will cause BSOD with 0X07e or 0X0124 - OR programs will quit responding and Windows is checking for a solution.
Most recent I tried Prime and the one core immediately quit then a BSOD.

In your UEFI BIOS the IMC is VCCIO Voltage (referred to as VVT below).
The recommended max voltage difference between Vcore and IMC is 0.50v, to prevent CPU damage according to Intel.

Default VCCIO voltage should be ~1.06v, I would bump it to 1.120 - 1.150v if you have 16GB RAM (your system specs) or 1.100 - 1.140v if running 8GB RAM (previous CPUZ memory tab).

The OverClockers BSOD code list

0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is on i7 45nm, usually means too little VVT/QPI for the speed of Uncore on i7 32nm SB, usually means too little vCore.

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

 

[Britton30]

Dave, this is my back up system, the specs are in the CPU-Z snips, no UEFI there, old American Megatrends blue and white BIOS. I will try the chkdsk and sfc though.

 

[Dave76]

What brand of mobo?
If it's Asus it should have the same name.