New
#1
BSODs all time.
Hello everybody.
I don´t know what can i do. I did many things and the BSOD continue.
I changed de hard disk, format and instal OS again, changed memory, put atualized drivers, upgade bios and chipset.
Here is the report from Whocrashed.
Thanks!
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 945 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8588025856 total
VM: 2147352576, free: 1941831680
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 24/07/2012 04:56:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-17050-01.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x5039)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880011C0039, 0xFFFFF88008E80D80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software SYSTEM_SERVICE_EXCEPTION
On Tue 24/07/2012 04:56:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: aswtdi.sys (aswTdi+0x5039)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880011C0039, 0xFFFFF88008E80D80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\aswtdi.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! TDI Filter Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswtdi.sys (avast! TDI Filter Driver, AVAST Software).
Google query: aswtdi.sys AVAST Software SYSTEM_SERVICE_EXCEPTION
On Tue 24/07/2012 03:59:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072412-15022-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003304760, 0xFFFFF880029B0030, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 24/07/2012 02:03:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-22791-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC9744)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800032DC744, 0xFFFFF88003D88C58, 0xFFFFF88003D884B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Tue 24/07/2012 01:44:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-14710-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xC9744)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800032D1744, 0xFFFFF88003D8FC58, 0xFFFFF88003D8F4B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 Tue 24/07/2012 01:20:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-18252-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032E8F8C, 0xFFFFF88008347E60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Mon 23/07/2012 23:15:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-16832-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1719A0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Sistema Operacional Microsoft® Windows®
company: Microsoft Corporation
description: Driver TCP/IP
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 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 Mon 23/07/2012 23:10:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-18267-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80610)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 Mon 23/07/2012 22:47:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072312-16629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1 (0x75032E09, 0x0, 0xFFFF, 0xFFFFF8800754DCA0)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Quote