Well here we are at the end of the year and my work set up in my home office has been honed to work like a fine machine.  The way I work in my office is I have the MacBook Pro on the desk to the […]

Well here we are at the end of the year and my work set up in my home office has been honed to work like a fine machine.  The way I work in my office is I have the MacBook Pro on the desk to the left.  It is hooked up to an external monitor for two screen goodness and everything works flawlessly.  On the desk to the right (in an L shape) is the HP 2710p sitting in its expansion bay, screen open to allow me to switch back and forth between the Mac and the HP as needed.  This system has worked flawlessly for me until three days ago.


I have written numerous times that the HP 2710p runs Vista better than any mobile PC I have tried.  I have experienced no issues that plague Vista-running devices like sleep and hibernate problems, disk thrashing problems, and other like issues that make using mobile PCs difficult to do under Vista.  The HP has been immune to those problems and worked flawlessly for me in my mobile workstyle.  Until three days ago when something unexplainedly has changed with Vista.

Each night when I am through working for the night and heading up for bed I simply close the lid of the HP sitting in the dock which puts it to sleep for the night.  The next morning I open the lid and resume from the exact point I was the night before.  I have done this every single day for months with everything working just as intended with no problems.  Then three days ago I awoke and opened the lid.  It was apparent when the machine fired up from sleep mode that the HP had rebooted itself during the night.  Something in Vista had awakened the HP which crashed and rebooted.  Vista pretended innocence in this process of course yet tried to find solutions to this problem which had not existed the day before.  Nothing in the Vista database could identify this problem so no solution was offered.  This has now been repeated every single day since, and in fact over those three days the HP has crashed during sleep mode in the dock two other times during the day.  It either never really makes it into sleep mode or it just crashes while asleep.  This problem has been reported by many mobile device owners running Vista since it was released and it is incredibly annoying to have it happening to me now.

You have to understand that I have used the HP for months with no problems.  This just started to appear all at once on its own and I am at a loss to come up with either a reason for it or a solution for it.  I blame Vista squarely, I believe the primary responsibility of the OS is to prevent behind the scenes changes from creating a consistent problem such as this.  I have reviewed the Windows Update log and it shows no updates were applied anywhere near the time when this problem reared its ugly head.  The HP Update logs show none were applied by the OEM at that time either.  No, something in the background was apparently changed or corrupted to create a problem that never existed before.  This is something that the OS cannot allow to happen, unless the OS itself is the root of the problem.  I believe that to be the case because how can a solidly running system suddenly develop a major flaw, and one that only exhibits itself when the device is asleep? 

I will continue to troubleshoot this problem as it is consistent and fatal and impacts the way I use my machine but so far I am having no luck determining what the problem is, much less a solution.  The problem only shows up when the HP is docked so my daily mobile wonderings with the 2710p have not been impacted which is very good.  But for the life of me I can’t see why the docking behavior would have changed all at once.  The really stupid thing is I can predict that the solution is going to entail reinstalling Vista, something I will have to give a lot of thought to decide if I think is worth that trouble.  Thanks for nothing, Vista.  Meanwhile my Mac rolls on with no problems.

  1. Very frustrating, but I don’t know that I would categorize this as a “Vista failure” so much as a “Windows failure”. This sort of random system instability is certainly nothing new to the Windows environment. Microsoft has been “upgrading” the same pig of an OS since Windows 95 and I really don’t think we’ll see any major improvements until they bite the bullet and build a whole new OS from scratch and take the beatings over the lack of backwards compatability.

    And no, I’m not an anti-Microsoft, Mac fanboy – as a matter of fact I’m typing this on my new Advantage. Of course between my P1610, UX380, Q1, Dell M90, and MacBook, guess which one has to be rebooted the least often… ;)

  2. I had this happen to me on my macbook running mac osx. I was typing a paper for class and closed the lid and when I woke up the next morning and opened the lid it rebooted as if I just turned it on. It was the one time I got pissed off at my macbook. Hasn’t happened again since.

  3. Have you tried to restore the system state before the initial crash?
    Have you tried to delete the system ibernate file or the swap file? (deleting them disabling ibernate and swap file in control panel).
    Maybe a corrupt sector could do a strange behavior in the system…maybe not but it is better that a reinstall.
    have you scanned vista’s event logs for specific errors?
    Sorry for grammar i am italian^^

  4. Why don’t you try restoring to a system restore point just prior to the day that the problem first appeared? This would reverse any changes you made to Windows that may have caused the problem.

  5. I feel for you, James! Using XP here, I’ve lost the Volume icon in the Taskbar and *nothing* I’ve done can restore it. I’ve tried everydamnthing too! I know it’s minor compared to what you’re going through, but I find it to be maddening!

  6. I too have a Mac + HP2170p working arrangement. And every now and then, my HP just doesn’t shut down, or it just doesn’t start up. Actually, it worked great for the first month or two, and then one day, I tried to resume, and I got a black screen. Either it failed to resume, or else it did and the screen was missing in action. Restarting it seems to be the only solution. I also now get a “security certificate alert” at work with Lotus Notes and my office’s wireless network. Somehow the Windows based security programs always seem to be more hassle than they’re worth. As with all Windows issues, this mysteriously started about 6 weeks ago as well, and clicking “Yes” on all the dialog boxes to accept the security settings seems to do no damn good.

    I will be *SO* happy if and when Apple releases a tablet solution.

  7. Could it be some sort of failure in a hardware component in the dock? Software doesn’t “wear out” but hardware could. That hardware failure could’ve triggered the OS to execute something that it had never needed to execute before in this device.

  8. Yeah, I have this problem frequently with my core 2 duo MBP. I wake it up from sleep to find out it’s rebooted. I also have to re-sleep it often to get it out of black screen. Sleep is notorious as the single hardest hardware feature to properly support because of USB drivers and network drivers that have difficulty saving state, among other subsystems. It’s too bad Vista can’t recover from this common issue however. Good luck.

  9. Wouldn’t it make a lot more sense to have the machine go into hibernation mode over night?

    It takes not very many seconds to hibernate and the machine actually turns itself off and thus can’t crash.

    Booting a hibernated machine is also a matter of seconds.


Comments have been disabled for this post