Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Stop Error on SBS 2003


  • Please log in to reply
1 reply to this topic

#1 Lucas Wright

Lucas Wright

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:13 AM

Posted 14 November 2011 - 12:09 PM

We recently experienced a system stop on a SBS 2003 server. This happened out of the blue as we haven't installed any new drivers for a long while, nor have there been any Windows Updates installed lately that would seem to cause this. We received the following stop code after the server rebooted: 0x0000000a (0x0000095c, 0xd000001b, 0x00000001, 0x808327f1). I'm attaching the Windbg analysis for your convenience. Any assistance is much appreciated.






Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini111411-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x86 compatible
Product: LanManNt, suite: SmallBusiness TerminalServer SmallBusinessRestricted SingleUserTS
Built by: 3790.srv03_sp2_gdr.101019-0340
Machine Name:
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Mon Nov 14 10:37:01.885 2011 (GMT-5)
System Uptime: 6 days 13:23:58.026
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {95c, d000001b, 1, 808327f1}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : ntkrpamp.exe ( nt!KiDeferredReadyThread+2f7 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000095c, memory referenced
Arg2: d000001b, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 808327f1, address which referenced memory

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


WRITE_ADDRESS: 0000095c

CURRENT_IRQL: 1b

FAULTING_IP:
nt!KiDeferredReadyThread+2f7
808327f1 870b xchg ecx,dword ptr [ebx]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xA

PROCESS_NAME: Idle

TRAP_FRAME: 8089a43c -- (.trap 0xffffffff8089a43c)
ErrCode = 00000002
eax=000000fb ebx=0000095c ecx=00000001 edx=ffdff120 esi=f775faa0 edi=00000000
eip=808327f1 esp=8089a4b0 ebp=8089a4d0 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!KiDeferredReadyThread+0x2f7:
808327f1 870b xchg ecx,dword ptr [ebx] ds:0023:0000095c=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 808327f1 to 8088c9eb

STACK_TEXT:
8089a43c 808327f1 badb0d00 ffdff120 8a1d1800 nt!KiTrap0E+0x2a7
8089a4d0 80832a82 00000000 808311bf 89154608 nt!KiDeferredReadyThread+0x2f7
8089a4d8 808311bf 89154608 00000181 8083137a nt!KiProcessDeferredReadyList+0x16
8089a4f4 80831d24 ffdffa40 ffdff120 00000000 nt!KiExitDispatcher+0x25
8089a5a8 808320b7 00000000 00000000 02295b80 nt!KiTimerExpiration+0x590
8089a600 8088de9f 00000000 0000000e 00000000 nt!KiRetireDpcList+0x65
8089a604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDeferredReadyThread+2f7
808327f1 870b xchg ecx,dword ptr [ebx]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiDeferredReadyThread+2f7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4cbda48f

FAILURE_BUCKET_ID: 0xA_nt!KiDeferredReadyThread+2f7

BUCKET_ID: 0xA_nt!KiDeferredReadyThread+2f7

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

BC AdBot (Login to Remove)

 


#2 Okharon

Okharon

  • Members
  • 9 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:06:13 AM

Posted 14 November 2011 - 05:19 PM

Try downloading Bluescreenview and having a look with that. It should show you which driver files were causing the error so that you can update/reinstall them.

Let us know how you go




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users