Home > Windows 2000 > Windows 2000 Blue Screen P2v

Windows 2000 Blue Screen P2v

However - the only thing that I did to fix it was downloaded the SP4 rollup, Go to Solution 3 3 2 +1 4 Participants za_mkh(3 comments) LVL 21 VMware19 Virtualization8 My current version was 5.0.2195.7017 and I needed 5.0.2195.7059. Quote from MS KB904374: "This problem occurs because of a code problem in the Scsiport.sys driver that is included in Update Rollup 1 for Windows 2000 SP4". CAUSE Update Rollup 1 for Windows 2000 SP4 (KB891861) was probably not installed before doing the conversion. his comment is here

I did the same for 3 other W2K servers that were giving me fits after P2Ving them and they all worked. Follow the instructions that appear on the screen, type the Administrator password, and then press ENTER. Have fun! Back in the day the very best conversion utilty was PlateSpin PowerConvert. https://communities.vmware.com/thread/206168?tstart=0

Join the community of 500,000 technology professionals and ask your questions. TechNet Products IT Resources Downloads Training Support Products Windows Windows Server System Center Browser   Office Office 365 Exchange Server   SQL Server SharePoint Products Skype for Business See all products I downloaded and extracted Hotfix from KB904374 and copied files to virtualized server. share|improve this answer answered Jun 1 '09 at 16:22 Sage 1112 This worked for me, as well.

There are "Rollups" with SP4. –andyhky Jun 1 '09 at 19:56 add a comment| 5 Answers 5 active oldest votes up vote 0 down vote accepted http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005208 I injected the SCSI Blog at WordPress.com. Boot virtualized server and "Voila" Windows 2000 virtualized server is now booting. d.

Since this is a really old server, my estimation is about 8 years, the best solution was to virtualize it. Let’s just say we aren’t concerned with all of the technicalities and want to fix it. Click Repair your computer. http://enterpriseadmins.org/blog/virtualization/windows-2000-p2v-blue-screens/ strcat implementation Is this Tic-Tac-Toe board valid?

Acronis backs up entire PC or Mac with patented reliable disk imaging technology and you will be able to restore workstations to a new, dissimilar hardware in minutes. 30 Day Free If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity vSphere - automatic migrating and errors 9 50 26d Adding JBOD to Required fields are marked *Comment Name * Email * Website CAPTCHA Code * Notify me of followup comments via e-mail. PROBLEM:If you migrate a Windows 2000 server and it finishes fine, but during boot up you get a BSOD;STOP: 0x0000001E (0xC0000005, 0x8045D9BF, 0x0000000, 0x001A0018)KMODE_EXCEPTION_NOT_HANDLEDAddress 8045D9BF base at 80400000, Datestamp 45069e6e -

Virtualizing Windows 2000 server (P2V) Virtualization and SAN upgrade on Windows 2003 clu... ► November (2) ► January (2) Simple template. https://social.technet.microsoft.com/Forums/windowsserver/en-US/89a25e51-6f80-48d2-9d73-383ff8b99c68/blue-screen-when-doing-p2v?forum=winserverhyperv The PC is a standard Pentium with IDE disk from circa 2001. I also tried changing Scsiport.sys with some older and newer versions and didn't help either. Is my understanding correct? 0 LVL 118 Overall: Level 118 VMware 110 Virtualization 70 Message Active today Expert Comment by:Andrew Hancock (VMware vExpert / EE MVE) ID: 354047552011-04-15 yes, we

Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com Marked as answer by Vincent HuModerator Monday, March 28, 2011 6:47 AM Friday, March 25, 2011 4:09 PM Reply | Quote Moderator this content I would add, make sure you have a backup of the current VM, before you start making any of these changes, before you make the situation worse. 0 LVL 118 Join our community for more solutions or to ask questions. Share This Page Legend Correct Answers - 10 points Fix Windows 2000 Vmware P2V BSOD with KMODE EXCEPTION NOT HANDLED From BonusBits Jump to: navigation, search Contents 1 PROBLEM 2 CAUSE

The OS lacks many of the hardware compatibility features that make Server 2008 really easy, and Server 2003 relatively easy to move between hardware. You don't need to do that, because you already have the image. Thank you for your help! 0 Comment Question by:bvoris Facebook Twitter LinkedIn https://www.experts-exchange.com/questions/24553940/Blue-Screen-ON-VM-After-P2V-Conversion-of-Windows-2000-Server.htmlcopy Best Solution bybvoris All, Thank you for the responses to the question. weblink Didn't help. 4.

Go find an ISO or DVD of any of the operating systems just listed in the title. We’ll assume you are using Windows 2003 media. Retrieved from "https://www.bonusbits.com/index.php?title=HowTo:Fix_Windows_2000_Vmware_P2V_BSOD_with_KMODE_EXCEPTION_NOT_HANDLED&oldid=162" Categories: HowToVmwareWindows Navigation menu Personal tools Log in Namespaces HowTo Discussion Variants Views Read View source View history More Search Navigation Main pageLatest ArticlesLatest Updates Top Namespaces How

I recently had two older model Compaq servers blue screen after a P2V conversion.

b. Back in the day the very best conversion utilty was PlateSpin PowerConvert. However - the only thing that I did to fix it was downloaded the SP4 rollup, installed in on the Windows 2000 server and reran the VConvertor to do a P2V A clock for 2017 Triptych of Animal Cryptics What is a good alternative for the reverse of a boycott?

I recently had two older model Compaq servers blue screen after a P2V conversion. What fixed the issue was the info initially provided by za_mkh. The solution that worked was: 1. check over here We’re going to use the recovery console.

How to prevent a thief from using my iPhone ever? Show 3 replies 1. In fact diskpart wouldn't let me change the correct partition to the C: drive. If you don't have one, eBay is probably the best place to try and purchase one. 0 Message Author Closing Comment by:btny ID: 355136132011-05-03 This did the trick, I had

RebootNOTE if you need to you can change the settings on startup by editing the VM settings/options for boot time this is in milliseconds so set it HIGH.