asked on

Unexpected server reboots, Reason Code: 0x805000f

A 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.

Coolie Sheppard

take a look at this:

http://forums.msrportal.com/archive/index.php?t-11025.html

ASKER CERTIFIED SOLUTION

MidnightOne

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SundeyPSU

ASKER

I will try this soon, and report back as soon as I can.

To analyze memory dumps, try this: http://blogs.technet.com/brad_rutkowski/archive/2006/09/09/455032.aspx

ChiefIT

You may have a known bug in Microsoft 2003 server>

http://support.microsoft.com/kb/937455

SundeyPSU

ASKER

I applied the hotfix from http://support.microsoft.com/kb/937455

Did not help.

SundeyPSU

ASKER

I also tried to analyze memory dumps as suggested above. Getting a message that the file is corrupt or unreadable. I deleted the file, so it would be created new (even though it is set to overwrite anyway), and same thing. File is corrupt or unreadable.

MidnightOne

You may want to turn off the automatic reboot on BSOD sdo you can get the name of the offending driver.

SundeyPSU

ASKER

Ref : MidnightOne:You may want to turn off the automatic reboot on BSOD sdo you can get the name of the offending driver.

In system, start up and recovery settings the "automatically restart" was already/has been disabled.

ChiefIT

Try this hotfix:
http://support.microsoft.com/kb/825760

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.

SundeyPSU

ASKER

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.

ChiefIT

This is good news. Glad to see you fixed it.