Solved unexpected shutdown

September 13, 2011 at 01:43:50
Specs: Windows 7
hey guys i really look forward to help me with this issue.
i have made a setup for mikrotik server on a virtual machine so i need to keep my computer on all the time
and that was fine for 4 or 5 days then i start to wake up every morning to see that my computer on and stopped
on user login screen
i click on my user to login and here i find message that said unexpected shutdown, i didnt care much at first time
but now its started to annoy me
my pc details is
CPU : Q8300
RAM : 4 GB
Motherboard : GA-EP35
Vga : Geforce 9500GT
and here is my (Minidump) files
http://www.mediafire.com/?mqsu4qs58...
plz answer me as soon as u can, my adsl users dont even give me a chance to breath.

See More: unexpected shutdown

Report •

#1
September 13, 2011 at 05:11:14
Restarting can be overheating, bad memory stick, Windows, Adobe, or other updates, to name the top ones.
Use Speedfan or similar program to monitor temperatures.
Use Memtest86 to test your memory for bad segments.
Reset all updates to download but ask for permission to install.
Run Malwarebytes if you suspect an infection.
Set all power saving features to "Never" except monitor.
(I could not see your dump files to check it, but maybe it was just me)

You have to be a little bit crazy to keep you from going insane.


Report •

#2
September 13, 2011 at 07:34:15
✔ Best Answer
Alright, something strange is going on:
2: kd> vertarget
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:Loading symbols for a5866000          srv.sys ->   srv.sys

Kernel base = 0x8281a000 PsLoadedModuleList = 0x82962810
Debug session time: Thu Sep  8 03:18:09.221 2011 (UTC - 4:00)
System Uptime: 0 days 13:17:18.844
I'm pretty sure "x86fre" is the normal retail version, but your first minidump shows:
2: kd> .bugcheck
Bugcheck code 00000001
Arguments 82a9570e 00000000 0000fffe 00000000
Bug check 0x1, which MSDN says shouldn't be possible unless you're using the check (debug) version of Windows.

The others are just 0x19's (BAD_POOL_HEADER). You could try disabling Kaspersky, but I doubt that's the problem.

Check your CPU, check your RAM, check your PSU. If you're over-clocking, stop. If you're not, make sure you're not.

How To Ask Questions The Smart Way


Report •
Related Solutions


Ask Question