Blue screen error: With various Error Code (Help pls)

F

fildoo

New member
Local time
10:20 PM
Messages
12
Hi folks,

Recently I built a new system and installed with Win7 64bit. Since then, I have been encountering various blue screen errors, after installing various software. However, at the basic (without installing any programs) it work fine.

PC Configuration:

Processor: AMD Phenom (TM) II X4 965 Processor 3.40GHZ
Graphic card: ATI HD 5850
RAM: OCZ DDR3 PC1333MHZ 2 GB Gold x 2
HDD: Samsung 1TB Sata2

Error Encounter today:

Problem signature:
 Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
 BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF68000010050
BCP3: B39000003C932867
BCP4: FFFFF6FC80614CCA
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1Not sure if anyone able to assist in this. Been troubleshooting it for a month. Thanks. I also attached the Dump files.
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
Run chkdsk /r from an elevated command prompt. Also, run memtest to test your ram.
 

My Computer

Computer Manufacturer/Model Number
Barebones
OS
Windows 7 Home Premium 64bit
CPU
AMD Phenom II X6 1090T Black Edition Thuban 3.2GHz
Motherboard
MSI NF980-G65 AM3 NVIDIA nForce 980a SLI
Memory
G.SKILL Ripjaws Series 8GB (4 x 2GB) DDR3 (PC3 12800)
Graphics Card(s)
SLI GeForce GTX 480 (Fermi) 1536MB 384-bit GDDR5
Sound Card
onboard
Monitor(s) Displays
Toshiba TV 42'' or 27.5'' widescreen monitor
Screen Resolution
1920x1080 60hz
Hard Drives
2x SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/
PSU
Antec TPQ-1200 1200W Continuous Power with PowerCache
Case
COOLER MASTER HAF 932 RC-932-KKN1-GP Black Steel ATX Full To
Cooling
1 x 140mm rear fan, 3x 230mm Fans (front, top, side)
Keyboard
Logitech G15
Mouse
Logitech MX 518
Internet Speed
13 mb/s down 5.5 mb/s up
Other Info
Main system.. other system is slightly different
  • Like
Reactions: JMH
That is a lot of dumps, 28! I looked at the six most recent and saw five different error codes. A variety of error codes usually indicates hardware or hardware related problem.

STOP 0x0000001A: MEMORY_MANAGEMENT



Usual causes: Device driver, memory, kernel


STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory


STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,


STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure


STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION



Usual causes: System service, Device driver, graphics driver, ?memory
Click to expand...
Look through the usual causes. These are what you will be troubleshooting. Davidxtux has started you on the right path. Follow his suggestions.
CHKDSK /R /F:[FONT=&quot]
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe"
[/FONT][FONT=&quot]
[/FONT]
Click to expand...
[FONT=&quot]

[/FONT] Download a copy of [FONT=&quot]Memtest86+ - Advanced Memory [/FONT][FONT=&quot]Diagnostic Tool[/FONT] and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7[FONT=&quot].[/FONT][FONT=&quot]Boot from the CD, and leave it running for at least 5 passes[/FONT][FONT=&quot].[/FONT]

Here are the dmp analyzes:
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\Temp2_Dump2.zip\063010-17050-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03251000 PsLoadedModuleList = 0xfffff800`0348ee50
Debug session time: Wed Jun 30 09:33:41.236 2010 (GMT-4)
System Uptime: 0 days 6:06:25.922
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 6b05c, 0, 11685c}

Unable to load image \SystemRoot\System32\Drivers\[COLOR=Red]avgldx64.sys[/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000006b05c, page frame number
Arg3: 0000000000000000, current page state
Arg4: 000000000011685c, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033512bc to fffff800032c1600

STACK_TEXT:  
fffff880`080dbb78 fffff800`033512bc : 00000000`0000004e 00000000`00000099 00000000`0006b05c 00000000`00000000 : nt!KeBugCheckEx
fffff880`080dbb80 fffff800`032ab994 : 00000000`00000000 fffffa80`0168bdf0 00000000`00002001 80000000`783f5882 : nt!MiBadShareCount+0x4c
fffff880`080dbbc0 fffff800`035b3203 : fffffa80`04552c10 00000000`00000000 fffffa80`04552c10 00000000`00002001 : nt!MiDeleteSegmentPages+0x404
fffff880`080dbc70 fffff800`032f4e5c : fffffa80`04552c00 00000000`00000000 fffffa80`04552c10 00000000`00000000 : nt!MiSegmentDelete+0x7b
fffff880`080dbcb0 fffff800`035db170 : fffffa80`05e5dbe0 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0x26c
fffff880`080dbdd0 fffff800`035db57b : 00000000`00000000 00000000`053f0000 fffffa80`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b0
fffff880`080dbe90 fffff800`032c0853 : 00000000`0000570f fffff800`0343d480 fffffa80`03a029e0 fffffa80`03ce0720 : nt!NtUnmapViewOfSection+0x5f
fffff880`080dbee0 fffff800`032bcdf0 : fffff880`03e4577a 00000000`80000000 00000000`00000013 00000000`2a677641 : nt!KiSystemServiceCopyEnd+0x13
fffff880`080dc078 fffff880`03e4577a : 00000000`80000000 00000000`00000013 00000000`2a677641 00000000`00000001 : nt!KiServiceLinkage
fffff880`080dc080 00000000`80000000 : 00000000`00000013 00000000`2a677641 00000000`00000001 fffff880`03e80fa0 : [COLOR=Red]avgldx64[/COLOR]+0x277a
fffff880`080dc088 00000000`00000013 : 00000000`2a677641 00000000`00000001 fffff880`03e80fa0 fffff880`03e68eb5 : 0x80000000
fffff880`080dc090 00000000`2a677641 : 00000000`00000001 fffff880`03e80fa0 fffff880`03e68eb5 00000000`00000020 : 0x13
fffff880`080dc098 00000000`00000001 : fffff880`03e80fa0 fffff880`03e68eb5 00000000`00000020 fffff8a0`08a0a0a8 : 0x2a677641
fffff880`080dc0a0 fffff880`03e80fa0 : fffff880`03e68eb5 00000000`00000020 fffff8a0`08a0a0a8 00000000`000493e0 : 0x1
fffff880`080dc0a8 fffff880`03e68eb5 : 00000000`00000020 fffff8a0`08a0a0a8 00000000`000493e0 fffff880`03e80fa0 : [COLOR=Red]avgldx64[/COLOR]+0x3dfa0
fffff880`080dc0b0 00000000`00000020 : fffff8a0`08a0a0a8 00000000`000493e0 fffff880`03e80fa0 fffff880`080dc4b0 : [COLOR=Red]avgldx64[/COLOR]+0x25eb5
fffff880`080dc0b8 fffff8a0`08a0a0a8 : 00000000`000493e0 fffff880`03e80fa0 fffff880`080dc4b0 fffff880`080dc110 : 0x20
fffff880`080dc0c0 00000000`000493e0 : fffff880`03e80fa0 fffff880`080dc4b0 fffff880`080dc110 00000000`00000000 : 0xfffff8a0`08a0a0a8
fffff880`080dc0c8 fffff880`03e80fa0 : fffff880`080dc4b0 fffff880`080dc110 00000000`00000000 00000000`00000000 : 0x493e0
fffff880`080dc0d0 fffff880`080dc4b0 : fffff880`080dc110 00000000`00000000 00000000`00000000 00000000`0000004c : [COLOR=Red]avgldx64[/COLOR]+0x3dfa0
fffff880`080dc0d8 fffff880`080dc110 : 00000000`00000000 00000000`00000000 00000000`0000004c fffff880`03e5cf49 : 0xfffff880`080dc4b0
fffff880`080dc0e0 00000000`00000000 : 00000000`00000000 00000000`0000004c fffff880`03e5cf49 00000000`00000000 : 0xfffff880`080dc110


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`033512bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------
[FONT=&quot][FONT=Verdana][SIZE=3] 

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\Temp2_Dump2.zip\063010-29390-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`0305ce50
Debug session time: Wed Jun 30 03:25:46.168 2010 (GMT-4)
System Uptime: 0 days 0:10:16.853
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fc30bf, fffff8800998adf0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )

Followup: Pool_corruption
---------

0: 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: fffff80002fc30bf, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800998adf0, 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: 
nt!ExDeferredFreePool+233
fffff800`02fc30bf 4c395008        cmp     qword ptr [rax+8],r10

CONTEXT:  fffff8800998adf0 -- (.cxr 0xfffff8800998adf0)
rax=0065006300720075 rbx=0000000000000000 rcx=fffffa8003965190
rdx=fffff8a00ccb8c50 rsi=0000000000000000 rdi=fffff8a00e356c00
rip=fffff80002fc30bf rsp=fffff8800998b7c0 rbp=0000000000000000
 r8=006f0073006f0072  r9=fffff8a00ccb93c0 r10=fffff8a00ccb93d0
r11=0000000000000001 r12=fffffa8003964500 r13=0000000000000000
r14=0000000000000003 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ExDeferredFreePool+0x233:
fffff800`02fc30bf 4c395008        cmp     qword ptr [rax+8],r10 ds:002b:00650063`0072007d=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  avgchsva.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002fc30bf

STACK_TEXT:  
fffff880`0998b7c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x233


