BOSD bugcheck code 124

[arendsoogg]

Hi guys,

 

The last few months I got bluescreens with a bugcheck code 124. That means one of my components doesn't work correctly or is broken. I mostly get these bluescreens when gaming.

 

· OS - Windows 7
· x86 (32-bit) or x64 - x64 
· What OS was originaly installed on the system - Windows 7
· Age of system (hardware) - My system is not older than one year
· Age of OS installation - have you re-installed the OS? - Yes, in hoped it would fix this problem. It didn't.
· CPU model - Intel I5 4690K
· Video Card model - Sapphire R9 280
· MotherBoard - (if NOT a laptop) - MSI Z97S SLI Krait Edition
· Power Supply - brand & wattage (if laptop, skip this) - Cooler Master G650M, 650 watt power supply
· System Manufacturer - I built my system myself.
· RAM - 8GB (2x4) Crucial BallistiX Sport
· Laptop or Desktop? - Desktop

I did NOT overclock my system.

 

SysnativeFileCollectionApp.zip can be downloaded here.

System diagnistic.thml file is included.

My OS is in dutch so there is a chance you won't understand everything.

 

This is the info from the most recent minidump file. All the minidump files can be downloaded here.

Dump File         : 082315-62431-01.dmp

Crash Time        : 23-8-2015 17:35:05

Bug Check String  : 

Bug Check Code    : 0x00000124

Parameter 1       : 00000000`00000000

Parameter 2       : fffffa80`08656038

Parameter 3       : 00000000`00000000

Parameter 4       : 00000000`00000000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+4b18cc

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7601.17592 (win7sp1_gdr.110408-1631)

Processor         : x64

Crash Address     : ntoskrnl.exe+4b18cc

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\082315-62431-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 262.144

Dump File Time    : 23-8-2015 17:35:21

 

This is some information I got when booting my pc after a crash:

BCCode: 124

  BCP1: 0000000000000000

  BCP2: FFFFFA8008656038

  BCP3: 0000000000000000

  BCP4: 0000000000000000

  OS Version: 6_1_7601

  Service Pack: 1_0

  Product: 256_1

 

I hope someone can tell me what this all means.

Thanks for your time,

Jeroen

[manikyath]

a hardware related error can also mean an error in windows, causing it to think the hardware is faulty (had this happen myself quite a bunch of times)

 

you can check windows for errors by opening CMD as administrator and typing the following:

sfc /scannow

[arendsoogg]

 

a hardware related error can also mean an error in windows, causing it to think the hardware is faulty (had this happen myself quite a bunch of times)

 

you can check windows for errors by opening CMD as administrator and typing the following:

sfc /scannow

No problems found when executing sfc /scannow

[manikyath]

No problems found when executing sfc /scannow

then its not a windows issue.

 

you could try the usual reseating CPU, RAM, and GPU.

[ionbasa]

Hi guys,

 

The last few months I got bluescreens with a bugcheck code 124. That means one of my components doesn't work correctly or is broken. I mostly get these bluescreens when gaming.

 

· OS - Windows 7

· x86 (32-bit) or x64 - x64 

· What OS was originaly installed on the system - Windows 7

· Age of system (hardware) - My system is not older than one year

· Age of OS installation - have you re-installed the OS? - Yes, in hoped it would fix this problem. It didn't.

· CPU model - Intel I5 4690K

· Video Card model - Sapphire R9 280

· MotherBoard - (if NOT a laptop) - MSI Z97S SLI Krait Edition

· Power Supply - brand & wattage (if laptop, skip this) - Cooler Master G650M, 650 watt power supply

· System Manufacturer - I built my system myself.

· RAM - 8GB (2x4) Crucial BallistiX Sport

· Laptop or Desktop? - Desktop

I did NOT overclock my system.

 

This is the info from the most recent minidump file. All the minidump files can be downloaded here.

Dump File         : 082315-62431-01.dmp

Crash Time        : 23-8-2015 17:35:05

Bug Check String  : 

Bug Check Code    : 0x00000124

Parameter 1       : 00000000`00000000

Parameter 2       : fffffa80`08656038

Parameter 3       : 00000000`00000000

Parameter 4       : 00000000`00000000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+4b18cc

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7601.17592 (win7sp1_gdr.110408-1631)

Processor         : x64

Crash Address     : ntoskrnl.exe+4b18cc

Stack Address 1   : 

