TA STRONA UŻYWA COOKIE. Dowiedz się więcej o celu ich używania. Korzystając ze strony wyrażasz zgodę na używanie cookie, zgodnie z aktualnymi ustawieniami przeglądarki.

Od dnia 25.05.2018 r. na terenie Unii Europejskiej wchodzi w życie Rozporządzenie Parlamentu Europejskiego w sprawie ochrony danych osobowych. Prosimy o zapoznanie się z polityką prywatności oraz regulaminem serwisu [X]
Windows 7 Forum

BSOD // Dmp do przejrzenia

BSOD // Dmp do przejrzenia
« dnia: 05 Listopad 2011, 20:13:23 »
Witam,
Co jakiś czas na laptopie HP Pavilion dv6 3125ew na wersji ultimate wywala mi bsody. Ma ktoś pomysł co może być nie tak?


Cytuj
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.



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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c4e670
Debug session time: Sat Nov  5 10:19:44.129 2011 (UTC + 1:00)
System Uptime: 0 days 17:34:42.619
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - Operacja uko czona pomy lnie.

FAULTING_IP:
+6666643263633562
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff88002f1ba18 -- (.exr 0xfffff88002f1ba18)
ExceptionAddress: fffffa80021a7159
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f1bac0 -- (.trap 0xfffff88002f1bac0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000214bb rbx=0000000000000000 rcx=fffffa8003707410
rdx=fffffa8003718758 rsi=0000000000000000 rdi=0000000000000000
rip=fffffa80021a7159 rsp=fffff88002f1bc58 rbp=fffffa80021a70bc
 r8=0000000000000000  r9=0000000f59964dfc r10=0000000000020a82
r11=fffffa800445d170 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
fffffa80`021a7159 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7d5fe to fffff80002a85c10

STACK_TEXT: 
fffff880`02f1aaf8 fffff800`02a7d5fe : fffffa80`003c5526 00000000`0000000e fffff880`02f1b270 fffff800`02ab1830 : nt!KeBugCheck
fffff880`02f1ab00 fffff800`02ab14fd : fffff800`02c8f488 fffff800`02bcdc8c fffff800`02a09000 fffff880`02f1ba18 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f1ab30 fffff800`02ab02d5 : fffff800`02bd00fc fffff880`02f1aba8 fffff880`02f1ba18 fffff800`02a09000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f1ab60 fffff800`02ac1361 : fffff880`02f1ba18 fffff880`02f1b270 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x415
fffff880`02f1b240 fffff800`02a852c2 : fffff880`02f1ba18 00000000`00000000 fffff880`02f1bac0 fffff880`009e8180 : nt!KiDispatchException+0x135
fffff880`02f1b8e0 fffff800`02a83bca : 00000000`0000002a 00000000`00000000 fffffa80`04347958 fffff880`04c2c1bc : nt!KiExceptionDispatch+0xc2
fffff880`02f1bac0 fffffa80`021a7159 : 00000000`00000000 00000000`000214bb fffff880`02d147f2 00000000`00000010 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f1bc58 00000000`00000000 : 00000000`000214bb fffff880`02d147f2 00000000`00000010 00000000`00000246 : 0xfffffa80`021a7159


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02a7d5fe 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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