Bootcamp OSX Reboot ?

[Washac]

When booting back into OSX I have to do a PRAM reset to get my OSX settings to work corrrectly.

Any ideas as to the cause or a fix ?

 

[casperes1996]

Which OS X settings?

Did this start after doing anything noteworthy in Windows?

 

[Washac]

Which OS X settings?

Did this start after doing anything noteworthy in Windows?

Which OSX settings
When I boot back into OSX ( Mavericks ) which is on a different to the drive where Bootcamp resides my
sound output settings are messed up as in instead of 4 choices which are, Headpones, Line Out, Digital Out
and AirParrot, when I boot back into OSX the only option I have is Airparrot until I do the PRAM reset.

Did this start after doing anything noteworthy in Windows?
Not that I am aware of

 

[casperes1996]

Which OSX settings
When I boot back into OSX ( Mavericks ) which is on a different to the drive where Bootcamp resides my
sound output settings are messed up as in instead of 4 choices which are, Headpones, Line Out, Digital Out
and AirParrot, when I boot back into OSX the only option I have is Airparrot until I do the PRAM reset.

There's nothing in NVRAM that would make sense with respect to this glitch to me. Only audio settings in NVRAM is audio volume.

When the issue next occurs, try changing the audio volume set in NVRAM with something like
sudo nvram BootAudio=%01

and see if that changes anything

 

[Washac]

There's nothing in NVRAM that would make sense with respect to this glitch to me. Only audio settings in NVRAM is audio volume.

When the issue next occurs, try changing the audio volume set in NVRAM with something like
sudo nvram BootAudio=%01

and see if that changes anything

Tried that made no difference.

 

[casperes1996]

Tried that made no difference.

Then your issue is severely puzzling to me. Any chance the NVRAM reset is not itself the fix, but you do something else when you do it that could be the fix? Like simply doing an extra power-cycle?

 

[Washac]

Then your issue is severely puzzling to me. Any chance the NVRAM reset is not itself the fix, but you do something else when you do it that could be the fix? Like simply doing an extra power-cycle?

It could be that but thanks for your input