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: Random BSOD while doing nothing on the computer

03 Mar 2012   #1

Windows 7 Ultimate x64
Random BSOD while doing nothing on the computer

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.

4GB PC3-10667U


My System SpecsSystem Spec
03 Mar 2012   #2

Windows 7 Home Premium 64 Bit

Possible drivers out of date:
TBPANELX64	fffff880`04bf4000	fffff880`04bfc000	Tue Sep 20 05:32:31 2005 (432ff34f)	00012376		TBPANELX64.SYS
EXPERTool by Gainward I suspect that this driver is not compatible with Win7 (and maybe Vista)

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*
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                                    *
*                                                                             *

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.
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.

00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000







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
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

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


fffff800`02c755fe 90              nop


SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


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.
My System SpecsSystem Spec

 Random BSOD while doing nothing on the computer

Thread Tools

Similar help and support threads
Thread Forum
Random BSOD messages, happens at random times while using computer
Hi All, First time poster and hope somebody can help. Have been getting BSOD for a few days now. All at random times, while using the internet, watching movies or just playing music. Have even formatted but of no use. Most recent BSOD was MEMORY MANAGEMENT but its different all the...
BSOD Help and Support
BSOD random when using computer
Sorry wrong place post, i should post on eightforums Hi can anyone help me check what is the cause of my BSOD Thank you so much Bacuaze
BSOD Help and Support
Random BSOD on new computer
I've had random BSOD for a few weeks now, maybe one BSOD every 5 days or so. Not really sure why. EDIT: I crashed again 10-20 minutes after making this post
BSOD Help and Support
Random BSOD on new computer
I've had this computer for about 2 week. The parts are all brand new and a friend of mine built it for me. (He is really good at what he does and I don't doubt his ability) But I've had at least 6 BSOD over the course of the 2 weeks which obviously is not good. Here are my spec: -Windows 7...
BSOD Help and Support
Random BSOD's - New Computer
Hello everyone, I built this computer recently and i've been plagued by random crashes. Sometimes I can go 2 weeks without crashing, other times it will crash back to back. Usually it will just go blue screen and all I can guess is that there is a hardware error somewhere. Any help would be...
BSOD Help and Support

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 21:14.
Twitter Facebook Google+