I remember.. xxxx* OCed also his mobo.. but he forgot to lock the PCIe @ 100 MHz. He was @ 105 MHz.
And now his GTX295 RAM is damaged.
Don't know - if because of this.

I think Sutaru is referring to my GTX295 which is currently with XFX on RMA. True my PCIe is locked at 105 rather than 100 - that gives me greatest stability on my FSB overclock and I am sure had no part to play in the failure of memory for GPU2 on the 295. The store I bought it from have already sent me a "no fault found" message but have sent on to XFX; I guess the store just hooked it up to a monitor and looked for symptoms on the screen. Hopefully XFX will be able to test it more thoroughly.

Sound like Mark was just unlucky being saddled with duff parts. Best of luck with EVGA.

F.

---

I remember.. xxxx* OCed also his mobo.. but he forgot to lock the PCIe @ 100 MHz. He was @ 105 MHz.
And now his GTX295 RAM is damaged.
Don't know - if because of this.

I think Sutaru is referring to my GTX295 which is currently with XFX on RMA. True my PCIe is locked at 105 rather than 100 - that gives me greatest stability on my FSB overclock and I am sure had no part to play in the failure of memory for GPU2 on the 295. The store I bought it from have already sent me a "no fault found" message but have sent on to XFX; I guess the store just hooked it up to a monitor and looked for symptoms on the screen. Hopefully XFX will be able to test it more thoroughly.

Sound like Mark was just unlucky being saddled with duff parts. Best of luck with EVGA.

F.

Duh.........
The PCIe is locked at 100......ya take me for a fool? LOL.

I have had the same problem with a 285 that I first bought and now the 295.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

The PCIe is locked at 100......ya take me for a fool? LOL.

Perish the thought - much of what I know of overclocking has come from your posts :)
The key point is that the PCIe is locked (that is what Sutaru was questioning); I didn't imagine it would not be on your rigs. Whether it is at 100 or 105 (as I have) is not relevant to my mind as that difference would not cause either your problem or mine.

F.

---

@ Fred W

Yes, I OCed my QX6700 with higher FSB on my Intel D975XBX2.
But, the PCIe was/is all the time locked @ 100 MHz.
The PCI and PCIe slots have own BIOS overview for OC.

I rised the FSB from 266 to 314 and the 100 (PCIe) didn't changed..


So your PCIe speed is connected to the FSB ?


But - what you have from higher PCIe speed?
More CUDA performance?

The only thing - I guess - little, very little speed up for to send the CUDA WU to/from GPU back to the CPU.
1/2 sec. faster/CUDA WU ? ;-)

The pure GPU calculation time wouldn't profit from it, or?

---

But - what you have from higher PCIe speed?
More CUDA performance?

No. My PCIe has been locked at 105 since long before CUDA was developed. That was the value that gave me the maximum stable FSB overclock when I originally turned up the wick on my rig. I tried everything between 95 and 110 and 105 was the "sweetspot". I don't believe it affects CUDA crunching significantly at all.

F.

---

You all miss the freakin' point.........

The DRIVER won't load. Yes, Fred, I did try locking the PCI at 100........

Whatever.............

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

... The DRIVER won't load.

Just for a giggle and just to test the hardware...

Does the Dotsch/UX USB diskless crunch come with CUDA?


Hope you didn't suffer any other damage from the lightning!

Good luck,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

... The DRIVER won't load.

Just for a giggle and just to test the hardware...

Does the Dotsch/UX USB diskless crunch come with CUDA?

According to Skip Da Shu posting earlier today at AQUA: no it doesn't.

It was a two fold problem... The first being the kernel that gets updated isn't the one used for boot on these PXE boot machines. So, the diskless machines are out till next release of Dotsch/UX which will have the CUDA support.

Then after doing a fresh install of Jaunty on one of the machines I found a timing thing in Debian/Ubuntu about when BOINC starts vs. when x-session starts. I haven't been able to figure out WHY my brother swears he's never seen this on his Jaunty but I can reproduce it on every reboot on one of mine. I've moved the boinc-client start up to later in the rc2.d sequence and it reduces the occurrences of it but does not completely eliminate the problem. All that's required to fix it is to restart boinc-client after the gdm is up so it's low down on my list of stuff to investigate for now.

But if anybody else finds that they don't have a cuda device or cuda device missing after a reboot of Debian/Ubuntu/Xubuntu/Kubuntu... they might try this:

sudo mv -v /etc/rc2.d/S20boinc-client /etc/rc2.d/S32boinc-client

You all miss the freakin' point.........

The DRIVER won't load. Yes, Fred, I did try locking the PCI at 100........

Whatever.............

Hi Mark,

What drivers are you _exactly_ talking about? Meaning: where did you get them, what's the file size etc.

I got 190.38_desktop_winxp_64bit_english_whql.exe from the nvidia website on July 25. It's 96,204,240 bytes and installed without a problem. I have a gtx260 and a gtx280, both Asus, running on it without a problem.

What exactly do you mean when you say that the driver won't load? Any error messages during installation of the driver or is it not recognized when the machine is started up?

Regards,
John.

Marks probably not open to this suggestion but............

I keep thinking that his machines are highly modified and not your run of the mill boxes. I would suggest that he set all the bios settings to the default settings and install Windows XP from scratch. If after this he still has problems with the NVIDIA drivers then he has proven some kind of fault exists. If no problems then probably some bios setting is causing the problem.

