New MSI Mobo - onboard graphics occasionally stop working, advice needed...

[fueg]

I bought a MSI B150I AC about 2 weeks ago. Yesterday I began experiencing issues with the onboard graphics (Intel HD Graphics 530). When I reboot, the monitor is not detected by the mobo (but the computer still boot). I tried different monitors and cables and nothing worked. The only way to get the monitor to be detected again is to reset the cmos. I have no problem at all if I use a dedicated graphics card. I guess I have a problem with the motherboard at this point. 

 

What should I do at this point? Should I contact MSI, ask for RMA from the seller (DirectCanada.com), RMA from MSI or just let it go (I plan to buy a real graphic card for the pc anyway)....??

 

Thanks for your advices!

[jcw150]

Check in the BIOS that it is enabled, I'm not sure where it'll be as I haven't used this BIOS.

[Nena Trinity]

That is your CPUs iGPU...

[fueg]

@jcw150

 

It is still enable in the bios, I did not had another graphic card in the system at the moment. It happens even when the bios is on default settings...

[fueg]

15 minutes ago, Nena360 said:

That is your CPUs iGPU...

I tried to stress test the GPU with Furmark and it seemed fine. When my problem occur Windows still boot ( I connected to my PC with Teamviewer) and I saw the iGPU but the monitor id was Generic non-PnP monitor.

 

I can I be sure if it's from the Motherboard or CPU?

[soup]

4 minutes ago, fueg said:

 

I can I be sure if it's from the Motherboard or CPU?

AIUI the motherboard has all the connections etc for on-board graphics but it is the CPU that does all the work for on-board graphics .

 

There are a few special cases where a graphics chip is enbedded in the MoBo but I think it would be safe to assume that your CPU is doing the actual work .

 

[Nena Trinity]

2 minutes ago, fueg said:

I tried to stress test the GPU with Furmark and it seemed fine. When my problem occur Windows still boot ( I connected to my PC with Teamviewer) and I saw the iGPU but the monitor id was Generic non-PnP monitor.

 

I can I be sure if it's from the Motherboard or CPU?

Could be the board but it can also be the iGPU on the CPU die... (maybe you RAM?)

[fueg]

2 minutes ago, Nena360 said:

Could be the board but it can also be the iGPU on the CPU die... (maybe you RAM?)

That's pretty much the conclusion I came to... I'd like find the problematic part asap since I bought everything 2 weeks ago ( I can still return to the vendor).

 

I am not sure how to test the different components, I don't have any other compatible parts.

 

I could do a memtest to eliminate the RAM. Any idea of what test I could do to know if it comes from the iGPU or the mobo?

 

[Nena Trinity]

1 minute ago, fueg said:

That's pretty much the conclusion I came to... I'd like find the problematic part asap since I bought everything 2 weeks ago ( I can still return to the vendor).

 

I am not sure how to test the different components, I don't have any other compatible parts.

 

I could do a memtest to eliminate the RAM. Any idea of what test I could do to know if it comes from the iGPU or the mobo?

 

Memtest86 should do the trick, (4 passes will do)

[fueg]

4 minutes ago, Nena360 said:

Memtest86 should do the trick, (4 passes will do)

I'll start memtest86 now! I will post the results here...  

[Nena Trinity]

1 minute ago, fueg said:

I'll start memtest86 now! I will post the results here...  

If it has only 1 fail after four passes you need to replace them...

[Sintezza]

To me this sounds like an issue with the bios.

Maybe you could go and check msi´s website if there is a newer bios version out for your motherboard.

Maybe updating the bios might solve it.

 

also dont forget to set the date and time correctly in the bios.

[fueg]

1 minute ago, Sintezza said:

To me this sounds like an issue with the bios.

Maybe you go and check msi´s website if there is a newer bios version out for your motherboard.

Maybe updating the bios might solve it.

I checked back today and i already have the latest version of the bios installed. 

 

