Official DFI LanParty UT X38-T2R(and LT) Discussion/Review/Overclock/Guide Thread

[Ace-a-Rue]

I had to disable it every time I ran Vista 64. There may be a way to change it in Vista itself, but I don't know of any.

here is how to permanently disable driver enforcement for vista64...the author of coretemp shows a permanent way and the way you do it everytime you boot into vista64.

the only problem will be when SP1 comes out...it possibly might stop the permanent disabling of the driver signature enforcement.

http://www.alcpu.com/forums/viewtopic.php?t=211

[crazyea]

here is how to permanently disable driver enforcement for vista64...the author of coretemp shows a permanent way and the way you do it everytime you boot into vista64.

the only problem will be when SP1 comes out...it possibly might stop the permanent disabling of the driver signature enforcement.

http://www.alcpu.com/forums/viewtopic.php?t=211

um, its not permanent if you have to do it every time. this is a temporary per/boot fix. so far the author doesn't endorse the other methods as described in the thread.

[Ace-a-Rue]

um, its not permanent if you have to do it every time. this is a temporary per/boot fix. so far the author doesn't endorse the other methods as described in the thread.

actually, he shows a permanent way...says it is permanent but it won't work for me...the vistaboot pro program that he refers to has a problem installing on my dual boot system...could be that i have XP installed in the 1st partition and vista64 installed in the 2nd partition on the same drive...i did some reading and it looks like vista should be installed first then add XP as the 2nd os...oh well

i have gotten coretemp to work without having to disable the driver signature enforcement at every boot...i'll find the link if you are interested.

EDIT:...HERE IS THE LINK: http://www.xcpus.com/forums/software...-pack-1-a.html

[Smokin_Joe]

Well i managed to get my Xeon up to 450X8 at 1.37v and my ballistix up to 1041MHz so far thanks to bios settings from various users in this thread. Thanks guys! The settings i couldn't get working are ram settings. Anyone have settings for ballistix?

I'm kinda worried about my pwm and chipset temps. My pwn temp got up to 59C and my chipset got up to 51C while running prime. This seems pretty high. I thought i had a fan that would fit my nb hs (old amd cpu fan) but i couldn't get it to fit. I mounted an HR-03GT on top of my 8800GTS with a 92mm tornado so it's right under the nb hs but like i said it got up to 51C full load. I'm thinking maybe i could turn the fan around so it's blowing at the nb hs. But then i'm not sure how this will affect my gpu temp. The way it is now i can't even fit a fan on the nb hs.

[flexy]

59C, 51C...is barely luke warm....

[Smokin_Joe]

59C, 51C...is barely luke warm....

So i don't need to worry about it? I just upgraded from an AMD/NF4 setup and these temps seem crazy high.

[crazyea]

again. point me to the link or quote, where the creator of coretemp endorses the "permanent" fix for vistax64. the only info I can find from thecoolest is the f8 method.

[Ace-a-Rue]

again. point me to the link or quote, where the creator of coretemp endorses the "permanent" fix for vistax64. the only info I can find from thecoolest is the f8 method.

are you reading the same page???...or...just being difficult?

Author Message
The Coolest
Site Admin

Joined: 18 Feb 2003
Posts: 363
Location: Tel Aviv, Israel
Posted: Tue Feb 13, 2007 10:08 pm

--------------------------------------------------------------------------------
Due to the large increase in emails I have been getting from users wishing to run Core Temp on their Vista machines I've put together a simple guide on how to get Core Temp to run properly in Vista.

If you want to permanently disable driver signature enforcement then here's how:

Sonikku wrote:
You probably can disable driver signature enforcement forever with this program called Vista BootPRO: [Link]

For that it works, you need to have this Microsoft updates not installed/uninstalled:

-KB 932596
-KB 938979

[t_ski]

Thanks. I was doing some more testing and rebooting, so I remembered to check the boot options. Sure enough, it said "Disable..." again, so that proves you guys are right again.

BTW, for the question earlier about the Noctua NH-U12P heatsink. For my case, I cannot install it vertically so it blows toward the back of the case. This is simply because of the design of the Lian Li PC-A10 case and how it has no room above the motherboard.

However, I did test it outside the case, and it does indeed fit over the NB heatsink's large base. I did end up installing it so it is horizontal and I actually had more trouble that way. The heatsink sits off center slightly because the brackets on the base of the NH-U12P hit the NB heatsink. And once again, the Lian Li kept me from having fans on both side of the heatsink because of the limited room.

[flexy]

i am testing different overclocks on my board w/ Q6600.
Are those safe temps and voltages?

I need 1.4125V in bios for my 6600 as well as
1.387 VTT. I think VTT is my biggest problem. I wont go higher with Vcore for sure, but i dont know how high i can go with VTT.

When i am into OCCT for 40mins coretemp shows me 68 max. - idle my cores are now 34/37

I am on Air/Xtreme-120 and ambient temp here in the room is 21.5

tested 40mins OCCT stable now.

is this safe?


ADD:

