Asus M4a79 deluxe up close and personal

Printable View

Show 100 post(s) from this thread on one page

03-05-2009, 04:38 PM
mattkosem

1 Attachment(s)

3.72 seems to be no trouble. It passes 10 iterations of linpak without any trouble. Anything 3.8 and over seems to crash with any moderate load on this chip(unless I leave core 3 at a lower clock). I'm hoping to get somewhere in between where I am now and 3.8 to be stable with some more tweaking or, if nothing else, I hope to get a little more NB speed.. I don't much care for OCCT's interface or waiting periods, so I dropped the occt linpak into LinX for testing. Temps top out at 42C after 2 or 3 iterations and don't increase from there.

--Matt
03-05-2009, 06:05 PM
FoxRacR17

I am running into a problem. I am trying to get my mobo setup and ready for my new x25-m, so I reinstalled vista x64 on my F1 1TB hdd with AHCI enabled in the mobo bios. Then once it was installed I went on to install all the drivers and such and no matter what drivers i install there is always a unknown device in device manager. I have installed 9.2 catalyst, the 9.2 for SB750, and 9.2 of the AHCI Raid drivers, but that unknown device is still there. Can anyone help me out please?
03-05-2009, 06:26 PM
chew*

Uninstall realtek and disable it.......Then rebbot and let you computer find the other driver that is unknown off the installation CD....I'm preety sure the file it wants is hdaudiobus.sys.

I had this issue in vista before I had to drop thefile in the drivers.bin file for windows before it found it.....I think IIRC I had to rename the file .sys as well.
03-05-2009, 06:50 PM
FoxRacR17

Thanks for trying to help out chew* but it was still a no go. I uninstalled the "high definition audio device" under device manager, then rebooted, and I told vista to look for the unknown devices driver under the cd that came with the mobo and it didnt find it. I then searched for the cd for "hdaudiobus.sys" and I couldnt find anything on the cd. Any other ideas cause this is driving me crazy. It says the device is "on PCI standard ISA bridge" if thats any help?
03-05-2009, 07:01 PM
chew*

Yah the file is not called hdaudiobus.sys I had to rename it look at the file size in the screenshot and you will know which file it is ;) .....It's in the realtek drivers in the WDM folder......sometimes it can be found in ati's WDM folder as well.....You may have to remove folder and file restrictions to see it.....It will not install if any realtek drivers are installed and it will only install at startup, if it doesn't find the driver the first time it will not allow you to install it untill you reboot again.

http://members.cox.net/bostonreefer3/hdaudio.JPG
03-05-2009, 08:05 PM
FoxRacR17

I really appreciate you helpin me out chew* but so far its not working. I downloaded the audio drive .zip from the asus website, looked inside the wdm folder and renamed rtkhdaud.sys to hdaudiobus.sys. Then I disabled the unidentified device and then uninstalled it through device manager, rebooted, and when it started up it asked to look for the driver, i told it to look where the hdaudiobus.sys was, and it still didnt like it. One thing i noticed is that it says for "hardwar Id: ACPI\PNP0700"
03-05-2009, 08:13 PM
chew*

Yah pointing it to it doesn't work in vista unless it in vistas driver bin.:shrug: gotta put it there yourself.

Have i mentioned I love vista :rolleyes:
03-05-2009, 08:15 PM
FoxRacR17

could you elaborate on what you mean "driver bin"? I dont have any experience with that.
03-05-2009, 08:16 PM
chew*

hmm let me hook up my vista drive and see if I can find the location I stuck it in.

I stuck both hdaudibus.inf and hdaudiobus.sys in this folder, not really good at explaining this stuff so heres a shot of vista/windows/system32/driverstore/filerepository

http://members.cox.net/bostonreefer3/hdaudio.jpg
03-05-2009, 08:51 PM
FoxRacR17