Just my opinion.

---

Boinc....Boinc....Boinc....Boinc....

Marks probably not open to this suggestion but............

I keep thinking that his machines are highly modified and not your run of the mill boxes. I would suggest that he set all the bios settings to the default settings and install Windows XP from scratch. If after this he still has problems with the NVIDIA drivers then he has proven some kind of fault exists. If no problems then probably some bios setting is causing the problem.

Just my opinion.

OMG........
STOCK settings????????????????//

Just for the record........

I tried every way from hoo hah to get the drivers to load on my working rig. Spent hours on it............and yes........I backed off on the OC too.

Then, I grabbed a virgin hard drive and installed XP x64 on it.....and updated it.......

Then I got the same results......

A freaking fault exists.........

The kittyman DOES make mistakes here and there.........BUT......this is a driver or Windows problem.

When I have the time, I shall scour the net for a solution as to how to totally remove Nvidia drivers from the system.......
As I am convinced this is the problem. Something is not getting wiped just using intall/remove programs.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

[quote]When I have the time, I shall scour the net for a solution as to how to totally remove Nvidia drivers from the system.......
As I am convinced this is the problem. Something is not getting wiped just using intall/remove programs.

I doubt this is your problem. I usually install NVida's drivers without erasing the older ones. These drivers get unpacked into their own directory and some entries in the registry are changed to point to the new drivers.

Anyway, you installed onto a system that didn't have any older nvidia drivers and it still didn't work. Difficult to judge from a distance, but I get the impression that there is something wrong with your copy of those drivers. That's why I asked where you got them.

Regards,
John.

[quote]When I have the time, I shall scour the net for a solution as to how to totally remove Nvidia drivers from the system.......
As I am convinced this is the problem. Something is not getting wiped just using intall/remove programs.

I doubt this is your problem. I usually install NVida's drivers without erasing the older ones. These drivers get unpacked into their own directory and some entries in the registry are changed to point to the new drivers.

Anyway, you installed onto a system that didn't have any older nvidia drivers and it still didn't work. Difficult to judge from a distance, but I get the impression that there is something wrong with your copy of those drivers. That's why I asked where you got them.

Regards,
John.

Ding ding ding.......wrong answer............

LOL....but thank you for trying.

I tried both the drivers from the CD that came with the card, and with ones downloaded from the net.

Tried installing them from CD, dick stick, and my temp file.

Used the CD files and the downloaded files.

Tried installing them in Windows and in Safe Mode.....

And got the same results on two different rigs................so it's not freakin' hardware........same OS and mobo.




Any other words of wisdom?


Not being mean.........but I DID try a few things before I started complaining.....

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

I don't get it Mark...........

Your posting and starting this thread would suggest you are open for suggestions to remedy the problem. Yet you seem to take every suggestion as a personal attack???

How can you say it's NOT hardware related when two systems with identical mother boards have the problem?

After this I'm outta here cause Mark will probably implode if I hang around.

---

Boinc....Boinc....Boinc....Boinc....

alright, if you want, go to nvidia forums to find some more help... i would say, wait for evga and the next version update and try again.

I don't get it Mark...........

Your posting and starting this thread would suggest you are open for suggestions to remedy the problem. Yet you seem to take every suggestion as a personal attack???

How can you say it's NOT hardware related when two systems with identical mother boards have the problem?

After this I'm outta here cause Mark will probably implode if I hang around.

Sorry to come off that way.........
My bad. Again.

I did not mean to push you off.......it's just that I have tried about every which way to get this to work and it won't.

You and the rest of the Seti crew's help is invaluable..........I was hoping somebody would have a simple sweet solution.

Please do not confuse my angst about the problem with your attempt at helping me.

I promise not to implode.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

When I have the time, I shall scour the net for a solution as to how to totally remove Nvidia drivers from the system.......

Mark, I already pointed you towards that tool in another thread - it's Driver Sweeper.

The clean install would have the default Windows Nvidia drivers in it. When you uninstall them from the control panel they leave a LOT of crap lying about the system. So, re-boot into safe mode then run Driver Sweeper and clean out the Nvidia graphics drivers (I tend to take out the PhysX drivers too). Then restart normally and install the new drivers from there - will require another re-boot before you are done.

Not guaranteeing that it will solve your problem but it works every time for me; I believe it is worth a try.

F.

---

I promise not to implode.

today or for the next week and a half as drivers come out near the 20th.

Apology accepted Mark. Simple and sweet fixes were never meant for you Mark. It's always gotta be the hard way!

---

Boinc....Boinc....Boinc....Boinc....

When I have the time, I shall scour the net for a solution as to how to totally remove Nvidia drivers from the system.......

Mark, I already pointed you towards that tool in another thread - it's Driver Sweeper.

The clean install would have the default Windows Nvidia drivers in it. When you uninstall them from the control panel they leave a LOT of crap lying about the system. So, re-boot into safe mode then run Driver Sweeper and clean out the Nvidia graphics drivers (I tend to take out the PhysX drivers too). Then restart normally and install the new drivers from there - will require another re-boot before you are done.

Not guaranteeing that it will solve your problem but it works every time for me; I believe it is worth a try.

F.

Will try it tomorrow........kitty sweeper, eh?

This has got me confounded, and apparently EVGA as well, as they have not been forthcoming with any answers.

It has to be some whispers of the old installs hanging around, even though Windows install/remove does not see them.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster