Build 3036 - BSOD
 

My system:
Windows XP Professional, member of domain

Steps:
1.Upgrade to 3036
2. Upgrade Parallels Tools
3. Work for a while. Loving coherence
4. Switch networking mode from Shared to Host-only on the fly --> No longer have network connection
5. Switch back to Shared --> Still no connection
6. Restart VM
7. BSOD: PAGE_FAULT_IN_NONPAGED_AREA
8. Boot in Safe mode, uninstall tools
9. Boot normally --> all is well.
10. Reinstall tools, restart VM --> BSOD: PAGE_FAULT_IN_NONPAGED_AREA
11. Unable to uninstall tools at this point.

Would love to know how to uninstall the tools completely, to see if that fixes issue.

Thanks

I have exactly the same problem now here, yet it worked flawlessly from Dec 1 until Dec 5. It started failing today, yet, I haven't touched any network mode setting recently, neither in the VM, neither the mode, neither anything network related on Mac OS X itself.
I'm a bit puzzled. I will revert to build 1970 if I don't find a workaround very quickly.

[QUOTE=Olivier]I have exactly the same problem now here, yet it worked flawlessly from Dec 1 until Dec 5. It started failing today, yet, I haven't touched any network mode setting recently, neither in the VM, neither the mode, neither anything network related on Mac OS X itself.
I'm a bit puzzled. I will revert to build 1970 if I don't find a workaround very quickly.[/QUOTE]

Doesn't the new version upgrade the files?

T

[QUOTE=debtoine]Doesn't the new version upgrade the files?[/QUOTE]
Don't you have backups when testing beta software? I do have. ;-)
But anyway, I properly fully uninstalled Tools from the VM using Safe mode, then shtudown VM, uninstalled Parallels 3036, installed Parallels 1970, boot my VM, install the 1970 Tools and all is well.

I can't uninstall in safe mode :(

Says something about the previous install never being finished.


T

According to Microsoft's diagnosis of the BSOD error, the problem lies in a driver. I've noticed that if I "Start with Last Known Good Configuration" some updates are rolled back and it works fine. I can reproduce this error by doing the following:

1. Create new VM in Build 3306.
2. Install Windows XP using custom method, not the automated (express) method.
3. Install Service Pack 2.
4. Install all updates.
5. BSOD.

I should note that after rebooting from step 4 is when I get the BSOD.

Bsod
 

I am also experiancing BSOD with my VMs. I happens after installing the Parallels tools. If I uninstall them and reboot everything is ok. If I boot from a previous good configuration everything is ok. But once I install the tools and reboot it BSODs on me. I've tried two different VMs with the same results.

I'm also having the exact same problem.

I got my VM working again, but like the others - as soon as I install the tools, I BSOD.

T

[QUOTE=Olivier]I have exactly the same problem now here, yet it worked flawlessly from Dec 1 until Dec 5. It started failing today, yet, I haven't touched any network mode setting recently, neither in the VM, neither the mode, neither anything network related on Mac OS X itself.
I'm a bit puzzled. I will revert to build 1970 if I don't find a workaround very quickly.[/QUOTE]

This is exactly what happened to me., Everything was working fine until 2 days ago, then Parallels rebooted "for no reason" in the background and now all I get is a BSOD. I'm unable to uninstall the tools, keeps telling me I need to restart the VM. Tried various safe modes, no luck. Uninstalled beta and tried reinstalling 1970, no luck with installing "new" old tools.

[QUOTE=glows]This is exactly what happened to me., Everything was working fine until 2 days ago, then Parallels rebooted "for no reason" in the background and now all I get is a BSOD. I'm unable to uninstall the tools, keeps telling me I need to restart the VM. Tried various safe modes, no luck. Uninstalled beta and tried reinstalling 1970, no luck with installing "new" old tools.[/QUOTE]
1)
If when booting in Safe Mode, you can't uninstall the Tools because it tells you their installation must first be completed, then shutdown and reboot on Last Known Good configuration. Do run the Tools uninstaller. Then do a normal boot to check that the tools are gone away and that you don't have the blue screen anymore.
2)
Shutdown your XP, close Parallels application.
Open the 3036 dmg and run the installer you find there.
Shtudown / restart the Mac OS X.
3)
Install Parallels 1970.
Start you VM, and install the tools (those will be the 1970 tools).