FOLLOWUP_IP: 
nt!ExDeferredFreePool+233
fffff800`02fc30bf 4c395008        cmp     qword ptr [rax+8],r10

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExDeferredFreePool+233

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .cxr 0xfffff8800998adf0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233

BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233

Followup: Pool_corruption
---------


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\Temp2_Dump2.zip\070110-14617-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`0308fe50
Debug session time: Wed Jun 30 16:21:47.817 2010 (GMT-4)
System Uptime: 0 days 0:50:32.503
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88007ba8228, fffff88007ba7a90, fffff80002e7f217}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCachedRead+180 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88007ba8228
Arg3: fffff88007ba7a90
Arg4: fffff80002e7f217

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


EXCEPTION_RECORD:  fffff88007ba8228 -- (.exr 0xfffff88007ba8228)
ExceptionAddress: fffff80002e7f217 (nt!MiInvalidateCollidedIos+0x0000000000000047)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88007ba7a90 -- (.cxr 0xfffff88007ba7a90)
rax=006100730070005c rbx=0000000000000000 rcx=fffffa80045277a0
rdx=0000000000000000 rsi=fffffa80045277a0 rdi=ffffffffffffffff
rip=fffff80002e7f217 rsp=fffff88007ba8460 rbp=fffffa80045277a0
 r8=003400360057004f  r9=fffffa8005527890 r10=fffffa80045277a0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=0000058000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiInvalidateCollidedIos+0x47:
fffff800`02e7f217 4c8900          mov     qword ptr [rax],r8 ds:002b:00610073`0070005c=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fa0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCachedRead+180
fffff880`0125afc0 84c0            test    al,al

FAULTING_IP: 
nt!MiInvalidateCollidedIos+47
fffff800`02e7f217 4c8900          mov     qword ptr [rax],r8

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff80002eb3cf6 to fffff80002e7f217

STACK_TEXT:  
fffff880`07ba8460 fffff800`02eb3cf6 : 00000000`00000000 fffffa80`045277a0 00000000`00000000 fffffa80`06300800 : nt!MiInvalidateCollidedIos+0x47
fffff880`07ba84b0 fffff800`02f06c8c : fffffa80`045277a0 00000000`00000000 00000000`00000000 00000000`00000052 : nt!MiWaitForInPageComplete+0xa4a
fffff880`07ba8590 fffff800`031e090b : 00000000`00000000 00000000`00052c00 fffffa80`03cdef20 00000000`000fd4e0 : nt!CcFetchDataForRead+0x20c
fffff880`07ba85f0 fffff880`0125afc0 : fffff8a0`00000000 fffff880`00000005 fffffa80`0002d400 fffff880`012ae001 : nt!CcCopyRead+0x16b
fffff880`07ba86b0 fffff880`0125f303 : 00000000`00052c00 fffff8a0`0173f670 fffff880`07ba88e0 fffff880`07ba87d8 : Ntfs!NtfsCachedRead+0x180
fffff880`07ba8710 fffff880`01261f78 : fffffa80`059767e0 fffffa80`03dd2780 fffff880`07ba8801 fffffa80`05cfe900 : Ntfs!NtfsCommonRead+0x583
fffff880`07ba88b0 fffff880`0107a23f : fffffa80`03dd2b20 fffffa80`03dd2780 fffffa80`05cfe930 00000000`00000001 : Ntfs!NtfsFsdRead+0x1b8
fffff880`07ba8960 fffff880`010786df : fffffa80`04906de0 00000000`00000001 fffffa80`04906d00 fffffa80`03dd2780 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`07ba89f0 fffff800`031d9c49 : 00000000`00000000 fffffa80`03cdef20 00000000`00000001 fffffa80`03dd2780 : fltmgr!FltpDispatch+0xcf
fffff880`07ba8a50 fffff800`031e1453 : fffffa80`03cdef20 fffffa80`03cdef20 fffffa80`03cdef20 fffff880`009e7180 : nt!IopSynchronousServiceTail+0xf9
fffff880`07ba8ac0 fffff800`02ec1853 : 00000000`0000016c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
fffff880`07ba8bb0 00000000`74132dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001be5d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74132dd9


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Ntfs!NtfsCachedRead+180

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88007ba7a90 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCachedRead+180

BUCKET_ID:  X64_0x24_Ntfs!NtfsCachedRead+180

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\Temp2_Dump2.zip\070110-14820-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`03095e50
Debug session time: Wed Jun 30 15:30:44.737 2010 (GMT-4)
System Uptime: 0 days 0:38:50.048
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880079caa8c, fffff880031c3eb8, fffff880031c3720}

Probably caused by : [COLOR=Red]avgldx64.sys[/COLOR] ( avgldx64+28a8c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880079caa8c, The address that the exception occurred at
Arg3: fffff880031c3eb8, Exception Record Address
Arg4: fffff880031c3720, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
avgldx64+28a8c
fffff880`079caa8c 458b442404      mov     r8d,dword ptr [r12+4]

EXCEPTION_RECORD:  fffff880031c3eb8 -- (.exr 0xfffff880031c3eb8)
ExceptionAddress: fffff880079caa8c (avgldx64+0x0000000000028a8c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000063eb62c
Attempt to read from address 00000000063eb62c

CONTEXT:  fffff880031c3720 -- (.cxr 0xfffff880031c3720)
rax=00000000052b0008 rbx=fffff880079dffa0 rcx=000000000113b620
rdx=0000000000632440 rsi=000000000000002c rdi=0000000000003757
rip=fffff880079caa8c rsp=fffff880031c40f0 rbp=000000000063246c
 r8=0000000000000000  r9=0000000000000000 r10=305a28f2f699a73f
r11=0000000000000000 r12=00000000063eb628 r13=0000000000a4e4c4
r14=0000000000a87626 r15=000000000000002c
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
avgldx64+0x28a8c:
fffff880`079caa8c 458b442404      mov     r8d,dword ptr [r12+4] ds:002b:00000000`063eb62c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000063eb62c

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031000e0
 00000000063eb62c 

FOLLOWUP_IP: 
avgldx64+28a8c
fffff880`079caa8c 458b442404      mov     r8d,dword ptr [r12+4]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880079dffa0 to fffff880079caa8c

STACK_TEXT:  
fffff880`031c40f0 fffff880`079dffa0 : fffff880`079dffa0 00000000`052b0008 fffff8a0`07976018 00000000`052b0008 : avgldx64+0x28a8c
fffff880`031c40f8 fffff880`079dffa0 : 00000000`052b0008 fffff8a0`07976018 00000000`052b0008 00000000`00560723 : avgldx64+0x3dfa0
fffff880`031c4100 00000000`052b0008 : fffff8a0`07976018 00000000`052b0008 00000000`00560723 00152410`00000000 : avgldx64+0x3dfa0
fffff880`031c4108 fffff8a0`07976018 : 00000000`052b0008 00000000`00560723 00152410`00000000 00000000`052b0008 : 0x52b0008
fffff880`031c4110 00000000`052b0008 : 00000000`00560723 00152410`00000000 00000000`052b0008 00000000`00632440 : 0xfffff8a0`07976018
fffff880`031c4118 00000000`00560723 : 00152410`00000000 00000000`052b0008 00000000`00632440 00000000`05820008 : 0x52b0008
fffff880`031c4120 00152410`00000000 : 00000000`052b0008 00000000`00632440 00000000`05820008 00000000`057b77d8 : 0x560723
fffff880`031c4128 00000000`052b0008 : 00000000`00632440 00000000`05820008 00000000`057b77d8 00000000`00000000 : 0x152410`00000000
fffff880`031c4130 00000000`00632440 : 00000000`05820008 00000000`057b77d8 00000000`00000000 fffff880`031c4370 : 0x52b0008
fffff880`031c4138 00000000`05820008 : 00000000`057b77d8 00000000`00000000 fffff880`031c4370 fffff880`079c8ec9 : 0x632440
fffff880`031c4140 00000000`057b77d8 : 00000000`00000000 fffff880`031c4370 fffff880`079c8ec9 00000000`00000000 : 0x5820008
fffff880`031c4148 00000000`00000000 : fffff880`031c4370 fffff880`079c8ec9 00000000`00000000 00000000`00000000 : 0x57b77d8


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  avgldx64+28a8c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: [COLOR=Red]avgldx64[/COLOR]

IMAGE_NAME:  [COLOR=Red]avgldx64.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4b737eff

STACK_COMMAND:  .cxr 0xfffff880031c3720 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_[COLOR=Red]avgldx64[/COLOR]+28a8c

BUCKET_ID:  X64_0x7E_avgldx64+28a8c

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

[/SIZE][/FONT][/FONT][FONT=&quot][FONT=Verdana][SIZE=3]
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\Temp2_Dump2.zip\070110-19172-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Wed Jun 30 14:51:17.709 2010 (GMT-4)
System Uptime: 0 days 5:17:04.005
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, a8e67, 0, a9167}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000a8e67, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000a9167, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchFilterHo

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f502bc to fffff80002ec0600

