BSOD running Excel 2010

organizator · Feb 1, 2012

Hello,

I had experience these BSOD's when running EXCEL 2010. Is happening once a day or after few days.

The computer is using Windows 7 Professional 64bit with Office 2010 Business 64bit. Both licenses are FPP (full package product).

The computer is an AMD quad core with 8GB ram, gigabyte mobo and gigabyte video. Is having a SSD Corsair sata3. For full computer description I added to the zip file a SIW Freeware report as html file. You can see into the html file all software installed and also specific info regarding hardware. More than can I describe in the topic post. Hope is helpful.

What to do? I hope that you can help me because this computer is running some excel sheets with calculations and is annoying to stop working because of an error.

Thank You in advance.

writhziden · Feb 1, 2012

Code:

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [K:\BSODDmpFiles\organizator\Windows_NT6_BSOD_jcgriff2\013012-10654-01.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 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`0300f000 PsLoadedModuleList = 0xfffff800`03254670
Debug session time: Mon Jan 30 07:14:38.112 2012 (GMT-7)
System Uptime: 0 days 1:52:50.285
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8000309376a, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+1ba )

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

2: 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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000309376a, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KeWaitForSingleObject+1ba
fffff800`0309376a c3              ret

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032be100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030d7588 to fffff8000308bc40

STACK_TEXT:  
fffff880`0a18c288 fffff800`030d7588 : 00000000`0000001e ffffffff`c0000005 fffff800`0309376a 00000000`00000000 : nt!KeBugCheckEx
fffff880`0a18c290 dffff800`0308b2c2 : dffff880`0a18ca68 00000000`00000002 dffff880`0a18cb10 fffffa80`06a1d040 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`0a18c930 dffff880`0a18ca68 : 00000000`00000002 dffff880`0a18cb10 fffffa80`06a1d040 00000000`00000001 : 0xdffff800`0308b2c2
fffff880`0a18c938 00000000`00000002 : dffff880`0a18cb10 fffffa80`06a1d040 00000000`00000001 00000000`00000000 : 0xdffff880`0a18ca68
fffff880`0a18c940 dffff880`0a18cb10 : fffffa80`06a1d040 00000000`00000001 00000000`00000000 00000000`00000000 : 0x2
fffff880`0a18c948 fffffa80`06a1d040 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : 0xdffff880`0a18cb10
fffff880`0a18c950 00000000`00000001 : 00000000`00000000 00000000`00000000 00000000`00000000 20000000`00000000 : 0xfffffa80`06a1d040
fffff880`0a18c958 00000000`00000000 : 00000000`00000000 00000000`00000000 20000000`00000000 20000000`00000000 : 0x1


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!KeWaitForSingleObject+1ba
fffff800`0309376a c3              ret

SYMBOL_NAME:  nt!KeWaitForSingleObject+1ba

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1E_nt!KeWaitForSingleObject+1ba

BUCKET_ID:  X64_0x1E_nt!KeWaitForSingleObject+1ba

Followup: MachineOwner
---------
[*]
Loading Dump File [K:\BSODDmpFiles\organizator\Windows_NT6_BSOD_jcgriff2\013012-9609-01.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 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`0305a000 PsLoadedModuleList = 0xfffff800`0329f670
Debug session time: Mon Jan 30 05:16:59.229 2012 (GMT-7)
System Uptime: 0 days 4:59:50.162
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffffa8008945a00, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4874 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
	the operating system. The only supported way to extend a kernel
	mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffffa8008945a00
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  EXCEL.EXE

CURRENT_IRQL:  2

EXCEPTION_RECORD:  dffff880080206d8 -- (.exr 0xdffff880080206d8)
Cannot read Exception record @ dffff880080206d8

TRAP_FRAME:  dffff88008020780 -- (.trap 0xdffff88008020780)
Unable to read trap frame at dffff880`08020780

LAST_CONTROL_TRANSFER:  from fffff8000312e37a to fffff800030d6c40

STACK_TEXT:  
fffff880`0801f7d8 fffff800`0312e37a : 00000000`000000c4 00000000`00000091 00000000`00000002 fffffa80`08945a00 : nt!KeBugCheckEx
fffff880`0801f7e0 fffff800`03100ef3 : 00000000`00000000 00000000`00000000 00000000`00000003 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4874
fffff880`0801f820 fffff800`03112361 : fffff880`080206d8 fffff880`08020430 fffff880`08020780 dffff880`02fd5180 : nt!RtlDispatchException+0x33
fffff880`0801ff00 dffff800`030d62c2 : dffff880`080206d8 dffffa80`08945a00 dffff880`08020780 dffffa80`08945ac0 : nt!KiDispatchException+0x135
fffff880`080205a0 dffff880`080206d8 : dffffa80`08945a00 dffff880`08020780 dffffa80`08945ac0 20000000`0d53f701 : 0xdffff800`030d62c2
fffff880`080205a8 dffffa80`08945a00 : dffff880`08020780 dffffa80`08945ac0 20000000`0d53f701 20000000`00000000 : 0xdffff880`080206d8
fffff880`080205b0 dffff880`08020780 : dffffa80`08945ac0 20000000`0d53f701 20000000`00000000 20000000`00000000 : 0xdffffa80`08945a00
fffff880`080205b8 dffffa80`08945ac0 : 20000000`0d53f701 20000000`00000000 20000000`00000000 00000000`00000000 : 0xdffff880`08020780
fffff880`080205c0 20000000`0d53f701 : 20000000`00000000 20000000`00000000 00000000`00000000 20000000`00000000 : 0xdffffa80`08945ac0
fffff880`080205c8 20000000`00000000 : 20000000`00000000 00000000`00000000 20000000`00000000 20000000`00000000 : 0x20000000`0d53f701
fffff880`080205d0 20000000`00000000 : 00000000`00000000 20000000`00000000 20000000`00000000 00000000`00000000 : 0x20000000`00000000
fffff880`080205d8 00000000`00000000 : 20000000`00000000 20000000`00000000 00000000`00000000 20000000`00000000 : 0x20000000`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4874
fffff800`0312e37a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4874

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4874

BUCKET_ID:  X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4874

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

[*]
Loading Dump File [K:\BSODDmpFiles\organizator\Windows_NT6_BSOD_jcgriff2\012712-9516-01.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 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`03060000 PsLoadedModuleList = 0xfffff800`032a5670
Debug session time: Fri Jan 27 01:34:35.331 2012 (GMT-7)
System Uptime: 0 days 1:04:51.341
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffff8a008d511b0, dffff8a008d511b0, fffff8a008d511b0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+118b )

Followup: Pool_corruption
---------

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

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a008d511b0, the pool entry being checked.
Arg3: dffff8a008d511b0, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a008d511b0, the read back blink freelist value (should be the same as 2).

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


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000320ab73 to fffff800030dcc40

STACK_TEXT:  
fffff880`073f6b18 fffff800`0320ab73 : 00000000`00000019 00000000`00000003 fffff8a0`08d511b0 dffff8a0`08d511b0 : nt!KeBugCheckEx
fffff880`073f6b20 fffff880`02aa0a4f : fffff880`02a7c110 00000000`00000000 00000000`424d5378 00000000`00000004 : nt!ExDeferredFreePool+0x118b
fffff880`073f6bd0 fffff880`02aa0037 : fffffa80`06fb5010 fffffa80`06fb5478 00000000`00000103 fffff880`02d79110 : mrxsmb10!SmbPseFinalizeOrdinaryExchange+0x163
fffff880`073f6c10 fffff880`02d5f1b1 : fffff880`02d7a278 fffff880`02d7a278 00000000`00000001 fffff880`02d7a278 : mrxsmb10!SmbPseContinueOrdinaryExchange+0x223
fffff880`073f6c80 fffff800`03377fee : fffff880`02d7a278 fffff880`02d7a8e8 fffffa80`06a29b00 fffff800`030d4700 : rdbss!RxpWorkerThreadDispatcher+0x1a1
fffff880`073f6d40 fffff800`030ce5e6 : fffff800`03252e80 fffffa80`0761d660 fffff800`03260cc0 fffff880`01250384 : nt!PspSystemThreadStartup+0x5a
fffff880`073f6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+118b
fffff800`0320ab73 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+118b

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+118b

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+118b

Followup: Pool_corruption
---------

[*]
Loading Dump File [K:\BSODDmpFiles\organizator\Windows_NT6_BSOD_jcgriff2\012512-10280-01.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 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`03066000 PsLoadedModuleList = 0xfffff800`032ab670
Debug session time: Wed Jan 25 00:46:59.821 2012 (GMT-7)
System Uptime: 0 days 0:10:31.088
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000f84780, ffff, 0}

Probably caused by : win32k.sys ( win32k!EngUnmapFontFileFD+8a )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8000f84780
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003152150 to fffff800030e2c40

STACK_TEXT:  
fffff880`09ef2398 fffff800`03152150 : 00000000`0000001a 00000000`00041790 fffffa80`00f84780 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09ef23a0 fffff800`03116569 : 00000000`00000000 00000000`07461fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`09ef2560 fffff800`033fa221 : fffffa80`06dda670 00000000`00000000 fffffa80`07d70f90 fffffa80`07d70f90 : nt!MiRemoveMappedView+0xd9
fffff880`09ef2680 fffff960`000693ee : fffff900`00000000 fffff900`c0092018 fffffa80`00000001 fffff900`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09ef2740 fffff960`000192c6 : fffff900`c388fa20 fffff900`c00926a0 fffff900`00000001 fffff960`00075ef8 : win32k!EngUnmapFontFileFD+0x8a
fffff880`09ef27a0 fffff960`0006567b : fffff960`00019250 fffff900`c00929d0 00000000`00000001 00000000`00000000 : win32k!ttfdSemQueryFontTree+0x76
fffff880`09ef27e0 fffff960`00065527 : fffff880`09ef28f0 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!PDEVOBJ::QueryFontTree+0x63
fffff880`09ef2860 fffff960`000200ae : fffff900`c008a010 00000000`00000000 00000000`00000002 00000000`00000000 : win32k!PFEOBJ::pfdg+0xa3
fffff880`09ef28c0 fffff960`00079cbc : fffff900`c1ccd3a0 fffff880`09ef2b40 fffff880`09ef2a50 fffff880`09ef2b30 : win32k!RFONTOBJ::bRealizeFont+0x46
fffff880`09ef29e0 fffff960`00038190 : 00000000`10018000 fffff900`00000000 fffff880`00000000 fffff960`00000002 : win32k!RFONTOBJ::bInit+0x548
fffff880`09ef2b00 fffff960`00037f6b : 00000000`00000000 00000000`00000001 fffff880`09ef2d60 00000000`000000e8 : win32k!GreGetOutlineTextMetricsInternalW+0x18c
fffff880`09ef2c90 fffff800`030e1ed3 : fffffa80`08460770 00000000`040111c6 00000000`00000020 00000000`000004e4 : win32k!NtGdiGetOutlineTextMetricsInternalW+0x73
fffff880`09ef2ce0 000007fe`ff80575a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0015c208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff80575a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!EngUnmapFontFileFD+8a
fffff960`000693ee 48837c242800    cmp     qword ptr [rsp+28h],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!EngUnmapFontFileFD+8a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5a

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!EngUnmapFontFileFD+8a

BUCKET_ID:  X64_0x1a_41790_win32k!EngUnmapFontFileFD+8a

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

[*]
Loading Dump File [K:\BSODDmpFiles\organizator\Windows_NT6_BSOD_jcgriff2\012412-10077-01.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 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`0305a000 PsLoadedModuleList = 0xfffff800`0329f670
Debug session time: Tue Jan 24 05:53:20.803 2012 (GMT-7)
System Uptime: 0 days 4:19:19.626
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000f47ce, fffff880080815d0, 0}

Probably caused by : win32k.sys ( win32k!EngTextOut+11e )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000f47ce, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880080815d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!EngTextOut+11e
fffff960`000f47ce 440301          add     r8d,dword ptr [rcx]

CONTEXT:  fffff880080815d0 -- (.cxr 0xfffff880080815d0)
rax=fffff900c22311d0 rbx=0000000000000000 rcx=dffff900c1ed6008
rdx=fffff900c209b688 rsi=0000000000000010 rdi=0000000002000017
rip=fffff960000f47ce rsp=fffff88008081fb0 rbp=fffff88008082e00
 r8=0000000000000011  r9=fffff88008082d40 r10=0000000000000000
r11=fffff900c209b680 r12=0000000000000001 r13=0000000000000000
r14=00000000000000d0 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
win32k!EngTextOut+0x11e:
fffff960`000f47ce 440301          add     r8d,dword ptr [rcx] ds:002b:dffff900`c1ed6008=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  EXCEL.EXE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960000f47ce

STACK_TEXT:  
fffff880`08081fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!EngTextOut+0x11e


FOLLOWUP_IP: 
win32k!EngTextOut+11e
fffff960`000f47ce 440301          add     r8d,dword ptr [rcx]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!EngTextOut+11e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5a

STACK_COMMAND:  .cxr 0xfffff880080815d0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!EngTextOut+11e

BUCKET_ID:  X64_0x3B_win32k!EngTextOut+11e

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


[/list]

Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.
Caused by Driver Verifier checking drivers that may be incompatible/conflicting with your system. The driver was not identified.
Possible cause is Drivers...
Possible causes are Memory problems... Drivers...
Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...

Thanks to Dave76 for help understanding possible causes.

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you are overclocking any hardware, please stop.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.

organizator · Feb 3, 2012

Thank you very much for your answer.
I forgot to tell you that I am running TrueCrypt with OS encryption on that drive. When I read your message I thought that TrueCrypt could make this error.
The SSD is SATA3 and is the last gadget on the market. Probably TC didn't upgraded the driver.

I decrypted the OS and left the system working over weekend. If nothing will happen in the next week than this was the case. Otherwise I should investigate further.

Thank you again for your answer and I will come back to left a reply with the results.

writhziden · Feb 3, 2012

Alright, good luck!

BSOD running Excel 2010

organizator

New member

My Computer

writhziden

Closed by request.

My Computer

organizator

New member

My Computer

writhziden

Closed by request.

My Computer