Hay guys,
My computer recently has been getting the BSOD and not too sure as too why this is occurring, as i have built a pretty good system and only up until late last year its started happening but more often now
i receive the STOP 0x00000124 message randomly whilst using my computer or i've also noticed when i wake it up from 'sleep'
i understand this is error is hardware? so i updated most drivers and performed some stress tests (which passed) and still get it
any clue guys i need my comp for heavy work load
the latest dump file is uploaded here Zippyshare.com - 041011-82337-01.dmp
could you please have a look at it and analyse it for me so we can work out what the problem is!
Im computer literate so i should be able to understand most things you say!
Thanks heaps guys
My computer recently has been getting the BSOD and not too sure as too why this is occurring, as i have built a pretty good system and only up until late last year its started happening but more often now
i receive the STOP 0x00000124 message randomly whilst using my computer or i've also noticed when i wake it up from 'sleep'
i understand this is error is hardware? so i updated most drivers and performed some stress tests (which passed) and still get it
any clue guys i need my comp for heavy work load
the latest dump file is uploaded here Zippyshare.com - 041011-82337-01.dmp
could you please have a look at it and analyse it for me so we can work out what the problem is!
Im computer literate so i should be able to understand most things you say!
Thanks heaps guys
Are you overclocking any hardware? Updating your BIOS might help
no overclocking and yes the latest bios F11 is what i have
thanks for the quick reply, amazing!
thanks for the quick reply, amazing!
have read that post numerous times
is there any chance of analyzing the dump file to pin point or at least get close to finding the problem?
is there any chance of analyzing the dump file to pin point or at least get close to finding the problem?
Bugcheck 0x124 = Hardware WHEA = Hardware Failure
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
Video Card - Stress Test with Furmark
RAM - Test with Memtest86+
http://www.sevenforums.com/tutorials...t-prime95.html
Video Card - Stress Test with Furmark
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dean\Downloads\041011-82337-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`0329ee50 Debug session time: Mon Apr 11 11:02:30.469 2011 (UTC + 12:00) System Uptime: 0 days 0:00:30.484 Loading Kernel Symbols ............................................................... ..................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8007dbb028, f2000000, 20008f} Probably caused by : hardware Followup: MachineOwner --------- 7: kd> !analyze -v ******************************************************************************* * * * 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: fffffa8007dbb028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value. Arg4: 000000000020008f, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f STACK_TEXT: fffff880`03172b58 fffff800`0302a903 : 00000000`00000124 00000000`00000000 fffffa80`07dbb028 00000000`f2000000 : nt!KeBugCheckEx fffff880`03172b60 fffff800`031e75a3 : 00000000`00000001 fffffa80`0705e630 00000000`00000000 fffffa80`0705e680 : hal!HalBugCheckSystem+0x1e3 fffff880`03172ba0 fffff800`0302a5c8 : 00000000`00000728 fffffa80`0705e630 fffff880`03172f30 fffff880`03172f00 : nt!WheaReportHwError+0x263 fffff880`03172c00 fffff800`03029f1a : fffffa80`0705e630 fffff880`03172f30 fffffa80`0705e630 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff880`03172d50 fffff800`03029dd5 : 00000000`00000008 00000000`00000001 fffff880`03172fb0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff880`03172d90 fffff800`0301de88 : fffff880`0316a180 fffff880`0316a180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff880`03172dc0 fffff800`030cffec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`03172df0 fffff800`030cfe53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`03172f30 fffff800`03035652 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 fffff880`03192c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalProcessorIdle+0x2 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN BUCKET_ID: X64_0x124_GenuineIntel_MEMORY__UNKNOWN Followup: MachineOwner --------- 7: kd> lmtsmn start end module name fffff880`00f5e000 fffff880`00fb5000 ACPI ACPI.sys Tue Jul 14 11:19:34 2009 (4A5BC106) fffff880`03d51000 fffff880`03ddb000 afd afd.sys Tue Jul 14 11:21:40 2009 (4A5BC184) fffff880`00c0b000 fffff880`00c16000 amdxata amdxata.sys Wed May 20 05:56:59 2009 (4A12F2EB) fffff880`00dc6000 fffff880`00dcf000 atapi atapi.sys Tue Jul 14 11:19:47 2009 (4A5BC113) fffff880`00dcf000 fffff880`00df9000 ataport ataport.SYS Tue Jul 14 11:19:52 2009 (4A5BC118) fffff880`02df6000 fffff880`02dfd000 Beep Beep.SYS Tue Jul 14 12:00:13 2009 (4A5BCA8D) fffff880`01800000 fffff880`0182a000 cdrom cdrom.sys Tue Jul 14 11:19:54 2009 (4A5BC11A) fffff880`00ce2000 fffff880`00da2000 CI CI.dll Tue Jul 14 13:32:13 2009 (4A5BE01D) fffff880`01990000 fffff880`019c0000 CLASSPNP CLASSPNP.SYS Tue Jul 14 11:19:58 2009 (4A5BC11E) fffff880`00c84000 fffff880`00ce2000 CLFS CLFS.SYS Tue Jul 14 11:19:57 2009 (4A5BC11D) fffff880`010da000 fffff880`0114d000 cng cng.sys Tue Jul 14 11:49:40 2009 (4A5BC814) fffff880`019c0000 fffff880`019ce000 crashdmp crashdmp.sys Tue Jul 14 12:01:01 2009 (4A5BCABD) fffff880`0197a000 fffff880`01990000 disk disk.sys Tue Jul 14 11:19:57 2009 (4A5BC11D) fffff880`019ce000 fffff880`019da000 dump_dumpata dump_dumpata.sys Tue Jul 14 11:19:47 2009 (4A5BC113) fffff880`019e5000 fffff880`019f8000 dump_dumpfve dump_dumpfve.sys Tue Jul 14 11:21:51 2009 (4A5BC18F) fffff880`019da000 fffff880`019e5000 dump_msahci dump_msahci.sys Tue Jul 14 12:01:01 2009 (4A5BCABD) fffff880`03f18000 fffff880`03f8e000 eeCtrl64 eeCtrl64.sys Sat May 22 09:44:45 2010 (4BF6FECD) fffff880`02dcd000 fffff880`02ded000 ENG64 ENG64.SYS Sat Mar 05 11:02:16 2011 (4D716168) fffff880`02c0a000 fffff880`02dcd000 EX64 EX64.SYS Sat Mar 05 11:10:51 2011 (4D71636B) fffff880`01068000 fffff880`0107c000 fileinfo fileinfo.sys Tue Jul 14 11:34:25 2009 (4A5BC481) fffff880`0101c000 fffff880`01068000 fltmgr fltmgr.sys Tue Jul 14 11:19:59 2009 (4A5BC11F) fffff880`013ed000 fffff880`013f7000 Fs_Rec Fs_Rec.sys Tue Jul 14 11:19:45 2009 (4A5BC111) fffff880`01940000 fffff880`0197a000 fvevol fvevol.sys Sat Sep 26 14:34:26 2009 (4ABD7DB2) fffff880`0148b000 fffff880`014d5000 fwpkclnt fwpkclnt.sys Tue Jul 14 11:21:08 2009 (4A5BC164) fffff800`03018000 fffff800`03061000 hal hal.dll Tue Jul 14 13:27:36 2009 (4A5BDF08) fffff880`01937000 fffff880`01940000 hwpolicy hwpolicy.sys Tue Jul 14 11:19:22 2009 (4A5BC0FA) fffff800`00bcb000 fffff800`00bd5000 kdcom kdcom.dll Tue Jul 14 13:31:07 2009 (4A5BDFDB) fffff880`013c2000 fffff880`013dc000 ksecdd ksecdd.sys Tue Jul 14 11:20:54 2009 (4A5BC156) fffff880`01460000 fffff880`0148b000 ksecpkg ksecpkg.sys Fri Dec 11 19:03:32 2009 (4B21E0B4) fffff880`00c2c000 fffff880`00c70000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 13:29:10 2009 (4A5BDF66) fffff880`018e1000 fffff880`01937000 MDFSYSNT MDFSYSNT.sys Fri Oct 08 09:39:16 2010 (4CAE2FF4) fffff880`01200000 fffff880`0120d000 MDPMGRNT MDPMGRNT.SYS Fri Oct 22 09:59:58 2010 (4CC0A9CE) fffff880`00dac000 fffff880`00dc6000 mountmgr mountmgr.sys Tue Jul 14 11:19:54 2009 (4A5BC11A) fffff880`00c00000 fffff880`00c0b000 msahci msahci.sys Tue Jul 14 12:01:01 2009 (4A5BCABD) fffff880`03cf8000 fffff880`03d03000 Msfs Msfs.SYS Tue Jul 14 11:19:47 2009 (4A5BC113) fffff880`00fbe000 fffff880`00fc8000 msisadrv msisadrv.sys Tue Jul 14 11:19:26 2009 (4A5BC0FE) fffff880`0107c000 fffff880`010da000 msrpc msrpc.sys Tue Jul 14 11:21:32 2009 (4A5BC17C) fffff880`03f0d000 fffff880`03f18000 mssmbios mssmbios.sys Tue Jul 14 11:31:10 2009 (4A5BC3BE) fffff880`015e4000 fffff880`015f6000 mup mup.sys Tue Jul 14 11:23:45 2009 (4A5BC201) fffff880`00da2000 fffff880`00dac000 mv91cons mv91cons.sys Wed Sep 23 09:36:37 2009 (4AB94365) fffff880`014da000 fffff880`015cc000 ndis ndis.sys Tue Jul 14 11:21:40 2009 (4A5BC184) fffff880`03c74000 fffff880`03c83000 netbios netbios.sys Tue Jul 14 12:09:26 2009 (4A5BCCB6) fffff880`03c00000 fffff880`03c45000 netbt netbt.sys Tue Jul 14 11:21:28 2009 (4A5BC178) fffff880`01400000 fffff880`01460000 NETIO NETIO.SYS Tue Jul 14 11:21:46 2009 (4A5BC18A) fffff880`03d03000 fffff880`03d14000 Npfs Npfs.SYS Tue Jul 14 11:19:48 2009 (4A5BC114) fffff880`03f01000 fffff880`03f0d000 nsiproxy nsiproxy.sys Tue Jul 14 11:21:02 2009 (4A5BC15E) fffff800`03061000 fffff800`0363e000 nt ntkrnlmp.exe Wed Oct 27 15:43:09 2010 (4CC791BD) fffff880`0121f000 fffff880`013c2000 Ntfs Ntfs.sys Tue Jul 14 11:20:47 2009 (4A5BC14F) fffff880`02ded000 fffff880`02df6000 Null Null.SYS Tue Jul 14 11:19:37 2009 (4A5BC109) fffff880`03c4e000 fffff880`03c74000 pacer pacer.sys Tue Jul 14 12:09:41 2009 (4A5BCCC5) fffff880`00e0d000 fffff880`00e22000 partmgr partmgr.sys Tue Jul 14 11:19:58 2009 (4A5BC11E) fffff880`00fc8000 fffff880`00ffb000 pci pci.sys Tue Jul 14 11:19:51 2009 (4A5BC117) fffff880`00e93000 fffff880`00e9a000 pciide pciide.sys Tue Jul 14 11:19:49 2009 (4A5BC115) fffff880`00e9a000 fffff880`00eaa000 PCIIDEX PCIIDEX.SYS Tue Jul 14 11:19:48 2009 (4A5BC114) fffff880`013dc000 fffff880`013ed000 pcw pcw.sys Tue Jul 14 11:19:27 2009 (4A5BC0FF) fffff880`00c70000 fffff880`00c84000 PSHED PSHED.dll Tue Jul 14 13:32:23 2009 (4A5BE027) fffff880`03eb0000 fffff880`03f01000 rdbss rdbss.sys Tue Jul 14 11:24:09 2009 (4A5BC219) fffff880`03cdd000 fffff880`03ce6000 RDPCDD RDPCDD.sys Tue Jul 14 12:16:34 2009 (4A5BCE62) fffff880`03ce6000 fffff880`03cef000 rdpencdd rdpencdd.sys Tue Jul 14 12:16:34 2009 (4A5BCE62) fffff880`03cef000 fffff880`03cf8000 rdprefmp rdprefmp.sys Tue Jul 14 12:16:35 2009 (4A5BCE63) fffff880`01199000 fffff880`011d3000 rdyboost rdyboost.sys Tue Jul 14 11:34:34 2009 (4A5BC48A) fffff880`01000000 fffff880`0101a000 SCDEmu SCDEmu.SYS Mon Nov 09 16:27:29 2009 (4AF78C21) fffff880`03c83000 fffff880`03ca0000 serial serial.sys Tue Jul 14 12:00:40 2009 (4A5BCAA8) fffff880`015dc000 fffff880`015e4000 spldr spldr.sys Tue May 12 04:56:27 2009 (4A0858BB) fffff880`0182a000 fffff880`0189d000 SRTSP64 SRTSP64.SYS Thu Jan 29 15:55:07 2009 (49811A8B) fffff880`011d3000 fffff880`011e7000 SRTSPX64 SRTSPX64.SYS Thu Jan 29 15:57:42 2009 (49811B26) fffff880`0189d000 fffff880`018d3000 SYMEVENT64x86 SYMEVENT64x86.SYS Thu May 29 12:35:19 2008 (483DFA47) fffff880`01601000 fffff880`017fe000 tcpip tcpip.sys Mon Jun 14 15:39:04 2010 (4C15A458) fffff880`03d32000 fffff880`03d3f000 TDI TDI.SYS Tue Jul 14 11:21:18 2009 (4A5BC16E) fffff880`03d14000 fffff880`03d32000 tdx tdx.sys Tue Jul 14 11:21:15 2009 (4A5BC16B) fffff880`011e7000 fffff880`011fb000 termdd termdd.sys Tue Jul 14 12:16:36 2009 (4A5BCE64) fffff880`00e00000 fffff880`00e0d000 vdrvroot vdrvroot.sys Tue Jul 14 12:01:31 2009 (4A5BCADB) fffff880`018d3000 fffff880`018e1000 vga vga.sys Tue Jul 14 11:38:47 2009 (4A5BC587) fffff880`03ca8000 fffff880`03ccd000 VIDEOPRT VIDEOPRT.SYS Tue Jul 14 11:38:51 2009 (4A5BC58B) fffff880`015cc000 fffff880`015dc000 vmstorfl vmstorfl.sys Tue Jul 14 11:42:54 2009 (4A5BC67E) fffff880`00e22000 fffff880`00e37000 volmgr volmgr.sys Tue Jul 14 11:19:57 2009 (4A5BC11D) fffff880`00e37000 fffff880`00e93000 volmgrx volmgrx.sys Tue Jul 14 11:20:33 2009 (4A5BC141) fffff880`0114d000 fffff880`01199000 volsnap volsnap.sys Tue Jul 14 11:20:08 2009 (4A5BC128) fffff880`03ddb000 fffff880`03df6000 wanarp wanarp.sys Tue Jul 14 12:10:21 2009 (4A5BCCED) fffff880`03ccd000 fffff880`03cdd000 watchdog watchdog.sys Tue Jul 14 11:37:35 2009 (4A5BC53F) fffff880`00eab000 fffff880`00f4f000 Wdf01000 Wdf01000.sys Tue Jul 14 11:22:07 2009 (4A5BC19F) fffff880`00f4f000 fffff880`00f5e000 WDFLDR WDFLDR.SYS Tue Jul 14 11:19:54 2009 (4A5BC11A) fffff880`03c45000 fffff880`03c4e000 wfplwf wfplwf.sys Tue Jul 14 12:09:26 2009 (4A5BCCB6) fffff880`00fb5000 fffff880`00fbe000 WMILIB WMILIB.SYS Tue Jul 14 11:19:51 2009 (4A5BC117) fffff880`03d3f000 fffff880`03d51000 wpsdrvnt wpsdrvnt.sys Thu Apr 23 10:07:15 2009 (49EF9513) running test now thanks 
ps, quick question
how does it become a hardware problem when everything was working fine before it started happening?
ps, quick question
how does it become a hardware problem when everything was working fine before it started happening?
CPU TEST
approx 6 hours
0 errors 0 warnings
approx 6 hours
0 errors 0 warnings
�� Quote: Originally Posted by stavee 
running test now thanks
ps, quick question
how does it become a hardware problem when everything was working fine before it started happening?
ps, quick question
how does it become a hardware problem when everything was working fine before it started happening?
Good point!!
Running memtest now/overnight and see how that goes
For the gpu test how hot can my graphics get cause i tried it briefly and it went high so I stopped so I could ask question before I leave it on
Running memtest now/overnight and see how that goes
For the gpu test how hot can my graphics get cause i tried it briefly and it went high so I stopped so I could ask question before I leave it on
If it goes above 90C, then it's likely your GPU is overheating.
RAM TEST
7hours 40mins
no errors
and for the GPU TEST
i got to 95 and i stopped it
so should i take my graphics card out and give it a clean?
7hours 40mins
no errors
and for the GPU TEST
i got to 95 and i stopped it
so should i take my graphics card out and give it a clean?
cleaned gpu test has been on for 20mins at 87degrees now
way better than before
how long do i leave it on for?
way better than before
how long do i leave it on for?
30 mins stayed the same so i stopped it there
all components passed tests
so hopefully bsod is solved? ill report back if it happens again
all components passed tests
so hopefully bsod is solved? ill report back if it happens again
Yeah, you are (were!!) looking for it to "peak" then stabilise, obviously at a not too hot temp. 87 sounds fine for a maxxed out graphics card. Hope all goes well.
cheers mate!
and yeah i hope it works im sick of this bsod randomly occurring especially with pretty decent specs
and yeah i hope it works im sick of this bsod randomly occurring especially with pretty decent specs
Go ahead and run the Memtest.
i ran it already my results passed!
crash again
please analyse the new dump to see if anything else shows
Zippyshare.com - 041111-84583-01.dmp
crash again
please analyse the new dump to see if anything else shows
Zippyshare.com - 041111-84583-01.dmp
bump
Please do not bump - if your thread has been missed, VM or PM me.
Dump still points to Hardware (STOP 0x124)
Bugcheck 0x124 = Hardware WHEA = Hardware Failure
Since you already run hardware tests, I suggest that you go to BIOS, take photos of the settings and upload it on your next post (I'm thinking of incorrect settings in your BIOS). If you are overclocking anything (CPU, GPU, RAM) - stop and return to default values.
Regards. . .
Dump still points to Hardware (STOP 0x124)
Bugcheck 0x124 = Hardware WHEA = Hardware Failure
Since you already run hardware tests, I suggest that you go to BIOS, take photos of the settings and upload it on your next post (I'm thinking of incorrect settings in your BIOS). If you are overclocking anything (CPU, GPU, RAM) - stop and return to default values.
Regards. . .
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Dean\Downloads\041111-84583-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`03255e50 Debug session time: Mon Apr 11 18:45:52.604 2011 (UTC + 12:00) System Uptime: 0 days 7:18:40.524 Loading Kernel Symbols .................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000 Unable to add module at 00000000`00000000 Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, fffffa8007dbe028, f2000000, 20008f} Unable to load image PSHED.dll, Win32 error 0n2 *** WARNING: Unable to verify timestamp for PSHED.dll *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* Probably caused by : hardware Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * 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: fffffa8007dbe028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value. Arg4: 000000000020008f, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER *** *** *** ************************************************************************* BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 STACK_TEXT: fffff800`00ba8fd8 fffff880`04213c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort fffff800`00b9cc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`04213c61 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN Followup: MachineOwner --------- 0: kd> lmtsmn start end module name fffff880`00e0f000 fffff880`00e66000 ACPI ACPI.sys unavailable (00000000) fffff880`00de7000 fffff880`00df2000 amdxata amdxata.sys unavailable (00000000) fffff880`00c86000 fffff880`00c8f000 atapi atapi.sys unavailable (00000000) fffff880`00db2000 fffff880`00ddc000 ataport ataport.SYS unavailable (00000000) fffff880`00e9a000 fffff880`00f5a000 CI CI.dll unavailable (00000000) fffff880`018c0000 fffff880`018f0000 CLASSPNP CLASSPNP.SYS unavailable (00000000) fffff880`00cf7000 fffff880`00d55000 CLFS CLFS.SYS unavailable (00000000) fffff880`0112b000 fffff880`0119e000 cng cng.sys unavailable (00000000) fffff880`018aa000 fffff880`018c0000 disk disk.sys unavailable (00000000) fffff880`010b9000 fffff880`010cd000 fileinfo fileinfo.sys unavailable (00000000) fffff880`0106d000 fffff880`010b9000 fltmgr fltmgr.sys unavailable (00000000) fffff880`0122b000 fffff880`01235000 Fs_Rec Fs_Rec.sys unavailable (00000000) fffff880`01870000 fffff880`018aa000 fvevol fvevol.sys unavailable (00000000) fffff880`0142b000 fffff880`01475000 fwpkclnt fwpkclnt.sys unavailable (00000000) fffff800`035f5000 fffff800`0363e000 hal hal.dll Tue Jul 14 13:27:36 2009 (4A5BDF08) fffff880`01867000 fffff880`01870000 hwpolicy hwpolicy.sys unavailable (00000000) fffff800`00bad000 fffff800`00bb7000 kdcom kdcom.dll Tue Jul 14 13:31:07 2009 (4A5BDFDB) fffff880`01200000 fffff880`0121a000 ksecdd ksecdd.sys unavailable (00000000) fffff880`01400000 fffff880`0142b000 ksecpkg ksecpkg.sys unavailable (00000000) fffff880`00c9f000 fffff880`00ce3000 mcupdate mcupdate.dll unavailable (00000000) fffff880`01811000 fffff880`01867000 MDFSYSNT MDFSYSNT.sys unavailable (00000000) fffff880`015f3000 fffff880`01600000 MDPMGRNT MDPMGRNT.SYS unavailable (00000000) fffff880`00c6c000 fffff880`00c86000 mountmgr mountmgr.sys unavailable (00000000) fffff880`00ddc000 fffff880`00de7000 msahci msahci.sys unavailable (00000000) fffff880`00e6f000 fffff880`00e79000 msisadrv msisadrv.sys unavailable (00000000) fffff880`010cd000 fffff880`0112b000 msrpc msrpc.sys unavailable (00000000) fffff880`015e1000 fffff880`015f3000 mup mup.sys unavailable (00000000) fffff880`00e8d000 fffff880`00e97000 mv91cons mv91cons.sys unavailable (00000000) fffff880`0148f000 fffff880`01581000 ndis ndis.sys unavailable (00000000) fffff880`01581000 fffff880`015e1000 NETIO NETIO.SYS unavailable (00000000) fffff800`03018000 fffff800`035f5000 nt ntkrnlmp.exe Wed Oct 27 15:43:09 2010 (4CC791BD) fffff880`0125c000 fffff880`013ff000 Ntfs Ntfs.sys unavailable (00000000) fffff880`00d88000 fffff880`00d9d000 partmgr partmgr.sys unavailable (00000000) fffff880`00d55000 fffff880`00d88000 pci pci.sys unavailable (00000000) fffff880`00e86000 fffff880`00e8d000 pciide pciide.sys unavailable (00000000) fffff880`00c5c000 fffff880`00c6c000 PCIIDEX PCIIDEX.SYS unavailable (00000000) fffff880`0121a000 fffff880`0122b000 pcw pcw.sys unavailable (00000000) fffff880`00ce3000 fffff880`00cf7000 PSHED PSHED.dll unavailable (00000000) fffff880`01000000 fffff880`0103a000 rdyboost rdyboost.sys unavailable (00000000) fffff880`01485000 fffff880`0148d000 spldr spldr.sys unavailable (00000000) fffff880`01603000 fffff880`01800000 tcpip tcpip.sys unavailable (00000000) fffff880`00e79000 fffff880`00e86000 vdrvroot vdrvroot.sys unavailable (00000000) fffff880`01475000 fffff880`01485000 vmstorfl vmstorfl.sys unavailable (00000000) fffff880`00d9d000 fffff880`00db2000 volmgr volmgr.sys unavailable (00000000) fffff880`00c00000 fffff880`00c5c000 volmgrx volmgrx.sys unavailable (00000000) fffff880`0119e000 fffff880`011ea000 volsnap volsnap.sys unavailable (00000000) fffff880`00f5a000 fffff880`00ffe000 Wdf01000 Wdf01000.sys unavailable (00000000) fffff880`00e00000 fffff880`00e0f000 WDFLDR WDFLDR.SYS unavailable (00000000) fffff880`00e66000 fffff880`00e6f000 WMILIB WMILIB.SYS unavailable (00000000) Sorry for not posting these earlier, my comp was doing ok but what do you know, another bsod this morning so heres my bios
http://img571.imageshack.us/f/img0699an.jpg/
http://img20.imageshack.us/i/img0700ez.jpg/
http://img827.imageshack.us/i/img0702rb.jpg/
http://img59.imageshack.us/i/img0703c.jpg/
http://img824.imageshack.us/i/img0704gh.jpg/
http://img705.imageshack.us/i/img0705zx.jpg/
http://img534.imageshack.us/i/img0706yq.jpg/
http://img4.imageshack.us/i/img0707nx.jpg/
if you cant see anything from these COULD it have anything to do with a windows file or something? i understand its showing hardware but may it be something else?
http://img571.imageshack.us/f/img0699an.jpg/
http://img20.imageshack.us/i/img0700ez.jpg/
http://img827.imageshack.us/i/img0702rb.jpg/
http://img59.imageshack.us/i/img0703c.jpg/
http://img824.imageshack.us/i/img0704gh.jpg/
http://img705.imageshack.us/i/img0705zx.jpg/
http://img534.imageshack.us/i/img0706yq.jpg/
http://img4.imageshack.us/i/img0707nx.jpg/
if you cant see anything from these COULD it have anything to do with a windows file or something? i understand its showing hardware but may it be something else?
I've requested someone to take a look at this as hardware is not one of my expertise.
thanks heaps dean, please keep me posted!
x124 stop code means your CPU isn't getting enough voltage.
If you turned it down manually, put it back up. If you left it at stock, you need to bump it up anyways.
Make sure you run Prime95+ for 12+ hours to check for stability.
~Lordbob
If you turned it down manually, put it back up. If you left it at stock, you need to bump it up anyways.
Make sure you run Prime95+ for 12+ hours to check for stability.
~Lordbob
Hay there, what should I be running it at?
�� Quote: Originally Posted by stavee Hay there, what should I be running it at?
~Lordbob
If Lordbob's CPU voltage bump doesn't solve it, let's check the RAM settings.
�� Quote: Originally Posted by stavee
Just to verify, you ran Memtest86+?
With all RAM cards installed?
Which test run did you get to?
These errors can be due to 4GB of RAM, 4 RAM cards installed or 2GB or larger RAM cards.
You will likely need a memory controller voltage bump, be careful too much voltage can cause problems.
If you can post some information, we can try to adjust some settings.
For reference: When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
UseReal Temp , run and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.
Can you post the pics you linked above?
Much easier for everyone to see and saves all of us D/L'ing files.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
�� Quote: Originally Posted by stavee RAM TEST
7hours 40mins
no errors
and for the GPU TEST
i got to 95 and i stopped it
so should i take my graphics card out and give it a clean?
7hours 40mins
no errors
and for the GPU TEST
i got to 95 and i stopped it
so should i take my graphics card out and give it a clean?
Just to verify, you ran Memtest86+?
With all RAM cards installed?
Which test run did you get to?
These errors can be due to 4GB of RAM, 4 RAM cards installed or 2GB or larger RAM cards.
You will likely need a memory controller voltage bump, be careful too much voltage can cause problems.
If you can post some information, we can try to adjust some settings.
For reference: When you run memtest86+ you are looking for bad RAM cards, bad motherboard slots, so you need to follow the testing procedure in the tutorial.
Sometimes errors from these tests can be corrected by adjusting the settings.
RAM - Test with Memtest86+
Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Have you been checking your temperatures?
UseReal Temp , run and check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.
Go to your BIOS and tell us what the CPU, RAM and North Bridge (NB) voltages are.
Can you post the pics you linked above?
Much easier for everyone to see and saves all of us D/L'ing files.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
hay fellas thanks for the input! appreciate it!
ok so here we go
yes i ran Memtest86+ with all cards installed and my cards are 2 gig cards (total 8 gig)
i ran the test for 7hours 40mins so not sure what test i was up to!
here is my cpu-z
Attachment 149450
here is my idle real temp (note, under load it is usually in reverse)
Attachment 149451
my BIOS PHOTOS are as follows
Attachment 149453
Attachment 149454
Attachment 149455
Attachment 149456
Attachment 149457
Attachment 149458
Attachment 149459
Attachment 149460
ok so here we go
yes i ran Memtest86+ with all cards installed and my cards are 2 gig cards (total 8 gig)
i ran the test for 7hours 40mins so not sure what test i was up to!
here is my cpu-z
Attachment 149450
here is my idle real temp (note, under load it is usually in reverse)
Attachment 149451
my BIOS PHOTOS are as follows
Attachment 149453
Attachment 149454
Attachment 149455
Attachment 149456
Attachment 149457
Attachment 149458
Attachment 149459
Attachment 149460
Make sure you run it for more than 12 hours to really make sure it is stable (yes, they can crash at 11 hours in).
It looks like your CPU should be fine at that voltage, and your temps are great. If it does BSOD again sometime soon, you can definitely take the voltage up to around 1.3 without worry.
Always watch the temps as well though.
~Lordbob
It looks like your CPU should be fine at that voltage, and your temps are great. If it does BSOD again sometime soon, you can definitely take the voltage up to around 1.3 without worry.
Always watch the temps as well though.
~Lordbob
Are you running the stock Intel CPU cooler?
What temps do get with a full CPU load?
In your 4th BIOS snip your QPI/Vtt Voltage is set at stock 1.10v.
With total 8GB RAM, 4 RAM cards and 2GB cards, any one of these can require a memory controller voltage bump, with all three you definitely need to increase the memory controller (QPI/Vtt) Voltage.
Change the QPI/Vtt Voltage to 1.15v.
Run memtest86+ for 12 hours, as suggested by Lordbob. If you get any errors, stop the test and let us know.
Welcome to the world of 8GB of RAM. You need longer testing to test all of that RAM.
If it passes then run Prime95 torture test for one hour, temps permitting.
First open RealTemp to monitor CPU temperatures, don't go over 78 degC.
Open Prime95 and stop the test, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 8, then click OK to start the test.
Let us know the results.
What temps do get with a full CPU load?
In your 4th BIOS snip your QPI/Vtt Voltage is set at stock 1.10v.
With total 8GB RAM, 4 RAM cards and 2GB cards, any one of these can require a memory controller voltage bump, with all three you definitely need to increase the memory controller (QPI/Vtt) Voltage.
Change the QPI/Vtt Voltage to 1.15v.
Run memtest86+ for 12 hours, as suggested by Lordbob. If you get any errors, stop the test and let us know.
Welcome to the world of 8GB of RAM. You need longer testing to test all of that RAM.
If it passes then run Prime95 torture test for one hour, temps permitting.
First open RealTemp to monitor CPU temperatures, don't go over 78 degC.
Open Prime95 and stop the test, in Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 8, then click OK to start the test.
Let us know the results.
Thanks again fellas for helping me out here!
Ok so i wont bump up the voltage on cpu just yet
no its not stock cpu cooler, i replaced it not long ago but i would get bsod before that
i will bump up voltage on ram and run test and report results
Ok so i wont bump up the voltage on cpu just yet
no its not stock cpu cooler, i replaced it not long ago but i would get bsod before that
i will bump up voltage on ram and run test and report results
OK HERE WE GO!
its good news in away
i think we may have something?!
i tested ram again (WITHOUT CHANGING VOLTAGE cause i couldnt find the specific voltage you told me)
and i got this within 30 secs
Attachment 149643
this is odd as i ran the test about a week ago for hours and got nothing :S
so ill run it again soon i have to step out atm but i wanted to post to you so you guys could see where we are at and TRY and solve this issue
thanks heaps
its good news in away
i think we may have something?!
i tested ram again (WITHOUT CHANGING VOLTAGE cause i couldnt find the specific voltage you told me)
and i got this within 30 secs
Attachment 149643
this is odd as i ran the test about a week ago for hours and got nothing :S
so ill run it again soon i have to step out atm but i wanted to post to you so you guys could see where we are at and TRY and solve this issue
thanks heaps
�� Quote: Originally Posted by stavee OK HERE WE GO!
its good news in away
i think we may have something?!
i tested ram again (WITHOUT CHANGING VOLTAGE cause i couldnt find the specific voltage you told me)
and i got this within 30 secs
Attachment 149643
this is odd as i ran the test about a week ago for hours and got nothing :S
so ill run it again soon i have to step out atm but i wanted to post to you so you guys could see where we are at and TRY and solve this issue
thanks heaps
its good news in away
i think we may have something?!
i tested ram again (WITHOUT CHANGING VOLTAGE cause i couldnt find the specific voltage you told me)
and i got this within 30 secs
Attachment 149643
this is odd as i ran the test about a week ago for hours and got nothing :S
so ill run it again soon i have to step out atm but i wanted to post to you so you guys could see where we are at and TRY and solve this issue
thanks heaps
~Lordbob
So you still think bump up the CPU voltage?
�� Quote: Originally Posted by stavee So you still think bump up the CPU voltage?
~Lordbob
It is possible that memtest86+ will not show errors everytime, but the settings need adjusting.
Just the nature of electronics.
The BIOS setting is in 'Advanced Voltage Settings', 'Motherboard Voltage Control', under 'CPU'.
Same as the 4th BIOS snip in post #28.
Look for 'QPI/Vtt Voltage'.
It is currently set at 1.10v change it to 1.15v.
Then run memtest86+ for 12 hours, overnight.
Just the nature of electronics.
The BIOS setting is in 'Advanced Voltage Settings', 'Motherboard Voltage Control', under 'CPU'.
Same as the 4th BIOS snip in post #28.
Look for 'QPI/Vtt Voltage'.
It is currently set at 1.10v change it to 1.15v.
Then run memtest86+ for 12 hours, overnight.
Quote:
In your 4th BIOS snip your QPI/Vtt Voltage is set at stock 1.10v.
With total 8GB RAM, 4 RAM cards and 2GB cards, any one of these can require a memory controller voltage bump, with all three you definitely need to increase the memory controller (QPI/Vtt) Voltage.
Change the QPI/Vtt Voltage to 1.15v.
Run memtest86+ for 12 hours, as suggested by Lordbob. If you get any errors, stop the test and let us know.
With total 8GB RAM, 4 RAM cards and 2GB cards, any one of these can require a memory controller voltage bump, with all three you definitely need to increase the memory controller (QPI/Vtt) Voltage.
Change the QPI/Vtt Voltage to 1.15v.
Run memtest86+ for 12 hours, as suggested by Lordbob. If you get any errors, stop the test and let us know.
�� Quote: Originally Posted by Dave76 It is possible that memtest86+ will not show errors everytime, but the settings need adjusting.
Just the nature of electronics.
The BIOS setting is in 'Advanced Voltage Settings', 'Motherboard Voltage Control', under 'CPU'.
Same as the 4th BIOS snip in post #28.
Look for 'QPI/Vtt Voltage'.
It is currently set at 1.10v change it to 1.15v.
Then run memtest86+ for 12 hours, overnight.
Just the nature of electronics.
The BIOS setting is in 'Advanced Voltage Settings', 'Motherboard Voltage Control', under 'CPU'.
Same as the 4th BIOS snip in post #28.
Look for 'QPI/Vtt Voltage'.
It is currently set at 1.10v change it to 1.15v.
Then run memtest86+ for 12 hours, overnight.
Quote:
In your 4th BIOS snip your QPI/Vtt Voltage is set at stock 1.10v.
With total 8GB RAM, 4 RAM cards and 2GB cards, any one of these can require a memory controller voltage bump, with all three you definitely need to increase the memory controller (QPI/Vtt) Voltage.
Change the QPI/Vtt Voltage to 1.15v.
Run memtest86+ for 12 hours, as suggested by Lordbob. If you get any errors, stop the test and let us know.
With total 8GB RAM, 4 RAM cards and 2GB cards, any one of these can require a memory controller voltage bump, with all three you definitely need to increase the memory controller (QPI/Vtt) Voltage.
Change the QPI/Vtt Voltage to 1.15v.
Run memtest86+ for 12 hours, as suggested by Lordbob. If you get any errors, stop the test and let us know.
hay there, i cant change it to 1.15 it jumps past that
Running test again and no errors so far, gonna leave for awhile this time.
Ps. Where do I change CPU voltage?
Ps. Where do I change CPU voltage?
�� Quote: Originally Posted by stavee hay there, i cant change it to 1.15 it jumps past that
Use the 1.170v setting.
Keep it at or below 1.20v.
sure will do that
and just a new update
i ran memtest for 13hours, no errors
weird that i got it before :S
and just a new update
i ran memtest for 13hours, no errors
weird that i got it before :S
I changed the memory voltage, still not sure where to change the CPU voltage
The memory controller voltage bump can stop the memory errors.
Let us know if you get any more BSoDs or STOP 0x00000124 codes.
Let us know if you get any more BSoDs or STOP 0x00000124 codes.
got another one today
how do i change the cpu voltage
how do i change the cpu voltage
�� Quote: Originally Posted by stavee got another one today
how do i change the cpu voltage
how do i change the cpu voltage
~Lordbob
�� Quote: Originally Posted by stavee CPU TEST
approx 6 hours
0 errors 0 warnings
approx 6 hours
0 errors 0 warnings
�� Quote: Originally Posted by Lordbob75 So you have some bad RAM it looks like. That shouldn't cause a 124 (that is from CPU voltage).
~Lordbob
~Lordbob
As mentioned in this post, this stop code can be from any hardware.
RAM is mentioned as a more likely culprit, from my experience this is true.
Quote:
It is important to note that there are many different possible MCE triggers, and one machine's stop 0x124 is likely to be entirely different to another's. Hence, it is best not to place too much emphasis on very specialised ways in which other individuals have resolved their own 0x124 problems - the more exotic the other machine's MCE solution, the less likely it is to apply to your own setup.
I have OC'ed my CPU to 3.84GHz on the stock CPU voltage setting, had to bump it a little when I went above 4GHz.
If the CPU voltage is increased it will generate more heat. This should be avoided unless necessary.
stavee, if you want to check your CPU again, use Prime95 torture test. This will stress the CPU more and some of the RAM.
This is the recommended test to run after adjusting RAM settings which have passed memtest86+.
First open RealTemp to monitor CPU temperatures, don't go over 78 degC.
Open Prime95, stop the test if it starts automatically.
In Advanced tab select 'Round off checking', in the Options tab select 'Torture Test...', in the window that opens select 'Blend', after 'Number of torture test threads to run' enter 8, then click OK to start the test.
Watch the CPU temps.
Run this test for a minimum of 2 hours, or, as Lordbob mentioned 12 hours is considered the minimum by some.
If Prime95 has an error, stops on it's own, or you have another STOP error, bump the 'DRAM voltage' to 1.550v.
It is currently at 1.500v according to previous BIOS snips.
Then run memtest86+ or Prime95 again.
�� Quote: Originally Posted by Dave76 �� Quote: Originally Posted by Lordbob75 So you have some bad RAM it looks like. That shouldn't cause a 124 (that is from CPU voltage).
~Lordbob
~Lordbob
As mentioned in this post, this stop code can be from any hardware.
RAM is mentioned as a more likely culprit, from my experience this is true.
Quote:
It is important to note that there are many different possible MCE triggers, and one machine's stop 0x124 is likely to be entirely different to another's. Hence, it is best not to place too much emphasis on very specialised ways in which other individuals have resolved their own 0x124 problems - the more exotic the other machine's MCE solution, the less likely it is to apply to your own setup.
~Lordbob
ok i bumped the DRAM up to 1.56 so should i run prime95 now?
Yes, if it shows an error or stops unexpectedly, that's a fault.
Seems to be running fine ATM been on for about an hour, I'll let you know the results!
That is good to hear.
Let us know the results.
Let us know the results.
4.5 hours no errors so i stopped
Sounds like the RAM might have needed a little bump up.
~Lordbob
~Lordbob
I ran this test before the voltage bump for 6hours and got no error so shall see of It worked either way, otherwise I think we are out of ideas :s
Could it be anything to do with the harddrive OR registry files?
Could it be anything to do with the harddrive OR registry files?
�� Quote: Originally Posted by stavee I ran this test before the voltage bump for 6hours and got no error so shall see of It worked either way, otherwise I think we are out of ideas :s
Could it be anything to do with the harddrive OR registry files?
Could it be anything to do with the harddrive OR registry files?
~Lordbob
What were your CPU temps while running Prime95?
Have you ran a hard disk test?
What brand HDDs do you have?
Check their website for a hard disk test app.
Seagate Seatools
Western Digital Lifeguard
If you get another BSoD, run memtest86+ again, best to run it overnight.
Due to the nature of electronics, this test can pass a couple of times and then fail again.
It's a good idea to double/triple check it.
Hope it is stable now, let us know how it's running.
Have you ran a hard disk test?
What brand HDDs do you have?
Check their website for a hard disk test app.
Seagate Seatools
Western Digital Lifeguard
If you get another BSoD, run memtest86+ again, best to run it overnight.
Due to the nature of electronics, this test can pass a couple of times and then fail again.
It's a good idea to double/triple check it.
Hope it is stable now, let us know how it's running.
pretty sure my harddrvies are seagate
and its running ok atm but gotta give it sometime first cause can go for a week for no bsod or a couple of days
my temps didnt get hotter than 70degrees
should i run harddrive tests or wait to see if bsod occurs again?
and its running ok atm but gotta give it sometime first cause can go for a week for no bsod or a couple of days
my temps didnt get hotter than 70degrees
should i run harddrive tests or wait to see if bsod occurs again?
If you use SeaGate HDD, then use the SeaTools HDD Diagnostic.
Definitely won't hurt anything to run the hard drive tests now.
Better to know.
Download SIW - System Information for Windows free version, it will tell you everything about your system.
Better to know.
Download SIW - System Information for Windows free version, it will tell you everything about your system.
bsod again
about to use seatools
about to use seatools
Let us know the SeaTools results.
What were the CPU Core temps when you ran Prime95?
Have you checked that all the cables are securely plugged in?
Un-plug them, check for any damage to the connections and wires, then plug them back in.
Look for any possible grounding points on the motherboard.
What were the CPU Core temps when you ran Prime95?
Have you checked that all the cables are securely plugged in?
Un-plug them, check for any damage to the connections and wires, then plug them back in.
Look for any possible grounding points on the motherboard.
Thanks everyone that's helped so far btw!
Seatools passed
And my temps didn't get past 70
Seatools passed
And my temps didn't get past 70
Have you checked that all the cables are securely plugged in?
Un-plug them, check for any damage to the connections and wires, then plug them back in.
Look for any possible grounding points on the motherboard.
Un-plug them, check for any damage to the connections and wires, then plug them back in.
Look for any possible grounding points on the motherboard.
If this is a BSOD problem, then please upload the .dmp file!
Blue Screen of Death (BSOD) Posting Instructions
Blue Screen of Death (BSOD) Posting Instructions
i have previously, its the same error everytime
ill upload the latest one
and @dave, everything looks sweet
ill upload the latest one
and @dave, everything looks sweet
Thank you ... however, I was hoping for the entire report ... there is more information contained within the report, other than just the .dmp file, that can aid in pinpointing the the faulting hardware involved. The last .dmp file is reporting a 0x124 error which is different than a simple 0x116 error. You may want to have a look at this thread for a more detailed explanation of the 0x124 error... Good lucl! 
Stop 0x124 - what it means and what to try
Stop 0x124 - what it means and what to try
I've run various stress tests, checked temps and still can't pin point it to anything, very annoying!
Could a clean install help?
Also this might help, ive noticed the bsod happening when I wake my comp up from sleep if that makes sense
Could a clean install help?
Also this might help, ive noticed the bsod happening when I wake my comp up from sleep if that makes sense
Error code says it's hardware, which may include hardware drivers.
Have you updated all the drivers from the Gigabyte site?
How many USB devices do you have plugged in?
Can you get another known working keyboard and mouse to test with?
Looks like the next step is going to be remove all non-essential devices, sound card, non-OS HDDs, everything possible, if you still have BSoDs you need to start replacing the other hardware with spare or borrowed components until you can find the culprit.
If that fails to turn anything up then you need to do a bench test.
Have you updated all the drivers from the Gigabyte site?
How many USB devices do you have plugged in?
Can you get another known working keyboard and mouse to test with?
Looks like the next step is going to be remove all non-essential devices, sound card, non-OS HDDs, everything possible, if you still have BSoDs you need to start replacing the other hardware with spare or borrowed components until you can find the culprit.
If that fails to turn anything up then you need to do a bench test.
Worst case scenario in this situation is a manual search. This means unplugging every and all non-essential components and running the system. Then you add each component back in 1 at a time until the error pops up.
~Lordbob
~Lordbob
hay guys its been awhile!!
i was going well but happened again
i unpluggged a harddrive i thought was causing the program as i installed it around the time of the bsod but it happened whilst this was unplugged so cant be
i have another theory
it could be my cd drive as i also changed from an ide drive to sate drive so maybe its that? should i just unplug it for the time being and see or plug the ide drive back in?
i was going well but happened again
i unpluggged a harddrive i thought was causing the program as i installed it around the time of the bsod but it happened whilst this was unplugged so cant be
i have another theory
it could be my cd drive as i also changed from an ide drive to sate drive so maybe its that? should i just unplug it for the time being and see or plug the ide drive back in?
also its getting me to the point where i dont think its a hardware problem cause i run another OS on here (hacnkintosh) and its perfect on there. infact without it on there i probably wouldnt be able to boot back into windows as i need to boot into mac - shutdown - then boot back into windows... if it crashes and loads to windows again it just wont boot
Take every componet that you don't absolutely need, check for BSoDs.
Minimum should be one OS HDD, no CD/DVD drive, minimum RAM for your system to run - 2GB, nothing external except monitor, keyboard and mouse.
Change the keyboard and mouse if you get a BSoD.
If you get the system to run stable, start adding the other components one at a time and test for BSoDs, when your are sure it's stable add another component.
Let us know how it's going.
Minimum should be one OS HDD, no CD/DVD drive, minimum RAM for your system to run - 2GB, nothing external except monitor, keyboard and mouse.
Change the keyboard and mouse if you get a BSoD.
If you get the system to run stable, start adding the other components one at a time and test for BSoDs, when your are sure it's stable add another component.
Let us know how it's going.
Không có nhận xét nào:
Đăng nhận xét