Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

0 points

OS X Mavericks (10.9): Why MS PowerPoint will not go into FULL screen mode?

Hello,

This is my first time turning to the Apple community for some feedback on my current issue. I've had this really bizzare error with Microsoft PowerPoint functioning improperly on the NEW OS X Mavericks (10.9) that I've uprgaded to last night.

Everything works fine until I enter into a FULL SCREEN mode, after which PowerPoint crashes.

It was working great prior to the upgrade! I use it to play PowerPoint slides for a class presentation, so some quick insight on what's happening would be very helpful! ASAP!

I've added pics and hopefully someone has a solution. Perhaps Apple will be able to fix this issue in the next update, in case it has anything to do with the compatability with the new OS!

Thanks a lot in advance!

After clicking on "More Information" button, here is the full ERROR message content:

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_BAD_ACCESS

Date/Time: 2013-10-24 05:10:03 +0000

Application Name: Microsoft PowerPoint

Application Bundle ID: com.microsoft.Powerpoint

Application Signature: PPT3

Application Version: 14.0.0.100825

Crashed Module Name: unknown

Crashed Module Version: unknown

Crashed Module Offset: unknown

Blame Module Name: unknown

Blame Module Version: unknown

Blame Module Offset: unknown

Application LCID: 1033

Extra app info: Reg=en Loc=0x0409

Crashed thread: 0

Thread 0 crashed:

# 1 0x4655b283 in ( + 0x00000000)

# 2 0x007f4190 in ( + 0x00000000)

# 3 0x0011a341 in ( + 0x00000000)

# 4 0x007c3869 in ( + 0x00000000)

# 5 0x007c5a04 in ( + 0x00000000)

# 6 0x007be9a8 in ( + 0x00000000)

# 7 0x007bea27 in ( + 0x00000000)

# 8 0x0127c4ad in ( + 0x00000000)

# 9 0x93dcfbe0 in ( + 0x00000000)

# 10 0x9c14f186 in ( + 0x00000000)

# 11 0x9c14eb43 in ( + 0x00000000)

# 12 0x9c1c92ad in ( + 0x00000000)

# 13 0x9c1066c3 in ( + 0x00000000)

# 14 0x9c105d5a in ( + 0x00000000)

# 15 0x9c105bbb in + 0x0000E7F0 ( + 0x00000000)

# 16 0x93c38e2d in ( + 0x00000000)

# 17 0x93c38a47 in ( + 0x00000000)

# 18 0x93dd3a46 in ( + 0x00000000)

# 19 0x93dd3aaa in ( + 0x00000000)

# 20 0x02c6d914 in ( + 0x00000000)

# 21 0x000e823a in ( + 0x00000000)

# 22 0x000e361d in ( + 0x00000000)

# 23 0x000e31b2 in ( + 0x00000000)

X86 Thread State:

eax: 0x006f0007 ebx: 0x7d675b28 ecx: 0x05fb9500 edx:0x7d5ad988

edi: 0x00000000 esi: 0x7d675b28 ebp: 0xbff1e6f8 esp:0xbff1e6dc

ss: 0x00000023 eip: 0x4655b283 cs: 0x0000001b ds:0x00000023

es: 0x00000023 fs: 0x00000000 gs: 0x0000000f eflags:0x00010206

Thread 1:

# 1 0x96f86992 in ( + 0x00000000)

# 2 0x91e49556 in ( + 0x00000000)

X86 Thread State:

eax: 0x00000171 ebx: 0xb00926a0 ecx: 0xb009267c edx:0x96f86992

edi: 0xb00926a0 esi: 0x91e497dd ebp: 0xb00926f8 esp:0xb009267c

ss: 0x00000023 eip: 0x96f86992 cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000286

Thread 2:

# 1 0x96f810a6 in ( + 0x00000000)

# 2 0x9ab837a0 in ( + 0x00000000)

# 3 0x03ae5252 in ( + 0x00000000)

# 4 0x03ae4920 in ( + 0x00000000)

# 5 0x03ae48ab in ( + 0x00000000)

# 6 0x03ae5e46 in ( + 0x00000000)

# 7 0x943465fb in ( + 0x00000000)

# 8 0x94346485 in ( + 0x00000000)

# 9 0x9434bcf2 in ( + 0x00000000)

