Overclock.net › Forums › Intel › Intel Motherboards › Question for X99 board owners with Nvidia cards: do you see PCIe bus errors, please respond to poll
New Posts  All Forums:Forum Nav:

Question for X99 board owners with Nvidia cards: do you see PCIe bus errors, please respond to poll - Page 3

Poll Results: You have X99 motherboard with Nvidia graphics card and you are seeing PCIe bus errors in your logs with the following PCI device IDs:

This is a multiple choice poll
  • 9% of voters (1)
    8086:2F02
  • 9% of voters (1)
    8086:2F03
  • 63% of voters (7)
    8086:2F04
  • 0% of voters (0)
    8086:2F06
  • 0% of voters (0)
    8086:2F07
  • 27% of voters (3)
    8086:2F08
  • 0% of voters (0)
    8086:2F0a
  • 9% of voters (1)
    other: post specifics in thread
11 Total Votes  
post #21 of 51
I have Win 8.1 64, how can I check for these particular errors you speak of?
PC
(11 items)
 
  
CPUMotherboardGraphicsRAM
i7-5930K @ 4.5/3.3 Ghz ASRock Fatal1ty X99X Killer 2x (SLI) GTX 980 Ti @ 1500/7750 16GB (4x4GB) DDR4 2400MHz 11-11-11-24-1T 
Hard DriveCoolingOSMonitor
Sam 840 Pro 256GB, WD Vlcrptr 1TB Swiftech H320 (push/pull) Windows 8.1 64-bit 3x Dell S2716DG 
PowerCaseAudio
Antec HCP-1200 Cooler Master HAF 932 Auzentech X-Fi Forte 7.1 
  hide details  
Reply
PC
(11 items)
 
  
CPUMotherboardGraphicsRAM
i7-5930K @ 4.5/3.3 Ghz ASRock Fatal1ty X99X Killer 2x (SLI) GTX 980 Ti @ 1500/7750 16GB (4x4GB) DDR4 2400MHz 11-11-11-24-1T 
Hard DriveCoolingOSMonitor
Sam 840 Pro 256GB, WD Vlcrptr 1TB Swiftech H320 (push/pull) Windows 8.1 64-bit 3x Dell S2716DG 
PowerCaseAudio
Antec HCP-1200 Cooler Master HAF 932 Auzentech X-Fi Forte 7.1 
  hide details  
Reply
post #22 of 51
You can see it in the eventlog under warnings.
Do your pc boot on random?
post #23 of 51
I am using the Asus Z10PE-D8 WS with dual Xeon E5-2620v3 and 64GB of ECC DDR4. I am using this system as a virt platform using KVM on the host with Windows clients. A dmesg of the host shows the following. The BIOS/UEFI is by AMI. What you are seeing below it the PCI bridge: Intel Corporation Xeon E5 v3/Core i7 PCI Express Root Port 2 (rev 02).
The Data Link looks really iffy and unstable from the root port. Normally one might see this if there was an issue with the hardware/firmware. I would like to point out that I am not using a Nvida GPU in this case. It is a AMD GPU. I also have the firmware in UEFI mode.
Code:
[32784.071010] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[32784.071024] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[32784.071029] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[32784.071033] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[32785.750927] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[32785.750956] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[32785.750961] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[32785.750965] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[32788.444802] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[32788.444814] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[32788.444818] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[32788.444822] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[32869.591463] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[32869.591479] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[32869.591484] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[32869.591488] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[32880.220827] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[32880.220843] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[32880.220847] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[32880.220851] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[32883.946839] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[32883.946854] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[32883.946859] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[32883.946863] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[32909.934238] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[32909.934255] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[32909.934260] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[32909.934264] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[33039.320409] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[33039.320425] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[33039.320430] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00001000/00002000
[33039.320434] pcieport 0000:00:02.0:    [12] Replay Timer Timeout  
[33049.891249] pcieport 0000:00:02.0: AER: Uncorrected (Fatal) error received: id=0010
[33049.891263] pcieport 0000:00:02.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, id=0010(Receiver ID)
[33049.891268] pcieport 0000:00:02.0:   device [8086:2f04] error status/mask=00000020/00000000
[33049.891272] pcieport 0000:00:02.0:    [ 5] Surprise Down Error    (First)
post #24 of 51
Thread Starter 
thanks for the report onryo. i haven't been able to convince any of the vendors to fix this problem, everyone seems to be pointing the finger elsewhere. for now, I'm using the workaround option by disabling MMCONFIG.
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
TAIPEI
(10 items)
 
