To analyze memory dumps, try this: http://blogs.technet.com/b
Main Topics
Browse All TopicsA client's server starting rebooting by itself. When it come back up and you log on, the reason reported is...
Reason Code: 0x805000f
Bug ID:
Bugcheck String: 0x000000cb (0x8091f634, 0x80833bdf, 0x898a5ba8, 0x00000001)
Comment: 0x000000cb (0x8091f634, 0x80833bdf, 0x898a5ba8, 0x00000001)
This is also then written into the event viewer. I havd a MEMORY.DMP file too, but no idea how to read it. Is it something I need to send to MS, or can someone here advise? I would upload, but it is 45MB.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
To analyze memory dumps, try this: http://blogs.technet.com/b
I will try this soon, and report back as soon as I can.
To analyze memory dumps, try this: http://blogs.technet.com/b
You may have a known bug in Microsoft 2003 server>
http://support.microsoft.c
I applied the hotfix from http://support.microsoft.c
Did not help.
Try this hotfix:
http://support.microsoft.c
The stop error you are receiving is indicative of your backup software. Stop errors can usually pinpoint the problem well. Check out your hotfix.
System restore is not the only place you can reboot upon error. Each services, in services.msc, will stop upon error if elected. For your situation, you could look at the redirector services and see if any are elected to reboot upon error.
OK, thanks for all the input. The rogue driver causing the reboots was a Juniper Network Driver. Apparently someone from the company that used to provide them support installed some Junpier Networking product, and that driver/product is NOT compatible with SBS 2003. Odd it just started to happen, becuase it had to have been installed on there for a while. A recent update probably caused the conflict? Anyway, removed all the remnants of the Junpier software and drivers. No more rebooting. You were all helpful.
/issue.
Business Accounts
Answer for Membership
by: cshepfamPosted on 2008-04-25 at 13:36:01ID: 21443018
take a look at this:
m/archive/ index.php? t-11025.ht ml
http://forums.msrportal.co