Stack Address 2   : 

Stack Address 3   : 

Computer Name     : 

Full Path         : C:\Windows\Minidump\082315-62431-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 262.144

Dump File Time    : 23-8-2015 17:35:21

 

This is some information I got when booting my pc after a crash:

BCCode: 124

  BCP1: 0000000000000000

  BCP2: FFFFFA8008656038

  BCP3: 0000000000000000

  BCP4: 0000000000000000

  OS Version: 6_1_7601

  Service Pack: 1_0

  Product: 256_1

 

I hope someone can tell me what this all means.

Thanks for your time,

Jeroen

Please do us a foavor and follow the BSOD posting instructions pinned in the top of this subforum: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

 

You didn't include any dump files so we have no way of analyzing the stack information or looking at which drivers are loaded at the time of the crash or which executable started the crash.

 

Once we get the dump files we'll be able to accurately gauge your BSOD issue.

[arendsoogg]

Please do us a foavor and follow the BSOD posting instructions pinned in the top of this subforum: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

 

You didn't include any dump files so we have no way of analyzing the stack information or looking at which drivers are loaded at the time of the crash or which executable started the crash.

 

Once we get the dump files we'll be able to accurately gauge your BSOD issue.

Added a download link to the requested files under my system information.

[ionbasa]

Added a download link to the requested files under my system information.

Took a look at the WinDBG output.

 

For Reference:

 

The bug check string in both BSODs were "0x124_GenuineIntel". You either have an unstable overclock or a faulty processor. You said you don't run an overclock? Is your RAM running in under the XMP profile?

 

While you're at it, what is your load line calibration/Vdroop settings set to in the BIOS? Your board might not be compensating enough for vdroop on your chip.

 

Also, mind running an stress test with AIDA64? What temps are you seeing on that chip?

