Home > Blue Screen > Blue Screen After P2v Windows 2000 Server

Blue Screen After P2v Windows 2000 Server

See http://support.microsoft.com/kb/263532 for details. sorry for a dumb question. My VMware | VMware.comSearch ActivityBrowseAll ContentBlog PostsDiscussionsDocumentsPollsBookmarksPopular tagsCommunitiesGroupsPeopleLog inRegisterHomeVMTN Forums Mobile AppsBlogsTwitterFacebookGoogle+LinkedInYouTubeGroupsPodcasts vSphere NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware Converter What can be wrong? his comment is here

Reply John Zoch says: February 15, 2016 at 10:03 pm Thank you! Connect to CD/DVD to BartPEClick on Fix VM SCSIMap to Windows DirectoryIf this is 2000 server install BUS adapter, if 2003 LS Logic, if NT then install the NT one. You'll need to reinstall all the service packs again. Reply Back says: May 4, 2015 at 1:21 pm Hello all, Thank Mike for your nice help … but i have bsod again on my vhdx (windows XP). https://communities.vmware.com/thread/206168?tstart=0

Reply Dminard says: October 28, 2015 at 10:28 pm Just used your method for a 2k8 R2 P2V Conversion to successfully fix our blue screen issue. After a couple of attempts I thought I was fighting a lost cause. One .vhd came from a laptop and the other from a HP workstation, but both yield the same stop error when booting in Hyper-V on Windows 8.1. Thanks for sharing how to fix this Michael.

Reply Michael Mollet says: May 11, 2015 at 5:33 am hah, after trying only to p2v drive c it worked … Reply NOEL says: June 3, 2015 at 7:28 pm Flawless! If you want an easy way to do this download Symantec Backup Exec System Recovery Server trial copy, install on the server and image. This saved my day 🙂 Reply Nicolas R. Word for unconscious body movements What is the source of the fable of Thor’s attempt to drink up a small spring?

I updated the post. Without it the drivercrashes the system at boot. Reply alex says: November 14, 2014 at 7:34 pm Genius! 🙂 Reply jan says: December 4, 2014 at 11:05 am Thanks! Take into account the following scenario.

You need to take a server level backup, then restore this to a new installation of Server 2000 (where the exact same patch levels have been installed). STOP 0x7B INACCESSIBLE_BOOT_DEVICE or STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE And of course I could not boot the converted machine. Powered by Blogger. should i not put them under HKEY_LOCAL_MACHINESystemControlSet001Servicesatapi or leave out system?

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. http://enterpriseadmins.org/blog/virtualization/windows-2000-p2v-blue-screens/ Reply Carlos says: March 16, 2016 at 10:45 am Capo total ! ! ! ! Popular Posts The Unofficial VMware Visio Stencils The VMware Visio Stencils I have created are by far the most popular post on my blog. Reply Hector Forcelledo says: October 15, 2015 at 1:47 pm Thanks Mike!!!!

more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed this content After successful first boot I prepared virtualized machine as described in my previous blog. CAUSE Update Rollup 1 for Windows 2000 SP4 (KB891861) was probably not installed before doing the conversion. I started searching and found it on some other W2k server.

Reply ChrAd says: December 13, 2016 at 8:47 pm Love it! Use vConverter to convert image to the ESX server, it knows about it natively and is usually seemless 0 LVL 21 Overall: Level 21 VMware 19 Virtualization 8 Message Assisted asked 7 years ago viewed 13055 times active 5 years ago Blog Stack Overflow Podcast #96 - A Face Full of Code Related 1Will VMWare Converter P2V a non-ACPI 2000 server?3VMWare http://helpsbs.com/blue-screen/blue-screen-1033-windows-server-2008.html Yey! - But - the conversion process - reported as failed somewhere between 97-99%.

Legal/emotional/behavioral repercussions of a punishment Does Avada Kedavra only damage the caster's soul *when it kills someone?* Why does NASA's B-52 008 have a smoking engine in this photograph? We can finally connect a USB device t... I have a random scenario: we have a windows 2k box that was p2v'd successfully, after trying to do an in place upgrade to 2k3, we get the BSOD related to

I have gone through and verified the drivers/registry are correct.

Just make sure you modify your .reg file to match what you have on your system. I copied the known working copy of SCSIPORT.SYS from C:\WINNT\System32\Drivers to my second drive (E:\WINNT\System32\Drivers\SCSIPORT.SYS). View Public vExpert Directory Search for: Categories Messaging (10) Scripting (105) Uncategorized (1) Virtualization (119) Archives Archives Select Month September 2016 (3) June 2016 (1) January 2016 (1) August 2015 (2) Thanks a lot!!!

If so raise you hand! Reply Not_So_Ninja says: April 13, 2015 at 7:51 pm I appreciate all the information that has been give in this post. You'll need to know the administrator password. check over here HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BusLogic HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\ pci#ven_104b&dev_1040 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmscsi (Note: The vmscsi service registry key may not exist if VMware Tools is not installed on the virtual machine.) Import these 3 registry keys onto your source

I recently had two older model Compaq servers blue screen after a P2V conversion. Running 2012 R2 Hyper-V Host. All rights reserved. It is painful.

Posted by luka at 7:55 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: windows 2000 p2v VMware Converter bsod Scsiport.sys 2 comments: AnonymousMarch 29, 2012 at 4:32 PMWhat version VMware Converter no longer supports Server 2000. This was also my suggestion for the customer. Like some said before, this should absolutely be worked out by Microsoft by now.

Reply MikesMMM says: January 23, 2014 at 1:48 am Thanks! I'm guessing there was a device driver misfiring. –Kara Marfia Jun 3 '09 at 20:01 add a comment| up vote 1 down vote the reason this happens is the physical disk Good Luck! In each case the server blue screened with an error “INACCESSIBLE_BOOT_DEVICE” after the conversion.

Reply anv says: June 27, 2015 at 12:38 pm Where i can mount vhd file..in Hyper-v server or local server.if hyper-V server how to i modify the registry. 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 Thank you Sir! you have a Windows 2000 SP6 Server running a customized app.

Just ran into this after doing a disk2vhd on a Windows 2008 R2 install for a Hyper-v 2012 R2 guest conversion and your fix did the trick. Like Show 0 Likes (0) Actions 3. How do professional bakers mass produce cookies/muffins/cakes/etc Plausible Original Concept For High-Fidelity Apocalypse? It just won't boot! –PowerApp101 Jun 1 '09 at 10:35 add a comment| up vote 1 down vote To be clear on the 'reinstall Windows 2000' you boot from Windows 2000

And most other conversion products have dropped support as well. It's never happened for Windows 2003 servers that I've P2Ved, I'm wondering if it's just a Win2000 thing. –PowerApp101 Jun 1 '09 at 9:42 I've just read the blog