** OFFICIAL ** Intel DX38BT & DX48BT2 BoneTrail Thread

Hey Jimmy. guess you'll learn to love it as we do. With most of the issues ironed out it's a sweet board.

Hi guys ,
I am Running on Hyper x (KHX1800C8D3T1K2/2G) 1800mhz ram that runs on 1066mhz . No matter how many times I change the timming and etc ,The X48bt2 board bios will reset itself !So can anyone enlighten me how to clock the ram to 1600mhz?

My Current setup

QX6800 @ stock(cooled by some china brand heat sink)
(idle at 38Degree celsius)
Intel x48bt2 (stock setting,Latest bios)
2sets x Hyper X (KHX1800C8D3T1K2/2G)
(South bridge and Rams cooled by 40mm fans idle at 38 Degree)
2 x WD black 500gb
1 x Seagate 80gb
1 x 100gb (hitachi)
Asus 8800gts 640mb (running on stock)(cooling by battle axe)
Creative Extrememusic
Window 7 Professional x64
psu > Cooler master 850watt

Quote:

---

Originally Posted by Manel

Hey Jimmy. guess you'll learn to love it as we do. With most of the issues ironed out it's a sweet board.

---

Thanks Manel!

So far I have my FSB at 378 @ 9x = 2.4GHz

My 1333 RAM is overclocked to 1508 9-9-9-24 1.72v

CPU Voltage is at 1.450 46c at idle 72c stressed

I'll give Prime 95 another shot overnight and if I have no problems I'll call it done.

My restart or not restrating problem simply went away. :confused:

Hopefully I won't have any more issues, but this is turning out to be a really nice board, especially since I was thinking it would be a huge nightmare.

The MCH heat sink is absolutely broiling, even at default voltage.

B3nj1, welcome. It seems you have your mem being set to the default SPD or something. What are your RAM settings in BIOS? You might need to set it to the correct frequency in BIOS, although you're not oc'ing as far as I can tell. Your mem will normally default to SPD just in case there are problems and not it's max or rated speed, and if you want it to work at the rated speed or any other you need to adjust it manually, don't leave it at auto or default. Hope that helps.
Jimmy, glad to see you're getting along with your BT. I guess you having all 4 mem slots populated will hold you back in oc'ing and also puts extra burden on the NB. Still, even with only 2 sticks it gets pretty hot. Intel engineers did a pretty good job with the problems in BIOS, I still think some tweaks were in order and a little polishing. However, it's now quite solid.

Quote:

---

Originally Posted by Manel

B3nj1, welcome. It seems you have your mem being set to the default SPD or something. What are your RAM settings in BIOS? You might need to set it to the correct frequency in BIOS, although you're not oc'ing as far as I can tell. Your mem will normally default to SPD just in case there are problems and not it's max or rated speed, and if you want it to work at the rated speed or any other you need to adjust it manually, don't leave it at auto or default. Hope that helps.
Jimmy, glad to see you're getting along with your BT. I guess you having all 4 mem slots populated will hold you back in oc'ing and also puts extra burden on the NB. Still, even with only 2 sticks it gets pretty hot. Intel engineers did a pretty good job with the problems in BIOS, I still think some tweaks were in order and a little polishing. However, it's now quite solid.

---

Hmmm , yes it's on SPD . But no matter what i do in the ram clock setting section it jsut resets , so any advice how to do the setting?

HOpe this maybe help me better
http://i137.photobucket.com/albums/q...0/IMG_0015.jpg
http://i137.photobucket.com/albums/q...0/IMG_0016.jpg

Manel,
Yeah, memory is likely the culprit. I got a lot more mileage out of the Patriot Viper than I could sqwueak from my old OCZ. As for Xs audio issues.... don't get me started on that Win 7 debacle. It does have a lot to do with MS actually implementing HDCP/PAP correctly this time around.

Hey B3nj1. I believe the problem could bw something else, looking at your BIOS pics. You have a Q6800 proc which, I'm not sure though and haven't checked yet, could have an FSB of 1066 also - please confirm. If that is the case you cannot go any further than that with your mem, that's an Intel constrain. Other board vendors go around this issue but not Intel. If this is so you can only oc your proc to get your mem faster.
The other possibility would be to force the mem freq to something else other than default or 1066, but I guess you have done that already.
Just looked at the first pic and in fact the proc is on an 1066 FSB (system bus speed). You're out of luck my friend. You can either get a new proc or underclock your current proc, if it's allowed to lower the multiplier so you can raise the FSB. With a chinese cooler I don't know. You must have an 11 multiplier, if you can set it to 9 and FSB 1333 you'll get 3GHz on your proc and mem at 1333, or maybe try higer even.
Hope that helped.

