Message boards :
Number crunching :
Linux boinc and nvidia cards
Message board moderation
Author | Message |
---|---|
elec999 ![]() Send message Joined: 24 Nov 02 Posts: 375 Credit: 416,969,548 RAC: 141 ![]() ![]() |
I am sick of windows blue screening on me. How good is linux with boinc and my nvidia Ati cards?[/code] |
![]() Send message Joined: 25 Nov 01 Posts: 21688 Credit: 7,508,002 RAC: 20 ![]() ![]() |
All works fine for most systems for Linux. nVidia cards require a proprietary install of nVidia software but that is all automated and most users 'never notice'. AMD and Intel are very well supported directly. Their drivers are often available on Linux before the other OSes! HOWEVER, beware! Check your hardware is OK first. Run memtest86+ overnight and run a disk check. Linux is very sympathetic to old hardware but will crash just the same for hardware problems. Clean out the dust also? Good luck, Happy crunch in', Martin See new freedom: Mageia Linux Take a look for yourself: Linux Format The Future is what We all make IT (GPLv3) |
OzzFan ![]() ![]() ![]() ![]() Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 ![]() ![]() |
When Windows blue screens, it means there's something wrong, either with the software configuration or the hardware. You may want to troubleshoot that first before switching OSes. Like Martin suggested, Linux is great with compatibility with older hardware, but if you have a hardware problem, switching OSes is not going to solve it. |
![]() ![]() Send message Joined: 18 Aug 99 Posts: 1432 Credit: 110,967,840 RAC: 67 ![]() ![]() |
I agree with the others that the problems that you're having may be caused by a software/hardware configuration. Have more or less solved this problem on my machines by doing the following and haven't had a BSOD since. 1) Get Memtest86+ and run for several hours or even overnight to check your ram sticks. 2) Get a program to analyze what is causing the crashes. I use a product called 'WHAT CRASHED' from http://www.resplendence.com/main. I have found it to be extremely helpful. 3) Get a registry cleaner, preferably one that includes a backup. I've found that too much junk-in-the-trunk of the registry will mess up your machine and sometimes be the actual cause of the BSOD. Did some research and found this one that works extremely well http://zookaware.com/ and I run it regularly on both of my machines. ![]() ![]() I don't buy computers, I build them!! |
OzzFan ![]() ![]() ![]() ![]() Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 ![]() ![]() |
To add to the list of suggestions, I use Blue Screen View. Simply install it on the machine that's crashing, it will show you the STOP (bugcheck) error and the drivers that were running when it crashed. A quick Google search on the bugcheck will often point you in the right direction. |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.