New
#21
63°C was the max.
EDIT: While running the temp. test, the PC froze, so I reset, not powered off, and got another BSOD after launching the game again.
63°C was the max.
EDIT: While running the temp. test, the PC froze, so I reset, not powered off, and got another BSOD after launching the game again.
Please update Tunggle.
Please remove ASUS software while troubleshooting, it uses outdated drivers and is known for causing bluescreens.
Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.
- Uninstall Daemon Tools
- Download the SPTD standalone installer and follow these steps:
- Double click the executable to open it
- Click on the button shown below
If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window
Did the steps, no bluescreens (there still were pc freezes) and then this hit me today, so I have no idea what's going on...
This one is a 0x124 a.k.a. a hardware crash which mostly is a processor cache type error, this one is a generic read error on the cache of the CPU. Please note that the CPU is reporting the error with this type, it only reports where the problem occurs but that does not mean the CPU is the cause. A 0x124 usually doesn't reveal enough to show a cause, finding a pattern in the problem may get a lead to possible problems.
Looking a bit deeper there is quite some network coming back in the dump what refers to the network drivers as you can see below in the code, the driver is the Realtek PCIe GBE Family controller network adapter driver. Because a driver has been flagged I would like to immediately remove all outdated drivers.
Please update following drivers and iTunes
Driver Reference Table - Rt630x64.sys
Driver Reference Table - speedfan.sys
Driver Reference Table - GEARAspiWDM.sys used by iTunes most likely.
On a side note, there is a generic troubleshooting guide for this error which you might want to read, it covers pretty much every possibility.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: ffffe00057504028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bc800800, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000010137, Low order 32-bits of the MCi_STATUS value. 1: kd> !errrec ffffe00057504028 =============================================================================== Common Platform Error Record @ ffffe00057504028 ------------------------------------------------------------------------------- Record Id : 01d16e5d385cc75f Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 2/23/2016 19:36:09 (UTC) Flags : 0x00000000 =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe000575040a8 Section @ ffffe00057504180 Offset : 344 Length : 192 Flags : 0x00000001 Primary Severity : Fatal Proc. Type : x86/x64 Instr. Set : x64 Error Type : Cache error Operation : Data Read Flags : 0x00 Level : 3 CPU Version : 0x0000000000600f20 Processor ID : 0x0000000000000001 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe000575040f0 Section @ ffffe00057504240 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000001 CPU Id : 20 0f 60 00 00 08 08 01 - 0b 32 98 3e 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 @ ffffe00057504240 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe00057504138 Section @ ffffe000575042c0 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : DCACHELG_DRD_ERR (Proc 1 Bank 0) Status : 0xbc80080000010137 Address : 0x0000000188359400 Misc. : 0xc00a0fff00000000 ffffd000`20891bd8 fffff800`dc48c49dUnable to load image Rt630x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Rt630x64.sys *** ERROR: Module load completed but symbols could not be loaded for Rt630x64.sys Rt630x64+0x1c49d 1: kd> lmvm Rt630x64 start end module name fffff800`dc470000 fffff800`dc53a000 Rt630x64 T (no symbols) Loaded symbol image file: Rt630x64.sys Image path: Rt630x64.sys Image name: Rt630x64.sys Timestamp: Fri Jun 21 11:29:10 2013 (51C41CE6) CheckSum: 000D4CEB ImageSize: 000CA000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
I suggest to try it when this error returns after updating the drivers :)
Stop 0x124 - what it means and what to try - Windows 7 Help Forums
Got two more, haven been able to post them because I was away for the weekend.
See if a BIOS update helps, you are running 2201 but the most recent is 2603.
M5A97 R2.0 | Moederbord | ASUS Nederland