Bsods ... :(

ashnaile · 28 Oct 2010

Hi, heres all the stuff requested .... I tryed to do the perfmon thing but it wouldnt give me any way to save a report or whatever etc ...

Pcs a amd phenom 2 x4 955, 4 gigs of ocz @ 1600, ati hd 5770,.

Windows 7 home 64 bit, been installed about 8 months when i built the pc, retail version.

Just started randomly bsoding on me 2 days ago, the day after i upgraded the drivers on the video card from some ancient version, next morning wake up to a bsod. No hardware changed or anything like that, ran memtest for 4 passes without errores etc.

It will go for a few hours now before dying ... im pretty sure its probably something driver related but im not sure ... if you could look at the pack of stuff that bsod dump util collected id be much obliged, thougha s i said i typed that whole perfmon / report and it wasnt a valid command etc.

anyways ... thanks :) (weird ... font change ... odd ...)

CarlTR6 · 28 Oct 2010

Welcome to the forum ashnaile; sorry you are having problems. I looked at your five most recent dumps. They indicate a hardware/hardware related problem.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

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

Error code 1A, MEMORY_MANAGEMENT. Usual causes: Device driver, memory, kernel.

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

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`03046e50
Debug session time: Thu Oct 28 14:13:43.045 2010 (GMT-4)
System Uptime: 0 days 6:15:41.731
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa7ffffffe60, 2, 1, fffff80002ec0349}

Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )

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

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

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

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b10e0
 fffffa7ffffffe60 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmZeroPageThread+3d4
fffff800`02ec0349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009a9a80 -- (.trap 0xfffff880009a9a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000013 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ec0349 rsp=fffff880009a9c10 rbp=00000000000000ff
 r8=0000000000000000  r9=0000058000000000 r10=0000000000000002
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MmZeroPageThread+0x3d4:
fffff800`02ec0349 f0410fba6d1000  lock bts dword ptr [r13+10h],0 ds:45b0:00000000`00000010=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e78ca9 to fffff80002e79740

STACK_TEXT:  
fffff880`009a9938 fffff800`02e78ca9 : 00000000`0000000a fffffa7f`fffffe60 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9940 fffff800`02e77920 : 00000000`00000000 ffffffff`fffffff7 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a80 fffff800`02ec0349 : fffffa80`03902800 00000000`00000008 00000000`000000ff 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9c10 fffff800`0311dc06 : fffffa80`039d45b0 00000000`00000080 fffffa80`039d4b30 fffff800`02e57c19 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d40 fffff800`02e57c26 : fffff800`02ff3e80 fffffa80`039d45b0 fffff800`03001c40 0002a8fc`000749f2 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmZeroPageThread+3d4
fffff800`02ec0349 f0410fba6d1000  lock bts dword ptr [r13+10h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MmZeroPageThread+3d4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MmZeroPageThread+3d4

BUCKET_ID:  X64_0xA_nt!MmZeroPageThread+3d4

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff8800892d6c0, 0, 0}

Probably caused by : NETIO.SYS ( NETIO!WfpHashtableInsert+1c )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800892d6c0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


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

FAULTING_IP: 
+5491952f01a6da74
fffff880`0892d6c0 d8e5            fsub    st,st(5)

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031090e0
 0000000000000000 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  utorrent.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff8800892e5d8 -- (.exr 0xfffff8800892e5d8)
ExceptionAddress: fffff80002eb126f (nt!RtlInsertEntryHashTable+0x0000000000000073)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800892e680 -- (.trap 0xfffff8800892e680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=6966744e021d0003 rbx=0000000000000000 rcx=0000000001b8070a
rdx=fffffa8004b6f700 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eb126f rsp=fffff8800892e810 rbp=0000000000000000
 r8=fffffa80048f67c0  r9=000000000000007f r10=0000124d3fcdadfb
r11=000000000000ccb8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!RtlInsertEntryHashTable+0x73:
fffff800`02eb126f 488b4810        mov     rcx,qword ptr [rax+10h] ds:0002:6966744e`021d0013=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f63bdb to fffff80002ed1740

STACK_TEXT:  
fffff880`0892d608 fffff800`02f63bdb : 00000000`0000001e ffffffff`c0000005 fffff880`0892d6c0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0892d610 fffff800`02f22d30 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KipFatalFilter+0x1b
fffff880`0892d650 fffff800`02effd1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`0892d690 fffff800`02ef740d : fffff800`0301dbc4 fffff880`089302d0 00000000`00000000 fffff800`02e61000 : nt!_C_specific_handler+0x8c
fffff880`0892d700 fffff800`02efea90 : fffff800`0301dbc4 fffff880`0892d778 fffff880`0892e5d8 fffff800`02e61000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0892d730 fffff800`02f0b9ef : fffff880`0892e5d8 fffff880`0892de40 fffff880`00000000 fffff880`00000004 : nt!RtlDispatchException+0x410
fffff880`0892de10 fffff800`02ed0d82 : fffff880`0892e5d8 fffff880`0892ecf8 fffff880`0892e680 fffff880`017ea6c0 : nt!KiDispatchException+0x16f
fffff880`0892e4a0 fffff800`02ecf68a : 00000000`00000002 fffffa80`0420ae80 fffff880`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`0892e680 fffff800`02eb126f : ffffffff`c0000225 fffffa80`04930978 fffffa80`07c462d0 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`0892e810 fffff880`017a309c : fffff880`0892ecf8 fffffa80`07c462d0 00000000`00000002 00000000`00000000 : nt!RtlInsertEntryHashTable+0x73
fffff880`0892e860 fffff880`017a304d : 00000000`00000000 fffff880`0892ecf8 fffffa80`07c462d0 00000000`00000011 : NETIO!WfpHashtableInsert+0x1c
fffff880`0892e890 fffff880`017a31c3 : fffff880`0892f770 00000000`00000002 fffffa80`07c462d0 00000000`00000000 : NETIO!KfdAleInsertFlowContextTable+0x9d
fffff880`0892e8e0 fffff880`018367c7 : fffffa80`00000000 fffff880`00000000 00000000`00000000 00000000`00000000 : NETIO!KfdAleInitializeFlowTable+0x13
fffff880`0892e910 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x8d7


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!WfpHashtableInsert+1c
fffff880`017a309c 84c0            test    al,al

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  NETIO!WfpHashtableInsert+1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

FAILURE_BUCKET_ID:  X64_0x1E_NETIO!WfpHashtableInsert+1c

BUCKET_ID:  X64_0x1E_NETIO!WfpHashtableInsert+1c

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000053fe8, fa30000032bf2867, fffff68000053fe0}

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

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: fffff68000053fe8
Arg3: fa30000032bf2867
Arg4: fffff68000053fe0

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  avgnt.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f3d6c8 to fffff80002ecb740

