BSOD, first in a long time

[nietzescher]

Help! I just got a BSOD for the first time in over two months, after I finally thought I had a stable system. I suspect the culprit may be a virtual CD drive program, which I have uninstalled. The dump is attached, I'll post more if I get them.

I'm running Windows 7 64-bit Home Premium, and it's the only OS installed on the computer.

Thanks!

 

[CarlTR6]

Hi nietzescher. I am sorry you are having problems.

Error code A, IRQL_NOT_LESS_OR_EQUAL - usual causes are Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\Downloads\082810-29172-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[url=http://msdl.microsoft.com/download/symbols]Symbol information[/url]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Sat Aug 28 16:57:32.894 2010 (GMT-4)
System Uptime: 7 days 0:15:11.639
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
..................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffaad3068ea48, 2, 1, fffff80002a9ecd8}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+6a8 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffaad3068ea48, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a9ecd8, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb50e0
 fffffaad3068ea48 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiUnlinkPageFromLockedList+6a8
fffff800`02a9ecd8 49890cc1        mov     qword ptr [r9+rax*8],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  MsMpEng.exe

TRAP_FRAME:  fffff88006fd3700 -- (.trap 0xfffff88006fd3700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000005a60d1d48 rbx=0000000000000000 rcx=00000000ea063c81
rdx=00000000f1022f8c rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a9ecd8 rsp=fffff88006fd3890 rbp=fffff80002cb71e0
 r8=0000058000000000  r9=fffffa8000000008 r10=0000000000000000
r11=2aaaaaaaaaaaaaab r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiUnlinkPageFromLockedList+0x6a8:
fffff800`02a9ecd8 49890cc1        mov     qword ptr [r9+rax*8],rcx ds:04c0:fffffaad`3068ea48=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a7cca9 to fffff80002a7d740

STACK_TEXT:  
fffff880`06fd35b8 fffff800`02a7cca9 : 00000000`0000000a fffffaad`3068ea48 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06fd35c0 fffff800`02a7b920 : 00000000`00000005 fffffa80`011b3bf0 00000000`00000000 fffff880`00000002 : nt!KiBugCheckDispatch+0x69
fffff880`06fd3700 fffff800`02a9ecd8 : fffffa80`00253aa0 0000000f`ffffffff 7ff00000`00000000 00000000`09a2754a : nt!KiPageFault+0x260
fffff880`06fd3890 fffff800`02aaf587 : 00000000`09a52820 fffff680`00000000 0000007f`00000000 fffff680`0004d290 : nt!MiUnlinkPageFromLockedList+0x6a8
fffff880`06fd3920 fffff800`02a99d26 : 00000000`00000000 00000000`09a52820 fffff880`06fd3a68 fffffa80`06643d78 : nt!MiResolveTransitionFault+0x167
fffff880`06fd39b0 fffff800`02a97743 : ffffffff`ffffffff fffff880`06fd3b40 00000000`00000000 ffffffff`ffffffff : nt!MiDispatchFault+0x946
fffff880`06fd3ac0 fffff800`02a7b82e : 00000000`00000000 00000000`6c19f101 00000000`0a08e001 00000000`1da361d0 : nt!MmAccessFault+0x343
fffff880`06fd3c20 00000000`6c14f797 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0a08e2a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6c14f797


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+6a8
fffff800`02a9ecd8 49890cc1        mov     qword ptr [r9+rax*8],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+6a8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkPageFromLockedList+6a8

BUCKET_ID:  X64_0xA_nt!MiUnlinkPageFromLockedList+6a8

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

The dump blames memory corruption and does not point to a specific cause. It does show that pbfilter.sys
was involved as was usbaapl64.sys .

pbfilter.sys - I do not have the date of this driver; I think it is a part of Peerblock. Read this two articles:

PeerBlock Development: PeerBlock r52 Interim Release

http://www.sevenforums.com/system-security/25386-peerblock-now-has-signed-drivers.html

usbaapl64.sys - I don't have a date for this driver either. I think it is a part of ITunes. Read the following two links and see if they apply. I do not know what version of ITunes you have. A Google search show a lot of problems with this driver.

How to fix iTunes usbaapl64.sys blue screen of death in Vista

Apple Re-Releases iTunes 8 for Windows - BSOD bug fixed by dumping buggy usbaapl.sys and usbaapl64.sys files - Softpedia

I have no idea if these to drivers are up to date; I recommend that you try to update them and the software.

This driver is out of date.

ALSysIO64.sys Sun Apr 19 15:41:04 2009 - Core Temp - CPU temperature monitorCore Temp. While driver may not be a problem, see if there is an update.

Enable Driver Verifier following this tutorial:

Driver Verifier - Enable and Disable

Upload and dumps generated by Driver Verifier.

 

[nietzescher]

Hello,

I just had another crash, but this time it did so without leaving a minidump file. Does this mean anything?

 

[nietzescher]

Hey guys, got another crash. Attached is the dump file. Thanks for your help!

 

[CarlTR6]

Sorry you are still having problems.

Error code 1E, KMODE_EXCEPTION_NOT_HANDLED - usually caused by Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS.

Kernel base = 0xfffff800`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Fri Sep 10 17:51:08.465 2010 (GMT-4)
System Uptime: 5 days 20:49:44.214
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002ac4ce9, 0, 90}

