Question Multiple BSOD and freezing without warning

Dec 6, 2019
6
0
10
0
Hello, this is my first time posting on this forums but your insight would be extremely valuable. Basically I recent built a new PC with these specs:
msi mpg z390 pro carbon
Intel 9700kf
RTX 2080 super
corsair RM 750 (2019)
16 GB vengeance pro RGB RAM.
corsair h150I AIO
1tb 970 evo m.2
2tb seagate barracuda
1 tb wd blue from my old system

However when I had finished building the system itself I encountered my first issue where the system freezes when trying to install windows but I also got a BSOD with the "system check exception error".
So I assumed it was the lack of bios update so I corrected that. Windows then installed correctly and successfully after that I wanted to test some games and RDR2 ran fine I then launched escape from tarkov and the system froze this was my second issue. So I rebooted the system and I assumed it was the game that did it and shrugged it off the pc froze again which worried me but after I rebooted again and it was fine so I just assumed it resolved itself.

Then I left the pc on to install some other software so that I could use it after I got in after going out and returned to find the system frozen on the "system check exception" BSOD and did some research to find out the causes only to see the possible causes. First I tested my memory, not for as long as I wanted to but the first set of loops turned out with no errors but now I am stuck as I cannot think of any testing methods for the other hardware problems I may have so I can rectify it or RMA the hardware. I left my PC on overnight to see if it would survive and it did not so I have only 1 dump file from the multiple freezes and crashes and cannot access it. To add, I have been monitoring the temps of my GPU and CPU and they are yet to go above 70 degrees. my GPU under basically max load on RDR2 runs at 68 and my CPU at about 40 but its usage was only about 42%
 
Last edited:

Lutfij

Titan
Moderator
Welcome to the forums! :)

Just to corroborate the BIOS end of your story, which version of BIOS are you currently working with? Did you recreate the installer for Windows 10 using Windows Media Creation Tools? You might also want to see if loosening the mounting screws for the AIO on the CPU block, by one revolution changes your experience with the system.
 
Dec 6, 2019
6
0
10
0
Welcome to the forums! :)

Just to corroborate the BIOS end of your story, which version of BIOS are you currently working with? Did you recreate the installer for Windows 10 using Windows Media Creation Tools? You might also want to see if loosening the mounting screws for the AIO on the CPU block, by one revolution changes your experience with the system.
Thank you for the warm welcome :)
I used another system to download a windows 10 ISO and used rufus to convert a USB into a boot drive. I then installed MSI's latest bios version 7B17v16, I couldve used 7B17v171 but that is in beta. I updated the bios from 7B17v13 and I sourced them from MSI's website as I dont have a disk drive in my current system https://www.msi.com/Motherboard/support/MPG-Z390-GAMING-PRO-CARBON.
Is is possible that missing a motherboard drive such as "intel chipset Driver" could cause these sorts of problems? if so I will try to reinstall all of the drivers provided to me again in case I did. I had to use another system to do this due to the lack of "natural" ill call it LAN support and the LAN driver has to be installed to recognise the Ethernet adaptor.
 

g-unit1111

Titan
Moderator
Is is possible that missing a motherboard drive such as "intel chipset Driver" could cause these sorts of problems? if so I will try to reinstall all of the drivers provided to me again in case I did. I had to use another system to do this due to the lack of "natural" ill call it LAN support and the LAN driver has to be installed to recognise the Ethernet adaptor.
It's possible that can happen. The way to make sure that it doesn't is to disconnect ALL drives but your primary boot drive during the installation, which in this case seems to be your M2 drive. The reason for that is that Windows can install boot files across all of the drives and certain files can get lost which would lead to the error messages that you're seeing. After you're done installing, then you can reconnect all the second and third drives. It's a pain but this way it centralizes all the critical boot files.
 
Dec 6, 2019
6
0
10
0
It's possible that can happen. The way to make sure that it doesn't is to disconnect ALL drives but your primary boot drive during the installation, which in this case seems to be your M2 drive. The reason for that is that Windows can install boot files across all of the drives and certain files can get lost which would lead to the error messages that you're seeing. After you're done installing, then you can reconnect all the second and third drives. It's a pain but this way it centralizes all the critical boot files.
sorry, I got the BSOD code wrong its not system check its machine check which is a hardware error apparently, I have installed the latest drivers now. my motherboard GPU and CPU are brand new, which is the one that has the most chance of being faulty because I'm certain one of them is faulty now, the system runs fine but if |I leave it idle or not doing anything it seems to freeze it isnt my ram because I've tested it and my GPU is fine as it doesnt artifact or stutter or get too hot so im torn between my CPU and MOBO so im lost. I am still able to return these parts because I got them this week. I in no way have damaged the components. The only insight I can give at this current time is that my CPU box came crumpled so I may just RMA both my mobo and my cpu see which one is causing problems. if they both come back ok then ill send my GPU back. I only have one minidump file as I did not get the chance to change my settings
 
