What OS? Can you describe what happens? Screenshot maybe?
What OS? Can you describe what happens? Screenshot maybe?
The OS is the Windows XP, is the clock generator that doesn´t work.Quote:
Originally Posted by lukija
Anyone tested A64info on a system with AMD dual core optimizer 1.1 installed? It seemed that A64info causing system restart with the AMD driver installed. Previous A64info release was fine on my system. BTW, I am running Windows XP SP2 Pro.
A64info is by far the best too for Athlon64 system. Great work!
First, greetings to all of you, since this is my first post ;)Quote:
Originally Posted by SunFlowerSeeds
SunFlowerSeeds, you are right. AMD dual core optimizer driver and A64info simply don`t work together.
When I started A64 info with optimizer installed, I got a BSOD (very short message; sorry Lukija, I forgot to write it down) and needed to restart the system. After removing the driver, A64info worked OK (I could start it without a BSOD).
But, need to say that the clock generator doesn`t work on my motherboard - Gigabyte M55Plus-S3G (Nvidia 6100 chipset with integrated graphics; AM2 socket). Since I can`t find anywhere on the internet, which clock generator is used on my MBO, I can not be more helpful
Greetings from Croatia,
Sven
Hi Vuco, earlier A64info-beta seemed working fine on system with AMD dual core optimizer installed.
Interesting. I have DC optimizer installed too (latest version) and it works. When does BSOD occur? Right after start or when you change some parameters? Maybe it is a driver issue. I'll check it out with Audiofreak. Frankly, i don't like DC optimizer because it does something that OS should do . I have had some lockups while runing other apps. Still, I will test it.
Regaridng clockgen support, since I have DFI nF4 Ultra mobo, i have tested it on this mobo. I have searched all over the Internet to find some usefull info about other nV chipsets, but no go. Officially, only nF4 is supported.
Hi lukija, the A64info windows never even shown up as I launched the lastest beta built. The screen became black and I "heard" my OS was shutting down (Little "Doo" sound generated by X-Fi). I don't have any issue with previous beta built. The only things I changed were installed AMD dual core optimizer and replaced my previous graphic card with X1900 XT.
It doesn't seem to have anything to do with dc optimizer. I have the same issue with a Venice E6 3200+, so no dual core. 0.5 works (haven't changed anything yet though) but 0.62 reboots my system. Double-click the icon, screen goes black, no BSOD, just spontaneous reboot.
My board is an Abit AV8 (via k8t800 pro). OS is WinXP SP2
Since I have nothing changed except for new driver, i will check it out. 10x for help.
TiMiN8R, SunFlowerSeeds, Vuco:
You have to help us to fix this crashing.
Right-click on My Computer | Properties | Advanced | Startup and Recovery | Settings then uncheck "Automatically Restart" and click Ok to close both dialogs.
After you have done that, get your digital camera ready and start A64Info.
When it BSODs take a snapshot (please try to make it as sharp/readable as possible) and attach it here so I can have a look at it.
Alternative is to carefully write down the error message (make sure not to confuse B and 8, O and 0 etc) to the piece of paper and then retype it here when you restart your computer.
Sure. I will try to do it this weekend.
My computer doesn't automatically restart, unchecking that option is one of the first things I do after a new install. Like I said in my previous post: no BSOD, just reboot. I understand you guys would like to see a blue screen as it could give you some clues but, at least in my case, there is none! Maybe that in itself could provide some clues? I was guessing maybe it was some other software issue. First time I tried to run it I was running sp2004, speedfan, winamp, firefox. So I figured it didn't cut it. After reboot tried again, only speedfan was running. Same thing, as with no speedfan. Maybe it could have something to do with the uGuru chip/software provided with my mobo? It has low-level hardware access, could be screwing up your drivers?
Sweet program enabled me to O\c my Sempron an extra 200 Mhz's
Sweet!!!!
Now here`s a funny situation.
As audiofreak said that we should post a pic of the BSOD, I went to re-install the (same) AMD Optimizer driver like before. Prepared my camera, restarted the computer, started A64Info and it worked fine (I mean it worked, bu i still can`t use the clock generator :p) !?
Last time, I got the BSOD right after starting A64info.:confused:
Didn`t change anything on my computer, or installed anything (except optimizer driver of course). Just like before...
Now I`m confused.
Then something really bad must be happening when Windows doesn't catch it.Quote:
Originally Posted by TiMiN8R
Sure that is an option. First thing I would try would be running A64Info without any other programs including SpeedFan.Quote:
Originally Posted by TiMiN8R
I would also try running the system at default speed, that is with no O/C just to see if it still happens.
We have few relatively small changes. First, we now enable load driver priviledge in 32-bit OS-es too and second, latest WDK was used to compile the driver so even compiler bugs are not excluded for now.Quote:
Originally Posted by TiMiN8R
Are you using 32-bit or 64-bit OS? At least that will narrow down the search because 64-bit driver hasn't changed except for recompiling.
EDIT:
Please check event log, reboot may be logged as machine check exception.
I am confused too. Have you by any chance did some steps in different order?Quote:
Originally Posted by Vuco
Haven`t changed a thing.Quote:
Originally Posted by audiofreak
I had optimizer installed on my sistem for a week or two before I read sunflower`s post, so i decided to test it on my rig. Started the A64info, got a BSOD (now I`m angry on myself for not writing the error). Uninstalled the optimizer, started again the A64info and it worked like a charm. Then I posted my first post here...
And now, I can`t get it BSOD again :D
Damn...
Ok just like Vuco case, the beta just work without shutdown. :confused: I tested it with the dual core optimizer installed. lol I even get ready a paper and pen in order to copy down the error code.
The only things that was changed is I have updated from ATI Cat 6.11 to Cat 6.12.
I have an Opteron 165 & AT8-32X and my bios is capable of much more than 1.40 vcore. So why does A64Info limit me to 1.400v max? Am I doing something wrong?
csimon, I have the same issue with all the versions on my Expert board.
No BSOD here with either versions and dualcore optimizer + dualcore winxp hotfix + amd x2 drivers.
its the best tool for cpu/ram/mobo ive ever had.
still some bugs (vcore) but nice work
Vcore - i never knew you could change volts with this proggie, What version is that feature in?Quote:
Originally Posted by prinzomat
thats in the beta version 0.62 I think.Quote:
Originally Posted by Neo2Neo
However Im not sure this is a safe way to go, any thought from the maker would be appreciated!
Quote:
Originally Posted by v0dka
Might try it out would love to give my ram more volts, max my mobo will give is 2.8.... booo