djs, those Vipers smoke? I like these OCZ cause they have pretty good timings, although with the first BIOS revisions it was a pain to get them working, every time it was working and power would be out the next boot attempts would make me pull out my hair. Now they're pretty ok, although I'm considering more mem and with lower voltage. I'm not sure how those LGA 1156 newer kits will do our board. They're supposed to be optimized for P55 but that would be marketing bull I guess, ost of it at least. Since the mem controller is now in the proc latencies are lower so they could be optimized for that.
Haven't tested 7 yet. Also, haven't seen any info on audio "enhancements" on 7 so I can't really say much. Do you know what changed really in the audio department in 7? That would be an interesting read. Still, a good HDCP implementation shouldn't spoil Dolby I guess.

Quote:

---

Originally Posted by Manel

Hey B3nj1. I believe the problem could bw something else, looking at your BIOS pics. You have a Q6800 proc which, I'm not sure though and haven't checked yet, could have an FSB of 1066 also - please confirm. If that is the case you cannot go any further than that with your mem, that's an Intel constrain. Other board vendors go around this issue but not Intel. If this is so you can only oc your proc to get your mem faster.
The other possibility would be to force the mem freq to something else other than default or 1066, but I guess you have done that already.
Just looked at the first pic and in fact the proc is on an 1066 FSB (system bus speed). You're out of luck my friend. You can either get a new proc or underclock your current proc, if it's allowed to lower the multiplier so you can raise the FSB. With a chinese cooler I don't know. You must have an 11 multiplier, if you can set it to 9 and FSB 1333 you'll get 3GHz on your proc and mem at 1333, or maybe try higer even.
Hope that helped.

---

wow THanks alot ....understood . was wondering isit safe to set it to 9x and FSB 1333

b3nj1, safe it is. Just take care that your temps don't get too high while doing it, just to make sure you don't burn your proc. If it can handle the 1333 FSB that is. You might wanna consider a better cooler for that, or even a new 1333 proc.
I don't think you'll get the 1800 FSB your mem is rated but at least I'm sure it will be running in lower latency. They're rated CL8 but you should be able to maintain it at CL7 up to 1333, maybe even 1600.
If that QX6800 can handle 1333 go for it, just be sure to check the temps. Aren't you running that extreme proc with the stock cooler? Intel doesn't make them, some OEM usually in Taiwan or China. That proc has an unlocked multi so you can play with it and see what's best. Have fun.

THanks... i shall clock it this week end...
Anyway , i will post pictures of the cooler . it shd be some chinese brand but i forgot what model it is.

Anyway , I am quite afraid to adjust the setting in the bios .
I have never set anything related to clock speed on the bios in my life .Mind to guide me through what to set?

b3nj1, Sean posted a pretty good guide some pages back. You might want to read it as it has very helpfull information.
You will need to manually adjust the System Bus Speed (FSB) as well as you System Memory Speed. Keep them synched at 1333 or higher if possible.
You might have to up the proc voltage and maybe the FSB and NB voltage as well. Your mem voltage is quite low at 1.54V which is good, if it's the rated voltage you probably don't need to raise it. Just go step by step raising freq and when your system gets unstable raise voltages. Read Sean's guide, it explains this in detail, not sure what page it is in though, it's 88 pages to look for. Should be in the latest ones. Let us know how it goes. Good luck.

Quote:

---

Originally Posted by Sean-E-Boy

Pontius,

ok, so does the Intel Burn In Self Test crash, hang or blue screen your system, or just give you results that indicate instability?

actually, nevermind that question...

So, since you are making it into windows and can run the intel burn test to some degree, you are hitting mild to moderate instability. In order to tune GTLs, you will need to keep pushing the host clock higher @6x without raising the vCore any (increasing vFSB and vMCH are fine).

Like I said before, there is a progression of overclocking to take here that results in having all areas stable, but you have to push the components in a particular order so that "interfering instability" from other components is minimized...basically making your life easier. and again, they are:

