Overclock.net › Forums › Intel › Intel - General › [FIXED] 3960X D1 BSOD 4.6GHz
New Posts  All Forums:Forum Nav:

[FIXED] 3960X D1 BSOD 4.6GHz - Page 2

post #11 of 20
10/14/12 at 2:16pm
Quote:
Originally Posted by ears1991 View Post

Hey! Yeah it seems great now, was the vccsa not being high enough, such a relief after endless banging my head against the desk!!
.....!

thumb.gif

As for the cooler, as you stated earlier, its not its fault but the case's tongue.gif
TheSadFlute
(22 items)
 
DyingHeart
(17 items)
  		 
CPUMotherboardGraphicsRAM
3930K (4.5GHz @ 1.344v) MSI BigBang Xpower II Gigabyte 7970 OC Windforce CF 32GB 1600 G.Skill ARES (4Gx8) 
Hard DriveHard DriveHard DriveHard Drive
Samsung 256GB 840pro Corsair ForceGT 240GB 2TB WD Green 2TB WD Black 
CoolingCoolingCoolingCooling
Zalman CNPS12X 4x 20cm CM MegaFlow Case fans 14cm CM Case fan 2x 120mm UQ fans 
CoolingOSMonitorKeyboard
AeroCool Touch2100 Controller Windows 7 Pro SP1 64-bit 40 Inch Toshiba Regza LCD Logitech G19 
PowerCaseMouseMouse Pad
MK-III Silencer 1200w Cooler Master HAF-X Razer Mamba  Steel Series 
AudioAudio
Sound Blaster X-Fi Titanium Logitech Z5500 5.1 
View all
CPUMotherboardGraphicsRAM
2500k (4.5GHz@1.312v) Asrock Z77 Extreme4 Gigabyte OC WF 580 SLI 16GB G.Skill (4x4GB) 
Hard DriveHard DriveCoolingCooling
G.Skill Phoenix Pro 120GB Seagate 1TB Thermaltake Spin-Q VT 5x120mm UQ fans 
OSMonitorKeyboardPower
W7 Pro SP1 x64 ViewSonic 20' LED 1600x900 Lycosa Thermaltake Toughpower 1500w 
CaseMouseMouse PadAudio
Thermaltake Armor  Razer Mamba XFX WarPad On-board 
Audio
Logitech G35 
View all
  hide details  
Reply
TheSadFlute
(22 items)
 
DyingHeart
(17 items)
  		 
CPUMotherboardGraphicsRAM
3930K (4.5GHz @ 1.344v) MSI BigBang Xpower II Gigabyte 7970 OC Windforce CF 32GB 1600 G.Skill ARES (4Gx8) 
Hard DriveHard DriveHard DriveHard Drive
Samsung 256GB 840pro Corsair ForceGT 240GB 2TB WD Green 2TB WD Black 
CoolingCoolingCoolingCooling
Zalman CNPS12X 4x 20cm CM MegaFlow Case fans 14cm CM Case fan 2x 120mm UQ fans 
CoolingOSMonitorKeyboard
AeroCool Touch2100 Controller Windows 7 Pro SP1 64-bit 40 Inch Toshiba Regza LCD Logitech G19 
PowerCaseMouseMouse Pad
MK-III Silencer 1200w Cooler Master HAF-X Razer Mamba  Steel Series 
AudioAudio
Sound Blaster X-Fi Titanium Logitech Z5500 5.1 
View all
CPUMotherboardGraphicsRAM
2500k (4.5GHz@1.312v) Asrock Z77 Extreme4 Gigabyte OC WF 580 SLI 16GB G.Skill (4x4GB) 
Hard DriveHard DriveCoolingCooling
G.Skill Phoenix Pro 120GB Seagate 1TB Thermaltake Spin-Q VT 5x120mm UQ fans 
OSMonitorKeyboardPower
W7 Pro SP1 x64 ViewSonic 20' LED 1600x900 Lycosa Thermaltake Toughpower 1500w 
CaseMouseMouse PadAudio
Thermaltake Armor  Razer Mamba XFX WarPad On-board 
Audio
Logitech G35 
View all
  hide details  
