Question about a STOP 0x101

usasma

Retired Admin
Joined
Feb 20, 2012
Posts
2,126
Topic here: Clock_watchdog_timeout
Right now all I have is one minidump

Unfortunately, that minidump shows no drivers - neither 3rd party nor Windows drivers in the lmtsmn output

Any ideas/discussion about this? What's the significance of it?

I've found that the fewer 3rd party drivers listed in a memory dump, the more likely it is that there's a hardware/low-level problem. This is just an observation of mine and has no scientific basis.

TIA!!!
 
IMO, that system likely came down so fast -- maybe no time..?

NT isn't even found.

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\John\AppData\Local\Temp\Temp1_SF_19-07-2013.zip\SF_19-07-2013\071913-16894-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have thread information
Symbol search path is: SRV*f:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000`00000000
Debugger can not determine kernel base address
Windows 8 Kernel Version 9200 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
Machine Name:
Kernel base = 0xfffff801`4d611000 PsLoadedModuleList = 0xfffff801`4d8dda20
Debug session time: Thu Jul 18 11:47:48.330 2013 (UTC - 4:00)
System Uptime: 0 days 0:34:11.991

"nt" was not found in the image list.
Debugger will attempt to load "nt" at given base 00000000`00000000.

Please provide the full image name, including the extension (i.e. kernel32.dll)
for more reliable results.Base address and size overrides can be given as
.reload <image.ext>=<base>,<size>.
Unable to load image nt, Win32 error 0n2
Unable to add module at 00000000`00000000
Debugger can not determine kernel base address
Loading Kernel Symbols

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff8800125d180, 2}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Unable to read KTHREAD address fffffa80067380f8
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`013e2338 fffff801`4d7eaeee : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`0125d180 : 0xfffff801`4d66b440
fffff880`013e2340 00000000`00000101 : 00000000`00000031 00000000`00000000 fffff880`0125d180 00000000`00000002 : 0xfffff801`4d7eaeee
fffff880`013e2348 00000000`00000031 : 00000000`00000000 fffff880`0125d180 00000000`00000002 00000000`0027dc36 : 0x101
fffff880`013e2350 00000000`00000000 : fffff880`0125d180 00000000`00000002 00000000`0027dc36 00000000`00000000 : 0x31
0: kd> lmnt;lmntsm
start             end                 module name
start             end                 module name
0: kd> lmv
start             end                 module name

Seems the dump is corrupted.
 
Yep, as John said, likely a corrupt dump. Also, for *101's, if you can get a kernel dump from the OP, that would be really great. Minidumps only contain info on the process and CPU that crashed, and we cannot switch CPU's in the debugger without at LEAST a kernel to get more info from these bugchecks.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top