- Joined
- Jun 16, 2009
- Messages
- 5,123 (0.94/day)
- Location
- North of Germany
System Name | Nexus PC |
---|---|
Processor | Intel Xeon E3-1231 v3, 3600 MHz |
Motherboard | Gigabyte GA-H97-HD3 |
Cooling | Thermalright Macho V2 |
Memory | 24GB DDR3, 1400MHZ CL8 |
Video Card(s) | Sapphire Radeon R9 290 |
Storage | Samsung EVO 960 250gb, EVO 850 250gb, Vertex 3 128gb. 2 TB of Rotational. |
Display(s) | 1xAsus MX299, 2x Asus MX239, Oculus Rift CV1 |
Case | Sunflower Tower |
Audio Device(s) | C-Media CMI8738/C3DX |
Power Supply | Corsair TX850 |
Mouse | Cyborg R.A.T. 7 |
Software | Win7 64Bit Ultimate |
So I was having issues with my GD-70 NB clocks. I finally managed to find stability with it at 2500mhz. I left it at 2500 for over a week just because it was really pissing me off before. Today I finally decided it was good and decided to up the CPU and RAM clocks. I was running 3.9ghz 24/7 on my DFI LP DK M2RSH. So I bumped it up to 3.9ghz and it wouldn't even boot. Neither would 3.8, 3.75 failed on desktop, so did 3.5ghz (whcih I had been running with my 2500mhz NB for the week), failed on 3.350, now running 3.0 stable. Beyond aggrivating.
do you left the rig shut down for a while + lowered NB VID?
i believe too high NB vid bugged me totally,2 days ago