sharepoint2014
asked on
New PC keeps rebooting by itself
Dear all,
My new PC is i3-3220 on GA-Z77 mobo, with 3 GPUs (Gigabyte R9 280X), on a 4GB RAM.
I've installed Win7-64bit and use it for mining, open-air.
I have set the powercfg to 100 and it still reboots, here is the minidump. See the attached gpu temp too.
Can someone help me to tell me what I should do?
Thanks!
021714-16208-01.dmp
1.png
My new PC is i3-3220 on GA-Z77 mobo, with 3 GPUs (Gigabyte R9 280X), on a 4GB RAM.
I've installed Win7-64bit and use it for mining, open-air.
I have set the powercfg to 100 and it still reboots, here is the minidump. See the attached gpu temp too.
Can someone help me to tell me what I should do?
Thanks!
021714-16208-01.dmp
1.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ok then try clearing the cmos - that works for me when I push my gigabyte board too far :)
Make sure the latest drivers are installed for your mobo.
That sounds like a heat issue to me.
- gurutc
- gurutc
+gurutc - possibly but I have this behaviour on my Gigabyte motherboard every so often, usually when I am playing with overclocks and, so far, bios reset and less aggressive OC have cured it.
regmigrant that would seem to be consistent with additional heat from the oc do you think?
-gurutc
-gurutc
well..yes, (blush) I took the OP to mean it was rebooting immediately on start and looping through a reboot sequence (which I now realise may not be the case) because in my own case the reboot happened before boot loader finished so nothing got warm enough to be a heat related failure - especially since once I stepped it back to more realistic values it all worked fine.
If the Author could give us an idea of how long it takes to fail that might indicate heat induced failure rather than bios settings
If the Author could give us an idea of how long it takes to fail that might indicate heat induced failure rather than bios settings
ASKER
intervals between 4-5 hrs, sometimes 9-12 hrs, it will reboot.
If its a cpu/gpu over temp cut out there should be reference to it in the event log showing that the temp was getting high and reseating cooler, changing thermal paste might be all you need. If its more subtle - a cracked PCB flexing in the heat it can be difficult to track down.
- do you have an alternate, lower power graphics card to try?
- you mentioned you are running open air, do you have desk fan you can point at the motherboard to provide a constant airflow
- can you swap out the ram for a known good set or alternate 2 sticks at a time
- can you run a torture test and see if you can force the problem whilst you are running
- do you have an alternate psu to try
You'll need to try each of these separately to eliminate possibilities. If none of them work you might be looking at a mobo failure
- do you have an alternate, lower power graphics card to try?
- you mentioned you are running open air, do you have desk fan you can point at the motherboard to provide a constant airflow
- can you swap out the ram for a known good set or alternate 2 sticks at a time
- can you run a torture test and see if you can force the problem whilst you are running
- do you have an alternate psu to try
You'll need to try each of these separately to eliminate possibilities. If none of them work you might be looking at a mobo failure
Agreeing. your issue looks like hardware, and that can be a bear to track down.
The above suggestions are very good.
- gurutc
The above suggestions are very good.
- gurutc
it certainly points to IMAGE_NAME: atikmpag.sys
here they discuss that kind of error http://forums.guru3d.com/showthread.php?t=363233
here they discuss that kind of error http://forums.guru3d.com/showthread.php?t=363233
I too have had a myriad problems with Catlayst Control Centre - once I managed to a get a 'driver only install' sorted out the problems went away.
However it tended to be BSOD rather than reboot and it was referenced in event log
However it tended to be BSOD rather than reboot and it was referenced in event log
ASKER