Audio Direct-X issue

J

JuggaloKillaz

New Member
hey guys i bought a creative sound blaster X-FI audio sound card and i went to access Everest Ultimate edition and i was looking to see the cool effects of the sound card from going to onboard to extream audio. I went to the video, music which it was fine but when i went to audio it shut down my PC badly just like unplugging the chord for the PSU. what can i do to fix this? any suggestions?

thanks,
Weezlexx89
 
Have you been running the system since that happened to see if any other problems have been seen? If you didn't receive a bad card it sounds like it or something else was suddenly overloaded! When too much power was drawn for some reason the protection circuit may have kicked in to prevent permanent damage. There are a few things to look at there.
 
im 99.9% sure its the sound card thing. i dont think its damaged cuz it works fine im think there might be something conflicting and also i was told that it doesn't run good of DFI boards. is this true?
 
The problems seen by others running any sound card may have nothing to do with a Sound Blaster but...! SBs are "known" for being power demanding little buggers at times! Why you saw the sudden shutoff is another matter. Even an SB model never slams a system that hard. The combo of Everest and SB? pulling too much? What do you have for a supply there?
 
heres my specs
COOLER MASTER Centurion 5
DFI LANPARTY UT nF4 Ultra-D Socket 939 NVIDIA nForce4 Ultra
AMD Opteron 144 Venus 1.8GHz 1MB L2 Cache Socket 939
Thermaltake TR2 ATX 430W Power Supply 115/230 V
Nvidia Geforce MX 4000 128 MB
CORSAIR One 512MB Stick 184-Pin DDR SDRAM DDR 400 (PC 3200)
Creative Sound Blaster X-Fi Xtreme Audio 7.1 Channels 24-bit 96KHz PCI Interface Sound Card
 
While the make of supply isn't on the "good" list here it should have enough power normally for the average user. The specifications seen at newegg show:
+3.3V=20A, +5V=30A, +12V=18A, -5V=0.5A, -12V=0.8A, +5VSB=2A http://www.newegg.com/Product/Product.asp?Item=N82E16817153023

You can compare those to an Antec supply with:
+3.3V=20A, +5V=20A, +12V1=17A, +12V2=17A, -12V=0.8A, +5VSB=2.5A

I had to substitute the "@" for the "=" to keep those from becoming links! When going to perform the Direct X test you shouldn't have seen that unless one of two things happened namely the supply is unstable or you ended up with a bad card.
 
Not when the system crashed! "Something" pulled a lot of power fast when you ran Everest there to see the system shutdown entirely! If the system simply rebooted it would be possible to look at a Windows/software problem seeing the auto reboot crach control in Windows take over. But a flaky supply or bad card would explain an overload. The shutdown there protected the board and other hardwares.
 
Something caused the shutdown there. Without running Everest how is the system running otherwise? If the leds for power and hard drive activity dim at all you know the supply isn't handling the initial pull at post time. If you are running games or playing dvds, avi files, mp3 in WMP with the visualzations going, etc. without problems and good sound the current installation of Everest is suspect! But if you start seeing lights dimming and other things "hardware" not software becomes a concern.
 
it runs fine. there was an issue with a screen thing with the game but i uninstalle dit and installed it and i havent had any problem since. im not sure what happend with the Everest issue.
 
It sounds like some part of Everest may have tried to access memory areas reserved specifically for the system. Windows may have been forced to shutdown by reasons unknown. The one thing that can help at times is the event viewer included in Windows. Although the data there needs to be researched due to technical terms it can at times point at a problem source. For instructions on this go to http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&sd=tech

So how's the sound working out? If you aren't seeing any problems running multimedia or gaming you may have simply had a bad install of Everest or it somehow pulled on power levels too hard. That would suggest a resource conflict of some type would be the thing to cause a system crash.
 
Deletion of individual logs by themselves is simply deletion of text files essentially created by the event viewer process to log events. Windows will create new ones as time goes on automatically. Often a new one will overwrite others after a period of a calendar month otherwise you would be seeing them fill the drive.

One tool everyone gets the word on generally is a basic crap cleaner that will go through your drive(s) and remove unattached and now useless files. CCleaner is a freeware you can download from http://www.ccleaner.com/

The one caution when running it is to keep an eye on the files it lists ready for deletion. You occasionally spot files you have saved in folders you created yourself. That's the only drawback seen with it. Otherwise it will quite literally clean up a ton of temp install logs and other useless clutter taking up drive space.
 
You must log in or register to reply here.
Back
Top