Question Windows 10 BSOD, I7-4790k, GTX 970, Minidump attached

mrkz

Reputable
Dec 18, 2014
41
0
4,530
0
Hello. Recently I have been getting some blue screens. I have been able to get a dump from the latest bluescreen which came today just minutes ago. Something I have noticed is that I have been getting BSOD recently when I have been playing or running CSGO and everything freezes and it gives me a BSOD.

Minidump file:
https://ufile.io/0hbg1i48

MOBO: Asus B85M-G
CPU: I7-4790k
GPU: GTX 970
 

mrkz

Reputable
Dec 18, 2014
41
0
4,530
0
  1. What PSU did you have?
  2. Use " reliability monitor tool " and post what error(s) you got. https://www.howtogeek.com/166911/reliability-monitor-is-the-best-windows-troubleshooting-tool-you-arent-using/
EVGA GQ 850W Hybrid Modular 80+ PSU

The reliability monitor is in Norwegian, but I guess the codes and everything is understandable..

Datamaskinen startet på nytt etter en feilkontroll. Feilkontrollen var: 0x00000124 (0x0000000000000000, 0xffff978d1092b028, 0x00000000be000000, 0x0000000000800400). Dump ble lagret i: C:\WINDOWS\MEMORY.DMP. Rapport-ID: 3e1233e6-15dc-4686-8dbf-83659b699390.

Problemsignatur
Problemhendelsesnavn: BlueScreen
Kode: 124
Parameter 1: 0
Parameter 2: ffff978d1092b028
Parameter 3: be000000
Parameter 4: 800400
OS-versjon: 10_0_17763
Service Pack: 0_0
Produkt: 768_1
OS-versjon: 10.0.17763.2.0.0.768.101
ID for nasjonal innstilling: 1044

Got a new bluescreen just now.

Datamaskinen startet på nytt etter en feilkontroll. Feilkontrollen var: 0x00000124 (0x0000000000000000, 0xffffa30d9d11b028, 0x00000000be000000, 0x0000000000800400). Dump ble lagret i: C:\WINDOWS\MEMORY.DMP. Rapport-ID: f17552a0-f01a-427f-8bca-9a6b9a63f7c2.

Problemsignatur
Problemhendelsesnavn: BlueScreen
Kode: 124
Parameter 1: 0
Parameter 2: ffffa30d9d11b028
Parameter 3: be000000
Parameter 4: 800400
OS-versjon: 10_0_17763
Service Pack: 0_0
Produkt: 768_1
OS-versjon: 10.0.17763.2.0.0.768.101
ID for nasjonal innstilling: 1044

So far I have only noticed the bluescreens while running or playing CS:GO. Mainly the only game I play, but havent noticed it while doing something like browsing the internet etc..

Got a new minidump just now for the recent bluescreen if you need it.
https://ufile.io/x0zm2m4c
 

Ketchup79

Notable
Aug 7, 2019
1,199
112
940
48
Your dump in post 1 shows "a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem."

I would recommend you start by looking in Event Viewer under Windows Logs/System. Pay attention to any critical alerts (in red).
 

mrkz

Reputable
Dec 18, 2014
41
0
4,530
0
Usually at least a couple of dumps are necessary with a 0x124 as it relies mostly on patterns.

Could you run https://www.sysnative.com/forums/pages/bsodcollectionapp/ and upload the zip the tool creates.
Here is the file: https://ufile.io/gkd62glt

Your dump in post 1 shows "a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem."

I would recommend you start by looking in Event Viewer under Windows Logs/System. Pay attention to any critical alerts (in red).
Looks like out from the Event Viewer, that this happened right before the crash.

Kritisk 19.10.2019 04:33:45 DriverFrameworks-UserMode 10110 User-mode Driver problems.
Det har oppstått et problem med en eller flere brukermodusdrivere, og vertsprosessen er stoppet. Dette kan midlertidig stoppe muligheten til å få tilgang til enheten.

Kritisk 19.10.2019 04:33:45 DriverFrameworks-UserMode 10111 User-mode Driver problems.
Enheten HID-compliant headset (plassering (unknown)) er frakoblet på grunn av en krasjet brukermodusdriver. Windows vil prøve å starte enheten på nytt 5 ganger til. Kontakt enhetsprodusenten for mer informasjon om dette problemet.
 

axe0axe0

Respectable
Jun 5, 2017
842
20
2,165
95
I mentioned there are usually a couple of dumps necessary, below code is usually the best info you can get from a 0x124. If there are more crashes that also record an internal timer you may want to look into the CPU.
All situations I've seen with an internal timer error have been a result of a faulty CPU.
Code:
===============================================================================
Common Platform Error Record @ ffff978d1092b028
-------------------------------------------------------------------------------
Record Id     : 01d585da7b782d40
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/18/2019 21:11:31 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff978d1092b0a8
Section       @ ffff978d1092b180
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   : 0x00000000000306c3
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : c3 06 03 00 00 08 10 04 - 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  @ ffff978d1092b240

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

Error         : Internal timer (Proc 4 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x000000005249d818
  Misc.       : 0x000000005249d818


===============================================================================
Common Platform Error Record @ ffffa30d9d11b028
-------------------------------------------------------------------------------
Record Id     : 01d585f925f35c0a
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/19/2019 2:30:44 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa30d9d11b0a8
Section       @ ffffa30d9d11b180
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   : 0x00000000000306c3
Processor ID  : 0x0000000000000005

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

Local APIC Id : 0x0000000000000005
CPU Id        : c3 06 03 00 00 08 10 05 - 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  @ ffffa30d9d11b240

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

Error         : Internal timer (Proc 5 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00000000556f0674
  Misc.       : 0x00000000556f0674
 

mrkz

Reputable
Dec 18, 2014
41
0
4,530
0
I mentioned there are usually a couple of dumps necessary, below code is usually the best info you can get from a 0x124. If there are more crashes that also record an internal timer you may want to look into the CPU.
All situations I've seen with an internal timer error have been a result of a faulty CPU.
Code:
===============================================================================
Common Platform Error Record @ ffff978d1092b028
-------------------------------------------------------------------------------
Record Id     : 01d585da7b782d40
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/18/2019 21:11:31 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff978d1092b0a8
Section       @ ffff978d1092b180
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   : 0x00000000000306c3
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : c3 06 03 00 00 08 10 04 - 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  @ ffff978d1092b240

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

Error         : Internal timer (Proc 4 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x000000005249d818
  Misc.       : 0x000000005249d818


===============================================================================
Common Platform Error Record @ ffffa30d9d11b028
-------------------------------------------------------------------------------
Record Id     : 01d585f925f35c0a
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 10/19/2019 2:30:44 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffa30d9d11b0a8
Section       @ ffffa30d9d11b180
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   : 0x00000000000306c3
Processor ID  : 0x0000000000000005

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

Local APIC Id : 0x0000000000000005
CPU Id        : c3 06 03 00 00 08 10 05 - 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  @ ffffa30d9d11b240

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

Error         : Internal timer (Proc 5 Bank 4)
  Status      : 0xbe00000000800400
  Address     : 0x00000000556f0674
  Misc.       : 0x00000000556f0674
Seems like its caused by my HyperX headset seeing its common on their reddit..
https://www.reddit.com/r/HyperX/comments/adgo7a View: https://www.reddit.com/r/HyperX/comments/adgo7a/hyperx_cloud_ii_restarting_my_pc_without_warning/?utm_source=reddit&utm_medium=usertext&utm_name=HyperX&utm_content=t1_eyp8axw
 

ASK THE COMMUNITY

TRENDING THREADS