STACK_TEXT:  
fffff880`07c11108 fffff800`02f502bc : 00000000`0000004e 00000000`00000099 00000000`000a8e67 00000000`00000000 : nt!KeBugCheckEx
fffff880`07c11110 fffff800`02f32937 : fffff880`02fd5180 fffff800`02ef4326 00000000`00000000 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`07c11150 fffff800`02e94b43 : fffffa80`03d47060 fffff700`000002c0 0000007f`fffffff8 fffff8a0`0326fc28 : nt! ?? ::FNODOBFM::`string'+0x3227e
fffff880`07c111e0 fffff800`02e935a2 : fffffa80`03d47060 fffffa80`0000006f 00000000`000000dd fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`07c11a90 fffff800`031a6c4f : fffff8a0`082269a0 00000000`00000001 00000000`00000000 fffffa80`03fc6340 : nt!MmCleanProcessAddressSpace+0x96
fffff880`07c11ae0 fffff800`0317e6eb : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`07c11ba0 fffff800`02ebf853 : fffffa80`03d47060 00000000`00000000 00000000`00153b01 fffffa80`03fc6340 : nt!NtTerminateProcess+0x25b
fffff880`07c11c20 00000000`775e017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000afd98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e017a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f502bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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\Temp2_Dump2.zip\070510-17456-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Mon Jul  5 03:12:30.128 2010 (GMT-4)
System Uptime: 0 days 0:31:45.813
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000010050, b39000003c932867, fffff6fc80614cca}

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

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

1: 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: fffff68000010050
Arg3: b39000003c932867
Arg4: fffff6fc80614cca

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f49608 to fffff80002ed7600

STACK_TEXT:  
fffff880`0a4cb7b8 fffff800`02f49608 : 00000000`0000001a 00000000`00000403 fffff680`00010050 b3900000`3c932867 : nt!KeBugCheckEx
fffff880`0a4cb7c0 fffff800`02f08251 : 00000000`00000000 fffff680`00010440 fffffa80`063bdb30 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x31f32
fffff880`0a4cb970 fffff800`02f18fca : 00000000`00000000 00000000`02088fff fffffa80`00000000 fffffa80`063bdb30 : nt!MiDeleteVirtualAddresses+0x408
fffff880`0a4cbb30 fffff800`02ed6853 : ffffffff`ffffffff 00000000`0302db90 00000000`0302db58 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0a4cbc20 00000000`76de009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0302dac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76de009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+31f32
fffff800`02f49608 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
---------

[/SIZE][/FONT][/FONT]
[FONT=&quot]

Three of these dumps show that AVG antivirus was involved in the crash and one points to AVG as the direct cause. AVG is known to cause BSOD's on some Win 7 systems. I suggest you uninstall AVG using the uninstall tool > [/FONT] Info > Tool (32bit) - Tool (64 bit)[FONT=&quot] Replace it with Microsoft Security Essentials while you are troubleshooting.

[/FONT]
 

My Computer

Computer Manufacturer/Model Number
Home built
OS
Windows 7 Ultimate 32 bit
CPU
Intel(R) Pentium(R) 4 CPU 3.00GHz
Motherboard
ASUS P4P800-VM Motherboard Chipset: Intel 865G + ICH5
Memory
2.50 GB RAM
Graphics Card(s)
NVIDIA GeForce 7600 GS
Sound Card
SoundMax Integrated Digital Audio (Chip)
Monitor(s) Displays
ViewSonic VX 1962 wm
Screen Resolution
1680 X 1050
Hard Drives
Seagate Barracuda 7200.10 80 GB
ST380215A ATA Device 18.6 GB
Western Digital "My Book" external hard drive 750 GB
Cooling
Fan based
Keyboard
Microsoft Comfort Curve Keyboard 2000 v10 USB
Mouse
Logitec optic USB
Internet Speed
3.01 Mb/s download 0.64 Mb/s upload
Thnks, Carl n David. I just done chkdsk, and replaced avg with win essential. Then Im downloading the memtest, and I will keep u guys posted.
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
I purchased a brand new HP laptop in February and bought Windows 7 separately. Constant BSOD. More than a dozen separate calls to the HP "Hotline" who told me it must be Windows 7 and to return the disk as it was obviously faulty. I uninstalled completely and took the disk back to the sellers who laughed and said sure, we'll swap for a brand new disk. I did so, reinstalled and sure enough BSOD. Almost always when I was using Word but sometimes even when I was just surfing the net. So I get really furious at HP; obviously I must have a faulty laptop. They make me do a total reset (lose everything returning to factory settings but sure, if it works I don't care). It's now fixed. Right up until I reinstall Windows 7. So I send the laptop back to HP and get a loaner laptop with W7 preinstalled. It's a totally different brand - Lenovo Think Pad (as it was from the purchaser and not HP). BSOD.

So the only thing these two laptops have in common is W7. I'm going to guess that something in W7 is not compatible with hardware commonly found on laptops because every thread here is about uninstalling programs that I don't even have on this laptop. I get my old laptop back on Monday so I'm guessing I should go out and buy another type of software. Is there a version that has fewer BSODs than W7? Windows 2005 maybe? I don't need to do anything very difficult, just save some PDFs and Word Documents. But the BSOD 3 and 4 times per night is beyond frustrating.
 

My Computer

OS
Windows 7
Just as I was replying to the thread, my newly built system encountered another Bluescreen, with the following error:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 00000000000445D9
BCP3: 0000000000000000
BCP4: 00000000000446D9
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
Alecto said:
I purchased a brand new HP laptop in February and bought Windows 7 separately. Constant BSOD. More than a dozen separate calls to the HP "Hotline" who told me it must be Windows 7 and to return the disk as it was obviously faulty. I uninstalled completely and took the disk back to the sellers who laughed and said sure, we'll swap for a brand new disk. I did so, reinstalled and sure enough BSOD. Almost always when I was using Word but sometimes even when I was just surfing the net. So I get really furious at HP; obviously I must have a faulty laptop. They make me do a total reset (lose everything returning to factory settings but sure, if it works I don't care). It's now fixed. Right up until I reinstall Windows 7. So I send the laptop back to HP and get a loaner laptop with W7 preinstalled. It's a totally different brand - Lenovo Think Pad (as it was from the purchaser and not HP). BSOD.

So the only thing these two laptops have in common is W7. I'm going to guess that something in W7 is not compatible with hardware commonly found on laptops because every thread here is about uninstalling programs that I don't even have on this laptop. I get my old laptop back on Monday so I'm guessing I should go out and buy another type of software. Is there a version that has fewer BSODs than W7? Windows 2005 maybe? I don't need to do anything very difficult, just save some PDFs and Word Documents. But the BSOD 3 and 4 times per night is beyond frustrating.
Click to expand...

Hi Alecto & welcome,

As your comments & questions don't relate to what is going on here I suggest that you start your own thread seeking help.

Jan.
 

My Computer

Computer Manufacturer/Model Number
LAPTOP. HP Pavilion dv7-4010TX .
OS
Win 7 Ultimate 64-bit. SP1.
CPU
Intel i7 -720QM.[1.6GHz Turbo Boost 2.8GHz. 6MB Cache.]
Memory
8 DDR 3 RAM. 1066MHZ
Graphics Card(s)
ATI 1024 MB. DDR3. Radeon HD5650
Monitor(s) Displays
17.3" High Definition Brightview LCD. LED Backlit.
Screen Resolution
1600 x 900.
Hard Drives
640GB
Case
Laptop / notebook.
Mouse
Logitech Anywhere mouse. MX.
Internet Speed
ADSL [ but too slow ]
CarlTR6 said:
That is a lot of dumps, 28! I looked at the six most recent and saw five different error codes. A variety of error codes usually indicates hardware or hardware related problem.

STOP 0x0000001A: MEMORY_MANAGEMENT



Usual causes: Device driver, memory, kernel


STOP 0x0000004E: PFN_LIST_CORRUPT

Usual causes: Device driver, ?memory


STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,


STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure


STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION



Usual causes: System service, Device driver, graphics driver, ?memory
Click to expand...
Look through the usual causes. These are what you will be troubleshooting. Davidxtux has started you on the right path. Follow his suggestions.
CHKDSK /R /F:[FONT=&quot]
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe"
[/FONT][FONT=&quot]
[/FONT]
Click to expand...
[FONT=&quot]

[/FONT] Download a copy of [FONT=&quot]Memtest86+ - Advanced Memory [/FONT][FONT=&quot]Diagnostic Tool[/FONT] and burn the ISO to a CD using http://isorecorder.alexfeinman.com/W7[FONT=&quot].[/FONT][FONT=&quot]Boot from the CD, and leave it running for at least 5 passes[/FONT][FONT=&quot].[/FONT]

Here are the dmp analyzes:
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\Temp2_Dump2.zip\063010-17050-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03251000 PsLoadedModuleList = 0xfffff800`0348ee50
Debug session time: Wed Jun 30 09:33:41.236 2010 (GMT-4)
System Uptime: 0 days 6:06:25.922
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 6b05c, 0, 11685c}