which file did you rename to hdaudiobus.inf? I tried renaming hdart.inf to hdaudiobus.inf, and then stuck both hdaudiobus.inf and hdaudiobus.sys into that filerepository folder, restarted windows, and it did that look for driver thing, but it still didnt find anything :confused:
03-05-2009, 08:59 PM
chew*

depends on the particular driver.

the one on the left first above screenshot for vista 32 would be RTKHDAUD.sys If its that type of driver, I would drop that and a clone named hdaudiobus.sys in that folder.

same file is in the other driver foldr on the right.....same thing...depends on if your 32bit or 64 bit which file you use.
03-05-2009, 09:09 PM
FoxRacR17

ok so i'm on vista x64, so then I should rename "RTKHDA64.SYS" to "hdaudiobus.INF" and then make another copy named "hdaudiobus.SYS" and put both in the the filerepository folder?
03-05-2009, 09:14 PM
chew*

Quote:

Originally Posted by FoxRacR17

ok so i'm on vista x64, so then I should rename "RTKHDA64.SYS" to "hdaudiobus.INF" and then make another copy named "hdaudiobus.SYS" and put both in the the filerepository folder?

yah drop the original and those 2, it won't hurt anything....
03-05-2009, 09:23 PM
FoxRacR17

ok, i have no idea what i'm doing wrong but windows still will not find the drivers, i made two copies of RTKHDA64.SYS, renamed one to hdaudiobus.inf and the other to hdaudiobus.sys, put all three in the root of the filerespository folder, and restarted, but windows still didnt want to find the driver and asked me to look online and stuff.:confused:
03-05-2009, 11:23 PM
mattkosem

1 Attachment(s)

I was troubleshooting some issues that I was having with high NB clocks on this board and found that having CnQ enabled causes Vista x64 to BSOD on boot if the NB frequency is at, around, or over 2600mhz. Disabling CnQ avoids the issue completely. I can set the NB multiplier that I wish, bump the ref frequency up in overdrive and attain the same NB clock with it enabled but cannot boot with it on. It's pretty strange, since I can boot right up at over 2800nb no problem without it. That's a pretty substantial difference! It really sucks though, since c1e and cnq knock an easy 60w off of the system's power consumption at idle. :-/

--Matt
03-05-2009, 11:45 PM
FoxRacR17

well now I have complete disabled the onboard audio within the bios, and tried reinstalling vista again, and after install all drivers (minus audio drivers) there is still that unknown device. I think its releated to ACPI because when I open up the system information under catalyst, and select "problem devices" it says "ACPI\PNP0700\4&CB4DC81&0" How come I am having trouble with this all of a sudden, i'm pretty sure that when I first installed vista everything was good and i have no unknown devices. Is anyone else having this problem?
03-06-2009, 01:08 AM
Lathode

Quote:

Originally Posted by FoxRacR17

well now I have complete disabled the onboard audio within the bios, and tried reinstalling vista again, and after install all drivers (minus audio drivers) there is still that unknown device. I think its releated to ACPI because when I open up the system information under catalyst, and select "problem devices" it says "ACPI\PNP0700\4&CB4DC81&0" How come I am having trouble with this all of a sudden, i'm pretty sure that when I first installed vista everything was good and i have no unknown devices. Is anyone else having this problem?

Did you run Windows update? Do you have ATK0110 ACPI UTILITY listed under System devices in device manager?
03-06-2009, 01:13 AM
FoxRacR17

I did update windows fully, and I do have ATK0110 listed under system devices.
03-06-2009, 01:33 AM
Lathode

Well here's my device manager:

http://home.comcast.net/~lathode/tal...ce_manager.jpg
03-06-2009, 05:04 AM
chew*

Quote:

Originally Posted by mattkosem

