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

BOSD at login screen, decoded dmp included


  • Please log in to reply
No replies to this topic

#1 kemstewa

kemstewa

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:11:38 PM

Posted 06 July 2009 - 03:12 PM

Basically after the computer boots up and sits at the login screen, it has a BSOD. Any ideas?


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


Loading Dump File [C:\Users\kevin.stewart\Desktop\Mini070609-07.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 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.22389.x86fre.vistasp1_ldr.090302-1506
Machine Name:
Kernel base = 0x82002000 PsLoadedModuleList = 0x8211ac70
Debug session time: Mon Jul 6 14:30:44.525 2009 (GMT-4)
System Uptime: 0 days 0:01:26.468
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, 82041824}

Unable to load image \SystemRoot\System32\Drivers\SRTSPL.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSPL.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSPL.SYS
Probably caused by : SRTSPL.SYS ( SRTSPL+1834e )

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

1: 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: 00000000, memory referenced
Arg2: 00000002, 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: 82041824, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8213a868
Unable to read MiSystemVaType memory at 8211a420
00000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeleteResourceLite+20
82041824 8901 mov dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT: 7

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 88b5fa58 -- (.trap 0xffffffff88b5fa58)
ErrCode = 00000002
eax=00000000 ebx=82054348 ecx=00000000 edx=00000000 esi=ae412518 edi=00000000
eip=82041824 esp=88b5facc ebp=88b5fae0 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!ExDeleteResourceLite+0x20:
82041824 8901 mov dword ptr [ecx],eax ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 82041824 to 8205cd84

STACK_TEXT:
88b5fa58 82041824 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
88b5fae0 ae42034e ae412518 85bcff38 ae416545 nt!ExDeleteResourceLite+0x20
WARNING: Stack unwind information not available. Following frames may be wrong.
88b5fb18 821724a3 85bcff38 8695d000 00000000 SRTSPL+0x1834e
88b5fcfc 82172e37 00000001 00000000 88b5fd24 nt!IopLoadDriver+0x805
88b5fd44 8203a45d 9494cd00 00000000 84032828 nt!IopLoadUnloadDriver+0x70
88b5fd7c 821d8c8c 9494cd00 9229b856 00000000 nt!ExpWorkerThread+0xfd
88b5fdc0 82030a7e 8203a360 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
SRTSPL+1834e
ae42034e ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: SRTSPL+1834e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SRTSPL

IMAGE_NAME: SRTSPL.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 47e2970b

FAILURE_BUCKET_ID: 0xA_SRTSPL+1834e

BUCKET_ID: 0xA_SRTSPL+1834e

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

1: 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: 00000000, memory referenced
Arg2: 00000002, 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: 82041824, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8213a868
Unable to read MiSystemVaType memory at 8211a420
00000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!ExDeleteResourceLite+20
82041824 8901 mov dword ptr [ecx],eax

CUSTOMER_CRASH_COUNT: 7

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: 88b5fa58 -- (.trap 0xffffffff88b5fa58)
ErrCode = 00000002
eax=00000000 ebx=82054348 ecx=00000000 edx=00000000 esi=ae412518 edi=00000000
eip=82041824 esp=88b5facc ebp=88b5fae0 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!ExDeleteResourceLite+0x20:
82041824 8901 mov dword ptr [ecx],eax ds:0023:00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 82041824 to 8205cd84

STACK_TEXT:
88b5fa58 82041824 badb0d00 00000000 00000000 nt!KiTrap0E+0x2ac
88b5fae0 ae42034e ae412518 85bcff38 ae416545 nt!ExDeleteResourceLite+0x20
WARNING: Stack unwind information not available. Following frames may be wrong.
88b5fb18 821724a3 85bcff38 8695d000 00000000 SRTSPL+0x1834e
88b5fcfc 82172e37 00000001 00000000 88b5fd24 nt!IopLoadDriver+0x805
88b5fd44 8203a45d 9494cd00 00000000 84032828 nt!IopLoadUnloadDriver+0x70
88b5fd7c 821d8c8c 9494cd00 9229b856 00000000 nt!ExpWorkerThread+0xfd
88b5fdc0 82030a7e 8203a360 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
SRTSPL+1834e
ae42034e ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: SRTSPL+1834e

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: SRTSPL

IMAGE_NAME: SRTSPL.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 47e2970b

FAILURE_BUCKET_ID: 0xA_SRTSPL+1834e

BUCKET_ID: 0xA_SRTSPL+1834e

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

BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users