Unable to load image \SystemRoot\System32\Drivers\[COLOR=Red]avgldx64.sys[/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000006b05c, page frame number
Arg3: 0000000000000000, current page state
Arg4: 000000000011685c, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033512bc to fffff800032c1600

STACK_TEXT:  
fffff880`080dbb78 fffff800`033512bc : 00000000`0000004e 00000000`00000099 00000000`0006b05c 00000000`00000000 : nt!KeBugCheckEx
fffff880`080dbb80 fffff800`032ab994 : 00000000`00000000 fffffa80`0168bdf0 00000000`00002001 80000000`783f5882 : nt!MiBadShareCount+0x4c
fffff880`080dbbc0 fffff800`035b3203 : fffffa80`04552c10 00000000`00000000 fffffa80`04552c10 00000000`00002001 : nt!MiDeleteSegmentPages+0x404
fffff880`080dbc70 fffff800`032f4e5c : fffffa80`04552c00 00000000`00000000 fffffa80`04552c10 00000000`00000000 : nt!MiSegmentDelete+0x7b
fffff880`080dbcb0 fffff800`035db170 : fffffa80`05e5dbe0 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0x26c
fffff880`080dbdd0 fffff800`035db57b : 00000000`00000000 00000000`053f0000 fffffa80`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b0
fffff880`080dbe90 fffff800`032c0853 : 00000000`0000570f fffff800`0343d480 fffffa80`03a029e0 fffffa80`03ce0720 : nt!NtUnmapViewOfSection+0x5f
fffff880`080dbee0 fffff800`032bcdf0 : fffff880`03e4577a 00000000`80000000 00000000`00000013 00000000`2a677641 : nt!KiSystemServiceCopyEnd+0x13
fffff880`080dc078 fffff880`03e4577a : 00000000`80000000 00000000`00000013 00000000`2a677641 00000000`00000001 : nt!KiServiceLinkage
fffff880`080dc080 00000000`80000000 : 00000000`00000013 00000000`2a677641 00000000`00000001 fffff880`03e80fa0 : [COLOR=Red]avgldx64[/COLOR]+0x277a
fffff880`080dc088 00000000`00000013 : 00000000`2a677641 00000000`00000001 fffff880`03e80fa0 fffff880`03e68eb5 : 0x80000000
fffff880`080dc090 00000000`2a677641 : 00000000`00000001 fffff880`03e80fa0 fffff880`03e68eb5 00000000`00000020 : 0x13
fffff880`080dc098 00000000`00000001 : fffff880`03e80fa0 fffff880`03e68eb5 00000000`00000020 fffff8a0`08a0a0a8 : 0x2a677641
fffff880`080dc0a0 fffff880`03e80fa0 : fffff880`03e68eb5 00000000`00000020 fffff8a0`08a0a0a8 00000000`000493e0 : 0x1
fffff880`080dc0a8 fffff880`03e68eb5 : 00000000`00000020 fffff8a0`08a0a0a8 00000000`000493e0 fffff880`03e80fa0 : [COLOR=Red]avgldx64[/COLOR]+0x3dfa0
fffff880`080dc0b0 00000000`00000020 : fffff8a0`08a0a0a8 00000000`000493e0 fffff880`03e80fa0 fffff880`080dc4b0 : [COLOR=Red]avgldx64[/COLOR]+0x25eb5
fffff880`080dc0b8 fffff8a0`08a0a0a8 : 00000000`000493e0 fffff880`03e80fa0 fffff880`080dc4b0 fffff880`080dc110 : 0x20
fffff880`080dc0c0 00000000`000493e0 : fffff880`03e80fa0 fffff880`080dc4b0 fffff880`080dc110 00000000`00000000 : 0xfffff8a0`08a0a0a8
fffff880`080dc0c8 fffff880`03e80fa0 : fffff880`080dc4b0 fffff880`080dc110 00000000`00000000 00000000`00000000 : 0x493e0
fffff880`080dc0d0 fffff880`080dc4b0 : fffff880`080dc110 00000000`00000000 00000000`00000000 00000000`0000004c : [COLOR=Red]avgldx64[/COLOR]+0x3dfa0
fffff880`080dc0d8 fffff880`080dc110 : 00000000`00000000 00000000`00000000 00000000`0000004c fffff880`03e5cf49 : 0xfffff880`080dc4b0
fffff880`080dc0e0 00000000`00000000 : 00000000`00000000 00000000`0000004c fffff880`03e5cf49 00000000`00000000 : 0xfffff880`080dc110


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`033512bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

Followup: MachineOwner
---------
[FONT=&quot][FONT=Verdana][SIZE=3] 

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\Temp2_Dump2.zip\063010-29390-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1f000 PsLoadedModuleList = 0xfffff800`0305ce50
Debug session time: Wed Jun 30 03:25:46.168 2010 (GMT-4)
System Uptime: 0 days 0:10:16.853
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fc30bf, fffff8800998adf0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )

Followup: Pool_corruption
---------

0: 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: fffff80002fc30bf, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800998adf0, 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: 
nt!ExDeferredFreePool+233
fffff800`02fc30bf 4c395008        cmp     qword ptr [rax+8],r10

CONTEXT:  fffff8800998adf0 -- (.cxr 0xfffff8800998adf0)
rax=0065006300720075 rbx=0000000000000000 rcx=fffffa8003965190
rdx=fffff8a00ccb8c50 rsi=0000000000000000 rdi=fffff8a00e356c00
rip=fffff80002fc30bf rsp=fffff8800998b7c0 rbp=0000000000000000
 r8=006f0073006f0072  r9=fffff8a00ccb93c0 r10=fffff8a00ccb93d0
r11=0000000000000001 r12=fffffa8003964500 r13=0000000000000000
r14=0000000000000003 r15=0000000000000001
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!ExDeferredFreePool+0x233:
fffff800`02fc30bf 4c395008        cmp     qword ptr [rax+8],r10 ds:002b:00650063`0072007d=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  avgchsva.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002fc30bf

STACK_TEXT:  
fffff880`0998b7c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x233


FOLLOWUP_IP: 
nt!ExDeferredFreePool+233
fffff800`02fc30bf 4c395008        cmp     qword ptr [rax+8],r10

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExDeferredFreePool+233

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .cxr 0xfffff8800998adf0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233

BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233

Followup: Pool_corruption
---------


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\Temp2_Dump2.zip\070110-14617-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e52000 PsLoadedModuleList = 0xfffff800`0308fe50
Debug session time: Wed Jun 30 16:21:47.817 2010 (GMT-4)
System Uptime: 0 days 0:50:32.503
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff88007ba8228, fffff88007ba7a90, fffff80002e7f217}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCachedRead+180 )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88007ba8228
Arg3: fffff88007ba7a90
Arg4: fffff80002e7f217

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


EXCEPTION_RECORD:  fffff88007ba8228 -- (.exr 0xfffff88007ba8228)
ExceptionAddress: fffff80002e7f217 (nt!MiInvalidateCollidedIos+0x0000000000000047)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88007ba7a90 -- (.cxr 0xfffff88007ba7a90)
rax=006100730070005c rbx=0000000000000000 rcx=fffffa80045277a0
rdx=0000000000000000 rsi=fffffa80045277a0 rdi=ffffffffffffffff
rip=fffff80002e7f217 rsp=fffff88007ba8460 rbp=fffffa80045277a0
 r8=003400360057004f  r9=fffffa8005527890 r10=fffffa80045277a0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000001
r14=0000000000000000 r15=0000058000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!MiInvalidateCollidedIos+0x47:
fffff800`02e7f217 4c8900          mov     qword ptr [rax],r8 ds:002b:00610073`0070005c=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fa0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
Ntfs!NtfsCachedRead+180
fffff880`0125afc0 84c0            test    al,al

FAULTING_IP: 
nt!MiInvalidateCollidedIos+47
fffff800`02e7f217 4c8900          mov     qword ptr [rax],r8

BUGCHECK_STR:  0x24

LAST_CONTROL_TRANSFER:  from fffff80002eb3cf6 to fffff80002e7f217

STACK_TEXT:  
fffff880`07ba8460 fffff800`02eb3cf6 : 00000000`00000000 fffffa80`045277a0 00000000`00000000 fffffa80`06300800 : nt!MiInvalidateCollidedIos+0x47
fffff880`07ba84b0 fffff800`02f06c8c : fffffa80`045277a0 00000000`00000000 00000000`00000000 00000000`00000052 : nt!MiWaitForInPageComplete+0xa4a
fffff880`07ba8590 fffff800`031e090b : 00000000`00000000 00000000`00052c00 fffffa80`03cdef20 00000000`000fd4e0 : nt!CcFetchDataForRead+0x20c
fffff880`07ba85f0 fffff880`0125afc0 : fffff8a0`00000000 fffff880`00000005 fffffa80`0002d400 fffff880`012ae001 : nt!CcCopyRead+0x16b
fffff880`07ba86b0 fffff880`0125f303 : 00000000`00052c00 fffff8a0`0173f670 fffff880`07ba88e0 fffff880`07ba87d8 : Ntfs!NtfsCachedRead+0x180
fffff880`07ba8710 fffff880`01261f78 : fffffa80`059767e0 fffffa80`03dd2780 fffff880`07ba8801 fffffa80`05cfe900 : Ntfs!NtfsCommonRead+0x583
fffff880`07ba88b0 fffff880`0107a23f : fffffa80`03dd2b20 fffffa80`03dd2780 fffffa80`05cfe930 00000000`00000001 : Ntfs!NtfsFsdRead+0x1b8
fffff880`07ba8960 fffff880`010786df : fffffa80`04906de0 00000000`00000001 fffffa80`04906d00 fffffa80`03dd2780 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`07ba89f0 fffff800`031d9c49 : 00000000`00000000 fffffa80`03cdef20 00000000`00000001 fffffa80`03dd2780 : fltmgr!FltpDispatch+0xcf
fffff880`07ba8a50 fffff800`031e1453 : fffffa80`03cdef20 fffffa80`03cdef20 fffffa80`03cdef20 fffff880`009e7180 : nt!IopSynchronousServiceTail+0xf9
fffff880`07ba8ac0 fffff800`02ec1853 : 00000000`0000016c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
fffff880`07ba8bb0 00000000`74132dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001be5d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74132dd9


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Ntfs!NtfsCachedRead+180

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff88007ba7a90 ; kb

FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCachedRead+180

BUCKET_ID:  X64_0x24_Ntfs!NtfsCachedRead+180

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\Temp2_Dump2.zip\070110-14820-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e58000 PsLoadedModuleList = 0xfffff800`03095e50
Debug session time: Wed Jun 30 15:30:44.737 2010 (GMT-4)
System Uptime: 0 days 0:38:50.048
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\Drivers\avgldx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgldx64.sys
*** ERROR: Module load completed but symbols could not be loaded for avgldx64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff880079caa8c, fffff880031c3eb8, fffff880031c3720}

Probably caused by : [COLOR=Red]avgldx64.sys[/COLOR] ( avgldx64+28a8c )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880079caa8c, The address that the exception occurred at
Arg3: fffff880031c3eb8, Exception Record Address
Arg4: fffff880031c3720, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
avgldx64+28a8c
fffff880`079caa8c 458b442404      mov     r8d,dword ptr [r12+4]

EXCEPTION_RECORD:  fffff880031c3eb8 -- (.exr 0xfffff880031c3eb8)
ExceptionAddress: fffff880079caa8c (avgldx64+0x0000000000028a8c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000063eb62c
Attempt to read from address 00000000063eb62c

CONTEXT:  fffff880031c3720 -- (.cxr 0xfffff880031c3720)
rax=00000000052b0008 rbx=fffff880079dffa0 rcx=000000000113b620
rdx=0000000000632440 rsi=000000000000002c rdi=0000000000003757
rip=fffff880079caa8c rsp=fffff880031c40f0 rbp=000000000063246c
 r8=0000000000000000  r9=0000000000000000 r10=305a28f2f699a73f
r11=0000000000000000 r12=00000000063eb628 r13=0000000000a4e4c4
r14=0000000000a87626 r15=000000000000002c
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
avgldx64+0x28a8c:
fffff880`079caa8c 458b442404      mov     r8d,dword ptr [r12+4] ds:002b:00000000`063eb62c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000063eb62c

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031000e0
 00000000063eb62c 

FOLLOWUP_IP: 
avgldx64+28a8c
fffff880`079caa8c 458b442404      mov     r8d,dword ptr [r12+4]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880079dffa0 to fffff880079caa8c

STACK_TEXT:  
fffff880`031c40f0 fffff880`079dffa0 : fffff880`079dffa0 00000000`052b0008 fffff8a0`07976018 00000000`052b0008 : avgldx64+0x28a8c
fffff880`031c40f8 fffff880`079dffa0 : 00000000`052b0008 fffff8a0`07976018 00000000`052b0008 00000000`00560723 : avgldx64+0x3dfa0
fffff880`031c4100 00000000`052b0008 : fffff8a0`07976018 00000000`052b0008 00000000`00560723 00152410`00000000 : avgldx64+0x3dfa0
fffff880`031c4108 fffff8a0`07976018 : 00000000`052b0008 00000000`00560723 00152410`00000000 00000000`052b0008 : 0x52b0008
fffff880`031c4110 00000000`052b0008 : 00000000`00560723 00152410`00000000 00000000`052b0008 00000000`00632440 : 0xfffff8a0`07976018
fffff880`031c4118 00000000`00560723 : 00152410`00000000 00000000`052b0008 00000000`00632440 00000000`05820008 : 0x52b0008
fffff880`031c4120 00152410`00000000 : 00000000`052b0008 00000000`00632440 00000000`05820008 00000000`057b77d8 : 0x560723
fffff880`031c4128 00000000`052b0008 : 00000000`00632440 00000000`05820008 00000000`057b77d8 00000000`00000000 : 0x152410`00000000
fffff880`031c4130 00000000`00632440 : 00000000`05820008 00000000`057b77d8 00000000`00000000 fffff880`031c4370 : 0x52b0008
fffff880`031c4138 00000000`05820008 : 00000000`057b77d8 00000000`00000000 fffff880`031c4370 fffff880`079c8ec9 : 0x632440
fffff880`031c4140 00000000`057b77d8 : 00000000`00000000 fffff880`031c4370 fffff880`079c8ec9 00000000`00000000 : 0x5820008
fffff880`031c4148 00000000`00000000 : fffff880`031c4370 fffff880`079c8ec9 00000000`00000000 00000000`00000000 : 0x57b77d8


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  avgldx64+28a8c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: [COLOR=Red]avgldx64[/COLOR]

IMAGE_NAME:  [COLOR=Red]avgldx64.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4b737eff

STACK_COMMAND:  .cxr 0xfffff880031c3720 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_[COLOR=Red]avgldx64[/COLOR]+28a8c

BUCKET_ID:  X64_0x7E_avgldx64+28a8c

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

[/SIZE][/FONT][/FONT][FONT=&quot][FONT=Verdana][SIZE=3]
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\Temp2_Dump2.zip\070110-19172-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e50000 PsLoadedModuleList = 0xfffff800`0308de50
Debug session time: Wed Jun 30 14:51:17.709 2010 (GMT-4)
System Uptime: 0 days 5:17:04.005
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, a8e67, 0, a9167}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000000a8e67, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000000a9167, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchFilterHo

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f502bc to fffff80002ec0600

STACK_TEXT:  
fffff880`07c11108 fffff800`02f502bc : 00000000`0000004e 00000000`00000099 00000000`000a8e67 00000000`00000000 : nt!KeBugCheckEx
fffff880`07c11110 fffff800`02f32937 : fffff880`02fd5180 fffff800`02ef4326 00000000`00000000 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`07c11150 fffff800`02e94b43 : fffffa80`03d47060 fffff700`000002c0 0000007f`fffffff8 fffff8a0`0326fc28 : nt! ?? ::FNODOBFM::`string'+0x3227e
fffff880`07c111e0 fffff800`02e935a2 : fffffa80`03d47060 fffffa80`0000006f 00000000`000000dd fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`07c11a90 fffff800`031a6c4f : fffff8a0`082269a0 00000000`00000001 00000000`00000000 fffffa80`03fc6340 : nt!MmCleanProcessAddressSpace+0x96
fffff880`07c11ae0 fffff800`0317e6eb : 00000000`00000000 00000000`00000001 000007ff`fffde000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`07c11ba0 fffff800`02ebf853 : fffffa80`03d47060 00000000`00000000 00000000`00153b01 fffffa80`03fc6340 : nt!NtTerminateProcess+0x25b
fffff880`07c11c20 00000000`775e017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000afd98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e017a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02f502bc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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\Temp2_Dump2.zip\070510-17456-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Mon Jul  5 03:12:30.128 2010 (GMT-4)
System Uptime: 0 days 0:31:45.813
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000010050, b39000003c932867, fffff6fc80614cca}

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

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