Reply
post #12 of 20
11/12/12 at 1:34pm
Hello,

I hope someone is going to see this one month after the problem was solved.

I seem to have a similar problem on my X79-UD5 board w/ i7-3820 at 35x125 Mhz (4375 MHz).

I also have d1 stop errors in storport.sys, however under somewhat different circumstances.

In my case it happens 64-74 minutes into OCCT, 64-bit mode with AVX enabled. Also I did believe so far that the iRSTe drivers play a role here.

With iRSTe drivers 3.0 and 3.1 installed, in either RAID or AHCI mode, all seems fine, while with 3.2, 3.5.0 and 3.5.1 involved, the errors occur.

I think that under the hood OCCT might be using Prime routines which leads to the D1 errors like on your ASUS board, when it gets to a certain FFT size. Hence the extremely dead on spot 64 minutes crashes.

What was the VCCSA that solved the problem?

Any other advice for a general voltage range to look for? I have mostly used VCCSA (IMC voltage in Gigabyte-BIOSses) at 1.1V and Vtt too at 1.1. I am currently load testing at 1.2V VCCSA (IMC).
Reply
Reply
post #13 of 20
11/12/12 at 2:16pm
Thread Starter 
VCCSA at 1.6 seemed to be the fix, however it seems my pc d1 BSOD again the other day so I have upped it to 1.2 (as set in the XMP profile for my RAM) so hopefully this is the fix, otherwise I am inclined to agree iwth you about the iRSTe drivers, is storport.sys an intel file?
Raven
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-3970X Asus P9X79 Deluxe GeForce GTX 680 Corsair Vengeance 
Hard DriveHard DriveOptical DriveCooling
Intel SSD 510 Samsung Spinpoint F3 LG GGC-H20L Be Quiet! Dark Rock Pro 
OSMonitorKeyboardPower
Windows 7 Ultimate Dell U2713HM Logitech Illuminated Coolermaster Silent Pro M700 
CaseMouseAudio
Silverstone RV01 Logitech G500 Logitech Z-5500 
View all
  hide details  
Reply
Raven
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-3970X Asus P9X79 Deluxe GeForce GTX 680 Corsair Vengeance 
Hard DriveHard DriveOptical DriveCooling
Intel SSD 510 Samsung Spinpoint F3 LG GGC-H20L Be Quiet! Dark Rock Pro 
OSMonitorKeyboardPower
Windows 7 Ultimate Dell U2713HM Logitech Illuminated Coolermaster Silent Pro M700 
CaseMouseAudio
Silverstone RV01 Logitech G500 Logitech Z-5500 
View all
  hide details  
Reply
post #14 of 20
11/12/12 at 3:26pm
I guess you mean 1.16V VCCSA, not 1.6, right? 1.2 BSODed for me, BTW. I am currently running Prime95 to see if it'll provoke this too.

storport.sys is a Microsoft file that comes with Windows but the name as such implies storage. There was a bug in it in WIndows 7 without SP1 that could also cause a D1, but apparently it is fixed on my Windows 7 SP1 install. I found taht in Microsoft's KB, but the fix it links to is solely for Win7 without SP.

I am also sure that this problem wasn't there before BIOS F13i. F13i fixed a VCore voltage dropping issue that Gigabyte still had. I am now stable with less voltage save for this D1 problem. VCore previously needed to be 1.375V, it is 1.34 now.

I am currently on BIOS F13n (The letter behind the number denominates a beta version)

The F13 beta BIOSses fix another weird problem where the PCH had to be run with 1.2 V with the 1.25 strap enabled, whereas now it runs stable at default. THat's why I wouldn't like to go back to the release F12.
Edited by Amurtigress - 11/12/12 at 3:28pm
Reply
Reply
post #15 of 20
11/12/12 at 5:02pm
Something I just noticed... Changing from F13M to F13n, Gigabyte has replaced the RAID option ROM and the chipset SATA controller is now detected as a regular Intel RAID controller like the ones before with Device ID 2822, instead of being a C600 Server RAID controller with device ID 2826.

What does it look like on the ASUS X79 boards in RAID mode?
Reply
Reply
post #16 of 20
11/13/12 at 4:02pm
Thread Starter 
Yes did mean 1.16V.

