Jump to content

Blue Screen Windows Vista Macbook Pro C2D


spiral
 Share

Recommended Posts

Hello,

I've installed Windows Vista Business on my Macbook Pro Core 2 Duo in order to do some testing, with a whole lot of drivers, and everything is working... Except that any time I logout (only logout, neither reboot nor shutdown), I get a BSOD.

As a Mac and Linux user, I'm not really a professionnal of the BSOD memory addresses, which are kinda hard to understand and analyze... The bsod says Win32k.sys is failing, and I provide a minidump attached to this post. I didn't manage to get any usefull information from it, but I hope someone here might have a bigger windows BSOD background than me and might be able to help me to find what's wrong.

Thanks in advance for your help,

Mini030507_02.dmp.zip

Link to comment
Share on other sites

The mini dump is very hard to decipher. What would help even more is if you provided the STOP code you recieve.

such as STOP 0x0000008.

All right, the message was : "STOP 0x0000008E"

After that, it went on saying 0xC0000005, 0X924686C6,0x95F53CD0,0x00000000

And then : "Address 924686C6 base at 924000 Part stamp 4545aea2

I hope this helps, thanks

Link to comment
Share on other sites

That error code relates to RAM errors.

For WXP, the explanation and remedy is given here I can only assume it is similar for Vista.

Hmmm, that's kinda weird, because I've already tested all my ram with "memtest86+" and there's no problem at all. What is more, macos runs absolutely fine on this computer, with the whole 2Gb of ram...

Btw, this problem does not happen during installation of vista, or during "current usage", but only for logout... Not even on shutdown or restart...

Link to comment
Share on other sites

Things are complicated by the fact you are running Windows on a Mac machine. It could be that normal error messages don't apply.

As the BSOD only happens on shutdown, presumably the system works OK before that, and you are only doing testing work is it too much of a problem or, do you want this setup to be permanent?

Link to comment
Share on other sites

Hmmm, first of all, the problem only happens on logout (I'dd say more presumably when the login screen is trying to appear, after the logout procedure is complete) and not on restart or shutdown.

Yes, of course, I could definitevely live without it, as I could definitively live without Windows as well thanks to MacOs, but as a matter of fact, I use Windows sometimes, and I sometimes have to logout of my session, and restarting the whole system is quite boring (what is more, it's slightly longer than a MacOs startup).

Concerning the fact that the error messages should not be the same on a Mac Hardware, I don't understand why... For windows, my Mac is a PC with a bios, no more no less... I used bootcamp, so I don't even use EFI...

I hope someone here might have another clue.

Thanks in advance for your help

Link to comment
Share on other sites

http://msdn2.microsoft.com/en-gb/library/ms794023.aspx

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

Update your drivers, bios, and disable any memory options as stated above.

Link to comment
Share on other sites

http://msdn2.microsoft.com/en-gb/library/ms794023.aspx

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. Make sure you have enough disk space. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

Update your drivers, bios, and disable any memory options as stated above.

All drivers are as recent as possible, there is no bios update (Bootcamp...), and I can't change any setting in the BIOS. Isn't there a way to know at least what driver is failing using the minidump as I could do on Linux or Macos?

Thanks again for your help

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy