This is such an insidious problem, and little has been provided by Microsoft about what we're supposed to do. As soon as I drag a field into a pivot table, the machine blue screens. I am running Windows 7 64 bit and Excel 2013 64 bit via small business premium subscription. 

Can someone speak to what can be done about this? It is a well known problem, but MS has put out nothing meaningful to address it and/or explain when it intends to do something about it. The rep I spoke to by phone was well aware of the problem but said only that MS is aware of the problem. With no further info or ETA on a fix (or even if they EVER plan to fix it). 

I cannot even use pivot tables anymore. I was using a 32 bit machine and it was doing it there. I upgraded to a brand new 64 bit ThinkPad with 64 bit Excel and the problem is as bad as ever. 

Please help. Thank you. 

Hi,

According to your description, we may try to collect the dump file and find the root cause. Please see this article:

http://blogs.technet.com/b/juanand/archive/2011/03/20/analyzing-a-crash-dump-aka-bsod.aspx

You can try to analyze dump by yourself if you would like to, or send it to us via email (ibsofc@microsoft.com)

Regards,

George Zhao
TechNet Community Support

Hi Sir,

I have received the dump and attempt to analysis it

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


Loading Dump File [C:\Users\v-qinlu\Desktop\032315-16723-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols;C:\mysymbols*http://symweb

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.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328d890
Debug session time: Tue Mar 24 00:41:38.188 2015 (UTC + 8:00)
System Uptime: 0 days 1:50:10.421
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004ed94a0, fffff88009baa430, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f4a0 )

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: fffff88004ed94a0, Address of the instruction which caused the bugcheck
Arg3: fffff88009baa430, 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: 
igdkmd64+f4a0
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h

CONTEXT:  fffff88009baa430 -- (.cxr 0xfffff88009baa430;r)
rax=0000000000000700 rbx=ff000000ff000000 rcx=fffffa80069ea000
rdx=fffff88009bab4c0 rsi=fffffa800a0b61b0 rdi=fffff88009bab4c0
rip=fffff88004ed94a0 rsp=fffff88009baae10 rbp=fffffa80069ea000
r8=0000000000000002  r9=fffffa800a0bc438 r10=000000000000000a
r11=fffffa800a0b61f8 r12=0000000000000000 r13=fffffa80177cf010
r14=0000000009bab4c0 r15=fffff8a0037b7000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
igdkmd64+0xf4a0:
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h ds:002b:ff000000`ff000138=????????
Last set context:
rax=0000000000000700 rbx=ff000000ff000000 rcx=fffffa80069ea000
rdx=fffff88009bab4c0 rsi=fffffa800a0b61b0 rdi=fffff88009bab4c0
rip=fffff88004ed94a0 rsp=fffff88009baae10 rbp=fffffa80069ea000
r8=0000000000000002  r9=fffffa800a0bc438 r10=000000000000000a
r11=fffffa800a0b61f8 r12=0000000000000000 r13=fffffa80177cf010
r14=0000000009bab4c0 r15=fffff8a0037b7000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
igdkmd64+0xf4a0:
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h ds:002b:ff000000`ff000138=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88009baafe0 to fffff88004ed94a0