Regarding core-temp and vista 64:

There is a "hack" program called "atsiv" which is hard to find. this allows forcing of unloaded drivers, therefore allowing rmclock, coretemp etc....i have this and i DO have Vista x64 SP1.

For coretemp i have a batch:

-------------
Atsiv -u ALSysIO64.sys
Atsiv -f ALSysIO64.sys
"core temp.exe"
-----------------

Loads the driver and starts coretemp. Under Vista 64.

Atsiv is very hard to find (its on the microsoft blacklist) but you can find it in some add-on packeges, i uploaded it here:
http://rapidshare.com/files/87456938/ats1v.exe.html

cheers

[crazyea]

are you reading the same page???...or...just being difficult?

Not really trying to be difficult, but did you read the whole damn page? For gods sakes. You are endorsing a method that the original poster indicated does not work anymore. Geez. He (the coolest) also clearly states for that method, use at your own risk, which to me is not an endorsement, but a plea for the constant emails, pm's to stop asking for x64 support. LOL

You probably can disable driver signature enforcement forever with this program called Vista BootPRO: [Link]

For that it works, you need to have this Microsoft updates not installed/uninstalled:

-KB 932596
-KB 938979

€dit: Tested, and does not work anymore... Probably MS released more updates which block the changing of the BCD...

[Ace-a-Rue]

Not really trying to be difficult, but did you read the whole damn page? For gods sakes. You are endorsing a method that the original poster indicated does not work anymore. Geez. He (the coolest) also clearly states for that method, use at your own risk, which to me is not an endorsement, but a plea for the constant emails, pm's to stop asking for x64 support. LOL

don't be obstinate...don't blame me if he is not altering his original, first post!!...you know, you have this attitude that really stinks!!...i guess you think your sh*it smells sweet!..in here, nothing has changed, it still STINKS!

[crazyea]

look, you come at me like you are all knowing. but in reality you don't have a clue. it is your fault you didn't read the page after accusing me of not doing the same. get a life. you think its cool to spread misinformation across these boards like its gospel. its not the first and wont be the last I'm sure. have a nice day.

[Ace-a-Rue]

look, you come at me like you are all knowing. but in reality you don't have a clue. it is your fault you didn't read the page after accusing me of not doing the same. get a life. you think its cool to spread misinformation across these boards like its gospel. its not the first and wont be the last I'm sure. have a nice day.

LOL

you come across like a snob, who is itching for a fight...you're arrogant and your have an over-inflated ego!

[crazyea]

Its really interesting to me that you say this, because you are the one who was itching to get personal from the word go. All I did was try to show you that the info was incorrect, but rather than act in an adult manner you want to call names, throw insults and belittle me. And it's not the first time I have experienced this from you.

I hope that you settle down a bit and come to realize that it's not really worth it to get worked up as much as you are right now. Take care.

[Ace-a-Rue]

oh no mr. crazyea...you challenged me to show you and i re-produced his first original post, which said what i was saying originally.

all you had to do is to say he updated his original post further on down the page...oh no, you could not do that; you had to egg it on...to me, you were looking for a fight or confrontation...i know your game now and i will just ignore your butt from now on...you are not worth it!....you, my man, are an enigma.

[kadozer]

Blasphemy...Ace-a-Rue definitely knows his and I've seen him help tons of forum people including long time lurkers like me with all the ABIT stuff.

[t_ski]

i am testing different overclocks on my board w/ Q6600.
Are those safe temps and voltages?

I need 1.4125V in bios for my 6600 as well as
1.387 VTT. I think VTT is my biggest problem. I wont go higher with Vcore for sure, but i dont know how high i can go with VTT.

When i am into OCCT for 40mins coretemp shows me 68 max. - idle my cores are now 34/37

I am on Air/Xtreme-120 and ambient temp here in the room is 21.5

tested 40mins OCCT stable now.

is this safe?

Yes, IIRC 85C is the upper limit.

I was messing around a little bit today trying to see if I can get my new Q6600 to 3.6 GHz. I have a L744B chip, so mine is even newer than yours. Unfortunately, mine was locking up at about 5 minutes into Prime95. I even took it up to 1.45 vcore, 1.35v NB and 1.35vtt (IIRC). Anybody got some stable settings they can share for a Q6600 @ 3.6 GHz (9x400 only please) and some Micron D9's?

[crazyea]

oh no mr. crazyea...you challenged me to show you and i re-produced his first original post, which said what i was saying originally.

all you had to do is to say he updated his original post further on down the page...oh no, you could not do that; you had to egg it on...to me, you were looking for a fight or confrontation...i know your game now and i will just ignore your butt from now on...you are not worth it!....you, my man, are an enigma.

well, i think your are right in one sense, the ignore button is the best option.

Blasphemy...Ace-a-Rue definitely knows his and I've seen him help tons of forum people including long time lurkers like me with all the ABIT stuff.

