EVGA

Whea-Logger Event ID: 17 x99 Classified PCIE 3.0

Page: < 12 Showing page 2 of 2
Author
Post
Essentials Only Full Version
corndogg18
iCX Member
  • Total Posts : 288
  • Reward points : 0
  • Joined: 2008/05/22 11:19:55
  • Location: Minnesota
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/29 18:06:36 (permalink)
Hmmm, yeah I just did a clean remove, and installed 344.11 again. Didn't work. So for not, what are you guys using? Anything work descent so your system doesn't lock up a handful of times a day?

Specs:
EVGA X99 Classified Mobo
Intel I7 5960x @ 4.3Ghz
Corsair H100i CPU Cooler
8x4GB (32GB) G.Skill Ripjaws 4  @
2400Mhz 15-15-15-35 @ 1.20V
2x EVGA 580 Classifieds 3GB SLI  @ 900Mhz
Intel 750 series 1.2TB AIC SSD (Main Drive)
Intel 730 Series 480GB SSD (Storage Drive)  
Corsair AX1200 PSU
Corsair Obsidian Series 650D Case 
Corsair K70 RGB Keyboard
EVGA TORQ X10 Mouse
#31
efilloon
New Member
  • Total Posts : 74
  • Reward points : 0
  • Joined: 2008/04/16 17:32:54
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/29 18:14:40 (permalink)
Just to note and it could be nothing...but I am not in raid. You comment that its locking up and freezing could this be the issue? I know its a pain in the butt and it may not be the issue but use one SSD and try that...just trying help and to think out the box...

EVGA X99 Classified
Intel 5930 4.329GHz (watercooled - Ek-Supremacy EV0 - (Original CSQ) Full Nickel)
32Gb Corsair Platinum Dominator 2800MHz
2 EVGA 980 Classified's (EK WBs)
512 Gb Samsung 850 Pro
Corsair 1000HX PSU
Corsair K70 Cherry MX Red RGB Mechanical Gaming Keyboard
Logitech G502 Proteus Spectrum
Sound Blaster Z PCIe Gaming Sound Card
Windows 10 Pro 64 bit
#32
squall-leonhart
CLASSIFIED Member
  • Total Posts : 2904
  • Reward points : 0
  • Joined: 2009/07/27 19:57:03
  • Location: Australia
  • Status: offline
  • Ribbons : 24
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/29 18:24:49 (permalink)
You will not fix this with drivers, as whea errors are produced between device-device and not device-device driver.
 
A bios update on both or either end might rectify the situation by allowing the device more time to negotiate a stable link (majority of gen 3 issues are link bit errors because the signal negotiated is out of spec)

CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:BenQ G2400WD, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme
#33
Sajin
EVGA Forum Moderator
  • Total Posts : 49165
  • Reward points : 0
  • Joined: 2010/06/07 21:11:51
  • Location: Texas, USA.
  • Status: offline
  • Ribbons : 199
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/29 19:16:21 (permalink)
lol @ this is will be fixed with a driver update.


See my current build here: https://forums.evga.com/My-bench-rig-unlimited-power-m3596024.aspx
RTX 2080 Ti 4-way SLI?!?!: https://forums.evga.com/RTX-2080-Ti-4way-SLi-set-by-yours-truly-m2954756.aspx
#34
corndogg18
iCX Member
  • Total Posts : 288
  • Reward points : 0
  • Joined: 2008/05/22 11:19:55
  • Location: Minnesota
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/29 19:59:05 (permalink)
Sounds good, I'll be patient and wait for the next set of NVidia drivers. It did cross my mind that my RAID 0 could be the issue, however they are one of the best SSD drives designed for RAID 0 that money can buy. Yes, I am sure there is something better, but this Intel 730's are really nice. Not ruling out that one could be faulty, because the second you tell someone its not the problem, it magically becomes the problem. I've only had the 730's for about 5 months. They worked without a hitch with my Z77 FTW. So did these 580 Classifieds. After guyzer6945(Thank you for that!) posted his discussion with Nvidia support, I feel that most likely is the issue, especially when the NVidia rep claimed she has heard of the issue, and there is a trouble ticket for it to be resolved with a driver fix dated for next release.
post edited by corndogg18 - 2014/09/29 20:01:14

