Minidump for BSOD on Shutdowns

Bill, I have another minidump file form my typical shutdown crash last night. It's pretty much the same BUT, for the first time time the problem seems to be identified as "OVERLAPPED_MODULE: Address regions for 'kmixer' and 'kmixer.sys' overlap" I don't know if this has contributed to all of the other BSODs but here is the file:

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini110306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\program files\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri Nov 3 05:37:30.843 2006 (GMT-8)
System Uptime: 0 days 0:15:19.552
Loading Kernel Symbols
....................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e3903000, 1, 805d711a, 1}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpCopyCell+72 )

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

1: kd> !analyze -V

Unknown option '-V'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e3903000, 1, 805d711a, 1}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpCopyCell+72 )

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

1: kd> !analyze
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e3903000, 1, 805d711a, 1}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpCopyCell+72 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e3903000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 805d711a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name

OVERLAPPED_MODULE: Address regions for 'kmixer' and 'kmixer.sys' overlap

WRITE_ADDRESS: e3903000

FAULTING_IP:
nt!CmpCopyCell+72
805d711a f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from 805d71f3 to 805d711a

STACK_TEXT:
ec35fb78 805d71f3 00523020 00000004 e1327008 nt!CmpCopyCell+0x72
ec35fbac 805d7c60 01cfeb60 00403080 00522338 nt!CmpCopyValue+0xc0
ec35fbf4 805d7d0b e2cfeb60 00403020 005222d8 nt!CmpCopyKeyPartial+0x16f
ec35fc34 805d77ed e137b000 00000400 00000007 nt!CmpCopySyncTree2+0x25a
ec35fc64 8065b1d5 e2cfeb60 00000020 e1327008 nt!CmpCopySyncTree+0x4f
ec35fc98 8065315f 00000020 000006b0 00000003 nt!CmSaveKey+0xde
ec35fcbc 804dd99f e37f0430 000006b0 ec35fd54 nt!NtSaveKey+0x78
ec35fcbc 804e42bf e37f0430 000006b0 ec35fd54 nt!KiFastCallEntry+0xfc
ec35fd3c 8065312c 00000094 000006b0 806530e7 nt!ZwSaveKey+0x11
ec35fd54 804dd99f 00000094 000006b0 0006f8b8 nt!NtSaveKey+0x45
ec35fd54 7c90eb94 00000094 000006b0 0006f8b8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006f8b8 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpCopyCell+72
805d711a f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

SYMBOL_NAME: nt!CmpCopyCell+72

FAILURE_BUCKET_ID: 0x50_W_nt!CmpCopyCell+72

BUCKET_ID: 0x50_W_nt!CmpCopyCell+72

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

Could either XP's audio drivers and/or the SB Audigy's drivers be corrupt? Thanks.

 

Updating the Creative drivers is always a good idea.

In addition, do the free registration at this site and download DocMemory. Unzip, run the utility to create a bootable floppy, reset your BIOS boot order to Floppy drive first, and reboot and run an extended Memory test:
http://www.simmtester.com/PAGE/products/doc/docinfo.asp

(I would not put much concern behind the kmixer kmixer.sys issue).

 

After weeks of shutdown BSODs with the cause being almost impossible to pin down, and the probability of of a corrupt OS growing stronger, I bit the bullet and gave up the ghost. I took my MPC recovery, driver and software CDs out, gulped and reinstalled XP SP1. Two hours later, after applying SP2 and letting Windows and Office Update apply over 80 security patches, I had a clean XP system. That was the easy part, although by reflex, I still hold my breath during a shutdown or restart. Restoring all of my installed programs and recustomizing everything to my liking is the hard part. Bill, I can't thank you enough for the help that you've given me. All of us in the windows community appreciate the time that you and your fellow experts devote to trying to help us work through all of Windows' "features" (LOL).