New
#1
Random BSOD'S
After I changes my CPU I've started receiving random BSOD's...Please help me with the analyze of my .dmp files...
Thank you in advance.
Last edited by Ovidiu85; 24 Jan 2013 at 05:51. Reason: didn't take my attachments
After I changes my CPU I've started receiving random BSOD's...Please help me with the analyze of my .dmp files...
Thank you in advance.
Last edited by Ovidiu85; 24 Jan 2013 at 05:51. Reason: didn't take my attachments
Yes, I did, and I had a lot of problems with that too, as the PC was instable and randomly restarted during the instalation or the install wizzard just froze at random points...Spent 6 full hours to manage to install a bloody OS...
Tested with different RAM memory, different video card and today I'll go to a friend to test it with a different motherboard...Did stress tests and the temperatures were ok...Idk what causes them but they are annoying as hell...
I want to see the .dmp so I can make sure it's a hardware problem, and I wanted to get an opinion from people whom actually know how to read this things and dealt with this kind of problems...
LE: I am 90% sure it's the CPU but I want to be 100% when I'll go to the store and crush their heads with it...
PS: Today i switched to my old CPU and haven't had any BS since than...
Specs:
Asus P5G4C1-M LX motherboard
Asus Nvidia GeForce GTX 650 video card (new, bought it yesterday)
8 GB of Kingmax DDR3 RAM
Intel Core 2 Quad Q9300 2.5 refurbished CPU (this is the "new" one that BS me)
Intel Dual Core Celeron E3400 2.6 OCC to 3.4 (old CPU that runs like a clock)
The stop code you are getting is a 0x124 which indicates a fatal hardware error, i do not think that it is the mother board unless you have some evidence that is to the contrary:
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8007ccb8f8, 0, 0} Probably caused by : GenuineIntel Followup: MachineOwner ---------You can run through this tutorial to try and help you better understand the issue and possibly rule out a number of things as part of the problem:Code:kd> !errrec fffffa8007ccb8f8 =============================================================================== Common Platform Error Record @ fffffa8007ccb8f8 ------------------------------------------------------------------------------- Record Id : 01cdf9c59e7e4004 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 1/23/2013 23:59:08 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ fffffa8007ccb978 Section @ fffffa8007ccba50 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 : 0 CPU Version : 0x0000000000010677 Processor ID : 0x0000000000000002 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ fffffa8007ccb9c0 Section @ fffffa8007ccbb10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000002 CPU Id : 77 06 01 00 00 08 04 02 - fd e3 08 00 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 @ fffffa8007ccbb10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ fffffa8007ccba08 Section @ fffffa8007ccbb90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 2 Bank 0) Status : 0xf200080000000800
Stop 0x124 - what it means and what to try
another thought your BIOS Is rather old you could try updating it and see if it helps.
Thank you very much for your help kind sir...So, as far as I understand it is the CPU causing all the trouble...I'll run that tutorial too, just to be sure...As far as the BIOS goes, it is the lastest version for this motherboard on the Asus site...