New
#1
BSOD when playing Starcraft 2
Some Specs
AMD Athlon(tm) II X4 630 Processor
Microsoft Windows 7 Home Premium
4.0 GB RAM
NVIDIA GeForce GTX 550 Ti 1GB
589 GB / 916 GB HDD
Some Specs
AMD Athlon(tm) II X4 630 Processor
Microsoft Windows 7 Home Premium
4.0 GB RAM
NVIDIA GeForce GTX 550 Ti 1GB
589 GB / 916 GB HDD
please start by doing the following:
Uninstall Daemon tools, once daemon tools is uninstalled please download and run this tools:
DuplexSecure
when the tool runs if the uninstall button ids grayed out you are done and you can close the window. If it is not click it and allow the tool to run. DO NOT click the install button it will install a driver Known to cause BSODs on your system.
let us know the results
It happened again after a few hours of gameplay of another game
It seems that the error you are getting now is a 0x124 error which usually indicates a hardware problem.
Taking a look at the error record we can see that the processor made a call to one of its busses and there was a time out reported causing the system to crash.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa80053a84b8, 0, 0} Probably caused by : AuthenticAMD Followup: MachineOwner ---------
Now this type of crash isnt always caused by hardware errors, you can try updating your bios (which can be found on the manufacturers website) and any drivers on your system, I.E. sound, network, videocard. If you still receive crashes after that please run prime95 for some hard ware tests: Hardware - Stress Test With Prime95Code:3: kd> !errrec fffffa80053a84b8 =============================================================================== Common Platform Error Record @ fffffa80053a84b8 ------------------------------------------------------------------------------- Record Id : 01ce152c5e66f0c4 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/27/2013 20:52:53 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa80053a8538 Section @ fffffa80053a8610 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : BUS error Operation : Generic Flags : 0x00 Level : 3 CPU Version : 0x0000000000100f52 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa80053a8580 Section @ fffffa80053a86d0 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU Id : 52 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17 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 @ fffffa80053a86d0 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa80053a85c8 Section @ fffffa80053a8750 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4) Status : 0xfa00000000070f0f
I am doing the tests now but I am not sure what I am looking for if it is a hardware issue.
Prime95 is meant to put a full load on your CPU which causes it to heat up, check the temperatures durring the test and report them here when they max out, also Prime 95 may throw errors if there is an actual problem with the processor.
Should I do a different setting instead of "Small FFTs"?
For the best results select the blend test it covers the most components report back your results.
I ran the test for five hours and counting and the max temp it has gone to was 58 C
Interesting... you may want to have a look at this in that case: Stop 0x124 - what it means and what to try