Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: lot of bsod

15 Sep 2010   #1
grhluna

windows 7
 
 
lot of bsod

im getting lot of bsod on windows 7
ive did maintenance where i could, ive done an extensive memory test and everything showed up ok this system is encrypted with truecrypt
the dump output seems to be different everytime a bit, the 9800gt graphic
card doesnt seem to be able to play games for a long time anymore system would shut down, these bsod occur random
these are the dump outputs ive saved the last days:
the drivers are updated.... first you get memory corruption but ram turned up ok
and the other dump outputs you get different types of drivers
if someone knows the problem please let me know thanks in advance

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


Loading Dump File [H:\Windows\Minidump\090610-26660-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03205000 PsLoadedModuleList = 0xfffff800`03442e50
Debug session time: Mon Sep 6 22:13:56.357 2010 (UTC + 2:00)
System Uptime: 1 days 0:29:39.152
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff88001219031, fffff880031e6e28, fffff880031e6690}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff88001219031, The address that the exception occurred at
Arg3: fffff880031e6e28, Exception Record Address
Arg4: fffff880031e6690, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UITZONDERING} Ongeldige instructie Er is geprobeerd een ongeldige instructie uit te voeren.

FAULTING_IP:
volsnap!VspQueryNtfsFreeSpaceBitmap+311
fffff880`01219031 06 ???

EXCEPTION_RECORD: fffff880031e6e28 -- (.exr 0xfffff880031e6e28)
ExceptionAddress: fffff88001219031 (volsnap!VspQueryNtfsFreeSpaceBitmap+0x0000000000000311)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT: fffff880031e6690 -- (.cxr 0xfffff880031e6690)
rax=0000000005150642 rbx=fffff880031e7170 rcx=0000000000000000
rdx=0000000000000003 rsi=0000000000a347ff rdi=0000000000000000
rip=fffff88001219031 rsp=fffff880031e7060 rbp=0000000000001000
r8=000000000000005e r9=0000000000000004 r10=0000000000000018
r11=fffffa80077d0ffc r12=fffffa80077c1000 r13=ffffffff80002a08
r14=0000000000000004 r15=0000000000000001
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
volsnap!VspQueryNtfsFreeSpaceBitmap+0x311:
fffff880`01219031 06 ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc000001d - {UITZONDERING} Ongeldige instructie Er is geprobeerd een ongeldige instructie uit te voeren.

MISALIGNED_IP:
volsnap!VspQueryNtfsFreeSpaceBitmap+311
fffff880`01219031 06 ???

LAST_CONTROL_TRANSFER: from fffff8800121cfa8 to fffff88001219031

FAILED_INSTRUCTION_ADDRESS:
volsnap!VspQueryNtfsFreeSpaceBitmap+311
fffff880`01219031 06 ???

STACK_TEXT:
fffff880`031e7060 fffff880`0121cfa8 : ffffffff`80002a08 00000000`00000000 fffffa80`0000005e 00000000`00000000 : volsnap!VspQueryNtfsFreeSpaceBitmap+0x311
fffff880`031e7130 fffff880`0121dbb0 : fffffa80`00000000 fffffa80`0430b540 00000000`00000000 00000000`00000000 : volsnap!VspMarkFreeSpaceInBitmap+0x178
fffff880`031e7320 fffff880`0121fcc1 : fffffa80`04acb190 ffffffff`80001fb4 fffffa80`04328a30 00000000`00000000 : volsnap!VspOptimizeDiffAreaFileLocation+0x2a0
fffff880`031e76a0 fffff880`0122f3ed : 00000000`00000000 fffffa80`0412f601 fffff880`031e7870 00000000`00004001 : volsnap!VspOpenDiffAreaFile+0x481
fffff880`031e7820 fffff880`01236250 : fffff880`031e7b80 00000000`00000000 00000000`00000000 00000000`00000004 : volsnap!VspCreateInitialDiffAreaFile+0x1ed
fffff880`031e7870 fffff880`01237256 : fffffa80`04acb190 fffff880`00000000 fffffa80`04acb190 fffffa80`04acb190 : volsnap!VspTryPrepareForSnapshot+0x710
fffff880`031e7b50 fffff880`012152ac : 00000000`00000001 fffffa80`043a86d0 fffffa80`04000bd0 fffffa80`062da710 : volsnap!VspPrepareForSnapshot+0x116
fffff880`031e7c10 fffff800`03571c43 : fffffa80`04acb040 fffff800`0341a5f8 fffffa80`039e1680 fffffa80`039e1680 : volsnap!VspPostWorker+0x2c
fffff880`031e7c40 fffff800`03282961 : fffff800`0341a500 fffff800`03571c20 fffffa80`039e1680 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031e7c70 fffff800`03519c06 : 00000000`00000000 fffffa80`039e1680 00000000`00000080 fffffa80`039a94a0 : nt!ExpWorkerThread+0x111
fffff880`031e7d00 fffff800`03253c26 : fffff880`009e7180 fffffa80`039e1680 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031e7d40 00000000`00000000 : fffff880`031e8000 fffff880`031e2000 fffff880`031e6300 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !volsnap
fffff88001219000-fffff88001219039 58 bytes - volsnap!VspQueryNtfsFreeSpaceBitmap+2e0
[ 44 8b ef 49 c1 e5 04 2b:41 44 4d 69 30 94 33 33 ]
fffff8800121903d-fffff88001219050 20 bytes - volsnap!VspQueryNtfsFreeSpaceBitmap+31d (+0x3d)
[ 3b 44 24 58 0f 82 a6 fe:00 00 00 00 00 00 00 00 ]
fffff88001219054-fffff88001219058 5 bytes - volsnap!VspQueryNtfsFreeSpaceBitmap+334 (+0x17)
[ 48 8b 8c 24 e8:00 00 00 00 00 ]
fffff8800121905c-fffff88001219068 13 bytes - volsnap!VspQueryNtfsFreeSpaceBitmap+33c (+0x08)
[ 49 03 4c 24 08 48 3b ce:00 00 00 00 00 00 00 00 ]
fffff8800121906c-fffff88001219085 26 bytes - volsnap!VspQueryNtfsFreeSpaceBitmap+34c (+0x10)
[ 0f 8c f2 fd ff ff 33 ff:00 00 00 00 00 00 00 00 ]
fffff88001219089-fffff8800121908c 4 bytes - volsnap!VspQueryNtfsFreeSpaceBitmap+369 (+0x1d)
[ 48 81 c4 90:00 00 00 00 ]
fffff88001219090-fffff880012190b3 36 bytes - volsnap!VspQueryNtfsFreeSpaceBitmap+370 (+0x07)
[ 41 5f 41 5e 41 5d 41 5c:00 00 00 00 00 00 00 00 ]
162 errors : !volsnap (fffff88001219000-fffff880012190b3)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

STACK_COMMAND: .cxr 0xfffff880031e6690 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------


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


Loading Dump File [H:\Windows\Minidump\090810-25880-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0325f000 PsLoadedModuleList = 0xfffff800`0349ce50
Debug session time: Wed Sep 8 00:00:01.276 2010 (UTC + 2:00)
System Uptime: 1 days 0:48:17.193
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8800136c0b2, 4800121, fffff88007fb4af0, b}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8800136c0b2, Virtual address for the attempted write.
Arg2: 0000000004800121, PTE contents.
Arg3: fffff88007fb4af0, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xBE

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88007fb4af0 -- (.trap 0xfffff88007fb4af0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000561717 rbx=0000000000000000 rcx=fffffa8003f53a30
rdx=fffffa800667b580 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800136c0ac rsp=fffff88007fb4c80 rbp=0000000000000000
r8=fffffa80049c0e40 r9=000000000000000e r10=fffff88007fb4d70
r11=fffff88007fb4d20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
volsnap! ?? ::OKHAJAOM::`string'+0x1394:
fffff880`0136c0ac 000500000000 add byte ptr [volsnap! ?? ::OKHAJAOM::`string'+0x139a (fffff880`0136c0b2)],al ds:49a0:fffff880`0136c0b2=00
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000334fae2 to fffff800032cf740

STACK_TEXT:
fffff880`07fb4988 fffff800`0334fae2 : 00000000`000000be fffff880`0136c0b2 00000000`04800121 fffff880`07fb4af0 : nt!KeBugCheckEx
fffff880`07fb4990 fffff800`032cd82e : 00000000`00000001 fffffa80`0667b580 fffff880`07f98400 fffff880`014f628d : nt! ?? ::FNODOBFM::`string'+0x4237e
fffff880`07fb4af0 fffff880`0136c0ac : fffffa80`0667b580 00000000`14000001 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`07fb4c80 fffff880`0145c54a : fffffa80`067c49a0 fffff880`07f988b0 fffff880`07f98c60 fffffa80`03f99060 : volsnap! ?? ::OKHAJAOM::`string'+0x1394
fffff880`07fb4cf0 fffff800`032c75c7 : fffff880`05e4c650 00000000`00000000 00000000`00000400 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
fffff880`07fb4d20 fffff800`032c7581 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
fffff880`07f98780 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !volsnap
fffff8800136c000-fffff8800136c021 34 bytes - volsnap! ?? ::OKHAJAOM::`string'+12e8
[ 9a 02 00 00 4c 8d 05 65:41 44 4d 69 30 94 33 33 ]
fffff8800136c024-fffff8800136c039 22 bytes - volsnap! ?? ::OKHAJAOM::`string'+130c (+0x24)
[ 4c 8d 05 65 90 02 00 e9:00 00 a5 aa aa b6 25 35 ]
fffff8800136c03c-fffff8800136c041 6 bytes - volsnap! ?? ::OKHAJAOM::`string'+1324 (+0x18)
[ 85 c0 0f 88 62 02:00 00 00 00 00 00 ]
fffff8800136c044-fffff8800136c049 6 bytes - volsnap! ?? ::OKHAJAOM::`string'+132c (+0x08)
[ 4c 8d 05 45 e6 01:00 00 00 00 00 00 ]
fffff8800136c04b-fffff8800136c04c 2 bytes - volsnap! ?? ::OKHAJAOM::`string'+1333 (+0x07)
[ e9 cb:00 00 ]
fffff8800136c050-fffff8800136c059 10 bytes - volsnap! ?? ::OKHAJAOM::`string'+1338 (+0x05)
[ 48 8b 4f 20 48 8b d3 e8:00 00 00 00 00 00 00 00 ]
fffff8800136c05c-fffff8800136c061 6 bytes - volsnap! ?? ::OKHAJAOM::`string'+1344 (+0x0c)
[ 85 c0 0f 88 46 02:00 00 00 00 00 00 ]
fffff8800136c064-fffff8800136c069 6 bytes - volsnap! ?? ::OKHAJAOM::`string'+134c (+0x08)
[ 48 8b cf e8 84 21:00 00 00 00 00 00 ]
fffff8800136c06c-fffff8800136c074 9 bytes - volsnap! ?? ::OKHAJAOM::`string'+1354 (+0x08)
[ 48 8b d3 48 8b cf e8 09:00 00 00 00 00 00 00 00 ]
fffff8800136c077-fffff8800136c07b 5 bytes - volsnap! ?? ::OKHAJAOM::`string'+135f (+0x0b)
[ 8b f0 e9 4a 02:00 00 00 00 00 ]
fffff8800136c07e-fffff8800136c081 4 bytes - volsnap! ?? ::OKHAJAOM::`string'+1366 (+0x07)
[ 3d 98 c1 53:00 00 00 00 ]
fffff8800136c083-fffff8800136c086 4 bytes - volsnap! ?? ::OKHAJAOM::`string'+136b (+0x05)
[ 0f 87 31 01:00 00 00 00 ]
fffff8800136c089-fffff8800136c08c 4 bytes - volsnap! ?? ::OKHAJAOM::`string'+1371 (+0x06)
[ 3d 98 c1 53:00 00 00 00 ]
fffff8800136c08e-fffff8800136c091 4 bytes - volsnap! ?? ::OKHAJAOM::`string'+1376 (+0x05)
[ 0f 84 14 01:00 00 00 00 ]
fffff8800136c094-fffff8800136c097 4 bytes - volsnap! ?? ::OKHAJAOM::`string'+137c (+0x06)
[ 3d 9c 41 53:00 00 00 00 ]
fffff8800136c099-fffff8800136c09b 3 bytes - volsnap! ?? ::OKHAJAOM::`string'+1381 (+0x05)
[ 0f 87 bf:00 1b 00 ]
fffff8800136c09d-fffff8800136c0a2 6 bytes - volsnap! ?? ::OKHAJAOM::`string'+1385 (+0x04)
[ 00 00 3d 9c 41 53:c4 09 b8 0b 00 00 ]
fffff8800136c0a4-fffff8800136c0a6 3 bytes - volsnap! ?? ::OKHAJAOM::`string'+138c (+0x07)
[ 0f 84 8e:00 00 00 ]
fffff8800136c0aa-fffff8800136c0ad 4 bytes - volsnap! ?? ::OKHAJAOM::`string'+1392 (+0x06)
[ 2d 2c 40 53:00 00 00 05 ]
fffff8800136c0af-fffff8800136c0b3 5 bytes - volsnap! ?? ::OKHAJAOM::`string'+1397 (+0x05)
[ 0f 84 0b fe ff:00 00 00 00 00 ]
147 errors : !volsnap (fffff8800136c000-fffff8800136c0b3)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE

Followup: memory_corruption
---------

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


Loading Dump File [H:\Windows\Minidump\090910-29733-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0321c000 PsLoadedModuleList = 0xfffff800`03459e50
Debug session time: Thu Sep 9 12:46:38.568 2010 (UTC + 2:00)
System Uptime: 1 days 12:28:19.456
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) - De bewerking is voltooid.

