Toggle sidebar

no post msi z370 a pro with i57600k cpu light constant

  • Thread starter Thread starter Immy
  • Start date Start date
  • Views Views 602
  • Replies Replies 10
I

Immy

Active Member
Newcomer
Level 2
Joined
Oct 27, 2020
Messages
29
Reaction score
7
Trophies
0
XP
173
Country
United Kingdom
hey everyone ive got a real headache here! this board will power on but i cant get it to post. it will power on and all the fans spin but no post.

ive done all the standard troubleshooting, stripped everything and just kept cpu and memory, different sticks of memory and slots. cleared cmos and battery changed.

the cpu error light on the mobo is constantly lit. i dont have another working cpu to test with.

A little background
initially my customer had another board and cpu in this case, and all of a sudden the cooler mounting became loose and im fairly sure the cpu overheated and cooked itself (that was a different board to the one im currently working on). but the issues with that one was when i had all atx and cpu (8x) cables connected it wouldn't power on but with the cpu power disconnected it would power on and off constantly.

with the current system the only thing thats the same is the cooler and memory and the gpu but that's disconnected

really hope someone knows what i should look at next as im totally lost.

i was thinking about removing bios and reprogramming it but this board used to work fine so im not sure of that's necessary
 
Immy said:
no ideas anyone???

aslso mobo does not complain when no memory is installed
Click to expand...
Uh... CMOS dead?
Corrupted BIOS?

Have you checked the BIOS is fine?
Post automatically merged:

Does it actually reaches the Desktop though?
If it's a GPU issue it should at least output video through whatever port is not GPU (vga, hdmi, dvi, dp, whatever).

Then it'd explain why with GPU there's constant light but apparently not video.

If not, try to go to BIOS upon boot.
Some BIOS has Hardware/Software checks report, might output what's wrong.

If you can't even reach BIOS (sounds unlikely) then you'll have to restore BIOS Firmware. Hope you have the tools, it's not like you can magically put "bios.bin" in USB and do it from there, you'd need to desolder BIOS chip, then use an USB converter, download BIOS update, extract the firmware, "burn/restore BIOS", reball and resoldeder BIOS chip and then turn on.
Easier to get another mobo with same bios chip, and replace to check if bios is at fault here.
 
Last edited by JuanMena,
hey thanks for replying. the cpu light on the biard is on not the gpu light. it does not post at all. will not boot at all

i have the tools to desolder the bios and write to it. can i do it with the chip clip while its on the board instead of having to remove it? from what im looking at the bios chip is a standard winbond 8 leg ic which i can write no issues

also why would i need a usb converter? i can use the fw dirent from the manufacturer right?
 
Immy said:
hey thanks for replying. the cpu light on the biard is on not the gpu light. it does not post at all. will not boot at all

i have the tools to desolder the bios and write to it. can i do it with the chip clip while its on the board instead of having to remove it? from what im looking at the bios chip is a standard winbond 8 leg ic which i can write no issues

also why would i need a usb converter? i can use the fw dirent from the manufacturer right?
Click to expand...
I honestly woulnd't attempt anything on board, specially if the method might potentially risk getting thigs shorted.
I'm glad to hear you have the tools required (I've seen those thingies that clutches the BIOS in a lock and then you plug the USB to read it, thought those where the only "BIOS Chip readers/converters")

Are we sure though, is the BIOS at fault?
Have you ruled out everything else?
Have you double checked all power rails are on track?
No broken resistors? No broken caps? No dead power rails?

BIOS chip desolder/rewrite/resolder should be the nuclear option.
 
  • Like
Reactions: zfreeman
JuanMena said:
I honestly woulnd't attempt anything on board, specially if the method might potentially risk getting thigs shorted.
I'm glad to hear you have the tools required (I've seen those thingies that clutches the BIOS in a lock and then you plug the USB to read it, thought those where the only "BIOS Chip readers/converters")

Are we sure though, is the BIOS at fault?
Have you ruled out everything else?
Have you double checked all power rails are on track?
No broken resistors? No broken caps? No dead power rails?

BIOS chip desolder/rewrite/resolder should be the nuclear option.
Click to expand...


the board powers on but doesn't post. i don't know what else it could be. considering it powers on im assuming the power rails are present no?

i normally don't do board repair on desktop boards so i'm definitely a little lost on this one. although i suppose its the same as laptop boards...
 
Immy said:
the board powers on but doesn't post. i don't know what else it could be. considering it powers on im assuming the power rails are present no?

i normally don't do board repair on desktop boards so i'm definitely a little lost on this one. although i suppose its the same as laptop boards...
Click to expand...
It's very difficult to diagnose by this statement (for clarification, not judging you nor critizicing you) but yes and no.

Yes: It powers on. So the rails must be present.
No: It powers on. So the rails must be present.
While indeed, powering on should literally make rails on, a broken or burned component might invalidate one of the "logics", let's put it this way: is like, having a car with different wheels... but no steering wheel... or no breaks, or no gas. In theory, it should run, right?
So, you must check that there's correct voltage values across the entire board, they're mostly separated in "logics" or "sections"... one voltage rail for RAM, another for BIOS, another for GPU, another for CPU, even another for SPEAKERS (and on some boards, having no speakers will invalidate proper MOBO function...) at this point, I think you already know this.

