Cool! Gives me faith that I should be able to get mine patched up later today too!

Thanks!

-mr moon

Gigabyte also personally issued me a fix for my P35-DS4 board: BIOS version F13b. I understand the "b" is beta, and not an official version. Just to recap, I have the GA-P35-DS4 revision 2.1 with an Intel Q9450 2.66GHz Yorkfield CPU.

Their words:

"Attached special bios is modified to support Q9450 and also keeping bios codes from F5 bios to avoid DPC issue."

So it's similar to what they've given others.

I've just emailed Gigabyte back to see if the new F13beta BIOS version is a universal update for all Intel Q9xxx and Q6xxx CPU users, but I suspect it's just version F5 with Q9xxx support.

But for now I've zipped and uploaded it for any other P35-DS4 users with specifically the Q9450.

http://www.gobo.dsl.pipex.com/data/Gigabyte_GA-P35-DS4_BIOS_Version_F13b.zip

To use: extract to a floppy, reboot, and then flash the BIOS during the usual initial POST sequence (I had to hold down "End" to access the BIOS flash menu).

Benchmarks. This is my previous XP 32-bit BIOS version F12:-



New XP 32-bit BIOS version F13b:



Anything from 4 microseconds to 22 at idle. I get an occasion lone spike at 129 microseconds every 15 seconds or so. But the average toggles between 5 and 12 microseconds.

I used a hard-wired PS/2 mouse for the above screengrab. My Microsoft wireless optical mouse was taking the latencies anything up to 42 microseconds whenever I moved it, but switching to a hardwired PS/2 mouse cut these latencies by half.

Now on to Vista-64...

This is what I was getting using BIOS F12 in Vista64 after a clean install (with chipset and graphics drivers only. I haven't updated Vista-64 via Microsoft Update yet, because Vista wont "see" my ruddy USB Modem even though the modem has genuine 64-bit drivers! Gah!):



... basically a mirror image of what was seen in XP-32.

Opening a few windows sent it wappy, though:



Now Vista64 with new BIOS version F13b:-

When it's all settled down (there's absolutely loads of spikes when the OS has first loaded up), and without optimising anything other than disabling ethernet, I get average of 59 microseconds. It oscillates tightly between 57 and 60 microseconds, apart from random spikes (anything up to 5000 microseconds):



Disabling Aero barely affected the values. However I went the whole hog and disabled ALL fancy frills, setting processor scheduling to Background services, etc., but then...

.. Disabling my Samsung SH-S203P DVD-RW drive (via Device Manager) took the average down to 29 microseconds:



Still get spikes when changing windows and stuff, though:



... these can be anything up to 5000 microseconds, as mentioned, and can last a second or two.

But still pretty surprised Vista got down that far, on the whole. I haven't even updated it yet, or installed SP1, etc.

All my tests/screegrabs were when the systems (XP-32 and Vista-64) were IDLE. I don't have any projects to test it as yet, as up until now I've generally been more hardware based, with a little bit of software. I can now work to integrating all my hardware with my computer, and get my hands more dirty with the software side of things.

Just read Mr. Moon's post about genuine URLs, fair enough. Wasn't sure about disclosing their URL to others, but given the issue here was my direct link to the P35-DS4 BIOS F13b for Q9450: http://ggts.gigabyte.com.tw/FileList/594495/p35ds4.13b

If you want to execute it standalone you'll need to pair it up with the Flash895.exe and the autoexec.bat files on floppy disk.

Wow. Indeed seems like good news. I would be very curious to hear about real world results...with old bios vs new bios in terms of track counts, plugin counts, audio dropouts, audio latency, etc..using the new bios with low DPC latencies....or the old one that we've been discussing.

Also, anyone know if this 13b bios can be used with a rev2.0 version of the DS4 mobo? guess I will have to log my own support ticket with Gigabyte about it and wait for my own private fix. You'd think they would just release a new bios with this stuff fixed, but its pretty impressive they are willing to send you a special patched BIOS.

I went here and submitted the request.

It's a self-explanatory site where you slect your config and can enter text about your request.

ORIGINAL: dewdman42

Wow. Indeed seems like good news. I would be very curious to hear about real world results...with old bios vs new bios in terms of track counts, plugin counts, audio dropouts, audio latency, etc..using the new bios with low DPC latencies....or the old one that we've been discussing.