Probably caused by : hardware ( nt!CcFetchDataForRead+149 )

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: fffff80002ac4ce9, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000090, 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!CcFetchDataForRead+149
fffff800`02ac4ce9 847ef9          test    byte ptr [rsi-7],bh

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000090

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb80e0
 0000000000000090 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff880055ff0f8 -- (.exr 0xfffff880055ff0f8)
ExceptionAddress: fffff80002ac4ce9 (nt!CcFetchDataForRead+0x0000000000000149)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000008
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000090
Attempt to read from address 0000000000000090

TRAP_FRAME:  fffff880055ff1a0 -- (.trap 0xfffff880055ff1a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000795f695f rbx=0000000000000000 rcx=fffffffffffffffd
rdx=0000000000001000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ac4ce9 rsp=fffff880055ff330 rbp=00000000ba0f48c3
 r8=0000000000000000  r9=fffffa8002186a00 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!CcFetchDataForRead+0x149:
fffff800`02ac4ce9 847ef9          test    byte ptr [rsi-7],bh ds:ffffffff`fffffff9=??
Resetting default scope

MISALIGNED_IP: 
nt!CcFetchDataForRead+149
fffff800`02ac4ce9 847ef9          test    byte ptr [rsi-7],bh

LAST_CONTROL_TRANSFER:  from fffff80002abaa39 to fffff80002a80740

STACK_TEXT:  
fffff880`055fe928 fffff800`02abaa39 : 00000000`0000001e ffffffff`c0000005 fffff800`02ac4ce9 00000000`00000000 : nt!KeBugCheckEx
fffff880`055fe930 fffff800`02a7fd82 : fffff880`055ff0f8 00000000`00000000 fffff880`055ff1a0 00000000`0000005d : nt!KiDispatchException+0x1b9
fffff880`055fefc0 fffff800`02a7e8fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`055ff1a0 fffff800`02ac4ce9 : fffffa80`040dd990 00000000`00000000 fffff980`33c00000 fffff800`02d36b73 : nt!KiPageFault+0x23a
fffff880`055ff330 fffffa80`040dd990 : 00000000`03239180 0000005d`00040000 fffffa80`00000000 fffffa80`03ccc4d0 : nt!CcFetchDataForRead+0x149
fffff880`055ff390 00000000`03239180 : 0000005d`00040000 fffffa80`00000000 fffffa80`03ccc4d0 fffff8a0`0000005d : 0xfffffa80`040dd990
fffff880`055ff398 0000005d`00040000 : fffffa80`00000000 fffffa80`03ccc4d0 fffff8a0`0000005d 00000000`00000000 : 0x3239180
fffff880`055ff3a0 fffffa80`00000000 : fffffa80`03ccc4d0 fffff8a0`0000005d 00000000`00000000 fffffa80`0611dc90 : 0x5d`00040000
fffff880`055ff3a8 fffffa80`03ccc4d0 : fffff8a0`0000005d 00000000`00000000 fffffa80`0611dc90 00000000`00000000 : 0xfffffa80`00000000
fffff880`055ff3b0 fffff8a0`0000005d : 00000000`00000000 fffffa80`0611dc90 00000000`00000000 00000000`0000005d : 0xfffffa80`03ccc4d0
fffff880`055ff3b8 00000000`00000000 : fffffa80`0611dc90 00000000`00000000 00000000`0000005d fffffa80`0442ad10 : 0xfffff8a0`0000005d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CcFetchDataForRead+149
fffff800`02ac4ce9 847ef9          test    byte ptr [rsi-7],bh

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!CcFetchDataForRead+149

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

