• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1311
  • Last Modified:

Repeated blue screen on Windows Server 2008

I have a Windows Server 2008 64bit Datacenter edition server running in a VMWare environment with a RHEL 5 host. I have just set this machine up, and I'm getting a blue screen, seemingly at random. I had this same issue with a Server 2003 VMWare guest on the same physical host machine.

The server is an Active Directory Domain Controller. It also hosts the DNS and IIS roles, and is protected by Symantec Endpoint Protection. What other information, logs, etc can I provide to help with the diagnosis? It is somewhat important that I get this working properly, so any help would be much appreciated. Thanks!

Best Regards,
Martin Schultz
0
WideAreaMedia
Asked:
WideAreaMedia
  • 6
1 Solution
 
WideAreaMediaAuthor Commented:
This is also happening repeatedly to a Windows Server 2003 install. I am running VMWare version 2.
0
 
ccnsCommented:
I would say if you are running both of these installs from the one server, that possibly the ram is faulty or some part fo the hardware is faulty. bluescreens do not happen out of no where and most of the time related to hardware... do you have spare ram to test with or can reseat the ram on the server?
0
 
WideAreaMediaAuthor Commented:
ccns, that was one of my thoughts as well. The box is hosted at a dedicated box provider, so I don't have access to it. However, if there is a simple RAM test utility that I can find that will run under RHEL that shows something is wrong, they're very responsive about fixing problems.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
WideAreaMediaAuthor Commented:
I'm also seeing the following:

[2008-10-13 17:38:29.951 'Vmomi' 1078245696 info] Activation [N5Vmomi10Activatio
nE:0x1333b060] : Invoke done [setScreenResolution] on [vim.VirtualMachine:144]
[2008-10-13 17:38:29.952 'Vmomi' 1078245696 info] Throw vmodl.fault.SystemError
[2008-10-13 17:38:29.952 'Vmomi' 1078245696 info] Result:
(vmodl.fault.SystemError) {
dynamicType = <unset>,
reason = "Unknown error",
msg = ""
}
0
 
WideAreaMediaAuthor Commented:
I've attached a few of the Server 2003 guest's minidump files. I had to append a .txt extension to the files in the archive so that EE would let me attach them.
Mini101308-02.dmp.zip
0
 
WideAreaMediaAuthor Commented:
I ended up getting a new host server, which seems to have resolved the issue. I was unable to determine the underlying cause on the old host.
0
 
WideAreaMediaAuthor Commented:
I should also note that the datacenter tested the RAM, and it showed no issues.
0
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.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now