This is why, while the MOBO you're diagnosing right now, turns on but won't do nothing, might indicate a power rail failure that prevents the entire MOBO from functioning correctly.

Depending on the builder, and even on BIOS version, the LED's might or might not indicate properly what's wrong with the MOBO. This is why "BIOS Updates" exists... mostly... and main reason why BIOS can check for failures at boot (but this, again, depends largely on BIOS firmware/tools/version and which vendor uses which BIOS)

Again... yes, it's turning on, yes diagnostic LED's are "fine"... but what if the failure is on the GPU and BIOS isn't outputing it?
Thankfully, harware level issues are relatively easier to diagnose than firmware level failures... literally a visual inspection on each rail (look for cracked, or burnt components) can reveal a possible hardware level failure.
Then, if you don't find anything logical, or, on sight... then it's time to go for schematics and check if voltage rails are present (these will vary greatly on vendor, some uses 3V for BIOS, others 1.5V for BIOS, which is WHY YOU NEED SCHEMATICS)
If then, you can confirm via Schematics + Multimeter Readings that "Yes, everything is working fine", then I'd assume it's BIOS Firmware level failure... and that's when I'd try to restore the BIOS... and main reason why BIOS Firmware level issues are your last resort.
Post automatically merged:

If "I've rewritten BIOS and still not working" then... it's just dead. Give up at this point. Usually points at CPU broken/damaged... "But why not switch CPU and check?"
Because if previous CPU died, the next one will absolutely die again because you haven't diagnosed what's killing the CPU (Overvoltage? Low Voltage? MOBO broken? Bent pins? Shorts to Ground?)
 
Last edited by JuanMena,
JuanMena said:
It's very difficult to diagnose by this statement (for clarification, not judging you nor critizicing you) but yes and no.

Yes: It powers on. So the rails must be present.
No: It powers on. So the rails must be present.
While indeed, powering on should literally make rails on, a broken or burned component might invalidate one of the "logics", let's put it this way: is like, having a car with different wheels... but no steering wheel... or no breaks, or no gas. In theory, it should run, right?
So, you must check that there's correct voltage values across the entire board, they're mostly separated in "logics" or "sections"... one voltage rail for RAM, another for BIOS, another for GPU, another for CPU, even another for SPEAKERS (and on some boards, having no speakers will invalidate proper MOBO function...) at this point, I think you already know this.

This is why, while the MOBO you're diagnosing right now, turns on but won't do nothing, might indicate a power rail failure that prevents the entire MOBO from functioning correctly.

Depending on the builder, and even on BIOS version, the LED's might or might not indicate properly what's wrong with the MOBO. This is why "BIOS Updates" exists... mostly... and main reason why BIOS can check for failures at boot (but this, again, depends largely on BIOS firmware/tools/version and which vendor uses which BIOS)

Again... yes, it's turning on, yes diagnostic LED's are "fine"... but what if the failure is on the GPU and BIOS isn't outputing it?
Thankfully, harware level are relatively easier to diagnose than firmware level failures... literally a visual inspection on each rail (look for cracked, or burnt components) can reveal a possible hardware level failure.
Then, if you don't find anything logical, or, on sight... then it's time to go for schematics and check if voltage rails are present (these will vary greatly on vendor, some uses 3V for BIOS, others 1.5V for BIOS, which is WHY YOU NEED SCHEMATICS)
If then, you can confirm via Schematics + Multimeter Readings that "Yes, everything is working fine", then I'd assume it's BIOS Firmware level failure... and that's when I'd try to restore the BIOS... and main reason why BIOS Firmware level issues are your last resort.
Post automatically merged:

If "I've rewritten BIOS and still not working" then... it's just dead. Give up at this point. Usually points at CPU broken/damaged... "But why not switch CPU and check?"
Because if previous CPU died, the next one will absolutely die again because you haven't diagnosed what's killing the CPU (Overvoltage? Low Voltage? MOBO broken? Bent pins? Shorts to Ground?)
Click to expand...


right ok i understand what you're saying. thank you i really do appreciate your help.

for context the previous cpu died in another mobo and this was his second board.

edit just spoke to him and he used the same cpu in in the previous board as well as this one. i think the issue may be a fried cpu. ill try and grab one to test with.

thank you for the help.

btw are there boardviews and schematics for desktop boards?
 
Immy said:
right ok i understand what you're saying. thank you i really do appreciate your help.

for context the previous cpu died in another mobo and this was his second board.

edit just spoke to him and he used the same cpu in in the previous board as well as this one. i think the issue may be a fried cpu. ill try and grab one to test with.

thank you for the help.

btw are there boardviews and schematics for desktop boards?
Click to expand...

I'm trying to do my best as far as my understanding go.
And, sorry, but can't point you directly towards "Schematics" sites because that'd be against the site's rules (shcematics are in theory copyrighted and we don't want to put the temp at trouble) so you're on your own on this matter.
 
  • Like
Reactions: Skv0ra, JuanMena and tech3475

Site & Scene News

Go to forum More news

Popular threads in this forum

Hard drive not connected(?)

Hacking  Update on my HKIA post.

Corsair one i164

HELP: LINUX Bedrock Dedicated Server Downgrade

getting a 3rd party wii u GCN controller adapter to work on dolphin?

Emulation  Pokémon Mystery Dungeon: Adventure Squad issue