2: kd> lmtsmn
start             end                 module name
fffff880`04274000 fffff880`042b2000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f0d000 fffff880`00f64000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02ce6000 fffff880`02d70000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`042d3000 fffff880`042e9000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`09496000 fffff880`0949e000   ALSysIO64 ALSysIO64.sys Sun Apr 19 15:41:04 2009 (49EB7E50)
fffff880`00e4d000 fffff880`00e58000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`042b2000 fffff880`042ba000   ASACPI   ASACPI.sys   Wed Jul 15 23:31:29 2009 (4A5E9F11)
fffff880`0948b000 fffff880`09496000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00e1a000 fffff880`00e23000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e23000 fffff880`00e4d000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`051ae000 fffff880`051ce000   AtihdW76 AtihdW76.sys Thu Jul 15 08:46:49 2010 (4C3F0339)
fffff880`04837000 fffff880`04fa5000   atikmdag atikmdag.sys Tue Aug 03 21:39:08 2010 (4C58C4BC)
fffff880`04046000 fffff880`0408d000   atikmpag atikmpag.sys Tue Aug 03 21:15:45 2010 (4C58BF41)
fffff880`018ff000 fffff880`01906000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02cc4000 fffff880`02cd5000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`0470e000 fffff880`0472c000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
fffff960`00610000 fffff960`00637000   cdd      cdd.dll      unavailable (00000000)
fffff880`0189f000 fffff880`018c9000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`01839000 fffff880`01869000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d42000 fffff880`00da0000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01147000 fffff880`011ba000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`042c3000 fffff880`042d3000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`051dc000 fffff880`051ea000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02ca6000 fffff880`02cc4000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02c97000 fffff880`02ca6000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01235000 fffff880`0124b000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`0503d000 fffff880`0505f000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`051f6000 fffff880`051ff000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`051ea000 fffff880`051f6000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`043be000 fffff880`043d1000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`050c1000 fffff880`050cd000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`0408d000 fffff880`04181000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`04fa5000 fffff880`04feb000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`09563000 fffff880`09599000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`010d5000 fffff880`010e9000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01089000 fffff880`010d5000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   unavailable (00000000)
fffff880`011ba000 fffff880`011f4000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`015ad000 fffff880`015f7000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`04267000 fffff880`04274000   GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`02fec000 fffff800`03035000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04800000 fffff880`04824000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`05065000 fffff880`050c1000   HdAudio  HdAudio.sys  Mon Jul 13 20:06:59 2009 (4A5BCC23)
fffff880`043df000 fffff880`043f8000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`04200000 fffff880`04208080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`043d1000 fffff880`043df000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`04646000 fffff880`0470e000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`01412000 fffff880`0141b000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`019d1000 fffff880`019e7000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`0439e000 fffff880`043ad000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0402f000 fffff880`0403d000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00ba1000 fffff800`00bab000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`050d3000 fffff880`05116000   ks       ks.sys       Mon Jul 13 20:00:31 2009 (4A5BCA9F)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`01582000 fffff880`015ad000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0505f000 fffff880`05064200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`01886000 fffff880`0189b000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`041d7000 fffff880`041fa000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cea000 fffff880`00d2e000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`051ce000 fffff880`051dc000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`043ad000 fffff880`043bc000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04feb000 fffff880`04ff8000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00e00000 fffff880`00e1a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`018c9000 fffff880`018f6000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`047e2000 fffff880`047f2000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
fffff880`0472c000 fffff880`04744000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`04744000 fffff880`04771000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
fffff880`04771000 fffff880`047bf000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
fffff880`047bf000 fffff880`047e2000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
fffff880`01964000 fffff880`0196f000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f6d000 fffff880`00f77000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010e9000 fffff880`01147000   msrpc    msrpc.sys    unavailable (00000000)
fffff880`02c8c000 fffff880`02c97000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01400000 fffff880`01412000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01430000 fffff880`01522000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0430d000 fffff880`04319000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`04319000 fffff880`04348000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`05199000 fffff880`051ae000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02de4000 fffff880`02df3000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02d70000 fffff880`02db5000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01522000 fffff880`01582000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`0196f000 fffff880`01980000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02c80000 fffff880`02c8c000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a10000 fffff800`02fec000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
fffff880`01250000 fffff880`013f3000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`018f6000 fffff880`018ff000   Null     Null.SYS     unavailable (00000000)
fffff880`05182000 fffff880`05199000   nusb3hub nusb3hub.sys Mon Oct 26 10:19:44 2009 (4AE5B000)
fffff880`04000000 fffff880`0402f000   nusb3xhc nusb3xhc.sys Mon Oct 26 10:19:48 2009 (4AE5B004)
fffff880`02dbe000 fffff880`02de4000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00fb7000 fffff880`00fcc000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f84000 fffff880`00fb7000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fe1000 fffff880`00fe8000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fe8000 fffff880`00ff8000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`0600d000 fffff880`060b3000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`05000000 fffff880`0503d000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d2e000 fffff880`00d42000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`042e9000 fffff880`0430d000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04348000 fffff880`04363000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04363000 fffff880`04384000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`04384000 fffff880`0439e000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02c2f000 fffff880`02c80000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`01949000 fffff880`01952000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`01952000 fffff880`0195b000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0195b000 fffff880`01964000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0104c000 fffff880`01086000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`019e7000 fffff880`019ff000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`04210000 fffff880`04267000   Rt64win7 Rt64win7.sys Mon Mar 22 05:57:14 2010 (4BA73EFA)
fffff880`060b3000 fffff880`060be000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`015f7000 fffff880`015ff000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`06165000 fffff880`061fb000   srv      srv.sys      Mon Jun 21 23:21:11 2010 (4C202C27)
fffff880`060fd000 fffff880`06165000   srv2     srv2.sys     Mon Jun 21 23:20:47 2010 (4C202C0F)
fffff880`060be000 fffff880`060eb000   srvnet   srvnet.sys   Mon Jun 21 23:20:32 2010 (4C202C00)
fffff880`043bc000 fffff880`043bd480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`060eb000 fffff880`060fd000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`0199e000 fffff880`019ab000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01980000 fffff880`0199e000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02c1b000 fffff880`02c2f000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`005f0000 fffff960`005fa000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`019ab000 fffff880`019d1000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`09599000 fffff880`095ed000   udfs     udfs.sys     Mon Jul 13 19:23:37 2009 (4A5BC1F9)
fffff880`05116000 fffff880`05128000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`01869000 fffff880`01886000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`04835000 fffff880`04836f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`04824000 fffff880`04835000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`05128000 fffff880`05182000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04181000 fffff880`041d7000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`00f77000 fffff880`00f84000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01906000 fffff880`01914000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01914000 fffff880`01939000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00fcc000 fffff880`00fe1000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00da0000 fffff880`00dfc000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02c00000 fffff880`02c1b000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`01939000 fffff880`01949000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e5a000 fffff880`00efe000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00efe000 fffff880`00f0d000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02db5000 fffff880`02dbe000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000a0000 fffff960`003af000   win32k   win32k.sys   Sat Jun 19 00:31:59 2010 (4C1C483F)
fffff880`042ba000 fffff880`042c3000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00f64000 fffff880`00f6d000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`01800000 fffff880`01821000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`09522000 fffff880`0953d000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`094cf000 fffff880`094d6000   pbfilter.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`094f1000 fffff880`09522000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`094d6000 fffff880`094f1000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`09431000 fffff880`09442000   usbaapl64.sy
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0949e000 fffff880`094cf000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`09442000 fffff880`0945d000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`095ca000 fffff880`095db000   usbaapl64.sy
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`09400000 fffff880`09431000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`095db000 fffff880`095f6000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`094c6000 fffff880`09537000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`09537000 fffff880`09548000   usbaapl64.sy
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`09599000 fffff880`095ca000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`09548000 fffff880`09563000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0949e000 fffff880`094aa000   hiber_atapor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`094aa000 fffff880`094b3000   hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`094b3000 fffff880`094c6000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0941a000 fffff880`0948b000   spsys.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01869000 fffff880`01877000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01877000 fffff880`01883000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01883000 fffff880`0188c000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`0188c000 fffff880`0189f000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000

The dump points to memory corruption. I believe Itunes is involved because this driver is implicated: usbaapl64.sys. I cannot find a date for it because it was unloaded from memory during the crash. See my post above regarding this driver and check out the link. You might try uninstalling Itunes and see how your system does then download and install a new version.

This driver, pbfilter.sys, was also unloaded during the crash. I mentioned this one in my above post. You might try completely uninstalling PeerBlock and reinstalling it. Check the links in the above post.

Did you ever run Driver Verifier? If not, please enable it following this tutorial:

Driver Verifier - Enable and Disable

Upload and dumps generated by Driver Verifier.



Our next step will be to test your RAM after you have run Driver Verifier.

 

[nietzescher]

Hello,

I eventually got frustrated and took a break from computers for a day. I'm still not ready to tackle this problem yet - I have some work to do for grad school - and so I'm running memtest presently, and plan on letting it run overnight. It hasn't detected any problems so far, and I'll let you know the results after I'm done running it.

If memtest doesn't find any problems, I'll enable Driver Verifier and get back to you.

It may be worth noting that I uninstalled both PeerBlock and iTunes; after doing so, the system crashed with even greater frequency. I'm not sure if it would stay stable long enough for me to actually zip up the dumps and upload them to this forum. So, basically, I have no idea what's going on.

But we'll figure this damn thing out! Thanks for your help!

 

[Mycatisbigfoot]

Do you have web cam max and skype running at the same time? I notice it gives me the same irq error

 

[nietzescher]

I don't use either of those programs ever. But thanks for the suggestion!

 

[nietzescher]

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

 

[nietzescher]

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?

 

[CarlTR6]

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.

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.

[FONT=&quot][FONT=Verdana][SIZE=3]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
---------
[/SIZE][/FONT][/FONT]

[FONT=&quot]

Run Memtest again and report your results.
[/FONT]

 

[nietzescher]

memtest ran for 12 hours last night and made 9 passes.... no errors.

The next step is Driver Verifier, I guess? Is that something I could enable before leaving the house for a while, or should I be around to monitor the system while it's running?

I'm wondering, at this point, if my problems might be due to overheating. According to Core Temp, my CPU idles at around 31-33C and occasionally exceeds 60C under load. These temperatures don't seem too extreme, but I'm running out of ideas at this point.

 

[CarlTR6]

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.

 

[nietzescher]

Hey guys,

I'm resurrecting this thread. I decided that I was frustrated with debugging Windows, so I installed Ubuntu on a separate partition and have been using that instead. However, I'd really like to be able to use a stable Win7 install, so I've enabled Driver Verifier (per the instructions in a thread on this site), and I'll upload any dumps I get to this thread.

Should I attempt playing games while Verifier is enabled? Most of my blue screens occur while playing games (leading me to believe that my video card and/or its drivers are the culprit).

 

[nietzescher]

One more thing I should mention: I never experienced any system crashes when running Ubuntu, which leads me to believe that the problem is NOT hardware. But I barely know what I'm talking about, so I could be very wrong.

 

[nietzescher]

Just for fun, here are the dump files for the crashes I've experienced recently. Perhaps they can be useful. The earlier one happened while playing a game; the later one happened while idle, with Chrome and a few other standard programs running.

 

[CarlTR6]

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. http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[nietzescher]

I followed the tutorial, and here's the requested .rar file.

The performance report indicates that I need to run chkdsk, which I will do presently. I will report back with the results.

Thanks for your help!

 

[nietzescher]

That didn't take long: Chkdsk found no problems. I ran it from a command prompt while booted into Windows; should I restart first and run chkdsk before fully booting into Windows?

I imagine the reason that Windows wanted me to run chkdsk in the first place was because I altered the hard drive on which Windows was installed; specifically, I created a new partition (300GB out of a total 1TB) and put Ubuntu on that partition. Could this have somehow damaged the integrity of my Windows install?

 

[Tews]

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

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

GEARAspiWDM.sys Mon May 18 08:17:04 2009 ... CD-ROM Class Filter Driver by Gear Software ... [url=http://www.gearsoftware.com/]GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering[/url]