![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
I have the strangest problem with my system (in sig). On cold boots and when it awakes from hibernation, I'm getting lock ups in Source engine games. It starts out with keyboard input lag (mouse isn't affected), then the sound starts to hiccup, then I get a hard-lock. This last time, I didn't get a BSOD, it just locked. But, when I restarted windows, it said that there was a BlueScreen event. Anyways, I grabbed WinDbg to analyze the minidump, and I get the following after executing "!analyze -v" in the debugger:
EDIT: Here's what comes up initially, before I execute the command:
Any ideas as to what could be causing this problem? As I stated before, it ONLY occurs during cold boots and after hibernation.
On a side note: I also ran BlueScreenView which stated that the problem was caused by the NTOS Kernel. So, that didn't really give me much to go on.
Thanks in advance!
EDIT: Here's what comes up initially, before I execute the command:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa80065e68f8, 0, 0}
Probably caused by : hardware
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* 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: fffffa80065e68f8, 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`0357e6f0 fffff800`02cd4a89 : fffffa80`065e68d0 fffffa80`05526680 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0357ec10 fffff800`02bb6547 : fffffa80`065e68d0 fffff800`02c2f5f8 fffffa80`05526680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0357ec40 fffff800`02b1eb95 : fffff800`02c91360 fffff880`0149ba18 00000000`00000000 fffffa80`05526680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0357ec80 fffff800`02a99161 : fffff880`0145a800 fffff800`02b1eb70 fffffa80`05526680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0357ecb0 fffff800`02d2f166 : 3fbb3fbb`4e9e4e9e fffffa80`05526680 00000000`00000080 fffffa80`055089e0 : nt!ExpWorkerThread+0x111
fffff880`0357ed40 fffff800`02a6a486 : fffff880`0336a180 fffffa80`05526680 fffff880`033750c0 b7e2b7e2`65476547 : nt!PspSystemThreadStartup+0x5a
fffff880`0357ed80 00000000`00000000 : fffff880`0357f000 fffff880`03579000 fffff880`0300d590 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
---------Any ideas as to what could be causing this problem? As I stated before, it ONLY occurs during cold boots and after hibernation.
On a side note: I also ran BlueScreenView which stated that the problem was caused by the NTOS Kernel. So, that didn't really give me much to go on.
Thanks in advance!