BugCheck 8E, rassstp.sys, Vista SP1, Analiza raportu z dmp

[OBCY]

Witam,
mam problem z odczytaniem tego raportu.
Czy ktos dostrzega w nim gdzie lezy przyczyna? Co powoduje niebieski ekran.
Nie mam wyszczególnionego procesu przez który sie spie...
Dotyczy Visty.


########################################################
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\medion\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x82200000 PsLoadedModuleList = 0x82317c70
Debug session time: Sat Jun 27 01:35:54.445 2009 (GMT+2)
System Uptime: 0 days 0:13:28.336

er Symbols
PEB is paged out (Peb.Ldr = 7ffdb00c). Type ".hh dbgerr001" for details
Loading unloaded module list
................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 0, 9cd6ea48, 0}

*** ERROR: Module load completed but symbols could not be loaded for rassstp.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndis.sys -
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 57a4c not present in the dump file. Type ".hh dbgerr004" for details


*********************************************************************
Probably caused by : rassstp.sys ( rassstp+26dd )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: 9cd6ea48, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.


ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: rassstp

FAULTING_MODULE: 82200000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4791911b

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:
+1d6952f014bdfdc
00000000 ?? ???

TRAP_FRAME: 9cd6ea48 -- (.trap 0xffffffff9cd6ea48)
ErrCode = 00000010
eax=9cd6eae4 ebx=00000000 ecx=86a5ed2c edx=00000000 esi=86a5ed30 edi=85c5a7d0
eip=00000000 esp=9cd6eabc ebp=9cd6ead8 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
00000000 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82236590 to 822cd0e3

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9cd6e608 82236590 0000008e c0000005 00000000 nt!KeBugCheckEx+0x1e
9cd6e9d8 822585da 9cd6e9f4 00000000 9cd6ea48 nt!ExfReleasePushLockShared+0xaa4
9cd6eab8 82219789 86a5ed30 9cd6eae4 00128038 nt!Kei386EoiHelper+0x1d2
9cd6ead8 8220d68e 86a5ed30 85c5a7d0 00000000 nt!IoCsqInsertIrpEx+0x3a
9cd6eaf0 8c7006dd 86a5ed30 85c5a7d0 00000000 nt!IoCsqInsertIrp+0x15
9cd6eb04 8c7029ef 86a5ed2c 85c5a7d0 880b2000 rassstp+0x26dd
9cd6eb20 8814e7fe 86a5bc70 85c5a7d0 86a5bd28 rassstp+0x49ef
9cd6eb3c 8814e938 86a5bc70 85c5a7d0 00000000 ndis!TrFilterDprIndicateReceiveComplete+0x106a
9cd6ec2c 822bbfd3 86a5bc70 85c5a7d0 85c5a7d0 ndis!TrFilterDprIndicateReceiveComplete+0x11a4
9cd6ec44 8244c5e5 85d95690 85c5a7d0 85c5a840 nt!IofCallDriver+0x64
9cd6ec64 8244cd8a 86a5bc70 85d95690 02c28100 nt!NtQueryInformationProcess+0x1c63
9cd6ed00 82436a5d 86a5bc70 85c5a7d0 00000000 nt!NtQueryInformationProcess+0x2408
9cd6ed34 82257a1a 00000764 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
9cd6ed64 772d9a94 badb0d00 010ff9a8 00000000 nt!ZwQueryLicenseValue+0xbd2
9cd6ed68 badb0d00 010ff9a8 00000000 00000000 0x772d9a94
9cd6ed6c 010ff9a8 00000000 00000000 00000000 0xbadb0d00
9cd6ed70 00000000 00000000 00000000 00000000 0x10ff9a8


STACK_COMMAND: kb

FOLLOWUP_IP:
rassstp+26dd
8c7006dd 5d pop ebp

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: rassstp+26dd

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: rassstp.sys

BUCKET_ID: WRONG_SYMBOLS

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

[cosik_ktosik]

Z tego co widzę, tu jest pewne rozwiązanie tego problemu (na samym dole) Dostępne tylko dla zarejestrowanych użytkowników
Z tłumaczeniem by Google Tłumacz Dostępne tylko dla zarejestrowanych użytkowników

Z tłumaczenia wynika, że problem zapewne zaczął się dziać po instalacji SP1 do Visty.