Asus Striker II Extreme: Corruption/Freezes Troubleshooting Thread

[Cibic]

Yeah, tried that mate. The hard drive is being recognized alright in the BIOS, Plug and play OS is disabled on default settings. I also tried SPP<> MCP 200, no effect. The ONLY way I can boot at higher frequencies now is to use CPU level up. If I select it to run cpu level up to get my Q6600 to 3ghz, it'll boot up fine. BUT, if I set fsb to 1333mhz. Oh no! You cant do that! You dont have a system disk! I've had this problem before, but I re-imaged the HDD everytime. Seing as its not a HDD problem, I thought I'd sort out this mobo, and why its doing it.

The black screen and a white message says : "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER."

I am really really really annoyed with this board by now.

Try these:
Insert your operating system installation cd or dvd. Just make sure its the same you used to install it and try to boot from HDD

Disable jmicron and sata raid. If you OS is vista insert vista dvd (that has the repair feature) and click Repair my Computer> startup

What model is your ram? what are you running it at?

[joebloggs]

Thanks for your reply mate.

Ram is Corsair XMS3 1333C9DHX. Everything is on AUTO. I have set command rate to 2T before, as it supposedly helps stability with this board. Running it at 1333mhz as its suposed to be.

As for repairing my Vista install, it is not needed. I just load up defaults in BIOS, and set Boot device priority to CD rom ONLY. Then let it search for a cd, and when it doesnt find anything, I reset, change boot device priority to Hard drive, and it'll boot up from the hard drive just fine, as if nothing had ever happened to it.

[Cibic]

Its worth trying dont you think? While its doing the problem I mean. I suggest changing PnP OS to enabled, boot priority to Hard Drive.
x64 or x86? It might be boot the boot loader. Don't use Level Ups, go manual. Keep FSB linked and synced with ram at 1333 with enough vcore (I would say 1.34~1.36) and stock voltage and timings on ram (check on manufacturers homepage), PLL at 1.52, VTT at 1.34, NB 1.44, SB 1.5, CPU GTL refs +42 +39 +39 +42, NB and DDR3 REFS on auto.
When you say Auto, do you mean voltages, timings? Do you overclock with auto?

[joebloggs]

x64 vista. I did have x86, and the same problem happened with that as well. As for this error it doesnt happen anymore. I've deliberately bluescreened it by not giving it enough voltages. It has booted up just fine 3 times in a row now. As for PnP OS, I thought you said to disable it 2 posts back? If this problem happens again, I will be sure to try repairing vista with the boot cd.

When I say AUTO I mean everything that I didn't otherwise specify. I have got it running 1500 fsb now, but for some reason my Q6600 needs a LOT of vcore. 1.536v after vdrop just to stay stable at 3.375 ghz.

[Cibic]

PNP OS should be disabled when using Raid or having boot issues IMO. Way too much, if your VID is 1.26 you would need 1.34 to 1.36 max with Loadline Calibration. With LLC I need 1.42 for 3.6 GHz and 1.54 for 3.8GHz and 1.6 for 4.05GHz. Oh yeah, forgot to mention my cpu is q6600. Are you running 1500 MHz ram too?

[joebloggs]

PnP OS is disabled now, no issues at the moment. No, running RAM at stock 1333 mhz at stock timings with 1T command rate. Should I set it to 2T?

VID of my cpu is 1.3v. I've set vcore to 1.475 with loadline calibration off. I cannot run 3.6ghz with 1.5vcore and loadline calibration enabled. Always a blue screen or a restart. Sometimes a quick blue screen saying "Parity check/ memory error" then a restart.

Settings I'm using are:
PSU ( Power Supply Unit ) = Zalman HP-1000
CPU = Intel Q6600
RAM = Corsair XMS3 1333 mhx C9DHX 1gb x 4
HDD = Samsung Spinpoint F1 640gb
VGA1 = BFG 9800 GTX+
VGA2 ( if you have ) = BFG 9800 GTX+
VGA3 ( if you have ) =
SPU ( Sound Card ) = Creative X-Fi Titanium
NorthBridge Cooling = Stock
SouthBridge Cooling = Stock
CPU Cooling = Noctua UH-12
RAM Cooling = Corsair dominator airflow fan
nFORCE Chipset Drivers Version = 15.23
ForceWare/GeForce Drivers Version = 181.22
Sound Card Drivers Version = Cant remember
BIOS version :1104

