BSOD errors, help with Minidump analysis

WinXP Pro SP2, fully patched. Pentium 3.2GHz, 2Gb RAM, NVIDIA Quadro FX1300 display, SW Raid 1 on 2 x 80Gb SATA. Onboard sound on Foxpro MB.

I keep getting BSOD at apparently random time on this computer. There are no real clues in the event log apart from the following message:-

*****************************************
Eample 1
*****************************************

Event Type:      Error
Event Source:      System Error
Event Category:      (102)
Event ID:      1003
Date:            22/03/2006
Time:            13:44:44
User:            N/A
Computer:      C0072
Description:
Error code 100000d1, parameter1 00000000, parameter2 00000002, parameter3 00000008, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:
0000:  53 79 73 74 65 6d 20 45   System.E
0008:  72 72 6f 72 20 20 45 72   rror..Er
0010:  72 6f 72 20 63 6f 64 65   ror.code
0018:  20 31 30 30 30 30 30 64   .100000d
0020:  31 20 20 50 61 72 61 6d   1..Param
0028:  65 74 65 72 73 20 30 30   eters.00
0030:  30 30 30 30 30 30 2c 20   000000,.
0038:  30 30 30 30 30 30 30 32   00000002
0040:  2c 20 30 30 30 30 30 30   ,.000000
0048:  30 38 2c 20 30 30 30 30   08,.0000
0050:  30 30 30 30               0000

*****************************************
End of example 1
*****************************************


*****************************************
Example 2
*****************************************
Event Type:      Error
Event Source:      System Error
Event Category:      (102)
Event ID:      1003
Date:            20/03/2006
Time:            09:18:02
User:            N/A
Computer:      C0072
Description:
Error code 100000d1, parameter1 427f5f6c, parameter2 00000002, parameter3 00000001, parameter4 890494fa.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:
0000:  53 79 73 74 65 6d 20 45   System.E
0008:  72 72 6f 72 20 20 45 72   rror..Er
0010:  72 6f 72 20 63 6f 64 65   ror.code
0018:  20 31 30 30 30 30 30 64   .100000d
0020:  31 20 20 50 61 72 61 6d   1..Param
0028:  65 74 65 72 73 20 34 32   eters.42
0030:  37 66 35 66 36 63 2c 20   7f5f6c,.
0038:  30 30 30 30 30 30 30 32   00000002
0040:  2c 20 30 30 30 30 30 30   ,.000000
0048:  30 31 2c 20 38 39 30 34   01,.8904
0050:  39 34 66 61               94fa

*****************************************
End of example 1
*****************************************


Could someone help me trace the source of the error please?

Minidumps are available here:-  http://www.phdconcepts.com/Minidump.zip
MadrillenoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cpc2004Commented:
The crashes have two culprits. C-media wdm onboard sound driver and Trend Micro Anti-Virus. Upgrade C-Media Wdm on-board Sound Card Driver and Trend Micro AV to latest patch.


Mini022706-01.dmp BugCheck 100000D1, {0, 2, 8, 0}
Probably caused by : cmaudio.sys ( cmaudio+26742 )

Mini030606-01.dmp BugCheck 100000D1, {0, 2, 8, 0}
Probably caused by : cmaudio.sys ( cmaudio+2679a )

Mini031306-01.dmp BugCheck 19, {20, 88f38100, 88f38ee8, ffbdabf7}
Probably caused by : TmPreFlt.sys ( TmPreFlt+1d10 )

Mini032006-01.dmp BugCheck 100000D1, {427f5f6c, 2, 1, 890494fa}
Probably caused by : cmaudio.sys ( cmaudio+267c1 )

Mini032206-01.dmp BugCheck 100000D1, {0, 2, 8, 0}
Probably caused by : cmaudio.sys ( cmaudio+2679a )

0
MadrillenoAuthor Commented:
Thanks. Will try the sound driver first. TheTrend AV should already be patched since the domain is automatically updated.

Mike
0
MadrillenoAuthor Commented:
Can you give me any tips on how you worked this out please? If it's not too big a topic.

I have been through the MS Support pages, and done some general searches, but I coldn't find a straightforward answer as to how to analyse memory dumps. I tried dumpchk.exe, but the explanation on MS didn't relly follow with the output I got.

Mike
0
cpc2004Commented:
1) Install microsoft debugging tools from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
2) Download and install the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
3) Locate your latest memory.dmp file- C:\windows\Minidump\Mini011005-01.dmp or whatever
4) Open a CMD prompt and cd\program files\debugging tools for windows\
5) Type the following stuff:

Code:
c:\program files\debugging tools>kd -z C:\windows\Minidump\Mini011005-01.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;lmnt;.logclose;q

Now you have a debuglog.txt in c:\, open it in notepad
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.