1. with the cpu at its lowest multi and your ram slow and loose, either
a) max out the vFSB and the vMCH (you will be fine here since your CPU and MCH are on water) and start increasing the host clock until the system freezes on boot. Write down the host clock at which the system freezes on boot. Since we are running a low multi, we are (in theory) finding the "maximum" that your FSB can run at.
or b) increase the host clock with vMCH and vFSB at default until instability occurs, then raise vFSB a notch or two...if the instability is gone, continue increasing the host clock until unstable again. if instability remains, increase the vMCH a notch or two and see if it helps. Keep doing this until you reach voltages that you do not want to go above. similar to above, this is the "maximum" that your FSB can run with the selected voltages.

2. once you know the "maximum" FSB for your selected voltages, you can begin tuning the GTLs found under "Reference voltage Override" in the CPU page of the BIOS. there are 3 GTLs that you will primarily be concerned with, 2 here (CPU GTL REF0 and 1), one later (MCH GTL REF), and possibly MCH DDR REF (not much performace or stability to be gained here, though.)

make sure you write down the values listed when you change from auto to manual. you will want to change them one at a time and they will most likely need to be raised, but this depends on the internals of your FSB and CPU cores, so you will need to go both up and down to find the best setting.

One thing to remember here is that while this fine tuning allows for higher FSBs and CPU clocks at lower voltages, the results you will see while testing are rather unimpressive. So with the host clock at the setting where windows freezes on boot and without changing the multi or the voltages, increase the first GTL ref by one. save, restart, and again count how many times the progress bar goes by on boot. now go back to BIOS and change the same GTL ref down one from default. save restart watch the bar.

now that you have gone both up and down one from default, you should be able to tell which direction increases the amount of times the status bar goes by before crashing. if you cannot, go 2 up and 2 down from default and compare. Now that you know which direction to go, change the ref by 1 in that direction save and reboot, count status bars, increase again, count status bars....once you increase beyond the optimal, the number of times the bar passes will start to go back down. then you know you went too far, change the setting back to the level that gives you the longest boot before crashing.

Now move on to the CPU GTL REF1 and repeat the same process. if changing these settings allows you to enter all the way into windows, simply increase the host clock until it freezes on boot.

Once both CPU GTL REF0 and 1 have been tuned DO NOT CHANGE your vFSB.

3. Now having found the optimal cpu refs, increase vCore some and the system should boot @6x multi. Start increasing the host clock again followed by increasing the vCore until you reach the point where you do not want to increase voltage anymore. this will give you the true maximum FSB (well, almost true, unless your vCore and vFSB are maxed).

4. now you know pretty much exactly how fast your FSB can go and can start tweaking memory. with all voltages untouched from #3, drop your host clock back to 333 and, while keeping memory timings loose, change the memory reference frequency to 333 and the memory frequency to 1333 (this is pretty much the fastest practical combination that the x38 as configured in this board can handle) and save and restart. once into windows, run burn in test at least 6 times and make sure that all numbers are the same.

***note*** On the x38/48 boards from intel, resulting memory speeds as seen on the first screen of the BIOS page cannot be higher than the FSB speed.

***also note***this board is f-ing stupid when it comes to changing memory settings....often times you will need to restart several times or even cut all power and then restart a few times to verify that the system will not boot with a particular setting.

5. if burn test results are good, increase the host clock by 20mhz or so and repeat testing. if your memory are good quality, you can probably get the mem frequency into the 1800s (at 333x1333 you will reach this at 450mhz host clock), but you may need to do some research on your ram to see how fast others have gotten it.

as you are working your way up and you start to have issues with booting, or instability or crashing during burn test, you will need to increase the vMCH to correct it. if you have reached either the max vMCH or the maximum you want to run, then you can start playing with MCH GTL REF in the same way you changed the CPU refs. you should know, though, that there is much less functional adjustability with the MCH GTL than with the CPU refs...a few steps is all you will be able to change and see a difference, but those small changes will result in very large gains.

6. once you max out the memory speed at 333x1333, be sure to write down the frequency and the host clock numbers for your reference later. also note that it is unlikely that you will be able to run at this speed at higher multi's, but at least you the max that either your memory can run or the max that the MCH can handle.

