New
#11
Hows it going Russ?
Hey Ant,
Thanks for responding. I wanted to wait a while before replying to see if it would happen again. I was optimistic that your solution would fix the problem, but alas, I just got another BSOD. Any other suggestions you may have?
Thanks,
Russ
Ant,
I also just attached another of the zip files with the latest information.
Thanks again,
Russ
I still see some Asus entry's Please make sure its remove completely!!
Download CPUZ and post an image of each tab.
Thanks
Ant,
Thanks for your response. I see a couple of ASUS entries too, but they seem to be for things like "ASUS Fan Control" and "ASUS System Control". These aren't necessary for the fans and motherboard to run properly?
I've attached the images from CPU-Z, as well as a text and html file that I was able to output from CPU-Z with information.
I really appreciate your help here.
-Russ
Just for some additional information, the two 0x124 crashes report that there was an internal CPU timer error. This is most often a problem with the CPU itself, but it can be caused by external interference, such as overheating, voltage problems (overclocking or PSU/Mobo issues), bent/broken CPU/socket pins, or even BIOS or driver issues.
I agree with Anthony that motherboard software is a big no-no, as they're often broken and gimmicky, ending up manifesting hardware-related errors like this when they themselves are the cause of it all. You're best to just clean up anything left that you installed for your motherboard, only leaving drivers (not USB drivers or AI Charger) updated and intact. This also does include removing the fan and "system control" stuff. Go ahead and do a BIOS update in addition to all of this while you're at it.
The one C4 error has Driver Verifier detecting PEUpdater (Asustek updating software) seemingly performing something unscrupulous. You may need to remove this as well if possible, and update drivers manually instead of relying on automated update software.
Just wanted to add that all in. Continue the investigation.
Analysts:
Code:1: kd> !errrec fffffa800fd83028 =============================================================================== Common Platform Error Record @ fffffa800fd83028 ------------------------------------------------------------------------------- Record Id : 01cd7ec99d4d9cc3 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/21/2012 2:02:59 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa800fd830a8 Section @ fffffa800fd83180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000306a9 Processor ID : 0x0000000000000001 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa800fd830f0 Section @ fffffa800fd83240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000001 CPU Id : a9 06 03 00 00 08 10 01 - ff e3 ba 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ fffffa800fd83240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa800fd83138 Section @ fffffa800fd832c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 1 Bank 3) Status : 0xbe00000000800400 Address : 0x0000380002eddfad Misc. : 0x000000000003ffff ____ 0: kd> !errrec fffffa800fe04028 =============================================================================== Common Platform Error Record @ fffffa800fe04028 ------------------------------------------------------------------------------- Record Id : 01cd7d5bb1738bc3 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 8/18/2012 17:28:01 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa800fe040a8 Section @ fffffa800fe04180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Micro-Architectural Error Flags : 0x00 CPU Version : 0x00000000000306a9 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa800fe040f0 Section @ fffffa800fe04240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : a9 06 03 00 00 08 10 00 - ff e3 ba 7f ff fb eb bf 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 Proc. Info 0 @ fffffa800fe04240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa800fe04138 Section @ fffffa800fe042c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : Internal timer (Proc 0 Bank 3) Status : 0xbe00000000800400 Address : 0x0000380002cd01fb Misc. : 0x000000000003ffff
Thanks guys. I uninstalled all that I could from ASUS using the Windows Uninstallers, and then I saw some services running that had to do with ASUS, so I stopped and disabled all of them. I wasn't sure how to completely remove it, but maybe this is good enough?
I attached the latest files for your info. I'm going to try running my video encoding soon to try to force a BSOD. If you think of anything else I could try in the meantime, please let me know. I'll respond back if I get a BSOD.
Thanks again,
Russ
So unfortunately the BSOD happened again, even after removing and stopping all ASUS services. Any other suggestions that I should try?
Thanks,
Russ
Can you provide us the new crashdump? Thanks.
Also, if worse comes to worse, you can always turn on Driver Verifier and provide us any new crashdumps from that. However, my initial suspicions may be accurate: you have a bad CPU, PSU, or motherboard, or memory, in that order from most suspect to least.
Vir,
I attached the latest diagnostic files. I've actually ran the verifier and it will crash within a minute of logging into Windows. I believe the first minidump file I attached was due to running through verifier.
Thanks,
Russ