January 18, 201016 yr Hello people :)I am starting to wonder if I did anything wrong with my rather new PC.I suffer from time to time complete freeze/crash while running fs9. Tonight, I managed to get the message about what was causing the freeze/crash: the nv drivers.Most of the time, the PC is totally locked, so no way to see what happened.The graphic card is an Asus nVidia GTX 260, operated on WinXP Home 32, 4gb and the 3GB switch for the OOMs etc.The drivers version is 190.45, the latest that were available when I bought the video card.I installed the original nVidia drivers, not the manufacturer's (Asus).The PC was brand new, the OS installation is brand new as well, never had any other gfx drivers.I am starting to wonder if i didnt do smething wrong with nhancer: I kept the original fs9 profile. I once deleted it in order to create a new one, but reverted back since I washaving issues with the new profile.Anyone have any clue as to why I suffer those nvidia drivers crashes?I know video drivers is tricky, and that sometime older drivers are more stable than newer ones.So, perhaps there are some known issues with 190.45 ?Thanks in advance for your replies.
January 18, 201016 yr Ive never used any other drivers but 182.50 since they came out...never had a problem. You can try those if all else fails. - Red E8500 @ 4.1 | EVGA 275GTX (overclocked) | 2x2GB Mushkin Enhanced Redline @ 1066 | Samsung 24inch LCD @ 1920x1080 |
January 20, 201016 yr Author Well thanks Red, I've just downloaded the 182.50 for my next OS reinstall.
January 20, 201016 yr Driver crashes in this case are likely to be caused by one of the following:1) pushing one's CPU overclock too far (unstable overclock)2) faulty RAM3) failing graphics card4) corrupt driver
January 20, 201016 yr Author Thanks Max. Of the 4 options, only the second has hit my mind. I first considered the possibility that my GTX260 was failing, but that would be bad luck: it's never been overheating (which I know cause freezes). The CPU isnt overclocked (an [email protected]), and corrupt drivers I dont see how that could happen, except some wrong writes by hNancer.But as you post, there's a question I have about my RAM: not that I think it could be faulty, otherwise I'd get many more crashes than that. I mounted some Corsair Dominator 2*2gb PC8500,my wonder was that perhaps the timings or whatever doesnt match the CPU FSB (300 in that matter for the E8500)The annoying thing is that the crashes happen on very random basis, I had perhaps only 4 in 5 monthes.The PSU can hardly be involved, being a Corsair 750W.
January 20, 201016 yr Author I understand, I once got mad on an old PC with random crash, but then the crashes resulted in reboots. Not freezes. anyhow, you are getting me now worried about the RAM,shall I modify the speeds accordingly to the FSB or what? I noticed that the BIOS has set the RAM to PC6400 although it is actually PC8500.
January 20, 201016 yr I would suggest you run a memory test using a tool like memtest, burn to CD, then run through several full passes. To be absolutely sure, you should run for 24 hours.
January 20, 201016 yr Author OK I know about memtest, I must still have it on a 3.5 drive, but I tell you what: I dont want to think one second that I might use memtest for some Corsair memory. Damn, if Corsair sells faulty stuff then where is the damned world going? I used memtest on some noname memory ten years ago, and since then only bought branded RAM and never ever had any memory issues.I thought you had some idea about some wrong RAM timings/setting rather than faulty sticks.Thanks for the advises though.
January 20, 201016 yr There's no such thing as a perfect product, especially not one produced in volume. I don't care who makes it. I like Corsair products too, use a VX550 in one of my machines and recommend their PSUs almost exclusively.Also, you misunderstand my advice. The point of testing the RAM is not to necessarily to say that the RAM is "bad", but rather to identify the RAM as a cause of the problems you are experiencing. This may very well include improper timings and/or voltage.
Create an account or sign in to comment