Specs:
EVGA X99 Classified Mobo
Intel I7 5960x @ 4.3Ghz
Corsair H100i CPU Cooler
8x4GB (32GB) G.Skill Ripjaws 4  @
2400Mhz 15-15-15-35 @ 1.20V
2x EVGA 580 Classifieds 3GB SLI  @ 900Mhz
Intel 750 series 1.2TB AIC SSD (Main Drive)
Intel 730 Series 480GB SSD (Storage Drive)  
Corsair AX1200 PSU
Corsair Obsidian Series 650D Case 
Corsair K70 RGB Keyboard
EVGA TORQ X10 Mouse
#35
squall-leonhart
CLASSIFIED Member
  • Total Posts : 2904
  • Reward points : 0
  • Joined: 2009/07/27 19:57:03
  • Location: Australia
  • Status: offline
  • Ribbons : 24
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/29 20:32:09 (permalink)
corndogg18
Sounds good, I'll be patient and wait for the next set of NVidia drivers.



Enjoy your wait . . . seriously.
 
I feel that most likely is the issue, especially when the NVidia rep claimed she has heard of the issue, and there is a trouble ticket for it to be resolved with a driver fix dated for next release.

 
just set Gen 2, its all a driver is going to do anyway.

CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:BenQ G2400WD, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme
#36
corndogg18
iCX Member
  • Total Posts : 288
  • Reward points : 0
  • Joined: 2008/05/22 11:19:55
  • Location: Minnesota
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/29 21:05:32 (permalink)
I did set it to Gen 2.0, bios still says 1.0. GPUz says 2.0. I guess time will tell.

Specs:
EVGA X99 Classified Mobo
Intel I7 5960x @ 4.3Ghz
Corsair H100i CPU Cooler
8x4GB (32GB) G.Skill Ripjaws 4  @
2400Mhz 15-15-15-35 @ 1.20V
2x EVGA 580 Classifieds 3GB SLI  @ 900Mhz
Intel 750 series 1.2TB AIC SSD (Main Drive)
Intel 730 Series 480GB SSD (Storage Drive)  
Corsair AX1200 PSU
Corsair Obsidian Series 650D Case 
Corsair K70 RGB Keyboard
EVGA TORQ X10 Mouse
#37
guyzer6945
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2008/01/31 19:44:43
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/30 06:02:08 (permalink)
After much reading, I'm torn, on one hand Nvidia is taking ownership of the issue, on the other hand what Squall says makes logical sense. I did receive an email from EVGA last night that they have identified the issue and are working on a mobo bios update as we speak. Its just frusterating because PCIE spec 3 has been out for how long? and we still have to deal with this garbage juice.
#38
corndogg18
iCX Member
  • Total Posts : 288
  • Reward points : 0
  • Joined: 2008/05/22 11:19:55
  • Location: Minnesota
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/09/30 07:39:59 (permalink)
I'm happy that these issues are atleast known of now, and working on a fix. Once this platform matures, it should really be nice!

Specs:
EVGA X99 Classified Mobo
Intel I7 5960x @ 4.3Ghz
Corsair H100i CPU Cooler
8x4GB (32GB) G.Skill Ripjaws 4  @
2400Mhz 15-15-15-35 @ 1.20V
2x EVGA 580 Classifieds 3GB SLI  @ 900Mhz
Intel 750 series 1.2TB AIC SSD (Main Drive)
Intel 730 Series 480GB SSD (Storage Drive)  
Corsair AX1200 PSU
Corsair Obsidian Series 650D Case 
Corsair K70 RGB Keyboard
EVGA TORQ X10 Mouse
#39
guyzer6945
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2008/01/31 19:44:43
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/06 09:45:05 (permalink)
I finally got the issue solved. I RMA'd the MSI board and bought an Asus X99-E WS. All problems solved. Learned the hard way not to trust MSI. That being said, its definitely a hardware issue. Hope this helps.
#40
bigmyke
iCX Member
  • Total Posts : 393
  • Reward points : 0
  • Joined: 2009/01/07 19:57:40
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/06 22:27:12 (permalink)
this isn't good news :/
#41
bigmyke
iCX Member
  • Total Posts : 393
  • Reward points : 0
  • Joined: 2009/01/07 19:57:40
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/07 18:04:06 (permalink)
any official update?
#42
AnonymousGuy
iCX Member
  • Total Posts : 452
  • Reward points : 0
  • Joined: 2014/09/17 21:15:46
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/07 22:28:43 (permalink)
Same problem as OP:
 
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus:Device:Function: 0x0:0x3:0x2
Vendor ID:Device ID: 0x8086:0x2f0a
Class Code: 0x30400

