x99 extreme 11 PCI Express Problems
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=4314
Printed Date: 15 Jul 2025 at 4:36pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: x99 extreme 11 PCI Express Problems
Posted By: phrenesis
Subject: x99 extreme 11 PCI Express Problems
Date Posted: 28 Jan 2017 at 6:43am
|
Rig: x99 extreme 11 i7-6850k Asus Strix 1080 8-Gaming 4x8GB HyperX Fury HX426C15FB/8 m2 Slot 2: PX-128M8PeG <- OS m2 Slot 1: PX-512M8PeG <- Finds it, but not used atm 750W Corsair psu Problem1: about 60% of the time, it wont get to bios Error Codes ranging mostly from 92-99 Problem2: WHEA correctable error (PCI Express Root Port) on startup from win10 (once I get to eventviewer they stop and don't spam) Problem3: WHEA uncorrectable/internal BSOD when updating gpu drivers manually or when windows update tries to update them I tested with 1 Ram, Tested with an old AMD Card, same errors. Edit: Forcing GEN2/GEN1 PCI Express does not work, same error, same crash Edit2: Tested with 3.00 and 3.20 BIOS
|
Replies:
Posted By: wardog
Date Posted: 28 Jan 2017 at 9:02am
|
Well, you're not running out of lanes, that's for sure. Not with that i7-6850K At the bottom left of the MB is a downward facing 4-pin Molex connector. Plug/power it from a separate cable coming directly from the PSU. It provides additional/supplemental power to the PCIe bus if and or when needed. Too, your 4 sticks? A single kit? And JiC, proper mem slots to use:  |
Posted By: wardog
Date Posted: 28 Jan 2017 at 9:04am
|
" rel="nofollow - And seeings I forgot in my first reply ............ FYI: http://www.asrock.com/support/faq.asp?id=334 |
Posted By: wardog
Date Posted: 28 Jan 2017 at 9:17am
|
" rel="nofollow - Meh, this is another ? PSU. What Model Corsair, and how old is it? I ask because a lot of folks seemingly hold on to their PSU's well after their Use By date. From build to build. |
Posted By: phrenesis
Date Posted: 28 Jan 2017 at 9:36am
|
" rel="nofollow - All the parts arrived today, and is a fresh install I installed the RAM as shown in the manual (A_1, B_1, C_1, D_1) I tried PCI Express slot 1,2,4,5 with the gpu I know the Dr. Debug code from the manual. Edit: Tested with single stick as well This 4pin? http://imgur.com/a/kB9D3 I thought this one is only if you have more than 3 GPUS installed It also has PCIE_PWR2, my PSU doesn't have any 4pin molex.
|
Posted By: wardog
Date Posted: 28 Jan 2017 at 10:06am
" rel="nofollow -
Yea. Excuse me, I overlooked this MB has two PCIE_PWR connectors. Use the one you pictured in that imgur link. PCIE_PWR1 Nothing harmful will come of it if the bus doesn't need it bucked up some with connecting this. |
phrenesis wrote:Posted By: wardog
Date Posted: 28 Jan 2017 at 10:10am
The Corsair website for the RMx 750 shows you should have 7 4-pin Molex connectors on, well, one or two modular cables. http://www.corsair.com/en-us/rmx-series-rm750x-750-watt-80-plus-gold-certified-fully-modular-psu" rel="nofollow - http://www.corsair.com/en-us/rmx-series-rm750x-750-watt-80-plus-gold-certified-fully-modular-psu |
Posted By: phrenesis
Date Posted: 28 Jan 2017 at 10:10am
| I checked my psu, it does not have a 4pin molex connector..... |
Posted By: phrenesis
Date Posted: 28 Jan 2017 at 10:14am
| Man, I think I was blind. Found them, will test tomorrow. Thanks a lot wardog! |
Posted By: wardog
Date Posted: 28 Jan 2017 at 10:23am
hehehe, Post back when you get to it. |
Posted By: phrenesis
Date Posted: 28 Jan 2017 at 7:33pm
|
Hello Wardog and others I attached the 4pin molex connector, it did not make any difference. I clean installed win10 again, updated all the chipset drivers. The BSOD when updating the GPU driver went away. It still does give me 92/94/96 Error Code on Dr. Debug sometimes. The WHEA correctable Error when starting is still there. I ran prime95 for an hour or two as well, no error, max temp 63° with 100% CPU load (no OC obviously) EDIT: I found out it might have been a driver problem by debugging the dump and checking google, some others even with different chipsets had the same error message when chipset drivers were bugged or not the newest installed.
|