Unsolved
This post is more than 5 years old
2 Posts
0
2044
February 27th, 2018 22:00
LED error codes ? XPS 1530
HI guys, i'll be quick.
I'm trying to restore some notebooks and give them to people in need.
I have boot problems with XPS1530, blank screen , no backlit, nothing happens when power on , except laptop itself is ON, but nothing on screen.
I preformed D + POWER test, screen is OK, show colors and backlit i s OK.
I performed Fn + POWER test, NO beeps, and the 3 LEDs are :
NUM-blink | CAPS-solid | SCR-solid
Any Advice about that errr code ?
0 events found
No Events found!
Wiklen
1 Rookie
•
29 Posts
0
February 27th, 2018 22:00
Is this an XPS 1530 or M1530? I can't find anything about a 1530. Seems to not exist. I couldn't find an error code list for the M1530 model on Dell's website. I got some results from a Google search. For an M1530 the error code you're seeing indicates a problem with the CPU. Dell suggests reseating the processor, replacing the system board, or replacing the processor.
BlazeBG
2 Posts
0
February 28th, 2018 01:00
I can't believe you ask me if it's XPS or M !!! Are you OK ? Did you read the title and post ?
ejn63
12 Elder
•
30.9K Posts
•
153.6K Points
0
February 28th, 2018 05:00
With an M1530, overwhelming odds with these symptoms are that the GPU has failed - the mainboard needs replacement.
speedstep
11 Legend
•
47K Posts
0
February 28th, 2018 05:00
Remove all ram all batteries including the coin cell and reserve batteries.
Then put Ram back and power on
What happens?
Wiklen
1 Rookie
•
29 Posts
0
February 28th, 2018 20:00
Relax. I read the title and post. I explained I can't find an XPS 1530 on Dell's website (I went looking for error LED codes for you) but I can find an XPS M1530 on Dell's website so I asked if that's what you have. I though maybe you accidentally left the 'M' out of the model number. However, after some more Googling I saw that others have asked about their XPS 1530 so I guess it is a real model number. I'm not sure why Dell doesn't have it listed. I did find this thread started by someone in 2011 who had the same issue.