In AHCI mode my C600 is DEV_1D02, will check in RAID when I get a chance.
Raven
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-3970X Asus P9X79 Deluxe GeForce GTX 680 Corsair Vengeance 
Hard DriveHard DriveOptical DriveCooling
Intel SSD 510 Samsung Spinpoint F3 LG GGC-H20L Be Quiet! Dark Rock Pro 
OSMonitorKeyboardPower
Windows 7 Ultimate Dell U2713HM Logitech Illuminated Coolermaster Silent Pro M700 
CaseMouseAudio
Silverstone RV01 Logitech G500 Logitech Z-5500 
View all
  hide details  
Reply
Raven
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-3970X Asus P9X79 Deluxe GeForce GTX 680 Corsair Vengeance 
Hard DriveHard DriveOptical DriveCooling
Intel SSD 510 Samsung Spinpoint F3 LG GGC-H20L Be Quiet! Dark Rock Pro 
OSMonitorKeyboardPower
Windows 7 Ultimate Dell U2713HM Logitech Illuminated Coolermaster Silent Pro M700 
CaseMouseAudio
Silverstone RV01 Logitech G500 Logitech Z-5500 
View all
  hide details  
Reply
post #17 of 20
11/13/12 at 8:17pm
Thanks., should not be neccessary anymore. It appears that Gigabyte did that change for all X79 boards for some reason and it does indeed fix my D1 problem. Tho some people are certainly peeved off now for cutting the controller down from Enterprise grade to standard RST drivers.

RST 11.2 drivers work fine here.

Basically we Gigabyte users are now running a ICH10R compatible RAID controller....
Reply
Reply
post #18 of 20
12/15/12 at 6:57pm
IntelBurnTest v2.54
Created by AgentGOD

Processor: Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Clock Speed: 4.66 GHz
Active Physical Cores: 12
Total System Memory: 16324 MB

Stress Level: High (2048 MB)
Testing started on 12/1/2012 3:07:31 PM
Time (s) Speed (GFlops) Result
[15:08:02] 17.961 147.1228 3.316935e-002
[15:08:32] 17.960 147.1362 3.316935e-002
[15:09:02] 18.208 145.1345 3.316935e-002
[15:09:33] 17.901 147.6173 3.316935e-002
[15:10:03] 17.863 147.9358 3.316935e-002
[15:10:32] 18.068 146.2545 3.316935e-002
[15:11:02] 18.000 146.8069 3.316935e-002
[15:11:32] 18.003 146.7809 3.316935e-002
[15:12:02] 17.938 147.3187 3.316935e-002
[15:12:32] 18.277 144.5814 3.316935e-002
Testing ended on 12/1/2012 3:12:32 PM
Test Result: Success.
I can pass the burn test but my BF3 started crashing or loading a MP map with no weapon in hand. I also have FC3 but it is buggy also. :/ IL2 COD runs fine.
Fish Tank
(25 items)
 
2006 C6 Corvette LS2 Z51
(6 photos)
 
CPUMotherboardGraphicsGraphics
Intel Core i7 3930K BIOS 3101 RAMPAGE IV EXTREME eVGA GTX 680, HK GPU X3 WB eVGA GTX 680 
RAMHard DriveHard DriveHard Drive
Corsair Dominator GT OCZ Revo 3 PCIe SSD Win7 64bit OCZ Vertex 60G x2 RAID 0 OCZ Vertex 60G Linux MInt 13  
Optical DriveCoolingCoolingCooling
SH-S223F XSPC Raystorm  Bitspower Dual D5 MOD Top extreme  Heatkiller GPU X3 with HK back plate 
CoolingCoolingOSOS
Swiftech MCR220 TFC Xchanger 240 Windows 7 64 bit Linux Mint 13  
MonitorKeyboardPowerCase
X270OC 27" 2560x1440, ASUS VW266H Logitech G510 Corsair AX1200 Danger Den Water Box Plus FE 
MouseAudioOtherOther
Razer Mamba 2012 Creative X-FI Titanium Fatality  Killer NIC K2100 Saitek Pro Flight Combat Rudder Pedals  
Other
Thrustmaster HOTAS Warthog 
View all
  hide details  