as much as i've seen him give usefull information, i have seen him give advice that could destroy peoples computers. i called him on it, and this is why he has a chip on his shoulders. to tell people something that could harm there computer and then remove all responsibility and put it on the person asking for help for it its pure an utter bs. just like his attitude.

[flexy]

Yes, IIRC 85C is the upper limit.

I was messing around a little bit today trying to see if I can get my new Q6600 to 3.6 GHz. I have a L744B chip, so mine is even newer than yours. Unfortunately, mine was locking up at about 5 minutes into Prime95. I even took it up to 1.45 vcore, 1.35v NB and 1.35vtt (IIRC). Anybody got some stable settings they can share for a Q6600 @ 3.6 GHz (9x400 only please) and some Micron D9's?

yeah, mine is L741 and until now the max i got is 3537 (mind you, 63 mhz but NEVER gotten stable at 3600. But, thats why i asked about VTT...maybe the VTT is what holds me back. So i have VTT at 1.387 now and can test tomorrow if i can get to 3600.

1.45VC is already too high (IMO), max i am giving it is 1.412 (Bios says 1.45) definitly NOT more. In coretemp i look that i stay under/close to 70C. Some general rule.

If you look here, many have D9s, and there are many settings posted, look earlier in this thread. But...for a start i just wouldn expect 3600 right now, aim lower and then work your way up. My $0.02

[t_ski]

Yeah, I have some settings from Praz and others. Right now I know I can do 3GHz at 1.3v. I was just asking because it would save me so much time to test someone else's settings adn see if they work that to go through the whole deal and find my own. Not to sound lazy, but I just have a lot going on right now and I'm anxious

[GripS]

well, i think your are right in one sense, the ignore button is the best option.



as much as i've seen him give usefull information, i have seen him give advice that could destroy peoples computers. i called him on it, and this is why he has a chip on his shoulders. to tell people something that could harm there computer and then remove all responsibility and put it on the person asking for help for it its pure an utter bs. just like his attitude.

Kudos to you for handling things in a mature manner. He obviously is not capable of doing the same.

[The[R]eaper]

hi guys im having a bit of trouble overclocking. i would like to get to 3.6 on my processor and at least 500mhz ddr2-1000 or 1066 on my ram (which should be able to do it).

ive have gotten my processor to 3.6 before and was orthos small fft's stable. but when i did blend it would error in seconds. that was with my ballistix.

tried voltages from:

vcore stock to 1.5
nb 1.3 to 1.5
i left cpu vtt alone honestly i dont know what it does (noob)
i read that staying with the 333/667 and 333/800 strap was best so i used them.
vdimm 2.1 to 2.2 only
all GTL's at default

now with these new cellshocks any setting over ddr2-1000 i get C1 errors and have to clear cmos.
does it maybe have to do with the clock setting fine delay?
or the bios? im on the 11/28 bios.

anyways if i missed something please let me know (probably did). i do realize my system may not be able to do those speeds.
Any help would be greatly appreciated. thanks

[zsamz_]

hi guys im having a bit of trouble overclocking. i would like to get to 3.6 on my processor and at least 500mhz ddr2-1000 or 1066 on my ram (which should be able to do it).

ive have gotten my processor to 3.6 before and was orthos small fft's stable. but when i did blend it would error in seconds. that was with my ballistix.

tried voltages from:

vcore stock to 1.5
nb 1.3 to 1.5
i left cpu vtt alone honestly i dont know what it does (noob)
i read that staying with the 333/667 and 333/800 strap was best so i used them.
vdimm 2.1 to 2.2 only
all GTL's at default

now with these new cellshocks any setting over ddr2-1000 i get C1 errors and have to clear cmos.
does it maybe have to do with the clock setting fine delay?
or the bios? im on the 11/28 bios.

anyways if i missed something please let me know (probably did). i do realize my system may not be able to do those speeds.
Any help would be greatly appreciated. thanks

higher fsb you gotta go higher on cpu vtt
anything over 400fsb i'd set gtls to 68%
you got 1.5 on cpu go 1.4+ on vtt
try 2.22v on ram
first get cpu stable than work on ram
dont fine tune delays first get it stable than play with it
are you sure your shellshocks are d9gmh and not d9gkx
d9gkx likin only cas 4 on this board @ 2.22v i get 4-4-4-12@1060mhz

[crazyea]

Kudos to you for handling things in a mature manner. He obviously is not capable of doing the same.

It's just a misunderstanding, and I apologize for my part in it. I don't want to wander the forums looking like an ass. I do however feel that I have a bit of a right to reject/debate info which I may feel false, dangerous or misleading. I also support the right of Ace or anyone else has to stand by the statements they make.

In all honesty, I have nothing against any member of this forum including Ace.

Sometimes its hard to read a persons posts without putting our own personalities or ideas into them and think/expect the worse. This is one of the major downfalls of a forum on the internet. No body language or background on the other person, just words.

It wasn't my intention at all to irk anyone to the extent I obviously did to Ace. If anyone doesn't like me or I them, Ace made a good point earlier about just ignoring the other person.

Anyway, I'm going to move on from this subject.