BSOD, first in a long time

nietzescher said:

While I'm at it, here are some programs I installed within a few days of the first crash (8/28)

- Mathematica (8/26)
- Dropbox (8/25)
- WinDJView (8/24)
- MiKTeX 2.8 (8/24)
- Adobe AIR (8/21)


Are any of those known to cause problems with Windows 7 64-bit?

As far as I know, none of these have a reputation for causing crashes. You can test it by uninstalling all of them and rebooting. If your system runs smooth, one or more of them become suspect. You can then install one at a time and run your system. If you start getting problems; you will know which one caused it.

nietzescher said:

I stopped memtest after six hours, with no errors detected. I know six hours is perhaps not long enough to find errors; if we can't figure it out after I enable Driver Verifier, I'll try memtest again.

Just for fun, here's the dump from when the computer crashed AFTER I uninstalled iTunes and Peerblock (so neither of the drivers for those programs should be implicated, right?).

Memtest needs to make at least seven passes.

Unfortunately, the dump points to a Windows system core driver which is, in all probability, not the cause. The dump indicates a memory problem, c0000005.

Error code 1E, Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Code:

Kernel base = 0xfffff800`02a04000 PsLoadedModuleList = 0xfffff800`02c41e50
Debug session time: Fri Sep 10 21:45:57.608 2010 (GMT-4)
System Uptime: 0 days 0:31:15.623
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
---------

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: 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: 
+5ca8952f019ed7d4
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002f924f8 -- (.exr 0xfffff88002f924f8)
ExceptionAddress: fffff80002a78cd8 (nt!KiTryUnwaitThread+0x0000000000000028)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002f925a0 -- (.trap 0xfffff88002f925a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffff88002f63180
rdx=fffffa8000e62ae8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a78cd8 rsp=fffff88002f92730 rbp=0000000005420000
 r8=0000000000000100  r9=0000000000000000 r10=00000000000000a7
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KiTryUnwaitThread+0x28:
fffff800`02a78cd8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0 ds:0001:00000000`00000040=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a6c46e to fffff80002a74710

STACK_TEXT:  
fffff880`02f915e8 fffff800`02a6c46e : 00000000`00000000 00000000`00000000 fffff880`02f91d60 fffff800`02aa1668 : nt!KeBugCheck
fffff880`02f915f0 fffff800`02a9a40d : fffff800`02c82b7c fffff800`02bbce84 fffff800`02a04000 fffff880`02f924f8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f91620 fffff800`02aa1a90 : fffff800`02bc3a40 fffff880`02f91698 fffff880`02f924f8 fffff800`02a04000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f91650 fffff800`02aae9ef : fffff880`02f924f8 fffff880`02f91d60 fffff880`00000000 fffffa80`05e62a00 : nt!RtlDispatchException+0x410
fffff880`02f91d30 fffff800`02a73d82 : fffff880`02f924f8 02000000`0012d3b0 fffff880`02f925a0 00000000`00000000 : nt!KiDispatchException+0x16f
fffff880`02f923c0 fffff800`02a7268a : 00000000`00000002 fffff880`02f8d000 fffffa80`06cac740 fffffa80`06cac740 : nt!KiExceptionDispatch+0xc2
fffff880`02f925a0 fffff800`02a78cd8 : 00000000`00000001 00000000`0002dc6f fffffa80`062a6f48 fffff880`02f63100 : nt!KiGeneralProtectionFault+0x10a
fffff880`02f92730 fffff800`02accdb0 : fffffa80`05e62ae8 00000000`05420000 00000000`00000000 fffffa80`05e62ae0 : nt!KiTryUnwaitThread+0x28
fffff880`02f92790 fffff800`02a7fd7d : fffffa80`05e62ae0 fffffa80`0636a880 fffffa80`0636a880 00000000`00000102 : nt! ?? ::FNODOBFM::`string'+0xb3d8
fffff880`02f92810 fffff800`02a804be : 00000004`5df56a0e fffff880`02f92e88 00000000`0001d5a7 fffff880`02f66a68 : nt!KiProcessExpiredTimerList+0x6d
fffff880`02f92e60 fffff800`02a7fcb7 : fffff880`02f631c2 fffff880`0001d5a7 00000000`00000000 00000000`000000a7 : nt!KiTimerExpiration+0x1be
fffff880`02f92f00 fffff800`02a7a865 : 0000057c`00000000 fffffa80`06cac740 00000000`00000000 fffff800`02b94da0 : nt!KiRetireDpcList+0x277
fffff880`02f92fb0 fffff800`02a7a67c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0746cbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

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

BUCKET_ID:  X64_0x1E_nt!KiKernelCalloutExceptionHandler+e

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

Run Memtest again and report your results.

When you enable Driver Verifier, use your computer as you normally would. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Upload the dump to us. If it runs for about 36 hours of computer use with a BSOD, turn it off.

Your temps look fine.

Please follow the instructions in this tutorial, run the tool and upload all of the files. I need a deeper look at your system and especially your drivers that I cannot get from just the dumps. Both of your latest dumps blame memory corruption. We need to find the cause of the corruption. https://www.sevenforums.com/crashes-d...tructions.html

Your .dmp file is blaming memory corruption .. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes. Test each stick until you get one that passes with no errors, then test each slot to eliminate any bad slots on the motherboard... Any modules that report errors will need to be replaced..

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002a59700, fffff88002e9df50, 0}

Probably caused by : memory_corruption

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

Update this driver if available..

Code:

GEARAspiWDM.sys Mon May 18 08:17:04 2009 ... CD-ROM Class Filter Driver by Gear Software ... GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering