MSI X99S gaming 7 Issues and BSOD!

Hello and i thank those that will come to help me. Ever since i have bought my motherboard and other parts to it my following problems are this: When i boot up my PC on the right corner of my screen and also on my LED i get this numbers: 99, 9C, B4, A2 and 99 again. I have seen on youtube as well as my friends and families PC that those numbers don`t show up when booting the PC. For me it takes a long time to load into windows because of that.
Next is the BSOD: My BSOD is called 0x124 and this is what it shows in WinDBG:
2: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: fffffa800ef8c8d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: a
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
DPC_STACK_BASE: FFFFF880035A1FB0
STACK_TEXT:
fffff880`0359a938 fffff800`02e1aa3b : 00000000`00000124 00000000`00000004 fffffa80`0ef8c8d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0359a940 fffff800`02fdec33 : 00000000`00000001 fffffa80`0ef770c0 00000000`00000000 fffffa80`0ef76b60 : hal!HalBugCheckSystem+0x1e3
fffff880`0359a980 fffff880`017c9bcf : fffffa80`00000750 fffffa80`0ef770c0 00000000`00000000 fffffa80`0ef8bab0 : nt!WheaReportHwError+0x263
fffff880`0359a9e0 fffff880`017c95f6 : 00000000`00000000 fffff880`0359ab30 fffffa80`0ed6dd80 fffff880`0359aab0 : pci!ExpressRootPortAerInterruptRoutine+0x27f
fffff880`0359aa40 fffff800`02ec171c : fffff880`03572180 fffff880`0359ab30 fffffa80`0ed6dd80 00000000`00000001 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`0359aab0 fffff800`02ebd5a2 : fffff880`03572180 fffff880`00000001 00000000`00000001 fffff800`00000000 : nt!KiInterruptDispatch+0x16c
fffff880`0359ac40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PCIEXPRESS
BUCKET_ID: X64_0x124_GenuineIntel_PCIEXPRESS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_pciexpress
FAILURE_ID_HASH: {3fd82133-403a-028a-6939-36a9eccfc17d}
Followup: MachineOwner
2: kd> !errrec fffffa800ef8c8d8
===============================================================================
Common Platform Error Record @ fffffa800ef8c8d8
Record Id : 01d0a416a02455e5
Severity : Fatal (1)
Length : 672
Creator : Microsoft
Notify Type : PCI Express Error
Timestamp : 6/11/2015 7:46:40 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : PCI Express
Descriptor @ fffffa800ef8c958
Section @ fffffa800ef8c9e8
Offset : 272
Length : 208
Flags : 0x00000001 Primary
Severity : Recoverable
Port Type : Root Port
Version : 1.1
Command/Status: 0x0010/0x0407
Device Id :
VenId:DevId : 8086:2f04
Class code : 030400
Function No : 0x00
Device No : 0x02
Segment : 0x0000
Primary Bus : 0x00
Second. Bus : 0x00
Slot : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ fffffa800ef8ca1c
Device Caps : 00008001 Role-Based Error Reporting: 1
Device Ctl : 0027 ur FE NF CE
Dev Status : 0002 ur fe NF ce
Root Ctl : 0008 fs nfs cs
AER Information @ fffffa800ef8ca58
Uncorrectable Error Status : 00004020 ur ecrc mtlp rof uc ca CTO fcp ptlp SD dlp und
Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Severity : 00062010 ur ecrc MTLP ROF uc ca cto FCP ptlp sd DLP und
Correctable Error Status : 00000000 adv rtto rnro dllp tlp re
Correctable Error Mask : 00000000 adv rtto rnro dllp tlp re
Caps & Control : 00000005 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
Header Log : 00000000 00000000 00000000 00000000
Root Error Command : 00000000 fen nfen cen
Root Error Status : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer
Correctable Error Source ID : 00,00,00
Correctable Error Source ID : 00,00,00
===============================================================================
Section 1 : Processor Generic
Descriptor @ fffffa800ef8c9a0
Section @ fffffa800ef8cab8
Offset : 480
Length : 192
Flags : 0x00000000
Severity : Informational
Proc. Type : x86/x64
Instr. Set : x64
CPU Version : 0x00000000000306f2
Processor ID : 0x0000000000000002
This has showed me that i have the following problem with this drivers or what ever they are :
So my question is: Is it my motherboards fault or CPU?
Can you guys please help me?
Dump file is attached hopefully.

