BSOD occasionally after closing fullscreen game and after restart

lobstrain · 18 Apr 2014

Hello,

I have been having this issue for a while and just haven't been able to detect what the problem could possibly be. I built this computer about 8 months ago, and have had a problem where my computer will just randomly BSOD. This tends to happen about once a day a few seconds after closing a fullscreen game, but it's completely inconsistent. And then after that happens, I'm forced to power down the machine. I'll boot it back up, and sometimes it will BSOD again after logging in. This could happen after a few more restarts, or this might not happen at all. Again, completely inconsistent, and I've decided to finally try and diagnose the problem. I would really appreciate your help in solving this. I've attached the collected information. Thank you!

koolkat77 · 18 Apr 2014

Your error is a hardware one.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\IPSUM-Fri_04_18_2014_222054_21\041614-12823-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`01c67000 PsLoadedModuleList = 0xfffff800`01eaa6d0
Debug session time: Wed Apr 16 09:34:27.545 2014 (UTC + 6:00)
System Uptime: 1 days 6:02:08.544
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e8a6028, fe000000, 800400}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : GenuineIntel

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

2: 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: fffffa800e8a6028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fe000000, 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:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`01e66a58 fffff800`01c30a3b : 00000000`00000124 00000000`00000000 fffffa80`0e8a6028 00000000`fe000000 : nt!KeBugCheckEx
fffff880`01e66a60 fffff800`01df3463 : 00000000`00000001 fffffa80`0d2e5270 00000000`00000000 fffffa80`0d2e52c0 : hal!HalBugCheckSystem+0x1e3
fffff880`01e66aa0 fffff800`01c30700 : 00000000`00000728 fffffa80`0d2e5270 fffff880`01e66e30 fffff880`01e66e00 : nt!WheaReportHwError+0x263
fffff880`01e66b00 fffff800`01c30052 : fffffa80`0d2e5270 fffff880`01e66e30 fffffa80`0d2e5270 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`01e66c50 fffff800`01c2ff0d : 00000000`00000004 00000000`00000001 fffff880`01e66eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`01e66c90 fffff800`01c23e88 : fffffa80`0e5242d0 fffff900`c4f8db34 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`01e66cc0 fffff800`01cdb4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`01e66cf0 fffff800`01cdb313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`01e66e30 fffff880`031b4260 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0bee44c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x523260


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_VRF_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_VRF_PROCESSOR_MAE

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

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try