ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - BSOD on new X99X install
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

BSOD on new X99X install

 Post Reply Post Reply Page  123>
Author
Message
Franko View Drop Down
Newbie
Newbie


Joined: 19 Dec 2015
Status: Offline
Points: 18
Post Options Post Options   Thanks (0) Thanks(0)   Quote Franko Quote  Post ReplyReply Direct Link To This Post Topic: BSOD on new X99X install
    Posted: 03 Jan 2016 at 4:11am
I built a new system with the following components from Newegg.  All are new except for the GTX780 video, which was used in my Win7 system and always worked fine.
I am getting Blue Screens about once a day, usually while playing WOW - once doing a backup copy.
I am looking for a suggestions for a procedure to identify the problem.

This is a fresh install of Windows 10 professional via a USB download from Microsoft.  I installed it on the Samsung 950 M.2 SSD in UEFI mode.
I disabled the Killer Ethernet in Bios and deinstalled the drivers because I thought that was the issue, but it did not stop the BSODs.  The mobo Bios is at 1.90.
I think I have all the hardware drivers up to date - the ones I checked again are listed below next to the hw.
Thanks in advance for your help!

Frank

===
ASRock ASRock Fatal1ty Gaming Fatal1ty X99X Killer LGA 2011-v3 Intel X99 SATA 6Gb/s USB 3.0 ATX Intel Motherboard

Intel Core i7-5930K Haswell-E 6-Core 3.5 GHz LGA 2011-v3 140W BX80648I75930K Desktop Processor

CORSAIR Vengeance LPX 32GB (4 x 8GB) 288-Pin DDR4 SDRAM DDR4 2666 (PC4 21300) memory kit for DDR4 Systems Model ...

GeoForce GTX 780 GF Game ready driver v 361.43 12/21/2015

Windows 10 Pro clean install - System, Games, Software:
SAMSUNG 950 PRO M.2 512GB PCI-Express 3.0 x4 Internal Solid State Drive (SSD) MZ-V5P512BW - downloaded the Samsung driver install program and ran it.

Separate SSD for alternate boot image and backup:
Mushkin Enhanced ECO2 2.5" 512GB SATA III Internal Solid State Drive (SSD) MKNSSDEC512GB

Data Disk:
SAMSUNG 850 EVO 2.5" 1TB SATA III 3-D Vertical Internal Solid State Drive (SSD) MZ-75E1T0B/AM

SeaSonic Platinum SS-860XP2 860W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS PLATINUM Certified Full Modular ...
Noctua NH-D15 SSO2 D-Type Premium CPU Cooler, NF-A15 x 2 PWM Fans
Antec Nine Hundred Black Steel ATX Mid Tower Computer Case with Upgraded USB 3.0
Razer Naga 2014 Gaming Mouse v 6.2.9200.16384 8/12/2015
Logitech M570 Trackball




Here is a list of the BSODS. All 0xa on ntoskrnl.exe


BlueScreenView Analysis:
010216-4546-01.dmp 1/2/2016 12:37:38 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffe001`a39eb898 00000000`00000002 00000000`00000000 fffff801`d5ac00e2 ntoskrnl.exe ntoskrnl.exe+142760 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10586.17 (th2_release.151121-2308) x64 ntoskrnl.exe+142760 C:\Windows\Minidump\010216-4546-01.dmp 12 15 10586 353,932 1/2/2016 12:38:48 AM
123015-4578-01.dmp 12/30/2015 9:07:02 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffe001`e28ecd08 00000000`00000002 00000000`00000000 fffff802`6d2450e2 ntoskrnl.exe ntoskrnl.exe+142760 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10586.17 (th2_release.151121-2308) x64 ntoskrnl.exe+142760 C:\Windows\Minidump\123015-4578-01.dmp 12 15 10586 299,828 12/30/2015 9:08:02 AM
123015-4625-01.dmp 12/30/2015 8:45:07 AM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffe001`28497d58 00000000`00000002 00000000`00000000 fffff802`b66c30e2 ntoskrnl.exe ntoskrnl.exe+142760 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10586.17 (th2_release.151121-2308) x64 ntoskrnl.exe+142760 C:\Windows\Minidump\123015-4625-01.dmp 12 15 10586 324,892 12/30/2015 8:46:19 AM
122915-4953-01.dmp 12/29/2015 6:21:12 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffe001`601dcf78 00000000`00000002 00000000`00000000 fffff800`71a590e2 ntoskrnl.exe ntoskrnl.exe+142760 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10586.17 (th2_release.151121-2308) x64 ntoskrnl.exe+142760 C:\Windows\Minidump\122915-4953-01.dmp 12 15 10586 338,108 12/29/2015 6:22:28 PM
122815-4312-01.dmp 12/28/2015 5:43:06 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffe001`481638e8 00000000`00000002 00000000`00000000 fffff802`d6c430e2 ntoskrnl.exe ntoskrnl.exe+142760 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10586.17 (th2_release.151121-2308) x64 ntoskrnl.exe+142760 C:\Windows\Minidump\122815-4312-01.dmp 12 15 10586 319,932 12/28/2015 5:44:13 PM
122815-4421-01.dmp 12/28/2015 3:00:15 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a ffffe001`131fdd18 00000000`00000002 00000000`00000000 fffff802`470b80e2 ntoskrnl.exe ntoskrnl.exe+142760 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 10.0.10586.17 (th2_release.151121-2308) x64 ntoskrnl.exe+142760 C:\Windows\Minidump\122815-4421-01.dmp 12 15 10586 317,244 12/28/2015 3:02:14 PM

Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 03 Jan 2016 at 5:49am
Corsair does certify the CMK32GX4M4A2400C14R to work on this motherboard.

