[ratzlaff]

Yesterday I ran windows update after a while of not updating. I had about 150mb of updates to download and install. Now today I have notices that a number of operations cause my computer to instantly restart. Some of these operations are: running windows update, watching video files, doing certain things in visual studio.

When the computer starts up again it gives me a message that says "The system has recovered from a serious error"

Error Signature:
BCCode : 1000008e BCP1 : C0000005 BCP2 : BFB11ED5 BCP3 : B9C5CC70
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

It also gives the system dump.

I ran dumpchk.exe to see if I could find anything in there. It basically meant nothing to me at all.

Do any of you have any Ideas what is going wrong? This is clearly a software problem as it only occurs if I do certain operations and will always occur when doing those operations.

Thank you for your help.


XP Pro
AMD 3700+
nVidia 6800 GS
1GB Corsair Memory

[Mak213]

Have you finished all the updates? Are you doing all of this stuff at once while trying to update? Could jsut be your overloading the system while it is trying to update.

[ratzlaff]

Well I downloaded all the updates and installed them. I didn't restart right away, but within an hour. I wasnt multitasking during the download/install phase. I cant check to see if the updates didnt install because I cant use windows update.

Also here is the dumpchk if this means anything to you all?
Loading dump file C:\Mini040708-09.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 0ad00380
PfnDataBase 810a6000
PsLoadedModuleList 805533a0
PsActiveProcessHead 80559458
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 1000008e
BugCheckParameter1 c0000005
BugCheckParameter2 bfb11ed5
BugCheckParameter3 b9c5cc70
BugCheckParameter4 00000000
PaeEnabled 00000001
KdDebuggerDataBlock 80544ee0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000200
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002728
CallStackOffset 00002980
SizeOfCallStack 00001380
DriverListOffset 00003f90
DriverCount 0000007d
StringPoolOffset 000064b0
StringPoolSize 00001118
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack b9c5cc80
DebuggerDataOffset 00003d00
DebuggerDataSize 00000290
DataBlocksOffset 000075c8
DataBlocksCount 00000006


Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Apr 07 19:41:51 2008
System Uptime: 0 days 0:17:48
start end module name
804d7000 806cd580 nt Checksum: 00200031 Timestamp: Wed Feb 28 02:
38:52 2007 (45E53F9C)

Unloaded modules:
bab3d000 bab68000 kmixer.sys Timestamp: unavailable (00000000)
f7c5a000 f7c5b000 drmkaud.sys Timestamp: unavailable (00000000)
bab68000 bab8b000 aec.sys Timestamp: unavailable (00000000)
bad20000 bad2d000 DMusic.sys Timestamp: unavailable (00000000)
f6624000 f6632000 swmidi.sys Timestamp: unavailable (00000000)
f7b0e000 f7b10000 splitter.sys Timestamp: unavailable (00000000)
f76fc000 f7705000 processr.sys Timestamp: unavailable (00000000)
f7944000 f7949000 Cdaudio.SYS Timestamp: unavailable (00000000)
f71a1000 f71a4000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

[Mak213]

To me it seems that the system needed to restart to let the updates take effect. As they probably had some effect on the things you did afterwards.

Kmixer.sys is the Kernel Mode Audio Mixer

drmkaud.sys Is the Microsoft Kernel DRM Audio Descrambler Filter.

aec.sys is the Acoustic Echo canceler

DMusic.sys is another Audio Kernel driver


So from the looks of it there was a update that applied to your audio that needed to take effect. Watching the video after doing the updates but not restarting caused this. Check to make sure that you have all the updates now and that they all were installed successfully thru Windows update. If so just restart again and see if it crashes again.

[Xaero]

Have you tried reinstalling Windows? After you have installed Windows, try updating again.

[Mak213]

That wouldnt help as it was related to his Audio driver. Which i am guessing came from Windows update. Which would only reproduce the issue.

[Xaero]

Has he tried reinstalling the original audio drivers? Or updated versions? He could also try downloading a driver cleaner, then attempt to reinstall the audio drivers.

[Mak213]

Do not know. He has not come back after my suggestion to update his audio drivers.