1: 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: fffff68000010050
Arg3: b39000003c932867
Arg4: fffff6fc80614cca

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  audiodg.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f49608 to fffff80002ed7600

STACK_TEXT:  
fffff880`0a4cb7b8 fffff800`02f49608 : 00000000`0000001a 00000000`00000403 fffff680`00010050 b3900000`3c932867 : nt!KeBugCheckEx
fffff880`0a4cb7c0 fffff800`02f08251 : 00000000`00000000 fffff680`00010440 fffffa80`063bdb30 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x31f32
fffff880`0a4cb970 fffff800`02f18fca : 00000000`00000000 00000000`02088fff fffffa80`00000000 fffffa80`063bdb30 : nt!MiDeleteVirtualAddresses+0x408
fffff880`0a4cbb30 fffff800`02ed6853 : ffffffff`ffffffff 00000000`0302db90 00000000`0302db58 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0a4cbc20 00000000`76de009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0302dac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76de009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+31f32
fffff800`02f49608 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
---------

[/SIZE][/FONT][/FONT]
[FONT=&quot]

Three of these dumps show that AVG antivirus was involved in the crash and one points to AVG as the direct cause. AVG is known to cause BSOD's on some Win 7 systems. I suggest you uninstall AVG using the uninstall tool > [/FONT] Info > Tool (32bit) - Tool (64 bit)[FONT=&quot] Replace it with Microsoft Security Essentials while you are troubleshooting.