Dec 6, 2019
6
0
10
0
sorry, I got the BSOD code wrong its not system check its machine check which is a hardware error apparently, I have installed the latest drivers now. my motherboard GPU and CPU are brand new, which is the one that has the most chance of being faulty because I'm certain one of them is faulty now, the system runs fine but if |I leave it idle or not doing anything it seems to freeze it isnt my ram because I've tested it and my GPU is fine as it doesnt artifact or stutter or get too hot so im torn between my CPU and MOBO so im lost. I am still able to return these parts because I got them this week. I in no way have damaged the components. The only insight I can give at this current time is that my CPU box came crumpled so I may just RMA both my mobo and my cpu see which one is causing problems. if they both come back ok then ill send my GPU back. I only have one minidump file as I did not get the chance to change my settings
actually it may be my cpu
I have the dump after 4 freezes so here it is


***
  • *
  • Bugcheck Analysis *
  • *
***

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
x86 Processors
If the processor has ONLY MCE feature available (For example Intel
Pentium), the parameters are:
1 - Low 32 bits of P5_MC_TYPE MSR
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of P5_MC_ADDR MSR
4 - Low 32 bits of P5_MC_ADDR MSR
If the processor also has MCA feature available (For example Intel
Pentium Pro), the parameters are:
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
IA64 Processors
1 - Bugcheck Type
1 - MCA_ASSERT
2 - MCA_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing MCA.
3 - MCA_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
4 - MCA_FATAL
FW reported a fatal MCA.
5 - MCA_NONFATAL
SAL reported a recoverable MCA and we don't support currently
support recovery or SAL generated an MCA and then couldn't
produce an error record.
0xB - INIT_ASSERT
0xC - INIT_GET_STATEINFO
SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
0xD - INIT_CLEAR_STATEINFO
SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
0xE - INIT_FATAL
Not used.
2 - Address of log
3 - Size of log
4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
AMD64 Processors
1 - Bank number
2 - Address of MCA_EXCEPTION structure
3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: ffff9901dc522d40
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd.

SYSTEM_PRODUCT_NAME: MS-7B17

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.60

BIOS_DATE: 08/08/2019

BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd.

BASEBOARD_PRODUCT: MPG Z390 GAMING PRO CARBON (MS-7B17)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: 0

BUGCHECK_P2: ffff9901dc522d40

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x9C_GenuineIntel

CPU_COUNT: 8

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: d

CPU_MICROCODE: 6,9e,d,0 (F,M,S,R) SIG: BE'00000000 (cache) BE'00000000 (init)

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: chrome.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: DESKTOP-CR41N2M

ANALYSIS_SESSION_TIME: 12-06-2019 22:37:57.0907

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

BAD_STACK_POINTER: ffff9901dc522d08

LAST_CONTROL_TRANSFER: from fffff80333651f0a to fffff80333856040

STACK_TEXT:
ffff9901dc522d08 fffff80333651f0a : 000000000000009c 0000000000000000 ffff9901dc522d40 0000000000000000 : nt!KeBugCheckEx
ffff9901dc522d10 fffff80333652381 : 0000000000000008 ffff9901dc523070 0000000000000000 0000000000000008 : hal!HalpMcaReportError+0x10e
ffff9901dc522e60 fffff8033365159c : 0000000000000000 ffff9901dc5230f0 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0x131
ffff9901dc522e90 fffff803336525c7 : ffffaf8f3b4d6f50 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
ffff9901dc522ec0 fffff80333931dab : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
ffff9901dc522ef0 fffff80333864a7a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0xb
ffff9901dc522f20 fffff80333864760 : ffff990100000000 fffff8033386469d ffffaf8f4aef46c0 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff9901dc523060 fffff80333711f20 : ffffaf8f466e8180 0000000000000000 0000000000000000 ffffaf8f4aef46c0 : nt!KiMcheckAbort+0x260
ffffd00f1c2446c0 fffff80333710c40 : ffffaf8f3fd72080 ffff9901dc5b9180 ffff9901dc5b9180 ffffaf8f41f0d000 : nt!KiChooseTargetProcessor+0x8c0
ffffd00f1c2447f0 fffff80333710387 : ffff9901dc517180 fffff803337122d9 00000039737ff400 fffff80300000001 : nt!KiDeferredReadyThread+0x620
ffffd00f1c2448b0 fffff8033370fe47 : ffffaf8f47442120 000001ca00000000 ffffaf8f47442120 0000000000000000 : nt!KiExitDispatcher+0x187
ffffd00f1c244920 fffff80333bdb5d2 : 0000000000000000 ffffd00f1c244a80 0000000000000020 ffffd3662b8048f1 : nt!KeSetEvent+0xb7
ffffd00f1c2449b0 fffff80333867285 : ffffaf8f466e8080 0000000000000168 ffffaf8f00000000 ffffaf8f47442120 : nt!NtSetEvent+0x92
ffffd00f1c244a00 00007ffb1b28e754 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
00000039737fefa8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb1b28e754


