Logical and Vitrual disk manager entered stop state

Two days after applying service pack 2 we started to experience several reboots back to back. Fours days later we had 8 reboots back to back and then twice later on in the day. At first it looked like it was contributed to a terminal session login that failed to install the printers but later it looked as if it were related to the CERC card drivers being outdate per SP2.  We keep seeing "The Virtual Disk Service service entered the stopped state" and "The Logical Disk Manager Administrative Service service entered the stopped state." We are planning an update to the controller tonight to eliviate the problem. Has anyone experienced this beofre or found a solution?

Event Type:      Information
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7036
Date:            10/23/2008
Time:            10:07:01 PM
User:            N/A
Computer:      PPSFSHQ001
Description:
The Logical Disk Manager Administrative Service service entered the stopped state.

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

------------------------

Event Type:      Information
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7036
Date:            10/23/2008
Time:            10:07:01 PM
User:            N/A
Computer:      PPSFSHQ001
Description:
The Virtual Disk Service service entered the stopped state.

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

----------------------------

Event Type:      Error
Event Source:      System Error
Event Category:      (102)
Event ID:      1003
Date:            10/22/2008
Time:            10:40:39 PM
User:            N/A
Computer:      PPSFSHQ001
Description:
Error code 00000050, parameter1 dba18878, parameter2 00000001, parameter3 de3fb554, 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 30 30 30 30 30 30 35    0000005
0020: 30 20 20 50 61 72 61 6d   0  Param
0028: 65 74 65 72 73 20 64 62   eters db
0030: 61 31 38 38 37 38 2c 20   a18878,
0038: 30 30 30 30 30 30 30 31   00000001
0040: 2c 20 64 65 33 66 62 35   , de3fb5
0048: 35 34 2c 20 30 30 30 30   54, 0000
0050: 30 30 30 30               0000    
LVL 4
bmonroe44Asked:
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.

bmonroe44Author Commented:
After updating the controller firmware and updating the drivers we eliinated the stopped state issue. We also fixed the RDP issue by updating the video drivers on the server.
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
Microsoft Server OS

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.