What else? haha!

So I've been having this BSOD issue haha! It only really happens while running graphically intensive processes -- games, generally.

I'm running Win 7 Ultimate Full Retail
I've an NVIDIA GTX 460
Mobo is an MSI with an AMD quad core haha!
My PSU is an ULTRA LS 600
My RAM is all p. generic cheap stuff
My OS install is just a couple months old. I've reinstalled multiple times before, to no avail haha.

I've noticed just how attentive some of you are to these forums. I'm honestly p. impressed. Thanks in advance haha!

KONG said:

So I've been having this BSOD issue haha! It only really happens while running graphically intensive processes -- games, generally.

I'm running Win 7 Ultimate Full Retail
I've an NVIDIA GTX 460
Mobo is an MSI with an AMD quad core haha!
My PSU is an ULTRA LS 600
My RAM is all p. generic cheap stuff
My OS install is just a couple months old. I've reinstalled multiple times before, to no avail haha.

I've noticed just how attentive some of you are to these forums. I'm honestly p. impressed. Thanks in advance haha!

These are virtually identical and caused by hardware

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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 0x124 - what it means and what to try

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\041911-16270-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03050e50
Debug session time: Tue Apr 19 23:05:05.022 2011 (GMT-4)
System Uptime: 0 days 0:00:07.082
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800558b8f8, 0, 0}

Probably caused by : hardware

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: fffffa800558b8f8, 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_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02fc46f0 fffff800`030cda99 : fffffa80`0558b8d0 fffffa80`04627040 fffff8a0`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc4c10 fffff800`02faf677 : fffffa80`0558b8d0 fffff800`030285f8 fffffa80`04627040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc4c40 fffff800`02f17c45 : fffff800`0308a360 fffffa80`05aa6a38 fffffa80`05aa6a30 fffffa80`04627040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc4c80 fffff800`02e90961 : fffff880`00c30e00 fffff800`02f17c20 fffffa80`04627040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc4cb0 fffff800`031267c6 : 00000000`00000000 fffffa80`04627040 00000000`00000080 fffffa80`04615b30 : nt!ExpWorkerThread+0x111
fffff880`02fc4d40 fffff800`02e61c26 : fffff880`02d64180 fffffa80`04627040 fffff880`02d6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc4d80 00000000`00000000 : fffff880`02fc5000 fffff880`02fbf000 fffff880`02fc31d0 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_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

I really hope it's my PSU haha. That thing's still under warranty haha!

Dave76 thank you haha

Hello all

I haven't had time to run any diagnostics on my computer yet. However, I forgot to give you one potentially important piece of information.

A short time ago, my computer was intermittently failing to boot upon startup. The computer would simply hang at a black screen, with the drive and fans spinning as usual. I noticed that the built-in overclocking switches on the MOBO were set to on. Turning off the overclocking decreased the frequency of these failed boots, but didn't eliminate them, with every 10th or 11th startup (on average) now being a failed boot. I'm not sure if this plays into the bluescreens I am experiencing with Windows 7 or not.

I appreciate the help and will run your suggested diagnostics when I get the time.

Dave76 said:

Thanks for the update, let us know how the tests go.

Alright, I've done the RAM test and found some errors. I'm wondering now if I should just try to find the faulty RAM, or continue on with the other tests?