The details view of this entry contains further information.
 
 
x1000's when I play BF4.  I hate when fresh installs of Windows aren't perfect b/c of hardware.  The whole Haswell-Xeon platform has been sampled for 18 months...did no one bother to check on SLI with Win 7?
post edited by AnonymousGuy - 2014/10/07 22:31:21

Workstation:  12900KF @ 5.2Ghz || MSI Pro-A Z690 DDR4|| EVGA FTW3 3090 1000W || G.Skill 3866 4x8GB || Corsair AX1200i || whole-house loop.
Mining Box: HP Prodesk G1 (Haswell 4590), 3x Gigabyte 3080Ti, AX1500i @ 240V.
LANRig/GuestGamingBox: 9900nonK || Gigabyte Z390 Master || ASUS TUF 3090 650W shunt || Corsair SF600 || CPU+GPU watercooled 280 rad pull only || whole-house loop.
Server Router (Untangle): 8350K @ 4.7Ghz || ASRock Z370 ITX || 2x8GB 3200 || PicoPSU 250W, running on AX1200i || whole-house loop.
Server Compute/Storage: 10850K @ 5.1Ghz || Gigabyte Z490 Ultra || EVGA 3060 || LSI 9280i-24 port || 4TB Samsung 860 Evo, 5x10TB Seagate Enterprise Raid 6, 4x8TB Seagate Archive Backup ||  whole-house loop.
Laptop: HP Elitebook 840 G8 (Intel 1185G7) + 3060 Thunderbolt Dock, Razer Blade Stealth 13" 2017 (Int
#43
Sajin
EVGA Forum Moderator
  • Total Posts : 49165
  • Reward points : 0
  • Joined: 2010/06/07 21:11:51
  • Location: Texas, USA.
  • Status: offline
  • Ribbons : 199
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/08 02:24:25 (permalink)
I knew it. 


See my current build here: https://forums.evga.com/My-bench-rig-unlimited-power-m3596024.aspx
RTX 2080 Ti 4-way SLI?!?!: https://forums.evga.com/RTX-2080-Ti-4way-SLi-set-by-yours-truly-m2954756.aspx
#44
bigmyke
iCX Member
  • Total Posts : 393
  • Reward points : 0
  • Joined: 2009/01/07 19:57:40
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/11 15:31:46 (permalink)
any update?
#45
EVGA_JacobF
EVGA Alumni
  • Total Posts : 16946
  • Reward points : 0
  • Joined: 2006/01/17 12:10:20
  • Location: Brea, CA
  • Status: offline
  • Ribbons : 26
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/16 16:41:32 (permalink)
This is fixed in 1.09 BIOS.


#46
bigmyke
iCX Member
  • Total Posts : 393
  • Reward points : 0
  • Joined: 2009/01/07 19:57:40
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/16 17:52:41 (permalink)
Thanks Jacob!
#47
bigmyke
iCX Member
  • Total Posts : 393
  • Reward points : 0
  • Joined: 2009/01/07 19:57:40
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/20 20:24:22 (permalink)
I'm now experiencing hard lockups while gaming with pcie set to auto in bios.  I have two 680 GTX SLI.  If i set them to PCIE 2.0, I won't lockup.
#48
corndogg18
iCX Member
  • Total Posts : 288
  • Reward points : 0
  • Joined: 2008/05/22 11:19:55
  • Location: Minnesota
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/10/25 09:27:25 (permalink)
Ok, so new drivers came out from NVidia on October 22nd 344.48. However my cards still crash randomly. Event viewer has the following log message: "
Display driver nvlddmkm stopped responding and has successfully recovered.". I looked on other sites for some things to do, follow the steps, made sure my system is set on "High Performance". Also went into advanced power settings and made sure my PCI-E lanes were not set to sleep.
 
Any other thoughts?

Specs:
EVGA X99 Classified Mobo
Intel I7 5960x @ 4.3Ghz
Corsair H100i CPU Cooler
8x4GB (32GB) G.Skill Ripjaws 4  @
2400Mhz 15-15-15-35 @ 1.20V
2x EVGA 580 Classifieds 3GB SLI  @ 900Mhz
Intel 750 series 1.2TB AIC SSD (Main Drive)
Intel 730 Series 480GB SSD (Storage Drive)  
Corsair AX1200 PSU
Corsair Obsidian Series 650D Case 
Corsair K70 RGB Keyboard
EVGA TORQ X10 Mouse
#49
matobsk
New Member
  • Total Posts : 6
  • Reward points : 0
  • Joined: 2014/10/05 08:40:22
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/11/15 12:21:41 (permalink)
Running linux, updating to 1.09 helped some.
Now on 1.11, still getting these logs:
 
