Macbook pro time reset too 12:00am 2001

Question

when i turned on my macbook pro this morning I got a message saying that the clock was set to a date earlier than 2008 (the actual date was 1/1/01) and this may cause problems. I also got a load of messages asking me to authorise a load of things ive never heard of network access.
I gave everything network access just so I could connect to the internet and post this and I had to type my network key in again
what could have caused this??
i put a screenshot up here http://www.flickr.com/photos/tomdefyinglife/5071088338/

Answer 1

pipelineoptika wrote:
It's installed, but haven't used it in many many months. Perhaps 8?
It's still there . . . .
Be advised - I'm a programmer, and often cause issues with my machine due to bad code. The system itself is clean, however.
I highly recommend running Time Machine, then you can always go back and undo what you did/get what you need. In addition, I clone to an external HD, then I can boot to it and do almost anything I want to mess it up, and still just reboot to my "good" internal HD (or vice versa).
Here's the system log for the event in question. Sequence of events:
- Shut down machine (I usually sleep it)
- Machine has 30% battery
- Left overnight - still has about 30% battery in the morning
- Power on - clock has been reset.
For reference, my machine name is arumi:
Oct 12 23:29:59 arumi loginwindow\[37]: DEAD_PROCESS: 37 console
Oct 12 23:29:59 arumi shutdown\[11554]: halt by \[my user name here]:
Oct 12 23:29:59 arumi shutdown\[11554]: SHUTDOWN_TIME: 1286886599 660576
Oct 12 23:29:59 arumi mDNSResponder\[19]: mDNSResponder mDNSResponder-214.3.2 (May 14 2010 15:29:49) stopping
Oct 12 23:29:59 arumi DirectoryService\[11]: BUG in libdispatch: 10F569 - 1960 - 0x10004004
Oct 12 23:30:00 arumi WindowServer\[67]: hidd died. Reestablishing connection.
Oct 12 23:30:00 arumi WindowServer\[67]: Unable to create event queue via hidd: (0x10000003)
Jan 1 11:00:06 localhost com.apple.launchd\[1]: * launchd\[1] has started up. *
Jan 1 11:00:13 localhost mDNSResponder\[17]: mDNSResponder mDNSResponder-214.3.2 (May 14 2010 15:29:49) starting
Jan 1 11:00:22 localhost bootlog\[48]: BOOT_TIME: 978307205 0
Jan 1 11:00:24 localhost configd\[15]: bootpsessiontransmit: bpf_write(en1) failed: Network is down (50)
Jan 1 11:00:24 localhost configd\[15]: DHCP en1: INIT-REBOOT transmit failed
Jan 1 11:00:24 localhost configd\[15]: network configuration changed.
... and so on.
Not sure why that would blow the clock away, but there you go.
Faulty? Return unit to Apple?
I don't claim to understand the entirety of that log (or even most of it). Gut feeling is it's not a MBP hardware issue.
Are you running wireless or ethernet cable?
What kind of modem and/or wireless router are you running?
I ask, because I had an issue somewhat similar about the same time as the OP and you did. It turns out that my modem/router (2Wire brand supplied by ATT) automatically did a firmware update and messed up a number of my settings (which was rather tedious to figure out). Have never had that happen before. Don't know if it was isolated to that brand and/or ATT, or if it was in response to some new internet issue. Suspect I'll never know the answer to that, but I do know the issue happened and it was due to the modem/router update.
Note that date/time are usually set automatically via internet, so it seems there could be some connection.
I don't know if any of this has any bearing whatsoever, but I find the timing interesting.
EDIT: It just registered to me that you are still in hardware warranty. If no resolution to this, I would contact Apple. Try AppleCare phone support, but if they won't deal with you because you're out of phone support's 3 month time allowance, can you get to an Apple Store? If so, call ahead for a "genius" bar appointment.
Message was edited by: tjk