Solved Can't resolve this BSOD, need some help.

[sspelak]

Well, I built a computer specifically to run FSX well in March. Just recently, it's started to chuck out random BSODs with random BCCodes, but generally the same file was the main problem, ntoskrnl.exe.

The only changes I've made to the system recently before it started happening is upgrading my NVIDIA drivers, and installing PMDG's 737NGX. I reinstalled the NVIDIA drivers just in case, but no luck.

Thought it could be a virus, but AVG says no. Then I did a little Googling and it said that the antivirus could be a problem, so that's been uninstalled as well. Frankly I'm at a loss, and any help would be greatly appreciated.

My system details:
-Retail Windows 7 Ultimate x64
-Hardware is only about 6 months old

 

[Maguscreed]

Wasn't really getting anywhere with this on the first 4 or so minidumps, they were identical and rather vague.
Then I found the one coded here.
This error commonly points to a actual hardware issue it's pretty rare for it to be caused by anything else, with the exception of a overclock that has become unstable. ...and this sometimes happens over time that a overclock will lose stability either because of wear on components or changes in the system.

Nothing here looks viral to me, ...even the aforementioned vague minidumps don't seem viral in nature.

Not too mention this one specific bugcheck doesn't get generated by a whole lot of things.

Probably caused by : hardware

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

1: 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: fffffa8007ee08f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  0

STACK_TEXT:  
fffff880`035776f0 fffff800`034d8c59 : fffffa80`07ee08d0 fffffa80`06d49680 fffffa80`00000004 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03577c10 fffff800`033b8f57 : fffffa80`07ee08d0 fffff800`034332b8 fffffa80`06d49680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03577c40 fffff800`033205d5 : fffff800`03494ae0 00000000`00000001 fffffa80`07e71820 fffffa80`06d49680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03577c80 fffff800`0329d001 : fffff880`01030e00 fffff800`033205b0 fffffa80`06d49600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03577cb0 fffff800`0352dfee : 00000000`00000000 fffffa80`06d49680 00000000`00000080 fffffa80`06d2d990 : nt!ExpWorkerThread+0x111
fffff880`03577d40 fffff800`032845e6 : fffff880`0336a180 fffffa80`06d49680 fffff880`033750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03577d80 00000000`00000000 : fffff880`03578000 fffff880`03572000 fffff880`030dc540 00000000`00000000 : nt!KxStartSystemThread+0x16


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_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

 

[sspelak]

I guess that would make sense. I have overclocked the CPU, but I didn't think I was pushing it so hard that it would become unstable this quickly. I just tried it at normal clock speeds and it's running fine too. *grrr*

Thanks for the quick replies though, guess I just need to cut back on the FSX settings.

 

[Maguscreed]

Overclocking is a really tricky thing, I've seen overclocks hold stable in prime 95 for days on end, then crash the first time a game is started. You really never know. If you go to the hardware section and post your specific system specs and ask for help with overclocking, there's some guys here with a lot of experience in that area.
I personally quit overclocking years ago I just never found the increases to be worth the extra wear on the hardware.

 

[sspelak]

Barring the hardware degradation, it's almost mandatory to run FSX with any decent amount of FPS.

But running the stock clocks seems to have fixed it thankfully. Shame though, my excuse to get a Sandy Bridge model hasn't yet come to fruition lol. Thanks again!