X86 Thread State:

eax: 0xffffffa6 ebx: 0x00000d2e ecx: 0xb0218a6c edx:0x96f810a6

edi: 0x165bcb1e esi: 0x00000d2e ebp: 0xb0218ab8 esp:0xb0218a6c

ss: 0x00000023 eip: 0x96f810a6 cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000206

Thread 3:

# 1 0x96f857ca in ( + 0x00000000)

# 2 0x9434abd9 in ( + 0x00000000)

# 3 0x971f0922 in ( + 0x00000000)

# 4 0x971f0b46 in ( + 0x00000000)

# 5 0x971bc58b in ( + 0x00000000)

# 6 0x01272905 in ( + 0x00000000)

# 7 0x051184d6 in ( + 0x00000000)

# 8 0x0511738f in ( + 0x00000000)

# 9 0x0511759e in ( + 0x00000000)

# 10 0x05117d76 in ( + 0x00000000)

# 11 0x05117eba in ( + 0x00000000)

# 12 0x051e0a73 in ( + 0x00000000)

# 13 0x051190ed in ( + 0x00000000)

# 14 0x012736e2 in ( + 0x00000000)

# 15 0x971bd56e in ( + 0x00000000)

# 16 0x943465fb in ( + 0x00000000)

# 17 0x94346485 in ( + 0x00000000)

# 18 0x9434bcf2 in ( + 0x00000000)

X86 Thread State:

eax: 0x00000131 ebx: 0x00000860 ecx: 0xb011493c edx:0x96f857ca

edi: 0x00000100 esi: 0x00000001 ebp: 0xb01149c8 esp:0xb011493c

ss: 0x00000023 eip: 0x96f857ca cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000246

Thread 4:

# 1 0x96f80f7a in ( + 0x00000000)

# 2 0x9c106f69 in ( + 0x00000000)

# 3 0x9c106541 in ( + 0x00000000)

# 4 0x9c105d5a in ( + 0x00000000)

# 5 0x9c105bbb in + 0x0000E7F0 ( + 0x00000000)

# 6 0x93c38e2d in ( + 0x00000000)

# 7 0x93c38bb2 in ( + 0x00000000)

# 8 0x93dd3a46 in ( + 0x00000000)

# 9 0x93dd3aaa in ( + 0x00000000)

# 10 0x051246ef in ( + 0x00000000)

# 11 0x0511738f in ( + 0x00000000)

# 12 0x0511759e in ( + 0x00000000)

# 13 0x051241ac in ( + 0x00000000)

# 14 0x051ea244 in ( + 0x00000000)

# 15 0x051190ed in ( + 0x00000000)

# 16 0x012736e2 in ( + 0x00000000)

# 17 0x971bd56e in ( + 0x00000000)

# 18 0x943465fb in ( + 0x00000000)

# 19 0x94346485 in ( + 0x00000000)

# 20 0x9434bcf2 in ( + 0x00000000)

X86 Thread State:

eax: 0xffffffe1 ebx: 0xb0195d58 ecx: 0xb0195c3c edx:0x96f80f7a

edi: 0x00000c00 esi: 0x07000006 ebp: 0xb0195c78 esp:0xb0195c3c

ss: 0x00000023 eip: 0x96f80f7a cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000206

Thread 5:

# 1 0x96f857ca in ( + 0x00000000)

# 2 0x9434abd9 in ( + 0x00000000)

# 3 0x971f0922 in ( + 0x00000000)

# 4 0x971f0b46 in ( + 0x00000000)

# 5 0x971bc58b in ( + 0x00000000)

# 6 0x01272905 in ( + 0x00000000)

# 7 0x051184d6 in ( + 0x00000000)

# 8 0x0511738f in ( + 0x00000000)

# 9 0x0511759e in ( + 0x00000000)

# 10 0x05117d76 in ( + 0x00000000)

# 11 0x05117efa in ( + 0x00000000)

# 12 0x051e0e2c in ( + 0x00000000)

# 13 0x051e5c34 in ( + 0x00000000)

# 14 0x051e5e00 in ( + 0x00000000)

# 15 0x051190ed in ( + 0x00000000)

# 16 0x012736e2 in ( + 0x00000000)

# 17 0x971bd56e in ( + 0x00000000)

