1 Rookie
•
2 Posts
2
12354
August 23rd, 2022 15:00
SupportAssist error code D0702
Latitude 3400
I keep having error code D0702 whenever I run Support Assist Hardware Scan manually. I've done this today with either Ethernet enabled and active or with wireless enabled and active and with Airplane mode disabled. Usually I just re-scan with out any settings changes and the error miraculously disappears. Today I've done 5 scans and all return this error. Is this a problem with numerous bloatware that came with the laptop?
No Events found!



XPS_Man
5 Practitioner
•
2.4K Posts
3
August 23rd, 2022 17:00
NOPES this is an issue with SupportAssist's latest built.
I have a case with their level 3 team and they have confirmed these false error messages will go away after next release of version 3.12
Until than you should ignore these errors and do hardware checks via F12 > Daignostics
But Why Dell
8 Posts
0
October 30th, 2022 19:00
I am on SupportAssist 3.12.3.5. Still shows DO702 and D0605 errors. These errors seem to come and go and I am unable to resolve. So in summary, I suggest 3.12 did not fix these false positives.
AdrianG001
4 Operator
•
4K Posts
0
October 31st, 2022 03:00
This sounds like a hardware fail which would be on the MB. Run diagnostics one more time (tap F12 immediately at boot) and watch for additional error codes. This MS forum page may help though a bit lengthy. Since you are under warranty I would also suggest calling Dell tech support if the above does not help.
But Why Dell
8 Posts
0
October 31st, 2022 22:00
Thanks Adrian. I ran the F12 advanced diagnostics, the only error returned was that it didn't recognise my battery charger (long standing issue).
However, once I ran the Dell SupportAssist diagnosis again after the F12 diagnosis, the D0702 and D0605 errors did not return, so I guess that is good.
The Support Assist diagnosis showed nil errors ... though to note, it also didn't pick up the ongoing on/off battery recharger issues I have been having for the last 6 months (I just work around that now as discussed earlier).
Yassin Mahgoub
1 Message
2
July 3rd, 2023 14:00
I have run the f12 diagnostics and it showed no errors. However, when I tried to run the SupportAssist app I still get the the D0702 error knowing that I have version 3.14.0.91 of the assist app. So what should I do?
labia
1 Message
2
July 16th, 2023 18:00
same problem
ispalten
4 Operator
•
2.5K Posts
3
August 5th, 2023 16:00
I'm on 3.14.0.91 as well, same problems:
F12 passes all tests. So I re-ran the H/W test, same results.
Same result last month too:
I have never seen any errors or operational problems with PCI bus or Network wireless card.
I do wonder what that error for the Network card is though? It is the Intel one that is both wired and wireless capable. I do use only the wireless, however there IS a wired connection I can use, but it is Disabled unless I want to use wired vs. wireless connection. Could explain the Network card error, but not the PCI one.
I should also mention I am on an XPS 8940.
Dave877
2 Posts
2
December 9th, 2023 16:31
@ispalten I'm on version 3.14.13.0 of SupportAssist. The D0702 error first appeared this week. I have no serious functional problems with my XPS 8910. It's irritating to get an error code when there might not be an error.
Downed_Aviator
1 Message
0
December 29th, 2023 14:42
@Dave877 I have this problem with Version: 3.14.2.45116 on Alienware Aurora r13
(edited)
Skwish
3 Posts
0
February 27th, 2024 17:37
@Downed_Aviator Same, except on Alien Aurora R9. Nearly had a heart attack.
Chuck-A-B
1 Rookie
•
2 Posts
1
March 21st, 2024 19:41
@XPS_Man Sorry but I have version 4.0.0.51819 and I received a cpuple of these errors:
PCI Status - Fail
Error Code List
- PCI Status Tests - D0702
- Network Card - Fail
Error Code3 List
- PCI Status Tests - D0702
I don't get these messages when running the diagnostics from the BIOS.
XPS_Man
5 Practitioner
•
2.4K Posts
0
March 22nd, 2024 11:26
@Chuck-A-B
Version 4.0 is full of bugs and they have pulled in back
If you uninstall 4.0 and reinstall it, you will get 3.14
D0702 this is a very old bug, they fixed it for most of the machines, but it still comes now n then