[/FONT]
Click to expand...


Hi carl,

I had removed avg, and done memtest with 8 passes. Then soon after the memtest I encountered another BSOD. Here the attached miniDump, please advise what should i do?
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
I assume memtest showed no errors? This latest dump gives a stop error code of 1A.
STOP 0x0000001A: MEMORY_MANAGEMENT

Usual causes: Device driver, memory, kernel
Click to expand...
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_miniDump(4).zip\070610-14570-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50
Debug session time: Tue Jul  6 10:49:41.350 2010 (GMT-4)
System Uptime: 0 days 0:22:28.020
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000094050, e59000003c427867, fffff6fc001e2138}

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

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

1: 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: fffff68000094050
Arg3: e59000003c427867
Arg4: fffff6fc001e2138

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ee5608 to fffff80002e73600

STACK_TEXT:  
fffff880`095d07b8 fffff800`02ee5608 : 00000000`0000001a 00000000`00000403 fffff680`00094050 e5900000`3c427867 : nt!KeBugCheckEx
fffff880`095d07c0 fffff800`02ea4251 : 00000000`00000000 fffff680`00094ff8 fffffa80`05abe2f0 00000000`00116001 : nt! ?? ::FNODOBFM::`string'+0x31f32
fffff880`095d0970 fffff800`02eb4fca : 00000000`00000000 00000000`12b41fff fffffa80`00000000 fffffa80`05abe2f0 : nt!MiDeleteVirtualAddresses+0x408
fffff880`095d0b30 fffff800`02e72853 : ffffffff`ffffffff 00000000`092cd6e0 00000000`092cd6a8 fffffa80`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`095d0c20 00000000`77b4009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`092cd618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b4009a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+31f32
fffff800`02ee5608 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
---------
To recap, you have run memtest and uninstalled AVG.

Did you run dskchk and SFC? If not, please run both of those. If SFC finds problems but does not fix some of them, run it again.

After you complete dskchk and SFC, turn on Driver Verifier.
Follow these instructions for enabling driver verifier: Using Driver Verifier to identify issues with Drivers
 Please follow these instructions in order to run it:

 [FONT=&quot]Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.

[/FONT] If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Click to expand...


Driver verifier will most like cause a BSOD's; that is the way it works. Post any BSOD's ASAP.


 [FONT=&quot]
[/FONT]
 

My Computer

Computer Manufacturer/Model Number
Home built
OS
Windows 7 Ultimate 32 bit
CPU
Intel(R) Pentium(R) 4 CPU 3.00GHz
Motherboard
ASUS P4P800-VM Motherboard Chipset: Intel 865G + ICH5
Memory
2.50 GB RAM
Graphics Card(s)
NVIDIA GeForce 7600 GS
Sound Card
SoundMax Integrated Digital Audio (Chip)
Monitor(s) Displays
ViewSonic VX 1962 wm
Screen Resolution
1680 X 1050
Hard Drives
Seagate Barracuda 7200.10 80 GB
ST380215A ATA Device 18.6 GB
Western Digital "My Book" external hard drive 750 GB
Cooling
Fan based
Keyboard
Microsoft Comfort Curve Keyboard 2000 v10 USB
Mouse
Logitec optic USB
Internet Speed
3.01 Mb/s download 0.64 Mb/s upload
yea i done the memtest, and no error shown. Firstly, I uninstalled AVG, then chkdsk, following memtest with no error ( to confirm error with be shown as number right?). Since, all done. till now there 3 BSOD.
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
Hi carl, this zip is the latest after doing verifier. Please advise what next. thanks.
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
fildoo said:
Hi carl, this zip is the latest after doing verifier. Please advise what next. thanks.
Click to expand...

I found an old driver on your system. Win 7 does not generally like old drivers and they can cause memory corruption and crashes.

Lachesis.sys Fri Aug 17 03:48:44 2007 (46C552DC) - Razer Lachesis Mouse driver http://www.razersupport.com

If you are still using this mouse, go to the Razer site and try to find an update. Apparently others have had problems with this mouse on Win 7. I read that it is not compatible with 7 64 bit. Check these two links:

Razer Blueprints - the razer community - Search

BSOD - Vista - Razer Lachesis? - TechSpot OpenBoards

You might want to get a new mouse compatible with Win 7.

The first dump pointed at RTKVHD64.sys as the cause of the crash.
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_070710-17378-01.zip\070710-17378-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`0309de50
Debug session time: Tue Jul  6 19:12:39.143 2010 (GMT-4)
System Uptime: 0 days 0:00:18.844
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98003912d60, 0, fffff8800677df7a, 0}

Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys

Could not read faulting driver name
Probably caused by : RTKVHD64.sys ( RTKVHD64+cbf7a )

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

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

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff98003912d60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff8800677df7a, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031080e0
 fffff98003912d60 

FAULTING_IP: 
RTKVHD64+cbf7a
fffff880`0677df7a 8b4630          mov     eax,dword ptr [rsi+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003a957e0 -- (.trap 0xfffff88003a957e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88003a95a08
rdx=fffff88003a95970 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800677df7a rsp=fffff88003a95970 rbp=0000000000000002
 r8=0000000000000000  r9=fffff8800677df7a r10=0000000000000000
r11=fffff8000304ae80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
RTKVHD64+0xcbf7a:
fffff880`0677df7a 8b4630          mov     eax,dword ptr [rsi+30h] ds:ae80:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f50e54 to fffff80002ed0600

STACK_TEXT:  
fffff880`03a95678 fffff800`02f50e54 : 00000000`00000050 fffff980`03912d60 00000000`00000000 fffff880`03a957e0 : nt!KeBugCheckEx
fffff880`03a95680 fffff800`02ece6ee : 00000000`00000000 fffff8a0`015f910e fffffa80`0633d500 fffff800`02f0320f : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`03a957e0 fffff880`0677df7a : fffff880`03a95a08 00000000`00000000 fffff8a0`015f910e fffffa80`06945440 : nt!KiPageFault+0x16e
fffff880`03a95970 fffff880`03a95a08 : 00000000`00000000 fffff8a0`015f910e fffffa80`06945440 00000000`00000000 : RTKVHD64+0xcbf7a
fffff880`03a95978 00000000`00000000 : fffff8a0`015f910e fffffa80`06945440 00000000`00000000 fffff800`00000000 : 0xfffff880`03a95a08


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTKVHD64+cbf7a
fffff880`0677df7a 8b4630          mov     eax,dword ptr [rsi+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+cbf7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b1e2855

FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+cbf7a

BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+cbf7a

Followup: MachineOwner
---------
The second dump blamed memory corruption and did not point to a driver.
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_070710-17378-01.zip\070710-16520-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Tue Jul  6 19:15:12.542 2010 (GMT-4)
System Uptime: 0 days 0:02:01.244
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C1, {fffff98013f9aee0, fffff98013f9a253, d0118, 23}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )

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

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.  Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98013f9aee0, address trying to free
Arg2: fffff98013f9a253, address where bits are corrupted
Arg3: 00000000000d0118, (reserved)
Arg4: 0000000000000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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


BUGCHECK_STR:  0xC1_23

SPECIAL_POOL_CORRUPTION_TYPE:  23

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

IRP_ADDRESS:  fffffa7fffffff89

LAST_CONTROL_TRANSFER:  from fffff80002f1953a to fffff80002e89600

STACK_TEXT:  
fffff880`009fa688 fffff800`02f1953a : 00000000`000000c1 fffff980`13f9aee0 fffff980`13f9a253 00000000`000d0118 : nt!KeBugCheckEx
fffff880`009fa690 fffff800`02f905d3 : fffff980`0979ace0 fffffa80`0719a010 00000000`00000000 00000000`00000000 : nt!MiCheckSpecialPoolSlop+0x9a
fffff880`009fa6d0 fffff800`02fbc356 : fffff800`02e19000 00000000`2b707249 00000000`00195780 00000000`00000001 : nt!MmFreeSpecialPool+0x1d3
fffff880`009fa800 fffff800`0332e026 : fffffa80`0719f402 fffffa80`0719f4c0 00000000`00000000 fffff980`13f9aee0 : nt!ExFreePool+0x9f3
fffff880`009fa8b0 fffff800`0332e5ec : fffff800`02ea8aa2 fffff980`13f9aee0 fffff880`009faca0 00000000`00000000 : nt!VfIoFreeIrp+0xe6
fffff880`009fa8e0 fffff800`02ea8aa2 : fffff880`009faca0 fffff980`13f9aee0 00000000`00000000 fffffa80`06931060 : nt!IovFreeIrpPrivate+0x5c
fffff880`009fa920 fffff800`02e5c0ed : fffffa80`00000001 00000000`00000000 fffff980`13e18e00 fffff800`031a56c7 : nt!IopCompleteRequest+0x402
fffff880`009fa9f0 fffff800`03185a77 : 00000000`00000000 fffff880`009fab60 fffff980`13e18ee0 fffffa80`06d36b60 : nt!IopPostProcessIrp+0x4d
fffff880`009faa70 fffff800`03145825 : 00000000`00000000 fffff880`009fab68 fffff880`009fab60 00000000`00000401 : nt!IoRemoveIoCompletion+0xe7
fffff880`009fab00 fffff800`02e88853 : fffffa80`06931060 00000000`01d1f818 fffff880`009fabc8 fffff880`009fac00 : nt!NtRemoveIoCompletion+0x145
fffff880`009fabb0 00000000`77b3ff4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01d1f7f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b3ff4a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCheckSpecialPoolSlop+9a
fffff800`02f1953a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiCheckSpecialPoolSlop+9a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xC1_23_VRF_nt!MiCheckSpecialPoolSlop+9a

BUCKET_ID:  X64_0xC1_23_VRF_nt!MiCheckSpecialPoolSlop+9a

Followup: MachineOwner
---------
The third dump also pointed to RTKVHD64.sys.
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_070710-17378-01.zip\070710-16458-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`03099e50
Debug session time: Tue Jul  6 19:05:16.301 2010 (GMT-4)
System Uptime: 0 days 0:00:18.628
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D5, {fffff98003482d60, 0, fffff88006741f7a, 0}

