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

VMware 3.1 & 3.0.3 - blue screen 64bit Win2003 EE

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
kgeddes
Asked:
kgeddes
  • 4
  • 2
1 Solution
 
ConUladhCommented:
Can you upload a screenshot of the edit settings screen of the VM?

Also is the correct OS selected on the options tab?

0
 
kgeddesAuthor Commented:
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
 
bgoeringCommented:
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
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
kgeddesAuthor Commented:
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
 
bgoeringCommented:
Thanks - can never have too much information when diagnosing an issue :)
0
 
kgeddesAuthor Commented:
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
 
kgeddesAuthor Commented:
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

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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