Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

VMware 3.1 & 3.0.3 - blue screen 64bit Win2003 EE

Posted on 2010-08-24
7
Medium Priority
?
556 Views
Last Modified: 2012-05-10
We are trying to buld a VM = 64bit-Win-2003-EE on a SunFire-x4600 platform with CPU=Dual Core AMD Operton-8220 which is a few years old. Linux 32 and 64bit work fine as does 32bit Win 2003. We have a combination of VMware 3.1 & 3.0.3. It goes through the bulk of the 64bit Win2003 build until whilst copying images, it blue screens pointing at "setupdd.sys"
stop:0x000000BE , Address FFFFFADF97B5CF44 , Base at: FFFFFADF97B4E000

We suspect hardware as a contributing source but, we also suspect our image although we have tried all sorts. Any help gratefully received.
0
Comment
Question by:kgeddes
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
7 Comments
 
LVL 8

Expert Comment

by:ConUladh
ID: 33509755
Can you upload a screenshot of the edit settings screen of the VM?

Also is the correct OS selected on the options tab?

0
 

Author Comment

by:kgeddes
ID: 33511290
Unfortunatley can not do that from the server environment but, can assure you that the correct OS is select and this image has worked on another IBM server. Thus we are now not supecting the image more the hardware platform.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 33527135
At this point I would edit settigns on the VM then

remove the hard drive (delete from disk)

create a new hard drive

Try the install again... Its possible something got messed up on earlier install attempt that won't let you continue. This should be a fresh start.

Let me know
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 

Author Comment

by:kgeddes
ID: 33534300
Been there done that a number of times, even tried different makes of server. Suspect driver now will try and get the text of the crash, that may help since its the same crash, same time and on multiple servers.
0
 
LVL 28

Expert Comment

by:bgoering
ID: 33534357
Thanks - can never have too much information when diagnosing an issue :)
0
 

Author Comment

by:kgeddes
ID: 33565818
We have switched to an newish IBM-3850 M2 server and exactly the same stop error as mention above happens at the same place in the build, i.e. when part way through copying windows o/s files to the instal directory. Tried another image, also can use 32bit images no problem.  Think it has to be something about running 64 bit VM image. Just do'nt get this error stating that the stop error was due to "an attempt being made to write to read only memory", when it was simply copying files to disk are and most had already gone through.
0
 

Accepted Solution

by:
kgeddes earned 0 total points
ID: 33577320
Think the final solution to this one is going to centre around  AMD-V and/or Intel-VT bios revisions and settings. We are down that route as I write.
0

Featured Post

On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct.  It's a good idea to compare checksums, because many installat…
Teach the user how to rename, unmount, delete and upgrade VMFS datastores. Open vSphere Web Client: Rename VMFS and NFS datastores: Upgrade VMFS-3 volume to VMFS-5: Unmount VMFS datastore: Delete a VMFS datastore:
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.

721 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question