轉貼 WIN7的
This bug check indicates that a fatal machine check exception has occurred.
*9C primarily appears on versions of Windows that predate Vista. For example, XP, Server 2003, etc. Nowadays, in Vista and later, we have *124 instead of *9C. However, in very uncommon cases, *9C is presented instead of *124 because the WHEA may not be fully initialized (Windows Error Hardware Architecture) or when a special processor issue on SMP systems occurs that is characterized by a failure with shared memory synchronization.
BugCheck 9C, {0, fffff880009f8b70, 0, 0}
Parameters 1, 3, and 4 are all 0 so I have no idea what happened here in this crash. Parameter 2 contains the address of the MCA_EXCEPTION structure which doesn't really help us in this case since the rest is 0.
---------------------
There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:
1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps -
http://www.piriform.com/speccy
2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting -
http://pcsupport.about.com/od/fixtheproblem/tp/clearcmo...
3. Ensure your BIOS is up to date.
4. The only software conflict that can usually cause *9C or *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite, AI Charger software, etc. If you have something like this software-wise, remove it ASAP (which I see you do have Asus software installed).
5. If all of the above fail, the only left to do is replace your processor as it is faulty.
Regards,
Patrick Barker
From microsoft forum answered this for me.
Post can be deleted