STACK_TEXT:  
fffff880`08ab77b8 fffff800`02f3d6c8 : 00000000`0000001a 00000000`00000403 fffff680`00053fe8 fa300000`32bf2867 : nt!KeBugCheckEx
fffff880`08ab77c0 fffff800`02efc381 : 00000000`00000000 fffff680`00053ff8 fffffa80`07fe2b30 00000000`00059d04 : nt! ?? ::FNODOBFM::`string'+0x31ef2
fffff880`08ab7970 fffff800`02f0d0da : 00000000`00000000 00000000`0b02efff fffffa80`00000000 fffffa80`07fe2b30 : nt!MiDeleteVirtualAddresses+0x408
fffff880`08ab7b30 fffff800`02eca993 : ffffffff`ffffffff 00000000`0008e310 00000000`0008e308 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`08ab7c20 00000000`77ab009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ab009a


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

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

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

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

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

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

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

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 9ab36, 2, 9ab34}

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: 000000000009ab36, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000009ab34, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  Steam.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f4b38c to fffff80002ebb740

STACK_TEXT:  
fffff880`0a0e1ca8 fffff800`02f4b38c : 00000000`0000004e 00000000`00000099 00000000`0009ab36 00000000`00000002 : nt!KeBugCheckEx
fffff880`0a0e1cb0 fffff800`02f2d6a0 : 00000000`00000000 fffff680`0006fed8 00000000`00000000 fffff900`c4f18434 : nt!MiBadShareCount+0x4c
fffff880`0a0e1cf0 fffff800`02eec381 : 00000000`00000000 fffff680`0006fff8 fffffa80`07654060 fffffa80`044f62c0 : nt! ?? ::FNODOBFM::`string'+0x31eca
fffff880`0a0e1ea0 fffff800`02efd0da : 00000000`00000000 00000000`0e271fff fffffa80`00000000 fffffa80`07654060 : nt!MiDeleteVirtualAddresses+0x408
fffff880`0a0e2060 fffff800`02eba993 : ffffffff`ffffffff fffff880`0a0e2320 fffff880`0a0e2388 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0a0e2150 fffff800`02eb6f30 : fffff960`00195460 00000000`00000001 fffff900`c00bf010 fffff900`c264c640 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a0e22e8 fffff960`00195460 : 00000000`00000001 fffff900`c00bf010 fffff900`c264c640 00000000`00000000 : nt!KiServiceLinkage
fffff880`0a0e22f0 fffff960`001957b4 : ffffffff`00000000 fffff880`00000000 fffff900`c264c640 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`0a0e2440 fffff960`001566e5 : ffffffff`d0051436 fffff900`c264c640 00000000`00001436 00000000`7efdb000 : win32k!bDeleteSurface+0x34
fffff880`0a0e2470 fffff800`02eba993 : fffffa80`044f62c0 fffff880`0a0e2520 00000000`02cd01a0 00000000`0000c02e : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`0a0e24a0 00000000`74cf2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008d3a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74cf2dd9


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

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

I recommend that you start your troubleshooting by uninstalling Avira using this removal tool: Tool. Avira has been known to cause BSOD's on some Win 7 systems. Download and install Microsoft Security Essentials in its place.

I find a number of out of date drivers on your system; some are quite obsolete. Older drivers can and do cause memory corruption and crashes. Update these drivers starting with those in bold font.

Rt64win7.sys Thu Feb 26 04:04:13 2009 - Rt64win7.sys - Latest PCIe GBE (GigaBit Ethernet) drivers here: Realtek

snapman.sys Thu Nov 22 03:19:33 2007 - Acronis True Image Snapshot Manager driver http://www.acronis.com
uninstall or purchase a new copy

tdrpman.sys Mon Nov 12 08:36:33 2007 - Acronis Try&Decide and Restore Points Volume Filter Driver http://www.acronis.com
uninstall or purchase a new copy

tifsfilt.sys Wed Aug 29 08:37:29 2007 - Acronis True Image FS Filter http://www.acronis.com
uninstall or purchase a new copy

timntr.sys Wed Aug 29 08:38:23 2007 - Acronis True Image Backup Archive Explorer http://www.acronis.com
uninstall or purchase a new copy

Update Rt64win7.sys. Uninstall Acronis completely. If you wish to use Acronis, download and install the latest version. Reboot and run your system; let's see how it does. If you get another BSOD upload and we will go from there. Update us on how your system is doing.

Jonathan_King · 28 Oct 2010

Out of the 5 dumps I ran, 3 of them appear to be network-related. I suspect that either AVG, Avira, your NIC drivers, or the combination is the problem here. Running multiple security programs is a recipe for crashes, or just poor performance.

Remove AVG with this tool: http://download.avg.com/filedir/util...removerx64.exe

Uninstall Avira from Programs and Features.

Replace it with MSE: http://www.microsoft.com/security_essentials

Install these Realtek NIC drivers: Realtek

At least one dump points to what I suspect SPTD is causing. Remove Daemon Tools (the program that uses this), and then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v174-x64.exe

Also, update Acronis TrueImage to the latest version.

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Oct 28 14:13:43.045 2010 (UTC - 4:00)
System Uptime: 0 days 6:15:41.731
BugCheck A, {fffffa7ffffffe60, 2, 1, fffff80002ec0349}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 19:26:05.608 2010 (UTC - 4:00)
System Uptime: 0 days 2:47:49.325
BugCheck 4E, {99, 9ab36, 2, 9ab34}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
BUGCHECK_STR:  0x4E_99
PROCESS_NAME:  Steam.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 08:45:02.549 2010 (UTC - 4:00)
System Uptime: 0 days 0:15:47.860
BugCheck 1E, {ffffffffc0000005, fffff8800892d6c0, 0, 0}
Probably caused by : NETIO.SYS ( NETIO!WfpHashtableInsert+1c )
BUGCHECK_STR:  0x1E_c0000005
PROCESS_NAME:  utorrent.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 08:25:56.484 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:17.185
BugCheck 1A, {403, fffff68000053fe8, fa30000032bf2867, fffff68000053fe0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31ef2 )
BUGCHECK_STR:  0x1a_403
PROCESS_NAME:  avgnt.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 27 08:23:09.816 2010 (UTC - 4:00)
System Uptime: 0 days 1:19:48.111
BugCheck A, {fffffa802396900e, 2, 1, fffff80002e9d649}
Probably caused by : ntkrnlmp.exe ( nt!RtlClearBits+69 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  setup_wm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

ashnaile · 28 Oct 2010

Ah, hadnt seen i still had pieces of avg still installed ... scrapped that and avira and got mse, updated the realtek drivers etc.

Im not sure what that acronis stuff is ... =/ Cant find anything on my pc etc, evidently its a backup util from googling, but ive never installed that etc.

Anyways we shall see how it goes as far as any more bsods, it would take 4-5 hours and be random before so if it happens ill repost a new dump file.

Thanks

Jonathan_King · 28 Oct 2010

Ah, I understand.

I did a bit more research, to learn that Seagate DiscWizard also uses that driver. I see you have that installed.

That is the program you should remove. Apologies for wasting your time.

ashnaile · 28 Oct 2010

Ah, yea i had to install that to get my second hdd to be recognized in windows, it was detected in bios just fine but without that installed it wouldnt show in windows, most irritating.

Jonathan_King · 28 Oct 2010

I suspect that means Windows didn't give it a drive letter. Try removing the program, and if the drive disappears, manually give it one.

https://www.sevenforums.com/tutorials...ndows-7-a.html

ashnaile · 29 Oct 2010

So things had been working fine all day yesterday, today i get on, 3-4 hours later the ati catalyst control center crashes and it bsods like 2 seconds later =/ Heres a new dump.

i wonder if i need to buy a new video card or if its just a driver thing? heres the dump.

Jonathan_King · 29 Oct 2010

I still see Daemon Tools installed. Please remove it, and then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v174-x64.exe

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Oct 29 10:44:36.348 2010 (UTC - 4:00)
System Uptime: 0 days 3:50:28.643
BugCheck 3B, {c0000005, fffff960000f9fac, fffff88008cbd180, 0}
Probably caused by : hardware ( win32k!xxxInternalGetMessage+34 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  LWEMon.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

ashnaile · 29 Oct 2010

Hmm well its all removed now ... see if it keeps bsoding ....