Windows 10 BSOD only when playing CSGO ntoskrnl.exe

Jen0vaCore · Dec 28, 2016

Hey. I play a lot of video games, all day, and never got BSODs. However when I play CSGO, I get a stutter for a few seconds, then a blue screen saying whea_uncorrectable_error after playing for about 30-40 minutes. My CPU is overclocked. I went back to stock BIOS settings and standard CPU clocks and it still had a BSOD.

Like I said, it only happens when I play CSGO. Other games work perfectly fine and I can play them for long periods without this happening.

I don't have a windows bug checking tool, so I'm uploading my minidump to see if someone can figure out what the problem is exactly.

I really appreciate the help.

kemical · Dec 28, 2016

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff8b06c7de6028, bf800000, 124}

Probably caused by : GenuineIntel

Followup:     MachineOwner

Hi,
sorry i meant to post this earlier but got diverted by someone at the front door, (neighbour). Ok so just to add to Neem's excellent post, I checked over your...

Neemobeer · Dec 28, 2016

WHEA bug checks are fun.

0: kd> !errrec ffff8b06c7de6028
===============================================================================
Common Platform Error Record @ ffff8b06c7de6028
-------------------------------------------------------------------------------
Record Id : 01d25fdfc22dd5c4
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 12/28/2016 6:53:56 (UTC)
Flags : 0x00000000

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

Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Generic
Flags : 0x00
Level : 0
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id : c3 06 03 00 00 08 10 00 - bf fb fa 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 @ ffff8b06c7de6240

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

Error : DCACHEL0_WR_ERR (Proc 0 Bank 1)
Status : 0xbf80000000000124
Address : 0x00000002d892c180
Misc. : 0x0000000000000086

This is a write error to L0 Cache on the CPU.

Somethings you can try to fix.

Replace the CMOS battery
Reset BIOS to defaults
Update your BIOS to the latest version
If none of these fix the issue you may need to replace the CPU

The manufacturer of the computer, or the manufacturer of the motherboard if this is a custom rig will have BIOS updates available.

Jen0vaCore · Dec 28, 2016

Neemobeer said:
WHEA bug checks are fun.

0: kd> !errrec ffff8b06c7de6028
===============================================================================
Common Platform Error Record @ ffff8b06c7de6028
-------------------------------------------------------------------------------
Record Id : 01d25fdfc22dd5c4
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 12/28/2016 6:53:56 (UTC)
Flags : 0x00000000

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

Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Generic
Flags : 0x00
Level : 0
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id : c3 06 03 00 00 08 10 00 - bf fb fa 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 @ ffff8b06c7de6240

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

Error : DCACHEL0_WR_ERR (Proc 0 Bank 1)
Status : 0xbf80000000000124
Address : 0x00000002d892c180
Misc. : 0x0000000000000086

This is a write error to L0 Cache on the CPU.

Somethings you can try to fix.

Replace the CMOS battery

Reset BIOS to defaults

Update your BIOS to the latest version

If none of these fix the issue you may need to replace the CPU

The manufacturer of the computer, or the manufacturer of the motherboard if this is a custom rig will have BIOS updates available.

Thank you very much for the answer. I have a quick question regarding this actually. Can a write failure to L0 cache be caused by faulty RAM at all or is it 100% a CPU problem?

Also my temps were good on this as well just to rule out a heat problem. My CPU was running at 55 degrees C when this happened.

Neemobeer · Dec 28, 2016

No it's strictly a CPU issue or hardware interface (BIOS code).

55 C during usage is fine, but if that is your idle temp I might be concerned, but you'd have to look up your CPU specs to determine the ideal idle and under load temps.

Jen0vaCore · Dec 28, 2016

Neemobeer said:
No it's strictly a CPU issue or hardware interface (BIOS code).

55 C during usage is fine, but if that is your idle temp I might be concerned, but you'd have to look up your CPU specs to determine the ideal idle and under load temps.

Sorry about that. Yeah that's during load. My idle is anywhere from 28-34 degrees.

But alright, I'll look into it and try your suggestions and see if it helps. It's so weird how it only does this during 1 application, haha.

kemical · Dec 28, 2016

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffff8b06c7de6028, bf800000, 124}

Probably caused by : GenuineIntel

Followup:     MachineOwner

Hi,
sorry i meant to post this earlier but got diverted by someone at the front door, (neighbour). Ok so just to add to Neem's excellent post, I checked over your drivers as the error your getting can also be software based. It might be the case that a driver or software is indirectly causing the bsod.

So if the bsod should continue, first run Intel's Diagnostic test for processors:
Link Removed

If the processor passes then let's look at the drivers/Bios.

CAM_V3.sys Sat Jul 26 14:29:37 2008: NZXT PC monitoring software. This is far too old for Windows 10 and needs updating. In fact it wouldn't surprise me if this is your culprit so either update or remove:
Introducing CAM 3.0 - Our Most Advanced PC Monitoring Software - NZXT Blog

e22w8x64.sys Wed Mar 20 21:24:01 2013: Killer Networks Ethernet driver. The latest driver for this component is here: Link Removed
Follow the instructions on how to update this driver.

Bios
Bios is F5 although versions stop at a beta F8d.

Notice after flashing to F6 you then cannot go back to an earlier bios.

Bios versions F6 onwards mainly deal with compatibility for 5th gen CPU's so it's uncertain whether flashing to these versions would be any help. I guess if you tried everything else and the bsod still remained it's worth a try..
GIGABYTE - Motherboard - Socket 1150 - GA-Z97X-Gaming 3 (rev. 1.0)

As I posted initially this is only to add to Neemobeers post and in the first instance follow his advice. 🙂