STACK_TEXT:  
fffff880`09baae10 fffff880`09baafe0 : fffff800`030c08af fffff880`009e5180 fffffa80`09b27060 00000000`00000005 : igdkmd64+0xf4a0
fffff880`09baae18 fffff800`030c08af : fffff880`009e5180 fffffa80`09b27060 00000000`00000005 00000000`00000001 : 0xfffff880`09baafe0
fffff880`09baae20 fffff800`0310999c : fffff8a0`037b7000 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KxDispatchInterrupt+0x12f
fffff880`09baaf60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xcc


FOLLOWUP_IP: 
igdkmd64+f4a0
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd64+f4a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52e04948

STACK_COMMAND:  .cxr 0xfffff88009baa430 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_igdkmd64+f4a0

BUCKET_ID:  X64_0x3B_igdkmd64+f4a0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_igdkmd64+f4a0

FAILURE_ID_HASH:  {59121e0a-8083-7c1b-be6f-4c7b1abe726b}

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

1: kd> lmvm igdkmd64
start             end                 module name
fffff880`04eca000 fffff880`052ee000   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Jan 23 06:42:16 2014 (52E04948)
    CheckSum:         004167F1
    ImageSize:        00424000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e

As far as I know, the file igdkmd64.sys could be the Intel Graphics driver,  Please try to update it to test.

Regards,

George Zhao
TechNet Community Support

Hi Sir,

I have received the dump and attempt to analyze it

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


Loading Dump File [C:\Users\v-qinlu\Desktop\032315-16723-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols;C:\mysymbols*http://symweb

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.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`03049000 PsLoadedModuleList = 0xfffff800`0328d890
Debug session time: Tue Mar 24 00:41:38.188 2015 (UTC + 8:00)
System Uptime: 0 days 1:50:10.421
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004ed94a0, fffff88009baa430, 0}

*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : igdkmd64.sys ( igdkmd64+f4a0 )

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: fffff88004ed94a0, Address of the instruction which caused the bugcheck
Arg3: fffff88009baa430, 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: 
igdkmd64+f4a0
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h

CONTEXT:  fffff88009baa430 -- (.cxr 0xfffff88009baa430;r)
rax=0000000000000700 rbx=ff000000ff000000 rcx=fffffa80069ea000
rdx=fffff88009bab4c0 rsi=fffffa800a0b61b0 rdi=fffff88009bab4c0
rip=fffff88004ed94a0 rsp=fffff88009baae10 rbp=fffffa80069ea000
r8=0000000000000002  r9=fffffa800a0bc438 r10=000000000000000a
r11=fffffa800a0b61f8 r12=0000000000000000 r13=fffffa80177cf010
r14=0000000009bab4c0 r15=fffff8a0037b7000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
igdkmd64+0xf4a0:
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h ds:002b:ff000000`ff000138=????????
Last set context:
rax=0000000000000700 rbx=ff000000ff000000 rcx=fffffa80069ea000
rdx=fffff88009bab4c0 rsi=fffffa800a0b61b0 rdi=fffff88009bab4c0
rip=fffff88004ed94a0 rsp=fffff88009baae10 rbp=fffffa80069ea000
r8=0000000000000002  r9=fffffa800a0bc438 r10=000000000000000a
r11=fffffa800a0b61f8 r12=0000000000000000 r13=fffffa80177cf010
r14=0000000009bab4c0 r15=fffff8a0037b7000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
igdkmd64+0xf4a0:
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h ds:002b:ff000000`ff000138=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88009baafe0 to fffff88004ed94a0

STACK_TEXT:  
fffff880`09baae10 fffff880`09baafe0 : fffff800`030c08af fffff880`009e5180 fffffa80`09b27060 00000000`00000005 : igdkmd64+0xf4a0
fffff880`09baae18 fffff800`030c08af : fffff880`009e5180 fffffa80`09b27060 00000000`00000005 00000000`00000001 : 0xfffff880`09baafe0
fffff880`09baae20 fffff800`0310999c : fffff8a0`037b7000 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KxDispatchInterrupt+0x12f
fffff880`09baaf60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xcc


FOLLOWUP_IP: 
igdkmd64+f4a0
fffff880`04ed94a0 f7833801000000000004 test dword ptr [rbx+138h],4000000h

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igdkmd64+f4a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME:  igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52e04948

STACK_COMMAND:  .cxr 0xfffff88009baa430 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_igdkmd64+f4a0

BUCKET_ID:  X64_0x3B_igdkmd64+f4a0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_igdkmd64+f4a0

FAILURE_ID_HASH:  {59121e0a-8083-7c1b-be6f-4c7b1abe726b}

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

1: kd> lmvm igdkmd64
start             end                 module name
fffff880`04eca000 fffff880`052ee000   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Thu Jan 23 06:42:16 2014 (52E04948)
    CheckSum:         004167F1
    ImageSize:        00424000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e

As far as I know, the file igdkmd64.sys could be the Intel Graphics driver,  Please try to update it and test.

Regards,

George Zhao
TechNet Community Support

This is devolving into a typical goose chase. After I sent the DMP file, I did some debugging as well. My results are as follows:

1. Analysis of file I sent you also highlighted igdkmd64.sys as the likely issue. And so I updated these drivers. 
2. Pivot tables immediately caused BSOD again. Next dump file highlighted ntoskrnl.exe as the likely issue. This is an MS NT Kernel & System file.
3. Tried another time, and results also included dxgmms1.sys (MS DirectX Graphics MMS) as the likely problem.

This is a new machine running a new version of Windows 7. Can I expect Microsoft to show any initiative in helping me solve this or am I basically on my own? Please advise. Thank you. 

 

Just tried again right now and the file highlighted once again is ntoskrnl.exe as the likely issue. (MS NT Kernel & System file). Any ideas? Thanks.