Jump to content

Sign of bad things to come?

Omnislash89
 Share
Posted

I started folding on max settings, typically needing to pause and cool before beginning another session, until I realized folding on fewer CPU cores and on medium (or light) versus high would allow me to fold overnight. I typically saw my GPU hover around 58'C and the CPU would be on average 3-4' cooler. and would run quite dependably for hours and hours.

Today, I noticed something odd when I awoke to find the room oddly cool and the PC at the sign-in screen. After coming home from work, I was able to run for about an hour until the same happened, and in the last hour faced two WHEA_Uncorectable errors. I carefully watched the thermals this latest time and saw it approach 56'C on a few instances, but nothing like th 58-59'C ceilings that it would reach during prolonged folding sessions.

I get that something failing somewhere...I just don't know which component and whether it is power or thermal related... Anyone have similar circumstances, and if so, how did you resolve this without sacrificing folding power?

Equipment: Zotac AMP! Edition GTX780 @ 1.1GHz (Factory OC) & 4930K @ 4.7GHz

Details courtesy of WhoCrashed (one of the main reasons I went back from W10, due to incompatibility with it):::

 On Tue 8/25/2015 1:45:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082415-9500-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE0018B5F1028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Tue 8/25/2015 1:45:40 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFE0018B5F1028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Tue 8/25/2015 1:36:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082415-9515-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE001CD3F3028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Tue 8/25/2015 12:26:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082415-9734-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE000D2AD8028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 

This is the Craft of PC Building. Mastered. #AshlarPC

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Those temps are fine, google that error though

The error is a generic hardware failure error, hence WHEA=Windows Hardware Error Architecture.

This is the Craft of PC Building. Mastered. #AshlarPC

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

This is most likely the cause:

4930K @ 4.7GHz

 

Your OC is just unstable. You can either: A- Raise voltage to try and achieve stability, but doing so will cause heat problems if you don't have a good cooler. B- lower the multiplier until it no longer crashes. C- a mixture of A and B (anyone got the Resident Evil 3 reference?).

Want to help researchers improve the lives on millions of people with just your computer? Then join World Community Grid distributed computing, and start helping the world to solve it's most difficult problems!

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

This is most likely the cause:

 

Your OC is just unstable. You can either: A- Raise voltage to try and achieve stability, but doing so will cause heat problems if you don't have a good cooler. B- lower the multiplier until it no longer crashes. C- a mixture of A and B (anyone got the Resident Evil 3 reference?).

+1, get this error all the time the second I bump my cpu even 100mhz higher or 0.1v lower xD

Gaming PC: CPU: i7 4770k@4.2GHz w/ CM Nepton 140xl, GPU: Gigabyte 1070 @2050, RAM: ADATA XPG V1 16GB@2133MHz, Mobo: MSI Z97 Gaming 7, Case: Corsair NZXT S340.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

+1, get this error all the time the second I bump my cpu even 100mhz higher or 0.1v lower xD

I just find it odd that this happened all of the sudden. Perhaps I am causing more stress than I realized on my components and now they require more power to keep up the same frequency? Haven't changed anything in my OC setting since I began folding a few weeks back.

Will raise vCore offset by .05v and report back.

This is the Craft of PC Building. Mastered. #AshlarPC

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

No bones. Changing the core voltage and active number of cores did not help.

Turns out that lowering the number of cores from 10 or 8 to 6 made it even more unstable, and it was only stable at 4 cores.
After running at 4 cores for a few days, I returned it 8 cores for the entire evening yesterday and all day today (up to the last half hour or so)

Crashed with the typical WHEA_Uncorrectable_Error every 5-10 minutes.

