Mon windows 2000 ne veut pas marcher mais ce coup si je c pourquoi ! c un probleme avec la carte son !
alors j'ai etait chercher un FAQ chez via et je pense que je l'ai trouvé mais je suis nul en anglais et je comprend pas !! ;(
alors si kk1 peut m'aider je met le FAQ sur cette page...
 
FAQ :
 
My sound card causes my system to hang, or screams on start-up
Some users report the above problem and find that selecting "15M-16M" for the Memory Hole in the Advanced Chipset Features page of the BIOS solves this problem. Note that this problem is frequently reported with the Soundblaster PCI128 and Soundblaster Live! Value cards. Under Linux you will need to also modify a configuration file - see BIOS section.  Do not enable this option unless you actually experience problems - for some users this setting actually causes instabilities!
 
Another common cause for this problem is the Soundblaster Emulation feature of many makes of soundcard. This mode emulates an ISA SB16 card, which is unable to share IRQs or DMA with other cards. See "Why does my computer hang when my sound card initialises SB16 emulation on my KT7-RAID?" below.
 
Other solutions
 
Most people with problems seem to have greatest success if they put their soundcard in PCI Slot 4.  Remember to enable Reset Configuration Data in the PnP/PCI Configuration page of the BIOS after moving your card.
 
One user, whose system hang whilst playing sound during a game, eventually traced the fault to the use of the ATA/66 80-way IDE cable supplied by Abit with the motherboard.  He had it connected to a Plextor IDE CDR - which worked perfectly.  On using an older ATA/33 cable the problem was resolved.  This solution may be related to the apparent problems the VIA 686B Southbridge has with bus mastering (see here).
 
How can I make my system stable with a Soundblaster Live! card?
On my system I have a Soundblaster 1024 Live! Player card installed under Windows Me, with ACPI enabled, Liveware 3.0! and default voltages, without a single problem!  The faults are therefore intermittent and likely due to a particular combination of cards.
 
The most common cause of difficulty is the SB16 emulation that the drivers seem to automatically install.  This emulates an old ISA driver, which cannot share resources, and thus causes your system to hang when another device unwittingly shares.  See "Why does my computer hang when my sound card initializes SB16 emulation on my KT7-RAID?" below.
 
Also check out the unofficial Creative Labs Product FAQ.
 
Other stability solutions
 
People struggling with exception messages and/or page faults involving devcon32.dll and msgsrv32.exe, under Windows 9x, have found that these can be resolved by replacing the devcon32.dll with an older version 4.06.642 or earlier solves these problems.  One user has placed the file at http://home.kc.rr.com/macjohn/DEVCON32.DLL and another at ftp://ftp.dq.com/special/devcon32.zip.
 
Problems with system crashes during heavy disk activity are due to an acknowledged problem with PCI latency on the VIA 686B Southbridge controller, and can be fixed using BIOS release ZTB01 and later.  See the BIOS page.
 
One user with problems with a Soundblaster card reported that lowering the I/O voltage a notch solved his frequent lock-ups.  This solution only seemed to apply to earlier drivers supplied with the card - the latest drivers work at 3.3v without difficulty.  Others have fixed this problem by ensuring no disks are on the Highpoint Secondary controller.
 
Several users have reported that the CPU core voltage reported in the BIOS or with the VIA Hardware Monitor is approximately 0.05v higher than the correct value.  They have found that by lowering this by the appropriate amount to make the reported CPU core voltage match the CPU's rated voltage, instabilities with Soundblaster cards are resolved.
 
A number of users with Soundblaster problems have found that installing Windows 9x without ACPI support (use "setup /p i" ) and without installing the Liveware! 3.0 drivers resolves instabilities.
 
Under Windows 2000, one user noted in an email to me that the WDM drivers supplied with Windows 2000 are considerably older than the latest drivers available at Creative's website.  He found that after downloading and installing the lw3drv.exe liveware drivers from http://www.soundblaster.com/drivers/ his system became completely stable.
 
Liveware can be the cause of stability problems.  One user reported complete stability by obtaining LiveService - a utility that runs LiveWare as a service under Windows 2000.
 
One user reports that upgrading to Microsoft DirectX 8 solves crackling and popping problems.
 
Solving Soundblaster crackling problems
 
This can often be fixed by using BIOS ZTB01 (see BIOS page) and later and disabling Delay Transaction and PCI master Read Caching and setting PCI master time-out to 0, in Advanced Chipset Features.
 
One user with Windows 2000 found that by adding the following keys to the registry under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\BIOS then crackling problems were resolved: PCIConcur = 1 (enabled), FastDRAM = 1 (enabled), AGPConcur = 1 (enabled) [if your video controller is AGP based].  These settings speed up hardware specific operations by allowing installed devices to use extra CPU cycles: PCI, AGP and/or DRAM based I/O transfers from the motherboard interface/bus/bridge (PCI, AGP, DRAM) to the CPU, and the other way around.
 
Disabling UDMA modes for disk drives in the BIOS solves stutters and crackles, at the expense of reduced disk performance (20% or so lower).  This is because bus mastering can prevent the sound card from gaining access to the PCI bus.
 
One user with crackling problems with his Soundblaster, particularly when the CPU was under heavy load (e.g. when running SETI@home) found that upgrading his memory to PC133 and thus setting the memory bus at HOST+PCICLK solved all crackling problems.
 
One user found that by enabling 'enhanced chipset performance' in SoftMenuIII of the BIOS the crackling could be removed.  
 
One user with crackling problems found that by setting all ATAPI devices (eg. CDROM, CDRW and DVD) in the BIOS as None rather than Auto resolved crackling problems.
 
Users with crackling problems and the Soundblaster Live! series of cards have reported that BIOS release WZ resolves this problem.
 
My Aureal Vortex2 card crackles, pops and hangs on my KT7. Why?
Users have reported success using driver version 4.06.2048 available from www.vortexofsound.com.
 
Why does my A3D/Aureal sound card keep crashing my computer under heavy activity?
Many users report success using driver version 4.06.2048 available from www.vortexofsound.com.
 
The following problem was noted for VIA KX133 chipset motherboards before the KT133 chipset was released. The KT7 motherboard uses the VIA KT133 chipset which is very similar to the KX133 chipset. The following comments therefore apply to the KT7 and KT7-RAID motherboards.
 
For audio cards that use A3D audio chip there appears to be an incompatibility that causes the KX133 system to deadlock when system traffic is heavy. The reason for this is that the A3D chip issues one memory read request cycle to the North Bridge and expects a grant within 4 mico-sec of latency time. If PCI TRDY# is not asserted after 4 mico-sec, the A3D hardware will de-assert the FRAME# and REQ# to terminate the operation. However, the A3D audio software driver cannot acknowledge the termination and continues waiting for hardware response. Hence the system hangs. This issue will only occur during heavy system traffic when the North Bridge cannot grant access to A3D audio chip within the 4 mico-sec latency time. There is no known work-around for this issue, and the principal advice is not to use A3D-based sound cards with KX133 based motherboards. Source: VIA Application note Serial #AN137 Date 07/05/00. This information found at BrokenPixel.
 
Another possible solution may be to reduce the sound quality setting in games to reduce the load on the Northbridge.
 
Another user found that disabling "geometric reverb" in the Control Panel under Aureal settings solved this problem.
 
Why does my computer hang when my sound card initialises SB16 emulation on my KT7-RAID?
This has been reported on a number of sound cards including the Diamond Monster MX300 and the Soundblaster family of cards. It is due to a conflict between the legacy SB16 emulation (which allows your soundcard to function under old DOS-only games) and the Highpoint controller provided on the KT7-RAID card. The SB16 was an ISA card, incapable of sharing its IRQ or DMA, and hence the problem.
 
Installation if the RAID controller is not in use
 
The following installation sequence can solve this problem:
 
Disable Highpoint controller  
Install sound card software  
Re-enable Highpoint controller  
This will leave your system with both SB16 and the Highpoint controller functional.
 
Also note that Aureal provide advice on permanently disabling SB16 emulation before installing the drivers.  One user reports that with the Aureal drivers 2048 for Win9x, by commenting out the line "HKR,Config,DisableSBFMIRQSharing,1,1" with a semicolon, in the file au30mmed.inf the card can happily run SB16 emulation and use the RAID controller.
 
Disabling or removing SB16 Emulation
 
If this doesn't work, and you don't plan to play old DOS games on your system you can always disable SB16 emulation. You can also achieve at the time you install the soundcard drivers by doing a custom or advanced install and deselecting "SB16 emulation". If you have already installed your soundcard drivers, then how to disable SB16 emulation will vary from soundcard to soundcard. It will probably require you to boot into Safe Mode and then remove any mention of your soundcard from the AUTOEXEC.BAT and CONFIG.SYS files, and also to "uncheck" any option marked "SB16 emulation" under your sound card's driver in My Computer-Properties-Device Manager.
 
Although it is easy to disable the SB16 emulation in the Device Manager, it can be harder to remove it completely, as Windows seems to insist on reinstalling it next time you reboot.  The following procedure will allow you to remove SB16 emulation from your Device Manage once and for all.
 
Under the System tab in Control Panel, choose Hardware Profiles.  There, choose copy, and name the profile "temp"  
Disable SB16 Emulation in the Device Manager.  Reboot your machine and select the new hardware profile "temp" when prompted.  It is an exact copy of the original so everything will run fine.  Disable SB16 Emulation here also.  Then uncheck the box that says "Exists in all hardware profiles".  
Reboot and choose original configuration for hardware profiles and make sure the settings of "disabled" are the same.  
Reboot and choose your new hardware profile "temp" and here Delete SB Live emulation.  A box will appear asking "remove from which hardware profile" and you should choose "original configuration".  
Reboot and choose "original configuration" and verify SB16 Emulation is gone.  If so, go to the hardware profile Tab and delete your second hardware profile.  
Now SB16 emulation does not appear anywhere in your tree.  It is not using any resources, has no conflicts, and cannot be seen.  
One user reported a less subtle approach - simply rename the file devldr16.exe (do a search for it!) and then SB16 cannot be loaded.
 
Using SB16 and the Highpoint Controller
 
Alternatively, if you wish have both SB16 emulation and the Highpoint controller active, you can solve this problem by reserving the IRQ and DMA assigned to the soundcard as "legacy" in the PnP/PCI settings of the BIOS. This prevents the IRQ and DMA being made available to the Plug-and-Play system, and hence stops them being assigned to the Highpoint Controller. This is important as legacy IRQ's cannot be shared with other devices, unlike the IRQ's used by PCI2.1 devices. You can probably determine which IRQ/DMA has been assigned to the sound card by, again, booting into Safe Mode and then looking in the AUTOEXEC.BAT and CONFIG.SYS files, or at the sound card driver in Device Manager in Windows. This way you can have SB16 emulation and the Highpoint controller - but you tie up an IRQ.  You may therefore prefer to go to "settings" in "Creative SB16 Emulation Properties" (Found in the Device Manager).  Going into this tab, at the bottom is an "Advanced Setting"  checkmark it to "Allow LPT Interrupt Sharing".  This will change the IRQ SB16 Emulation uses to IRQ7, which should resolve the IRQ issue.
 
How do I disable SB16 emulation on the MX300 soundcard to prevent the BSOD on installation?
Comment OUT the Lines By SST in au30mmed.inf in version 9x2048_full.  This has been reported as working fine on the KT7A-raid and on KT7-raid, but may need further testing.
 
[AspenOverides.Addreg]
; virtual devices
;HKR,Config,DisableJoystick,1,1
;HKR,Config,DisableMPU401,1,1
;HKR,Config,DisableDOSModemPort,1,1
;HKR,Config,DisableSBFM,1,1
;HKR,Config,DisableRealModeLegacySBFM,1,1 By SST
;HKR,Config,DisableRealModeLegacySBFMUsingREM,1,1 By SST
;HKR,Config,DisableSBFMIRQLevel,1,1 By SST
;HKR,Config,DisableSBFMIRQSharing,1,1 By SST
;HKR,Config,DisableBusDetection,1,1
; a3d
;HKR,Config,EnableA3DReserve,1,1
;HKR,Config,NumHost3DBuffers,1,6
 
Why does my MX300 card not work after going into sleep mode?
One user writes that this problem can be fixed by disabling and then re-enabling the sound card driver in Device Manager under System Properties.
 
Why do I get TBS Montego PCI error: 0x1009?
 
This error is caused by an unsolvable problem between the Turtle Beach Montego soundcard and the VIA KT133 chipset.  Turtle Beach recommend buying the Montego II card to solve this problem.  
 
Why do I get noise or crackle with the Soundblaster AWE32 ISA sound card?
This may be fixed by using BIOS ZTB01 (see BIOS page) and later and disabling Delay Transaction and PCI master Read Caching and setting PCI master time-out to 0, in Advanced Chipset Features.  
 
One user reports that this can be fixed by overclocking the front side bus (FSB) using SoftMenuIII in the BIOS.  Alternatively this problem can be fixed by disabling the 16-bit DMA support from the sound card's driver.  Note, however, this will disable the full duplex capabilities of the card.  To do this, do the following:  
 
Go to Control Panel, System, Device Manager and select the soundcard.  
Go to the "Properties" of the soundcard, then move to the "Resources" tab.  
Uncheck the "Use automatic settings" box if it's checked.  The information we want to play around with is in the "Settings based on" dialogue box.  
There are a number of "basic configuration" choices ranging from 1 - 7.  At the moment there will be one "Interrupt Request", and two "Direct Memory Access" values in the list box below.  They will probably be 5, 1, 5 respectively.  The idea is to get rid of the 2nd DMA (16-bit DMA) so you
only have the IRQ (1), and one DMA (8-bit DMA).  So try out all of the "basic configuration" options and the information about the IRQs and DMAs will change.  Choose one where there is only one DMA, and try it out.  There could be more than one, so try them out until the problem is fixed.  
Another user had limited success with the above solution, but found that by disabling DMA on the disks the crackling problem was solved - at the expense of much reduced disk performance.  Your choice!
 
Another user reported that setting his card to "Basic Configuration 004" solved the problem.  This is likely to be configuration dependent - but it's worth trying the different configurations offered.
 
Why do I get crackling with my SB16/PnP card?
You need to disable 16-bit DMA support as described in "Why do I get noise or crackle with the Soundblaster AWE32 ISA sound card?" above.
 
Why doesn't my Yamaha DS2416 Audio Mixing Card work with the KT7-RAID?
This is because the card tries to use the same IRQ as the Highpoint HPT370 controller, and is unable to share.  This can be overcome by editing the ds2416.inf file for the driver before installation, removing any reference in the file from the IRQ used by the Highpoint controller.
 
Why does my Soundblaster AWE64 soundcard not work?
Some people have reported that after working fine for a while, the card suddenly stops working, and may report the message "The BIOS of this device is incorrectly reporting the resources for this device. Try getting an updated BIOS from your system manufacturer. Error code (9)."  For some reason the BIOS update for this problem can only be found on the Dell site.  Do the following:
 
go to http://support.dell.com/filelib  
search for aweflsh.exe and download the file  
Running AWE64Flsh.exe will create a diskette with the flashing utility and
an upgrade of the AWE drivers for Windows 95.  Follow the instructions
regarding the flashing of the AWE-64 card, but do not use the drivers
included, because they are old (release 12). Download the latest drivers (sbw9xup.exe) from the Creative Labs web site, http://www.creativehelp.com/files/ [...] rod=awe_64  
 
When Windows starts, if MSGSRV32.EXE crashes in SB16SND.DRV, you still have problems. You can follow Creative Labs advice:  suppress all AWE entries in Peripherals Manager  
 
 create a C:\REMOVESB.BAT file containing:
CD \WINDOWS\SYSTEM
DEL SB*.*
DEL WFM*.*
DEL CIF*.*
DEL CSPMAN.DLL
DEL SYNTHGM.SBK
CD ..
DEL AWE*.*
REM ^ (for AWE cards only)
CD INF
REN SB16AWE.INF SB16AWE.CLI
REN *.BIN *.CLI  
 
 reboot and go in DOS mode  
 
 execute C:\REMOVESB.BAT  
 
 reboot  
 
 
 
When Windows detects the AWE-64 card, indicate the directory where you
extracted files from sbw9xup.exe.  
 
If you still have problems: reboot and go into BIOS Settings. Set "P&P OS" to No. Reboot.  
 
This program resets the AWE-EEPROM (it says for model ct4520, but it works with the ct4390 and ct4550 as well.  
 
Why do I get crackling with my Diamond M80 sound card?
This may be fixed by using BIOS ZTB01 (see BIOS page) and later and disabling Delay Transaction and PCI master Read Caching and setting PCI master time-out to 0, in Advanced Chipset Features.
 
One user found this problem can be solved by placing the card in PCI Slot 1, to share its IRQ with the AGP card.
 
Why do I get crackling and distortion using the APS drivers?
This may be fixed by using BIOS ZTB01 (see BIOS page) and later and disabling Delay Transaction and PCI master Read Caching and setting PCI master time-out to 0, in Advanced Chipset Features.
 
Users of professional sound cards that use the APS ASIO soundcard drivers (or Soundblaster users that are using these instead of the Creative Labs drivers) may experience popping, clicking and distortion, particularly when used in conjunction with the Cubase VST card.  A partial cure for this is to simply deactivate all of the audio inputs of the APS card. To do this in Cubase5 use, 'panels - vst inputs', in Cubase 3.7 'system - vst inputs'.  For more details of the APS and ASIO drivers see Live! Centre.