Please post any new dump files.

Jen0vaCore · Dec 28, 2016

kemical said:
Code:

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 124, {0, ffff8b06c7de6028, bf800000, 124} Probably caused by : GenuineIntel Followup: MachineOwner

Hi,
sorry i meant to post this earlier but got diverted by someone at the front door, (neighbour). Ok so just to add to Neem's excellent post, I checked over your drivers as the error your getting can also be software based. It might be the case that a driver or software is indirectly causing the bsod.

So if the bsod should continue, first run Intel's Diagnostic test for processors:
Link Removed

If the processor passes then let's look at the drivers/Bios.

CAM_V3.sys Sat Jul 26 14:29:37 2008: NZXT PC monitoring software. This is far too old for Windows 10 and needs updating. In fact it wouldn't surprise me if this is your culprit so either update or remove:
Introducing CAM 3.0 - Our Most Advanced PC Monitoring Software - NZXT Blog

e22w8x64.sys Wed Mar 20 21:24:01 2013: Killer Networks Ethernet driver. The latest driver for this component is here: Link Removed
Follow the instructions on how to update this driver.

Bios
Bios is F5 although versions stop at a beta F8d.

Notice after flashing to F6 you then cannot go back to an earlier bios.

Bios versions F6 onwards mainly deal with compatibility for 5th gen CPU's so it's uncertain whether flashing to these versions would be any help. I guess if you tried everything else and the bsod still remained it's worth a try..
GIGABYTE - Motherboard - Socket 1150 - GA-Z97X-Gaming 3 (rev. 1.0)

As I posted initially this is only to add to Neemobeers post and in the first instance follow his advice. 🙂

Please post any new dump files.

Thanks for your diagnostics as well mate!

So I did what you said and ran the CPU test. It passed with flying colors. So it may be software/driver based.

Now that you mention it, this happened a lot after installing CAM. I got NZXT Hue+ LED strips for Christmas this year and installed CAM so I could control the lights. Also, I had CAM open during the test and it crashed and opened/closed a lot during the test, so I'm willing to bet that may be the culprit.

Also thanks for the driver update for my network, I'll install that too. Right now I'm on F7 in my BIOS so that's all fine.

I'm willing to bet it's CAM due to the behavior of it during the CPU test. It may be conflicting with my processor during CSGO because there's a lighting profile for it in the driver/application itself.

I'll uninstall CAM and see how it goes, although I dunno how I'll be able to control the Hue+ without it. However CAM is at the latest version right now, which is 3.2.26 at the moment of this post. As I said though, I'm willing to bet it's the culprit with it's gaming LED profiles and it only has one LED profile for a game, and that's CSGO.

Thanks for your answer, I really appreciate it!

kemical · Dec 28, 2016

Jen0vaCore said:
I'm willing to bet it's CAM due to the behavior of it during the CPU test. It may be conflicting with my processor during CSGO because there's a lighting profile for it in the driver/application itself.

Agreed.
I've heard of similar apps (Corsair RGB) causing bsod's as well so it's worth a try removing it.

Jen0vaCore · Dec 30, 2016

kemical said:
Agreed.
I've heard of similar apps (Corsair RGB) causing bsod's as well so it's worth a try removing it.

Upon uninstalling both for testing purpose, I got a few more BSODs so I reinstalled them as I need them for my keyboard/mouse and such. I did tests where I left a game running and/or played for a few hours and no other games do this, just the one.

I got one more dump file (the other 2 BSODs didn't save one) here, could you run them through bugchecker to see if it's the same L0 cache error? Thanks! : )

kemical · Dec 30, 2016

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, ffffd20dfb021028, bf800000, 124}

Probably caused by : GenuineIntel

Followup:     MachineOwner

Hi,
I did as you asked and checked for the cache error which is still there:

Code:

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

Error         : DCACHEL0_WR_ERR (Proc 3 Bank 1)
  Status      : 0xbf80000000000124
  Address     : 0x00000002ffdc6800
  Misc.       : 0x0000000000000086

However I still feel it's perhaps software based otherwise it would crash with every game. I've noticed that some of the dumps show that the network was being used around the time of the bsod:

Code:

PROCESS_NAME:  KillerService.

bwcW8x64.sys Wed Feb 13 17:25:48 2013: Killer Bandwidth Control Filter Driver please update making sure that any security you have running is disabled when uninstalling and installing the Killer driver
Link Removed

e22w8x64.sys Wed Mar 20 21:24:01 2013: Killer Networks Ethernet Card. Driver, same as the above.

MBfilt64.sys Fri Jul 31 04:40:32 2009: Realtek Hi Definition Audio driver (file labelled as Creative Audio Driver) later version can be found under win 10 drivers for your motherboard:
GIGABYTE - Motherboard - Socket 1150 - GA-Z97X-Gaming 3 (rev. 1.0)

synth3dvsp.sys Sat Jul 16 03:27:08 2016: Microsoft RemoteFX Synth3D Video VSP . I couldn't find out much about this driver so any information you have regarding it's use i'd love to know. If it isn't used anymore please remove.

Try and monitor your temperatures whilst playing CS:go, I did this once with a game and was shocked at the temps I was seeing especially on my so called stable rig so it's worth a look.

Hope all goes well!

Search

Appearance

Windows 10 BSOD only when playing CSGO ntoskrnl.exe

Jen0vaCore

Member

Attachments

kemical

Neemobeer

Windows Forum Team

Jen0vaCore

Member

Neemobeer

Windows Forum Team

Jen0vaCore

Member

kemical

Essential Member

Jen0vaCore

Member

kemical

Essential Member

Jen0vaCore

Member

Attachments

kemical

Essential Member