Quantcast
Channel: Server Manager forum
Viewing all articles
Browse latest Browse all 1903

Server got rebooted due to a bugcheck,bugcheck was: 0x0000001a (0x0000000000003452, 0x000000007efd0000, 0xfffff70001080590, 0x0000000000000000

$
0
0

Hi All,

One of the server got rebooted in our environment because of the bugcheck below is the error in event logs

bugcheck was: 0x0000001a (0x0000000000003452, 0x000000007efd0000, 0xfffff70001080590, 0x0000000000000000Below is the bug check analysis

*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003452, The subtype of the bugcheck.
Arg2: 000000007efd0000
Arg3: fffff70001080590
Arg4: 0000000000000000

Debugging Details:
------------------

Page 64928a not present in the dump file. Type ".hh dbgerr004" for details

BUGCHECK_STR:  0x1a_3452

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  WmiPrvSE.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80001743e33 to fffff800016d2bc0

STACK_TEXT:  
fffff880`09e00ee8 fffff800`01743e33 : 00000000`0000001a 00000000`00003452 00000000`7efd0000 fffff700`01080590 : nt!KeBugCheckEx
fffff880`09e00ef0 fffff800`016a3892 : fffffa80`1bde61f0 fffffa80`00000000 fffff880`00000009 fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x35163
fffff880`09e017a0 fffff800`019a805a : fffff8a0`166bcaf0 fffff880`09e01ae0 00000000`00000000 fffffa80`1d313b50 : nt!MmCleanProcessAddressSpace+0x96
fffff880`09e017f0 fffff800`0198cb7d : 00000000`000000ff fffff880`09e01a01 00000000`7efad000 fffffa80`1bd94830 : nt!PspExitThread+0x56a
fffff880`09e018f0 fffff800`016c56fa : 00000000`00000001 fffff880`09e01a68 00000000`00000001 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`09e01920 fffff800`016c5a40 : 00000000`0040fa20 fffff880`09e019a0 fffff800`0198caf0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`09e019a0 fffff800`016d1ef7 : fffffa80`1d313b50 00000000`7efad000 fffff880`000000c0 00000000`7efad000 : nt!KiInitiateUserApc+0x70
fffff880`09e01ae0 00000000`77432bba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0044e578 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77432bba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35163
fffff800`01743e33 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35163

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

FAILURE_BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+35163

BUCKET_ID:  X64_0x1a_3452_nt!_??_::FNODOBFM::_string_+35163

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_3452_nt!_??_::fnodobfm::_string_+35163

FAILURE_ID_HASH:  {b68bb6d6-c4e1-ed4f-abca-56d9004b82c0}

Can someone please help to analyse the root cause of the reboot.

Regards

Asish


Viewing all articles
Browse latest Browse all 1903

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>