BSOD's On New Gaming PC - Windows 7 x64

Prevention · Nov 21, 2014

Hi folks,

Was wondering if I could get your input on the BSOD's I've been experiencing over the last 7 days. I thought I'd treat myself and by a new gaming machine. I ordered it on Monday of last week and by the Friday it had arrived. After plugging it all in on the Friday, I experience 3 BSOD's that day. The first was seemingly whilst the machine was idling, I had left the room and come back to find the "Windows has recovered from an unexpected reboot Message". The next I experience was whilst playing "Lords of the fallen". I think I had been in game for about 15 minutes when it blue screened again. The third of that day happened whilst watching a YouTube video. Since then I have experienced more BSOD's either whilst watching YouTube or the machine being idle (although the web browser was open, not playing any videos).

Here is the information asked for in the posting instructions:

OS: Windows 7 (SP1) Home Premium Edition
Architecture: 64Bit
Original OS: Only this one as far as I know - it's a custom built machine from a company.
OEM: The machine came with a fully licensed retail copy of windows 7 (I have the official windows 7 install disc and CDkey)
Age of System: I have owned the PC for 7 days (Friday 17th November). I ordered it on Monday the 10th of November and it was built between those two dates.
Age of OS Installation: Same as the machine age - I am yet to re-install windows.

CPU: Intel Core i7 5820K
Video Card: Zotac Nvidia Geforce GTX 980
Motherboard: Gigabyte X99-Gaming 5
Power Supply: Corsair CX600

As well as the two zipped files that you've asked for, I've also included a screenshot of every installed program on the system, as after reading up a little bit I understand that some programs can cause "phantom" 124 errors. If you see any in this list please let me know and I will remove them.

If you need any more information, please ask.

Thanks in advance. I'll try the driver verifier and the HDD/RAM diagnostics in the meantime.

x BlueRobot · Nov 21, 2014

Code:

BugCheck 124, {0, fffffa800e78e028, bf800000, 200401}

Probably caused by : GenuineIntel

The first parameter indicates that the error was found by the processor using the MCE (Machine Check Error) mechanism, it doesn't mean the error was caused by the processor. The error sources are stored within a structure called WHEA_ERROR_SOURCE_TYPE. The second parameter is the address of the WHEA error record, this is the important structure for this bugcheck.

Code:

6: kd> !errrec fffffa800e78e028
===============================================================================
Common Platform Error Record @ fffffa800e78e028
-------------------------------------------------------------------------------
Record Id     : 01d0057e61b2d344
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 11/21/2014 12:10:50 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e78e0a8
Section       @ fffffa800e78e180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306f2
Processor ID  : 0x0000000000000006

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e78e0f0
Section       @ fffffa800e78e240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000006
CPU Id        : f2 06 03 00 00 08 10 06 - bf fb fe 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800e78e240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e78e138
Section       @ fffffa800e78e2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal unclassified (Proc 6 Bank 1)
  Status      : 0xbf80000000200401
  Address     : 0x00000000fee00040
  Misc.       : 0x0000000000000086

The error was a internal error, which was raised by Processor 6, Cache Bank 1. The Fatal flag indicates the hardware wasn't able to recover from the error. Some hardware errors are recoverable. These two error types fall under a larger category called Uncorrected errors.

The GeniuneIntel string is simply used to lets users know they're used a real Intel processor.

Code:

6: kd> dt nt!_KPRCB -y CpuVendor
   +0x63d CpuVendor : UChar

Since this is a new computer, have you ensured you have all the latest drivers, including chipset drivers? Is everything fully connected, and most importantly is the CPU connected properly?

Prevention · Nov 21, 2014

Thanks a lot for taking a look at this for me.

I've checked my chipset drivers and they seem to be the latest available (checking both windows update & the manufacturers page on the motherboard). I installed the latest GPU drivers this morning.

As for everything being fully connected, I will check that the RAM is firmly sat on the board in a while.

When checking the CPU is sat correctly in it's socket, is this something I can do without disturbing the thermal paste on the CPU? Because this was built in house by the people I bought it from I don't have any thermal paste of my own.

By the way, when I tried to turn on driver verifier earlier (I tried on two separate occasions about 4 hours apart) the machine would blue screen on the Windows boot screen. It would do this constantly, meaning I had to boot into safe mode and roll back to the restore point made just before.

I'll report back soon about the situation with the RAM as well as verification on the rest of the drivers being up to date. If you happen to know about the CPU/thermal paste that would be fantastic.

x BlueRobot · Nov 21, 2014

I wouldn't worry about it for now, and do you know if the dump files were saved for the BSODs at boot? They should be stored in:

Code:

C:\Windows\Minidump

Prevention · Nov 23, 2014

The driver verification BSOD's didn't result in any dumps, but I seem to have made some progress.

I spoke with a friend yesterday who has the same motherboard as me. He mentioned to me that the Gigabyte software that comes with it (all of the stuff listed in the image above) is known to cause BSOD's on Windows 7. Sure enough after removing it, the machine is *seemingly* more stable. I left a 3 hour YouTube video playing today whilst I was out and came back to the computer still perfectly fine. Normally any videos between 10 to 30 minutes would have caused a BSOD almost every time.

I don't want to jump the gun but I'm somewhat confident that I might have the problem licked.

If it occurs again I'll report back. Thank's for taking the time to look into it for me though, you guys are awesome!

Search

Search

BSOD's On New Gaming PC - Windows 7 x64

Prevention

New member

Attachments

x BlueRobot

Administrator

Prevention

New member

x BlueRobot

Administrator

Prevention

New member