This recovered it for me, despite what my signature reads below this post, I'm now on 1970, I'll come back to 3??? when I'll see there is hints this problem might be fixed.

Thanks, Oliver, no luck. It would be good to know how to manually get rid of the tools.

Salut

I've got the same problems on a ImacCoreDuo20" trying to boot Parallels's BootCamp partition :

-The partition has been recognize but the process stoped in the WindowXP black screen just before the "welcome" and a blue screen appears with a long text saying there's a problem and just hang-on………………

So I reboot in 'safe mode'.

To get ride of the Tools :

The uninstaller didn't manage to do it in 'safe mode' so i've search for all stuff named 'parallels' and throw it in the "corbeille".
Then execute 'regedit' and search for all 'parallels' stuff and delete it again and again (many keys).

Reboot in normal mode and it's done.


What is a BSOD ?

n'tcha

BSOD = [B]B[/B]lue [B]S[/B]creen [B]O[/B]f [B]D[/B]eath ;)

I have this exact problem. Everything was working yesterday. Today, BSOD with the PAGE_FAULT_IN_NONPAGED_AREA error. I hate this. I didn't do anything!!! I know this is beta stuff, but I figured it was safe to assume that if it was working yesterday, and I didn't change anything, that it'd be working today. If anyone figures this one out, please let me know.

For your info,
I CAN boot into safe mode in Parallels.
I CAN boot into bootcamp regularly.

Problems with copy-protected programs...
 

I need to use a number of copy-protected programs in my work. I was able to load almost all of these in the prior stable build. Now, in the 3036 build, they often bomb when I try to launch them, sending an automatic message to Parallels. If I try to delete and re-install, the virtual machine bombs and sends a bug report at the moment the install program is trying to install the copy protection. :(

These are important programs used very widely in psychology and psychiatry to administer and score psychological tests. They all appear to use a copy protection scheme involving sub-routines named CCChange and CCMove.

Is Parallels aware of this problem? Is any work being done on it? How soon might it be fixed? I am wondering whether to revert to the old build and re-install the psych testing programs, but like many of the new features.

Thanks for any help.

[B]I FIXED IT!!!!![/B]

In another thread here: [url]http://forums.parallels.com/thread6263.html[/url]
It seems that the common thread was people who shut down the VM in coherence mode while plugged into a big monitor. Here is the solution, and without crazy reinstalls! (or at least, how I did it).

1) Uninstall paralells tools.
You might have to boot into safe mode to do this. If it says you have to complete the installation before you can uninstall, reboot in "Last Known Good" mode, and then uninstall. Restart vm into regular mode.

2) [b]Set the resolution in the VM to the same resolution as the last time you shut it down[/b] (i.e. on your big monitors). For me, this was 1920x1200. This is the critcal step.

3) NOW, reinstall paralells tools. Restart. Hooray!

4) Don't be stupid next time, and shut down only in (small) windowed mode.

Hope this helps.

I noticed that too. The following may be slightly easier:

1. When booting XP, press F8 until you see the "Windows Advanced Options Menu".
2. Select "Enable VGA Mode"
3. XP should boot in a low-color, small-screen mode. You can then adjust the screen size and reboot in normal mode.

enjoy,
m

[QUOTE=parsec]I noticed that too. The following may be slightly easier:

1. When booting XP, press F8 until you see the "Windows Advanced Options Menu".
2. Select "Enable VGA Mode"
3. XP should boot in a low-color, small-screen mode. You can then adjust the screen size and reboot in normal mode.

enjoy,
m[/QUOTE]


This is a great, and much more elegant solution. Good thinking.