My computer keeps turning off without warning

[Nal]

Hi.

I've been having this problem recently where my computer just suddenly - without any kinds of warning - turns off, as if somebody had pulled out the plug. It immediately restarts after, showing the message upon starting that "Windows was closed incorrectly, do you want to boot into safe mode?". It's happened a few times now, mostly when playing games which made me think it might be heat-related, but it doesn't seem to be. When it happens the computer usually isn't as warm as it sometimes is.
Any idea what might be causing this? I'd really appreciate some help!
Thanks in advance

 

[richc46]

Welcome
If you upload the following information we may have a better idea of the problem
http://www.vistax64.com/crashes-debugging/282419-blue-screen-death-bsod-posting-instructions.html
Off the top, possibly hard drive.

 

[Nal]

Thanks for the quick reply. I did as you asked, here's the file.

 

[richc46]

This is what you do make a system restore point
Uninstall your firewall (very possibly that is the problem)
Use the Windows firewall.
This is what some of your reports show as the cause
Afwcore.sys file descriptionProductname: Outpost Firewall Description: Agnitum Firewall Core Driver Company: Agnitum Ltd.

 

[Nal]

Ok, thanks. I've done so. Hopefully this'll fix it. Cheers!

 

[Nal]

Unfortunately this didn't seem to fix the problem, as this has still been occuring. I've run the SF diagnostic tool again, here are the files:

 

[richc46]

Unfortunately, the most import report is called a mind-dmp. You have not given us any new ones. The files that you submitted are the same as the last time that you posted.

 

[richc46]

go to search type cmd
in cmd type driverquery
See if this driver is still there
Afwcore.sys

 

[Nal]

Oh. That's very strange, I just ran the SF diagnostic tool right now. Do you have any idea for what else I could try?

Edit: Oops, didn't see you already responded. Damn, you're fast. :P

 

[Nal]

No, as far as I can see that driver is not there.

 

[richc46]

OK
Then we know that the apparent cause of the last bsod is not the same as this. Wait for another BSOD and send the files again. Do it right after the BSOD.

 

[Nal]

Ok, thanks, I will.

 

[Nal]

It happened just now. Here are the files:

 

[richc46]

For some reason your computer has stopped giving the necessary reports. Read how to configure dump types.
How to read the small memory dump files that Windows creates for debugging

 

[Nal]

These are the four steps listed in the "Configure the dump type" section of the website.

1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. Click the Advanced tab, and then click Settings under Startup and Recovery.
4. In the Write debugging information list, click Small memory dump (64k).


"Small memory dump (64k) doesn't seem to be an option for me, though. Following are the options I have (poorly translated from Danish):

- Storage of core memory
- Partial story of memory (128 KB)
- (none)

Currently it's set to "Storage of core memory". Should I switch to the second option?

Also, thanks again for all the help, it's very professional and I really appreciate it!

 

[richc46]

First you are very welcome. We are all volunteers and we are here only because we are interested in computers and get great satisfaction from helping others.
That being said, you have to be set for the mini dmp. maybe in your case, due to language its the small dump. You do have the setting because your early posts had the information.

 

[Nal]

Ok, I changed it to the "Partial storage of memory (128 kb)". Hoping it's the right one. What should I do now?

 

[richc46]

Have fun with the computer and if you get more BSODs, send us the files and lets hope we have the necessary information.

 

[Nal]

Ok, thanks!

 

[Patonb]

Is it blue screening or just powering off?