FAULTING_IP:
+6332303064356436
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: svchost.exe

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff88005e98888 -- (.exr 0xfffff88005e98888)
ExceptionAddress: fffff88001570000 (volsnap!VspWriteApplicationInfo)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000003
Attempt to read from address 0000000000000003

TRAP_FRAME: fffff88005e98930 -- (.trap 0xfffff88005e98930)
Unable to read trap frame at fffff880`05e98930

LAST_CONTROL_TRANSFER: from fffff8000328446e to fffff8000328c710

STACK_TEXT:
fffff880`05e97978 fffff800`0328446e : 00000000`00000000 fffff880`05e98170 00000000`00000000 fffff800`032e0f6b : nt!KeBugCheck
fffff880`05e97980 fffff800`032b240d : fffff800`03498cf8 fffff800`033dbaf0 fffff800`0321c000 fffff880`05e98888 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`05e979b0 fffff800`032b9a90 : fffff800`033dbae8 fffff880`05e97a28 fffff880`05e98888 fffff800`0321c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`05e979e0 fffff800`032c69ef : fffff880`05e98888 fffff880`05e980f0 fffff880`00000000 fffff8a0`00000004 : nt!RtlDispatchException+0x410
fffff880`05e980c0 fffff800`0328bd82 : fffff880`05e98888 fffffa80`03eca650 fffff880`05e98930 fffffa80`054bb390 : nt!KiDispatchException+0x16f
fffff880`05e98750 fffff800`0328a8fa : 00000000`00000000 fffffa80`03eca650 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`05e98930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`0328446e 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: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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


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


Loading Dump File [H:\Windows\Minidump\091210-27237-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03204000 PsLoadedModuleList = 0xfffff800`03441e50
Debug session time: Sun Sep 12 21:30:35.166 2010 (UTC + 2:00)
System Uptime: 0 days 21:49:55.311
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880456baae9, 8, fffff880456baae9, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40e8b )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff880456baae9, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff880456baae9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ac0e0
fffff880456baae9

