all kind of BSOD is happening

xhei88 · 03 Jul 2010

I have so many time testing my pc and is always the same. Random bsod happens all the time, i have try to change 32 to 62 bit and again happens, to reformat etc

My symtem is windows 7 32bit
intel i5 2.66
2x2 g ram ddr3
etc

I make some analysis with WhoCrashed for anly today and yesterday problems

On Sat 7/3/2010 16:14:59 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC0402128, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070310-21406-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 15:59:32 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC04020C2, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070310-21375-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 15:54:33 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x2, 0x2, 0x1, 0x82C9FB78)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\070310-22562-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:38:10 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC1 (0xB23A4EE0, 0xB23A4CE8, 0x54124, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-21734-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:35:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xB5BD8EF0, 0xB5BD8F28, 0xA070833)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\070310-21750-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:31:48 your computer crashed
This was likely caused by the following module: netio.sys
Bugcheck code: 0xC1 (0xB3BB8FF0, 0xB3BB8CA8, 0xE14014, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-21609-01.dmp
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:29:56 your computer crashed
This was likely caused by the following module: pciidex.sys
Bugcheck code: 0xA (0xBA239000, 0x2, 0x0, 0x82C81E50)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\070310-28687-01.dmp
file path: C:\Windows\system32\drivers\pciidex.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: PCI IDE Bus Driver Extension
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:17:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC1 (0xB1DFCEE0, 0xB1DFC228, 0x254124, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-21890-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:15:11 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFFFEA, 0x1, 0x82C9E348, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\070310-16734-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:11:59 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x82C96B2E, 0x80EB19BC, 0x80EB15A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\070310-16078-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:08:35 your computer crashed
This was likely caused by the following module: avipbb.sys
Bugcheck code: 0xC1 (0xB4F9EF78, 0xB4F9ECA8, 0xA1C08C, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-17515-01.dmp
file path: C:\Windows\system32\drivers\avipbb.sys
product: AntiVir Desktop
company: Avira GmbH
description: Avira Driver for Security Enhancement

On Fri 7/2/2010 14:58:37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC04020FE, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070210-22484-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Fri 7/2/2010 11:14:21 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC0402130, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070210-17250-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Fri 7/2/2010 11:08:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC04020BE, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070210-18578-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

I have atach the minidumb files. Please can anybody help me ?? thanks anyway

zigzag3143 · 03 Jul 2010

xhei88 said:

I have so many time testing my pc and is always the same. Random bsod happens all the time, i have try to change 32 to 62 bit and again happens, to reformat etc

My symtem is windows 7 32bit
intel i5 2.66
2x2 g ram ddr3
etc

I make some analysis with WhoCrashed for anly today and yesterday problems

On Sat 7/3/2010 16:14:59 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC0402128, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070310-21406-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 15:59:32 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC04020C2, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070310-21375-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 15:54:33 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x2, 0x2, 0x1, 0x82C9FB78)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\070310-22562-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:38:10 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC1 (0xB23A4EE0, 0xB23A4CE8, 0x54124, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-21734-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:35:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xB5BD8EF0, 0xB5BD8F28, 0xA070833)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\070310-21750-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:31:48 your computer crashed
This was likely caused by the following module: netio.sys
Bugcheck code: 0xC1 (0xB3BB8FF0, 0xB3BB8CA8, 0xE14014, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-21609-01.dmp
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:29:56 your computer crashed
This was likely caused by the following module: pciidex.sys
Bugcheck code: 0xA (0xBA239000, 0x2, 0x0, 0x82C81E50)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\070310-28687-01.dmp
file path: C:\Windows\system32\drivers\pciidex.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: PCI IDE Bus Driver Extension
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:17:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC1 (0xB1DFCEE0, 0xB1DFC228, 0x254124, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-21890-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:15:11 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x50 (0xFFFFFFEA, 0x1, 0x82C9E348, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\Windows\Minidump\070310-16734-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:11:59 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007E (0xC0000005, 0x82C96B2E, 0x80EB19BC, 0x80EB15A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\070310-16078-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 7/3/2010 11:08:35 your computer crashed
This was likely caused by the following module: avipbb.sys
Bugcheck code: 0xC1 (0xB4F9EF78, 0xB4F9ECA8, 0xA1C08C, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Dump file: C:\Windows\Minidump\070310-17515-01.dmp
file path: C:\Windows\system32\drivers\avipbb.sys
product: AntiVir Desktop
company: Avira GmbH
description: Avira Driver for Security Enhancement

On Fri 7/2/2010 14:58:37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC04020FE, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070210-22484-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Fri 7/2/2010 11:14:21 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC0402130, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070210-17250-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Fri 7/2/2010 11:08:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xC04020BE, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\070210-18578-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

I have atach the minidumb files. Please can anybody help me ?? thanks anyway

Ok so more than half of these show memory management as the problem. To test your memory download an app called memtestx86, burn it to cd, and run it for at least 6 passes.

If any errors show, and they will, your memory is probably bad and should be replaced.

Ken

xhei88 · 04 Jul 2010

Hi Ken, Thanks for the reply.
I run memtest ovenight for 16 passes and no errors. what can i do else? thanks in advance

Jonathan_King · 04 Jul 2010

I see two problems.

First, is Avira. It is indirectly blamed by one dmp. Please remove it with this tool: http://www.avira.com/en/documents/ut...ninstXPeng.zip

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

The other is SPTD.sys. A component of Daemon Tools and some other CD virtualization programs, it is notorious for causing BSODs.

Please remove any such programs you may have installed, and then run this SPTD installer/uninstaller to completely remove it: DuplexSecure - Downloads

Summary of the Dumps:

Code:


Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 07:39:45.591 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:00.576
BugCheck A, {2, 2, 1, 82c9fb78}
Probably caused by : ntkrnlmp.exe ( nt!DeleteNodeFromTree+72 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 07:34:05.578 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:42.625
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 07:20:00.430 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:50.415
BugCheck A, {ba239000, 2, 0, 82c81e50}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : PCIIDEX.SYS ( PCIIDEX!BmSetup+3d )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  sidebar.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 07:16:08.312 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:18.296
BUGCHECK_STR:  0xC1_32
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Sat Jul  3 07:07:06.671 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:57.703
*** WARNING: Unable to verify timestamp for avipbb.sys
*** ERROR: Module load completed but symbols could not be loaded for avipbb.sys
BUGCHECK_STR:  0xC1_32
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  rundll32.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 07:12:56.785 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:28.816
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Debug session time: Fri Jul  2 07:07:24.235 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:30.266
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

ttran · 04 Jul 2010

Hi xhei88

Did you use memtestx86 to test your RAM as Ken suggested? Memory Diagnostics

Also, Virtual CD program such as Deamon tool or Alcohol 120% are known for causing BSODs. Please remove them completely, then using this tool to remove sptd.sys, which is a component of those Virtual CD program that based on that, I knew you have Deamon tool or Alcohol 120%
DuplexSecure - Downloads

Code:

sptd     sptd.sys     Mon Oct 12 03:54:02 2009 (4AD245EA)

If you need a program that doesn't use sptd.sys (Bsod cause), you can use Magicdisc, I believe it doesn't contain sptd.sys and it is free too.

Let us know if you need help

Tuan

xhei88 · 04 Jul 2010

Hello Jonathan and Tuan. Thanks for the help.
I use the memtest exactly how Ken suggest, overnight with no errors.
I make what you guys sad, i unistall avira and demon tools, and some unececary programs.Till now no bsod. But i think this is not the faul of this two programs. I experience bsod before instaling avira and demon tools, at the firs when i bought my pc. The only problem i have at the firs time was the drivers for my nvidia 250 gts. now after updates i expected more rarely but is the only problem i expected from the firs bsod till now. can be the grapphic card cause tewh bsod ?? maybe the shared memory of ram for the graphics cause this ? i have 4 gb ram and its readeble only 3.2, its normal for 32 bit system. anyway thank you so far, i am monitoring my system, if any other bsod happens i will post minidump files. thank again.

ttran · 04 Jul 2010

I've heard about shared memory of ram for graphic card cause BSODs before. Try to set it to normal to test
Thanks for reporting back

Tuan