Sign in with
Sign up | Sign in
Your question
Solved

Computer just shuts down by itself.

Last response: in Windows 7
Share
November 3, 2013 4:38:47 AM

Hey guys for the past hour ive been experiencing something bad with my computer it jsut turns off by itself, theres no blue screen or anything, the monitor just turns black and restarts. Idk whats the source of this problem I was just playing BF4 then this happen. Every time i open a software like anti virus or malwarebytes after a few min it will just turn black again and restart, sorry if the information ive given is kinda vague but im writing this quickly cus my computer might turn off again. Please help Here is some information about my computer. GB ram, gtx770,i7 4770k,windows 7,msi g45 gaming motherboard.

Im running an ssd card for my windows and hdd for my files etc. Also i used to run windows from my hdd but then i installed an ssd card, when i installed my ssd card i didnt bother cleaning my old hdd so it still has windows in it. Is that probably where the issue is coming from? The problem is getting worst sometimes after i turn it on it doesnt reach the "login to windows " it will just turn off right away. Im really worried my computer is just 2 months old and ive been getting this "shutdown" 8x already for the past 24hours...:( 

here are the event log:
-Error:ATAPI. (The driver detected a controller error on \Device\Ide\IdePort1)
-Critical Error: (The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.)
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000010, 0x0000000000000002, 0x0000000000000001, 0xfffff80002ed7f1f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 110313-4648-01.

UPDATE

-Critical Kernel-power Event ID 41 The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. I have this event 9x already for the past 24hours.
Quote:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2013-11-04T10:04:50.654402000Z" />
<EventRecordID>48178</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Jeff-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

More about : computer shuts

a b $ Windows 7
a b C Monitor
November 3, 2013 5:07:53 AM

Sounds like a possible hardware issue, I'm suspecting the HDD, specifically the HDD's logic board. Try running SeaTools for DOS see if any issues found
m
0
l
November 3, 2013 4:02:00 PM

Im currently runnkng seatools atm.heres more info about my system Im running an ssd card for my windows and hdd for my files etc. Also i used to run windows from my hdd but then i installed an ssd card, when i installed my ssd card i didnt bother cleaning my old hdd so it still has windows in it. Is that probably where the issue is coming from? The problem is getting worst sometimes after i turn it on it doesnt reach the "login to windows " it will just turn off right away. Im really worried my computer is just 2 months old :( 
m
0
l
Related resources
November 3, 2013 4:39:19 PM

Btw when it turns of its like a reset(turns back on right away) its like someone just pressed the reset button only that when it turn back on again it says the comouter has not been turn off properly(the usual stuff asking you to turn on in safe mode, normaly and etc)
m
0
l
a b $ Windows 7
a b C Monitor
November 3, 2013 7:00:54 PM

jeff2013 said:
Btw when it turns of its like a reset(turns back on right away) its like someone just pressed the reset button only that when it turn back on again it says the comouter has not been turn off properly(the usual stuff asking you to turn on in safe mode, normaly and etc)


That may be a setting in BIOS causing the automatic restart, it is usually an option for what to do if the computer shuts down
m
0
l
a b $ Windows 7
November 3, 2013 7:14:21 PM

At the moment, I would be tempted to suspect the SSD.

How is your machine when you reinstate the original hard drive?
m
0
l
November 4, 2013 12:47:35 AM

himnextdoor said:
At the moment, I would be tempted to suspect the SSD.

How is your machine when you reinstate the original hard drive?


I havent really used my old HDD aside from using it as a storage for files and stuff. Ive done a "seatools for DOS" diagonose on my HDD and it says it passed. Idk what else to do
m
0
l
November 4, 2013 12:49:52 AM

C12Friedman said:
jeff2013 said:
Btw when it turns of its like a reset(turns back on right away) its like someone just pressed the reset button only that when it turn back on again it says the comouter has not been turn off properly(the usual stuff asking you to turn on in safe mode, normaly and etc)


That may be a setting in BIOS causing the automatic restart, it is usually an option for what to do if the computer shuts down


I did a seatools diagnose on the HDD as you suggested, the diagnose took 3hours and the results says it passed the diagnose. I also read from a thread to turn off the auto restart when some error comes up, Im just waiting for the "auto turn off" to happen again so i can take note of the error. Im so worried this rig is just 2 months and i kinda lose my receipt for the parts i bought :( 
m
0
l
a b $ Windows 7
November 4, 2013 12:18:33 PM

Did the problem begin when you installed the SSD?

I wonder, do you have your old HDD set as 'master' rather than 'slave'?

Have you tried running the system with the HDD removed altogether?
m
0
l
November 4, 2013 4:06:18 PM

himnextdoor said:
Did the problem begin when you installed the SSD?

I wonder, do you have your old HDD set as 'master' rather than 'slave'?

Have you tried running the system with the HDD removed altogether?


No. Its been almost a month since i instaled ssd. And yes i made ssd master and hdd as slave. I havent tried that yet, ill try that suggestion later. But i think its not the hdd, cus i did a 3hour diagnose using seatools and it passed the test..
m
0
l
November 4, 2013 5:06:18 PM

New update: updated my drivers and stuff except update the firmware for my sandisk ssd. I was just browsing the internet when thr black screen happened again but this time no restart hapoened maybe because i turn off the auto restart when error comes up. I havent check the dumo files or event log this time yet cus im off to work. God this is frustrating...:( 
m
0
l
a b $ Windows 7
a b C Monitor
November 4, 2013 7:22:57 PM

Going another direction here, what is the make and model of your PSU? How old is it?
m
0
l
November 4, 2013 8:05:49 PM

C12Friedman said:
Going another direction here, what is the make and model of your PSU? How old is it?


Wow my computer shutdown again while i was typing this, and its only been ~5minutes since i turned it on... Everything is about 2 months old they are brand new. The name of the pwoer supply is Corsair CX-750 Modular 80+ bronze power supply. This is frustrating its my first computer that i built myself and after only 2months im experiencing this stuff. :( 

Event Log: Kernerl Power 41 again..
Event Log: Wininit Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications.

I manage to read the dump files and these are the drivers that causes it dxgkrnl.sys dxgkrnl.sys+5d140 fffff880`06ce8000 fffff880`06ddc000 0x000f4000 0x51fa153d 8/1/2013 6:58:53 PM
and nvlddmkm.sys nvlddmkm.sys+153034 fffff880`0f0dd000 fffff880`0fd14000 0x00c37000 0x52676afe 10/23/2013 5:21:50 PM
m
0
l

Best solution

a b $ Windows 7
November 4, 2013 9:07:07 PM

Can I ask you, how many running tasks does Task Manager report and how much CPU usage?

And did you try to use system restore to repair the computer?

In your position and since it's a home build, I would strip the system as bare as possible to rule out certain hardware.

If there is an on-board graphics device then I would remove the graphics card and plug the monitor into the motherboard.

Any other cards, network, sound, extra USB's, I would take them out too.

I would disconnect all USB devices, printer, etc., and remove all but one stick of memory.

I would also remove all the hard drives except for the SSD and leave only one DVD ROM device connected.

Check that the fans are clean and airways and grills are free from obstruction..

I would then remove the battery and reset CMOS.

Then, I would attempt to reinstall Windows from the disk onto the SSD but wouldn't let it update yet.

If Windows installed successfully then I would proceed to install the drivers for the system and I would probably look for updated drivers for the system as soon as I got onto the net.

If the installation fails along the way then I would try and install windows onto the other drive and see how that works out.

At the end of this somewhat drawn out process, you will know whether it is a drive problem or not.

This is my thinking:

If the SSD is faulty and, as an example, it intermittently disconnects itself from the system while it is being written or read to, then that could cause this error.

If the error doesn't occur when the other hard drive is installed in the system as a replacement, then it is the SSD that is the problem.

If you get the same error regardless of which drive is connected (and there should only ever be one hard drive connected to the system at this stage) then the problem is with either the PSU or the motherboard.

And I would say that if removing the side cover has no effect on how long it takes the problem to manifest itself, then the PSU is the root of the cause.

If there is a difference, I would give some final attention to the cooling system and CPU by checking that the heat-sink is firmly seated before deciding that there was a problem with the motherboard itself.

I would say that since the system shuts down rather than 'freezes' exonerates the CPU.

And I the error failed to appear at any of these stages, then I would be able to conclude that the problem was caused by software and in particularly, windows updates.

If you remove half the gear and the problem disappears, you know which half the problem lies in.
Share
!