No signal to monitor on startup

Smffy said:
I had the same problem, basically the same kit. Solution for me:

Loosen the CPU cooler screws slightly, see if it boots fine - does the Q Code readout display get stuck at a certain number? My issue stemmed from that, not sure what cooler you are using but my CPU back plate was on a little tight. The reason it changes when its a cold boot I assume is due to things expanding when hot and contracting cold - no idea if the Asus boards have a pressure sensor but I tested this thoroughly and it was defo the issue with mine.

Sounds strange but over time its now fine screwed down tight, next time try loosening each of the 4 screws on the front a few turns and trying again... If you are using an aftermarket CPU cooler that is, with a 6700k you probably are. I don't think its a GPU driver issue, at the point of it booting to BIOS its not really loading the full Nvidia package so you should see it post. If that works loosen off the back plate screws slightly so the screws are not sticking out the threads (laying flush with it) and tighten down the front fully (testing post as you go).
Click to expand...

What do you mean by the Q code display?

I'm using a Noctua NH-U12S . First time I've mounted one, it was quite straight forward. I was really careful not to tighten too much. Considering how it's designed, I'm surprised it can be tightened too much. I'll try loosening the screws a bit.
 
Superlevure said:
What do you mean by the Q code display?

I'm using a Noctua NH-U12S . First time I've mounted one, it was quite straight forward. I was really careful not to tighten too much. Considering how it's designed, I'm surprised it can be tightened too much. I'll try loosening the screws a bit.
Click to expand...

Sorry Q Code is not on that model my bad... Its just an LED readout of the status code.

I was careful too, and yes the screws are sprung so its hard to over tighten but for me it was due to a slight over tighten in to the backplate (not sprung and not provided assembled in my case). Basically slightly shortening the mounts, therefore tighter fitting. I don't know if this is the cause of your problem but its simple to test when you get the issue, simply relax the screws to the heat sink and try again. If this is your problem it can be a long term fix as it will still be fully secure as it sandwiches the board/CPU. I'm talking a few turns here - the heat sink should still be fixed pretty firmly. Consider that you over tightened the mounting screws in to the backplate (not sprung), looking at the diagram in the manual for it here but either way loosening the front sprung screws will tell you if this is your problem.

Worth a shot anyway, just slacken them off next time it fails to post and see how you go. The other obvious means of testing is to remove the GPU and use the onboard graphics - the monitor should turn on at the very least to post.
 
Last edited:
Smffy said:
Sorry Q Code is not on that model my bad... Its just an LED readout of the status code.

I was careful too, and yes the screws are sprung so its hard to over tighten but for me it was due to a slight over tighten in to the backplate (not sprung and not provided assembled in my case). Basically slightly shortening the mounts, therefore tighter fitting. I don't know if this is the cause of your problem but its simple to test when you get the issue, simply relax the screws to the heat sink and try again. If this is your problem it can be a long term fix as it will still be fully secure as it sandwiches the board/CPU. I'm talking a few turns here - the heat sink should still be fixed pretty firmly. Consider that you over tightened the mounting screws in to the backplate (not sprung), looking at the diagram in the manual for it here but either way loosening the front sprung screws will tell you if this is your problem.

Worth a shot anyway, just slacken them off next time it fails to post and see how you go. The other obvious means of testing is to remove the GPU and use the onboard graphics - the monitor should turn on at the very least to post.
Click to expand...

I'll try that next week as I'll be out of the country for a bit. I'll come back to this thread with the results. Your explanations were very clear, thanks for your time.
 
This morning I started the computer with one memory module out and it started normally (and very quickly) for the first time ever! I had tested the pc with the other module, and it wasn't starting on the first boot.

Now, does that mean I need to return the memory or that I need to adjust something about the timings in the bios? I've left everything on auto in the bios and I don't think AI Suite 3 has made any change on the ram (I only changed the multiplying factor there)

Next step:
a) put the bios in default?
b) set the frequency / timings of memory manually
c) return the memory

This is what I've got: Corsair Vengeance LPX Black 16GB (2x8GB) DDR4 PC4-19200 2400MHz
 
Superlevure said:
This morning I started the computer with one memory module out and it started normally (and very quickly) for the first time ever! I had tested the pc with the other module, and it wasn't starting on the first boot.

Now, does that mean I need to return the memory or that I need to adjust something about the timings in the bios? I've left everything on auto in the bios and I don't think AI Suite 3 has made any change on the ram (I only changed the multiplying factor there)

Next step:
a) put the bios in default?
b) set the frequency / timings of memory manually
c) return the memory

This is what I've got: Corsair Vengeance LPX Black 16GB (2x8GB) DDR4 PC4-19200 2400MHz
Click to expand...

Run memtest and see what the outcome is, should show up the faulty stick to return.
 
I've run memtest all night with both memory modules and not a single error was detected :(

The morning after, I started my computer (with that second memory module installed then) and the problem reoccurred: no boot at first, then it booted when restarted.

Should I make any changes in the bios to ensure timings / frequency are ok? I've left everything on 'auto' so far.
 
hi i have same board had similar issues pc random restarts,
freezing in windows, random shutdowns playing games.
had it stress tested at 0cuk for 5+ hrs
got it back ran for 3-4 days ok
then started to get artifacts even booting up.
i reformatted removed drivers. tried running in safe mode,
you name it i tried it.,
my advise
swap the gcard see what happens
if you have a spare.
and then see where your at.
i put my old gcard in and i have not had a single issue since?
hope this helps a little.
good luck. :)
 
Thanks for your help. Actually I do have some freezes but I though this was due to skylake.

It's the first boot problem which is an issue, and it goes away when I removed one of the ram modules! But memtest doesn't manage to show any fault with it. I'll try to return it anyway.

The GPU was working fine on my old rig.
 
You must log in or register to reply here.
Back
Top Bottom