Next you will want to go to BIOS, drop the host clock by 20 or so, and then change the memory ref and speed to 400x1600 (results in the same DDR3-Speed, but internal timings of the MCH are loosened). this may or may not boot, but if it does, start increasing the host clock by 5 or 10 and run burn test. repeat until you find the max host clock and memory frequency at this memory setting and write down.

7. continue to work your way down in memory speed....333x1333, 400x1600, 400x1333, 333x1066, 266x800 (unlikely to boot), 400x1066, and finally 333x800 (you already know the max for 400x800, so you dont need to do this again.)

8. now that you know the fastest FSB and the fastest that your memory can run with different memory reference frequencies and memory frequencies, it is time to test the potential of the CPU.

so, set your memory back to 400x800, and go to the max host clock that you found in step #3. save and reboot just to make sure that it still boots. once into windows, restart, go to BIOS and increase the multi by 1 step. save, restart, and run burn test. if everything is ok, restart, go to BIOS, and increase again. Keep doing this until it isnt stable or wont boot.

when you get to the instability part, either increase vCore if you are comfortable doing so, or reduce the host clock until stability is reached.

do this all the way up to your highest multi and write down the highest host clock for each multi and the resulting CPU frequency as you go.

you will find yourself reducing host clock frequency quite a bit as you get closer to your max multi. for example, my q9550 @ 6x could boot at around 505Mhz x6, but at 8x somewhere around 490 was the highest that would boot and the highest stable at 8.5x is 485 and that is with a chit ton of vCore...1.565 or so.

9. now that you know the maximum processor speed at each multi, look at your memory testing and see which setting would run at or above that host clock. pick the fastest resulting DDR3-speed, set it up in BIOS and drop your host clock by 20-30 but stay at highest multi. save, restart and see if it boots. if it does, run burn test 6-10 iterations and see if it is stable. if it is, then increase host clock by 5 or so and try again. if it isnt stable, decrease the host clock and try again. once you know the fastest memory speed that the MCH can handle at your highest multi you can decide if that is good enough or if you want the CPU to be faster and the memory a little slower.

if you choose the faster cpu, leave your host clock at the stable from #9 and change memory settings to next fastest from step #7. save, restart, burn test. if good, increase host clock a few and repeat.

Once you get to a combination that you like that is "stable" run 30 iterations of burn test and see if it passes. if it does, you can start reducing memory timings (start with going from Command Rate of 2T to 1T and see how it goes) if ok, lower the first timing option in BIOS then 2nd and 3rd...if command rate 1T just crashes system (and it probably will) decide if you want faster memory speed or tighter timings and either stay at current mem ref and mem freq and reduce timings with Command Rate at 2T, or reduce host clock until 1T is stable, or reduce memory ref and memory frequency until 1T is stable at the higher host clock.


ok, i am done for now. this should keep you busy for quite some time.

as far as voltages go, yes, increasing them will shorten the life of the component for which they are increased, but whether you will still have this board and processor by the time it dies is unlikely. the most common issue with operating at speeds requiring high voltages is not board or component failure, but rather a degredation of stability at those voltages, requiring you to either increase them more, or overclock to become stable again. but like i said before, my system is running at max vFSB, vMCH, and 1.565 vCore for 6+months. No degredation, no need to increase voltages further. I will for sure let all of you know when these issues come up.

on that note, the 1 voltage to be careful with is the vCore. I havent read anything about peoples processors being killed by high voltage so long as good water cooling is installed. That being said, i wouldnt go over 1.5 if you are at all concerned about killing your CPU...if you are less concerned and may buy another computer in the next year, stay under 1.6.

---

Hi , manel thanks for all ur advices . Is this the guide?

So In the bios i just increase my fsb from 266 to to 333? and mutiplier to x9?
and fsb to 1333mhz? So , i just need to set the setting stright right?

b3nj1, this is the "advanced" guide, this gets into GTL even and it's kinda only when you're an expert and really wanna push the envelope.
There is, I believe, an easier one before this one, posted long time ago.
Anyway, the process is the same, start raising FSB until voltages are not enough anymore, raise voltages a bit, repeat while voltages are safe. You can play it safe and only oc as far as your current voltage lets you go and don't overvolt.
This is a very simplistic aproach of course. You should have some margin at first so you can raise a bit at first, I guess if you go straight for 333 FSB you should manage to hold, try some stress test. If it's ok then start your way from there with smaller increments, like 5 or 10 MHz at a time a when you get to the limit try with even lower increments to reach the highest possible freq.
Go easy on it.

