Windows 10 Random BSOD 'Whea Uncorrectable error'

[jnelsoninjax]

This is a relatively new install of the OS (8/10)) and without fail at least one time during the day I get the BSOD Whea Uncorrectable error.

Quote

On Fri 8/26/2016 01:00:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082516-10937-01.dmp
This was probably caused by the following module: hal.dll (hal+0x3620F)
Bugcheck code: 0x124 (0x0, 0xFFFFC402630C8028, 0xB0800000, 0x40151)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

It happens when the system is idle, it happens in the middle of games, it happens in the middle of watching video, but always the same exact error. I have run SFC and DISM and both report nothing, I have run SDI (Snappy driver installer) and checked to see if any drivers are outdated, currently only showing Bluetooth drivers, has shown Realtek in the past, but each time I have updated the drivers, the issue persists. I have of course checked for virus/malware just as a precaution with no trouble. Am I missing something here, or is this something that is just completely random and can't be fixed.

My system:

Operating System
            Windows 10 Pro 64-bit
        CPU
            AMD FX-8370    26 °C
            Vishera 32nm Technology
        RAM
            16.0GB Dual-Channel DDR3 @ 802MHz (11-11-11-28)
        Motherboard
            ASUSTeK COMPUTER INC. M5A97 R2.0 (Socket 942)    31 °C
        Graphics
            4K2K@60HzDP (3840x2160@60Hz)
            4095MB NVIDIA GeForce GTX 1080 (Asus)    54 °C
        Storage
            232GB Samsung SSD 850 EVO 250GB (SSD)    36 °C
            232GB Samsung SSD 850 EVO 250GB (SSD)    33 °C
            232GB Seagate ST3250410AS (SATA)    37 °C
            465GB Seagate ST3500630AS (SATA)    39 °C
            2794GB Seagate ST3000DM001-9YN166 (SATA)    34 °C
            1862GB Western Digital WD My Book 1230 USB Device (SSD)    36 °C
            931GB Western Digital WDC WD10 EADS-65M2B0 USB Device (SSD)    36 °C
              Optical Drives
            HL-DT-ST BD-RE WH14NS40
        Audio
            Realtek High Definition Audio
 

[Hum]

Is this the Anniversary edition ?

 

Perhaps roll back.

 

If this is an Upgrade from 8.x I would Save personal files, zero-out the drive, and do a clean Install of Windows 10.

 

Free download from Microsoft.

 

There is a tool to record your Product Key:

 

 

 

Edited August 26, 2016 by Hum

[Eric Veteran]

Did you run the dump file through something like BlueScreenView? It should tell you where in the HAL it's failing.

[jnelsoninjax]

13 minutes ago, Eric said:

Did you run the dump file through something like BlueScreenView? It should tell you where in the HAL it's failing.

 

@Eric, Bluescreenview is giving me a little more info: The most recent crash which was today was caused by hal.dll and ntoskrnl.exe the previous 2 were just caused by ntoskrnl.exe - any idea what this means?

I had previously used WhoCrashed for my info, but I see that it does not give all the details that might be useful!

Edited August 26, 2016 by jnelsoninjax
Added the screen caps

[jnelsoninjax]

30 minutes ago, Hum said:

Is this the Anniversary edition ?

 

Perhaps roll back.

 

If this is an Upgrade from 8.x I would Save personal files, zero-out the drive, and do a clean Install of Windows 10.

 

Free download from Microsoft.

 

There is a tool to record your Product Key:

 

 

 

Yes @Hum, this is a clean Windows 10 with AU install from an ISO downloaded directly from MS so a rollback is not possible in this scenario. 

[Hum]

1 minute ago, jnelsoninjax said:

Yes @Hum, this is a clean Windows 10 with AU install from an ISO downloaded directly from MS  so a rollback is not possible in this scenario. 

I've read numerous problems with W10 AU.

 

I had several problems with AU.

 

I think you will end up reinstalling regular Windows 10.

 

But good luck finding a solution besides a reinstall.

[+Warwagon MVC]

download crystal disk and let us know what the health of your hard drive is

 