THREAD_SHA1_HASH_MOD_FUNC: 0f746ba31102503dc73493fb818c5fa1dd0b2265

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 9620701ea99ae2c302c9923ef48a6fcbf5e87551

THREAD_SHA1_HASH_MOD: d926851fa3a09455854e7f53f4164266e459fbfd

FOLLOWUP_IP:
nt!KiHandleMcheck+b
fffff803
33931dab 0f1f440000 nop dword ptr [rax+rax]

FAULT_INSTR_CODE: 441f0f

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: nt!KiHandleMcheck+b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: b

FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

PRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KiHandleMcheck

TARGET_TIME: 2019-12-06T03:03:23.000Z

OSBUILD: 17763

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 598

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_nt!kihandlemcheck

FAILURE_ID_HASH: {f10d6786-a78f-4993-4f62-7de145ea1ce2}

Followup: MachineOwner
---------
 
Dec 15, 2019
3
0
10
0
I too am having a similar problem to this and my specs are similar to the system. i built the PC this past August and have yet to get rid of random freezing BSOD Machine Check Exception. It is not all time, sometimes when i am gaming, sometimes just at idle. Removing 1 stick of Ram made it a bit more stable for certain games. When it blue screens it almost always requires a hard reset so out of all the times it has done it, i only have 2 dump files saved. I am more suspecting the motherboard and RAM than the CPU. Ran Memtest on both Ram Sticks and they tested good. Have interchanged Ram sticks in the slots an it still freezes. Intel's Processor Diagnostic Tool passed with flying colors. I'm kind of at the point where i am suspecting a motherboard to be the problem.

Have you gotten anywhere with the problem in your Rig?
 
Dec 6, 2019
6
0
10
0
I too am having a similar problem to this and my specs are similar to the system. i built the PC this past August and have yet to get rid of random freezing BSOD Machine Check Exception. It is not all time, sometimes when i am gaming, sometimes just at idle. Removing 1 stick of Ram made it a bit more stable for certain games. When it blue screens it almost always requires a hard reset so out of all the times it has done it, i only have 2 dump files saved. I am more suspecting the motherboard and RAM than the CPU. Ran Memtest on both Ram Sticks and they tested good. Have interchanged Ram sticks in the slots an it still freezes. Intel's Processor Diagnostic Tool passed with flying colors. I'm kind of at the point where i am suspecting a motherboard to be the problem.

Have you gotten anywhere with the problem in your Rig?
Mine turned out to be a problem with the CPU itself. The machine check exception BSOD is almost always a hardware error so it may be your MOBO, I RMA'd my cpu and I am getting a replacement. Are you OCing your CPU? that can be a cause if the overclock is too high. the BSOD can also be caused by corrupted drivers so you could try reinstalling them.
If you think your motherboard is the problem I would RMA it if you can still do that but depending on the company you may have to pay a small fee for testing. if you can examine the dump as it may give you some valuable info or get someone who understands them to examine them. Thats what I tried to do anyway.

Hope you fix your rig soon
P.S. check you cooler and other temps to see if something is getting too hot for no reason as that could also be a cause
 
Dec 15, 2019
3
0
10
0
Thanks for those few tips. Tried most of them after searching for hours on forums over the past few months. I have already performed a clean install of windows 10 a few weeks ago. Thinking that would fix it to no avail. My rig just froze again after running great for about 3 hours.

Everything is 4 months old on my rig except my power supply and cpu cooler. So I would hope it would be under warranty. When you say RMA, you are saying send the suspected defective part back to the manufacturer for them to test and fix it? The only thing that is overclocked is my ram and that is just having XMP enabled in bios. Everything in my rig runs cool as well. Cpu never goes over 55 degrees Celsius, GPU never over 50. I did take it out of the socket and reset it to make sure the thermal paste was good. Still freezing.

I hope a new processor fixes your problem, make sure to post on here if it does. Good Luck!
 
Dec 6, 2019
6
0
10
0
XMP to my knowledge shouldn't really affect it especially if you are juts running the RAM at its 3600Mhz clock as you need to enable it for the processor to be able to support that speed if I'm correct. Yeah just email where you bought it from and ask them if you can RMA it and they'll talk to you about the options you have.

Thanks, I'll let you know if that fixes it and good luck with the RMA process :)
 

ASK THE COMMUNITY

TRENDING THREADS