Blue screen viahduaa.sys

**Posty:** 11 · przez **rifi** 20 Lip 2010, 00:26

Otóż gdy mam włączonego counter-strike bądź jakąś inną grę i przy minimalizacji, gdy włączę np. YouTube komp się restaruje z niebieskim ekranem.
Nie wiedziałem jakiego programu użyć więc użyłem dumpa

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini071409-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0 Debug session time: Tue Jul 14 20:26:20.580 2009 (GMT+2) System Uptime: 0 days 23:58:56.027 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ . Loading User Symbols Loading unloaded module list .............................. *** WARNING: Unable to verify timestamp for viahduaa.sys *** ERROR: Module load completed but symbols could not be loaded for viahduaa.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {f4242d0c, 2, 8, f4242d0c} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. *** WARNING: Unable to verify timestamp for portcls.sys *** ERROR: Module load completed but symbols could not be loaded for portcls.sys ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : viahduaa.sys ( viahduaa+17d0c ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: f4242d0c, memory referenced Arg2: 00000002, IRQL Arg3: 00000008, value 0 = read operation, 1 = write operation Arg4: f4242d0c, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. FAULTING_MODULE: 804d7000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 477b73ac READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd f4242d0c CURRENT_IRQL: 2 FAULTING_IP: viahduaa+17d0c f4242d0c ?? ??? CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from f4237445 to f4242d0c FAILED_INSTRUCTION_ADDRESS: viahduaa+17d0c f4242d0c ?? ??? STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. f78a69e8 f4237445 f78a6ec0 831c3290 00001120 viahduaa+0x17d0c f78a6f54 f420a4c5 f778e100 f778cfe0 f778e100 viahduaa+0xc445 f78a6f7c f420a263 f78a6f00 00001120 f78a6fac portcls+0x14c5 f78a6fbc f420a704 000a3100 04484c1e ffdff000 portcls+0x1263 f78a6fc0 000a3100 04484c1e ffdff000 000000c9 portcls+0x1704 f78a6fc4 04484c1e ffdff000 000000c9 80540d5d 0xa3100 f78a6fc8 ffdff000 000000c9 80540d5d 846f9300 0x4484c1e f78a6fcc 00000000 80540d5d 846f9300 846f92f0 0xffdff000 STACK_COMMAND: kb FOLLOWUP_IP: viahduaa+17d0c f4242d0c ?? ??? SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: viahduaa+17d0c FOLLOWUP_NAME: MachineOwner MODULE_NAME: viahduaa IMAGE_NAME: viahduaa.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------

Te blue screeny zdarzają się często i powoli działa mi to na nerwy.

**Posty:** 2547 · przez **lance87** 20 Lip 2010, 16:54

Plik ten to sterownik karty dźwiękowej, trzeba go przeinstalować. Podaj dokładne dane Twojej płyty głównej, karty dźwiękowej i innych podzespołów lub spróbuj samemu pobrać i przeinstalować odpowiednie sterowniki z TEJ stronki :wink:

**Posty:** 11 · przez **rifi** 20 Lip 2010, 18:03

Właśnie wiem że to sterownik dźwięku, instalowałem nowe sterowniki ze strony producenta i jest to samo.
Tu masz raport z everesta cały mój sprzęt
http://wklej.org/id/366843/
Płyta główna to M2N-CM DVI
Stare sterowniki pochodziły z płyty oryginalnej dołączonej do płyty głównej myślę że to od czegoś innego, ale nie jestem pewien, karta dźwiękowa jest zintegrowana.
Jak będziesz potrzebował nazwę zasilacza to dam edit i podam.

**Posty:** 1916 · przez **lamar** 20 Lip 2010, 18:30

Można spróbować wyczyścić pozostałości po starych sterownikach...

1. Pobierasz sterowniki audio
2. Pobierasz i instalujesz program Driver Sweeper
3. Menedżer urządzeń :arrow:

kontrolery dźwięku, video i gier :arrow:

PPM na VIA HD Audio :arrow:

odinstaluj
4. Uruchamiasz kompa w trybie awaryjnym (F8 przy starcie)
5. W trybie awaryjnym włączasz program Driver Sweeper, wybierasz z listy Realtek Sound i klikasz klikamy na przycisk Analizować (Analyse) :arrow:

zaznaczasz wszystkie znalezione pliki :arrow:

klikasz na przycisk Wyczyścić (Clean)
6. Uruchamiasz kompa Normalnie
7. Instalujesz te sterowniki, które Ci podałem

**Posty:** 11 · przez **rifi** 20 Lip 2010, 20:14

Jako że ten program który podałeś nie działa na moim Windowsie użyłem Driver cleaner pro i zainstalowałem sterowniki na nowo. Zobaczę czy problem będzie jeszcze występował jak coś nie zamykać tematu dopóki dopóty nie będę miał 100% pewności że problem zniknął. :wink:

Dodano Dzisiaj, 12:16:
Przepraszam że post pod postem ale chyba nie podskoczył by w górę. Problem jest cały czas i to tak często że powoli tracę cierpliwość i mam ochotę wywalić kompa za okno. Proszę o wszelaką pomoc, bo nie chce stracić komputera który zginie śmiercią tragiczną.

**Posty:** 141 · przez **HiVu** 26 Lip 2010, 11:33

Witam ,
też jestem zainteresowany tym problemem gdyż mam podobny .

**Posty:** 2753 · przez **Hellfire** 29 Lip 2010, 13:00

Jaki zasilacz masz w tym komputerze?

**Posty:** 11 · przez **rifi** 29 Lip 2010, 16:49

Procomp Model ATX KY-400W

**Posty:** 29 · przez **CindyThomas91** 30 Maj 2025, 12:52

Blue screen viahduaa is a common issue faced by many computer users, often indicating a system crash or critical error. This problem can disrupt important tasks and cause frustration. Understanding the root causes, such as hardware failures or driver conflicts, is essential for troubleshooting. For those working with digital displays or graphic design, accurate measurements are crucial—tools like the pixel-to-inches calculator found at https://allcolorscreen.com/pixels-to-inches-calculator/ help ensure precision. By combining technical knowledge with the right resources, users can effectively address blue screen viahduaa errors and optimize their screen settings for better performance.

Dodano Dzisiaj, 13:23:
Eliminate distractions and boost focus by creating a quiet workspace using PrivacyPod.ai. Designed for busy offices, it offers a compact, sound-isolating pod that fits any environment. Whether you need a private call or deep concentration, this solution delivers comfort and silence without major renovations. Discover how to transform your office experience by visiting https://privacypod.ai/. Enjoy enhanced productivity and peace without the usual office clatter.

Kto jest na forum