Also, anyone know if this 13b bios can be used with a rev2.0 version of the DS4 mobo? guess I will have to log my own support ticket with Gigabyte about it and wait for my own private fix. You'd think they would just release a new bios with this stuff fixed, but its pretty impressive they are willing to send you a special patched BIOS.

Hey dewd, I imagine it would be fully compatible with mobo revision 2.0, although you can always check with Gigabyte. However, I'd bet that the different revisions of the mobos would probably refer to slightly different mechanical hardware aspects on the motherboard itself, such as slightly tweaked heatsinks, or whatever, rather than intricate changes to the actual computing system itself, but I guess it's best to be sure.

You could always download the F12 versions for both 2.0 and 2.1 from Gigabyte's site, and use a free duplicate file finder to see if they are identical (using an accurate byte-per-byte check), or at least were created at the same time and same filename/size. If they are, then you'll be able to use the current F13b fix. I use Brook Younce Software's free "Duplicate File Finder" utility to compare duplicate files: http://www.snapfiles.com/get/dupfilefinder.html

EDIT: Have just downloaded 2.0 and 2.1 versions of F12 BIOS and run a quick byte-by-byte comparison test for you, and they're both identical, so my P35-DS4 F13b should work for revision 2.0 too.

ORIGINAL: Dan DAmico

BTW, I had no errors in MemTest86.

Great stuff!

ORIGINAL: HighestOlive
If someone has to contact that how specific about the problem would we have to be. Would it be as simple as saying the GA-P35-DS3L is expiriecing DPC spiking issues the same as other boards?

Does any one have a copy of their email that the sent to gigabyte we could use as a template to send follow up emails for other boards?

Go here, and raise a ticket: http://www.giga-byte.com/Support/ServiceCenter.aspx

This is what I initially sent, regards the P35-DS4 rev2.1, along with my computer specs:-

I'm a professional musician attempting to use the above computer configuration for high performance music studio recording, but I'm suffering from unduly large and regular Deferred Procedure Call spikes on the machine affecting performance.

I am using the free DPC monitor utility from Thesycon to monitor the system, which you can download here: http://www.thesycon.de/eng/latency_check.shtml

Attached to this post is an average screengrab of the system idling, which clearly displays the spikes. The DPC latencies oscillate wildly between 5 microseconds up to 1500 microseconds.

I have attempted to narrow the suspect down by disabling all non-critical devices such as ethernet/LAN, CD/DVD and Floppy Disk components from within Device Manager, and every non-critical Service, as well as even disabling System.ini and Win.ini at startup, to no avail. I've even gone as far as disabling all USB and IEEE1394 (firewire) devices, and using a PS/2 mouse and keyboard instead, again to no avail.

It occurs even right after a completely clean installation of Windows, before even installing chipset drivers, graphics, etc.

Looking at other public forums, such as Tom's Hardware and the Cakewalk Sonar music sequencer forums it appears I'm not alone:

http://www.tomshardware.co.uk/forum/247210-12-audio-latency-problem-ds3r

and...

http://forum.cakewalk.com/tm.asp?m=1351472&mpage=1&key=

... shows many others with the identical problem with BIOS versions F6 and thereafter.

However, my Intel Q9450 Yorkfield CPU requires BIOS version F9 or above, so downgrading to BIOS version F5 or below is NOT an option for me.

I would much appreciate a response at your very earliest convenience regarding the matter.

Thanks kindly,

Tim Edwards

PS > More details here: http://www.soundonsound.com/forum/showflat.php?Cat=&Board=PCMus&Number=604296&Searchpage=1&Main=588140&Words=+T%EDmo&topic=&Search=true#Post604296

-------------------------------------------------------------------------------
Model Name : GA-P35-DS4(rev. 2.1)
--------------------------
M/B Rev : 2.1
BIOS Ver : F12
Serial No. : SN0745.... etc. etc. etc.
...etc.

Attachment: http://ggts.gigabyte.com.tw/ClientUserFile/OK/594495/DeferredProcedureCallLatenciesOnGigabyteP35DS4.gif

Hope it goes well, HOlive.

And thanks guys! Solidarity amongst fellow musos.