# 18 0x943465fb in ( + 0x00000000)

# 19 0x94346485 in ( + 0x00000000)

# 20 0x9434bcf2 in ( + 0x00000000)

X86 Thread State:

eax: 0x00000131 ebx: 0x00000860 ecx: 0xb029aa9c edx:0x96f857ca

edi: 0x00000100 esi: 0x00000001 ebp: 0xb029ab28 esp:0xb029aa9c

ss: 0x00000023 eip: 0x96f857ca cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000246

Thread 6:

# 1 0x96f80f7a in ( + 0x00000000)

# 2 0x9c106f69 in ( + 0x00000000)

# 3 0x9c106541 in ( + 0x00000000)

# 4 0x9c105d5a in ( + 0x00000000)

# 5 0x9c105bbb in + 0x0000E7F0 ( + 0x00000000)

# 6 0x01272fb1 in ( + 0x00000000)

# 7 0x01274bf9 in ( + 0x00000000)

# 8 0x012736e2 in ( + 0x00000000)

# 9 0x971bd56e in ( + 0x00000000)

# 10 0x943465fb in ( + 0x00000000)

# 11 0x94346485 in ( + 0x00000000)

# 12 0x9434bcf2 in ( + 0x00000000)

X86 Thread State:

eax: 0xffffffe1 ebx: 0xb05240b8 ecx: 0xb0523f9c edx:0x96f80f7a

edi: 0x00000c00 esi: 0x07000006 ebp: 0xb0523fd8 esp:0xb0523f9c

ss: 0x00000023 eip: 0x96f80f7a cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000206

Thread 7:

# 1 0x96f857ca in ( + 0x00000000)

# 2 0x9434abd9 in ( + 0x00000000)

# 3 0x99bc9540 in ( + 0x00000000)

# 4 0x99bc9180 in ( + 0x00000000)

# 5 0x943465fb in ( + 0x00000000)

# 6 0x94346485 in ( + 0x00000000)

# 7 0x9434bcf2 in ( + 0x00000000)

X86 Thread State:

eax: 0x00000131 ebx: 0x00010068 ecx: 0xb0420c7c edx:0x96f857ca

edi: 0x00000e00 esi: 0x00000d01 ebp: 0xb0420d08 esp:0xb0420c7c

ss: 0x00000023 eip: 0x96f857ca cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000246

Thread 8:

# 1 0x96f86046 in ( + 0x00000000)

# 2 0x9434bcce in ( + 0x00000000)

X86 Thread State:

eax: 0x00100170 ebx: 0x00007a5f ecx: 0xb031cf9c edx:0x96f86046

edi: 0x94347c69 esi: 0xb031d000 ebp: 0xb031cfc8 esp:0xb031cf9c

ss: 0x00000023 eip: 0x96f86046 cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000282

Thread 9:

# 1 0x96f86046 in ( + 0x00000000)

# 2 0x9434bcce in ( + 0x00000000)

X86 Thread State:

eax: 0x00100170 ebx: 0x0000afbf ecx: 0xb0080f9c edx:0x96f86046

edi: 0x94347c69 esi: 0xb0081000 ebp: 0xb0080fc8 esp:0xb0080f9c

ss: 0x00000023 eip: 0x96f86046 cs: 0x0000000b ds:0x00000023

es: 0x00000023 fs: 0x00000023 gs: 0x0000000f eflags:0x00000282

Loaded modules:

Operating System Information

Operating System: Mac OS X 10.9 (Build 13A603)

CPU: Intel Core Duo, Number: 4, Speed: 2147 MHz

gestaltPhysicalRAMSizeInMegabytes err = 0, result = 8192 MB

gestaltSystemVersion err = 0, result = 0x1090

Screen: 1280 x 800, depth = 32, ltbr = 0, 0, 800, 1280

Microsoft Application Information:

Error Reporting UUID: C4BF6C87-1362-41A9-9E51-0708955052C5

Time from launch: 3 hours, 12 minutes, 24 seconds

Total errors on this client: 9

MacBook Pro, OS X Mavericks (10.9)

Posted on Oct 23, 2013 10:46 PM

43 replies

Oct 10, 2014 2:36 PM in response to Room713

