vallanzaska
New Member
- Joined
- May 9, 2011
- Messages
- 6
- Thread Author
-
- #1
hi everybody
im having trouble with these bsod
Crash Dump Analysis
On Mon 09/05/2011 13:50:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050911-17066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x97F7, 0x97F900012FEF)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 09/05/2011 13:48:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050911-14289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFD7FFD000000, 0x0, 0xFFFFF800033023FA, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 08/05/2011 11:18:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050811-10873-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0x6E81000, 0x1, 0x73F7500A, 0x8)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/05/2011 10:22:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050711-18720-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007B8D828, 0xFFFFF88007B8D090, 0xFFFFF800033F80F3)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 07/05/2011 10:14:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050711-16364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF6C6F7800088, 0x0, 0xFFFFF80003293D83, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Link RemovedLink Removed
dunno what to do
thank you for help
and sorry for my bad english
im having trouble with these bsod
Crash Dump Analysis
On Mon 09/05/2011 13:50:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050911-17066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x97F7, 0x97F900012FEF)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 09/05/2011 13:48:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050911-14289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFFD7FFD000000, 0x0, 0xFFFFF800033023FA, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 08/05/2011 11:18:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050811-10873-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0x6E81000, 0x1, 0x73F7500A, 0x8)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 07/05/2011 10:22:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050711-18720-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88007B8D828, 0xFFFFF88007B8D090, 0xFFFFF800033F80F3)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sat 07/05/2011 10:14:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050711-16364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF6C6F7800088, 0x0, 0xFFFFF80003293D83, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Link RemovedLink Removed
dunno what to do
thank you for help
and sorry for my bad english
Last edited:
Solution
cybercore
New Member
- Joined
- Jul 7, 2009
- Messages
- 15,641
Memory:
1. Make sure RAM settings are up to the manufacturers rates.
2. Attach CPUZ CPU tab
3. Attach Passmark RAMMon HTML.zip
4. Uninstall Daemon Tools
sptd.sys Sun Oct 11 16:55:14 2009
Link Removed
5. Update drivers:
Copy Protection platform developed by Tages SA
lirsgt.sys Sat Mar 06 14:53:01 2004http://www.tagesprotection.com/
Logitech Camera
LVUSBS64.sys Sat Jul 26 11:06:36 2008
ASUS Kernel Mode Driver for NT
EIO64.sys Tue Jul 21 22:34:42 2009
JMicron RAID Driver
jraid.sys Fri Jul 17 11:31:50 2009
CRASH DUMPS
DRIVERS
1. Make sure RAM settings are up to the manufacturers rates.
2. Attach CPUZ CPU tab
3. Attach Passmark RAMMon HTML.zip
4. Uninstall Daemon Tools
sptd.sys Sun Oct 11 16:55:14 2009
Link Removed
5. Update drivers:
Copy Protection platform developed by Tages SA
lirsgt.sys Sat Mar 06 14:53:01 2004http://www.tagesprotection.com/
Logitech Camera
LVUSBS64.sys Sat Jul 26 11:06:36 2008
ASUS Kernel Mode Driver for NT
EIO64.sys Tue Jul 21 22:34:42 2009
JMicron RAID Driver
jraid.sys Fri Jul 17 11:31:50 2009
CRASH DUMPS
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050911-14289-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03261000 PsLoadedModuleList = 0xfffff800`0349ee50
Debug session time: Mon May 9 09:48:19.397 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:29.427
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffd7ffd000000, 0, fffff800033023fa, 7}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteVirtualAddresses+481 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffd7ffd000000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800033023fa, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800035090e0
fffffd7ffd000000
FAULTING_IP:
nt!MiDeleteVirtualAddresses+481
fffff800`033023fa 448b2b mov r13d,dword ptr [rbx]
MM_INTERNAL_CODE: 7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: MsMpEng.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005de26a0 -- (.trap 0xfffff88005de26a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000ffff00000 rbx=0000000000000000 rcx=0000058000000000
rdx=0000000010a93fff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800033023fa rsp=fffff88005de2830 rbp=0000000010a89000
r8=0000000000000000 r9=fffffa80098ea730 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MiDeleteVirtualAddresses+0x481:
fffff800`033023fa 448b2b mov r13d,dword ptr [rbx] ds:aac8:00000000`00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003350849 to fffff800032d1740
STACK_TEXT:
fffff880`05de2538 fffff800`03350849 : 00000000`00000050 fffffd7f`fd000000 00000000`00000000 fffff880`05de26a0 : nt!KeBugCheckEx
fffff880`05de2540 fffff800`032cf82e : 00000000`00000000 fffffd7f`fd000000 fffffa80`06601c00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`05de26a0 fffff800`033023fa : fffffa80`098ea730 55555555`55555555 00000000`00000000 b1f00000`80bf9025 : nt!KiPageFault+0x16e
fffff880`05de2830 fffff800`03304df9 : 00000000`00000000 00000000`10a93fff fffff8a0`00000000 fffff800`00000000 : nt!MiDeleteVirtualAddresses+0x481
fffff880`05de29f0 fffff800`035e8010 : fffffa80`068a1010 0007ffff`00000000 fffffa80`0a085b90 fffffa80`0a085b90 : nt!MiRemoveMappedView+0xd9
fffff880`05de2b10 fffff800`035e841b : 00000000`00000000 00000000`10710000 fffffa80`00000001 00000000`00000601 : nt!MiUnmapViewOfSection+0x1b0
fffff880`05de2bd0 fffff800`032d0993 : fffffa80`08887a90 fffff880`05de2ca0 fffffa80`098ea730 fffffa80`00008000 : nt!NtUnmapViewOfSection+0x5f
fffff880`05de2c20 00000000`7748f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0521d788 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7748f95a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDeleteVirtualAddresses+481
fffff800`033023fa 448b2b mov r13d,dword ptr [rbx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiDeleteVirtualAddresses+481
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiDeleteVirtualAddresses+481
BUCKET_ID: X64_0x50_nt!MiDeleteVirtualAddresses+481
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050711-16364-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`0348ce50
Debug session time: Sat May 7 06:14:40.089 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:39.119
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff6c6f7800088, 0, fffff80003293d83, 5}
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+468 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6c6f7800088, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003293d83, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034f70e0
fffff6c6f7800088
FAULTING_IP:
nt!MiDeleteAddressesInWorkingSet+468
fffff800`03293d83 488b0408 mov rax,qword ptr [rax+rcx]
MM_INTERNAL_CODE: 5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88008acfee0 -- (.trap 0xfffff88008acfee0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000046f7800088 rbx=0000000000000000 rcx=fffff68000000000
rdx=00000000000089b2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003293d83 rsp=fffff88008ad0070 rbp=fffff700010c7408
r8=fffffa80092afec8 r9=0000000000000000 r10=00000000000070ac
r11=fffff70001080000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiDeleteAddressesInWorkingSet+0x468:
fffff800`03293d83 488b0408 mov rax,qword ptr [rax+rcx] ds:0290:fffff6c6`f7800088=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000333e8c1 to fffff800032bf740
STACK_TEXT:
fffff880`08acfd78 fffff800`0333e8c1 : 00000000`00000050 fffff6c6`f7800088 00000000`00000000 fffff880`08acfee0 : nt!KeBugCheckEx
fffff880`08acfd80 fffff800`032bd82e : 00000000`00000000 0000000f`ffffffff fffff680`0007fb00 00000000`0ff62000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`08acfee0 fffff800`03293d83 : fffffa80`0a81a010 fffffa80`0a6c4001 00000000`00000000 fffff880`01856380 : nt!KiPageFault+0x16e
fffff880`08ad0070 fffff800`0329268a : fffffa80`092afb30 fffffa80`00000008 fffff8a0`000070ac fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x468
fffff880`08ad0920 fffff800`035a4dcf : fffff8a0`00f7d060 fffff880`08ad0c20 00000000`00000000 fffffa80`094f8b60 : nt!MmCleanProcessAddressSpace+0x96
fffff880`08ad0970 fffff800`0357d635 : 00000000`000000ff fffff8a0`0112b801 000007ff`fffa0000 fffffa80`07c0cb60 : nt!PspExitThread+0x92f
fffff880`08ad0a30 fffff800`0329c1db : 00000000`00000000 fffffa80`09297820 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`08ad0a60 fffff800`0329c620 : 00000000`774e4298 fffff880`08ad0ae0 fffff800`0357d74c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`08ad0ae0 fffff800`032bea37 : fffffa80`094f8b60 00000000`774e4270 00000000`000000c0 00000000`00412340 : nt!KiInitiateUserApc+0x70
fffff880`08ad0c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiDeleteAddressesInWorkingSet+468
fffff800`03293d83 488b0408 mov rax,qword ptr [rax+rcx]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiDeleteAddressesInWorkingSet+468
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x50_nt!MiDeleteAddressesInWorkingSet+468
BUCKET_ID: X64_0x50_nt!MiDeleteAddressesInWorkingSet+468
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050711-18720-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03253000 PsLoadedModuleList = 0xfffff800`03490e50
Debug session time: Sat May 7 06:22:36.540 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:54.571
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff88007b8d828, fffff88007b8d090, fffff800033f80f3}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+949 )
Followup: MachineOwner
---------
4: 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: fffff88007b8d828
Arg3: fffff88007b8d090
Arg4: fffff800033f80f3
Debugging Details:
------------------
EXCEPTION_RECORD: fffff88007b8d828 -- (.exr 0xfffff88007b8d828)
ExceptionAddress: fffff800033f80f3 (nt!ExFreePoolWithTag+0x0000000000000043)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88007b8d090 -- (.cxr 0xfffff88007b8d090)
rax=0000000000000000 rbx=fffffa8006f49a40 rcx=08fffff8a00d5775
rdx=0000000000000000 rsi=fffff8a00e973010 rdi=fffff88007b8dc38
rip=fffff800033f80f3 rsp=fffff88007b8da60 rbp=fffff800034685a0
r8=fffff8a00d5ef470 r9=00000000000000a0 r10=fffff880009b3960
r11=fffff8a00f33c5a0 r12=fffffa80079f7180 r13=08fffff8a00d5775
r14=fffff8a00e973450 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!ExFreePoolWithTag+0x43:
fffff800`033f80f3 418b45f0 mov eax,dword ptr [r13-10h] ds:002b:08fffff8`a00d5765=????????
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_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 fffff800034fb0e0
ffffffffffffffff
FOLLOWUP_IP:
Ntfs!NtfsCommonClose+949
fffff880`012e3e0c e914fbffff jmp Ntfs!NtfsCommonClose+0x465 (fffff880`012e3925)
FAULTING_IP:
nt!ExFreePoolWithTag+43
fffff800`033f80f3 418b45f0 mov eax,dword ptr [r13-10h]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff880012e3e0c to fffff800033f80f3
STACK_TEXT:
fffff880`07b8da60 fffff880`012e3e0c : fffffa80`079f7180 fffff800`034685a0 fffff8a0`4946744e 00000000`00000009 : nt!ExFreePoolWithTag+0x43
fffff880`07b8db10 fffff880`012bd38f : fffffa80`06f49a40 fffff8a0`0e973140 fffff8a0`0e973010 fffffa80`079f7180 : Ntfs!NtfsCommonClose+0x949
fffff880`07b8dbe0 fffff800`032d0961 : 00000000`00000000 fffff880`016a9000 fffff800`03468501 fffffa80`00000003 : Ntfs!NtfsFspClose+0x15f
fffff880`07b8dcb0 fffff800`03567c06 : 00000000`05d076eb fffffa80`0a3c6040 00000000`00000080 fffffa80`06714040 : nt!ExpWorkerThread+0x111
fffff880`07b8dd40 fffff800`032a1c26 : fffff800`0343de80 fffffa80`0a3c6040 fffff800`0344bc40 fffff880`01247534 : nt!PspSystemThreadStartup+0x5a
fffff880`07b8dd80 00000000`00000000 : fffff880`07b8e000 fffff880`07b88000 fffff880`07b8d700 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsCommonClose+949
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f
STACK_COMMAND: .cxr 0xfffff88007b8d090 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsCommonClose+949
BUCKET_ID: X64_0x24_Ntfs!NtfsCommonClose+949
Followup: MachineOwner
---------
4: 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: fffff88007b8d828
Arg3: fffff88007b8d090
Arg4: fffff800033f80f3
Debugging Details:
------------------
EXCEPTION_RECORD: fffff88007b8d828 -- (.exr 0xfffff88007b8d828)
ExceptionAddress: fffff800033f80f3 (nt!ExFreePoolWithTag+0x0000000000000043)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88007b8d090 -- (.cxr 0xfffff88007b8d090)
rax=0000000000000000 rbx=fffffa8006f49a40 rcx=08fffff8a00d5775
rdx=0000000000000000 rsi=fffff8a00e973010 rdi=fffff88007b8dc38
rip=fffff800033f80f3 rsp=fffff88007b8da60 rbp=fffff800034685a0
r8=fffff8a00d5ef470 r9=00000000000000a0 r10=fffff880009b3960
r11=fffff8a00f33c5a0 r12=fffffa80079f7180 r13=08fffff8a00d5775
r14=fffff8a00e973450 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!ExFreePoolWithTag+0x43:
fffff800`033f80f3 418b45f0 mov eax,dword ptr [r13-10h] ds:002b:08fffff8`a00d5765=????????
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_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: ffffffffffffffff
FOLLOWUP_IP:
Ntfs!NtfsCommonClose+949
fffff880`012e3e0c e914fbffff jmp Ntfs!NtfsCommonClose+0x465 (fffff880`012e3925)
FAULTING_IP:
nt!ExFreePoolWithTag+43
fffff800`033f80f3 418b45f0 mov eax,dword ptr [r13-10h]
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff880012e3e0c to fffff800033f80f3
STACK_TEXT:
fffff880`07b8da60 fffff880`012e3e0c : fffffa80`079f7180 fffff800`034685a0 fffff8a0`4946744e 00000000`00000009 : nt!ExFreePoolWithTag+0x43
fffff880`07b8db10 fffff880`012bd38f : fffffa80`06f49a40 fffff8a0`0e973140 fffff8a0`0e973010 fffffa80`079f7180 : Ntfs!NtfsCommonClose+0x949
fffff880`07b8dbe0 fffff800`032d0961 : 00000000`00000000 fffff880`016a9000 fffff800`03468501 fffffa80`00000003 : Ntfs!NtfsFspClose+0x15f
fffff880`07b8dcb0 fffff800`03567c06 : 00000000`05d076eb fffffa80`0a3c6040 00000000`00000080 fffffa80`06714040 : nt!ExpWorkerThread+0x111
fffff880`07b8dd40 fffff800`032a1c26 : fffff800`0343de80 fffffa80`0a3c6040 fffff800`0344bc40 fffff880`01247534 : nt!PspSystemThreadStartup+0x5a
fffff880`07b8dd80 00000000`00000000 : fffff880`07b8e000 fffff880`07b88000 fffff880`07b8d700 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsCommonClose+949
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc14f
STACK_COMMAND: .cxr 0xfffff88007b8d090 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsCommonClose+949
BUCKET_ID: X64_0x24_Ntfs!NtfsCommonClose+949
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050811-10873-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0325a000 PsLoadedModuleList = 0xfffff800`03497e50
Debug session time: Sun May 8 07:18:31.664 2011 (UTC - 4:00)
System Uptime: 0 days 2:00:00.694
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {6e81000, 1, 73f7500a, 8}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43017 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 0000000006e81000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: 0000000073f7500a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000008, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800035020e0
0000000006e81000
FAULTING_IP:
+6266396537393863
00000000`73f7500a ?? ???
MM_INTERNAL_CODE: 8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: League of Lege
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003276f89 to fffff800032ca740
STACK_TEXT:
fffff880`07b64ab8 fffff800`03276f89 : 00000000`00000050 00000000`06e81000 00000000`00000001 fffff880`07b64c20 : nt!KeBugCheckEx
fffff880`07b64ac0 fffff800`032c882e : 00000000`00000001 00000000`0018ed28 fffff880`07b64b01 fffffa80`06b86780 : nt! ?? ::FNODOBFM::`string'+0x43017
fffff880`07b64c20 00000000`73f7500a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0018ecc4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73f7500a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+43017
fffff800`03276f89 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+43017
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+43017
BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+43017
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050911-17066-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03267000 PsLoadedModuleList = 0xfffff800`034a4e50
Debug session time: Mon May 9 09:50:33.618 2011 (UTC - 4:00)
System Uptime: 0 days 0:01:36.648
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {5003, fffff70001080000, 97f7, 97f900012fef}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+21b46 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 00000000000097f7
Arg4: 000097f900012fef
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_5003
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: Skype.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000333f986 to fffff800032d7740
STACK_TEXT:
fffff880`09012a68 fffff800`0333f986 : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`000097f7 : nt!KeBugCheckEx
fffff880`09012a70 fffff800`032f204c : fffff680`000afb90 fffff880`09012b40 00000000`00000000 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x21b46
fffff880`09012ac0 fffff800`032d582e : 00000000`00000001 00000000`1588a800 00000000`14a90001 00000000`11210b02 : nt!MmAccessFault+0xc4c
fffff880`09012c20 00000000`76849b60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`00189f2c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76849b60
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+21b46
fffff800`0333f986 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+21b46
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
BUCKET_ID: X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+21b46
Followup: MachineOwner
---------DRIVERS
Code:
start end module name
fffff880`10b6d000 fffff880`10bab000 1394ohci 1394ohci.sys Mon Jul 13 20:07:12 2009 (4A5BCC30)
fffff880`10bab000 fffff880`10bf0000 a8h26a29 a8h26a29.SYS Tue Jul 14 17:12:55 2009 (4A5CF4D7)
fffff880`01000000 fffff880`01057000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`02c00000 fffff880`02c8a000 afd afd.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0fe00000 fffff880`0fe16000 AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`00e1e000 fffff880`00e29000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`045c5000 fffff880`045cd000 ASACPI ASACPI.sys Wed May 13 21:25:17 2009 (4A0B72FD)
fffff880`04195000 fffff880`0419b000 AsIO AsIO.sys Mon Apr 06 03:21:08 2009 (49D9AD64)
fffff880`00fa9000 fffff880`00fb2000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fb2000 fffff880`00fdc000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`06400000 fffff880`0644f000 atksgt atksgt.sys Mon Oct 20 03:50:38 2008 (48FC384E)
fffff880`02cd3000 fffff880`02cda000 Beep Beep.SYS Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`04184000 fffff880`04195000 blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`06525000 fffff880`06543000 bowser bowser.sys Wed Feb 23 00:15:06 2011 (4D6497DA)
fffff960`007b0000 fffff960`007d7000 cdd cdd.dll Wed Jan 26 01:31:34 2011 (4D3FBFC6)
fffff880`00dcf000 fffff880`00df9000 cdrom cdrom.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00cc0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`04ad6000 fffff880`04ae8000 circlass circlass.sys Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`01200000 fffff880`01230000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00d25000 fffff880`00d83000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`014a3000 fffff880`01516000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`045ef000 fffff880`045ff000 CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`05a00000 fffff880`05a0e000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`04166000 fffff880`04184000 dfsc dfsc.sys Mon Jul 13 19:23:44 2009 (4A5BC200)
fffff880`04157000 fffff880`04166000 discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01400000 fffff880`01416000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`04a00000 fffff880`04a22000 drmk drmk.sys Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`05a28000 fffff880`05a31000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05a1c000 fffff880`05a28000 dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`05a31000 fffff880`05a44000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`05bf2000 fffff880`05bfe000 Dxapi Dxapi.sys Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`04456000 fffff880`0454a000 dxgkrnl dxgkrnl.sys Tue Jan 25 23:22:56 2011 (4D3FA1A0)
fffff880`0454a000 fffff880`04590000 dxgmms1 dxgmms1.sys Tue Jan 25 23:22:12 2011 (4D3FA174)
fffff880`0414e000 fffff880`04157000 EIO64 EIO64.sys Tue Jul 21 22:34:42 2009 (4A667AC2)
fffff880`06b19000 fffff880`06b4f000 fastfat fastfat.SYS Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`00e29000 fffff880`00e3d000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00d83000 fffff880`00dcf000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`01527000 fffff880`01531000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`015b7000 fffff880`015f1000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`0178a000 fffff880`017d4000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`045d9000 fffff880`045e6000 GEARAspiWDM GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
fffff800`0321e000 fffff800`03267000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`04590000 fffff880`045b4000 HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
fffff880`04a79000 fffff880`04a92000 HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
fffff880`05a54000 fffff880`05a5c080 HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`05a46000 fffff880`05a54000 hidusb hidusb.sys Mon Jul 13 20:06:22 2009 (4A5BCBFE)
fffff880`0645d000 fffff880`06525000 HTTP HTTP.sys Mon Jul 13 19:22:16 2009 (4A5BC1A8)
fffff880`017ee000 fffff880`017f7000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`041c1000 fffff880`041d7000 intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`00e00000 fffff880`00e1e000 jraid jraid.sys Fri Jul 17 11:31:50 2009 (4A609966)
fffff880`10bf0000 fffff880`10bff000 kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04a28000 fffff880`04a36000 kbdhid kbdhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff800`00b9f000 fffff800`00ba9000 kdcom kdcom.dll Sat Feb 05 07:21:45 2011 (4D4D40D9)
fffff880`04a93000 fffff880`04ad6000 ks ks.sys Wed Mar 03 23:32:25 2010 (4B8F37D9)
fffff880`01489000 fffff880`014a3000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0175f000 fffff880`0178a000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`04a22000 fffff880`04a27200 ksthunk ksthunk.sys Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`04be4000 fffff880`04bfb000 LEqdUsb LEqdUsb.Sys Tue Aug 24 13:21:23 2010 (4C73FF93)
fffff880`04ae8000 fffff880`04aebd80 LGBusEnum LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
fffff880`06b64000 fffff880`06b66480 LGVirHid LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
fffff880`04a43000 fffff880`04a4b000 LHidEqd LHidEqd.Sys Tue Aug 24 13:21:26 2010 (4C73FF96)
fffff880`0407d000 fffff880`04092000 LHidFilt LHidFilt.Sys Tue Aug 24 13:21:36 2010 (4C73FFA0)
fffff880`0644f000 fffff880`0645c000 lirsgt lirsgt.sys Sat Mar 06 14:53:01 2004 (404A2C1D)
fffff880`03942000 fffff880`03957000 lltdio lltdio.sys Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`0404a000 fffff880`0405e000 LMouFilt LMouFilt.Sys Tue Aug 24 13:21:43 2010 (4C73FFA7)
fffff880`038a7000 fffff880`038ca000 luafv luafv.sys Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`0391c000 fffff880`03926980 LVUSBS64 LVUSBS64.sys Sat Jul 26 11:06:36 2008 (488B3D7C)
fffff880`00ccd000 fffff880`00d11000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`05a0e000 fffff880`05a1c000 monitor monitor.sys Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`0403b000 fffff880`0404a000 mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`04a36000 fffff880`04a43000 mouhid mouhid.sys Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00f8f000 fffff880`00fa9000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02c99000 fffff880`02cca000 MpFilter MpFilter.sys Tue Sep 14 20:19:28 2010 (4C901110)
fffff880`06b09000 fffff880`06b19000 MpNWMon MpNWMon.sys Tue Sep 14 20:19:30 2010 (4C901112)
fffff880`06543000 fffff880`0655b000 mpsdrv mpsdrv.sys Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`0655b000 fffff880`06588000 mrxsmb mrxsmb.sys Wed Feb 23 00:15:23 2011 (4D6497EB)
fffff880`06588000 fffff880`065d6000 mrxsmb10 mrxsmb10.sys Wed Feb 23 00:15:14 2011 (4D6497E2)
fffff880`065d6000 fffff880`065f9000 mrxsmb20 mrxsmb20.sys Wed Feb 23 00:15:13 2011 (4D6497E1)
fffff880`00fdc000 fffff880`00fe7000 msahci msahci.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`02d38000 fffff880`02d43000 Msfs Msfs.SYS Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01057000 fffff880`01061000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`0142b000 fffff880`01489000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`04143000 fffff880`0414e000 mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`017dc000 fffff880`017ee000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`0160d000 fffff880`016ff000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0fe3a000 fffff880`0fe46000 ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`0fe46000 fffff880`0fe75000 ndiswan ndiswan.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`04b58000 fffff880`04b6d000 NDProxy NDProxy.SYS Mon Jul 13 20:10:05 2009 (4A5BCCDD)
fffff880`02c8a000 fffff880`02c99000 netbios netbios.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`02d7f000 fffff880`02dc4000 netbt netbt.sys Mon Jul 13 19:21:28 2009 (4A5BC178)
fffff880`016ff000 fffff880`0175f000 NETIO NETIO.SYS Thu Apr 08 22:43:59 2010 (4BBE946F)
fffff880`06b4f000 fffff880`06b64000 NisDrvWFP NisDrvWFP.sys Tue Sep 14 20:20:25 2010 (4C901149)
fffff880`02d43000 fffff880`02d54000 Npfs Npfs.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`04137000 fffff880`04143000 nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`03267000 fffff800`03844000 nt ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`0123b000 fffff880`013de000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`02cca000 fffff880`02cd3000 Null Null.SYS Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`10b1a000 fffff880`10b1b180 nvBridge nvBridge.kmd Thu Apr 07 23:14:49 2011 (4D9E7DA9)
fffff880`04b7a000 fffff880`04ba7000 nvhda64v nvhda64v.sys Thu Mar 03 10:59:02 2011 (4D6FBAC6)
fffff880`0fe75000 fffff880`10b19300 nvlddmkm nvlddmkm.sys Thu Apr 07 23:22:12 2011 (4D9E7F64)
fffff880`02dcd000 fffff880`02df3000 pacer pacer.sys Mon Jul 13 20:09:41 2009 (4A5BCCC5)
fffff880`011cf000 fffff880`011e4000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00ef0000 fffff880`00f23000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`011f9000 fffff880`01200000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00f7f000 fffff880`00f8f000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01516000 fffff880`01527000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`03800000 fffff880`038a6000 peauth peauth.sys Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`04ba7000 fffff880`04be4000 portcls portcls.sys Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d11000 fffff880`00d25000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0fe16000 fffff880`0fe3a000 rasl2tp rasl2tp.sys Mon Jul 13 20:10:11 2009 (4A5BCCE3)
fffff880`041d7000 fffff880`041f2000 raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`04000000 fffff880`04021000 raspptp raspptp.sys Mon Jul 13 20:10:18 2009 (4A5BCCEA)
fffff880`04021000 fffff880`0403b000 rassstp rassstp.sys Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`040e6000 fffff880`04137000 rdbss rdbss.sys Mon Jul 13 19:24:09 2009 (4A5BC219)
fffff880`02d1d000 fffff880`02d26000 RDPCDD RDPCDD.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02d26000 fffff880`02d2f000 rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`02d2f000 fffff880`02d38000 rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`0157d000 fffff880`015b7000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`03957000 fffff880`0396f000 rspndr rspndr.sys Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`10b1c000 fffff880`10b6d000 Rt64win7 Rt64win7.sys Tue Jan 12 01:37:27 2010 (4B4C18A7)
fffff880`01193000 fffff880`011c2000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`0396f000 fffff880`0397a000 secdrv secdrv.SYS Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`045cd000 fffff880`045d9000 serenum serenum.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`0409a000 fffff880`040b7000 serial serial.sys Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`017d4000 fffff880`017dc000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`01064000 fffff880`0118a000 sptd sptd.sys Sun Oct 11 16:55:14 2009 (4AD24632)
fffff880`06a74000 fffff880`06b09000 srv srv.sys Wed Feb 23 00:16:24 2011 (4D649828)
fffff880`06a0d000 fffff880`06a74000 srv2 srv2.sys Wed Feb 23 00:15:59 2011 (4D64980F)
fffff880`0397a000 fffff880`039a7000 srvnet srvnet.sys Wed Feb 23 00:15:49 2011 (4D649805)
fffff880`0407b000 fffff880`0407c480 swenum swenum.sys Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`01801000 fffff880`019fe000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`039a7000 fffff880`039b9000 tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
fffff880`02d72000 fffff880`02d7f000 TDI TDI.SYS Mon Jul 13 19:21:18 2009 (4A5BC16E)
fffff880`02d54000 fffff880`02d72000 tdx tdx.sys Mon Jul 13 19:21:15 2009 (4A5BC16B)
fffff880`040d2000 fffff880`040e6000 termdd termdd.sys Mon Jul 13 20:16:36 2009 (4A5BCE64)
fffff960`00410000 fffff960`0041a000 TSDDD TSDDD.dll unavailable (00000000)
fffff880`0419b000 fffff880`041c1000 tunnel tunnel.sys Mon Jul 13 20:09:37 2009 (4A5BCCC1)
fffff880`04aec000 fffff880`04afe000 umbus umbus.sys Mon Jul 13 20:06:56 2009 (4A5BCC20)
fffff880`03927000 fffff880`03941c00 usbaudio usbaudio.sys Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`04a5c000 fffff880`04a79000 usbccgp usbccgp.sys Mon Jul 13 20:06:45 2009 (4A5BCC15)
fffff880`05a44000 fffff880`05a45f00 USBD USBD.SYS Mon Jul 13 20:06:23 2009 (4A5BCBFF)
fffff880`045b4000 fffff880`045c5000 usbehci usbehci.sys Mon Jul 13 20:06:30 2009 (4A5BCC06)
fffff880`04afe000 fffff880`04b58000 usbhub usbhub.sys Mon Jul 13 20:07:09 2009 (4A5BCC2D)
fffff880`04400000 fffff880`04456000 USBPORT USBPORT.SYS Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`0405e000 fffff880`04079000 USBSTOR USBSTOR.SYS Mon Jul 13 20:06:34 2009 (4A5BCC0A)
fffff880`011c2000 fffff880`011cf000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`02cda000 fffff880`02ce8000 vga vga.sys Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`05a5e000 fffff880`05bf2000 viahduaa viahduaa.sys Thu Jul 09 23:07:01 2009 (4A56B055)
fffff880`02ce8000 fffff880`02d0d000 VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`011e4000 fffff880`011f9000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00f23000 fffff880`00f7f000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01531000 fffff880`0157d000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`040b7000 fffff880`040d2000 wanarp wanarp.sys Mon Jul 13 20:10:21 2009 (4A5BCCED)
fffff880`02d0d000 fffff880`02d1d000 watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00e3d000 fffff880`00ee1000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ee1000 fffff880`00ef0000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`02dc4000 fffff880`02dcd000 wfplwf wfplwf.sys Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`00050000 fffff960`00362000 win32k win32k.sys Wed Mar 02 22:58:01 2011 (4D6F11C9)
fffff880`045e6000 fffff880`045ef000 wmiacpi wmiacpi.sys Mon Jul 13 19:31:02 2009 (4A5BC3B6)
fffff880`0118a000 fffff880`01193000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`038ca000 fffff880`038eb000 WudfPf WudfPf.sys Mon Jul 13 20:05:37 2009 (4A5BCBD1)
fffff880`038eb000 fffff880`0391c000 WUDFRd WUDFRd.sys Mon Jul 13 20:06:06 2009 (4A5BCBEE)
Unloaded modules:
fffff880`01416000 fffff880`01424000 crashdmp.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000E000
fffff880`01600000 fffff880`0160c000 dump_ataport
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000C000
fffff880`017f7000 fffff880`01800000 dump_atapi.s
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00009000
fffff880`013de000 fffff880`013f1000 dump_dumpfve
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00013000
fffff880`04a5a000 fffff880`04a5c000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00002000
fffff880`04a4f000 fffff880`04a5a000 LVUSBS64.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000B000
fffff880`04a4d000 fffff880`04a4f000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00002000
fffff880`04a42000 fffff880`04a4d000 LVUSBS64.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000B000
fffff880`04a40000 fffff880`04a42000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00002000
fffff880`04a35000 fffff880`04a40000 LVUSBS64.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000B000
fffff880`04a33000 fffff880`04a35000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00002000
fffff880`04a28000 fffff880`04a33000 LVUSBS64.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000B000
fffff880`04b78000 fffff880`04b7a000 USBD.SYS
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00002000
fffff880`04b6d000 fffff880`04b78000 LVUSBS64.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000B000
fffff880`0404a000 fffff880`0407b000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00031000
fffff880`0404a000 fffff880`0407b000 WUDFRd.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 00031000vallanzaska
New Member
- Joined
- May 9, 2011
- Messages
- 6
- Thread Author
-
- #3
here it is
Link Removed
Link Removed
thank so much for the help
how can i update those drivers?
thank you again for your time
Link Removed
Link Removed
thank so much for the help
how can i update those drivers?
thank you again for your time
cybercore
New Member
- Joined
- Jul 7, 2009
- Messages
- 15,641
CPU and memory settings look right, and the sticks are identical which is very good.
As for the drivers, check support sites:
http://www.tagesprotection.com/
Link Removed
Link Removed
Link Removed due to 404 Error
As for the drivers, check support sites:
http://www.tagesprotection.com/
Link Removed
Link Removed
Link Removed due to 404 Error
Last edited:
vallanzaska
New Member
- Joined
- May 9, 2011
- Messages
- 6
- Thread Author
-
- #5
i did also a test with memtest 86
i did it with only one ram slot with every ram with no errors
when i tried it with all 4 ram slot full i had like 200k errors...dunno why
i did it with only one ram slot with every ram with no errors
when i tried it with all 4 ram slot full i had like 200k errors...dunno why
cybercore
New Member
- Joined
- Jul 7, 2009
- Messages
- 15,641
Similar threads
- Article
- Article