http://crystalmark.info/software/CrystalDiskInfo/index-e.html

 

How is the cooler on your graphics card operating? Is it dusty. Maybe your video card is overheating. Do you have onboard video you could run off of for a while?

 

Although your video card looks temp looks good in that listing.

 

Have you memtested your memory?

 

could also be a possible issue with the PSU.

[Hum]

Troubleshoot blue screen errors

 

https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors

[+Warwagon MVC]

4 minutes ago, Hum said:

Troubleshoot blue screen errors

 

https://support.microsoft.com/en-us/help/14238/windows-10-troubleshoot-blue-screen-errors

Well .. for his case, that page just told him to check for windows updates and remove new hardware.

 

Which I guess that video card is pretty new.

[Hum]

Uncoorrectable Error suggests bad hardware.

 

https://msdn.microsoft.com/en-us/library/windows/hardware/ff557321(v=vs.85).aspx

 

The WHEA_UNCORRECTABLE_ERROR bug check has a value of 0x00000124. This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).

 

I would Reseat the RAM chips and run Memory Diagnostics.

 

Reseat video card as well.

 

Check drive cables for tightness.

Edited August 26, 2016 by Hum

[jnelsoninjax]

8 hours ago, warwagon said:

download crystal disk and let us know what the health of your hard drive is

 

http://crystalmark.info/software/CrystalDiskInfo/index-e.html

 

How is the cooler on your graphics card operating? Is it dusty. Maybe your video card is overheating. Do you have onboard video you could run off of for a while?

 

Although your video card looks temp looks good in that listing.

 

Have you memtested your memory?

 

could also be a possible issue with the PSU.

OK, dust not an issue, just cleaned it out ~2 weeks ago and do so at least monthly.

Memory - have not run a memtest, but find it highly unlikely that it's failing as it's ~1 year old.

No onboard video, only the Nvida.

PSU, again I suppose anything is possible, but I feel that I would be seeing allot more issues then a random BSOD if the PSU were failing.

 

Here is the CrystalDiskInfo: the drive(s) that are showing caution, one just has videos on it and is located on an external dock, the other is the drive that I download to, so neither one are critical.

 

Quote

 

----------------------------------------------------------------------------
CrystalDiskInfo 6.7.5 (C) 2008-2016 hiyohiyo
                                Crystal Dew World : http://crystalmark.info/
----------------------------------------------------------------------------

    OS : Windows 10 Professional [10.0 Build 14393] (x64)
  Date : 2016/08/26 7:56:27

-- Controller Map ----------------------------------------------------------
 + Standard SATA AHCI Controller [ATA]
   - Samsung SSD 850 EVO 250GB
   - Samsung SSD 850 EVO 250GB
   - ST3250410AS
   - ST3500630AS
   - ST3000DM001-9YN166
   - HL-DT-ST BD-RE  WH14NS40
 - Microsoft Storage Spaces Controller [SCSI]
 + Covecube Cloud Disk Enumerator [SCSI]
   - Covecube Virtual Disk

-- Disk List ---------------------------------------------------------------
 (1) Samsung SSD 850 EVO 250GB : 250.0 GB [0/0/0, pd1] - sg
 (2) Samsung SSD 850 EVO 250GB : 250.0 GB [1/0/0, pd1] - sg
 (3) ST3250410AS : 250.0 GB [2/0/0, pd1] - st
 (4) ST3500630AS : 500.1 GB [3/0/0, pd1] - st
 (5) ST3000DM001-9YN166 : 3000.5 GB [4/0/0, pd1] - st
 (6) WDC WD20EZRX-00D8PB0 : 2000.3 GB [5/0/0, sa1] - wd
 (7) WDC WD10EADS-65M2B0 : 1000.2 GB [6/0/0, sa1] - wd

----------------------------------------------------------------------------
 (1) Samsung SSD 850 EVO 250GB
