BSOD while idle overnight

[ICIT2LOL]

Yes no problems there. Having said that volts might be ok - current is another matter but I am guessing it is ok too.

 

[Thookrull]

I got a freeze up while watching a movie on VLC player. It did not create a new .dmp file but I uploaded the info anyway. (I also had other programs running such as my browser).

This type of freeze up is what's mainly happening pretty much for as long as I can remember (1-2yrs?). Sometimes a few times a day, other times it can go for a few days without freezing up. During the freeze, I cannot do anything with the mouse or keyboard and if there was sound, it will play that last bit of that sound continuously like a buzz sound. To restart, I need to push the reset button on the computer case and sometimes that doesn't work so I need to do a hard stop/start (keeping the power button pressed to reset).

 

[ICIT2LOL]

Thookrull mate I think maybe you have a faulty CPU or a faulty board socket as seen in the dump file readout and I am not sure what can be done about it as it is intermittent and that it comes to a complete standstill hence I think the buzzing sound.
There is also some mention of the NVidia problem also.

See this
BSOD - Stop: 0x124 - Microsoft Community

BugCheck 124, {0, fffffa800eb27028, be000000, 800400}
*** [COLOR=red]WARNING: Unable to verify timestamp for nvlddmkm.sys
[/COLOR]*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : GenuineIntel
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: fffffa800eb27028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff800`00ba6a98 fffff800`03016a3b : 00000000`00000124 00000000`00000000 fffffa80`0eb27028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba6aa0 fffff800`031d9713 : 00000000`00000001 fffffa80`0dc52870 00000000`00000000 fffffa80`0dc528c0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba6ae0 fffff800`03016700 : 00000000`00000728 fffffa80`0dc52870 fffff800`00ba6e70 fffff800`00ba6e00 : nt!WheaReportHwError+0x263
fffff800`00ba6b40 fffff800`03016052 : fffffa80`0dc52870 fffff800`00ba6e70 fffffa80`0dc52870 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba6c90 fffff800`03015f0d : 00000000`00000004 00000000`00000001 fffff800`00ba6ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba6cd0 fffff800`03009e88 : fffffa80`0fed0000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba6d00 fffff800`030c07ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba6d30 fffff800`030c0613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba6e70 fffff880`04c3f005 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9a6e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x3b3005

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x124_GenuineIntel_PROCESSOR_MAE[/COLOR]
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae
FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
Followup: MachineOwner

 

[Thookrull]

Got a bluescreen this morning, new dump.

In regards to nvlddmkm.sys I found this post - Bsod On Startup - Nvlddmkm.sys - Windows Vista
I changed the name of it and re-installed the drivers, we'll see how it goes.

 

[ICIT2LOL]

Hmm still got that CPU error Eric

*******************************************************************************
*                                                                             *
*                        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: fffffa800ec26028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------

BUGCHECK_STR:  [COLOR=red]0x124_GenuineIntel[/COLOR]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  f
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff800`04486a98 fffff800`0302ea3b : 00000000`00000124 00000000`00000000 fffffa80`0ec26028 00000000`be000000 : nt!KeBugCheckEx
fffff800`04486aa0 fffff800`031f1713 : 00000000`00000001 fffffa80`0eb23a60 00000000`00000000 fffffa80`0eb23ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`04486ae0 fffff800`0302e700 : 00000000`00000728 fffffa80`0eb23a60 fffff800`04486e70 fffff800`04486e00 : nt!WheaReportHwError+0x263
fffff800`04486b40 fffff800`0302e052 : fffffa80`0eb23a60 fffff800`04486e70 fffffa80`0eb23a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`04486c90 fffff800`0302df0d : 00000000`00000004 00000000`00000001 fffff800`04486ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`04486cd0 fffff800`03021e88 : fffffa80`10148000 fffffa80`10148000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04486d00 fffff800`030d87ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`04486d30 fffff800`030d8613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`04486e70 fffff880`048084ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`0447a530 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x3e

STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
IMAGE_VERSION:  
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  [COLOR=red]km:x64_0x124_genuineintel_processor_mae[/COLOR]
FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
Followup: MachineOwner

Run through this too 0x124_GenuineIntel - WIN7_DRIVER_FAULT - WHEA_UNCORRECTABLE_ERROR - Microsoft Community

 

[Slartybart]

Just an aside: you might want to validate the NVidia drivers by doing a clean re-install following this tutorial:
http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

I know ICIT2LOL is focusing on the CPU - but bugchecks often get reported in the last piece in the chain

Good luck,

Bill
.

 

[ICIT2LOL]

Yes Bill I did see the graphics stuff too but it seemed like doubling up on what you posted so I didn't mention it. The CPU seems to crop up in all the files though and I am not sure if it is the actual CPU itself or something that is supplying power for example to it.