I must strenuously disagree. If these were software problems then online forums and Apple tech sites would be filled with folks tearing down the virtual walls. If you get a box with bizarre stuff going on and a search doesn't turn up a screaming horde with exactly your symptoms, then in all likelihood it's a local problem. That is a silver-lining to the decreasing post-purchase configurability of the Macbook Pro line: it makes it a heck of a lot easier to diagnose potential hardware issues.
Taken all together, these almost certainly point to bad hardware. It's possible that a bad third-party kernel extension might be the culprit as well, so testing in SafeBoot can be useful to ferret out such issues.
Last but not least, I'm personally making heavy use of the same hardware and OS daily with zero issues. I'm pretty sure it's not the Apple-supplied software.
>I must strenuously disagree. If these were software problems then online forums and Apple tech sites would be filled with folks tearing down the virtual walls. If you get a box with bizarre stuff going on and a search doesn't turn up a screaming horde with exactly your symptoms, then in all likelihood it's a local problem.
That a bug is a software bug doesn't mean that it manifests in all identical systems. It depends on various factors (ie. combination of third party peripherals, e.g some Macs have Samsung SSDs, others have other brand), install software, user workflow, etc.
Taken all together, these almost certainly point to bad hardware. It's possible that a bad third-party kernel extension might be the culprit as well, so testing in SafeBoot can be useful to ferret out such issues.
Last but not least, I'm personally making heavy use of the same hardware and OS daily with zero issues. I'm pretty sure it's not the Apple-supplied software.