I have now lost all confidence in using Powerpoint with Mavericks at public presentations using dual screens or laptop + projector etc. I have reinstalled the (Mavericks) operating system from scratch, done all the Microsoft upgrades (to Office 2011) , and I get unpredictable behaviour as soon as I ask Powerpoint to go into presentation mode - when using dual screens. Have ended up looking like a complete prat at two recent high profile public presentations - with the illuminated Apple logo on the back of my laptop very publicly in view!! Will have to take a non-Apple laptop along in future until I can once again rely on my Macbook / Mavericks / Powerpoint to deliver. Absolute bloody nightmare. Will someone please sort this out - fast. Never used to happen on pre Mavericks operating systems.

Or provide me with a totally bombproof suggestion. I can't spend time at a public high profile gathering trying this out - ie which screen to start on, where the dock is etc etc. I just want to use a pre-rehearsed Powerpoint presentation to load up and run. At yesterday's attempt, after complete failure and time wasting, I had to ask the next speaker to go ahead of me - while I printed the Powerpoint to a pdf - then came back on stage and flipped through a pdf - absolutely PATHETIC.

olbjolbj

Level 1

0 points

Nov 4, 2014 4:07 AM in response to _vladdy

I found a work around that is slightly different than the one xzhang-mech suggests.

I changed primary display from my external screen to the laptop and after that PowerPoint starts screenshow in presenter mode without problem.

This means I can continue to have my displays in different spaces.

Best regards /Olle

Nov 5, 2014 9:24 AM in response to olbjolbj

Olle -

How do you change the "Primary" Display ? Somewhere in settings ?

Thanks - Robin

olbjolbj

Level 1

0 points

Nov 5, 2014 12:28 PM in response to Robin Curtis

All you have to do is to drag the menu bar from one display to the other in the Systems preferences: Display settings. However, I had a lecture today and the system worked perfectly in 30 minutes and after that Powerpoint started to crash just like before. During my lecture I switched between mirrored screens and separate displays and it messed up the system. When I returned to xzhang-mech's workaround the presentation worked smoothly again. This bug is really annoying. I plan to move to Keynote instead.

Regards Olle

Nov 5, 2014 1:33 PM in response to olbjolbj

Olle - thanks for your reply. To say that the bug is really annoying - is an understatement!! I can live with messing around in the office with some Apple / Microsoft screwup - but to be exposed at a significant professional presentation doesn't help with one's credibility ! Perhaps Apple have achieved their goal - another convert to Keynote?

Does anyone know if this bug has evaporated in Yosemite ? I'm not planning on moving to it until the first update arrives.

olbjolbj

Level 1

0 points

Nov 5, 2014 1:50 PM in response to Robin Curtis

Hi again. I am using Yosemite and unfortunately the bug is still present /Olle

Nov 5, 2014 2:03 PM in response to olbjolbj

Amazing.

I guess I'm not surprised - but I might have half expected an offering from either Microsoft or Apple or both. What changed in Mavericks that caused this? There must be a bunch of people plugging their Macs into projectors / second screens - and having this problem......No point in me hurrying to upgrade to Yosemite for the moment.

Thanks again for your replies. Good luck with Keynote!!

UMUPONDO

Level 1

0 points

Nov 20, 2014 12:01 AM in response to trek2710

just like what the others have said,after updating the problem disappears.i did the same and now i can enjoy with no problems

Jan 7, 2015 11:37 AM in response to olbjolbj

Assuming you have updated your Office 2011 version, have you tried exiting full screen mode under View>Exit Full Screen (Command+Control+F)?

Feb 28, 2015 10:32 AM in response to _vladdy

Update to 14.1 . The issue will be resolved ( confirmed on mavericks )

Jul 2, 2015 5:54 AM in response to _vladdy

thank you so much for this!

it took a long time to update but at least it worked!

smisra

Level 1

0 points

Sep 21, 2015 12:09 AM in response to _vladdy

THANK YOU!

Dec 1, 2015 10:39 AM in response to brianfromwaverly

I was also having problems where Powerpoint presentation view would not show on 2 screens. I could switch between presentation view with notes and presentation view but it only showed on 1 screen. Not sure why but Unclicking "Displays have separate spaces," as suggested by xzhang-mech seems to have fixed the problem. Thank you so much!

OS X Mavericks (10.9): Why MS PowerPoint will not go into FULL screen mode?