errors
- Thread starter Tommy Boy
- Start date
Well I hope it has. Keep us postedIt's still doing it after the reformat.....
I've tried a few other things to no avail also, I just keep getting that bsod, so I figured it happened when I played music, so I upgraded my Musicmatch Jukebox and so far no problems....we'll see....only time will tell
I've tried a few other things to no avail also, I just keep getting that bsod, so I figured it happened when I played music, so I upgraded my Musicmatch Jukebox and so far no problems....we'll see....only time will tell
Here's one of the dump files from yesterday, they are all pretty much the same......anyone know what to make of it?
______________________________________________________
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini051705-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue May 17 22:24:07.906 2005 (GMT-4)
System Uptime: 0 days 1:50:47.493
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
Unable to load image kmixer.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for kmixer.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, f118c0be, f1e81c18, f1e81914}
Probably caused by : kmixer.sys ( kmixer!MixOneBuff+55e )
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: f118c0be, The address that the exception occurred at
Arg3: f1e81c18, Exception Record Address
Arg4: f1e81914, Context Record Address
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
kmixer!MixOneBuff+55e
f118c0be 8b88a8000000 mov ecx,[eax+0xa8]
EXCEPTION_PARAMETER1: f1e81c18
CONTEXT: f1e81914 -- (.cxr fffffffff1e81914)
eax=54935493 ebx=0000013c ecx=e1630dc8 edx=00000000 esi=f10714f8 edi=e1630dc8
eip=f118c0be esp=f1e81ce0 ebp=f1e81d50 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
kmixer!MixOneBuff+0x55e:
f118c0be 8b88a8000000 mov ecx,[eax+0xa8] ds:0023:5493553b=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from f117adf0 to f118c0be
STACK_TEXT:
f1e81d50 f117adf0 fdd3a008 fec665e8 00000000 kmixer!MixOneBuff+0x55e
f1e81d84 f117b1fd fec665e8 00000000 00000000 kmixer!MxWorker+0x1c0
f1e81dac 8057be15 fdd3a008 00000000 00000000 kmixer!MxPrivateWorkerThread+0xad
f1e81ddc 804fa4da f117b150 fdd3a008 00000000 nt!CcCopyRead+0x3aa
00000000 00000000 00000000 00000000 00000000 nt!KeStartThread+0x4b
FOLLOWUP_IP:
kmixer!MixOneBuff+55e
f118c0be 8b88a8000000 mov ecx,[eax+0xa8]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: kmixer!MixOneBuff+55e
MODULE_NAME: kmixer
IMAGE_NAME: kmixer.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d32
STACK_COMMAND: .cxr fffffffff1e81914 ; kb
FAILURE_BUCKET_ID: 0x7E_kmixer!MixOneBuff+55e
BUCKET_ID: 0x7E_kmixer!MixOneBuff+55e
Followup: MachineOwner
______________________________________________________
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini051705-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Tue May 17 22:24:07.906 2005 (GMT-4)
System Uptime: 0 days 1:50:47.493
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.......................................................................................................................
Loading unloaded module list
...........
Loading User Symbols
Unable to load image kmixer.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for kmixer.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, f118c0be, f1e81c18, f1e81914}
Probably caused by : kmixer.sys ( kmixer!MixOneBuff+55e )
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: f118c0be, The address that the exception occurred at
Arg3: f1e81c18, Exception Record Address
Arg4: f1e81914, Context Record Address
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
kmixer!MixOneBuff+55e
f118c0be 8b88a8000000 mov ecx,[eax+0xa8]
EXCEPTION_PARAMETER1: f1e81c18
CONTEXT: f1e81914 -- (.cxr fffffffff1e81914)
eax=54935493 ebx=0000013c ecx=e1630dc8 edx=00000000 esi=f10714f8 edi=e1630dc8
eip=f118c0be esp=f1e81ce0 ebp=f1e81d50 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
kmixer!MixOneBuff+0x55e:
f118c0be 8b88a8000000 mov ecx,[eax+0xa8] ds:0023:5493553b=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from f117adf0 to f118c0be
STACK_TEXT:
f1e81d50 f117adf0 fdd3a008 fec665e8 00000000 kmixer!MixOneBuff+0x55e
f1e81d84 f117b1fd fec665e8 00000000 00000000 kmixer!MxWorker+0x1c0
f1e81dac 8057be15 fdd3a008 00000000 00000000 kmixer!MxPrivateWorkerThread+0xad
f1e81ddc 804fa4da f117b150 fdd3a008 00000000 nt!CcCopyRead+0x3aa
00000000 00000000 00000000 00000000 00000000 nt!KeStartThread+0x4b
FOLLOWUP_IP:
kmixer!MixOneBuff+55e
f118c0be 8b88a8000000 mov ecx,[eax+0xa8]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: kmixer!MixOneBuff+55e
MODULE_NAME: kmixer
IMAGE_NAME: kmixer.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d32
STACK_COMMAND: .cxr fffffffff1e81914 ; kb
FAILURE_BUCKET_ID: 0x7E_kmixer!MixOneBuff+55e
BUCKET_ID: 0x7E_kmixer!MixOneBuff+55e
Followup: MachineOwner
Here's one from today while I was running Winamp instead of Musicmatch.......any suggestions?
___________________________________________
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini051805-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed May 18 21:25:33.828 2005 (GMT-4)
System Uptime: 0 days 2:06:58.409
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
Unable to load image kmixer.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for kmixer.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : hardware ( kmixer!Convert16+147 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
MISALIGNED_IP:
kmixer!Convert16+147
f09cfc57 0283c1044a75 add al,[ebx+0x754a04c1]
LAST_CONTROL_TRANSFER: from f09c50b8 to f09cfc57
STACK_TEXT:
f12dfccc f09c50b8 e30addc0 0000006e 000001b9 kmixer!Convert16+0x147
f12dfd50 f09b3df0 feb8f008 ff8d3008 00000000 kmixer!MixOneBuff+0x558
f12dfd84 f09b41fd ff8d3008 00000000 00000000 kmixer!MxWorker+0x1c0
f12dfdac 8057be15 feb8f008 00000000 00000000 kmixer!MxPrivateWorkerThread+0xad
f12dfddc 804fa4da f09b4150 feb8f008 00000000 nt!CcCopyRead+0x3aa
00000000 00000000 00000000 00000000 00000000 nt!KeStartThread+0x4b
FOLLOWUP_IP:
kmixer!Convert16+147
f09cfc57 0283c1044a75 add al,[ebx+0x754a04c1]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: kmixer!Convert16+147
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_kmixer.sys
BUCKET_ID: IP_MISALIGNED_kmixer.sys
Followup: MachineOwner
___________________________________________
Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini051805-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed May 18 21:25:33.828 2005 (GMT-4)
System Uptime: 0 days 2:06:58.409
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
Unable to load image kmixer.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for kmixer.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : hardware ( kmixer!Convert16+147 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
MISALIGNED_IP:
kmixer!Convert16+147
f09cfc57 0283c1044a75 add al,[ebx+0x754a04c1]
LAST_CONTROL_TRANSFER: from f09c50b8 to f09cfc57
STACK_TEXT:
f12dfccc f09c50b8 e30addc0 0000006e 000001b9 kmixer!Convert16+0x147
f12dfd50 f09b3df0 feb8f008 ff8d3008 00000000 kmixer!MixOneBuff+0x558
f12dfd84 f09b41fd ff8d3008 00000000 00000000 kmixer!MxWorker+0x1c0
f12dfdac 8057be15 feb8f008 00000000 00000000 kmixer!MxPrivateWorkerThread+0xad
f12dfddc 804fa4da f09b4150 feb8f008 00000000 nt!CcCopyRead+0x3aa
00000000 00000000 00000000 00000000 00000000 nt!KeStartThread+0x4b
FOLLOWUP_IP:
kmixer!Convert16+147
f09cfc57 0283c1044a75 add al,[ebx+0x754a04c1]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: kmixer!Convert16+147
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: kb
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED_kmixer.sys
BUCKET_ID: IP_MISALIGNED_kmixer.sys
Followup: MachineOwner
Well, I finally sorted all this out, I uninstalled my soundcard and installed my onboard sound.....no help. I also updated all my drivers and updated the bios....no help. then I remembered I had my cpu overclocked (XP 2600 oc'd to 2.3 ghz) and someone told me once that might be causing problems, so I finally set it back to stock settings and everything seems okay. hasn't errored in a few days. so I'm going to run it a few more days like this and if everything is okay, I'm going to reinstall my soundcard and go about living my life happily.....lol Anyway, thanks everyone for the help.