BIOS Settings
Extreme Tweaker
CPU Level Up = Auto
Memory Level Up = Auto
AI Overclock Tuner = Manual
CPU Multiplier = 9x
FSB - Memory Clock Mode = Unlinked
FSB - Memory Ratio =
FSB (QDR) MHz = 1500
MEM (DDR) MHz = 1333
LDT Frequency = 5x
PCIE Bus Slot 1 & 2 MHz = 100
PCIE Bus Slot 3 MHz = 100
SPP<->MCP Ref Clock, MHz = 200
SLI-Ready Memory = Disabled

Memory Timing Setting
P1 = Auto
P2 = Auto
tCL ( CAS Latency ) = Auto (9)
tRCD = Auto (9)
tRP = Auto (9)
tRAS = Auto (24)
Command Per Clock (CMD) = Auto (1T)
tRRD = Auto
tRC = Auto
tWR = Auto
tWTR = Auto
tFAW = Auto
tRD = Auto
tRTP = Auto
tRFC = Auto
tREF = Auto

Over Voltage
CPU Voltage = 1.475
Loadline Calibration = Disabled
CPU PLL Voltage = Auto (1.52)
CPU VTT Voltage = Auto (1.42)
Memory Voltage = Auto (1.66)
NB Core Voltage = 1.44 (1.45/46)
SB Core Voltage = Auto (1.5)
CPU GTL REF0 Ratio = Auto
CPU GTL REF1 Ratio = Auto
CPU GTL REF2 Ratio = Auto
CPU GTL REF3 Ratio = Auto
NB GTL REF Ratio = Auto
DDR3 CHA1 Ref Volt = Auto
DDR3 CHB1 Ref Volt = Auto
DDR3 CHA2 Ref Volt = Auto
DDR3 CHB2 Ref Volt = Auto

CPU Configuration
CPU Internal Thermal Control = Disabled
Limit CPUID MaxVal = Disabled
Enhanced C1 (C1E) = Disabled
Execute Disable Bit = Enabled
Virtualization Technology = Disabled
Enhanced Intel SpeedStep(tm) Tech. = Disabled
CPU Core 2 = Enabled
CPU Core 3 ( Ignore this setting, unless you have a Quad-Core CPU ) = Enabled
CPU Core 4 ( Ignore this setting, unless you have a Quad-Core CPU ) = Enabled

Spread Spectrum Control
CPU Spread Spectrum = Disabled
PCIE Spread Spectrum = Disabled
MCP PCIE Spread Spectrum = Disabled
SATA Spread Spectrum = Disabled
LDT Spread Spectrum = Disabled

Any suggestions to that? Thank for your help so far mate, I really really appreciate it.


EDIT - It Froze on a BSOD stop 1

EDIT - It blue screened during OCCT and stayed there until I reset it.
I tried 2T, and it froze up and bluscreend, and then restarted. I've given it more vcore (1.425 with loadline cal enabled, and 2T now).

[Cibic]

BIOS Settings
Extreme Tweaker
CPU Level Up = Auto
Memory Level Up = Auto
AI Overclock Tuner = Manual
CPU Multiplier = 9x
FSB - Memory Clock Mode = Unlinked
FSB - Memory Ratio =
FSB (QDR) MHz = 1333 You will be unstable on ratios other than 1:1, 1:2, 3:2. Stick to this for now.
MEM (DDR) MHz = 1333
LDT Frequency = 5x
PCIE Bus Slot 1 & 2 MHz = 100
PCIE Bus Slot 3 MHz = 100
SPP<->MCP Ref Clock, MHz = 200
SLI-Ready Memory = Disabled

Memory Timing Setting
P1 = Auto
P2 = Auto
tCL ( CAS Latency ) = 9 set it manualy
tRCD = 9
tRP = 9
tRAS = 24
Command Per Clock (CMD) = 2T That's why u got BSOD at startup
tRRD = Auto
tRC = Auto
tWR = Auto
tWTR = Auto
tFAW = Auto
tRD = Auto
tRTP = Auto
tRFC = Auto
tREF = Auto

Over Voltage
CPU Voltage = 1.39 On load it will drop to 1.36-1.37
Loadline Calibration = Disabled
CPU PLL Voltage = 1.52
CPU VTT Voltage = 1.34
Memory Voltage = 1.6 Your memory is designed for 1.6v, even with corsair dominator 1.66 (1.68-1.7v actual) was too much.
NB Core Voltage = 1.44
SB Core Voltage = 1.5
CPU GTL REF0 Ratio = Auto
CPU GTL REF1 Ratio = Auto
CPU GTL REF2 Ratio = Auto
CPU GTL REF3 Ratio = Auto
NB GTL REF Ratio = Auto
DDR3 CHA1 Ref Volt = DDR3_REF
DDR3 CHB1 Ref Volt = DDR3_REF
DDR3 CHA2 Ref Volt = DDR3_REF
DDR3 CHB2 Ref Volt = DDR3_REF

