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

Need BSOD Help


  • Please log in to reply
4 replies to this topic

#1 jtichner

jtichner

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:01:25 PM

Posted 29 October 2011 - 12:37 PM

Here is the analysis from Windows Debugger - can someone help me?? Lenovo T520 that is only a couple of months old...


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`03060670
Debug session time: Sat Oct 29 12:45:55.416 2011 (UTC - 4:00)
System Uptime: 0 days 2:35:04.820
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
---------

0: 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) - The operation completed successfully.

FAULTING_IP:
+3762323161353730
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff80000b9c188 -- (.exr 0xfffff80000b9c188)
ExceptionAddress: fffff80002ea6e38 (nt!KiTryUnwaitThread+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff80000b9c230 -- (.trap 0xfffff80000b9c230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004917c40 rbx=0000000000000000 rcx=fffff8000300de80
rdx=fffffa8009fed140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ea6e38 rsp=fffff80000b9c3c0 rbp=fffff800030105a8
r8=0000000000000100 r9=0000000000000000 r10=00000000000000eb
r11=fffffa80073d82b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`02ea6e38 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e8f5fe to fffff80002e97c10

STACK_TEXT:
fffff800`00b9b268 fffff800`02e8f5fe : fffffa80`0a825300 fffffa80`081d1160 fffff800`00b9b9e0 fffff800`02ec3830 : nt!KeBugCheck
fffff800`00b9b270 fffff800`02ec34fd : fffff800`030a171c fffff800`02fdec30 fffff800`02e1b000 fffff800`00b9c188 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b2a0 fffff800`02ec22d5 : fffff800`02fe20fc fffff800`00b9b318 fffff800`00b9c188 fffff800`02e1b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b2d0 fffff800`02ed3361 : fffff800`00b9c188 fffff800`00b9b9e0 fffff800`00000000 fffff800`03010500 : nt!RtlDispatchException+0x415
fffff800`00b9b9b0 fffff800`02e972c2 : fffff800`00b9c188 78ed98ed`f783fdf7 fffff800`00b9c230 953b87f3`21091fb3 : nt!KiDispatchException+0x135
fffff800`00b9c050 fffff800`02e95bca : 00000000`00000000 00000000`00000000 fffff880`047d8110 fffffa80`04336440 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c230 fffff800`02ea6e38 : fffffa80`0a01b000 fffff800`00b9c4c0 fffff880`054b45c0 00000000`00000003 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c3c0 fffff800`02ef1e6e : fffff800`030105b0 fffff800`030105a8 953b87f3`21091fb3 fffff800`030105a8 : nt!KiTryUnwaitThread+0x28
fffff800`00b9c420 fffff800`02ea343d : fffff800`030105a8 fffffa80`07c0deb0 fffffa80`07c0aec0 00000000`00000102 : nt! ?? ::FNODOBFM::`string'+0xb473
fffff800`00b9c4a0 fffff800`02ea337e : 00000015`aa1afdd5 fffff800`00b9cb18 00000000`000919eb fffff800`03011fe8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9caf0 fffff800`02ea3167 : 00000005`4550a4c8 00000005`000919eb 00000005`4550a450 00000000`000000eb : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e8f96a : fffff800`0300de80 fffff800`0301bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e8f5fe 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
---------

0: 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) - The operation completed successfully.