AURORA
(13 items)
 
 
MotherboardGraphicsRAMHard Drive
ASRock X99 Extreme11 EVGA GTX 980 Superclocked 32GB 8x4GB Corsair LPX Samsung XP941  
Hard DriveCoolingOSMonitor
Western Digital 3TB RE Noctua NH-D15 Fedora 21 Linux Samsung S27D590C 
PowerCase
Seasonic SS-1200XP Cooler Master Cosmos II 
CPUMotherboardGraphicsRAM
Dual Quad-core L5430 2.66Ghz 12mb cache Intel 5000 chipset ATI ES1000 64GB FBDIMM DDR2 PC2-5300 667Mhz 
Hard DriveOSPower
WD3000FYYZ PERC H700 w/ 512MB cache CentOS 7.2.1511 950W x2 
  hide details  
Reply
post #25 of 51
This occurs with my AMD R280x cards under Linux as well. I am using mesa 10.5.9 and several before it. Kernel 3.19

MMCONFIG and NOMSI help a bit but the system still locks up.

I found that the amd catalyst driver made my system stable. So maybe the binary drivers have a workaround ?
post #26 of 51
Same problem on MSI x99s plus board with NVIDIA GeForce GTX 970
post #27 of 51
My asus sabertooth x99 reports that the cpu microcode is of a bad revision. I wonder if this could be part of what we are experiencing ?

Doing some R&D on getting it to update.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776431

microcode: CPU0 sig=0x306f2, pf=0x4, revision=0x2d
post #28 of 51
In my case, this problem appears to be caused by bad physical connection. The card was mostly working, so something fairly subtle is going on here. I noticed it was happening less when my case was horizontal, so I tried holding the card very tightly flush to the case while putting in the bracket screws. This seems to have fixed this issue for me for the last 24 hours. If I loosen the screw even slightly and retighten it without apply force to keep the card flush to the case, the problem comes back.
post #29 of 51
X99 Deluxe, 2001 BIOS with titan black. No errors.
What
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7-6950X X99 Deluxe ASUS GTX Titan Black 32GB @ 3200 
Hard DriveOSMonitorKeyboard
Samsung 960 Pro Windows 10 Pro x64 Dell UltraSharp U3014 Microsoft SideWinder X4 
PowerCaseMouseAudio
Corsair AX860 NZXT Switch 810 Mionix Castor Asus Xonar STX + 2x LME49860NA OPs + HD650s 
  hide details  
Reply
What
(12 items)
 
  
CPUMotherboardGraphicsRAM
i7-6950X X99 Deluxe ASUS GTX Titan Black 32GB @ 3200 
Hard DriveOSMonitorKeyboard
Samsung 960 Pro Windows 10 Pro x64 Dell UltraSharp U3014 Microsoft SideWinder X4 
PowerCaseMouseAudio
Corsair AX860 NZXT Switch 810 Mionix Castor Asus Xonar STX + 2x LME49860NA OPs + HD650s 
  hide details  
Reply
post #30 of 51
Hi!

Same thing on my Asrock X99E ITX/AC (Bios 1.40 and 1.20) with a 5280k and a GTX 970 (Gigabyte g1), all at default clocks sadsmiley.gif
Edited by rozjan - 1/26/16 at 7:35am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › Question for X99 board owners with Nvidia cards: do you see PCIe bus errors, please respond to poll