Quote:

---

Originally Posted by Manel

b3nj1, this is the "advanced" guide, this gets into GTL even and it's kinda only when you're an expert and really wanna push the envelope.
There is, I believe, an easier one before this one, posted long time ago.
Anyway, the process is the same, start raising FSB until voltages are not enough anymore, raise voltages a bit, repeat while voltages are safe. You can play it safe and only oc as far as your current voltage lets you go and don't overvolt.
This is a very simplistic aproach of course. You should have some margin at first so you can raise a bit at first, I guess if you go straight for 333 FSB you should manage to hold, try some stress test. If it's ok then start your way from there with smaller increments, like 5 or 10 MHz at a time a when you get to the limit try with even lower increments to reach the highest possible freq.
Go easy on it.

---

hey Manel , I Tired 333mhz and 300mhz at 9x mutiplier , however I was promt to revert back to bios to change setting as it failed for 333mhz , if i set it to 300mhz , i will be able to boot into window 7 loading screen but it hangs after awhile . so what does this means? My rams are still at 1066mhz though

I guess your proc can't handle 333 or 300 right out of the box then. You'll probably need to up the voltage a motch or so.
Have you tried to raise the freq just like 10MHz at a time and see where you get stable, without any voltage adjustments? Try that.
Also, when you adjust reference freq you need to also adjust mem freq since your're on manual now. Keep them in synch.

Quote:

---

Originally Posted by Manel

I guess your proc can't handle 333 or 300 right out of the box then. You'll probably need to up the voltage a motch or so.
Have you tried to raise the freq just like 10MHz at a time and see where you get stable, without any voltage adjustments? Try that.
Also, when you adjust reference freq you need to also adjust mem freq since your're on manual now. Keep them in synch.

---

I heard from my friend that QX chips have extreme high rate of failure during overclocking isit true?
Anyway i dont think my cooler is some china cooler... its actually Gelid Solutions Silent Spirit CPU Cooler

you might wanna check this out
http://www.xoxide.com/gelid-silent-s...cpucooler.html

Well , when i have time after my exams i shall learn how to clock it up step by step .

Haven't heard of QX chips failing, still those are the ones people tend to push harder cause they're specifically made for oc'ers. I believe they're really the same as their Q counterparts, only with unlocked multiplier, probably higher binned as well. They also have higher TDP, for oc'ing for sure.
That's not a chinese cooler alright.
Good luck for your exams, let us know how it goes.

Hey folks, I've been out of touch on this board for awhile.
Got some Corsair 8GB (4x2GB) 1600MHz sticks o RAM here.

What's the trick to getting RAM to run at 1600 on this mobo?

Quote:

---

Originally Posted by Mr Steveo

Hey folks, I've been out of touch on this board for awhile.
Got some Corsair 8GB (4x2GB) 1600MHz sticks o RAM here.

What's the trick to getting RAM to run at 1600 on this mobo?

---

Underclock it to 1333. :rofl:

1600 will happen with only two sticks according to Intel.

Quote:

---

Originally Posted by GasPipeJimmy

Underclock it to 1333. :rofl:

1600 will happen with only two sticks according to Intel.

---

Im laughing . . (on the inside) LOL
Gotta love Intel at times!

Heres some other things Ive gleaned if anyone wants to grade these with a True / False:

XMP only works with 2 RAM sticks in the black slots
RAM wont run at 1600 stable on BIOS 2000 and higher
Intel wont let the RAM run at a bus frequency higher than the FSB



-------------
I tried popping the RAM in, setting all 8GB at XMP profile. (Corsair says CL8 volts are 1.65 but XMP set RAM voltage to 1.91v - weird.)

I then changed the CPU from 9x 333 to 8x 400
- thus CPU went from 3.0GHz to 3.2GHz - seems mild enough. And this allowed the RAM to show and run at 1600.
Sweet yes?
No.
Probably wont surprise many, it booted, but couldn't pass memtest. Had to stop there.

Not much time these days for tweaking and o/c - (married with children now)

Hey guys,

Been a while. I don't know what happened with the latest bios updates, but both my mem are going Haywire.

Viper 1600 running at 1333 System crashes.

Tried my OCZ XMP 1066, machine freezes Man this is my first Intel board., what a fussy piece of junk.