Unable to load image \SystemRoot\system32\drivers\RTKVHD64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys

Could not read faulting driver name
Probably caused by : RTKVHD64.sys ( RTKVHD64+cbf7a )

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

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

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff98003482d60, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff88006741f7a, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031040e0
 fffff98003482d60 

FAULTING_IP: 
RTKVHD64+cbf7a
fffff880`06741f7a 8b4630          mov     eax,dword ptr [rsi+30h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xD5

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002a937e0 -- (.trap 0xfffff88002a937e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88002a93a08
rdx=fffff88002a93970 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006741f7a rsp=fffff88002a93970 rbp=0000000000000002
 r8=0000000000000000  r9=fffff88006741f7a r10=0000000000000000
r11=fffff88002fd5180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
RTKVHD64+0xcbf7a:
fffff880`06741f7a 8b4630          mov     eax,dword ptr [rsi+30h] ds:5180:00000000`00000030=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f4ce54 to fffff80002ecc600

STACK_TEXT:  
fffff880`02a93678 fffff800`02f4ce54 : 00000000`00000050 fffff980`03482d60 00000000`00000000 fffff880`02a937e0 : nt!KeBugCheckEx
fffff880`02a93680 fffff800`02eca6ee : 00000000`00000000 fffff8a0`0234410e fffffa80`06b17000 fffff800`02eff20f : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`02a937e0 fffff880`06741f7a : fffff880`02a93a08 00000000`00000000 fffff8a0`0234410e fffffa80`06b10a00 : nt!KiPageFault+0x16e
fffff880`02a93970 fffff880`02a93a08 : 00000000`00000000 fffff8a0`0234410e fffffa80`06b10a00 00000000`00000000 : RTKVHD64+0xcbf7a
fffff880`02a93978 00000000`00000000 : fffff8a0`0234410e fffffa80`06b10a00 00000000`00000000 fffff800`00000000 : 0xfffff880`02a93a08


STACK_COMMAND:  kb

FOLLOWUP_IP: 
RTKVHD64+cbf7a
fffff880`06741f7a 8b4630          mov     eax,dword ptr [rsi+30h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  RTKVHD64+cbf7a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b1e2855

FAILURE_BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+cbf7a

BUCKET_ID:  X64_0xD5_VRF_RTKVHD64+cbf7a

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

3: kd> lmtsmn
start             end                 module name
fffff880`03e00000 fffff880`03e3e000   1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`00f35000 fffff880`00f8c000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c83000 fffff880`02d0d000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03e5a000 fffff880`03e70000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`01851000 fffff880`01866000   amdppm   amdppm.sys   Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00ff4000 fffff880`00fff000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00e78000 fffff880`00e81000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00c1a000 fffff880`00c44000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`04807000 fffff880`04ee3000   atikmdag atikmdag.sys Thu May 27 12:47:58 2010 (4BFEA23E)
fffff880`03e77000 fffff880`03ebd000   atikmpag atikmpag.sys Thu May 27 12:25:36 2010 (4BFE9D00)
fffff880`0197c000 fffff880`01983000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`02c2d000 fffff880`02c3e000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff960`00740000 fffff960`00767000   cdd      cdd.dll      unavailable (00000000)
fffff880`0191c000 fffff880`01946000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00cc9000 fffff880`00d89000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`018b6000 fffff880`018e6000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00c6b000 fffff880`00cc9000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01115000 fffff880`01188000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`03e4a000 fffff880`03e5a000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`068a0000 fffff880`068ae000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02c0f000 fffff880`02c2d000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`02c00000 fffff880`02c0f000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`018a0000 fffff880`018b6000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`06454000 fffff880`06476000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`068ba000 fffff880`068c3000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`068ae000 fffff880`068ba000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`068c3000 fffff880`068d6000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`06894000 fffff880`068a0000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04ee3000 fffff880`04fd7000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
fffff880`03ebd000 fffff880`03f03000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
fffff880`010a3000 fffff880`010b7000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01057000 fffff880`010a3000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01866000 fffff880`018a0000   fvevol   fvevol.sys   Mon Jul 13 19:22:15 2009 (4A5BC1A7)
fffff880`01400000 fffff880`0144a000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff800`02e13000 fffff800`02e5c000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04fd7000 fffff880`04ffb000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`06938000 fffff880`06951000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`06951000 fffff880`06959080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`0692a000 fffff880`06938000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`01464000 fffff880`0146d000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`00d99000 fffff880`00db9000   jraid    jraid.sys    Thu Oct 29 04:14:20 2009 (4AE94EDC)
fffff880`044d4000 fffff880`044e3000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`06962000 fffff880`06970000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00bcc000 fffff800`00bd6000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff880`044f4000 fffff880`04537000   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`015c5000 fffff880`015f0000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`06476000 fffff880`0647b200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`0695a000 fffff880`06961680   Lachesis Lachesis.sys Fri Aug 17 03:48:44 2007 (46C552DC)
fffff880`0698b000 fffff880`069ae000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00c4a000 fffff880`00c57000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`0690e000 fffff880`0692a000   Mkd2Nadr Mkd2Nadr.sys Thu Mar 12 01:37:18 2009 (49B89F8E)
fffff880`0697d000 fffff880`0698b000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`044e3000 fffff880`044f2000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`06970000 fffff880`0697d000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00c00000 fffff880`00c1a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`01946000 fffff880`01973000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
fffff880`019e1000 fffff880`019ec000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00f95000 fffff880`00f9f000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010b7000 fffff880`01115000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`02df4000 fffff880`02dff000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`01452000 fffff880`01464000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01473000 fffff880`01565000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`03fe4000 fffff880`03ff0000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`0444f000 fffff880`0447e000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`045ba000 fffff880`045cf000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02d3c000 fffff880`02d4b000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02c3e000 fffff880`02c83000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`01565000 fffff880`015c5000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`019ec000 fffff880`019fd000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`02de8000 fffff880`02df4000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02e5c000 fffff800`03438000   nt       ntkrnlmp.exe Sat Feb 27 02:55:23 2010 (4B88CFEB)
fffff880`01252000 fffff880`013f5000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01973000 fffff880`0197c000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`04549000 fffff880`04560000   nusb3hub nusb3hub.sys Fri Nov 20 05:15:57 2009 (4B066C5D)
fffff880`03f03000 fffff880`03f33000   nusb3xhc nusb3xhc.sys Fri Nov 20 05:16:01 2009 (4B066C61)
fffff880`02d16000 fffff880`02d3c000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`00fdf000 fffff880`00ff4000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00f9f000 fffff880`00fd2000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00e71000 fffff880`00e78000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00d89000 fffff880`00d99000   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`06417000 fffff880`06454000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00c57000 fffff880`00c6b000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`011d4000 fffff880`011f8000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`0447e000 fffff880`04499000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04499000 fffff880`044ba000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`044ba000 fffff880`044d4000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`02d97000 fffff880`02de8000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`019c6000 fffff880`019cf000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`019cf000 fffff880`019d8000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`019d8000 fffff880`019e1000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`01000000 fffff880`0103a000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`03f33000 fffff880`03f72000   Rt64win7 Rt64win7.sys Thu Aug 20 12:05:06 2009 (4A8D7432)
fffff880`04400000 fffff880`04432700   RtHDMIVX RtHDMIVX.sys Wed Dec 02 01:33:25 2009 (4B160A35)
fffff880`06676000 fffff880`06893300   RTKVHD64 RTKVHD64.sys Tue Dec 08 05:20:05 2009 (4B1E2855)
fffff880`00db9000 fffff880`00de8000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`03e3e000 fffff880`03e4a000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`02d4b000 fffff880`02d68000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`0144a000 fffff880`01452000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`044f2000 fffff880`044f3480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Mon Jul 13 19:25:34 2009 (4A5BC26E)
fffff880`0181e000 fffff880`0182b000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`01800000 fffff880`0181e000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`02d83000 fffff880`02d97000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`005f0000 fffff960`005fa000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0182b000 fffff880`01851000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04537000 fffff880`04549000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`068f1000 fffff880`0690e000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`04ffb000 fffff880`04ffcf00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`03fd3000 fffff880`03fe4000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04560000 fffff880`045ba000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`03f72000 fffff880`03f7d000   usbohci  usbohci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`03f7d000 fffff880`03fd3000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`068d6000 fffff880`068f1000   USBSTOR  USBSTOR.SYS  Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`00fd2000 fffff880`00fdf000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01983000 fffff880`01991000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`01991000 fffff880`019b6000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e00000 fffff880`00e15000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e15000 fffff880`00e71000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01188000 fffff880`011d4000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`02d68000 fffff880`02d83000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`019b6000 fffff880`019c6000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e82000 fffff880`00f26000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f26000 fffff880`00f35000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02d0d000 fffff880`02d16000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000a0000 fffff960`003af000   win32k   win32k.sys   Sat May 01 11:06:30 2010 (4BDC4376)
fffff880`015f0000 fffff880`015f9000   wmiacpi  wmiacpi.sys  Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`00f8c000 fffff880`00f95000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`069ae000 fffff880`069cf000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)

