The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    T510 - PCI System Error Bus/Device/Function 00F0h

    Discussion in 'Lenovo' started by oct, Nov 12, 2011.

  1. oct

    oct Notebook Evangelist

    Reputations:
    116
    Messages:
    402
    Likes Received:
    15
    Trophy Points:
    31
    Hey guys,

    Getting subj error on my wife's T510, any hint what can I check? All i can tell it got much hotter before freezing and after restart started to get this...

    However Windows 7 is starting fine, seems at least... I tried to google but nothing close could be found..

    Thank you in advance.

    PS: Never had any issues before, for at least 1 year...
     
  2. oct

    oct Notebook Evangelist

    Reputations:
    116
    Messages:
    402
    Likes Received:
    15
    Trophy Points:
    31
    Bump.

    Now it doesn't start at all... after pressing power button screen is blank... so, system board is fried?

    This sucks... $1K for one year of usage... deep disappointment.
     
  3. ZaZ

    ZaZ Super Model Super Moderator

    Reputations:
    4,982
    Messages:
    34,001
    Likes Received:
    1,415
    Trophy Points:
    581
    Pull the battery, hard drive, memory, optical drive and wifi card. Hit the power button 10 times for a second, then once again for 30 seconds. Plug the AC in and hit the power button. If the board doesn't beep, it's most likely dead. If it does, try replacing things one at a time to see if you can find the culprit. Good Luck.
     
  4. oct

    oct Notebook Evangelist

    Reputations:
    116
    Messages:
    402
    Likes Received:
    15
    Trophy Points:
    31
    Ha! Thanks a lot! Looks like it may be the Wi-Fi...

    I took everything out and got those beeps. Putting them back one by one.. showed it may be the Wi-Fi... though initially I just disconnected it. The 00f0h error disappeared...too!

    Now, I'll let it run for a while without wifi and see how it goes...

    Thanks again!
     
  5. oct

    oct Notebook Evangelist

    Reputations:
    116
    Messages:
    402
    Likes Received:
    15
    Trophy Points:
    31
    Error came back, though it's much stable without Wi-Fi card.

    I'll try to take them out and put back again...

    Btw, what does 10 times + 1 x 30 sec press do? Does it reset any errors or what?

    Thanks.
     
  6. ZaZ

    ZaZ Super Model Super Moderator

    Reputations:
    4,982
    Messages:
    34,001
    Likes Received:
    1,415
    Trophy Points:
    581
    Static discharge.
     
  7. oct

    oct Notebook Evangelist

    Reputations:
    116
    Messages:
    402
    Likes Received:
    15
    Trophy Points:
    31
    Thanks!

    So, at this point I have following:

    - put wi-fi adapter back and changed RAM(just to make sure)
    - no subj error so far
    - i replaced CPU/GPU thermal paste
    - laptop would start fine on cold start only
    - if it gets to windows, it works fine
    - I performed some CPU crash test for an hour and temperature did not get passed 55C, which is nice, but not sure if it's normal..

    Now the problem starts when I'm doing a simple restart. During it I get a blank screen, it's right before Thinkpad logo is displayed. Sometimes it will display it, but it hangs there. F1 won't get me into BIOS... if I turn it off and leave for a while it works fine again...

    Now, I wonder if I messed up something with thermal paste, though the CPU test I mentioned earlier passed OK, i think.

    PS: Cpu is i5-540m
     
  8. ZaZ

    ZaZ Super Model Super Moderator

    Reputations:
    4,982
    Messages:
    34,001
    Likes Received:
    1,415
    Trophy Points:
    581
    You could run memtest on the memory to rule that out.