FAULTING_IP:
+6332303064356436
fffff880`456baae9 ?? ???

MM_INTERNAL_CODE: 5

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: fffff880031e01b0 -- (.trap 0xfffff880031e01b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8004a9d1a8
rdx=fffffa8004a9c040 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880456baae9 rsp=fffff880031e0340 rbp=000000000004dac0
r8=fffff800033f3400 r9=0000000000000000 r10=0000000000000004
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
fffff880`456baae9 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032f38c1 to fffff80003274740

STACK_TEXT:
fffff880`031e0048 fffff800`032f38c1 : 00000000`00000050 fffff880`456baae9 00000000`00000008 fffff880`031e01b0 : nt!KeBugCheckEx
fffff880`031e0050 fffff800`0327282e : 00000000`00000008 00000005`5849c000 00000000`00000000 00000000`00004000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`031e01b0 fffff880`456baae9 : 00000000`00000000 fffffa80`04a9c040 00000000`0009fc00 00000005`58498000 : nt!KiPageFault+0x16e
fffff880`031e0340 00000000`00000000 : fffffa80`04a9c040 00000000`0009fc00 00000005`58498000 fffff880`00000000 : 0xfffff880`456baae9


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+40e8b
fffff800`032f38c1 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+40e8b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+40e8b

BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+40e8b

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


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