The issue only started after I enabled the  S3 state on the USB (Power on / Wake on from USB) (I don't remember the exact name).

 

Now the issue persist even if I set the bios to default settings.

 

When it happens I found 2 way to fix it:

- Reset the CMOS

or

- Drain the capacitors (unplug then press power button until the caps are drained)

[Sintezza]

1 minute ago, fueg said:

I checked back today and i already have the latest version of the bios installed. 

 

The issue only started after I enabled the  S3 state on the USB (Power on / Wake on from USB) (I don't remember the exact name).

 

Now the issue persist even if I set the bios to default settings.

 

When it happens I found 2 way to fix it:

- Reset the CMOS

or

- Drain the capacitors (unplug then press power button until the caps are drained)

 

Hmm which powersuply do you have?

[fueg]

I have a cors

1 minute ago, Sintezza said:

 

Hmm which powersuply do you have?

I have a Corsair SF450 (2 weeks old) 

[fueg]

The issue only happens with integrated gpu. I stole my wife's GTX 560 and I can't reproduce the problem with it.

[Sintezza]

4 minutes ago, fueg said:

I have a cors

I have a Corsair SF450 (2 weeks old) 

Ah okay that should be fine aswell then.

I just wanted to say that some older psu´s dont work well with low ripple current.

Then you needed to disable C6 and C7 states in the bios, which automaticly means that you could not use hybernate mode.

 

But the corsair SF psu´s are new, so that shouldnt be an issue.

[fueg]

1 minute ago, Sintezza said:

Ah okay that should be fine aswell then.

I just wanted to say that some older psu´s dont work well with low ripple current.

Then you needed to disable C6 and C7 states in the bios, which automaticly means that you could not use sleep mode.

 

But the corsair SF psu´s are new, so that shouldnt be an issue.

I tought the same, the psu has been released not too long ago, it's brand new and it has a 7 years warranty. I would be surprised if it was the problem!

[Sintezza]

4 minutes ago, fueg said:

The issue only happens with integrated gpu. I stole my wife's GTX 560 and I can't reproduce the problem with it.

 

Ah thats realy value information.

I personaly dont think that thats the igpu inside your cpu that has problems.

But you might contact the re-seller and explain your problem.

Since you can proof that you dont have an issue with a dedicated gpu.

So it could be that either there is an issue with the board, or the igpu.

[Sintezza]

2 minutes ago, fueg said:

I tought the same, the psu has been released not too long ago, it's brand new and it has a 7 years warranty. I would be surprised if it was the problem!

 

Well then you basicly should have had a similar problem with a dedicated gpu aswell.

[Sintezza]

My guess is that its most likely an issue with your motherboard.

Because as you explained above, wenn you clear the cmos it does work.

And an igpu dying inside a cpu, doesnt sound very likely to me.

If you contact the re-seller, they will most likely send you a new board, or offer a refund.

[fueg]

7 minutes ago, Sintezza said:

 

Ah thats realy value information.

I personaly dont think that thats the igpu inside your cpu that has problems.

But you might contact the re-seller and explain your problem.

Since you can proof that you dont have an issue with a dedicated gpu.

So it could be that either there is an issue with the board, or the igpu.

I personally suspect the board.. Maybe a bad capacitor (since draining the caps seems to fix the problem)... I guess I will contact directcanada later today

[Sintezza]

2 minutes ago, fueg said:

I personally suspect the board.. Maybe a bad capacitor (since draining the caps seems to fix the problem)...

 

Could verywell be the case indeed.

Msi doesnt build the best boards for that matter.

Could be an issue with the power delivery to the igpu.

VCCGT.

[fueg]

7 hours ago, Nena360 said:

Memtest86 should do the trick, (4 passes will do)

As expected, the RAM is fine...

[Nena Trinity]

47 minutes ago, fueg said:

As expected, the RAM is fine...

4 passes went fast?