Not sure what is causing this, as I went into the BIOS and removed the thermal protection, due my attempt to monitor the CPU thermals and shut down PC if it became dangerous... but it never made it that far. Never attained thermals at the level the previous BSOD occurred at... which would lead me to believe iot is a hardware error independent of voltage OR thermals. (even BSOD'd on me when writing the first draft of this post)

If anyone has ever resolved similar situation, please let me know ALL steps taken. I am running both a CPU and GPU slot, and again, all of these issues have occurred in the last 10 days or so, even after 3 weeks of folding. Went back to original settings when I installed FAH and apparently that isn't even stable.


--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 8/30/2015 8:43:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083015-10187-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE000B7BF7028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/30/2015 8:43:16 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFE000B7BF7028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/30/2015 8:34:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083015-9640-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE000D2FF6028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/30/2015 8:11:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083015-9406-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE001DF9F0028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/30/2015 7:13:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083015-9500-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE00154D74028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 8/30/2015 7:02:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083015-9843-01.dmp
This was probably caused by the following module: hal.dll (hal+0x37213)
Bugcheck code: 0x124 (0x0, 0xFFFFE001424AF028, 0xBE200000, 0xB110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

This is the Craft of PC Building. Mastered. #AshlarPC

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Did you OC GPU or RAM? Maybe those are the cause for the errors. If you did, try removing them.

 

Also, did you try lowering the OC to 4.6ghz?

Want to help researchers improve the lives on millions of people with just your computer? Then join World Community Grid distributed computing, and start helping the world to solve it's most difficult problems!

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Follow my BSOD posting instructions pinned in the Troubleshooting subforum: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

 

I'll take a look at the dump files in WinDBG. Do me a favor, and never use WhoCrashed, it sucks, isn't always accurate, and there is no way of examining the memory, drivers, or stack information from it.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Follow my BSOD posting instructions pinned in the Troubleshooting subforum: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

 

I'll take a look at the dump files in WinDBG. Do me a favor, and never use WhoCrashed, it sucks, isn't always accurate, and there is no way of examining the memory, drivers, or stack information from it.

I have the dump files, but when attempting to run the Resource Monitor report, the following occurs:

 

post-250792-0-02403600-1441062497.png

post-250792-0-02403600-1441062497.png

This is the Craft of PC Building. Mastered. #AshlarPC

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

I have the dump files, but when attempting to run the Resource Monitor report, the following occurs:

 

SKip that step then. The dump files themselves should be enough for me to work off of.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Ok. Took a look at the dump files in the Windows Debugger (WinDBG). I've included the dump outputs in the spoiler below for reference:

 

The bugcheck string was "0x124_GenuineIntel" and the failure bucket id was "X64_0x124_GenuineIntel_PROCESSOR_CACHE".

 

What this essentially means is an unstable overclock, some corruption or I/O issue from the CPU cache caused all of the BSODs. I'd suggest also adjusting the Vdroop settings in your BIOS to something more aggressive. While you're at it, update your Nvidia GPU drivers if necessary. One of the processes also involved "NvStreamService" which is a part of the Nvidia GPU driver. If you happened to be folding on your GPU, this may be why.

 

So, I have a question: Do you run your memory under a XMP Profile? XMP makes the BCLK run slightly faster at 133Mhz.

If you want, try to also play around with the CPU Cache Ratio in the BIOS to make it run slightly slower than the CPU ratio.

Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`f8a7a000 PsLoadedModuleList = 0xfffff800`f8d4f7b0Debug session time: Sun Aug 30 16:11:58.984 2015 (UTC - 4:00)System Uptime: 0 days 0:57:30.656********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001df9f0028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  FahCore_a4.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`36b33ef8 fffff800`f8a41213 : 00000000`00000124 00000000`00000000 ffffe001`df9f0028 00000000`be200000 : nt!KeBugCheckExffffd000`36b33f00 fffff800`f8c3b209 : 00000000`00000001 ffffe001`da4e95e0 ffffe001`da4e95e0 ffffe001`df9f0028 : hal!HalBugCheckSystem+0xcfffffd000`36b33f40 fffff800`f8a416a0 : 00000000`00000728 00000000`0000000a ffffd000`36b34330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`36b33fa0 fffff800`f8a41a0d : ffffe001`00000010 ffffe001`da4e95e0 ffffd000`36b34148 ffffe001`da4e95e0 : hal!HalpMcaReportError+0x50ffffd000`36b340f0 fffff800`f8a418f8 : ffffe001`da4e86b0 00000000`00000001 00000000`0000000a 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`36b34140 fffff800`f8a41b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`36b34180 fffff800`f8a41ccf : ffffe001`da4e86b0 ffffd000`36b343b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`36b341b0 fffff800`f8bd44bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`36b341e0 fffff800`f8bd4271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`36b34320 00000000`006655ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x17100000000`04a8e6b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6655efSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`49689000 PsLoadedModuleList = 0xfffff800`4995e7b0Debug session time: Sun Aug 30 15:13:28.707 2015 (UTC - 4:00)System Uptime: 0 days 0:09:35.379********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe00154d74028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`27d33ef8 fffff800`49650213 : 00000000`00000124 00000000`00000000 ffffe001`54d74028 00000000`be200000 : nt!KeBugCheckExffffd000`27d33f00 fffff800`4984a209 : 00000000`00000001 ffffe001`4f8e85e0 ffffe001`4f8e85e0 ffffe001`54d74028 : hal!HalBugCheckSystem+0xcfffffd000`27d33f40 fffff800`496506a0 : 00000000`00000728 00000000`0000000a ffffd000`27d34330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`27d33fa0 fffff800`49650a0d : ffffe001`00000010 ffffe001`4f8e85e0 ffffd000`27d34148 ffffe001`4f8e85e0 : hal!HalpMcaReportError+0x50ffffd000`27d340f0 fffff800`496508f8 : ffffe001`4f8e76b0 00000000`00000001 00000000`0000000a 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`27d34140 fffff800`49650b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`27d34180 fffff800`49650ccf : ffffe001`4f8e76b0 ffffd000`27d343b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`27d341b0 fffff800`497e34bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`27d341e0 fffff800`497e3271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`27d34320 fffff800`5a72e214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`27d548e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff802`8b27f000 PsLoadedModuleList = 0xfffff802`8b5547b0Debug session time: Sun Aug 30 16:34:03.737 2015 (UTC - 4:00)System Uptime: 0 days 0:17:54.409********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe000d2ff6028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  NvStreamServicCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`5ff33ef8 fffff802`8b246213 : 00000000`00000124 00000000`00000000 ffffe000`d2ff6028 00000000`be200000 : nt!KeBugCheckExffffd000`5ff33f00 fffff802`8b440209 : 00000000`00000001 ffffe000`cdae95e0 ffffe000`cdae95e0 ffffe000`d2ff6028 : hal!HalBugCheckSystem+0xcfffffd000`5ff33f40 fffff802`8b2466a0 : 00000000`00000728 00000000`0000000a ffffd000`5ff34330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`5ff33fa0 fffff802`8b246a0d : ffffe000`00000010 ffffe000`cdae95e0 ffffd000`5ff34148 ffffe000`cdae95e0 : hal!HalpMcaReportError+0x50ffffd000`5ff340f0 fffff802`8b2468f8 : ffffe000`cdae86b0 00000000`00000001 00000000`0000000a 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`5ff34140 fffff802`8b246b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`5ff34180 fffff802`8b246ccf : ffffe000`cdae86b0 ffffd000`5ff343b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`5ff341b0 fffff802`8b3d94bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`5ff341e0 fffff802`8b3d9271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`5ff34320 00007ff7`5fdfac17 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171000000ba`abafeda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff7`5fdfac17STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`bcc84000 PsLoadedModuleList = 0xfffff800`bcf597b0Debug session time: Sun Aug 30 15:02:54.918 2015 (UTC - 4:00)System Uptime: 1 days 1:30:28.590********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001424af028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  FahCore_a4.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`725d9ef8 fffff800`bcc4b213 : 00000000`00000124 00000000`00000000 ffffe001`424af028 00000000`be200000 : nt!KeBugCheckExffffd000`725d9f00 fffff800`bce45209 : 00000000`00000001 ffffe001`3cce7a60 ffffe001`3cce7a60 ffffe001`424af028 : hal!HalBugCheckSystem+0xcfffffd000`725d9f40 fffff800`bcc4b6a0 : 00000000`00000728 00000000`00000002 ffffd000`725da330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`725d9fa0 fffff800`bcc4ba0d : ffffe001`00000010 ffffe001`3cce7a60 ffffd000`725da148 ffffe001`3cce7a60 : hal!HalpMcaReportError+0x50ffffd000`725da0f0 fffff800`bcc4b8f8 : ffffe001`3cce7130 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`725da140 fffff800`bcc4bb42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`725da180 fffff800`bcc4bccf : ffffe001`3cce7130 ffffd000`725da3b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`725da1b0 fffff800`bcdde4bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`725da1e0 fffff800`bcdde271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`725da320 00000000`007b577e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x17100000000`0343e880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7b577eSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff803`b2876000 PsLoadedModuleList = 0xfffff803`b2b4b7b0Debug session time: Sun Aug 30 16:43:16.899 2015 (UTC - 4:00)System Uptime: 0 days 0:06:09.572********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe000b7bf7028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  fSTACK_TEXT:  fffff803`b436da38 fffff803`b283d213 : 00000000`00000124 00000000`00000000 ffffe000`b7bf7028 00000000`be200000 : nt!KeBugCheckExfffff803`b436da40 fffff803`b2a37209 : 00000000`00000001 ffffe000`b47ce1a0 ffffe000`b47ce1a0 ffffe000`b7bf7028 : hal!HalBugCheckSystem+0xcffffff803`b436da80 fffff803`b283d6a0 : 00000000`00000728 00000000`00000000 fffff803`b436de70 00000000`00000000 : nt!WheaReportHwError+0x22dfffff803`b436dae0 fffff803`b283da0d : ffffe000`00000010 ffffe000`b47ce1a0 fffff803`b436dc88 ffffe000`b47ce1a0 : hal!HalpMcaReportError+0x50fffff803`b436dc30 fffff803`b283d8f8 : ffffe000`b36e7fd0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1fffff803`b436dc80 fffff803`b283db42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4fffff803`b436dcc0 fffff803`b283dccf : ffffe000`b36e7fd0 fffff803`b436def0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xcefffff803`b436dcf0 fffff803`b29d04bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40fffff803`b436dd20 fffff803`b29d0271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bfffff803`b436de60 fffff800`188b4214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171fffff803`b43598e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`29e19000 PsLoadedModuleList = 0xfffff800`2a0ee7b0Debug session time: Mon Aug 31 20:24:35.396 2015 (UTC - 4:00)System Uptime: 1 days 3:40:49.069********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe000a87f9028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  chrome.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd001`7fe49ef8 fffff800`2a5e0213 : 00000000`00000124 00000000`00000000 ffffe000`a87f9028 00000000`be200000 : nt!KeBugCheckExffffd001`7fe49f00 fffff800`29fda209 : 00000000`00000001 ffffe000`a2ee8d40 ffffe000`a2ee8d40 ffffe000`a87f9028 : hal!HalBugCheckSystem+0xcfffffd001`7fe49f40 fffff800`2a5e06a0 : 00000000`00000728 00000000`00000004 ffffd001`7fe4a330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd001`7fe49fa0 fffff800`2a5e0a0d : ffffe000`00000010 ffffe000`a2ee8d40 ffffd001`7fe4a148 ffffe000`a2ee8d40 : hal!HalpMcaReportError+0x50ffffd001`7fe4a0f0 fffff800`2a5e08f8 : ffffe000`a2ee8290 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd001`7fe4a140 fffff800`2a5e0b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd001`7fe4a180 fffff800`2a5e0ccf : ffffe000`a2ee8290 ffffd001`7fe4a3b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd001`7fe4a1b0 fffff800`29f734bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`7fe4a1e0 fffff800`29f73271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`7fe4a320 000004e5`003445c8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171000004e5`fea5b390 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4e5`003445c8STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Ok. Took a look at the dump files in the Windows Debugger (WinDBG). I've included the dump outputs in the spoiler below for reference:

 

The bugcheck string was "0x124_GenuineIntel" and the failure bucket id was "X64_0x124_GenuineIntel_PROCESSOR_CACHE".

 

What this essentially means is an unstable overclock, some corruption or I/O issue from the CPU cache caused all of the BSODs. I'd suggest also adjusting the Vdroop settings in your BIOS to something more aggressive. While you're at it, update your Nvidia GPU drivers if necessary. One of the processes also involved "NvStreamService" which is a part of the Nvidia GPU driver. If you happened to be folding on your GPU, this may be why.

 

So, I have a question: Do you run your memory under a XMP Profile? XMP makes the BCLK run slightly faster at 133Mhz.

If you want, try to also play around with the CPU Cache Ratio in the BIOS to make it run slightly slower than the CPU ratio.

I currently run on tweaked settings from the XMP, so while it is near XMP (for my LV DDR3), it only adjected voltage up from 1.35v to 1.5v, and T2 ->T1 command rate.

I also run my CPU at 4.7GHz at an offset of +.065v and Very High load line calibration.

Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`f8a7a000 PsLoadedModuleList = 0xfffff800`f8d4f7b0Debug session time: Sun Aug 30 16:11:58.984 2015 (UTC - 4:00)System Uptime: 0 days 0:57:30.656********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001df9f0028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  FahCore_a4.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`36b33ef8 fffff800`f8a41213 : 00000000`00000124 00000000`00000000 ffffe001`df9f0028 00000000`be200000 : nt!KeBugCheckExffffd000`36b33f00 fffff800`f8c3b209 : 00000000`00000001 ffffe001`da4e95e0 ffffe001`da4e95e0 ffffe001`df9f0028 : hal!HalBugCheckSystem+0xcfffffd000`36b33f40 fffff800`f8a416a0 : 00000000`00000728 00000000`0000000a ffffd000`36b34330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`36b33fa0 fffff800`f8a41a0d : ffffe001`00000010 ffffe001`da4e95e0 ffffd000`36b34148 ffffe001`da4e95e0 : hal!HalpMcaReportError+0x50ffffd000`36b340f0 fffff800`f8a418f8 : ffffe001`da4e86b0 00000000`00000001 00000000`0000000a 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`36b34140 fffff800`f8a41b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`36b34180 fffff800`f8a41ccf : ffffe001`da4e86b0 ffffd000`36b343b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`36b341b0 fffff800`f8bd44bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`36b341e0 fffff800`f8bd4271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`36b34320 00000000`006655ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x17100000000`04a8e6b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6655efSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`49689000 PsLoadedModuleList = 0xfffff800`4995e7b0Debug session time: Sun Aug 30 15:13:28.707 2015 (UTC - 4:00)System Uptime: 0 days 0:09:35.379********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe00154d74028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`27d33ef8 fffff800`49650213 : 00000000`00000124 00000000`00000000 ffffe001`54d74028 00000000`be200000 : nt!KeBugCheckExffffd000`27d33f00 fffff800`4984a209 : 00000000`00000001 ffffe001`4f8e85e0 ffffe001`4f8e85e0 ffffe001`54d74028 : hal!HalBugCheckSystem+0xcfffffd000`27d33f40 fffff800`496506a0 : 00000000`00000728 00000000`0000000a ffffd000`27d34330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`27d33fa0 fffff800`49650a0d : ffffe001`00000010 ffffe001`4f8e85e0 ffffd000`27d34148 ffffe001`4f8e85e0 : hal!HalpMcaReportError+0x50ffffd000`27d340f0 fffff800`496508f8 : ffffe001`4f8e76b0 00000000`00000001 00000000`0000000a 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`27d34140 fffff800`49650b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`27d34180 fffff800`49650ccf : ffffe001`4f8e76b0 ffffd000`27d343b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`27d341b0 fffff800`497e34bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`27d341e0 fffff800`497e3271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`27d34320 fffff800`5a72e214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171ffffd000`27d548e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff802`8b27f000 PsLoadedModuleList = 0xfffff802`8b5547b0Debug session time: Sun Aug 30 16:34:03.737 2015 (UTC - 4:00)System Uptime: 0 days 0:17:54.409********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe000d2ff6028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  NvStreamServicCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`5ff33ef8 fffff802`8b246213 : 00000000`00000124 00000000`00000000 ffffe000`d2ff6028 00000000`be200000 : nt!KeBugCheckExffffd000`5ff33f00 fffff802`8b440209 : 00000000`00000001 ffffe000`cdae95e0 ffffe000`cdae95e0 ffffe000`d2ff6028 : hal!HalBugCheckSystem+0xcfffffd000`5ff33f40 fffff802`8b2466a0 : 00000000`00000728 00000000`0000000a ffffd000`5ff34330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`5ff33fa0 fffff802`8b246a0d : ffffe000`00000010 ffffe000`cdae95e0 ffffd000`5ff34148 ffffe000`cdae95e0 : hal!HalpMcaReportError+0x50ffffd000`5ff340f0 fffff802`8b2468f8 : ffffe000`cdae86b0 00000000`00000001 00000000`0000000a 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`5ff34140 fffff802`8b246b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`5ff34180 fffff802`8b246ccf : ffffe000`cdae86b0 ffffd000`5ff343b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`5ff341b0 fffff802`8b3d94bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`5ff341e0 fffff802`8b3d9271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`5ff34320 00007ff7`5fdfac17 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171000000ba`abafeda8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ff7`5fdfac17STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`bcc84000 PsLoadedModuleList = 0xfffff800`bcf597b0Debug session time: Sun Aug 30 15:02:54.918 2015 (UTC - 4:00)System Uptime: 1 days 1:30:28.590********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe001424af028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  FahCore_a4.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd000`725d9ef8 fffff800`bcc4b213 : 00000000`00000124 00000000`00000000 ffffe001`424af028 00000000`be200000 : nt!KeBugCheckExffffd000`725d9f00 fffff800`bce45209 : 00000000`00000001 ffffe001`3cce7a60 ffffe001`3cce7a60 ffffe001`424af028 : hal!HalBugCheckSystem+0xcfffffd000`725d9f40 fffff800`bcc4b6a0 : 00000000`00000728 00000000`00000002 ffffd000`725da330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd000`725d9fa0 fffff800`bcc4ba0d : ffffe001`00000010 ffffe001`3cce7a60 ffffd000`725da148 ffffe001`3cce7a60 : hal!HalpMcaReportError+0x50ffffd000`725da0f0 fffff800`bcc4b8f8 : ffffe001`3cce7130 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd000`725da140 fffff800`bcc4bb42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd000`725da180 fffff800`bcc4bccf : ffffe001`3cce7130 ffffd000`725da3b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd000`725da1b0 fffff800`bcdde4bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd000`725da1e0 fffff800`bcdde271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd000`725da320 00000000`007b577e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x17100000000`0343e880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7b577eSTACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff803`b2876000 PsLoadedModuleList = 0xfffff803`b2b4b7b0Debug session time: Sun Aug 30 16:43:16.899 2015 (UTC - 4:00)System Uptime: 0 days 0:06:09.572********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe000b7bf7028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  fSTACK_TEXT:  fffff803`b436da38 fffff803`b283d213 : 00000000`00000124 00000000`00000000 ffffe000`b7bf7028 00000000`be200000 : nt!KeBugCheckExfffff803`b436da40 fffff803`b2a37209 : 00000000`00000001 ffffe000`b47ce1a0 ffffe000`b47ce1a0 ffffe000`b7bf7028 : hal!HalBugCheckSystem+0xcffffff803`b436da80 fffff803`b283d6a0 : 00000000`00000728 00000000`00000000 fffff803`b436de70 00000000`00000000 : nt!WheaReportHwError+0x22dfffff803`b436dae0 fffff803`b283da0d : ffffe000`00000010 ffffe000`b47ce1a0 fffff803`b436dc88 ffffe000`b47ce1a0 : hal!HalpMcaReportError+0x50fffff803`b436dc30 fffff803`b283d8f8 : ffffe000`b36e7fd0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe1fffff803`b436dc80 fffff803`b283db42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4fffff803`b436dcc0 fffff803`b283dccf : ffffe000`b36e7fd0 fffff803`b436def0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xcefffff803`b436dcf0 fffff803`b29d04bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40fffff803`b436dd20 fffff803`b29d0271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bfffff803`b436de60 fffff800`188b4214 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171fffff803`b43598e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x18STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 9600.17936.amd64fre.winblue_ltsb.150715-0840Machine Name:Kernel base = 0xfffff800`29e19000 PsLoadedModuleList = 0xfffff800`2a0ee7b0Debug session time: Mon Aug 31 20:24:35.396 2015 (UTC - 4:00)System Uptime: 1 days 3:40:49.069********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffe000a87f9028, Address of the WHEA_ERROR_RECORD structure.Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  chrome.exeCURRENT_IRQL:  fSTACK_TEXT:  ffffd001`7fe49ef8 fffff800`2a5e0213 : 00000000`00000124 00000000`00000000 ffffe000`a87f9028 00000000`be200000 : nt!KeBugCheckExffffd001`7fe49f00 fffff800`29fda209 : 00000000`00000001 ffffe000`a2ee8d40 ffffe000`a2ee8d40 ffffe000`a87f9028 : hal!HalBugCheckSystem+0xcfffffd001`7fe49f40 fffff800`2a5e06a0 : 00000000`00000728 00000000`00000004 ffffd001`7fe4a330 00000000`00000000 : nt!WheaReportHwError+0x22dffffd001`7fe49fa0 fffff800`2a5e0a0d : ffffe000`00000010 ffffe000`a2ee8d40 ffffd001`7fe4a148 ffffe000`a2ee8d40 : hal!HalpMcaReportError+0x50ffffd001`7fe4a0f0 fffff800`2a5e08f8 : ffffe000`a2ee8290 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xe1ffffd001`7fe4a140 fffff800`2a5e0b42 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4ffffd001`7fe4a180 fffff800`2a5e0ccf : ffffe000`a2ee8290 ffffd001`7fe4a3b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xceffffd001`7fe4a1b0 fffff800`29f734bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40ffffd001`7fe4a1e0 fffff800`29f73271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bffffd001`7fe4a320 000004e5`003445c8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171000004e5`fea5b390 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x4e5`003445c8STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHEFollowup: MachineOwner 

This is the Craft of PC Building. Mastered. #AshlarPC

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

I currently run on tweaked settings from the XMP, so while it is near XMP (for my LV DDR3), it only adjected voltage up from 1.35v to 1.5v, and T2 ->T1 command rate.

I also run my CPU at 4.7GHz at an offset of +.065v and Very High load line calibration.

Try adjusting your Memory timings and adjusting your CPU Cache multiplier to something a bit lower. Don't have to be by much, but for now, your settings are indeed unstable. 

Your best bet would be to dial down your settings until you no longer get crashes. Seems like you have got a bit of testing testing to do.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted
  • Author

Try adjusting your Memory timings and adjusting your CPU Cache multiplier to something a bit lower. Don't have to be by much, but for now, your settings are indeed unstable. 

Your best bet would be to dial down your settings until you no longer get crashes. Seems like you have got a bit of testing testing to do.

It's funny. FAH is turning out to be a more strict stability test than AIDA64, haha! Will do. IF you have a suggested Cache ratio, let me know (also, will that be a voltage or a frequency, just so I know what  I am looking for in the BIOS. (using a Rampage IV Gene)

Much thanks again, @ionbasa!

This is the Craft of PC Building. Mastered. #AshlarPC

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

It's funny. FAH is turning out to be a more strict stability test than AIDA64, haha! Will do. IF you have a suggested Cache ratio, let me know (also, will that be a voltage or a frequency, just so I know what  I am looking for in the BIOS. (using a Rampage IV Gene)

Much thanks again, @ionbasa!

Cache ratio is similar to the CPU multiplier. It takes the BCLK * Cache Ratio = Cache Frequency.

Unfortunately, I don't have an suggested cache ratio for you as I don't use k-series chips.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Folding@home, Boinc, and Coin Mining

×