----------------------------------------------------------------------------
           Model : Samsung SSD 850 EVO 250GB
        Firmware : EMT02B6Q
   Serial Number : S21NNXBGA15769Y
       Disk Size : 250.0 GB (8.4/137.4/250.0/250.0)
     Buffer Size : Unknown
     Queue Depth : 32
    # of Sectors : 488397168
   Rotation Rate : ---- (SSD)
       Interface : Serial ATA
   Major Version : ACS-2
   Minor Version : ATA8-ACS version 4c
   Transfer Mode : SATA/600 | SATA/600
  Power On Hours : 5020 hours
  Power On Count : 55 count
     Host Writes : 3307 GB
Wear Level Count : 16
     Temperature : 35 C (95 F)
   Health Status : Good (100 %)
        Features : S.M.A.R.T., 48bit LBA, NCQ, TRIM, DevSleep
       APM Level : ----
       AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
05 100 100 _10 000000000000 Reallocated Sector Count
09 _99 _99 __0 00000000139C Power-on Hours
0C _99 _99 __0 000000000037 Power-on Count
B1 _99 _99 __0 000000000010 Wear Leveling Count
B3 100 100 _10 000000000000 Used Reserved Block Count (Total)
B5 100 100 _10 000000000000 Program Fail Count (Total)
B6 100 100 _10 000000000000 Erase Fail Count (Total)
B7 100 100 _10 000000000000 Runtime Bad Block (Total)
BB 100 100 __0 000000000000 Uncorrectable Error Count
BE _65 _56 __0 000000000023 Airflow Temperature
C3 200 200 __0 000000000000 ECC Error Rate
C7 100 100 __0 000000000000 CRC Error Count
EB _99 _99 __0 000000000017 POR Recovery Count
F1 _99 _99 __0 00019D7BB2E8 Total LBAs Written

 

---------------------------------------------------------------------------

 (2) Samsung SSD 850 EVO 250GB
----------------------------------------------------------------------------
           Model : Samsung SSD 850 EVO 250GB
        Firmware : EMT02B6Q
   Serial Number : S21NNXBGA15668D
       Disk Size : 250.0 GB (8.4/137.4/250.0/250.0)
     Buffer Size : Unknown
     Queue Depth : 32
    # of Sectors : 488397168
   Rotation Rate : ---- (SSD)
       Interface : Serial ATA
   Major Version : ACS-2
   Minor Version : ATA8-ACS version 4c
   Transfer Mode : SATA/600 | SATA/600
  Power On Hours : 5019 hours
  Power On Count : 57 count
     Host Writes : 1382 GB
Wear Level Count : 7
     Temperature : 34 C (93 F)
   Health Status : Good (100 %)
        Features : S.M.A.R.T., 48bit LBA, NCQ, TRIM, DevSleep
       APM Level : ----
       AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
05 100 100 _10 000000000000 Reallocated Sector Count
09 _99 _99 __0 00000000139B Power-on Hours
0C _99 _99 __0 000000000039 Power-on Count
B1 _99 _99 __0 000000000007 Wear Leveling Count
B3 100 100 _10 000000000000 Used Reserved Block Count (Total)
B5 100 100 _10 000000000000 Program Fail Count (Total)
B6 100 100 _10 000000000000 Erase Fail Count (Total)
B7 100 100 _10 000000000000 Runtime Bad Block (Total)
BB 100 100 __0 000000000000 Uncorrectable Error Count
BE _66 _45 __0 000000000022 Airflow Temperature
C3 200 200 __0 000000000000 ECC Error Rate
C7 100 100 __0 000000000000 CRC Error Count
EB _99 _99 __0 00000000001B POR Recovery Count
F1 _99 _99 __0 0000ACC6D09D Total LBAs Written

----------------------------------------------------------------------------

 (3) ST3250410AS
----------------------------------------------------------------------------
           Model : ST3250410AS
        Firmware : 4.AAA
   Serial Number : 6RYJWB3E
       Disk Size : 250.0 GB (8.4/137.4/250.0/250.0)
     Buffer Size : 16384 KB
     Queue Depth : 32
    # of Sectors : 488397168
   Rotation Rate : Unknown
       Interface : Serial ATA
   Major Version : ATA/ATAPI-7
   Minor Version : ----
   Transfer Mode : ---- | SATA/300
  Power On Hours : 44099 hours
  Power On Count : 903 count
     Temperature : 38 C (100 F)
   Health Status : Good
        Features : S.M.A.R.T., 48bit LBA, NCQ
       APM Level : ----
       AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 100 253 __6 000000000000 Read Error Rate
