Bongobob

Ok, so my computer is starting to go through Hard restarts, before i actually turned off automatically restart on system failure, so now i get to actually read the nice blue screen, bsod , after opening it with the windows debugger, and analyzing it, it supplies me with this;


Loading Dump File [C:\WINDOWS\Minidump\Mini021408-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
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Thu Feb 14 16:26:58.187 2008 (GMT-5)
System Uptime: 0 days 1:06:03.815
************************************************** *******************
* 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 viaudios.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for viaudios.sys
*** ERROR: Module load completed but symbols could not be loaded for viaudios.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, f7f87d1b, b9b33a44, b9b33740}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214080,42251106
***** 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
*** WARNING: Unable to verify timestamp for ks.sys
*** ERROR: Module load completed but symbols could not be loaded for ks.sys
*** WARNING: Unable to verify timestamp for kmixer.sys
*** ERROR: Module load completed but symbols could not be loaded for kmixer.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 : viaudios.sys ( viaudios+8d1b )

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: f7f87d1b, The address that the exception occurred at
Arg3: b9b33a44, Exception Record Address
Arg4: b9b33740, Context Record Address

Debugging Details:
------------------

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214080,42251106
***** 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+ *
************************************************** *******************

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4057fcd1

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

FAULTING_IP:
viaudios+8d1b
f7f87d1b 8b0486 mov eax,dword ptr [esi+eax*4]

EXCEPTION_RECORD: b9b33a44 -- (.exr 0xffffffffb9b33a44)
ExceptionAddress: f7f87d1b (viaudios+0x00008d1b)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000004
Attempt to read from address 00000004

CONTEXT: b9b33740 -- (.cxr 0xffffffffb9b33740)
eax=00000001 ebx=00000000 ecx=822f5000 edx=822938f8 esi=00000000 edi=00000000
eip=f7f87d1b esp=b9b33b0c ebp=b9b33b60 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
viaudios+0x8d1b:
f7f87d1b 8b0486 mov eax,dword ptr [esi+eax*4] ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f7f88fe6 to f7f87d1b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b9b33b60 f7f88fe6 822938f8 00000400 82196bb8 viaudios+0x8d1b
b9b33ba4 f7f895c6 fcda6e00 821e46d0 822a29c0 viaudios+0x9fe6
b9b33bc4 f7f899f9 822938f8 b9e03400 00001680 viaudios+0xa5c6
b9b33c74 f7f89c0d 822a29c0 82129010 822a29f0 viaudios+0xa9f9
b9b33c90 f7f6ba59 82129010 81ec06c8 00000001 viaudios+0xac0d
b9b33cc8 f7f6d19a 00000000 81ec06c8 00000001 portcls+0x10a59
b9b33cfc f7f6b69d 00000000 821ae030 81ec06c8 portcls+0x1219a
b9b33d18 f7fa4f85 821ae030 81ec06c8 b9b33d54 portcls+0x1069d
b9b33d28 f7f929e2 821ae030 81ec06c8 804e37f7 ks+0x8f85
b9b33d54 b9a47e63 81edc468 00000000 82122b38 viaudios+0x139e2
b9b33d84 b9a481fd 81edc468 00000000 00000000 kmixer+0x1e63
b9b33dac 8057be15 82122b38 00000000 00000000 kmixer+0x21fd
b9b33ddc 804fa4da b9a48150 82122b38 00000000 nt+0xa4e15
00000000 00000000 00000000 00000000 00000000 nt+0x234da


FOLLOWUP_IP:
viaudios+8d1b
f7f87d1b 8b0486 mov eax,dword ptr [esi+eax*4]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: viaudios+8d1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: viaudios

IMAGE_NAME: viaudios.sys

STACK_COMMAND: .cxr 0xffffffffb9b33740 ; kb

BUCKET_ID: WRONG_SYMBOLS

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

kd> lmvm viaudios
start end module name
f7f7f000 f7f9ba00 viaudios T (no symbols)
Loaded symbol image file: viaudios.sys
Image path: viaudios.sys
Image name: viaudios.sys
Timestamp: Wed Mar 17 02:22:57 2004 (4057FCD1)
CheckSum: 0001FFD5
ImageSize: 0001CA00
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
kd> gh
^ No runnable debuggees error in 'gh'



Can anyone explain to me what can fix, help me here, and if this is sound card related, will it fix it if i got a sound card? rather than using a onboard crappy one? This has been happening for quite sometime now, and i would love to get this fixed asap.

Someone HELP!