|
Poslao: 10 Sep 2012 00:56
|
offline
- Pakito93
- Zaslužni građanin
- Milos Pavlovic
- System Administrator
- Pridružio: 10 Dec 2011
- Poruke: 560
- Gde živiš: 127.0.0.1
|
ja imam maticnu asrock g31m-gs r2.0 i koristim njenu integrisanu zvucnu kartu e sad problem se javio kada je moj drugar u toku rada racunara izvadio iz PCI slota wireless kartu a onda je se ugasio ekran jer je verovatno i graficku malo izvukao. Kada je vratio wifi restartovali smo komp i posle toga zvuka nema u opste zvucnici rade ali kada ih ukljucim u komp ne. Dali neko zna sta se desava? nerade ni kada ih stavim u bilo koji ulaz.
|
|
|
|
|
Registruj se da bi učestvovao u diskusiji. Registrovanim korisnicima se NE prikazuju reklame unutar poruka.
|
|
|
Poslao: 10 Sep 2012 01:05
|
offline
- djolew
- Elitni građanin
- Pridružio: 24 Dec 2011
- Poruke: 1638
- Gde živiš: Novi Banovci
|
Proveri u device manager da li nemas neki upitnik, uzvicnik.
|
|
|
|
|
|
|
Poslao: 01 Okt 2012 22:11
|
offline
- Pakito93
- Zaslužni građanin
- Milos Pavlovic
- System Administrator
- Pridružio: 10 Dec 2011
- Poruke: 560
- Gde živiš: 127.0.0.1
|
Napisano: 10 Sep 2012 1:12
instalirao nove drajvere pa oborio sistem (win 7) i nista a sto se tice dev.manager-a sve je normalno
uzeo sam novu zvucnu kartu intex cmi 8738-6ch ali nisam dobio drajvere za nju ako bi mogao neko da mi nadje
Dopuna: 01 Okt 2012 22:11
Da osvezimo temu malo.
Ja sam skinuo drajver C-media Audio ali mi se ne svidja uopste!
Dali postoje jos neki drajveri sem ovoga?
|
|
|
|
|
|
|
Poslao: 01 Okt 2012 22:16
|
offline
- SlobaBgd
- Mod u pemziji
- Pridružio: 10 Okt 2005
- Poruke: 13526
- Gde živiš: Beograd
|
Čekaj, najpre napiši da li si rešio problem, odnosno imaš li zvuk?
A za drajvere, oni se ne biraju po izgledu nego po funkcionalnosti.
Postoje i drugi drajveri sa lepim panelom za podešavanje, ali oni ne odgovaraju tvojoj zvučnoj kartici.
|
|
|
|
|
|
|
|
|
Poslao: 04 Okt 2012 13:07
|
offline
- Pakito93
- Zaslužni građanin
- Milos Pavlovic
- System Administrator
- Pridružio: 10 Dec 2011
- Poruke: 560
- Gde živiš: 127.0.0.1
|
Evo:
https://www.mycity.rs/must-login.png
Imam zvuk ali je krenuo recimo da se pojavljuje i BSOD a evo sta kaze Who Crashed:
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 3.06
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: PSYHO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3220496384 total
VM: 2147352576, free: 1974317056
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 10/2/2012 7:04:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100212-24515-01.dmp
This was probably caused by the following module: cmudax3.sys (cmudax3+0xCB8E6)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x86D0000, 0xFFFFFFFF87666008)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\cmudax3.sys
product: C-Media Audio Driver (WDM)
company: C-Media Inc
description: C-Media Audio WDM Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cmudax3.sys (C-Media Audio WDM Driver, C-Media Inc).
Google query: cmudax3.sys C-Media Inc BAD_POOL_CALLER
On Tue 10/2/2012 7:04:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cmudax3.sys (cmudax3+0xCB8E6)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x86D0000, 0xFFFFFFFF87666008)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\cmudax3.sys
product: C-Media Audio Driver (WDM)
company: C-Media Inc
description: C-Media Audio WDM Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cmudax3.sys (C-Media Audio WDM Driver, C-Media Inc).
Google query: cmudax3.sys C-Media Inc BAD_POOL_CALLER
On Sun 9/23/2012 7:41:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-27406-01.dmp
This was probably caused by the following module: hal.sys (hal+0xEFCD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85E11024, 0xFFFFFFFFB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys WHEA_UNCORRECTABLE_ERROR
On Tue 9/18/2012 10:38:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-28296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x31834B)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85DF94DC, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 9/18/2012 10:14:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-38781-01.dmp
This was probably caused by the following module: hal.sys (hal+0xEFCD)
Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85E4F024, 0xFFFFFFFFB2000040, 0x800)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys WHEA_UNCORRECTABLE_ERROR
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
cmudax3.sys (C-Media Audio WDM Driver, C-Media Inc)
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
i to je poceo konstantno da se pojavljuje recimo kada idu neka 2 zvuka u isto vreme.
|
|
|
|
|
|
|
|
|
Poslao: 04 Okt 2012 14:29
|
offline
- Pakito93
- Zaslužni građanin
- Milos Pavlovic
- System Administrator
- Pridružio: 10 Dec 2011
- Poruke: 560
- Gde živiš: 127.0.0.1
|
Nazalost se opet isto desi
|
|
|
|
|
|
|
|
|
|