03 _98 _97 __0 000000000000 Spin-Up Time
04 _99 _99 _20 000000000445 Start/Stop Count
05 100 100 _36 000000000000 Reallocated Sectors Count
07 _84 _60 _30 00022234D1A0 Seek Error Rate
09 _50 _50 __0 00000000AC43 Power-On Hours
0A 100 100 _97 000000000000 Spin Retry Count
0C 100 100 _20 000000000387 Power Cycle Count
BB 100 100 __0 000000000000 Reported Uncorrectable Errors
BD 100 100 __0 000000000000 High Fly Writes
BE _62 _47 _45 0000350F0026 Airflow Temperature
C2 _38 _53 __0 000F00000026 Temperature
C3 _62 _55 __0 00000C64D071 Hardware ECC recovered
C5 100 100 __0 000000000000 Current Pending Sector Count
C6 100 100 __0 000000000000 Uncorrectable Sector Count
C7 200 175 __0 000000000323 UltraDMA CRC Error Count
C8 100 253 __0 000000000000 Write Error Rate
CA 100 253 __0 000000000000 Data Address Mark Error

----------------------------------------------------------------------------

 (4) ST3500630AS
----------------------------------------------------------------------------
           Model : ST3500630AS
        Firmware : 3.AAK
   Serial Number : 9QG0CY9Z
       Disk Size : 500.1 GB (8.4/137.4/500.1/500.1)
     Buffer Size : 16384 KB
     Queue Depth : 32
    # of Sectors : 976773168
   Rotation Rate : Unknown
       Interface : Serial ATA
   Major Version : ATA/ATAPI-7
   Minor Version : ----
   Transfer Mode : ---- | SATA/150
  Power On Hours : 53749 hours
  Power On Count : 5050 count
     Temperature : 40 C (104 F)
   Health Status : Caution
        Features : S.M.A.R.T., 48bit LBA, NCQ
       APM Level : ----
       AAM Level : ----

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 118 _82 __6 00000A5A2443 Read Error Rate
03 _95 _92 __0 000000000000 Spin-Up Time
04 _94 _94 _20 000000001B57 Start/Stop Count
05 100 100 _36 000000000000 Reallocated Sectors Count
07 _53 _51 _30 0C9F28840F07 Seek Error Rate
09 _39 _39 __0 00000000D1F5 Power-On Hours
0A 100 100 _97 000000000000 Spin Retry Count
0C _96 _96 _20 0000000013BA Power Cycle Count
BB 100 100 __0 000000000000 Reported Uncorrectable Errors
BD 100 100 __0 000000000000 High Fly Writes
BE _60 _29 _45 4DE12A270028 Airflow Temperature
C2 _40 _71 __0 001000000028 Temperature
C3 _63 _48 __0 000009B71B4D Hardware ECC recovered
C5 100 100 __0 000000000002 Current Pending Sector Count
C6 100 100 __0 000000000002 Uncorrectable Sector Count
C7 200 __1 __0 0000000149F5 UltraDMA CRC Error Count
C8 100 253 __0 000000000000 Write Error Rate
CA 100 253 __0 000000000000 Data Address Mark Error

 

 (7) WDC WD10EADS-65M2B0
----------------------------------------------------------------------------
       Enclosure : WDC WD10 EADS-65M2B0 USB Device (V=8882, P=009D, sa1) - wd
           Model : WDC WD10EADS-65M2B0
        Firmware : 01.00A01
   Serial Number : WD-WCAV53148636
       Disk Size : 1000.2 GB (8.4/137.4/1000.2/1000.2)
     Buffer Size : 32767 KB
     Queue Depth : 32
    # of Sectors : 1953525168
   Rotation Rate : Unknown
       Interface : USB (Serial ATA)
   Major Version : ATA8-ACS
   Minor Version : ----
   Transfer Mode : ---- | SATA/300
  Power On Hours : 31841 hours
  Power On Count : 2511 count
     Temperature : 33 C (91 F)
   Health Status : Caution
        Features : S.M.A.R.T., AAM, 48bit LBA, NCQ
       APM Level : ----
       AAM Level : 8080h [OFF]