I was troubleshooting some issues that I was having with high NB clocks on this board and found that having CnQ enabled causes Vista x64 to BSOD on boot if the NB frequency is at, around, or over 2600mhz. Disabling CnQ avoids the issue completely. I can set the NB multiplier that I wish, bump the ref frequency up in overdrive and attain the same NB clock with it enabled but cannot boot with it on. It's pretty strange, since I can boot right up at over 2800nb no problem without it. That's a pretty substantial difference! It really sucks though, since c1e and cnq knock an easy 60w off of the system's power consumption at idle. :-/

--Matt

yep matt theres is a long list of stuff you must disable to get the most out of the cpu.....

C1E, C&Q, spread spectrum.....when you really want to hammer it which I usually reserve for cracking records you turn EVERYTHING off...USB,NIC,Sound, anything onboard except the ps2 ports....I don't notice much if any in gains but I have killed a few onboard nics when pushing the system to its limits if left enabled.
03-06-2009, 08:37 AM
mattkosem

Quote:

Originally Posted by chew*

yep matt theres is a long list of stuff you must disable to get the most out of the cpu.....

C1E, C&Q, spread spectrum.....when you really want to hammer it which I usually reserve for cracking records you turn EVERYTHING off...USB,NIC,Sound, anything onboard except the ps2 ports....I don't notice much if any in gains but I have killed a few onboard nics when pushing the system to its limits if left enabled.

That really sucks, since the NB speed makes such a huge difference. I didn't have this problem on the M3A78-T that I had before this. I guess that settign can only be pushed for benching sessions and heavy gaming sessions. There's no way I'm going to leave my computer drawing 210w at idle 24/7 when backing the speed off a little makes it draw only 130.

--Matt
03-06-2009, 09:40 AM
bingo13

Quote:

Originally Posted by FoxRacR17

I did update windows fully, and I do have ATK0110 listed under system devices.

You need to turn off the floppy drive controller in the BIOS, unless you have one installed, if so, the cable might be reversed or the device is really old. Your PNP string of 0700 is for the floppy drive controller on this board, at least on mine it is. ;)

The 0700 string is part of a series of strings (0303 is for PS/2 keyboards, etc) for Legacy ISA Devices within ACPI and usually this device message pops up when the device is not attached but activated in the BIOS or is attached but the device is not PnP aware (usually older keyboards, floppy drives, serial devices from several years back). Oddly, the device will normally work just fine, even with the error message.

Vista 64 SP1 actually increased the number of legacy devices that would be recognized properly, of course, if you are not on SP1, there is no real reason to be running Vista. :D
03-07-2009, 03:18 PM
FoxRacR17

Thanks for the reply bingo13, I ended up figuring it out that night. I already had disabled the floppy drive in the bios, and I was using a copy of my vista ultimate that I made with vlite, and in vlite I told it to remove the floppy disk drivers since I never use a floppy and it was disabled in the bios. So I dont know why it was showing up when it was disabled in the bios. I made another copy using vlite and made sure that I left the floppy disk drivers in and reinstalled and everything is good now. And thanks again for trying to help me out the other night chew*
03-07-2009, 03:40 PM
chew*

Quote:

Originally Posted by FoxRacR17

Thanks for the reply bingo13, I ended up figuring it out that night. I already had disabled the floppy drive in the bios, and I was using a copy of my vista ultimate that I made with vlite, and in vlite I told it to remove the floppy disk drivers since I never use a floppy and it was disabled in the bios. So I dont know why it was showing up when it was disabled in the bios. I made another copy using vlite and made sure that I left the floppy disk drivers in and reinstalled and everything is good now. And thanks again for trying to help me out the other night chew*

Np man wish I had been able to help.....guess it wasn't the audio driver that beat me up for a few hours.
03-08-2009, 07:37 AM
Jethro

Current settings: 3.4 @ 1.47v (235x14.5) 940mhz cas 4 4 4 12 HT 2115 NB 2350 Pretty happy with everything except NB clocks. Any suggestions? NBv= 1.28 atm, CPU NBv @ auto HTv @ 1.24

Show 100 post(s) from this thread on one page

All times are GMT -8. The time now is 11:57 PM.

XtremeSystems