Maybe it's me that isn't patient, but I never got this kind of crap from an ASUS board. Asus boards just plain die, they mess with you :shrug:

Check these nice crash reports:

.................................................
Loading User Symbols
Loading unloaded module list
...............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009ef180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009ef180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

Debugging Details:
------------------


BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff880`03385528 fffff800`02c75443 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ef180 : nt!KeBugCheckEx
fffff880`03385530 fffff800`02cd15f7 : 00000000`00000000 fffff800`00000001 00000000`00001389 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`033855c0 fffff800`02c18895 : fffff800`02c3d3c0 fffff880`03385770 fffff800`02c3d3c0 2aaaaaaa`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`033856c0 fffff800`02cc53f3 : 00000000`51508824 fffff800`02e41e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`033856f0 fffff800`02cd6e00 : fffffa80`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03385880 fffff800`02cb816c : fffffa80`00d55640 00000000`00000000 00000000`00000000 f8a01576`aba80400 : nt!KeFlushMultipleRangeTb+0x260
fffff880`03385950 fffff800`02cb4a11 : fffffa80`039e5b60 00000000`00000000 fffff880`03385c58 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`03385a50 fffff800`02cbc18b : fffffa80`06db2358 fffff800`00000001 00000000`00000001 00000000`00006000 : nt!CcFlushCache+0x561
fffff880`03385b50 fffff800`02cbcd60 : fffff880`04249d00 fffff880`03385c58 00000000`00000000 fffff800`00000000 : nt!CcWriteBehind+0x1eb
fffff880`03385c00 fffff800`02cd6161 : fffffa80`039e2be0 fffff800`02fc2504 fffff800`02ece140 fffffa80`00000005 : nt!CcWorkerThread+0x1c8
fffff880`03385cb0 fffff800`02f6c166 : 480c080c`0c0c040c fffffa80`039e5b60 00000000`00000080 fffffa80`039ce890 : nt!ExpWorkerThread+0x111
fffff880`03385d40 fffff800`02ca7486 : fffff880`03163180 fffffa80`039e5b60 fffff880`0316dfc0 0c080c0a`04040c04 : nt!PspSystemThreadStartup+0x5a
fffff880`03385d80 00000000`00000000 : fffff880`03386000 fffff880`03380000 fffff880`033859f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCL USIVE

BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCL USIVE

Followup: MachineOwner
---------

0: kd> lmvm Unknown_Module
start end module name
0: kd> lmvm Unknown_Module
start end module name
0: kd> lmvm Unknown_Module
start end module name
0: kd> lmvm Unknown_Module
start end module name

So, now i'm trying again with Viper. 4 sticks @ 1333 voltage lowered from 1.90to 1.82 7-7-7-24

Let's wait and see.

Suggestions are more than welcome :up:

Quote:

---

Originally Posted by Zardoc

So, now i'm trying again with Viper. 4 sticks @ 1333 voltage lowered from 1.90to 1.82 7-7-7-24

Let's wait and see.

Suggestions are more than welcome :up:

---

Make sure you are at 2T

Put a 40mmm fan on your Northbridge

Bump your MCH voltage to 1.3v.

My mem timings are in my sig, and they seem to be OK at that all the way up to about 1500+

Reference Frequency: 333
Memory Frequency: 1333

Then go into your "Host Clock" processor frequency override and start marching upward from 333 until it goes unstable or you get the speed you want.

look at the BIOS screen shots here (scroll to bottom): http://www.xbitlabs.com/articles/mai...l-dx48bt2.html

I have not messed with the "Reference Voltage Override Parameter'" screen in the BIOS.

Thanks Gaspipe Jimmy.

I'll look into that.

I just find that this board is very picky with settings (almost Neuro Surgery)

:rofl:

Quote:

---

Originally Posted by Zardoc

Thanks Gaspipe Jimmy.

I'll look into that.

I just find that this board is very picky with settings (almost Neuro Surgery)

:rofl:

---

Picky with setting, picky with memory, and no real documentation as to what some of those BIOS settings actually do, or even which ones go "non-functional" and then suddenly turn back on with various BIOS updates.

In short, it's unnecessarily complicated, with Intel giving no indication of what it takes to get the most out of that board. I think that's one of the reasons this board received such uncomplimentary reviews and had such a short production run.