Sounds and Audio Devices модул реинстал...

ето я грешката... :Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini092109-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 Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820
Debug session time: Mon Sep 21 14:08:58.156 2009 (GMT+3)
System Uptime: 0 days 5:22:17.714
*********************************************************************
* 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
.....
Unable to load image tridwave.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for tridwave.sys
Unable to load image portcls.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for portcls.sys
*** ERROR: Module load completed but symbols could not be loaded for portcls.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, f1fd6093, f7c6fc0c, f7c6f908}

***** 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+ *
*********************************************************************
Probably caused by : tridwave.sys ( tridwave+9093 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: f1fd6093, The address that the exception occurred at
Arg3: f7c6fc0c, Exception Record Address
Arg4: f7c6f908, Context Record Address

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: 3a0376ce

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
tridwave+9093
f1fd6093 8b08 mov ecx,dword ptr [eax]

EXCEPTION_RECORD: f7c6fc0c -- (.exr 0xfffffffff7c6fc0c)
ExceptionAddress: f1fd6093 (tridwave+0x00009093)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT: f7c6f908 -- (.cxr 0xfffffffff7c6f908)
eax=00000000 ebx=c00000b5 ecx=1e290008 edx=f7c6fcf0 esi=00000000 edi=f1fcd3f8
eip=f1fd6093 esp=f7c6fcd4 ebp=f7c6fd24 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
tridwave+0x9093:
f1fd6093 8b08 mov ecx,dword ptr [eax] ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f746f7a9 to f1fd6093

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7c6fd24 f746f7a9 83842990 83843568 f7e48000 tridwave+0x9093
f7c6fd4c f746f73f 00000000 00000000 83842990 portcls+0x137a9
f7c6fd60 80563b90 83842990 e1141650 805618dc portcls+0x1373f
f7c6fd74 804e426b 84776618 00000000 853c8b30 nt+0x8cb90
f7c6fdac 8057cfce 84776618 00000000 00000000 nt+0xd26b
f7c6fddc 804f88fa 804e4196 00000001 00000000 nt+0xa5fce
00000000 00000000 00000000 00000000 00000000 nt+0x218fa

FOLLOWUP_IP:
tridwave+9093
f1fd6093 8b08 mov ecx,dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: tridwave+9093

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: tridwave

IMAGE_NAME: tridwave.sys

STACK_COMMAND: .cxr 0xfffffffff7c6f908 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

kd> lmvm tridwave
start end module name
f1fcd000 f1fdb860 tridwave (no symbols)
Loaded symbol image file: tridwave.sys
Image path: tridwave.sys
Image name: tridwave.sys
Timestamp: Sat Nov 04 04:39:10 2000 (3A0376CE)
CheckSum: 000214F2
ImageSize: 0000E860
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
kd> lmvm tridwave
start end module name
f1fcd000 f1fdb860 tridwave (no symbols)
Loaded symbol image file: tridwave.sys
Image path: tridwave.sys
Image name: tridwave.sys
Timestamp: Sat Nov 04 04:39:10 2000 (3A0376CE)
CheckSum: 000214F2
ImageSize: 0000E860
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

tridwave.sys го намерх за хп и я инстална, но разкарах цялото аудио след белята...

обобщавам - Sounds and Audio Devices модул НЕ ВИЖДА ИНСТАлНАТИТЕ аудио карти -или\и\ миксерите им
или търся да заместя модула от работеща хп ,намиращ се вероятно в system32 папка,или кой регистър отговаря за Sounds and Audio Devices модул...