Unexpected Shutdowns
I have Windows 7 Home Premium 32 bit with 4 gig ram. It is a generic computer with Intel components (MB and Processor Core 2 Duo 3 gig). Hard drive is less than year old 1 TB WD. I log off when I leave it for the day.
On about three occasions in the past month, I have returned to find that the computer has rebooted and I get the message that it has recovered from an unexpected shutdown. The only thing I find in the logs is that the computer shut down unexpectedly. Any
ideas?
April 22nd, 2010 6:12pm
I've got exactly the same thing. I have two systems, desktop & laptop, both recent Dell purchases running Win7. Both were running fine until this week when they have both been hit by sudden bsods. It then automatically reboots and I get the 'recovered
from unexpected shutdown' message mentioned above.
Looking in C:\Windows\Minidump I've got 6 dumps on the desktop and 5 on the laptop, all dated since 19th April 2010. I didn't install anything on that date, and the Windows Update doesn't show any new installs.
I downloaded the Windows Debugger but I'm a little lost with it. It seems to be blaming netio.sys, but searching for help on that seems to point the finger from everything to nvidea to Zone Alarm.
Can anyone help analyze my dumps?
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 7:29pm
Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services).
The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case
some more severe damage happens. Then we get a blue screen or the system reboots (it depends on what the system settings are).
To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. A suggestion would be to contact Microsoft Customer Service and Support (CSS) via telephone so that
a dedicated Support Professional can assist with your request. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
Microsoft - Help and Support
If you are outside the US please see
Microsoft Worldwide Home for regional support phone numbers.
Meantime we can try some available steps as a general troubleshoot.
1. Please remove the antivirus and run the system with a period. If the issue does not occur, mainly focus on antivirus settings and compatibility.
2. Disable Automatic Restart and see detail information on the blue screen.
1).Click Start, in the Start Search box enter sysdm.cpl.
2).Click the tab Advanced. Under Startup and Recovery, click the Settings button.
3). Uncheck “Automatically restart”.
4). On the drop-down menu “Write debugging information”, choose “Small memory dump”.
5). Click OK.
When Blue Screen displays, you may get more information from the screen.Arthur Xie - MSFT
April 23rd, 2010 11:17am
Thanks both. Have now disabled Zone Alarm and AVG. Still getting BSOD, in fact they now seem to be worse! The logs now seem to point to something else. If I can manage to do it before I get another bsod then I'll paste them in here if that's ok.
Now also Control Panel is crashing! Start CP, click on System and I get a popup telling me Explorer has stopped working. Seems to do it every time.
BTW - Does “Small memory dump” or "Kernel memory dump" give the most useful output?
Free Windows Admin Tool Kit Click here and download it now
April 23rd, 2010 12:27pm
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41790, fffffa8000db1b30, ffff, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8000db1b30
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ce6ede to fffff80002c73600
STACK_TEXT:
fffff880`08552768 fffff800`02ce6ede : 00000000`0000001a 00000000`00041790 fffffa80`00db1b30 00000000`0000ffff : nt!KeBugCheckEx
fffff880`08552770 fffff800`02cb4fca : 00000000`00000000 00000000`19348fff fffffa80`00000000 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`08552930 fffff800`02c72853 : ffffffff`ffffffff 00000000`02a0d230 00000000`02a0d1f8 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`08552a20 00000000`7773009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02a0d168 fffff800`02c6af40 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7773009a
fffff880`08552e20 fffff880`08552e20 : fffff880`08552e20 fffff880`08552e30 fffff880`08552e30 00000000`00000000 : nt!KiCallUserMode
fffff880`08552e28 fffff880`08552e20 : fffff880`08552e30 fffff880`08552e30 00000000`00000000 fffff880`08553db0 : 0xfffff880`08552e20
fffff880`08552e30 fffff880`08552e30 : fffff880`08552e30 00000000`00000000 fffff880`08553db0 00000000`00000000 : 0xfffff880`08552e20
fffff880`08552e38 fffff880`08552e30 : 00000000`00000000 fffff880`08553db0 00000000`00000000 00000000`00000000 : 0xfffff880`08552e30
fffff880`08552e40 00000000`00000000 : fffff880`08553db0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`08552e30
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02ce6ede cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946
BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946
Followup: MachineOwner
---------
4: kd> lmvm nt
start end module name
fffff800`02c03000 fffff800`031df000 nt (pdb symbols) c:\debug_symbols\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
Loaded symbol image file: ntkrnlmp.exe
Mapped memory image file: c:\debug_symbols\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe
Image path: ntkrnlmp.exe
Image name: ntkrnlmp.exe
Timestamp: Sat Feb 27 07:55:23 2010 (4B88CFEB)
CheckSum: 00545094
ImageSize: 005DC000
File version: 6.1.7600.16539
Product version: 6.1.7600.16539
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 1.0 App
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: ntkrnlmp.exe
OriginalFilename: ntkrnlmp.exe
ProductVersion: 6.1.7600.16539
FileVersion: 6.1.7600.16539 (win7_gdr.100226-1909)
FileDescription: NT Kernel & System
LegalCopyright: © Microsoft Corporation. All rights reserved.
April 23rd, 2010 12:29pm
From the debug information, we can find that there are driver issues. Since we cannot obtain more information from mini dump, you may need to contact Microsoft Customer Service and Support, they will help you to analyze the system dumps.
Since your computer is from Dell, you can also try to download Windows 7 compatible drivers from Dell website.
Dell - Drivers and Downloads
Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
If it does not help, you may contact Dell support for assistance on hardware issue troubleshooting.
Dell - Contact Us
Arthur Xie - MSFT
Free Windows Admin Tool Kit Click here and download it now
April 26th, 2010 9:50am