CPU Configuration
CPU Internal Thermal Control = Auto
Limit CPUID MaxVal = Disabled
Enhanced C1 (C1E) = Disabled
Execute Disable Bit = Enabled
Virtualization Technology = Disabled
Enhanced Intel SpeedStep(tm) Tech. = Disabled
CPU Core 2 = Enabled
CPU Core 3 = Enabled
CPU Core 4 = Enabled

Spread Spectrum Control
CPU Spread Spectrum = Disabled
PCIE Spread Spectrum = Disabled
MCP PCIE Spread Spectrum = Disabled
SATA Spread Spectrum = Disabled
LDT Spread Spectrum = Disabled

[joebloggs]

OK, set everything like you said there. Boots up fine. My RAM has a sticker that says 9-9-9-24 1.5v on their sides. Dont know if that helps? Actual reported voltages by EVEREST are now:
Vcore: 1.46
VTT: 1.36/38
PLL: 1.55
VDIMM: 1.66/68
NB : 1.47
SB: 1.49/50

Cpu-Z reports: 1.456 IDLE, and 1.408 LOAD.

What next?

[Cibic]

OK, set everything like you said there. Boots up fine. My RAM has a sticker that says 9-9-9-24 1.5v on their sides. Dont know if that helps? Actual reported voltages by EVEREST are now:
Vcore: 1.46
VTT: 1.36/38
PLL: 1.55
VDIMM: 1.66/68
NB : 1.47
SB: 1.49/50

Cpu-Z reports: 1.456 IDLE, and 1.408 LOAD.

What next?

Jesus! There's a great chance you damaged your ram, I thought it was the model that runs on 1.6v Mate, check the stickers on all of your ram, if all say 1.5v then set 1.5 on Memory Votlage ASAP.

Use PC Probe to monitor voltages, temps and fan rpm's. If you set 1.39vCore in bios and loadline calibration (LLC) disabled it should be at 1.4 and should drop at 1.36 to 1.37 on load. Verify this in bios, Power> Hardware Monitor>Voltage Monitor

[joebloggs]

Set RAM to 1.5v. I didnt think too much of it at first, They've been getting 1.66 v from the board since September last year. When I first built the pc, I did not have a clue about voltages etc. So on stock its been getting .16v over what its rated for. My RAM reports no errors in Memtest anyway, did 2 full passes. Surely they'd be getting problems by now? Maybe i am just REALLY REALLY lucky that they arent produced errors yet?

As for vcore, I just checked in BIOS voltage monitor, Vcore reports as : 1.44. Cpu-z (v1.50) in windows idle reports 1.456v. Load is 1.392v. These voltages seem all over the place dont they? LLC is disabled.

[Cibic]

Luck is not enough, DDR3 is sensitive to votlages, 2 memtest86+ passes is not enough, leave it overnight or at least 6-12 loopss to check for any errors. To be honest I think you should try booting with 1.36v actual in bios (on load 1.30 -1.31) and run small FFT's in prime95. If it's unstable it should BSOD you immediately.

[MajorFU]

MajorFU running fsb unlinked with ram, though stock is unstable with this board. It might be stable for a while but after a few days you will get BSOD's.

well the most stable setting I have found so far ir running the cpu on auto and setting that ram profile as suggested by the mfr:

XMP profile XMP-1600
Specification PC3-12800
Voltage level 1.900 Volts
Min Cycle time 1.250 ns (800 MHz)
Min tRP 8.75 ns
Min tRCD 8.75 ns
Min tWR 12.50 ns
Min tRAS 22.50 ns
Min tRC 37.50 ns
Min tRFC 75.00 ns
Min tRTP 7.50 ns
Min tRRD 7.50 ns
Command Rate 2T

Timings table
Frequency (MHz) 800
CAS# 7.0
RAS# to CAS# delay 7
RAS# Precharge 7
TRAS 18
TRC 30

If i up the cpu to 1600 it crashes and if i reduce the ram its prolly gonna work ok but the timing table at 667 is fa!l

Timings table
Frequency (MHz) 444 519 593 667 741
CAS# 6.0 7.0 8.0 9.0 10.0
RAS# to CAS# delay 6 8 9 10 11
RAS# Precharge 6 8 9 10 11
TRAS 16 19 22 25 27
TRC 22 26 30 34 37

[joebloggs]

Luck is not enough, DDR3 is sensitive to votlages, 2 memtest86+ passes is not enough, leave it overnight or at least 6-12 loopss to check for any errors. To be honest I think you should try booting with 1.36v in bios (on load 1.30 -1.31) and run small FFT's in prime95. If it's unstable it should BSOD you immediately.

