Random BSOD while doing nothing on the computer

perishment · 03 Mar 2012

Hi.
3 weeks ago a computer i built startet with bsods and black screens, before it was used for about a year
So i reinstalled windows 7 ultimate x64 retail, checked the rams several times on each slot, tried another powersupply, made stresstest and benchmarks.
So the computer was stable.
Today i brought it back to the owner and right after first start... bsod.
No software changes made and the hardware differences are: monitor (DVI), mouse (USB) and printer (USB).
Now i use another mouse and so far stable.
But please take a look into my dump file, windows was not able to find any problems.

system:
i3-540
H55H-M
4GB PC3-10667U

regards,
Florian

writhziden · 03 Mar 2012

Possible drivers out of date:

Code:

TBPANELX64	fffff880`04bf4000	fffff880`04bfc000	Tue Sep 20 05:32:31 2005 (432ff34f)	00012376		TBPANELX64.SYS

TBPANELX64.SYS

EXPERTool by Gainward I suspect that this driver is not compatible with Win7 (and maybe Vista)

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\perishment\030312-21824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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`02c01000 PsLoadedModuleList = 0xfffff800`02e46670
Debug session time: Sat Mar  3 05:28:45.064 2012 (UTC - 7:00)
System Uptime: 0 days 0:04:07.531
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
---------

3: 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: 
+3637656261633635
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002ffdaf8 -- (.exr 0xfffff88002ffdaf8)
ExceptionAddress: fffff80002c88686 (nt!KeInterlockedClearProcessorAffinityEx+0x0000000000000036)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002ffdba0 -- (.trap 0xfffff88002ffdba0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000003
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c88686 rsp=fffff88002ffdd38 rbp=fffff880083cbdb0
 r8=fffdfa8003dfdbb8  r9=0000000000000008 r10=fffffffffffffff7
r11=fffff88002fd5101 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeInterlockedClearProcessorAffinityEx+0x36:
fffff800`02c88686 498b44c008      mov     rax,qword ptr [r8+rax*8+8] ds:c2c1:fffdfa80`03dfdbc0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c755fe to fffff80002c7dc10

STACK_TEXT:  
fffff880`02ffcbd8 fffff800`02c755fe : 00000000`00000001 fffffa80`03ea3d30 fffff880`02ffd350 fffff800`02ca9830 : nt!KeBugCheck
fffff880`02ffcbe0 fffff800`02ca94fd : fffff800`02e870c8 fffff800`02dc8030 fffff800`02c01000 fffff880`02ffdaf8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffcc10 fffff800`02ca82d5 : fffff800`02dc80fc fffff880`02ffcc88 fffff880`02ffdaf8 fffff800`02c01000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffcc40 fffff800`02cb9361 : fffff880`02ffdaf8 fffff880`02ffd350 fffff880`00000000 fffffa80`0000000e : nt!RtlDispatchException+0x415
fffff880`02ffd320 fffff800`02c7d2c2 : fffff880`02ffdaf8 fffff880`02fd5180 fffff880`02ffdba0 fffff880`02fdffc0 : nt!KiDispatchException+0x135
fffff880`02ffd9c0 fffff800`02c7bbca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02ffdba0 fffff800`02c88686 : fffff800`02c80895 fffffa80`00000003 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffdd38 fffff800`02c80895 : fffffa80`00000003 00000000`00000000 00000000`00000000 fffffa80`06990060 : nt!KeInterlockedClearProcessorAffinityEx+0x36
fffff880`02ffdd40 fffff800`02c75a1d : fffff880`02fd5180 fffff880`02fdffc0 00000000`00000000 fffff880`0f0c7ea0 : nt!SwapContext_PatchXSave+0x94
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x10d


STACK_COMMAND:  kb

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

The .dmp file was fairly inconclusive. 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.

See about the aforementioned driver that may be outdated and is suspected not to be compatible with Windows 7.