First thing I'll inquire of is if you've flashed to the latest NON-BETA production BIOS available? As the X99 is a new chipset and with new variants of DDR4 coming onto the market manufacturers have been on a steady pattern of releasing new BIOS to tackles this issue.

Unfortunately, those errors look to me and my experience building as memory related. My guess by seeing the likes myself, this doesn't mean 100% positive here in your/this instance though.

Get her running the latest BIOS first. This alone may prove the simple and easy way.

Failing the latest BIOS, get MemTest86+ HERE and run it for 6-7 complete passes to determine if any tweaks you've made are stable on her.


Edited by wardog - 03 Jan 2016 at 5:51am
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 26933
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 03 Jan 2016 at 6:33am
I am inclined to agree with Wardog here, memory compatibility seems a likely culprit so grabbing the latest BIOS may resolve that. If that fails you can try using 1 module of RAM and check with memtest and for BSODs, if clear keep adding the RAM one module at a time and testing until you have all 4 installed or you run into a BSOD/memtest errors. You may have a bad module or a kit that does not operate in quad channel correctly. Additionally, ensure your RAM is seated properly. 

Now if the RAM comes up clear try uninstall your GPU driver using DDU from safe mode then install the latest driver again. NTOSKRNL errors can be caused by display drivers, especially if you updated them and they failed to uninstall the old ones correctly.
Back to Top
Franko View Drop Down
Newbie
Newbie


Joined: 19 Dec 2015
Status: Offline
Points: 18
Post Options Post Options   Thanks (0) Thanks(0)   Quote Franko Quote  Post ReplyReply Direct Link To This Post Posted: 03 Jan 2016 at 6:36am
Thanks much for the suggestion!  I did have the latest 1.90 Bios, but it looks like the 2.10 bios has gone Production a few days ago.  I will give it a try and see how it goes, and then work on the memory.  I remember having some strange problems that were fixed permanently by reseating the memory, too, although that was a machine exposed to fluctuating outdoor temperatures.

Frank
Back to Top
Franko View Drop Down
Newbie
Newbie


Joined: 19 Dec 2015
Status: Offline
Points: 18
Post Options Post Options   Thanks (0) Thanks(0)   Quote Franko Quote  Post ReplyReply Direct Link To This Post Posted: 04 Jan 2016 at 10:54pm
Brief update:
- Upgraded to 2.1 BIOS.  Got the same BSOD later that day.
- Downloaded Prime95 and ran it for 20 minutes of so to load CPU 100%.  System ran nice and cool and no errors or problems.
- Downloaded PassMark MemTest86, installed to USB stick, and ran default.
   Got a single error after about 15 minutes of running.
   Stopped the test, checked options, which made me realize I better just use the default test regimen.
   Restarted for a longer test to see if I could determine location etc of errors.
   Over the next few days, I ran several hours of mem tests - trying new cold boots, etc, but could not get a single error to reappear.
 

Question for the group:  I don't like seeing even ONE memory error, but how many hours of running memtest do you need to decide if that one error was a cosmic ray hit or some other fluke?

Future tests:
- removed data SSD, backup SSD, all USB devices except Mouse and Keyboard.
- continued testing bare machine to see if any BSODs appear
- if I get a BSOD, I may remove the M.2 pciE drive and boot to a Sata SSD to eliminate it