-- S.M.A.R.T. --------------------------------------------------------------
ID Cur Wor Thr RawValues(6) Attribute Name
01 200 _98 _51 000000025995 Read Error Rate
03 122 106 _21 000000001ACA Spin-Up Time
04 _96 _96 __0 0000000011D9 Start/Stop Count
05 200 200 140 000000000000 Reallocated Sectors Count
07 100 253 __0 000000000000 Seek Error Rate
09 _57 _57 __0 000000007C61 Power-On Hours
0A 100 100 __0 000000000000 Spin Retry Count
0B 100 100 __0 000000000000 Recalibration Retries
0C _98 _98 __0 0000000009CF Power Cycle Count
C0 198 198 __0 0000000008C9 Power-off Retract Count
C1 _95 _95 __0 00000004D42E Load/Unload Cycle Count
C2 114 _93 __0 000000000021 Temperature
C4 200 200 __0 000000000000 Reallocation Event Count
C5 198 196 __0 0000000001AE Current Pending Sector Count
C6 200 196 __0 000000000019 Uncorrectable Sector Count
C7 200 200 __0 000000000378 UltraDMA CRC Error Count
C8 196 182 __0 0000000003AC Write Error Rate

 

 

[Hum]

Quote

Memory - have not run a memtest, but find it highly unlikely that it's failing as it's ~1 year old.

I know RAM can be improperly seated -- it will function most of the time, then cause a hardware error.

 

I have had RAM test out as 'bad' until I took it out and put it back in, more securely.

 

It doesn't take long for Windows Memory Diagnostic to check the RAM.

 

The test will show  either unseated RAM or if it is bad.

 

Somewhere, you probably have either a bad connection to the hardware, or some hardware component is actually defective.

 

Again, I would test the RAM, reseat it if it shows as bad.

 

Reseat the video card.

 

Check the drive connections.

 

Maybe this will help:

 

http://www.makeuseof.com/tag/how-to-test-your-pc-for-failing-hardware/

 

 

[+Gary7 Subscriber²]

I would look at your video card drivers. I used to get that same BSOD till I got an EVGA 1060. Get in the fast Ring and live fast..

[atcapistrano]

turn off computer, remove sata cable for the Seagate 3TB hdd, turn on computer, and check if the WHEA error disappears...

(do the same for the 2TB wd hdd)

[jnelsoninjax]

4 hours ago, atcapistrano said:

turn off computer, remove sata cable for the Seagate 3TB hdd, turn on computer, and check if the WHEA error disappears...

(do the same for the 2TB wd hdd)

The 2TB wd is an external, the other 2 is sitting in an external dock.

[Circaflex]

7 hours ago, Gary7 said:

Get in the fast Ring and live fast..

That is some of the worst advice given. Why would you install a pre-production OS on a machine with some sort of error. That makes no sense and is not a proper way to troubleshoot.

 

 

OP, we need to narrow down what is causing the BSOD. When you analyzed the dump, did it mention what file caused the BSOD or the driver?

 

I would run memtest on the computer to verify the RAM.

 

I would run the hard-drive OEM's diagnostic tools to verify your hard-drive is ok, I like these more than third party tools like crystal disk

 

I would also try and run sfc /scannow. If there are errors, you need to rebuilt the image health and run sfc again.

[+Gary7 Subscriber²]

29 minutes ago, Circaflex said:

That is some of the worst advice given. Why would you install a pre-production OS on a machine with some sort of error. That makes no sense and is not a proper way to troubleshoot.

 

 

OP, we need to narrow down what is causing the BSOD. When you analyzed the dump, did it mention what file caused the BSOD or the driver?

 

I would run memtest on the computer to verify the RAM.

 

