it might be your board, ive got an extra DFI SLI-D motherboard laying around, brand new back from RMA..... http://forums.guru3d.com/showthread.php?t=162096Quote:
Originally Posted by ION84
Printable View
it might be your board, ive got an extra DFI SLI-D motherboard laying around, brand new back from RMA..... http://forums.guru3d.com/showthread.php?t=162096Quote:
Originally Posted by ION84
MSI confirmed that it is my board after all. So would you ship your dfi to Europe Greece? How much do you ask? :)Quote:
it might be your board, ive got an extra DFI SLI-D motherboard laying around, brand new back from RMA..... http://forums.guru3d.com/showthread.php?t=162096
Hi GAR. I was having the exact same problems you spoke of after a few hours of gaming. Things are a lot better now. Thanks!
BTW*Opty 165 user here. :)
Youre welcome!Quote:
Originally Posted by Super Nade
New 1B bios is out and now C&Q works just fine! :)
Hmm sorry but I am confused, which driver do I need to use for a dual-core Opteron 165 (socket 939)?
Gar,
Registered to say thanks. I just changed from a FX-53 to a x2 4400+, and there was a bit of choppiness. Also, I noticed when I ran a CPU intensive app, like rthdribl, the app would be split about 50/50 between the cores. Now, it gets dedicated to 1 core. If I open another occurence, it goes to the other.
I also noticed that after applying the hotfix that certain programs, like WMP, automatically gets it's affinity set to Core1. So, I think the hotfix sets affinities appropriately.
I have had no BSODs, or any problems of any kind.
Thanks again!
these are the drivers that apply to your cpu, download the one for your OS.... http://www.amd.com/us-en/Processors/...1_9033,00.htmlQuote:
Originally Posted by Vassili
and to the guy above, your welcome man, this is why i made the thread to help people who dont know about this.
Applying the registry setting after installing the hotfix increased my idle temperature by 3C with no measureable increase in performance :(
Removed the reg setting and it's back to normal now.
Win 64 bits users don't need to update to this right? I have the x2 3800+.
i dont think you do.Quote:
Originally Posted by MonkSP
Thanks GAR for the useful information.
Only one thing.
Change:
http://www.amd.com/us-en/Processors/...1_9706,00.html
(AMD Athlon™ 64 Processor Utilities and Updates)
To:
http://www.amd.com/us-en/Processors/..._13118,00.html
(AMD Athlon™ 64 X2 Dual Core Processor Utilities & Updates)
:toast:
-k0nsl
Thanks for the heads up man, i changed it.Quote:
Originally Posted by k0nsl
i ran some 3dmark05 tests with and without amd driver... no performance change...
dfi expert
opteron 170 2,9ghz
corsair tccd 2x512
7800gtx
3dmark05
with amd driver: 9190, 9189
with ms driver: 9189, 9184
but cnq dont work for me - it just freeze at windows startup when cnq is enabled. with cnq disabled windows works fine with amd driver, patch and reg entry... maybe its experts fault?
one is clear - with amd driver need for speed mw problem is gone :)
Hi Gar
I can see the point of the reg edit / fix and turning off C&Q and CPU Throttling in the BIOS etc.... *BUT* what is the point of the BOOT.INI edit - you suggest editing the BOOT.INI as follows:-
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOW S
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Micro soft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimer
Whats the point of this BOOT.INI if everythign else is done ?
Also, what does the " S " stand for / do ?
Ben
Hey,
just make sure /usepmtimer is at the end of your boot.ini, then you should be find.
Hi GAR
Can you elaborate on what the /usepmtimer will do if I put it into my boot.ini ?
Ben
Quote:
Originally Posted by ben ifin
via Ars OpenForums:
"So it appears that with the intro of XP SP2 & 2K3 SP1 an additional switch was created for the boot.ini: /usepmtimer.
It appears to correct issues with SpeedStep/related power management features & ACPI HALs where by a processor will clock itself down which may cause the Time Stamp Counter (TSC) to change.
When drivers call hal!HalpPmTimerStallExecProc, they may call for a 50µs wait time, for example, but that wait time increases because the processor is in a different state (not "full power") and creates a longer wait time that is not intended."
"It seems like a crude fix to handle that certain BIOS cannot provide a stable clock when entering power saving modes
http://support.microsoft.com/kb/Q835730
http://support.microsoft.com/kb/Q895980"
Your answer is in the above post, good job man.
Guys, the hotfix from MS only works for WinXP installations that are in the English language. Does somebody have the patch or hotfix for other languages? Someone did post a link to a "hacked" version but the link is not working anymore.
EDIT
link is working, I am downloading now, hopefully it works...
-k0nsl
Quote:
Originally Posted by MonkSP
"update" meaning the hotfix, right? You'll still need the driver? Does anyone have any comments/experience with the differences between win32 and win64? Is it smoother or anything nifty?Quote:
Originally Posted by GAR
this is a great guide! Kudos
please help. I installed the hotfix but now when i go to add/remove programs I can't find it. Whats it called. Also, does it mean i didn't really install it if i can't find it. The setup said it was complete and i downloaded it from the link from this thread????????
when you are in add/remove in the top right side there is a box that says show updates, click on that and its update numbered WindowsXP-KB896256.Quote:
Originally Posted by wisedude
is there a way I can tell if I have the AMD dual core driver installed on my system?