While I wait:
- Evaluate every hardware driver and make sure it is current with no documented issues
Back to Top
PetrolHead View Drop Down
Groupie
Groupie


Joined: 07 Oct 2015
Status: Offline
Points: 403
Post Options Post Options   Thanks (0) Thanks(0)   Quote PetrolHead Quote  Post ReplyReply Direct Link To This Post Posted: 05 Jan 2016 at 12:29am
I believe the standard test will do four full passes and I think that's what you should go for, especially since you already got one error. It may take ages, though. With my two sticks and 16 GB of RAM it took nearly 40 hours to finish all four passes. It will also look like it's stuck, as it may not show any progress for 6 hours or more, but as long as the symbols for the CPU cores keep spinning, it's still working through the tests.
Ryzen 5 1500X, ASRock AB350M Pro4, 2x8 GB G.Skill Trident Z 3466CL16, Sapphire Pulse RX Vega56 8G HBM2, Corsair RM550x, Samsung 960 EVO SSD (NVMe) 250GB, Samsung 850 EVO SSD 500 GB, Windows 10 64-bit
Back to Top
Franko View Drop Down
Newbie
Newbie


Joined: 19 Dec 2015
Status: Offline
Points: 18
Post Options Post Options   Thanks (0) Thanks(0)   Quote Franko Quote  Post ReplyReply Direct Link To This Post Posted: 06 Jan 2016 at 4:00am
Did you find any errors after 40 hours?
My BSODs usually show up within 4-5 hours of running, sometimes within a few minutes of startup.  So I thought 4 or 5 hours of continuous memory tests with no errors would clear the memory.

But it only takes time so I will let it run all the way next time.  I know I made it to the 4th pass but I don't think it completed all the way.
Back to Top
Franko View Drop Down
Newbie
Newbie


Joined: 19 Dec 2015
Status: Offline
Points: 18
Post Options Post Options   Thanks (0) Thanks(0)   Quote Franko Quote  Post ReplyReply Direct Link To This Post Posted: 06 Jan 2016 at 4:09am
Update:

I removed all the devices, even the CDROM, except for the SSD, the Video card, keyboard and mouse.
I removed the M.2 PCIE Samsung SSD and installed only a single 500G SATA SSD.
Reseated the memory sticks.
I used diskpart to clean the SSD and installed a fresh Win 10 Pro on it in UEFI mode.
Install went well, so I updated the drivers, triple checking only those from the ASROCK website.
I updated the drivers for Nvidia card with the recommended dec 2015 drivers.
I installed minimal apps - Chrome and World of Warcraft (great test case)
Played WOW last night for about 3 hours with no issues.
Booted machine today, did a couple of web browses and got a BSOD.

Problem is stil there.  I will do an extended memory test but am beginning to think I have an unstable motherboard.

The Nvidia card has been working in another machine for over 6 months with no problems.

I will update after memtest completes 4 full passes.

thanks guys!

Frank



Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 06 Jan 2016 at 5:15am
Too, in just now going back over the thread, check what your GPU temps are. This will also show its ugly head if the GPUs thermal paste has dried out some and now letting the card get warm/hot.

Reading over your posts with your writing style I assume the machine has been cleaned and now free of dust. But I'll ask anyways, no harm no foul in asking, right?
Back to Top
Franko View Drop Down
Newbie
Newbie


Joined: 19 Dec 2015
Status: Offline
Points: 18
Post Options Post Options   Thanks (0) Thanks(0)   Quote Franko Quote  Post ReplyReply Direct Link To This Post Posted: 06 Jan 2016 at 5:49am
I appreciate all input.  The gear is all new - no dust, except a bit on the reused video card, which was blown off.

I see the GPU temps do go up when I run WOW.  I installed one of those apps that show it and the CPU temp continuously on a little bar graph, which I run on a second monitor.  I am trying to remember the number I reach on the GPU - maybe 75C, or maybe 80C?  Whatever it was, as soon as I started playing the game it went right up to that temp and then was a level line.  I think the card prevents it from getting any higher by limiting the work it does, but I am not a GPU expert.  The card worked in my Windows 7 machine for over 6 months, but this has a faster CPU so are you thinking that maybe it makes the card run faster/hotter?  I am running a full 4 pass memtest, so I can't check right now.  Could a hot video card cause a 'IRQL NOT LESS OR EQUAL' BSOD do you think?

Thanks,

Frank  


Back to Top
 Post Reply Post Reply Page  123>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.078 seconds.