Loading Dump File [H:\Windows\Minidump\091410-24476-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03205000 PsLoadedModuleList = 0xfffff800`03442e50
Debug session time: Tue Sep 14 11:17:26.618 2010 (UTC + 2:00)
System Uptime: 1 days 12:39:31.508
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88001569fff, fffff88009eb5878, fffff88009eb50e0}

Probably caused by : volsnap.sys ( volsnap!VspQueryFileRecord+8f )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88001569fff, The address that the exception occurred at
Arg3: fffff88009eb5878, Exception Record Address
Arg4: fffff88009eb50e0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.

FAULTING_IP:
volsnap!VspQueryFileRecord+8f
fffff880`01569fff 488b4308 mov rax,qword ptr [rbx+8]

EXCEPTION_RECORD: fffff88009eb5878 -- (.exr 0xfffff88009eb5878)
ExceptionAddress: fffff88001569fff (volsnap!VspQueryFileRecord+0x000000000000008f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000003
Attempt to read from address 0000000000000003

CONTEXT: fffff88009eb50e0 -- (.cxr 0xfffff88009eb50e0)
rax=0000000000000000 rbx=fffffa8004366bd0 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff88009eb5b98 rdi=0000000000000400
rip=fffff88001569fff rsp=fffff88009eb5ab0 rbp=fffffa8004a9a040
r8=0000000000000003 r9=00000000c0000800 r10=00000000000133a1
r11=fffff800033efe80 r12=00000000c0000000 r13=fffffa8004a9b190
r14=7fffffffffffffff r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
volsnap!VspQueryFileRecord+0x8f:
fffff880`01569fff 488b4308 mov rax,qword ptr [rbx+8] ds:002b:fffffa80`04366bd8=fffffa8006d825b0
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. Een lees- of schrijfbewerking op het geheugen is mislukt: %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000003

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ad0e0
0000000000000003

FOLLOWUP_IP:
volsnap!VspQueryFileRecord+8f
fffff880`01569fff 488b4308 mov rax,qword ptr [rbx+8]

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER: from fffff8800156a63c to fffff88001569fff

STACK_TEXT:
fffff880`09eb5ab0 fffff880`0156a63c : 00000000`c0000800 00000000`00000400 00000000`00001000 00000000`00001000 : volsnap!VspQueryFileRecord+0x8f
fffff880`09eb5b10 fffff880`01594b37 : 01cb5192`26ab5e9a 00020000`00000002 00000000`00000080 fffffa80`04bda5e0 : volsnap!VspQueryFileExtents+0x15c
fffff880`09eb5b90 fffff880`0159d8e4 : fffffa80`04bda5e0 00000000`00000429 fffffa80`00000003 fffff880`09eb5cd0 : volsnap!VspPopulateHotBlocksBitmap+0x187
fffff880`09eb5cb0 fffff800`03519c06 : fffffa80`00000000 fffffa80`061ee040 00000000`00000080 fffffa80`039a95a0 : volsnap!VspLazyPreCopyOnWriteWorker+0x94
fffff880`09eb5d00 fffff800`03253c26 : fffff880`009e7180 fffffa80`061ee040 fffffa80`0623c5d0 fffff880`0121f534 : nt!PspSystemThreadStartup+0x5a
fffff880`09eb5d40 00000000`00000000 : fffff880`09eb6000 fffff880`09eb0000 fffff880`09eb5760 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: volsnap!VspQueryFileRecord+8f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: volsnap

IMAGE_NAME: volsnap.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc128

STACK_COMMAND: .cxr 0xfffff88009eb50e0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_volsnap!VspQueryFileRecord+8f

BUCKET_ID: X64_0x7E_volsnap!VspQueryFileRecord+8f

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


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


Loading Dump File [H:\Windows\Minidump\091510-25974-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`0348ce50
Debug session time: Wed Sep 15 00:27:15.834 2010 (UTC + 2:00)
System Uptime: 0 days 13:07:26.978
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 : volsnap.sys ( volsnap! ?? ::OKHAJAOM::`string'+1366 )

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) - De bewerking is voltooid.

FAULTING_IP:
+6332303064356436
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: svchost.exe

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff8800935aa48 -- (.exr 0xfffff8800935aa48)
ExceptionAddress: fffff8800135607e (volsnap! ?? ::OKHAJAOM::`string'+0x0000000000001366)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000560038
Attempt to write to address 0000000000560038

TRAP_FRAME: fffff8800935aaf0 -- (.trap 0xfffff8800935aaf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000560038 rbx=0000000000000000 rcx=fffffa8006aac1b0
rdx=fffffa8003f18bd0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800135607e rsp=fffff8800935ac80 rbp=0000000000000000
r8=fffffa800493f920 r9=000000000000000e r10=fffff8800935ad70
r11=fffff8800935ad20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
volsnap! ?? ::OKHAJAOM::`string'+0x1366:
fffff880`0135607e 3d98c15300 cmp eax,53C198h
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032b746e to fffff800032bf710

STACK_TEXT:
fffff880`09359b38 fffff800`032b746e : 00000000`00000001 fffff8a0`0b94a008 00000000`00000000 fffff800`03313f6b : nt!KeBugCheck
fffff880`09359b40 fffff800`032e540d : fffff800`034cbcf8 fffff800`0340eaf0 fffff800`0324f000 fffff880`0935aa48 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`09359b70 fffff800`032eca90 : fffff800`0340eae8 fffff880`09359be8 fffff880`0935aa48 fffff800`0324f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`09359ba0 fffff800`032f99ef : fffff880`0935aa48 fffff880`0935a2b0 fffff880`00000000 fffffa80`06aac1b0 : nt!RtlDispatchException+0x410
fffff880`0935a280 fffff800`032bed82 : fffff880`0935aa48 fffffa80`03f18bd0 fffff880`0935aaf0 fffffa80`03f18f70 : nt!KiDispatchException+0x16f
fffff880`0935a910 fffff800`032bd8fa : 00000000`00000001 fffffa80`03f18bd0 fffff880`09345400 fffff880`014da28d : nt!KiExceptionDispatch+0xc2
fffff880`0935aaf0 fffff880`0135607e : fffffa80`03f18bd0 00000000`14000001 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
fffff880`0935ac80 fffff880`0144054a : fffffa80`06b88010 fffff880`093458b0 fffff880`09345c60 fffffa80`0655f060 : volsnap! ?? ::OKHAJAOM::`string'+0x1366
fffff880`0935acf0 fffff800`032b75c7 : fffff880`093453e0 00000000`00000000 00000000`00000400 00000000`00000000 : Ntfs!NtfsStorageDriverCallout+0x16
fffff880`0935ad20 fffff800`032b7581 : 00000000`00000000 fffffa80`0655f060 fffff880`0935b000 fffff800`032cf01a : nt!KySwitchKernelStackCallout+0x27
fffff880`09345780 fffff800`032cf01a : fffffa80`04063000 fffffa80`0655f060 00000000`00001000 fffff800`00000000 : nt!KiSwitchKernelStackContinue
fffff880`093457a0 fffff880`0144d3d5 : fffff880`01440534 fffff880`093458b0 00000000`00000000 fffffa80`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x29a
fffff880`09345880 fffff880`014b3afd : fffffa80`0429c040 00000000`00000001 00000000`00000001 00000000`00001000 : Ntfs!NtfsCallStorageDriver+0x31
fffff880`093458e0 fffff880`00d836af : fffffa80`0429c040 fffffa80`03f18bd0 00000000`0023b7a0 00000000`0000000c : Ntfs!NtfsFsdDeviceControl+0x10d
fffff880`09345970 fffff800`035da707 : fffffa80`05bd0a00 fffff880`09345c60 fffffa80`03f19000 fffffa80`03f18bd0 : fltmgr!FltpDispatch+0x9f
fffff880`093459d0 fffff800`035daf66 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`09345b00 fffff800`032be993 : 00000000`00000595 00000000`0064cfa8 00000000`0113fc80 0000007f`ffffffff : nt!NtDeviceIoControlFile+0x56
fffff880`09345b70 00000000`778efdca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0064d0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778efdca


STACK_COMMAND: kb

FOLLOWUP_IP:
volsnap! ?? ::OKHAJAOM::`string'+1366
fffff880`0135607e 3d98c15300 cmp eax,53C198h

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: volsnap! ?? ::OKHAJAOM::`string'+1366

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: volsnap

IMAGE_NAME: volsnap.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc128

FAILURE_BUCKET_ID: X64_0x1E_0_volsnap!_??_::OKHAJAOM::_string_+1366

BUCKET_ID: X64_0x1E_0_volsnap!_??_::OKHAJAOM::_string_+1366

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

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


Loading Dump File [H:\Windows\Minidump\091510-27534-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0320c000 PsLoadedModuleList = 0xfffff800`03449e50
Debug session time: Wed Sep 15 12:32:45.363 2010 (UTC + 2:00)
System Uptime: 0 days 10:29:27.252
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) - De bewerking is voltooid.

FAULTING_IP:
+6663636163363733
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: svchost.exe

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff88009e39888 -- (.exr 0xfffff88009e39888)
ExceptionAddress: fffff8800136000b (volsnap!VspWriteApplicationInfo+0x000000000000000b)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME: fffff88009e39930 -- (.trap 0xfffff88009e39930)
Unable to read trap frame at fffff880`09e39930

LAST_CONTROL_TRANSFER: from fffff8000327446e to fffff8000327c710

STACK_TEXT:
fffff880`09e38978 fffff800`0327446e : 00690064`006f004d 00720065`00690066 00000000`00000000 fffff800`032d0f6b : nt!KeBugCheck
fffff880`09e38980 fffff800`032a240d : fffff800`03488cf8 fffff800`033cbaf0 fffff800`0320c000 fffff880`09e39888 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`09e389b0 fffff800`032a9a90 : fffff800`033cbae8 fffff880`09e38a28 fffff880`09e39888 fffff800`0320c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`09e389e0 fffff800`032b69ef : fffff880`09e39888 fffff880`09e390f0 fffff880`00000000 fffff8a0`00000004 : nt!RtlDispatchException+0x410
fffff880`09e390c0 fffff800`0327bd82 : fffff880`09e39888 fffffa80`06bd61b0 fffff880`09e39930 fffffa80`03d4f4a0 : nt!KiDispatchException+0x16f
fffff880`09e39750 fffff800`03279edf : fffff880`09e39930 00000001`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`09e39930 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`0327446e 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: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

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


My System SpecsSystem Spec
.
15 Sep 2010   #2
lorddenis

 

My System SpecsSystem Spec
15 Sep 2010   #3
grhluna

windows 7
 
 

ive followed further instructions on site
64 win7 installed myself bought
hardware couple years
reinstalled no.. couple years
attached files includedAttachment 97770
My System SpecsSystem Spec
.

15 Sep 2010   #4
grhluna

windows 7
 
 

ive switched to a laptop and ppc for now since the system is backedup however this system is used for work
so please let me know if you find out the problem because i could not figure it out thanks in advance
peter
edit: im also offering a full year bed&breakfast with Heidi Klum for the person who can figure out the problem
My System SpecsSystem Spec
07 Oct 2010   #5
grhluna

windows 7
 
 

another forum already solved my problem there were some driver problems
thanks
My System SpecsSystem Spec
Reply

 lot of bsod




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 00:55.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App