I would run the hard-drive OEM's diagnostic tools to verify your hard-drive is ok, I like these more than third party tools like crystal disk

 

I would also try and run sfc /scannow. If there are errors, you need to rebuilt the image health and run sfc again.

You would not know sarcasm if hit hit you in the face. I had the same BSOD and I still am on a Pre Production OS 14905. The problem was already taken care of before I posted. First you say I am weird and then you post this, do yourself and me a favor and put me on ignore--Please.

[Jim K Global Moderator]

I didn't see it mentioned ... but OP ... is anything overclocked (to include memory)?  I would run everything on "Auto" (like CPU voltage)...and see if the WHEA returns.  Do you have the latest BIOS?  I'm not confident this is a driver issue ... but instead is a hardware issue.  Anyway...disable what you don't need and have everything else run at stock....see what happens.

[Pork Chopper]

I get WHEA errors (usually correctable) in my event log when I overclock my CPU but my Vcore isn't high enough.  Have you increased your CPU clock without increasing your vcore?

[Circaflex]

37 minutes ago, Gary7 said:

You would not know sarcasm if hit hit you in the face. I had the same BSOD and I still am on a Pre Production OS 14905. The problem was already taken care of before I posted. First you say I am weird and then you post this, do yourself and me a favor and put me on ignore--Please.

Right. If you do not like my reply, you are free to add me to ignore, but I will quote and reply to whom I want on this forum.

[jnelsoninjax]

3 hours ago, Circaflex said:

That is some of the worst advice given. Why would you install a pre-production OS on a machine with some sort of error. That makes no sense and is not a proper way to troubleshoot.

 

 

OP, we need to narrow down what is causing the BSOD. When you analyzed the dump, did it mention what file caused the BSOD or the driver?

 

I would run memtest on the computer to verify the RAM.

 

I would run the hard-drive OEM's diagnostic tools to verify your hard-drive is ok, I like these more than third party tools like crystal disk

 

I would also try and run sfc /scannow. If there are errors, you need to rebuilt the image health and run sfc again.

I have run memtest as well as the OEM hard drive software, nothing reported wrong.

3 hours ago, jjkusaf said:

I didn't see it mentioned ... but OP ... is anything overclocked (to include memory)?  I would run everything on "Auto" (like CPU voltage)...and see if the WHEA returns.  Do you have the latest BIOS?  I'm not confident this is a driver issue ... but instead is a hardware issue.  Anyway...disable what you don't need and have everything else run at stock....see what happens.

Not OC. Everything is stock

3 hours ago, Pork Chopper said:

I get WHEA errors (usually correctable) in my event log when I overclock my CPU but my Vcore isn't high enough.  Have you increased your CPU clock without increasing your vcore?

Again, I am not OC.

This issue did not present itself until after the AU, and the installation of the 1080 GPU, so I am led to believe the issue is either the GPU (driver most likely) or something in Windows, at this point I do not suspect any type of hardware failure. I unfortunately do not have the old GPU that I replaced with the 1080 to do any type of troubleshooting with the GPU.   

[atcapistrano]

4 hours ago, jnelsoninjax said:

The 2TB wd is an external, the other 2 is sitting in an external dock.

Quote

2794GB Seagate ST3000DM001-9YN166 (SATA)    34 °C
1862GB Western Digital WD My Book 1230 USB Device (SSD)    36 °C
931GB Western Digital WDC WD10 EADS-65M2B0 USB Device (SSD)    36 °C

I failed to see the WD hdds as usb device but how about the Seagate 3TB marked as sata device in your previous post?

 

I raised this possible cause because I have two failed/dead Seagate 3TB hdd under windows 7 home premium 64bit, separate desktop pc. symptoms in my case include (a) inability to boot the machines though the drives are not system drives, (b) random bsod (I failed to record exact bsod code). removal of the failed/dead Seagate hdds fixed the no boot problem and the random bsod.

 

I suggest to try to remove the external drives before you power up the pc and see what happens. as they say in troubleshooting, remove non-essential usb devices first and then test one component at a time...