[ 21.795306] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 21.795312] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[ 21.795314] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00001000/00002000 
[ 21.795316] pcieport 0000:00:02.0: [12] Replay Timer Timeout 
[ 21.799829] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 21.799834] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[ 21.799835] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00001000/00002000 
[ 21.799836] pcieport 0000:00:02.0: [12] Replay Timer Timeout 
[ 22.203150] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 22.203158] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 22.203160] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000 
[ 22.203161] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 23.418624] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 23.418631] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[ 23.418632] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00001000/00002000 
[ 23.418634] pcieport 0000:00:02.0: [12] Replay Timer Timeout 
[ 24.526247] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 24.526256] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[ 24.526259] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00001000/00002000 
[ 24.526262] pcieport 0000:00:02.0: [12] Replay Timer Timeout 
[ 26.504053] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 26.504060] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[ 26.504062] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00001000/00002000 
[ 26.504063] pcieport 0000:00:02.0: [12] Replay Timer Timeout 
[ 27.486651] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 27.486659] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 27.486661] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000 
[ 27.486662] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 28.190934] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 28.190942] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 28.190944] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000 
[ 28.190946] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 28.225928] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 28.225935] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 28.225936] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000 
[ 28.225937] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 31.416802] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 31.416811] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 31.416812] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000 
[ 31.416814] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 33.568113] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 33.568123] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[ 33.568126] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00001000/00002000 
[ 33.568128] pcieport 0000:00:02.0: [12] Replay Timer Timeout 
[ 36.355896] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 36.355903] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.355905] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000 
[ 36.355906] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.406108] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 36.406117] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.406119] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000 
[ 36.406120] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.508848] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 36.508854] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Transmitter ID)
[ 36.508856] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00001000/00002000
[ 36.508858] pcieport 0000:00:02.0: [12] Replay Timer Timeout 
[ 36.556550] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 36.556558] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.556559] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.556561] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.856783] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 36.856790] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.856792] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.856793] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.890645] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 36.890653] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.890655] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.890656] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.906467] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 36.906475] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.906476] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.906478] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.911869] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 36.911875] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.911877] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.911878] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.924266] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 36.924274] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.924276] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.924277] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.924531] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 36.924536] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.924537] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.924538] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.974541] pcieport 0000:00:02.0: AER: Corrected error received: id=0010
[ 36.974547] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.974549] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.974553] pcieport 0000:00:02.0: [ 6] Bad TLP 
[ 36.990686] pcieport 0000:00:02.0: AER: Multiple Corrected error received: id=0010
[ 36.990694] pcieport 0000:00:02.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=0010(Receiver ID)
[ 36.990696] pcieport 0000:00:02.0: device [8086:2f04] error status/mask=00000040/00002000
[ 36.990697] pcieport 0000:00:02.0: [ 6] Bad TLP

 
I have my EVGA 780Ti installed in the lower x16 slot (only PCIE board). I cannot move it to slot 1 due to CPU heatsink interference.
The number of errors reduces if I run in Gen2 (which I do most of the time)
#50
subvert
New Member
  • Total Posts : 56
  • Reward points : 0
  • Joined: 2010/05/26 17:15:21
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2014/12/27 13:50:42 (permalink)
I was getting this error increasingly on an evga SR-2 with 4 x GTX 780 6Gb
 
I just installed new Nvidia drivers 347.09 and ok so far... (only been 10 minutes, but crashes were very frequent)
 
I may try the latest evga sr-2 drivers also

SR-2 / 2 x X5650 / 48Gb (6 x 8gb) / RTX 2080 super, GTX 1080Ti / Lian-Li PC-A77F
#51
eyepiz
New Member
  • Total Posts : 20
  • Reward points : 0
  • Joined: 2007/12/26 14:58:22
  • Status: offline
  • Ribbons : 0
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2015/03/29 10:10:11 (permalink)
Dis this ever get resolved?? I'm having the same error running a (1) Titan and BCOD when I and a Second titan.
 
