• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

GeForce drivers freezing new system

Associate
Joined
17 Dec 2003
Posts
492
I've just upgraded my system from a Q6600 based one to this:

New components: Intel i5-2500k, ASUS P8H67-M (B3), OCZ 4Gb DDR3
Old components: NVIDIA GTX 260, Corsair HX520W, Crucial P64 SSD
OS: W7x64

However my problem is I can't get the NVIDIA GTX260 to work on my new ASUS P8H67-M.

It freezes my system within a few seconds of reaching the desktop after boot. If I don't install the GeForce drivers and just use the Standard Windows VGA drivers, or boot in Safe Mode, it doesn't freeze, but i've tried 3 different Geforce drivers and all have the same problem.

(275.27 (latest beta), 266.58 (latest stable), 197.13 (Apr'10 driver))

I know the graphics card hardware is fine as I've tested it on another system. Everything points to it being a graphics driver issue but I can't yet rule out it being a motherboard issue until I can get hold of another PCI-e card to try (preferably ATI).

Maybe the old GTX260 just won't work on the new motherboard? As I say, I don't have another PCI-e card to try and don't want to buy one when I know my GTX260 isn't faulty.

I've tried clearing the CMOS a couple of times, all drivers/bios are up to date, and I have no reason to think it's power issue based on my spec. I've also done 3 clean installs, same problem each time.

At the moment I'm just using the on board graphics, which disable automatically on this board when a gfx card is present, so I don't think there is a conflict there.

Any ideas?
 
Did you reinstall windows after changing motherboard?

Yes, I'm on my third clean install.

Also make sure that Intel EIST/Speed Step is disabled in the BIOS and correct RAM timings are loaded/set.

I'll check the Intel EIST/Speed Step.

I wouldn't know what the correct RAM timings should be though. They are just the default ones. Is there any more advice you can give on that?

Thanks
 
Do you have an option in the BIOS to load an XMP profile for your RAM? friend of mine was having issues with freezing on his Asus 67 board because it wasn't loading the correct SPD settings by default - can't really help with the specifics of the BIOS on that board as I tend to stay away from Asus motherboards when I can :S
 
Do you have an option in the BIOS to load an XMP profile for your RAM? friend of mine was having issues with freezing on his Asus 67 board because it wasn't loading the correct SPD settings by default - can't really help with the specifics of the BIOS on that board as I tend to stay away from Asus motherboards when I can :S

I do yes.

You mentioning that it might be a RAM issue lead me to this thread:

http://www.ocztechnologyforum.com/f...hannel-mode-in-a-ASUS-P8H67-M-Pro-Motherboard.

The guys spec is almost identical to mine and he fixed it by changing the RAM voltage.

I'll try what he did.
 
Do you know what model your RAM is? some is designed for 1.5 and some 1.65 operation.

OCZ Intel Extreme XMP 4GB (2x2GB) DDR3 (OCZ3X1333LV4GK)

It's the same as the guys in the thread I posted above, who was advised that the voltage needs to be changed manually to 1.65 from 1.5.
 
According to the XMP profile these should run at XMP Profile 1:1333MHz 8-8-8-20 1.60V in standard mode - you shouldn't need 1.65 unless using the higher performance profile, tho you'd definitely need more than 1.5 to get them stable so hopefully thats what your problem is and not something harder to troubleshoot.
 
OCZ Intel Extreme XMP 4GB (2x2GB) DDR3 10666C7 1333MHz Low Voltage Dual-Channel Kit (OCZ3X1333LV4GK)
- Designed specifically for the Intel® P55 chipset
- XMP Profile 1:1333MHz 8-8-8-20 1.60V
- XMP Profile 2:1333MHz 7-7-7-20 1.60V
- Available 4GB D/C Optimized kits
- Unbuffered
- Intel Branded XTC Heatspreader
-Lifetime Warranty
- 240Pin DIMM

Try just using one stick at a time and see whats happens or test your memory with memtest one stick at a time, memory might be faulty.
 
I've enabled XMP and selected a profile, and while the BIOS is stating the DRAM voltage has changed from 1.5 to 1.6v, my CPU-Z SPD details don't change.

5ifzKSzF3GCAuxQ-Region.png


However i'm confused as that states 1.5 and 1.6v.

Any ideas?
 
That 2nd part of the window just lists available profiles that the RAM can be run in - AFAIK the only true way to see DRAM voltage is from the hardware monitoring section of the BIOS (if its included there).

The problem is XMP isn't really a proper standard and JEDEC/SPD settings have never worked correctly so you end up with some weird mix of settings at default which often don't work properly - manually loading an XMP profile and checking voltage is correct should work properly.
 
I see.

OK well my BIOS is saying the RAM is at 1.6v, but it's not fixed my problem.

I guess I'll return to my original theory that it's a graphics card problem. I'll try a new card on Saturday when I borrow one.
 
Last edited:
OCZ Intel Extreme XMP 4GB (2x2GB) DDR3 10666C7 1333MHz Low Voltage Dual-Channel Kit (OCZ3X1333LV4GK)
- Designed specifically for the Intel® P55 chipset
- XMP Profile 1:1333MHz 8-8-8-20 1.60V
- XMP Profile 2:1333MHz 7-7-7-20 1.60V
- Available 4GB D/C Optimized kits
- Unbuffered
- Intel Branded XTC Heatspreader
-Lifetime Warranty
- 240Pin DIMM

Try just using one stick at a time and see whats happens or test your memory with memtest one stick at a time, memory might be faulty.

I've tried single sticks, and memtest. No difference or any errors.
 
If memtest passes fine then its probably not the RAM.

The problem is the GPU drivers being one of the most intensive real time parts of the system are very sensitive to any fault or instability in the system and the first point of failure even tho its probably not a GPU/GPU driver problem, sometimes changing GPU/driver can mask the problem making you think its solved but its still lurking there underneath.
 
Back
Top Bottom