Reply
Fish Tank
(25 items)
 
2006 C6 Corvette LS2 Z51
(6 photos)
 
CPUMotherboardGraphicsGraphics
Intel Core i7 3930K BIOS 3101 RAMPAGE IV EXTREME eVGA GTX 680, HK GPU X3 WB eVGA GTX 680 
RAMHard DriveHard DriveHard Drive
Corsair Dominator GT OCZ Revo 3 PCIe SSD Win7 64bit OCZ Vertex 60G x2 RAID 0 OCZ Vertex 60G Linux MInt 13  
Optical DriveCoolingCoolingCooling
SH-S223F XSPC Raystorm  Bitspower Dual D5 MOD Top extreme  Heatkiller GPU X3 with HK back plate 
CoolingCoolingOSOS
Swiftech MCR220 TFC Xchanger 240 Windows 7 64 bit Linux Mint 13  
MonitorKeyboardPowerCase
X270OC 27" 2560x1440, ASUS VW266H Logitech G510 Corsair AX1200 Danger Den Water Box Plus FE 
MouseAudioOtherOther
Razer Mamba 2012 Creative X-FI Titanium Fatality  Killer NIC K2100 Saitek Pro Flight Combat Rudder Pedals  
Other
Thrustmaster HOTAS Warthog 
View all
  hide details  
Reply
post #19 of 20
12/16/12 at 2:13am
Thread Starter 
Id avoid offset voltage until you can get your pc stable with a fixed vcore, then you can use that to work out what offset you need (personally dont trust offset so ive just left mine on fixed)

IBT isnt a good enough stress test in my experience, so use prime95, blend, then click custom, enter a large amount of ram (i do 14000 for 16gb)
and see how you get on with that. For me, once i had the right vcore + ram set up correct (just used xmp profile to set it for me) i didnt really have to change much else. The bsod error codes can be useful to work out whats wrong smile.gif
Raven
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-3970X Asus P9X79 Deluxe GeForce GTX 680 Corsair Vengeance 
Hard DriveHard DriveOptical DriveCooling
Intel SSD 510 Samsung Spinpoint F3 LG GGC-H20L Be Quiet! Dark Rock Pro 
OSMonitorKeyboardPower
Windows 7 Ultimate Dell U2713HM Logitech Illuminated Coolermaster Silent Pro M700 
CaseMouseAudio
Silverstone RV01 Logitech G500 Logitech Z-5500 
View all
  hide details  
Reply
Raven
(15 items)
  		  
CPUMotherboardGraphicsRAM
Core i7-3970X Asus P9X79 Deluxe GeForce GTX 680 Corsair Vengeance 
Hard DriveHard DriveOptical DriveCooling
Intel SSD 510 Samsung Spinpoint F3 LG GGC-H20L Be Quiet! Dark Rock Pro 
OSMonitorKeyboardPower
Windows 7 Ultimate Dell U2713HM Logitech Illuminated Coolermaster Silent Pro M700 
CaseMouseAudio
Silverstone RV01 Logitech G500 Logitech Z-5500 
View all
  hide details  
Reply
post #20 of 20
12/16/12 at 11:45am
ears: I've used IBT with AVX support, without AVX, Prime95 and OCCT to stress test. Prime 95 does NOT seem to be a viable test, it passes for hours while OCCT in 64 bit mode with AVX enabled crashes the system within minutes on insufficient voltage.

How is Prime 95, which is at least 7 years old in the latest build (binaries are just as old), supposed to seriously stress test new command extensions like SSE 3,4 and AVX which they were never written for? wink.gif

Sorry for bringing this up, but I called Gigabyte on this D1 crash issue and they treated me like I knew nothing even after having made my own builds for beyond 20 years.... mad.gif ...and this support PERSON said I should use Prime 95 instead. Yah right....

Edit: Apparently I lost track of Prime95. Just downloaded v2.77 64 bit w/ AVX support.

Harumph! rolleyes.gif
Edited by Amurtigress - 12/16/12 at 12:16pm
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › [FIXED] 3960X D1 BSOD 4.6GHz