PC keeps rebooting every 10 secs after cleaning with compressed air

foxh0und

Honorable
Aug 18, 2012
63
0
10,630
My PC was getting pretty dusty so I decided to clean it with a can of compressed air and now my pc keeps rebooting every 10 seconds, I can't even get to the bios.

I made sure to not let any of the liquid come out by holding it the correct way up and I'm fairly positive it didn't spurt out any liquid.

The CPU fan is spinning, the gpu fan is spinning.

I have the following in my system.

I5 3570k
8gb corsair vengeance ram
MSI z77a-g45
MSI 760 2gb
Hyper evo 212 CPU cooler.


Any ideas what could have happened? Or fixes?
 

foxh0und

Honorable
Aug 18, 2012
63
0
10,630
Ok I have managed to get it to turn on again and all seems fine, and I'm getting cooler temps.

However, before functioning it said something about a previous attempt to overclock had failed and to run set up or something like that? So I agreed to remove the overclock and run set up, nothing happened so I rebooted and it turned on and everything worked ok, I'm kind of afraid to reboot again, any ideas what it was and if it might come back?

Note I haven't tried to overclock anything on this system. I attempted to overclock a 660ti using afterburner, but this is a different card
 

Dorosh

Honorable
Dec 1, 2013
215
0
10,760
The "previous attempt failed" warning happens when the system fails basic stability tests on Boot. So if you haven't made any changes to your system you could have hardware problems; something is unstable. Restore everything to default in your BIOS and try again. You shouldn't worry about starting up again as the system is shutting off to prevent further damage. Do you blue screen before restarting or does it just shut down? If you can get into windows, try a memory test to see what happens.
I'm worried you did get some water somewhere which could have damaged any number of things.
 

foxh0und

Honorable
Aug 18, 2012
63
0
10,630


Hey, thanks for the reply :)

I can get into windows and it seems to be functioning as normal, i did the memory test, found no detects, the reboot for the test went fine too.

The only thing I see that that strikes me as odd is the CPU fan is running at 100% on idle, is this normal?

My package temps are min 32 and max 43. (Probably needs some new thermal paste but I don't think that would be causing this?)
 

Dorosh

Honorable
Dec 1, 2013
215
0
10,760
When you say Package temps, do you mean inside the case or the CPU temp? The CPU fan should not be running at 100% unless the CPU is getting hot. Download HWMonitor and tell me what your CPU temp is.
 

foxh0und

Honorable
Aug 18, 2012
63
0
10,630


By package temps I think it means the CPU as a whole instead of each core.

here is a screen shot of HWmonitor.

It's running hotter than I'd like and probably needs paste replacing, but I can't do that until I find my paste or buy new paste, but i don't think those temps justify 100% fans.

Any ideas?

http://imgur.com/XhsGxHn
 

Dorosh

Honorable
Dec 1, 2013
215
0
10,760
Ok that makes sense. Those temps are super low. You only have to worry about them if they were getting over 80 degrees C.
I'm not sure why the fan is at 100 % idle though. I'm not too familiar with that MSI board, but it looks like there is software for it that will allow you to control your fan speeds. Install/re-install any fan control software from the MSI website and it should either fix the problem or at least allow you to control it. Something might be set to turn the fan speed up when it gets to a certain temp, and that temp should be set to something a lot higher like 50 degrees C or something.
 

foxh0und

Honorable
Aug 18, 2012
63
0
10,630


Thanks for the help :) I'll try to find the fan software, since you don't see anything suspicious other than the CPU fan running at 100% I suppose the best cause of action right now is "If it ain't broke, don't fix it" if it happens again, I'll either come back here or contact MSI, I'm hoping it was just one of those moments you get where the PC messes up then corrects itself on it's own somehow. Perhaps the board got too cold and got confused, who knows.