Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

How do I use this device?

  • Designed to troubleshoot PC boot failures, when PC doesn't even show Video Card/BIOS screen (thus no error code/info is available)
  • 4-digit numeric display for detailed diagnostic code
  • With USB interface
  • Plug-and-play
  • Comes with power cable & Chinese manual
share|improve this question
3  
Looks like the first step will be to learn Chinese in order to read the manual... –  Mokubai Jul 23 '11 at 9:07
    
There is really not much to using them. You just plug them in and the look up the code that is displayed in a table that explains the meaning of the code. The codes used are not some "universal error code" and may differ by manufacturer. But, "Plug-and-Play" is, of course, a Windows function. It implies to me that it needs drivers and Windows. But it could simply be a mistake in denotation by a translator. –  Abraxas Jul 23 '11 at 9:55

1 Answer 1

up vote 3 down vote accepted

Many motherboards put one or more progress/status codes in a specific memory locations while they are running their diagnotics and these devices read those values and display them. The idea is that on a faulty unit that can't even get as far as driving a display you can use the supplied information (and sometimes the data supplied by the motherboard or computer manufacturer) to get an indication of which component has failed.

Under most circumstances, these failure codes refer to individual chips or sub-components (eg: keyboard controller failure or stuck interrupt line x) and so although you can perhaps see why a board has failed you are not likely to be able to fix the fault without some specialist board repairing and reworking tools.

share|improve this answer
    
It only shows onboard failed components? Not video card, processor, memory etc.? –  Boris_yo Jul 24 '11 at 20:56
    
Only the results of the onboard tests - you may get some indication of faults in certain areas you mention but only for the interfaces to those bits - for example, memory controller error or stuck address line - but no in-depth testing of CPU or RAM. –  Linker3000 Jul 25 '11 at 20:59

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.