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: RAM-Related BSODs, Several Times / Day

08 Aug 2010   #1

Windows 7 64-Bit
 
 
RAM-Related BSODs, Several Times / Day

I have had several crashes per day for the past few months since I installed Windows 7. I've been searching for a fix forever, but cannot figure out how to fix it. I am fairly confident the issues are RAM-related, however I don't think it could be inherently damaged sticks, because I've tested 3-4 sets of working RAM in the machine and I get the same errors.

Here's a highlight reel of some info from my crash dumps:
Probably caused by : afd.sys ( afd!AfdAllocateMdlChain32+fa )
Probably caused by : cdd.dll ( cdd!DrvMovePointer+a )
Probably caused by : memory_corruption
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )

I've got dozens more, but they all revolve around these sorts of memory related errors. I've downloaded PC Wizard and CPU-Z, but I don't really know how to use them to figure out memory configuration issues, etc. Can anyone help me out?

I'd really like to have some more faith in this machine again!

My System SpecsSystem Spec
09 Aug 2010   #2

Windows 7 64-Bit
 
 

Hey guys, I fixed one issue, I think - I found a working driver for the Abit Airpace Wifi adapter. I think that was causing some of the issues.

However, I am still getting BSODs, albeit less frequently. Can anyone help me figure out what the other driver might be that's crashing my system? I thought I was up-to-date now!

My undying gratitude goes out to anyone who responds to this
My System SpecsSystem Spec
09 Aug 2010   #3

Windows 7 Ultimate 32 bit
 
 

I will take a look. Be right back.

I looked at the four most recent dumps. The error codes are all hardware/hardware related. A couple specifically mentions memory corruption. Click on the links to see the usual causes.

BugCheck A - BSOD Index

BugCheck 50 - BSOD Index

BugCheck 3B - BSOD Index

BugCheck 1A - BSOD Index

Here are the dumps. Most of them blame Windows core systems drivers which is very unlikely to be the real cause.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\080310-28220-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Wed Aug  4 00:18:33.460 2010 (GMT-4)
System Uptime: 0 days 13:24:51.879
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {248, 2, 1, fffff80002d2ad9e}

Probably caused by : afd.sys ( afd!AfdAllocateMdlChain32+fa )

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

0: 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: 0000000000000248, 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: fffff80002d2ad9e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f040e0
 0000000000000248 

CURRENT_IRQL:  2

