#Error ‘Bad CurrentVBLDelta for display 69673216 is zero. defaulting to 60Hz.’ MBP5,1 late 2008,15”

65 messages · Page 1 of 1 (latest)

analog bear
safe herald
#

Defaulting to 60Hz is expected, your issue is unrelated
Try reinstalling

cinder sparrow
#

I appreciate the advice. Any idea what how reinstalling can fix this? What would it specifically address? On MBP 5,1, 15”, there is no ability to change frequency whichever resolution is used. Can process’ Bad CurrentVbLDelta’ be killed the moment it starts up, or better still prevented from being issued?

analog bear
#

You can manually set resolution and refresh rate with DisplayPlacer

#

CurrentVBLDelta isn't a process per se

cinder sparrow
#

Also Bad CurrentVBLDelta defaulting to 60HZ still happening regardless of fullscreen or not.

analog bear
cinder sparrow
#

Do you mean this “Try adding OS_ACTIVITY_MODE to the envirable variables (within the run settings) and set that env variable to disable”?

analog bear
#

Yes

cinder sparrow
#

Ah! not sure how to do that.

#

Do you know how to do this?

analog bear
#

Actually it won't help, it's an xcode env variable, not a system one

cinder sparrow
#

I have reported this to Apple as happening in the Core Video API.

#

I wonder if downgrading the offending browsers to pre-Monterey versions will stop it? Or if it has something to do with the disabled dGpu (9600M)?

safe herald
#

It’s a non-metal side affect

#

Perfectly normal, and as I said before, not your issue

safe herald
cinder sparrow
#

Do you recommend reinstall over existing or fully delete ssd for clean install?

safe herald
#

Clean if possible, but could try a reinstall

cinder sparrow
#

What’s your understanding of what gets resolved by doing this? What specifically gets rectified?

cinder sparrow
analog bear
cinder sparrow
#

That’s a shame as it fixed the blank Wifi pane in Preferences. I’ll do a fresh install tomorrow. Thanks for all your help. 🙂

analog bear
#

What I do with mine is alternate partitions, so I have a stable version to fall back on

#

Like right now my 2015 has a partition for Monterey, a partition for Ventura, and a partition for user profiles

cinder sparrow
#

What size is your Monterey partition?

analog bear
#

100gb each

#

Roughly, from a 512gb

#

Probably like 96gb

#

When macOS Sequoia comes out I'll wipe the Monterey partition to install it

#

macOS will be fine with much smaller partitions though

cinder sparrow
#

I’m stuck with a main 240gb SSD and another internal 750GB HDD with El Capitan partition for the time being. I can’t afford the space to give 100gb on the SSD to two partitions. I think i’ll be ok when I do the full clean install of Ventura again as the Bad CurrentVBLDelta error happens less than it did with Monterey. In other words I can get work done with this oclp Ventura.

cinder sparrow
#

I’ve never seen this screen before when installing oclp!?

tacit siren
# cinder sparrow I’ve never seen this screen before when installing oclp!?

I had the same issue when installing Ventura on my MacBookPro9,2. I forced a shutdown and booted back into the Boot Picker (hold Option). And then I tried the install again, and it worked. But I started having further issues and just went with Monterey. It's been completely stable compared to Ventura. I'll make the shift when I'm confident that it's better.

cinder sparrow
#

I had to format the SSD from within The Boot Picker -> Install Ventura, as opposed to from booting into Recovery and selecting Disk Utility in order to format from there. Now I am back up and running on Ventura but with the same issues as before - Bad CurrentVBLDelta etc.

analog bear
#

I would be very curious to see if a copy of Ventura installed on an external drive using a different computer produces the same error when booted on this computer

cinder sparrow
#

Interesting idea! I will see about arranging that. Thanks…..

safe herald
#

How many times do you have to be told that the CurrentVBDelta error is not even remotely related to your problem and is totally normal

cinder sparrow
#

My mac freezing for 30 second durations regularly is not normal. I have noted the start and stop times of the freezing and cross referenced those times with the error outputs in the Console. Bad CurrentVBDDelta appears at the start at stop times with multiple appearances in between. Forgive me if I have concluded incorrectly. If you know it is absolutely not the cause of the problem then what is the cause?

cinder sparrow
#

This is the error log from Console when I opened Tot App (quick notes app) which initiated a 30s freeze/hang starting at 13:56:33. The log includes 1s before the hang started. No Bad Current this time. Is there anything hear that suggests what is causing the freeze? Would seeing AllMessages during that time period from Console be helpful?

analog bear
#

It could help, it sounds like this error might be a symptom rather than the cause

cinder sparrow
cinder sparrow
cinder sparrow
analog bear
cinder sparrow
analog bear
#

By working through and eliminating possible causes. Have you already tried installing macOS to an external drive and booting from that?

safe herald
#

Which is your monitors default refresh rate

#

I, along with the rest of the non-metal devs, have spent extensive time researching these bugs and errors

#

It’s totally harmless and unrelated

cinder sparrow
analog bear
#

Do you have the Magic Keyboard? You may need to connect it with a lightning cable in order to pair it again

cinder sparrow
#

I don’t. Must it be the Magic Keyboard?

safe herald
#

You need a wired keyboard through a usb hub

#

Read the guide and documentation, please

#

Both of you

cinder sparrow
cinder sparrow
#

👍