Interpret my minidump file(s)?

I've been getting BSOD's during the shutdown process lately; the BSOD's themselves are not referring to any particular driver... but minidumps are being created, attached hereto.  I'd prefer not to have to download the entire debugging/minidump diagnosis kit just to read these minidumps, so if one of you already has installed that and can let me know what the dumps are trying to tell me, that would be worth 500 points to me.  I'm running WinXP, SP3, 32 bit.   Thanks!
Mini041010-01.dmp
Mini040710-01.dmp
LVL 26
akahanAsked:
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.

optomaCommented:
Hi Akahan,
Mbam.sys
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
B HCommented:
seems that you might want to uninstall malwarebytes, maybe reinstall it

here's the output of your dumps:


Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

mini040710-01.dmp:

Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.091208-2036
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Apr  7 15:11:32.858 2010 (GMT-4)
System Uptime: 2 days 14:25:34.343
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, 87edf470, 87edf4d0, a0c0009}

Unable to load image mbam.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mbam.sys
*** ERROR: Module load completed but symbols could not be loaded for mbam.sys
Probably caused by : mbam.sys ( mbam+120b )

-------------------------------------------------------------------------------------------------
mini041010-01.dmp

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.091208-2036
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sat Apr 10 13:43:48.796 2010 (GMT-4)
System Uptime: 1 days 15:56:36.363
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image mbam.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mbam.sys
*** ERROR: Module load completed but symbols could not be loaded for mbam.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e5b31000, 0, 8053a5a3, 1}


Could not read faulting driver name
Probably caused by : mbam.sys ( mbam+162c )

Open in new window

0
akahanAuthor Commented:
Thanks to both of you!
0
optomaCommented:
No prob ;)
0
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
Microsoft Legacy OS

From novice to tech pro — start learning today.