Unloaded modules:
fffff880`018e6000 fffff880`018f4000   crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`018f4000 fffff880`01900000   dump_ataport
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01900000 fffff880`01909000   dump_atapi.s
    Timestamp: unavailable (00000000)
    Checksum:  00000000
fffff880`01909000 fffff880`0191c000   dump_dumpfve
    Timestamp: unavailable (00000000)
    Checksum:  00000000
RTKVHD64.sys is your Realtek High Definition Audio Function (sound card) Driver Realtek

I suggest you upgrade your mouse driver or upgrade your mouse. Then try reinstalling RTKVHD64.sys. The driver is current; but it could possibly be corrupt.

Reboot and make sure Driver Verifier is turned off. If you get another BSOD, upload the dump file and turn Driver Verifier back on.

Keep us posted on how you are doing.
 

My Computer

Computer Manufacturer/Model Number
Home built
OS
Windows 7 Ultimate 32 bit
CPU
Intel(R) Pentium(R) 4 CPU 3.00GHz
Motherboard
ASUS P4P800-VM Motherboard Chipset: Intel 865G + ICH5
Memory
2.50 GB RAM
Graphics Card(s)
NVIDIA GeForce 7600 GS
Sound Card
SoundMax Integrated Digital Audio (Chip)
Monitor(s) Displays
ViewSonic VX 1962 wm
Screen Resolution
1680 X 1050
Hard Drives
Seagate Barracuda 7200.10 80 GB
ST380215A ATA Device 18.6 GB
Western Digital "My Book" external hard drive 750 GB
Cooling
Fan based
Keyboard
Microsoft Comfort Curve Keyboard 2000 v10 USB
Mouse
Logitec optic USB
Internet Speed
3.01 Mb/s download 0.64 Mb/s upload
  • Like
Reactions: JMH
Hi carl,

Im not sure if the verifier had been turned off. Basically, I turned off (by choosing delete existing setting), then reboot my system. However, every reboot attempt directs me to a BSOD with memory corruption. I will tell you more using my other laptop.(in case of another BSOD). I attached the minidump here.
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
Carl,

Thanks for your patience in helping me out. Seeing so many memory corruption error. I decided to perform another Memtest. This time round it return me with errors, alot of them. Hence I done the following,

01 & 02 RAM on slot 01 n 02: Errors return on test#5 onwards.
01 RAM on Slot 01: No error
02 RAM on Slot 01: No error
02 RAM on slot 02: No error

With the results, i retested step1; this time round ensuring tt it is properly secured. Result is the same, error on test#5 onward.

FYI, I not tamper on any setting on bios.

any idea?
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
Replace the defective ram ....
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
LENOVO K450 @3.0GHZ
OS
64-bit Windows 8.1 Pro
CPU
Core(TM) i5 CPU 4330 Haswell @ 3.20GHz
Motherboard
LENOVO
Memory
12.00 GB
Graphics Card(s)
Intel(R) HD Graphics
Sound Card
Intel HD integtrated
Monitor(s) Displays
HP 25' ISP Monitor
Screen Resolution
1900/1020
Hard Drives
(1) ST1000DM003-1CH162 (2) Generic STORAGE DEVICE USB Device (3) Generic STORAGE DEVICE USB Device
Internet Speed
100mb down/10mb up
Both sticks reported no errors in other slots and individually. So you might have a bad dimm slot.
 

My Computer

Computer Manufacturer/Model Number
Barebones
OS
Windows 7 Home Premium 64bit
CPU
AMD Phenom II X6 1090T Black Edition Thuban 3.2GHz
Motherboard
MSI NF980-G65 AM3 NVIDIA nForce 980a SLI
Memory
G.SKILL Ripjaws Series 8GB (4 x 2GB) DDR3 (PC3 12800)
Graphics Card(s)
SLI GeForce GTX 480 (Fermi) 1536MB 384-bit GDDR5
Sound Card
onboard
Monitor(s) Displays
Toshiba TV 42'' or 27.5'' widescreen monitor
Screen Resolution
1920x1080 60hz
Hard Drives
2x SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/
PSU
Antec TPQ-1200 1200W Continuous Power with PowerCache
Case
COOLER MASTER HAF 932 RC-932-KKN1-GP Black Steel ATX Full To
Cooling
1 x 140mm rear fan, 3x 230mm Fans (front, top, side)
Keyboard
Logitech G15
Mouse
Logitech MX 518
Internet Speed
13 mb/s down 5.5 mb/s up
Other Info
Main system.. other system is slightly different
Thank you everyone. I think my com is now fixed.
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
Pleased to hear that. Thanks for reporting back.
Jan.
 

My Computer

Computer Manufacturer/Model Number
LAPTOP. HP Pavilion dv7-4010TX .
OS
Win 7 Ultimate 64-bit. SP1.
CPU
Intel i7 -720QM.[1.6GHz Turbo Boost 2.8GHz. 6MB Cache.]
Memory
8 DDR 3 RAM. 1066MHZ
Graphics Card(s)
ATI 1024 MB. DDR3. Radeon HD5650
Monitor(s) Displays
17.3" High Definition Brightview LCD. LED Backlit.
Screen Resolution
1600 x 900.
Hard Drives
640GB
Case
Laptop / notebook.
Mouse
Logitech Anywhere mouse. MX.
Internet Speed
ADSL [ but too slow ]
fildoo said:
Thank you everyone. I think my com is now fixed.
Click to expand...

I am late getting back to the thread. Very good job on running Memtest again. I think you have a bad slot. It appears that both sticks are good. I am glad you are running smoothly now. Thank you for reporting back.

Did you take care of your obsolete mouse driver?
 

My Computer

Computer Manufacturer/Model Number
Home built
OS
Windows 7 Ultimate 32 bit
CPU
Intel(R) Pentium(R) 4 CPU 3.00GHz
Motherboard
ASUS P4P800-VM Motherboard Chipset: Intel 865G + ICH5
Memory
2.50 GB RAM
Graphics Card(s)
NVIDIA GeForce 7600 GS
Sound Card
SoundMax Integrated Digital Audio (Chip)
Monitor(s) Displays
ViewSonic VX 1962 wm
Screen Resolution
1680 X 1050
Hard Drives
Seagate Barracuda 7200.10 80 GB
ST380215A ATA Device 18.6 GB
Western Digital "My Book" external hard drive 750 GB
Cooling
Fan based
Keyboard
Microsoft Comfort Curve Keyboard 2000 v10 USB
Mouse
Logitec optic USB
Internet Speed
3.01 Mb/s download 0.64 Mb/s upload
CarlTR6 said:
fildoo said:
Thank you everyone. I think my com is now fixed.
Click to expand...

I am late getting back to the thread. Very good job on running Memtest again. I think you have a bad slot. It appears that both sticks are good. I am glad you are running smoothly now. Thank you for reporting back.

Did you take care of your obsolete mouse driver?
Click to expand...

hi Carlt

Oh what happened is that my previous ram.. is not compatible to my pc's motherboard when it runs 2 rams.. I try 5 others ram brands.. and they all work well to all slots. In the end.. i ended up with team elite, (wasn't a very popular name in singapore thou.)

Yeap. I got the mouse driver updated fm the website.
 

My Computer

OS
Win 7 64bit
CPU
AMD Phenom(tm)II X4 965 Processor 3.40Ghz
Motherboard
Gigabyte 890GPA-UD3H
Memory
4GB
Graphics Card(s)
ATI HD5850
Sound Card
Nil
You must log in or register to reply here.

Similar threads

J
Solved My stupid error -.- Blue Screen after change MSConfig 0xc000000e
Replies
13
Views
12K
SIW2
SIW2
J
HELP! Blue screen error: "STOP: 0x000000F4 (0X0000000000000003, 0XFFFF
Replies
4
Views
5K
Laith
Laith
A
Windows 7 Blue Screen Of Death with error: IRQL_NOT_LESS_OR_EQUAL
Replies
1
Views
759
axe0
A
D
blue screen error with a problem with atinavrr.sys
Replies
1
Views
2K
Snick
Snick
S
Power Error Blue Screen After WIN 7 Updates
Replies
1
Views
1K
Snick
Snick
Back
Top