CPU ez boot error
Solved/Closed
Emag_7887
Posts
3
Registration date
Thursday February 28, 2019
Status
Member
Last seen
March 1, 2019
-
Feb 28, 2019 at 02:09 PM
Blocked Profile - Mar 12, 2019 at 01:42 PM
Blocked Profile - Mar 12, 2019 at 01:42 PM
Related:
- Msi ez debug led boot no display
- Ez debug led cpu - Best answers
- Ez debug led boot - Best answers
- Boot camp download - Download - Security and maintenance
- Msi app player - Download - Android emulators
- How to open .msi file - Guide
- Hiren boot cd 17.2 iso download - Download - Backup and recovery
- 3 beeps on startup no display ✓ - CPU & Desktop Forum
2 responses
Ok problem solved.
After more investigation of stripping down the casing for the on - off switch and USB 3.0 I found the cables twisted badly together, I know this shouldn't make a difference with them both having protective insulation covering the wire but when I seperated the power button cable from the USB cable and then booted up there was no problem.
I built the casing back up making sure the cables went in different paths and did not touch and rebooted again no problem.
I connected the keyboard to the USB 3.0 to see if that trigger a reset as it had sometimes in the past, no problems now.
It has now been a couple of weeks and no more problems have occurred so the cables somehow must have been contaminating each other.
PROBLEM SOLVED
After more investigation of stripping down the casing for the on - off switch and USB 3.0 I found the cables twisted badly together, I know this shouldn't make a difference with them both having protective insulation covering the wire but when I seperated the power button cable from the USB cable and then booted up there was no problem.
I built the casing back up making sure the cables went in different paths and did not touch and rebooted again no problem.
I connected the keyboard to the USB 3.0 to see if that trigger a reset as it had sometimes in the past, no problems now.
It has now been a couple of weeks and no more problems have occurred so the cables somehow must have been contaminating each other.
PROBLEM SOLVED
Mar 12, 2019 at 01:42 PM