Continuing from yesterday. I just got a BSOD 124 while playing Witcher 3. Here is the WinDBG info:
2: kd> !analyze -v
* Bugcheck Analysis *
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: fffffa8005ee48d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: witcher3.exe
CURRENT_IRQL: a
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
STACK_TEXT:
fffff880`096400a8 fffff800`03607a3b : 00000000`00000124 00000000`00000004 fffffa80`05ee48d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`096400b0 fffff800`03196c33 : 00000000`00000001 fffffa80`05eccb10 00000000`00000000 fffffa80`05ecc1b0 : hal!HalBugCheckSystem+0x1e3
fffff880`096400f0 fffff880`00fa6bcf : fffffa80`00000750 fffffa80`05eccb10 00000000`00000000 fffffa80`05ee4010 : nt!WheaReportHwError+0x263
fffff880`09640150 fffff880`00fa65f6 : 00000000`00000000 fffff880`096402a0 fffffa80`05cbbd80 fffff800`03601a0a : pci!ExpressRootPortAerInterruptRoutine+0x27f
fffff880`096401b0 fffff800`0307971c : 00000000`00000000 ffffffff`ffffffff fffffa80`05cbbd80 ffffffff`ffffff01 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`09640220 fffff800`03080110 : fffff800`030c8853 fffff800`030898cc fffff800`03089938 00000000`00000000 : nt!KiInterruptDispatch+0x16c
fffff880`096403b8 fffff800`030c8853 : fffff800`030898cc fffff800`03089938 00000000`00000000 fffff880`09640450 : nt!KiDispatchInterrupt
fffff880`096403c0 fffff800`03089938 : 00000000`00000000 fffff880`09640450 00000000`00000001 00000000`00000000 : nt!KiDpcInterruptBypass+0x13
fffff880`096403d0 fffff880`05e01c8e : 00000000`00000000 fffff880`09640620 fffffa80`069c7000 00000000`00000000 : nt!KiSecondaryClockInterrupt+0x1a8
fffff880`09640560 00000000`00000000 : fffff880`09640620 fffffa80`069c7000 00000000`00000000 fffff880`096406b0 : nvlddmkm+0x1c4c8e
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PCIEXPRESS
BUCKET_ID: X64_0x124_GenuineIntel_PCIEXPRESS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_pciexpress
FAILURE_ID_HASH: {3fd82133-403a-028a-6939-36a9eccfc17d}
Followup: MachineOwner
2: kd> !errrec fffffa8005ee48d8
===============================================================================
Common Platform Error Record @ fffffa8005ee48d8
Record Id : 01d0a80359c89c07
Severity : Fatal (1)
Length : 672
Creator : Microsoft
Notify Type : PCI Express Error
Timestamp : 6/16/2015 7:23:49 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : PCI Express
Descriptor @ fffffa8005ee4958
Section @ fffffa8005ee49e8
Offset : 272
Length : 208
Flags : 0x00000001 Primary
Severity : Recoverable
Port Type : Root Port
Version : 1.1
Command/Status: 0x0010/0x0407
Device Id :
VenId:DevId : 8086:2f04
Class code : 030400
Function No : 0x00
Device No : 0x02
Segment : 0x0000
Primary Bus : 0x00
Second. Bus : 0x00
Slot : 0x0000
Dev. Serial # : 0000000000000000
Express Capability Information @ fffffa8005ee4a1c
Device Caps : 00008001 Role-Based Error Reporting: 1
Device Ctl : 0027 ur FE NF CE
Dev Status : 0002 ur fe NF ce
Root Ctl : 0008 fs nfs cs
AER Information @ fffffa8005ee4a58
Uncorrectable Error Status : 00004020 ur ecrc mtlp rof uc ca CTO fcp ptlp SD dlp und
Uncorrectable Error Mask : 00000000 ur ecrc mtlp rof uc ca cto fcp ptlp sd dlp und
Uncorrectable Error Severity : 00062010 ur ecrc MTLP ROF uc ca cto FCP ptlp sd DLP und
Correctable Error Status : 00000000 adv rtto rnro dllp tlp re
Correctable Error Mask : 00000000 adv rtto rnro dllp tlp re
Caps & Control : 00000005 ecrcchken ecrcchkcap ecrcgenen ecrcgencap FEP
Header Log : 00000000 00000000 00000000 00000000
Root Error Command : 00000000 fen nfen cen
Root Error Status : 00000000 MSG# 00 fer nfer fuf mur ur mcr cer
Correctable Error Source ID : 00,00,00
Correctable Error Source ID : 00,00,00
===============================================================================
Section 1 : Processor Generic
Descriptor @ fffffa8005ee49a0
Section @ fffffa8005ee4ab8
Offset : 480
Length : 192
Flags : 0x00000000
Severity : Informational
Proc. Type : x86/x64
Instr. Set : x64
CPU Version : 0x00000000000306f2
Processor ID : 0x0000000000000002
I was playing with MSI ODS on and saw the temps: GPU 69ºC using 1732MBRam and 1320 Mhz CPU 45ºC and RAM used 3500 since i had only one module inside. As for what i was doing while in game is that i was heading towards a village to free it from some ghouls (if this is of any help).

Similar Messages

MSI X99S Gaming 7 and debug code 67

Hi,
I have MSI X99S Gaming 7 motherboard, Crucial 2x8GB 2133 DDR4, MSI GTX970 Gaming 4G, Corsair RM650, i7-5820k setup.
When I am trying to boot the machine it always stops and the debug led shows code 67. I have tried to take everything out, reseated processor and to boot with just the minimum set of components. Result is always the same code 67.
I am running out of ideas. Do you have any hints or should I just return the mobo and processor?
Best Regards,
juha

Quote from: shadow85 on 22-December-14, 19:40:31
So are you going to RMA the board or just use it with 2 sticks? Thats means you are not planning on using it in quad channel, would be a waste.
Anyways if I were you I would definatly RMA it asap. This error 67 problem people are having seems to be widespread. MSI really need to look into this.
As has been said previously, contact MSI. Should they look into it? Yes, but the moderators here are not MSI employees, and while we can bring issues to their attention, we cannot make them look into problems.
So if you have this problem, please contact MSI directly: >>How to contact MSI.<<

MOVED: Msi x99s gaming 9 and overclocking

This topic has been moved to Overclocking, Undervolting.
https://forum-en.msi.com/index.php?topic=258176.0

Bump removed
>>Please read and comply with the Forum Rules.<<
You could try to >>Use the MSI HQ Forum USB flasher<<[/ur...

Re: Msi x99s gaming 9 and overclocking

Dear MSI Support & all guys
I bought a new gtx 960 but after i boot my pc sometimes it shows no display on monitor...sometimes it shows till windows loading but after that no display on monitor...i had worked out a temporary solution. When that happens...

Quote from: chc on Today at 09:02:51The MSI F3 recovery may not work if you remove its partition to somewhere else. ...

MSI X99S Gaming 7, Update firmware of HD in raid

Hi all,
I've got an MSI X99S Gaming 7, and I builded a raid maded by 2 HD Samsung 840 EVO, cause Samsung recently released an update of firmware for this HDs that fix some performance bug, I would like to apply it, but samsung Magician doesn't recognize HDs cause they are into a raid.
Is there a way to apply the firmware without destroy the raid?
Regards

Quote from: Nichrome on 30-May-15, 03:00:13
Firmware update/change is usually putting a device( In your case:SSDs) back to factory settings/conditions. So most likely you have to remove RAID, apply updates and recreate everything. Ask Samsung for perfect answer on this.
Umm....no. Not this at all.
SSD's are a bit different than motherboards. If updating the firmware on an SSD destroyed all the data on it, you would have a TON of very unhappy customers on your hands.
It will NOT reset it back to factory settings......I have never seen a case of an SSD firmware (that works properly....) that destroys the data that it holds. I have seen a few firmware updates where the data got destroyed because the firmware wasn't good and was not tested properly.
The big problem I really see here is the fact that you are using a RAID setup. I'm not sure how well it will take updating the SSD firmware, but I would imagine the data should be preserved.

Msi z87 gd 65 gaming freezing and bsod

msi z87 gd 65 gaming freezing and bsod happens in a game or on desktop
build 26/09/2013 08:16 PM
i7 - 4770k
msi z87 gd65 gaming
corsair 32 gb ddr3 cmy32gx3m4a2400c10r
asus r9280x-dc2-3gd5 r9 280x
h110i corsair
corsair hx860i
crucial m4
cooler master cormos 2 case
system started to freeze and bsod
items I have done
osri
new psu
memtest all sticks and one at a time all passed
hd tune smart test passed
increased voltage on memory in case it was that as the x m p does it at 1.5v increase 4 steps from 1.5v to 1.9v all 4 gave the same issue
1.65v bsod as well
who crashed says amd ccc is causing the issue reinstalled with driver from asus and latest also the beta same issue is happening
this is why I think its the main board but was going to run the system from intel gpu by removing the amd gpu from system maybe even test an alt slot x8 to see what happens
currently testing r9 280z card with default gpu clock 850mhz instead of 1000mhz incase that's whats causing it
I know this is another post the other post does not have edit on the post any more so making you aware of this
any one got any ideas as to what to try next
On Sat 06/09/2014 04:26:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8346-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2DBA1)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FFB3BA1, 0xFFFFF8800CFEE540, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 21:27:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-8564-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF9600012E354)
Bugcheck code: 0x50 (0xFFFFFD00C0873680, 0x0, 0xFFFFF9600012E354, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 05/09/2014 17:54:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-7909-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x3267E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004A3267E, 0xFFFFF880060F6A30, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 23:44:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-9796-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00B7F9E50, 0x0, 0x15B641)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:54:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-7878-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800494A12B, 0xFFFFF88011FF4558, 0xFFFFF88011FF3DB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 04/09/2014 21:30:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090414-8470-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800FF8F8F0, 0xFFFFF8800907E420, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Tue 02/09/2014 18:50:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090214-8143-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF8B00E9D800C, 0x0, 0xFFFFF8000397A981, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 31/08/2014 15:31:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-7753-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x2112B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800413B12B, 0xFFFFF88011DEF558, 0xFFFFF88011DEEDB0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sun 31/08/2014 08:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-8424-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x308F7)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880048308F7, 0xFFFFF88008DC2B00, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Sat 30/08/2014 22:58:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083114-9687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0xFFFFDA801908C040, 0x2, 0x0, 0xFFFFF80003659EC9)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
26 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

No need to edit, just add a reply as flobelix asked for exact models of RAM and motherboard.
As it's double posting, this one gets locked. Please continue this one:
https://forum-en.msi.com/index.php?topic=183138.msg1314803#msg1314803
>>Please read and comply with the Forum Rules.<<
Topic Locked

MSI X99S GAMING 7 - slow booting; HDD aren´t recognized in BIOS

Hi,
i´m facing a similar Problem as it is described in "MSI X99A Gaming 7 and Samsung SM951 PCI-e very slow boot time" https://forum-en.msi.com/index.php?topic=255919.0
My rig:
- i7 5930k
- X99S Gaming 7 (BIOS h90)
- PALIT GTX 980 Super Jetstream
- OCZ revodrive 3 x2 240 GByte (System disk)
- Corsair Force 3 120 GByte (game disk)
- 2x SAMSUNG HD501LJ 500 GByte (SATA 3GB/s)
- 1 LG Electronics BH16NS40
- 16 GByte Corsair Vengeance LPX schwarz DIMM Kit 16GB, DDR4-2666, CL15-17-17-35 (CMK16GX4M4A2666C15)
- 1000W power supply
- ANTEC P193 case
- G19 Keyboard
- MX518 Mouse.
I assembled it yesterday and during the first booting sequence it restarted 3 times.
After that it took 5 minutes to be on the Windows Desktop. Furthermore I recognized that all the HDDs and the optical drive weren´t available.
I tried to activate them in the Windows System - with no result. Than I checked the BIOS, they weren´t present there.
At the end i checked the HDDs only with the power supply, they booted. As soon as I connect them with the SATA cable they stand still - no spin up hear-able.
Now The BluRay and the HDDs are disconnected, the booting sequence is a Little bit faster (still 3 minutes).
In the BIOS I only activated the XMP-Profile für the RAM and I changed the booting sequence for the REVODRIVE.
May someone has any hint for me, how to deal with this Problem - but as I stated at the very beginning: it sounds similar to me.
Best regards from Austria
Gerald
P.S.: I apologize for "hijacking" - I tried to simplify the Forum by merging similar issues.

Your explanation isn't very helpful.
Your third try you got the Revodrive, corsair, and optical running? Meaning that you could boot multiple times and have it all work correctly?
I hate saying it, but if you aren't going to be descriptive, we aren't going to be very much help.
For what it's worth, I'm starting to think that the Revodrive and the motherboard do not work well together.
Personally, I would also consider contacting MSI directly about the issue. They might be able to issue a new BIOS that improves compatibility.
>>How to contact MSI.<<

MSI x99 Gaming 7 Crashing during Windows UEFI Boot

Hello everyone,
I'm dealing with a strange problem here and i cannot seem to find any solution. Yesterday i updated my m/b bios from H.8 to H.9 and everything worked fine but 30 minutes later during some regular windows and drivers updates i restarted the machine only to find it crashing during windows loading logo when booting. I initially thought to be something about the new bios update (or windows/drivers updates) so i switched to the back-up bios ,updated it to H.8 (which i was using before) and did a quick format but the problem still occurs.
I pinpointed the problem to be something in the bios (bios update resets settings to defaults both when i updated to H.9 for the main bios & H.8 for the backup bios) and the UEFI settings for windows 8.1 since it doesn't occur when i disable the "Windows 8/8.1 Feature". What exactly does this feature do? The only difference i saw was the loading logo , now i see MSI red/black picture with the small circle-dots loading instead of a Black screen with white MSI logo if i enable the feature.
My system is new (three months old) and i never had any crash or lock-up anywhere (nor it is overclocked). All settings in the bios are default except the "Boot Mode Select" is UEFI and the "MSI Fast boot" is enabled. Windows 8.1 64Bit are installed in UEFI mode.
-MSI X99 Gaming 7
-Intel I7 5820k + Corsair H110
-G.Skill Ripjaws DDR4 16GB
-Gigabyte 970 G1 Gaming SLI
-Samsung 850 Pro 256GB
-EVGA SuperNOVA 1000 G2

Ok ,seem to have some updates:
First of all i was wrong about the SATA ports i was using (my second GPU blocks the view of the ports).
- SSD was connected to SATA3 while the other two HDD's to SATA10 & 9
I first disabled Samsung RAPID mode (you never know). Then i changed the SSD from SATA3 to SATA1 port and didn't connected the other 2HDD's at all. Enabled the "Windwos 8/8.1 feature" & Secure Boot and quickly did 4-5 restarts from the bios and from Windows, even a cold boot. No crashes but i need to do more reboots to make sure it doesn't occur any more. Then i will connect the other two HDD's and check for crashes.
Update#1 . Ok my other two HDD's are connected to SATA ports 3 & 4. After 3-4 restarts & 2 cold boots everything seems fine , no crashes at all. I don't know if maybe after 10 restarts it will occur but i'm confident enough that it should already be present now. So it seems that either Samsung Rapid Mode is responsible or the other SATA ports.
Update#2 . So Samsung Rapid Mode seems to work fine, again no crashes at all. This is getting really weird. So that leaves me with the Sata ports ,now i don't know if i need to change again sata ports to recreate the problem or leave it as it is (working) but then again if it's indeed the SATA ports then maybe something is faulty. Either way i'll check it. :/
Update#3 . I think i came to a conclusion. SATA ports 7-10 seem to have the problem.
- I reconnected everything to the original ports i was using (SSD to SATA3 and 2xHDD's to SATA10 & 9) .The crash happens the second time i restart the PC.
- Moved SSD to SATA1 , crash happens again at the second boot.
- Moved the 2xHDD's to SATA 7&8 ,crash happens at first boot.
- Moved the 2xHDD's to SATA 3&4 . NO Crash occurs.
I have no idea what's going on, the manual states that SATA 7-10 support only IDE mode and AHCI (SATA 1-6 supports RAID 0,1,5,10). For the record i do not use RAID.
So what is the problem? I didn't have any issues at all with the previous configuration. Did any of the SATA port's became faulty when using the "Windows 8/8.1 feature" after the bios update? Should i ask for a replacement?
The last thing i could try is to unistall the Intel Rapid Storage. MSI's drivers site for this m/b has the 13.1.0.1058 version while Intel has 13.6.0.1002 but they do not work as it says platform is not supported. I have the MSI's version installed all this time.

How to update my MSI X99S Gaming 7 Bios without loose my raid settings

Hi all,
I've got a MSI X99S Gaming 7 Motherboard.
Last time I used MSI Live Update and I performed BIOS update I lost totally my raid settings ( O.S. HardDisk C is build on my raid 1) and I had to reinstall all from 0. Now MSI Live Update notified me a new BIOS version available, is there a way to perform it without lost my C Drive one more time?
Thanks in advance for your help.

Quote from: JLio01 on 03-March-15, 09:17:09
The only settings should do is after BIOS updating, go the BIOS Settings--Advanced--Integrated Peripherals--SATA Mode switch to [RAID Mode], and everything should be fine.
Yes exactly, that's usually and typically which has to be done.
But with some note there are an exceptions from this:
in the past there was some BIOSes due bugs which caused RAID array lost issue after flashing,
assume raid was re-enabled after the update,
but RAID array was lost(didn't recognize the settings) and didn't show and unable to rebuild..
so its always good to have a backup of important data just in case..
don't trust too much to technology

MSI X99S Gaming 9 AC Unboxing Video

Hey guys,
newbie here on the forum...just bought my first MSI mobo, so I thought I should join MSI forum just in case I have any problem.
Anyway this is my first unboxing video for a motherboard...the mobo is the MSI X99S Gaming 9 AC motherboard.

Hi again,
Regarding RAM and watercooling: how I see this (and MSI might too) is that X99 series is based and thought about professional editing, creating, and in most cases people don't have water cooling attached to their, I don't know, Quadro K5200. Anyways, you can ask them why they actually did it this way (no matter it's X99 board, matter is that it doesn't fit watercooling backplate together with RAM, so surprised too).
>>How to contact MSI.<< If required.
For the BIOS: well.. in most cases new BIOS release is stability rather than performance. But glad you found out the issue of impossibility to update it. I wouldn't really help you, as I know enough to help you brick it Kidding. Rather not give bad info/guidance and then see you blaming me for bricking your board. Also X99 is new series, and I have no clue (yet) if M-Flash is improved (compared to Z87/Z97 boards) but also if Forum's Flash tool would work at all.
Regarding USB Key: I guess your Kingston is around 4Gb, whereas Sandisk Extreme 8 or 16? Had same issue, not just with update but also with taking screenshots within BIOS.
Quote from: vmanuelgm on 19-September-14, 01:24:23
Next time I ask for help, I would like ideas to solve the problem, and not answers like that...
Sorry I tried to help. The fact RAM slots are that near, none of us can help it. Regarding BIOS, I tried to tell you it's risky, and that if you don't experience problems, is usually not worth updating.
Regards

MSI X99S Gaming 7 Won't Boot

Hi -
I just recently purchased an X99S motherboard. I put it all together, and all was fine for about 24 hours. I updated the BIOS and then started running a defrag and left the machine on while I went to work. When I got home, the machine was off. It's not responding to the power button the board or on my case. If I turn the power off on my PSU and turn it back on and hit the power switch, I get a split second flash of lights and then nothing. I initially thought that it was my power supply so I bought a new one. I got that installed and same thing. One thing to note is that the MSI LED up by the 24 pin connector is on red. I've already tried the secondary BIOS and I have removed all of the memory except the DIMM in Slot 7. I haven't yet tried to remove the board from the case yet and tried it on a non conductive surface. I just wanted to get some thoughts on that debug LED that is currently on. I believe the motherboard has just died, but wanted to run it by someone first.
Here are my specs:
Board: MSI X99S Gaming 7
Bios: Version 14.7
VGA: MSI GTX980 Gaming
PSU: EVGA 1000 Watt G2
CPU: Intel Core i7-5930K 3.5GHz
MEM: Corsair Vengeance 2666 4x4gb CMK16GX4M4A2666C16
HDD: PNY 256GB SSD
COOLER: Corsair CWCH60 Water Cooler
OC: None
OS: Windows 8.1 64bit

Take it out of the case, place on non conductive surface (wooden table, motherboard box) and run it then. Also try with single RAM stick in every RAM slot.
Try clearing CMOS >>Clear CMOS Guide<<
Also make sure all power connectors are properly fitted in.
What way did you update the BIOS? Also was it successful?

MSI x99 Gaming 7 Debug code 04

hi this day my computer dont start only black screen , i see mobo debug code 04
msi x99 gaming 7 service manuel say 04 code = Power on South Bridge Initialization
i use 2. bios swich computer working no problem
now i go RMA?
edit: me try bios clear button nothing always full black screen and debug code 04 , i cant remove bios battery 2 graphic card + water cooling :/

If you familiar with flashing bios, you can try use the second bios to recover the first one.
Manuel has some guide...
BIOS recovery with AFUDOS command
When BIOS updating fails or causes the computer non-bootable, you can recover the
failed BIOS by the steps below.
Preparation:
1. Prepare a bootable USB flash drive.
2. Download the latest BIOS file from the MSI official website at www.msi.com, and
then decompress the file.
3. Copy the AFUDE238.exe and the BIOS file to the bootable USB flash drive
BIOS recovery steps:
1. Power off the computer.
2. Set the Multi-BIOS switch to the functional BIOS ROM.
3. Insert the bootable USB flash drive you have made to the USB port.
4. Boot the computer into the bootable USB flash drive.
5. Set the Multi-BIOS switch to the failed BIOS ROM.
6. Execute the below command to flash the BIOS:
For example: AFUDE238 EXXXXIMS.XXX
7. Restart the computer after the BIOS flashing is complete.
Important
Do not use the Multi-BIOS switch when system is booting up.

Msi x99 gaming 9 ack problems

ok got my new msi x99 gaming 9 ack with i7 5930k and g.skill 2400 ram
got my corsair ax1200i
so my problems i have been working on this all night near enough but today we have progress.
so problem is when i put ram in slot 1 would not post debug 04/55/60 no keyboard or signal to monitor. so i have finally got it working and got into the bios by put just one stick in slot 5. tried all 4 sticks in slot 5 but one failed at 6f so i think now one stick is faulty. but back to main problem with slot one.
once i had it booting up i switched off system and added 1 stick in slot one.
and it would not post debug 04/55/60.
so do i ram it or do you think bios update will fix this problem thanks in advance

Last night the exact same problem occurred to my Gaming 9 ACK.
Board worked flawlessly for three months with a 5960X processor, quad channel G.Skill 3.33 memory ( 16gb- 4x4 ) and four msi GTX980 gaming in quad sli mode.
Turned off the pc last night, and today, upon start the pc did not boot.
04-55-60-04 and all over again.
Memory modules are populated in slots 1-3-5-7. After several try and error efforts, slot 7 is blocking the system from booting. All four modules checked and are fine.
Removed module in slot 7 and booted. No problem there.
After entering windows 7 environment, a second even bigger surprise surfaced.
NO SLI. Device manager sees only gtx980 in slot 1 and nothing else.
New tests.
Only pci-e slot 1 works. All others are non functional.
So I am with an 8000$ pc, which works with 12gb triple channel memory and one VGA.
Obviously motherboard has gone south.
What now ???

MSI x99s Gaming 7 Debug code 79

MSI x99s Gaming 7 Debug code 79
Anyone have any ideas what this is?

79 - CSM initialization
Does it stop at that point or continue booting? If stopping and more assistance is needed add specs following >>Posting Guide<<

Hey i have problem white msi x99s gaming 7 main board led debug cod 04

hey me is Jacob. and i have thes problem White me msi x99s gaming 7 that i get code 04 in the led debug when i power it up and then it whont boot up as normal and it stands on the code 04 in the led debug on the motherboard and it just came Yesterday. and it have been runing for 7 months White no problem and that is that i have the time I have had it in. and when the led debug code 04 in the manual it say power on south bridge initiation. me bios version on me msi x99s gaming 7 is H.90

Board: MSI x99s gaming 7
Bios: Version H.90
VGA: MSI 970GTX gaming 4g, MSI 750TIGTX GAMING 2 GB
PSU: Cooler Master G750M, 750W PSU
Intel Core i7-5820k Intel® Haswell-E 3.3GHz (3.6GHz Turbo Boost) LGA 2011-v3
MEM: Crucial DDR4 16GB 2133MHz Quad-channel KIT
HDD: samsung 840 evo 120gb SSD and Seagate® Desktop SSHD 1TB
COOLER: Intel TS13A Air Cooler
OS: Windows 8.1 64bit Professional
i have tried:
1. Tested power supply with a Thermaltake power supply tester, all voltages are within range, including the CPU power connector, which i did double check to be plugged in.
2. Tried the video card in another PC, working fine, also tried it in each pci express slot (four of them) on the MSI X99S GAMING 7 board.
3. Tried resetting the bios and have also tried booting with just one memory stick in Dimm slot 1
4. Tried powering up the board out of the case with just the power supply, video and memory connected.
and it still get the samme problem as before and still stand on code 04 and still not boot up.

Msi x99 gaming 9 ack does not detect capture card when using with xsplit

msi x99 gaming 9 ack does not detect capture card when using with xsplit
i install every but still it does not work.

Hi
It wasn't hard to find your motherboard version:
http://www.msi.com/support/mb/Z68AGD80_B3.html#down-bios
Since your BIOS is v20.1, it couldn't be G3
Apart from checking BIOS, you can only check motherboard or moth...

MSI X99S gaming 7 Issues and BSOD!

Similar Messages

Maybe you are looking for