Windows 7 Kernel Version 7600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e49e50Debug session time: Tue Aug 11 08:00:30.754 2015 (UTC - 4:00)System Uptime: 0 days 0:00:08.002********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: fffffa8007c2e038, 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:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  fffff880`031ee6b0 fffff800`02ec6a89 : fffffa80`07c2e010 fffffa80`0671fb60 00000000`00000010 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6cfffff880`031eebd0 fffff800`02da8547 : fffffa80`07c2e010 fffff800`02e215f8 fffffa80`0671fb60 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49fffff880`031eec00 fffff800`02d10b95 : fffff800`02e83360 fffffa80`07735ae8 fffffa80`07735ae0 fffffa80`0671fb60 : nt!WheapProcessWorkQueueItem+0x57fffff880`031eec40 fffff800`02c8b161 : fffff880`01129e00 fffff800`02d10b70 fffffa80`0671fb60 c148310f`c1af0f4c : nt!WheapWorkQueueWorkerRoutine+0x25fffff880`031eec70 fffff800`02f21166 : 8d480000`02588689 fffffa80`0671fb60 00000000`00000080 fffffa80`0670a400 : nt!ExpWorkerThread+0x111fffff880`031eed00 fffff800`02c5c486 : fffff880`02f71180 fffffa80`0671fb60 fffff880`02f7bfc0 058d48f9`8b4820ec : nt!PspSystemThreadStartup+0x5afffff880`031eed40 00000000`00000000 : fffff880`031ef000 fffff880`031e9000 fffff880`041a7500 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVFollowup: MachineOwner 

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631Machine Name:Kernel base = 0xfffff800`03208000 PsLoadedModuleList = 0xfffff800`0344d650Debug session time: Sun Aug 23 11:35:05.735 2015 (UTC - 4:00)System Uptime: 0 days 0:00:10.531********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: fffffa8008656038, 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:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  fffff880`031d25b0 fffff800`034cac59 : fffffa80`08656010 fffffa80`0670a680 00000000`0000001f 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6cfffff880`031d2ad0 fffff800`033aafa7 : fffffa80`08656010 fffff800`034252b8 fffffa80`0670a680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49fffff880`031d2b00 fffff800`033125c5 : fffff800`03486ac0 00000000`00000001 fffffa80`0773ac60 fffffa80`0670a680 : nt!WheapProcessWorkQueueItem+0x57fffff880`031d2b40 fffff800`03292021 : fffff880`01030e00 fffff800`033125a0 fffffa80`0670a600 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25fffff880`031d2b70 fffff800`0352432e : 00000000`00000000 fffffa80`0670a680 00000000`00000080 fffffa80`066ceb30 : nt!ExpWorkerThread+0x111fffff880`031d2c00 fffff800`03279666 : fffff880`02f72180 fffffa80`0670a680 fffff880`02f7cfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5afffff880`031d2c40 00000000`00000000 : fffff880`031d3000 fffff880`031cd000 fffff880`041b44a0 00000000`00000000 : nt!KxStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVFollowup: MachineOwner 

[arendsoogg]

Took a look at the WinDBG output.

 

For Reference:

 

The bug check string in both BSODs were "0x124_GenuineIntel". You either have an unstable overclock or a faulty processor. You said you don't run an overclock? Is your RAM running in under the XMP profile?

 

While you're at it, what is your load line calibration/Vdroop settings set to in the BIOS? Your board might not be compensating enough for vdroop on your chip.

 

Also, mind running an stress test with AIDA64? What temps are you seeing on that chip?

I checked my bios and as far as I can tell XMP is not enabled and Vdroop is set to auto (just like all the other overclock settings).

I ran a stress test for a little time and didn't get higher temperatures than 60 degrees under a 100% load.

 

I also discovered that I sometimes hear a buzz that gets louder and randomly turns down again, it's really annoying. Although I don't know if this is connected to the crashes.

Windows 7 Kernel Version 7600 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e49e50Debug session time: Tue Aug 11 08:00:30.754 2015 (UTC - 4:00)System Uptime: 0 days 0:00:08.002********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: fffffa8007c2e038, 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:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  fffff880`031ee6b0 fffff800`02ec6a89 : fffffa80`07c2e010 fffffa80`0671fb60 00000000`00000010 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6cfffff880`031eebd0 fffff800`02da8547 : fffffa80`07c2e010 fffff800`02e215f8 fffffa80`0671fb60 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49fffff880`031eec00 fffff800`02d10b95 : fffff800`02e83360 fffffa80`07735ae8 fffffa80`07735ae0 fffffa80`0671fb60 : nt!WheapProcessWorkQueueItem+0x57fffff880`031eec40 fffff800`02c8b161 : fffff880`01129e00 fffff800`02d10b70 fffffa80`0671fb60 c148310f`c1af0f4c : nt!WheapWorkQueueWorkerRoutine+0x25fffff880`031eec70 fffff800`02f21166 : 8d480000`02588689 fffffa80`0671fb60 00000000`00000080 fffffa80`0670a400 : nt!ExpWorkerThread+0x111fffff880`031eed00 fffff800`02c5c486 : fffff880`02f71180 fffffa80`0671fb60 fffff880`02f7bfc0 058d48f9`8b4820ec : nt!PspSystemThreadStartup+0x5afffff880`031eed40 00000000`00000000 : fffff880`031ef000 fffff880`031e9000 fffff880`041a7500 00000000`00000000 : nt!KiStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVFollowup: MachineOwner 

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631Machine Name:Kernel base = 0xfffff800`03208000 PsLoadedModuleList = 0xfffff800`0344d650Debug session time: Sun Aug 23 11:35:05.735 2015 (UTC - 4:00)System Uptime: 0 days 0:00:10.531********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: fffffa8008656038, 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:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2BUGCHECK_STR:  0x124_GenuineIntelCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  0STACK_TEXT:  fffff880`031d25b0 fffff800`034cac59 : fffffa80`08656010 fffffa80`0670a680 00000000`0000001f 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6cfffff880`031d2ad0 fffff800`033aafa7 : fffffa80`08656010 fffff800`034252b8 fffffa80`0670a680 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49fffff880`031d2b00 fffff800`033125c5 : fffff800`03486ac0 00000000`00000001 fffffa80`0773ac60 fffffa80`0670a680 : nt!WheapProcessWorkQueueItem+0x57fffff880`031d2b40 fffff800`03292021 : fffff880`01030e00 fffff800`033125a0 fffffa80`0670a600 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25fffff880`031d2b70 fffff800`0352432e : 00000000`00000000 fffffa80`0670a680 00000000`00000080 fffffa80`066ceb30 : nt!ExpWorkerThread+0x111fffff880`031d2c00 fffff800`03279666 : fffff880`02f72180 fffffa80`0670a680 fffff880`02f7cfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5afffff880`031d2c40 00000000`00000000 : fffff880`031d3000 fffff880`031cd000 fffff880`041b44a0 00000000`00000000 : nt!KxStartSystemThread+0x16STACK_COMMAND:  kbFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: GenuineIntelIMAGE_NAME:  GenuineIntelDEBUG_FLR_IMAGE_TIMESTAMP:  0FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVBUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRVFollowup: MachineOwner 

[ionbasa]

I checked my bios and as far as I can tell XMP is not enabled and Vdroop is set to auto (just like all the other overclock settings).

I ran a stress test for a little time and didn't get higher temperatures than 60 degrees under a 100% load.

 

I also discovered that I sometimes hear a buzz that gets louder and randomly turns down again, it's really annoying. Although I don't know if this is connected to the crashes.

Can you check if the buzz is coming from the PSU? If so, the PSU may be faulty. Having too much Vdroop will cause the CPU error out. Maybe try setting a more aggressive Vdroop setting other than auto.

[arendsoogg]

Can you check if the buzz is coming from the PSU? If so, the PSU may be faulty. Having too much Vdroop will cause the CPU error out. Maybe try setting a more aggressive Vdroop setting other than auto.

It is not coming from the PSU, I forgot to mention that I hear it trough my headphones. I will try a more agressive Vdroop setting as soon as possible.

[ionbasa]

It is not coming from the PSU, I forgot to mention that I hear it trough my headphones. I will try a more agressive Vdroop setting as soon as possible.

ALthough not common, if the buzzing noise isn't coming from the  PSU or GPU as coil while. It could actually be coming from the motherboard power delivery Mosfets and chokes.

 

If you can hear buzzing coming through your headphones, then that is a good indication that there may be something wrong with the motherboards power delivery.

[Skander1345]

ALthough not common, if the buzzing noise isn't coming from the  PSU or GPU as coil while. It could actually be coming from the motherboard power delivery Mosfets and chokes.

 

If you can hear buzzing coming through your headphones, then that is a good indication that there may be something wrong with the motherboards power delivery.

The motherboard he's using does not have any kind of shielding on the internal sound area. Might be the cause of the interference there.

DISABLE any overclock of any kind, auto or anything.

Set the CPU to the default settings and set a 1.3v manual voltage setting, use this just for testing to completely make sure if it's the CPU or not. OC Genie might be setting a bad oc.

[arendsoogg]

The motherboard he's using does not have any kind of shielding on the internal sound area. Might be the cause of the interference there.

DISABLE any overclock of any kind, auto or anything.

Set the CPU to the default settings and set a 1.3v manual voltage setting, use this just for testing to completely make sure if it's the CPU or not. OC Genie might be setting a bad oc.

The interference appeared recently so it's not an issue of not having any kind of shielding.

I will try testing with the suggested settings.

 

 

 

Can you check if the buzz is coming from the PSU? If so, the PSU may be faulty. Having too much Vdroop will cause the CPU error out. Maybe try setting a more aggressive Vdroop setting other than auto.

Set the Vdroop to 25%, no issues so far.

[arendsoogg]

So today I was playing GTA V, while skyping with friends and having spotify in the background and suddenly my monitor got no signal and my gpu's fans started spinning at 100%. I could still use skype and hear the song that was playing on spotify. Windows did not react on using the sleep button from my keyboard so I had to shut my pc down by pressing the reset button.

 

I have no idea if this is connected to the bluescreens because I didn't get a bluescreen, but it definitely is very strange..

[ionbasa]

So today I was playing GTA V, while skyping with friends and having spotify in the background and suddenly my monitor got no signal and my gpu's fans started spinning at 100%. I could still use skype and hear the song that was playing on spotify. Windows did not react on using the sleep button from my keyboard so I had to shut my pc down by pressing the reset button.

 

I have no idea if this is connected to the bluescreens because I didn't get a bluescreen, but it definitely is very strange..

What you are describing is actually a GPU driver crash. What GPU driver version do you currently have installed?

 

Also, I'd recommend a Windows' Repair Install to rule out any issues with a corrupt Windows' install. Follow the guide here: http://www.sevenforums.com/tutorials/3413-repair-install.html

You'll keep all documents and programs, but settings will be reset and system files will be replaced. You'll keep your activation.

[arendsoogg]

I am almost 100% sure my GPU is the problem.

So today I was playing black ops III beta and my pc crashed, no minidump was created.

After a reboot I decided to play some GTA V but after less than 15 minutes my screen went black, I could still hear sounds for about 2 seconds and after that my screen displayed some weird grey lines (artifacts?).

After that I decided to run a stress test on my GPU with AIDA64. It ran less than 5 minutes and my pc crashed again! (GPU didn't even hit 70 degrees which it can hit while playing demanding games)

 

A month ago I tested if my pc would crash if I used integrated graphics instead of the GPU. In that gaming session my pc did not crash.

 

Is this enough evidence to confidently say that my GPU is faulty and needs to be returned/replaced?

[arendsoogg]

I am almost 100% sure my GPU is the problem.

So today I was playing black ops III beta and my pc crashed, no minidump was created.

After a reboot I decided to play some GTA V but after less than 15 minutes my screen went black, I could still hear sounds for about 2 seconds and after that my screen displayed some weird grey lines (artifacts?).

After that I decided to run a stress test on my GPU with AIDA64. It ran less than 5 minutes and my pc crashed again! (GPU didn't even hit 70 degrees which it can hit while playing demanding games)

 

A month ago I tested if my pc would crash if I used integrated graphics instead of the GPU. In that gaming session my pc did not crash.

 

Is this enough evidence to confidently say that my GPU is faulty and needs to be returned/replaced?

So after I posted the message above I wanted to play some battlefield 3. And after less than 5 minutes of playing, you can guess it by now, my pc crashed again! No minidump was created this time either. My monitor also displayed an artifact for a longer time. Picture I took of the artifact: https://pbs.twimg.com/media/CNhbK9rUYAAdVoE.jpg:large

[ionbasa]

I am almost 100% sure my GPU is the problem.

So today I was playing black ops III beta and my pc crashed, no minidump was created.

After a reboot I decided to play some GTA V but after less than 15 minutes my screen went black, I could still hear sounds for about 2 seconds and after that my screen displayed some weird grey lines (artifacts?).

After that I decided to run a stress test on my GPU with AIDA64. It ran less than 5 minutes and my pc crashed again! (GPU didn't even hit 70 degrees which it can hit while playing demanding games)

 

A month ago I tested if my pc would crash if I used integrated graphics instead of the GPU. In that gaming session my pc did not crash.

 

Is this enough evidence to confidently say that my GPU is faulty and needs to be returned/replaced?

 

So after I posted the message above I wanted to play some battlefield 3. And after less than 5 minutes of playing, you can guess it by now, my pc crashed again! No minidump was created this time either. My monitor also displayed an artifact for a longer time. Picture I took of the artifact: https://pbs.twimg.com/media/CNhbK9rUYAAdVoE.jpg:large

Yup. That artifacting confirms an bad GPU. RMA the card.

[arendsoogg]

Yup. That artifacting confirms an bad GPU. RMA the card.

By the way, is it possible that a broken GPU interferes with my onboard audio?

[Redicat]

By the way, is it possible that a broken GPU interferes with my onboard audio?

 

Intresting when my PC doesnt display it gives my bose setup alot of sound soo i'd think so 

[Centurius]

I am almost 100% sure my GPU is the problem.

So today I was playing black ops III beta and my pc crashed, no minidump was created.

After a reboot I decided to play some GTA V but after less than 15 minutes my screen went black, I could still hear sounds for about 2 seconds and after that my screen displayed some weird grey lines (artifacts?).

After that I decided to run a stress test on my GPU with AIDA64. It ran less than 5 minutes and my pc crashed again! (GPU didn't even hit 70 degrees which it can hit while playing demanding games)

 

A month ago I tested if my pc would crash if I used integrated graphics instead of the GPU. In that gaming session my pc did not crash.

 

Is this enough evidence to confidently say that my GPU is faulty and needs to be returned/replaced?

 

No, from my own experience I can say, that the symptoms of PSU failure are easily confused with GPU failure. Try a different PSU first.

[ionbasa]

No, from my own experience I can say, that the symptoms of PSU failure are easily confused with GPU failure. Try a different PSU first.

The OP can easily test against the PSU being an issue if he has a spare GPU to try/borrow. If the spare works fine, then it would be his original GPU that needs to be RMA'd. If the replacement GPU also artifacts, then yes it is likely the PSU.

[arendsoogg]

I RMA'd the 280 and after a really slow RMA I got a MSI R9 380 Gaming 4G. Pc runs fine now

 

So in the end the GPU was the problem.