BSOD 0x1000000a - kmixer.sys at fault?

[Guest]

New PC / fresh install of windows XP pro ~3 months ago. This is my first BSOD
on this system. I wasn't doing anything special at the time of the crash --
it just randomly happened. Full BSOD is 0x1000000a (0x00000021, 0x00000002,
0x00000000, 0x80514851). The minidump file says the bucket ID is
DRIVER_FAULT, yet it couldn't resolve the name because of memory_corruption.
So it points to ntkrpamp.exe. It seems the majority of the loaded modules
were kmixer.sys, which would point to the Microsoft sound mixer. Thoughts?

call stack:
1. nt!MiResolveMappedFileFault+0x37
2. nt!MiResolveProtoPteFault+0x195
3. nt!MiDispatchFault+0xf1
4. nt!MmAccessFault+0x877
5. nt!MmCheckCachedPageState+0x601
6. nt!CcPerformReadAhead+0x20b
7. nt!CcWorkerThread+0x150
8. nt!ExpWorkerThread+0xef
9. nt!PspSystemThreadStartup+0x34
10. nt!KiThreadStartup+0x16

http://bsod2600.home.comcast.net/Mini101807-01.dmp

 

[Gerry]

Has the problem occured once or has it been repeated?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Guest]

It's only happened once. thankfully.

Has the problem occured once or has it been repeated?


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~