I'll run memtest all day tomorrow then, as I'm in uni all day .

I set Vcore to 1.361v. Its been running Prime95 for 10 minutes with no problems so far. Vcore drops to 1.376 according to cpu-z v1.50.

As for my VDIMM now, I set 1.5v in BIOS. Everest reports 1.58/59v.

What should I do now? vcore seems a lot higher than what it should be yes?

[Cibic]

That's because your cpu needs more voltage. You could try running ram at stock timings, that is most on Auto (including DDR3 REFs) except tCL, tRCD, tRP, tRAS, tRC and tRFC and stock voltage (not the actual, if it says 1.9 then set 1.9 in bios for now).

[Cibic]

I'll run memtest all day tomorrow then, as I'm in uni all day .

I set Vcore to 1.361v. Its been running Prime95 for 10 minutes with no problems so far. Vcore drops to 1.376 according to cpu-z v1.50.

As for my VDIMM now, I set 1.5v in BIOS. Everest reports 1.58/59v.

What should I do now? vcore seems a lot higher than what it should be yes?

I don't think cpu-z or everest should be trusted with this board. From my experience, your ram is probably running at 1.52 - 1.54v. On vCore I meant the actual voltage (in bios or pc probe II) should be at 1.36v.

[joebloggs]

You know where I can get an older version of cpu-z? As I think 1.44 or something like that reported voltages closer to what I set them to...

EDIT - Ill install PC Probe II, see what it says..

[Cibic]

These board utilities piss me off when I have to install them too But since I need them...

[joebloggs]

PC Probe II reports Vcore as 1.42, Load it goes down to 1.38v. Is this OK?

EDIT - So long as I know what they are set at, there should be no problems right?

[Cibic]

Yeah. Set vCore at 1.3 in bios and check PC probe for the actual. You goal is 1.36 actual. What does pc probe say about ram voltage?

[joebloggs]

I set vcore to 1.3v, and as it booted it restarted. BIOS reported 1.36v, but couldnt get it into windows with those volts. I've set it at 1.325v now. ASUS PC probe reports 1.38 vcore, and 1.58 VDIMM.

EDIT - 1.35vcore seems stable so far.. done 15 minutes,

[Cibic]

I set vcore to 1.3v, and as it booted it restarted. I've set it at 1.325v now. ASUS PC probe reports 1.38 vcore, and 1.58 VDIMM.

EDIT - 1.35vcore seems stable so far..

Hm, VID does make a bigger difference than I thought. Same scenario though find where you are stable with small fft's at least an hour and once you think you found the appropriate run prime95 again for at least 4 hours. Hm, vdimm is still quite high, but from what I understand you report the highest value you detect rather the dominant/average. Perhaps you can average it at 1.52 actual thus 1.48 in bios. But to find the appropriate ram voltage (though on stock timings and frequencies) there's technique I found that works great. Run IntelBurnTest latest version, maximum stress and monitor cpu and ram usage (task manager is fine, performance tab). This only takes a minute, once you run IBT it consumes all of your memory then it starts stressing CPU, once it starts on CPU exit, do this twice. You see if ram voltage is low, this technique will freeze your pc. Once you find the voltage that is stable test it with prime95 blend for at least 4 hours.

Edit: I just remembered, memtest for windows does the same memory consuption. It might be best to use that instead.

[joebloggs]

Lowest I can set RAM voltage is 1.5v. I did try the technique you suggested just now. I did it 4 times, just to be safe, didn't freeze at all. Running Stock frequencies and timings but with 2T command rate. maybe try 1T?

EDIT - Dont know if my RAM is totally OK though. i was just watching a video, and was surfing the web, and it sort of "froze" for 1 second with the sound looping in the vid, like a short stutter. But its ok after that.

[Cibic]

I'm not the one to make that decision for you. But I can tell you my opinion, it would probably create instabilities and the performance you get out of it is little. It will not harm your ram but there's a slim chance it might corrupt your OS. You are better of enabling P1 and P2 since it takes it out on vNB (1.44 is fine for your system IMO), which enhances some mch internal timings which gives you some memory read/write improvements.

EDIT: AnandTech suggests that 1T would be good up to DDR3-1860 with 2GB ram. You fit the speed, but not the size. I am not saying there's no chance but I can say that it will be hard.

[joebloggs]

Alright, i'll leave it at 2T for now. Ill forget P1 and P2 for now as well. Ill run memtest all day tomorrow then, see what it'll show.

[Cibic]

That would be a good idea, especially before these 2 changes.