Best regards,

Timo. :)

Tim

Thanks that email is exactly what I wanted to see I didn't know how to best explain the situation to gigabyte. that helps so much.

You guys that are getting the results about 13B, please make sure to give feedback back to Gigabyte so that they will be motivated to make sure this ends up in the next official BIOS release. i'm out of town now, but I intend to try this when i get home. I'm really feeling very good that gigabyte was on top of this issue really so quickly if you think about it.

ORIGINAL: vanceen



Here's what I got on a very similar system:

512 Samples (11.6 ms) - 84 Multichannel Compressors / Save-ReOpen 83 :

256 Samples (5.8 ms) - 67 Multichannel Compressors / Save-ReOpen 65 :

128 Samples (2.9 ms) - 44 multichannel compressors / Save-Reopen 45

064 Samples (1.5 ms) - 21 Multichannel Compressors / Save-ReOpen 21

Your 64 samples looks just about the same as what I got. With the old BIOS, at 64 samples I was able to get 55 multiband compressors with the WDM-KS drivers, but I couldn't even play it without pops and clicks with ASIO. I haven't been able to try the beta BIOS with the WDM drivers yet, but I'll be curious to see the results.

Thank you all for your work on this. Very enlightening. Will keep an eye on this thread. :)

GA-EP35-DS3P here... just tried the F4c bios and the DPC latency values certainly came down (now running ~10us or lower on average.) I wasn't having performance issues at all before, so I don't expect to see any improvement in performance.

Just a note... with the F4c bios, my system will not boot if the onboard LAN is disabled in the bios. You have to make sure it is enabled. I'm not sure if this will be true on other people's systems with DS3P and the F4c bios, but just thought I'd share that in case someone could not get the system to boot. (If you disable the LAN and it won't boot, you have to clear the bios by shorting the clear cmos jumper on the mobo.)

-Clayton

ORIGINAL: Dan DAmico

ORIGINAL: vanceen



I used WDM for these. Haven't tried ASIO.

Hmmm. I wonder why are figures show such a difference, since we have very similar systems and we're both using Delta soundcards. I am using the previous driver version, though. The newest one keeps defaulting to 256 samples everytime I restart Windows, and I found that to be annoying.

I'm using a Delta 66 and an Audiophile 2496 linked together.

Also, the figure of 55 multibands at 64 samples with WDM was with an overclock to 3.0 Ghz (9x333). At stock clock speed I got 37 multibands with WDM. 0 with either overclock or stock with ASIO and the old BIOS.

Yes, but that's still a big difference: 37 compared with 21. You said you got 22 with the 13B BIOS. Have you had a chance to confirm that?

I just ran the test again. At 64 samples, I got 41 (reopen 42) multibands with WDM, 20 (reopen 20) multibands with ASIO, at stock clock speeds. I haven't tried them overclocked yet, but I'll post those results later.

I am using an EP35-DS3R Rev 2.1 Gigabyte Board and my DPC Latency while not Bad isn't great like some of you with the DS4 boards are getting. Anyone know of a way to get my board to perform better? I am finding that I can't run Sonar below 512 Samples Latency setting in my Fireface 800 without clicks when moving the Faders/ It also doesn't make any difference whether the Project is large or small, even Two tracks will cause Clicks when moving the Faders at Anything under 512 Samples.

Do you see any difference when using WDM-KS drivers instead of ASIO drivers? Are you using the new beta Bios? It might make a difference. It made a big difference in ASIO performance on my system.

WDM Drivers are unuseable on my system, tried last night again, hopeless, won't even play back

I have PCI soundcards, and I've never used a firewire interface. Have you evr tried your interface on another system and achieved better results?

No, but these Units are supposedley the best Money can buy in their price range. I doubt the Fireface is faulty. I used to have an RMI 96/8 which was PCI Based and it definately performed better in certain ways, like saving while playing back and rendering while playing back which you cant really do with Firewire.

What bit rate/sample rate are you experiencing pops and clicks with? With my Delta PCI cards I can run anything below 24 bit/96k at 64 samples, the lowest the Delta driver will allow. But if I go to 24/96K, I have to go up to 128 samples.

I am using only 24bit 44.1 I daren't go any higher as that will make the problem worse.