Answers

That event ID 14 is associated with a known bug in the Sleep/Hibernation components in Windows 7 RC.

A general description of the bug is, "when a system resumes from Sleep or Hibernation, one or more random hardware components will fail to reinitialize which requires that the system must be restarted to resume normal operation." We have seen this affect just about every type of hardware device attached to a system.

In this case, when this bug manifests itself, the Machine Check Exception (MCE) is initiated by the CPU because a hardware error was detected, but there is simply not enough information to define exactly where the error came from. The hardware error is usually the random hardware component that failed to reinitialize.

The only solution is to try and refrain from using the Sleep/Hibernate functions as much as possible. Also try to save any work you are doing prior to leaving the computer for any extended period.

This bug only seems to affect systems with particular hardware/driver configurations. The latest information we have is that this bug has been fixed in the RTM Build.

That event ID 14 is associated with a known bug in the Sleep/Hibernation components in Windows 7 RC.

A general description of the bug is, "when a system resumes from Sleep or Hibernation, one or more random hardware components will fail to reinitialize which requires that the system must be restarted to resume normal operation." We have seen this affect just about every type of hardware device attached to a system.

In this case, when this bug manifests itself, the Machine Check Exception (MCE) is initiated by the CPU because a hardware error was detected, but there is simply not enough information to define exactly where the error came from. The hardware error is usually the random hardware component that failed to reinitialize.

The only solution is to try and refrain from using the Sleep/Hibernate functions as much as possible. Also try to save any work you are doing prior to leaving the computer for any extended period.

This bug only seems to affect systems with particular hardware/driver configurations. The latest information we have is that this bug has been fixed in the RTM Build.

Currently using the nForce 15.37 chipset drivers and GeForce 186.18 graphic drivers. The only drivers I haven't updated are with the audio, as I must have some new motherboard revision or something since SiSoft Sandra and a few other utilities are saying I have a Realtek ALC1200 in addition to the known VIA VT1708B chipset as per specification.

The only thing I noticed that stopped working was the Bluetooth mouse (Microsoft Wireless IntelliMouse Explorer for Bluetooth), but I just deleted the device from the device manager and did a rescan to reinstall it. It's been working fine ever since.

Maxim, your problems are definitely from a hacked version of Win 7. Build 7100 is the version supported here and the only official public version.

All,I found this interesting response from a Vista thread which relates to AMD processors and the machine check error. Here's the Nov 1, 2008 response:

"AMD provides a tool called MCAT (Machine Check Exception Analysis Tool). You can find it on the AMD site in the downloads/processor utilities section. Choose the version appropriate to your processor. It installs a command line utility. To use it, execute mcat on the command line. There are several ways to use it. Execute mcat /? to see the possible options. Hopefully it can shed some light on the source of your problems.

Modern processors such as yours support advanced self-diagnostic capabilities, such that they analyze their own behavior and are capable of recognizing conditions that "can't happen". When one of these not-possible conditions occur, the CPU raises a "machine check exception". Windows is simply retrieving the information provided by the processor and recording it in the event log.

You mention on this thread that you've tried many different processors. That would be my first recommendation. This eliminates the processor as a potential source of the problem. Several other possible causes still remain.

Installation of a processor that is too much for your motherboard to handle (excessive power requirement, incompatibility)

Defective hardware that may be drawing excessive power or otherwise disrupting proper voltage regulation

The TLB is a part of the processor that manages translation of virtual addresses to physical addresses (to implement advanced memory management required for a multitasking operating system). The processor uses "page tables" to map virtual addresses to physical addresses. The TLB caches information from the page tables so it won't have to keep looking up this information. The machine check exception in your post shows that, while the processor was attempting to fetch instructions to be executed, it detected invalid information in the TLB. This can lead to major software errors, so it raises a machine check exception. If windows doesn't crash, the processor may have detected a benign error, but still an error worth reporting since it "can't happen". It is highly unlikely that this sort of error could be caused by software (i.e. Windows), since the operation of the TLB is entirely automatic and managed by the processor itself.

Machine check exceptions are almost always caused by a hardware problem.

Thank you for your quick answer. I'm really know all main possible reasons of that error, but... I've tested all components of my PC in all kind of tests (including stress test in S&M) and there was no errors (not S&M reported of them, nor events in system log). All temperatures in normal ranges in all modes of operation (at stand-by and at heavy load) and it's not strange case I have Hi-End coolers on all components (I've installed them personally, so I'm sure the contact of cooler surface with chips is good). PSU have more than enough power reserve for my configuration. I didn't noticed that this error crashes my system. There is no BSOD and no problems with stability. But... I'm still not really happy with this error messages. And one more detail. They are occurs every time I reboot the system. At system start-up actually. And they are not occurred at a time of stress or any other type of tests. And that is really strange you know... So I assumed, that this error have a software nature. Of course I'm not sure and that is the problem:). About your advices. I've download the AMD Utility and I'm shame to admit it, but I don't understand how it works:). I have experience of UNIX based systems administration, but I don't understand what should I do with this stuff:). Maybe all this case I worked today toooo much:). The Vista thread describes not exactly the same situation and I've read it already:). Can you please tell me some more about self-diagnostic capabilities of my kind of CPU? Is there any utilities, that can help Me run this self-diagnostic tests and get results of their work? Thank you again for your time. And sorry if my english is not very good:).

I've noticed the similar connection of this error to "Bluetooth Support Service", but at start-up in my case. Don't use sleep mode, but I guess I'll check it too. One more thing. The service "Portable Device Enumerator Service" cause exactly the same error in event log and at start-up too. Didn't noticed any other service causing the same effect yet. And have the similar hardware by the way.

Installed Phenom II X2 550 instead of Athlon X2 7750+. No changes. So problem is not the CPU for sure. Memory was replaced earlier, so it's not the RAM too. All possible hardware reason I can see is MB. Seems like bug described by Ronnie Vernon with only one difference. I don't use sleep/hibernation and even if send PC to sleep, don't got this warning, but got it at system start-up. One or more devices fail to initialize correctly at system start-up. It can be because of MB hardware malfunction, OS or drivers bugs.

Just an update: Yesterday I uninstalled the Asus ATK0110 ACPI driver that Windows Update originally installed (driver dated 2004) and installed a more recent version dated May 5, 2009 that came with Asus PC Probe II. I did this because the software installation would always hang at five percent and eventually error out about trying to install the included ACPI driver. Moreover, when I uninstalled the driver, I noticed Windows Update had an updated driver as well dated July 27, 2009.

As it currently stands, my computer is actually going to sleep again after it randomly stopped doing so for several weeks. With everything running for the past 24 hours, including a few sleeps and reboots, I haven't noticed any more machine check exceptions. Although, the Bluetooth transceiver (Microsoft) is still acting up with "Bluetooth HID device (00:50:f2:e3:5c:83) either went out of range or became unresponsive." messages, but it's still usable. Anyway, I'm picking up a new Bluetooth transceiver from Newegg today (cirago BTA-6210 USB 2.0 Micro Bluetooth Dongle support Bluetooth 2.1) which uses the Toshiba stack in order to get more profile support--and it also has better range. So I'll see if those messages go away as well and post here with any more findings.

Updated the BIOS to 0704 and MB drivers to 15.45 and it seems that the problem is solved:). Thanks, man. I've didn't checked the ASUS support site for a while. Meanwhile they released 2 new versions of BIOS and new drivers:). So, as I supposed from the start the problem had a software nature:).