FAULTING_IP:
+3762323161353730
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff80000b9c188 -- (.exr 0xfffff80000b9c188)
ExceptionAddress: fffff80002ea6e38 (nt!KiTryUnwaitThread+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff80000b9c230 -- (.trap 0xfffff80000b9c230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004917c40 rbx=0000000000000000 rcx=fffff8000300de80
rdx=fffffa8009fed140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ea6e38 rsp=fffff80000b9c3c0 rbp=fffff800030105a8
r8=0000000000000100 r9=0000000000000000 r10=00000000000000eb
r11=fffffa80073d82b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`02ea6e38 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e8f5fe to fffff80002e97c10

STACK_TEXT:
fffff800`00b9b268 fffff800`02e8f5fe : fffffa80`0a825300 fffffa80`081d1160 fffff800`00b9b9e0 fffff800`02ec3830 : nt!KeBugCheck
fffff800`00b9b270 fffff800`02ec34fd : fffff800`030a171c fffff800`02fdec30 fffff800`02e1b000 fffff800`00b9c188 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b2a0 fffff800`02ec22d5 : fffff800`02fe20fc fffff800`00b9b318 fffff800`00b9c188 fffff800`02e1b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b2d0 fffff800`02ed3361 : fffff800`00b9c188 fffff800`00b9b9e0 fffff800`00000000 fffff800`03010500 : nt!RtlDispatchException+0x415
fffff800`00b9b9b0 fffff800`02e972c2 : fffff800`00b9c188 78ed98ed`f783fdf7 fffff800`00b9c230 953b87f3`21091fb3 : nt!KiDispatchException+0x135
fffff800`00b9c050 fffff800`02e95bca : 00000000`00000000 00000000`00000000 fffff880`047d8110 fffffa80`04336440 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c230 fffff800`02ea6e38 : fffffa80`0a01b000 fffff800`00b9c4c0 fffff880`054b45c0 00000000`00000003 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c3c0 fffff800`02ef1e6e : fffff800`030105b0 fffff800`030105a8 953b87f3`21091fb3 fffff800`030105a8 : nt!KiTryUnwaitThread+0x28
fffff800`00b9c420 fffff800`02ea343d : fffff800`030105a8 fffffa80`07c0deb0 fffffa80`07c0aec0 00000000`00000102 : nt! ?? ::FNODOBFM::`string'+0xb473
fffff800`00b9c4a0 fffff800`02ea337e : 00000015`aa1afdd5 fffff800`00b9cb18 00000000`000919eb fffff800`03011fe8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9caf0 fffff800`02ea3167 : 00000005`4550a4c8 00000005`000919eb 00000005`4550a450 00000000`000000eb : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e8f96a : fffff800`0300de80 fffff800`0301bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e8f5fe 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
---------

0: 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) - The operation completed successfully.

FAULTING_IP:
+3762323161353730
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff80000b9c188 -- (.exr 0xfffff80000b9c188)
ExceptionAddress: fffff80002ea6e38 (nt!KiTryUnwaitThread+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff80000b9c230 -- (.trap 0xfffff80000b9c230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004917c40 rbx=0000000000000000 rcx=fffff8000300de80
rdx=fffffa8009fed140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ea6e38 rsp=fffff80000b9c3c0 rbp=fffff800030105a8
r8=0000000000000100 r9=0000000000000000 r10=00000000000000eb
r11=fffffa80073d82b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`02ea6e38 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e8f5fe to fffff80002e97c10

STACK_TEXT:
fffff800`00b9b268 fffff800`02e8f5fe : fffffa80`0a825300 fffffa80`081d1160 fffff800`00b9b9e0 fffff800`02ec3830 : nt!KeBugCheck
fffff800`00b9b270 fffff800`02ec34fd : fffff800`030a171c fffff800`02fdec30 fffff800`02e1b000 fffff800`00b9c188 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b2a0 fffff800`02ec22d5 : fffff800`02fe20fc fffff800`00b9b318 fffff800`00b9c188 fffff800`02e1b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b2d0 fffff800`02ed3361 : fffff800`00b9c188 fffff800`00b9b9e0 fffff800`00000000 fffff800`03010500 : nt!RtlDispatchException+0x415
fffff800`00b9b9b0 fffff800`02e972c2 : fffff800`00b9c188 78ed98ed`f783fdf7 fffff800`00b9c230 953b87f3`21091fb3 : nt!KiDispatchException+0x135
fffff800`00b9c050 fffff800`02e95bca : 00000000`00000000 00000000`00000000 fffff880`047d8110 fffffa80`04336440 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c230 fffff800`02ea6e38 : fffffa80`0a01b000 fffff800`00b9c4c0 fffff880`054b45c0 00000000`00000003 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c3c0 fffff800`02ef1e6e : fffff800`030105b0 fffff800`030105a8 953b87f3`21091fb3 fffff800`030105a8 : nt!KiTryUnwaitThread+0x28
fffff800`00b9c420 fffff800`02ea343d : fffff800`030105a8 fffffa80`07c0deb0 fffffa80`07c0aec0 00000000`00000102 : nt! ?? ::FNODOBFM::`string'+0xb473
fffff800`00b9c4a0 fffff800`02ea337e : 00000015`aa1afdd5 fffff800`00b9cb18 00000000`000919eb fffff800`03011fe8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9caf0 fffff800`02ea3167 : 00000005`4550a4c8 00000005`000919eb 00000005`4550a450 00000000`000000eb : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e8f96a : fffff800`0300de80 fffff800`0301bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e8f5fe 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
---------

0: 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) - The operation completed successfully.

FAULTING_IP:
+3762323161353730
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff80000b9c188 -- (.exr 0xfffff80000b9c188)
ExceptionAddress: fffff80002ea6e38 (nt!KiTryUnwaitThread+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff80000b9c230 -- (.trap 0xfffff80000b9c230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004917c40 rbx=0000000000000000 rcx=fffff8000300de80
rdx=fffffa8009fed140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ea6e38 rsp=fffff80000b9c3c0 rbp=fffff800030105a8
r8=0000000000000100 r9=0000000000000000 r10=00000000000000eb
r11=fffffa80073d82b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`02ea6e38 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e8f5fe to fffff80002e97c10

STACK_TEXT:
fffff800`00b9b268 fffff800`02e8f5fe : fffffa80`0a825300 fffffa80`081d1160 fffff800`00b9b9e0 fffff800`02ec3830 : nt!KeBugCheck
fffff800`00b9b270 fffff800`02ec34fd : fffff800`030a171c fffff800`02fdec30 fffff800`02e1b000 fffff800`00b9c188 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b2a0 fffff800`02ec22d5 : fffff800`02fe20fc fffff800`00b9b318 fffff800`00b9c188 fffff800`02e1b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b2d0 fffff800`02ed3361 : fffff800`00b9c188 fffff800`00b9b9e0 fffff800`00000000 fffff800`03010500 : nt!RtlDispatchException+0x415
fffff800`00b9b9b0 fffff800`02e972c2 : fffff800`00b9c188 78ed98ed`f783fdf7 fffff800`00b9c230 953b87f3`21091fb3 : nt!KiDispatchException+0x135
fffff800`00b9c050 fffff800`02e95bca : 00000000`00000000 00000000`00000000 fffff880`047d8110 fffffa80`04336440 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c230 fffff800`02ea6e38 : fffffa80`0a01b000 fffff800`00b9c4c0 fffff880`054b45c0 00000000`00000003 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c3c0 fffff800`02ef1e6e : fffff800`030105b0 fffff800`030105a8 953b87f3`21091fb3 fffff800`030105a8 : nt!KiTryUnwaitThread+0x28
fffff800`00b9c420 fffff800`02ea343d : fffff800`030105a8 fffffa80`07c0deb0 fffffa80`07c0aec0 00000000`00000102 : nt! ?? ::FNODOBFM::`string'+0xb473
fffff800`00b9c4a0 fffff800`02ea337e : 00000015`aa1afdd5 fffff800`00b9cb18 00000000`000919eb fffff800`03011fe8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9caf0 fffff800`02ea3167 : 00000005`4550a4c8 00000005`000919eb 00000005`4550a450 00000000`000000eb : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e8f96a : fffff800`0300de80 fffff800`0301bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e8f5fe 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
---------

0: 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) - The operation completed successfully.

FAULTING_IP:
+3762323161353730
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR: 0x1E_0

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff80000b9c188 -- (.exr 0xfffff80000b9c188)
ExceptionAddress: fffff80002ea6e38 (nt!KiTryUnwaitThread+0x0000000000000028)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff80000b9c230 -- (.trap 0xfffff80000b9c230)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8004917c40 rbx=0000000000000000 rcx=fffff8000300de80
rdx=fffffa8009fed140 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ea6e38 rsp=fffff80000b9c3c0 rbp=fffff800030105a8
r8=0000000000000100 r9=0000000000000000 r10=00000000000000eb
r11=fffffa80073d82b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`02ea6e38 f0480fba6b4000 lock bts qword ptr [rbx+40h],0 ds:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e8f5fe to fffff80002e97c10

STACK_TEXT:
fffff800`00b9b268 fffff800`02e8f5fe : fffffa80`0a825300 fffffa80`081d1160 fffff800`00b9b9e0 fffff800`02ec3830 : nt!KeBugCheck
fffff800`00b9b270 fffff800`02ec34fd : fffff800`030a171c fffff800`02fdec30 fffff800`02e1b000 fffff800`00b9c188 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b2a0 fffff800`02ec22d5 : fffff800`02fe20fc fffff800`00b9b318 fffff800`00b9c188 fffff800`02e1b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b2d0 fffff800`02ed3361 : fffff800`00b9c188 fffff800`00b9b9e0 fffff800`00000000 fffff800`03010500 : nt!RtlDispatchException+0x415
fffff800`00b9b9b0 fffff800`02e972c2 : fffff800`00b9c188 78ed98ed`f783fdf7 fffff800`00b9c230 953b87f3`21091fb3 : nt!KiDispatchException+0x135
fffff800`00b9c050 fffff800`02e95bca : 00000000`00000000 00000000`00000000 fffff880`047d8110 fffffa80`04336440 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c230 fffff800`02ea6e38 : fffffa80`0a01b000 fffff800`00b9c4c0 fffff880`054b45c0 00000000`00000003 : nt!KiGeneralProtectionFault+0x10a
fffff800`00b9c3c0 fffff800`02ef1e6e : fffff800`030105b0 fffff800`030105a8 953b87f3`21091fb3 fffff800`030105a8 : nt!KiTryUnwaitThread+0x28
fffff800`00b9c420 fffff800`02ea343d : fffff800`030105a8 fffffa80`07c0deb0 fffffa80`07c0aec0 00000000`00000102 : nt! ?? ::FNODOBFM::`string'+0xb473
fffff800`00b9c4a0 fffff800`02ea337e : 00000015`aa1afdd5 fffff800`00b9cb18 00000000`000919eb fffff800`03011fe8 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9caf0 fffff800`02ea3167 : 00000005`4550a4c8 00000005`000919eb 00000005`4550a450 00000000`000000eb : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e8f96a : fffff800`0300de80 fffff800`0301bcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`02e8f5fe 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
---------

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:25 PM

Posted 29 October 2011 - 05:14 PM

Let's try this.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt in Notepad, copy all content and paste it into your next reply.

Louis

#3 jtichner

jtichner
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:01:25 PM

Posted 29 October 2011 - 06:03 PM

==================================================
Dump File : 102911-48079-01.dmp
Crash Time : 10/29/2011 12:47:30 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102911-48079-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 266,288
==================================================

==================================================
Dump File : 102011-65177-01.dmp
Crash Time : 10/20/2011 7:52:30 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffffa80`c2286290
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`02c99299
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102011-65177-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 101511-80543-01.dmp
Crash Time : 10/15/2011 9:58:05 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`03ce4700
Parameter 3 : fffff800`00b9c3d8
Parameter 4 : fffffa80`0a5593e0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101511-80543-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 1,101,776
==================================================

#4 hamluis

hamluis

    Moderator


  • Moderator
  • 56,274 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:12:25 PM

Posted 30 October 2011 - 10:18 AM

I don't see anything I would construe as informative.

Last time you scanned system for malware?

Any operational problems noted other than BSODs? System current with critical updates?

Louis

#5 Allan

Allan

  • BC Advisor
  • 8,629 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:01:25 PM

Posted 30 October 2011 - 10:22 AM

Multiple and varied bsod's can be indicative of anything from malware (as suggested above by hamluis) to a bad motherboard. I suggest a full system scan with BOTH your installed anti virus app AND with MalwareBytes as a starting point.

Also, what is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users