Freezing/BSOD Randomly, Different Error Codes

DeathPhage · 16 Oct 2012

I would like to thank everyone in advance who reads this and offers help.

I recently build a new computer and everything was running fine. A few days later I start getting random freeze ups and BSOD's. I mean random, there wasn't one thing that I was doing the same when the freeze ups happened. Only once out of 20 or so times did the freeze up happen while I was playing a game. All of the other freeze up were when the computer was under little stress or idling during the night.

One of the the first error I saw was a BCCode 124 so I looked it up online and they said it was most likely due to bad RAM. From this I downloaded Memtester86+ and ran 7 passes, it found 0 errors. After this I did a clean boot of Windows, reinstalled all drivers one by one and everything seemed to be fine. The next day I get another freeze up. I look online again and find that it might be caused due to my video card sound, motherboard sound, and my sound card sound. I then disabled my video card sound and motherboard sound only leaving my sound card and PnP input/output from my keyboard running. Everything seemed to be working fine. Sadly at about the 48hr mark of my computer being up and running, I got another BSOD. This is the BSOD that I am providing the information about on this post.

The information that I got when windows booted back up was:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800F3AD028
BCP3: 00000000BE000000
BCP4: 0000000000800400
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Also, I have attached the file that the SF Diagnostics Tool has gathered.

If there is any other information that I have left out or more information you need out of me please let me know. I will keep posting my BSOD's info when I get them.

Thanks again,
DeathPhage

koolkat77 · 16 Oct 2012

Welcome

Go through this thread for best reference:

Stop 0x124 - what it means and what to try

But your dump does indicate a problem with your Nvidia card/drivers.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800f3ad028, be000000, 800400}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware

Followup: MachineOwner
---------

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f40b000 fffff880`100ff000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Oct 03 00:21:13 2012 (506B3099)
    CheckSum:         00CD4613
    ImageSize:        00CF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
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: fffffa800f3ad028, 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:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff800`04818a98 fffff800`03012a3b : 00000000`00000124 00000000`00000000 fffffa80`0f3ad028 00000000`be000000 : nt!KeBugCheckEx
fffff800`04818aa0 fffff800`031d5b13 : 00000000`00000001 fffffa80`0cf55a60 00000000`00000000 fffffa80`0cf55ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`04818ae0 fffff800`03012700 : 00000000`00000728 fffffa80`0cf55a60 fffff800`04818e70 fffff800`04818e00 : nt!WheaReportHwError+0x263
fffff800`04818b40 fffff800`03012052 : fffffa80`0cf55a60 fffff800`04818e70 fffffa80`0cf55a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`04818c90 fffff800`03011f0d : 00000000`00000004 00000000`00000001 fffff800`04818ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`04818cd0 fffff800`03005e88 : fffffa80`0f33c000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`04818d00 fffff800`030c68ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`04818d30 fffff800`030c6713 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`04818e70 fffff880`0f5a903e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`0480c6f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x19e03e


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

Try using your onboard VGA if your motherboard has one. It's either a bad card, or an under powered PSU.

DeathPhage · 16 Oct 2012

Okay, my graphic card say it requires 450W and I have a 600W PSU, I would assume that should be enough. My card did come standard over clocked from the factory could that be causing an issue? Also, would it be more likely a bad driver or a bad card? I have disabled my graphics card driver for now so we'll see where that gets me.

Thanks for the quick response!

koolkat77 · 16 Oct 2012

DeathPhage said:

My card did come standard over clocked from the factory could that be causing an issue? Also, would it be more likely a bad driver or a bad card?

Could be related. Were all the parts compatible with each other during time of purchase? You can call the vendor and ask them if there's a way to clock it back to its default or check on the manual. Do you have a friend or neighbor who can lend you their video card for a while (obviously should be compatible with your mobo) :)

DeathPhage · 16 Oct 2012

koolkat77 said:

DeathPhage said:

My card did come standard over clocked from the factory could that be causing an issue? Also, would it be more likely a bad driver or a bad card?

Could be related. Were all the parts compatible with each other during time of purchase? You can call the vendor and ask them if there's a way to clock it back to its default or check on the manual. Do you have a friend or neighbor who can lend you their video card for a while (obviously should be compatible with your mobo) :)

Yes, I made sure all of the parts were compatible with each other during purchase. I'll try clocking it back to the default settings. Unfortunately, all of my friends are using their video cards

koolkat77 · 17 Oct 2012

Aww okay. No need to be sad.

If you follow the 124 guide, it says that there should be no overclocking on any hardware parts. So check the settings for the other pc components as well.

You may also take the Furmark test (after reverting to original clocks):
Video Card - Stress Test with Furmark

Video Card - Stress Test with Furmark

Monitor your temps with Speccy during these tests

Speccy - System Information - Free Download

:)

DeathPhage · 17 Oct 2012

I ran the FurMark Stress test for 5 minutes. From 2-5mins the card ran at a cool 63 C. There were also no artifacts that appeared.

koolkat77 · 17 Oct 2012

Okay, does it crash in all type of games? And are your games settings set to max? Try lowering those and see if it crashes. Were you able to reset the overclock?

DeathPhage · 17 Oct 2012

It actually has only crashed playing a game once out of the 20 or so times that it has happened. It usually crashes while it's idling during the night or under low load during the day. I have not yet unclocked my card since I did not have enough time last night. I will work on that today.

koolkat77 · 17 Oct 2012

Okay, take your time. Will wait for an update