#52
AnonymousGuy
iCX Member
  • Total Posts : 452
  • Reward points : 0
  • Joined: 2014/09/17 21:15:46
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2017/01/15 14:40:53 (permalink)
Replying to myself, I moved from the EVGA X99 Classified to a ASUS Rampage V Extreme to a ASRock X99 WS-E.
 
Back to getting the exact same:
 
"Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)"
 
Flood of errors.
 
I laughed that I had the same problem on the Classy and forgot all about this thread.  Guess ASRock sucks at updating their BIOS.  Sent them a support request so we'll see if anything happens.

Workstation:  12900KF @ 5.2Ghz || MSI Pro-A Z690 DDR4|| EVGA FTW3 3090 1000W || G.Skill 3866 4x8GB || Corsair AX1200i || whole-house loop.
Mining Box: HP Prodesk G1 (Haswell 4590), 3x Gigabyte 3080Ti, AX1500i @ 240V.
LANRig/GuestGamingBox: 9900nonK || Gigabyte Z390 Master || ASUS TUF 3090 650W shunt || Corsair SF600 || CPU+GPU watercooled 280 rad pull only || whole-house loop.
Server Router (Untangle): 8350K @ 4.7Ghz || ASRock Z370 ITX || 2x8GB 3200 || PicoPSU 250W, running on AX1200i || whole-house loop.
Server Compute/Storage: 10850K @ 5.1Ghz || Gigabyte Z490 Ultra || EVGA 3060 || LSI 9280i-24 port || 4TB Samsung 860 Evo, 5x10TB Seagate Enterprise Raid 6, 4x8TB Seagate Archive Backup ||  whole-house loop.
Laptop: HP Elitebook 840 G8 (Intel 1185G7) + 3060 Thunderbolt Dock, Razer Blade Stealth 13" 2017 (Int
#53
bcavnaugh
The Crunchinator
  • Total Posts : 38977
  • Reward points : 0
  • Joined: 2012/09/18 17:31:18
  • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
  • Status: offline
  • Ribbons : 282
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2017/01/15 14:44:44 (permalink)
AnonymousGuy
Replying to myself, I moved from the EVGA X99 Classified to a ASUS Rampage V Extreme to a ASRock X99 WS-E.
 
Back to getting the exact same:
 
"Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)"
 
Flood of errors.
 
I laughed that I had the same problem on the Classy and forgot all about this thread.  Guess ASRock sucks at updating their BIOS.  Sent them a support request so we'll see if anything happens.


Is their an Apology in here somewhere?

Associate Code: 9E88QK5L7811G3H


 
#54
Sleinous
EVGA Forum Moderator
  • Total Posts : 7663
  • Reward points : 0
  • Joined: 2010/06/12 12:22:01
  • Location: France
  • Status: offline
  • Ribbons : 32
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2018/01/09 00:30:57 (permalink)
Getting the
AnonymousGuy
Same problem as OP:
 
A corrected hardware error has occurred.

Component: PCI Express Root Port
Error Source: Advanced Error Reporting (PCI Express)

Bus:Device:Function: 0x0:0x3:0x2
Vendor ID:Device ID: 0x8086:0x2f0a
Class Code: 0x30400

The details view of this entry contains further information.
 
 
x1000's when I play BF4.  I hate when fresh installs of Windows aren't perfect b/c of hardware.  The whole Haswell-Xeon platform has been sampled for 18 months...did no one bother to check on SLI with Win 7?


Getting the same issue here with an SR-X but no BIOS update around for now

My Affiliate Code: GL1IAAFWJF
#55
Bepzinky
iCX Member
  • Total Posts : 281
  • Reward points : 0
  • Joined: 2016/04/30 13:15:31
  • Status: offline
  • Ribbons : 2
Re: Whea-Logger Event ID: 17 x99 Classified PCIE 3.0 2020/07/14 11:17:05 (permalink)
Sorry to dig up this old thread but almost 10 years after release of the SR board, it still happens.
I mean guys, bloody hell...both SR2 and SRX show the EXACT SAME behaviour, corrected WHEA on PCI-E.
No driver or BIOS updates seem to fix it, I've already tried disabling peripherals and with both AMD and Nvidia cards. The PCI-E power link management is set do disabled by default in BIOS.
 
Lenovo even states s...w it: https://support.lenovo.com/nl/en/solutions/ht500599
post edited by Bepzinky - 2020/07/15 16:08:55
#56
Page: < 12 Showing page 2 of 2
Jump to:
  • Back to Mobile