FAULTING_IP: 
nt! ?? ::FNODOBFM::`string'+1192e
fffff800`02d2ad9e f0480fc18148020000 lock xadd qword ptr [rcx+248h],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  fffff880089f15d0 -- (.trap 0xfffff880089f15d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000040 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cec560 rsp=fffff880089f1760 rbp=fffff880089f1ca0
 r8=fffffa800947b668  r9=000000000331d000 r10=0000000000000040
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!MmProbeAndLockPages+0x130:
fffff800`02cec560 410fb601        movzx   eax,byte ptr [r9] ds:7030:00000000`0331d000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ccbb69 to fffff80002ccc600

STACK_TEXT:  
fffff880`089f0e18 fffff800`02ccbb69 : 00000000`0000000a 00000000`00000248 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`089f0e20 fffff800`02cca7e0 : 00000000`00000080  fffffa80`00000000 00000000`00000002 00000000`00000008 :  nt!KiBugCheckDispatch+0x69
fffff880`089f0f60 fffff800`02d2ad9e : fffffa80`0012a560  00000000`00000001 fffffa80`0012a560 00000000`00000080 :  nt!KiPageFault+0x260
fffff880`089f10f0 fffff800`02d8d1dd : fffffa80`00000000  fffff880`089f1240 00000000`00000080 00000000`0006d115 : nt! ??  ::FNODOBFM::`string'+0x1192e
fffff880`089f1150 fffff800`02d3bb53 : 00000000`0000003c  fffff880`089f1240 fffffa80`0a501a18 00000000`00000003 :  nt!MiRemoveLowestPriorityStandbyPage+0x2ad
fffff880`089f11d0 fffff800`02cf2d88 : 00000000`00000000  00000000`0331d000 fffff880`089f15d0 fffff8a0`011f5bb0 : nt! ??  ::FNODOBFM::`string'+0x29d34
fffff880`089f12c0 fffff800`02ce849e : 00000000`00000000  00000000`0331d000 fffff680`000198e8 fffffa80`0a501a18 :  nt!MiResolveProtoPteFault+0x508
fffff880`089f1360 fffff800`02ce6623 : ffffffff`ffffff00  00000000`0331d000 fffff800`02e46e80 fffff880`00000000 :  nt!MiDispatchFault+0x1de
fffff880`089f1470 fffff800`02cca6ee : 00000000`00000000  ffffffff`ffffffff 00000000`63416d00 fffffa80`00d47b70 :  nt!MmAccessFault+0x343
fffff880`089f15d0 fffff800`02cec560 : 00000000`00000000  fffff800`02e5b888 fffffa80`0a501600 00000000`00000801 :  nt!KiPageFault+0x16e
fffff880`089f1760 fffff880`042ef4ba : fffffa80`0947b550  fffff800`02fddd01 00000000`00000001 00000000`03300000 :  nt!MmProbeAndLockPages+0x130
fffff880`089f1870 fffff880`042ecdf4 : ffffffff`00040000  00000000`0b816aac fffffa80`00000001 fffffa80`00000001 :  afd!AfdAllocateMdlChain32+0xfa
fffff880`089f1900 fffff800`02fe86b7 : fffffa80`096f3b70  fffffa80`09b0e010 fffffa80`00000000 fffffa80`00000020 : afd! ??  ::GFJBLGFE::`string'+0xeecc
fffff880`089f1a10 fffff800`02fe8f16 : fffff880`089f1bf8  00000000`00000b84 00000000`00000001 00000000`0b816a84 :  nt!IopXxxControlFile+0x607
fffff880`089f1b40 fffff800`02ccb853 : fffff880`089f1ca0  fffffa80`0976c1c0 fffff880`089f1bf8 00000000`00000000 :  nt!NtDeviceIoControlFile+0x56
fffff880`089f1bb0 00000000`75082dd9 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13
00000000`0035eb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75082dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd!AfdAllocateMdlChain32+fa
fffff880`042ef4ba 4d892f          mov     qword ptr [r15],r13

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  afd!AfdAllocateMdlChain32+fa

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc184

FAILURE_BUCKET_ID:  X64_0xA_afd!AfdAllocateMdlChain32+fa

BUCKET_ID:  X64_0xA_afd!AfdAllocateMdlChain32+fa

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\080610-25818-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Fri Aug  6 09:49:12.765 2010 (GMT-4)
System Uptime: 0 days 0:10:37.591
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff800024ca788, 8, fffff800024ca788, 0}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42877 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff800024ca788, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff800024ca788, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0
 fffff800024ca788 

FAULTING_IP: 
+5b8c952f00b3d810
fffff800`024ca788 ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  havasvc.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005ff5350 -- (.trap 0xfffff88005ff5350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88005ff5e70 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff88005ff5b18 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800024ca788 rsp=fffff88005ff54e0 rbp=fffff80002f593c0
 r8=00000000000002d4  r9=0000000000000003 r10=fffff88005ff5570
r11=fffff80002c1b000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fffff800`024ca788 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d0be54 to fffff80002c8b600

STACK_TEXT:  
fffff880`05ff51e8 fffff800`02d0be54 : 00000000`00000050 fffff800`024ca788 00000000`00000008 fffff880`05ff5350 : nt!KeBugCheckEx
fffff880`05ff51f0 fffff800`02c896ee : 00000000`00000008  fffff880`05ff5600 00000000`00000000 fffffa80`055e51a0 : nt! ??  ::FNODOBFM::`string'+0x42877
fffff880`05ff5350 fffff800`024ca788 : fffff880`05ff6600  00000000`00000000 fffff880`05ff55e8 fffff800`02c63d92 :  nt!KiPageFault+0x16e
fffff880`05ff54e0 fffff880`05ff6600 : 00000000`00000000  fffff880`05ff55e8 fffff800`02c63d92 fffff800`000002d4 :  0xfffff800`024ca788
fffff880`05ff54e8 00000000`00000000 : fffff880`05ff55e8  fffff800`02c63d92 fffff800`000002d4 fffff800`02eacda0 :  0xfffff880`05ff6600


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+42877
fffff800`02d0be54 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+42877

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+42877

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+42877

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\080810-24273-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Sun Aug  8 15:20:30.442 2010 (GMT-4)
System Uptime: 1 days 3:42:53.268
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960007a09da, fffff88003a37af0, 0}

Probably caused by : cdd.dll ( cdd!DrvMovePointer+a )

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

3: 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: fffff960007a09da, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003a37af0, 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: 
cdd!DrvMovePointer+a
fffff960`007a09da 488b5910        mov     rbx,qword ptr [rcx+10h]

CONTEXT:  fffff88003a37af0 -- (.cxr 0xfffff88003a37af0)
rax=00000000450b75c0 rbx=fffff900c00f8010 rcx=0000000000000000
rdx=0000000000000487 rsi=fffff900c011dce8 rdi=0000000000000081
rip=fffff960007a09da rsp=fffff88003a384c0 rbp=0000000000000487
 r8=0000000000000081  r9=0000000000000000 r10=fffffa80091260d0
r11=fffffa800920c720 r12=0000000000000000 r13=0000000000000081
r14=0000000000000001 r15=0000000000000c07
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
cdd!DrvMovePointer+0xa:
fffff960`007a09da 488b5910        mov     rbx,qword ptr [rcx+10h] ds:002b:00000000`00000010=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960007a09da

STACK_TEXT:  
fffff880`03a384c0 00000000`00000000 : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  cdd!DrvMovePointer+0xa


FOLLOWUP_IP: 
cdd!DrvMovePointer+a
fffff960`007a09da 488b5910        mov     rbx,qword ptr [rcx+10h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cdd!DrvMovePointer+a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4bf4408a

STACK_COMMAND:  .cxr 0xfffff88003a37af0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_cdd!DrvMovePointer+a

BUCKET_ID:  X64_0x3B_cdd!DrvMovePointer+a

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


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\072910-21340-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50
Debug session time: Wed Jul 28 22:46:24.608 2010 (GMT-4)
System Uptime: 0 days 2:42:14.636
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000605658, d620000025ed4867, fffff68000603358}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000605658
Arg3: d620000025ed4867
Arg4: fffff68000603358

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  AfterFX.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ce7608 to fffff80002c75600

STACK_TEXT:  
fffff880`095227b8 fffff800`02ce7608 : 00000000`0000001a 00000000`00000403 fffff680`00605658 d6200000`25ed4867 : nt!KeBugCheckEx
fffff880`095227c0 fffff800`02ca6251 : 00000000`00000000  fffff680`00605920 fffffa80`03fd8060 fffff900`c0237ab8 : nt! ??  ::FNODOBFM::`string'+0x31f32
fffff880`09522970 fffff800`02cb6fca : 00000000`00000000  00000000`c0b24fff fffffa80`00000000 fffffa80`03fd8060 :  nt!MiDeleteVirtualAddresses+0x408
fffff880`09522b30 fffff800`02c74853 : ffffffff`ffffffff  00000000`0008e310 00000000`0008e308 00000000`00008000 :  nt!NtFreeVirtualMemory+0x5ca
fffff880`09522c20 00000000`77baff3a : 00000000`00000000  00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77baff3a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+31f32
fffff800`02ce7608 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+31f32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f32

BUCKET_ID:  X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f32

Followup: MachineOwner
---------
One dump specifically points out I looked at the four most recent dumps. The error codes are all hardware/hardware related. A couple specifically mentions memory corruption. Click on the links to see the usual causes.


One of the dumps specifically points out havasvc.exe as being the cause, Hava - Wireless TV tuner from Monsoon multimedia Inc.

Another dump blames AfterFX.exe - After Effects belonging to Adobe After Effects CS3 from Adobe Systems Incorporated .

Let's start trouble shooting by enabling Driver Verifier.

Driver Verifier - Enable and Disable

Upload any dumps created by driver Verifier. and we will go from there.

My System SpecsSystem Spec
.


09 Aug 2010   #4

Windows 7 64-Bit
 
 

Hey Carl, thanks so much for your help - I just enabled the driver verifier and tried to boot up the machine a few times. I got BAD POOL CALLER Bsods before even getting back into Windows. Are those the dumps you're looking for?

I'm System Restoring right now to get back in - hopefully Ill see the dumps that those crashes made.

I'll post those ASAP. Thanks again for taking the time to help!

Edit: Sorry for all the typos in this post - I'm keeping up with the thread from my tablet.

Edit 2: Okay, I'm back on the offending PC. It only made one crash dump - here it is though.
My System SpecsSystem Spec
09 Aug 2010   #5

Windows 7 Ultimate 32 bit
 
 

I also find the following out of date drivers on your system. Older drivers can cause conflicts and memory corruption with Win 7.

The first three are drivers for your TV tuner which was blamed for one of the crashes. I recommend that you update your tuner or uninstall it completely.

Quote:
havabus.sys Fri May 23 07:31:15 2008
HAVATV.sys Fri Oct 03 07:20:29 2008
HavaTV_10.sys Fri Oct 03 07:20:29 2008
nvstor.sys Wed May 20 02:45:37 2009
SCDEmu.SYS Tue Aug 07 11:19:48 2007 (Extremely obsolete)
SI3132.sys Wed Oct 03 14:39:29 2007
SiRemFil.sys Wed Jun 20 15:42:10 2007
SiWinAcc.sys Thu Jun 14 20:02:02 2007
uGuru.sys Wed Sep 20 04:06:44 2006 (Extremely obsolete)
wacmoumonitor.sys Mon Oct 06 14:47:51 2008
wacommousefilter.sys Fri Feb 16 13:12:17 2007
wacomvhid.sys Fri Jul 11 14:16:41 2008
WacomVKHid.sys Thu Feb 15 18:10:54 2007
Update anything 2008 or earlier ASAP. I would guess that these obsolete drivers are responsible for most, if not all, of your crashes. They are certainly not contributing to the stability of your system.

If you can't find current drivers for your Wacom hardware dated July 13, 2009 or later, you are probably going to have to upgrade to something that is certified as Win 7 compatible.

If we can help you locate these drivers please post back and ask.

Turn off Driver Verifier for the time being and work on these obsolete drivers and we will go from there. I will look at the dump you just uploaded.
My System SpecsSystem Spec
09 Aug 2010   #6

Windows 7 Ultimate 32 bit
 
 

The latest dump was a Driver Verifier enabled dump and directly blamed havabus.sys which is one of you obsolete drivers. Completely uninstall your TV tuner. It is definitely part of the problem.

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_080910-29702-01.zip\080910-29702-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50
Debug session time: Mon Aug  9 22:49:37.798 2010 (GMT-4)
System Uptime: 0 days 0:00:19.999
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {9d, dee0, 0, fffff880044de5eb}

Unable to load image \SystemRoot\system32\DRIVERS\havabus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for havabus.sys
*** ERROR: Module load completed but symbols could not be loaded for havabus.sys
Probably caused by : havabus.sys ( havabus+75eb )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000009d, Attempt to allocate pool with a tag that does not contain any letters or digits.
    Using these tags makes tracking pool issues very hard.
Arg2: 000000000000dee0, Incorrect pool tag used.
Arg3: 0000000000000000, Pool type
Arg4: fffff880044de5eb, Caller's address.

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


BUGCHECK_STR:  0xc2_9d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030ff3dc to fffff80002c75600

STACK_TEXT:  
fffff880`033a1248 fffff800`030ff3dc : 00000000`000000c2 00000000`0000009d 00000000`0000dee0 00000000`00000000 : nt!KeBugCheckEx
fffff880`033a1250 fffff800`030ffded : 00000000`c0000023 fffff800`0000dee0 fffff880`033a13c0 fffff8a0`05028d10 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`033a1290 fffff800`03110df8 : 00000000`0000dee0 00000000`00000080 00000000`00000001 00000000`00000000 : nt!ExAllocatePoolSanityChecks+0x9d
fffff880`033a12d0 fffff800`0311109d : 00000000`00000000 fffffa80`04666bb0 00000000`0000dee0 fffffa80`065ee3f0 : nt!VeAllocatePoolWithTagPriority+0x88
fffff880`033a1340 fffff880`044de5eb : 00000000`00000001 00000000`00000000 fffff8a0`0507d5a0 00000000`00000060 : nt!VerifierExAllocatePoolWithTag+0x1d
fffff880`033a1380 00000000`00000001 : 00000000`00000000 fffff8a0`0507d5a0 00000000`00000060 fffff880`033a13c0 : havabus+0x75eb
fffff880`033a1388 00000000`00000000 : fffff8a0`0507d5a0 00000000`00000060 fffff880`033a13c0 fffff8a0`0507d5b0 : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
havabus+75eb
fffff880`044de5eb 4889442448      mov     qword ptr [rsp+48h],rax

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  havabus+75eb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: havabus

IMAGE_NAME:  havabus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4836ab03

FAILURE_BUCKET_ID:  X64_0xc2_9d_VRF_havabus+75eb

BUCKET_ID:  X64_0xc2_9d_VRF_havabus+75eb

Followup: MachineOwner
---------
My System SpecsSystem Spec
09 Aug 2010   #7

Windows 7 64-Bit
 
 

Wow, I didn't realize so much was so out of date!

I uninstalled uGuru, found a Windows 7 Beta driver for my Hava, and an up-to-date Windows 7 driver for my Wacom.

The one thing that I am having difficulty finding is an updated driver for my Silicon Image SiI 3132 SATALink Controller. Could this be causing issues? I'm not quite sure what this Controller even does, to be honest.

Also, if I find that the Hava continues to cause problems, I will uninstall it entirely as per your advice. I figured I would give this beta driver a shot at least, though.

Thanks again for all your help, Carl.
My System SpecsSystem Spec
09 Aug 2010   #8

Windows 7 Ultimate 32 bit
 
 

Good find on the beta driver; it is certainly worth a try. Glad you found updated drivers for your Wacom mouse. Good work!

Here is the link to the Silicon Image support site: www.siliconimage.com/support/ If they do not Win 7 drivers, the software is not compatible with Win 7. You will need to uninstall it and find relacement software compartible with Win 7.

I am signing off for the night. Please post any questions you have or any updates. Someone else on the team will pick it up. See you tomorrow.
My System SpecsSystem Spec
10 Aug 2010   #9

Windows 7 64-Bit
 
 

Left the computer on overnight, just to see if it would blue screen. However, it looks like it was good! I think my problems are solved - thanks so much Carl.
My System SpecsSystem Spec
10 Aug 2010   #10

Windows 7 Ultimate 32 bit
 
 

How that is the news we like to hear! Excellent. Let's wait another day or so before we called it solved; But this is certainly encouraging!
My System SpecsSystem Spec
Reply

 RAM-Related BSODs, Several Times / Day





Thread Tools



Similar help and support threads for2: RAM-Related BSODs, Several Times / Day
Thread Forum
BSOD @ Random Times. Running SQL Server, could be related? BSOD Help and Support
BSOD 2-3 times a week, Dell XPS9100. Possibly related controller errs BSOD Help and Support
Really weirds BSODs, need help i think it's memory related!! BSOD Help and Support
bsods related to ntoskrnl BSOD Help and Support
Random BSODs - RAM related probably BSOD Help and Support
Regular BSODs related to Kernal BSOD Help and Support
Random BSODs related to NetIO.sys 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 02:20 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33