please check dump for me having some odd issues
#1
Posted 07 April 2010 - 07:29 AM
==================================================
Dump File : 040110-18579-01.dmp
Crash Time : 4/1/2010 6:19:30 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04c848f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a63cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\040110-18579-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 040110-17690-01.dmp
Crash Time : 4/1/2010 5:36:59 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04cbe8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a63cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\040110-17690-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 040110-24492-01.dmp
Crash Time : 4/1/2010 5:29:27 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04cbe8f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a63cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\040110-24492-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 032610-18376-01.dmp
Crash Time : 3/26/2010 10:45:51 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04c958f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a63cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\032610-18376-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 032610-20092-01.dmp
Crash Time : 3/26/2010 10:38:24 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04c988f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a63cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\032610-20092-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
==================================================
Dump File : 032610-23431-01.dmp
Crash Time : 3/26/2010 10:32:39 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04cd58f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a63cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Computer Name :
Full Path : C:\Windows\minidump\032610-23431-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 07/04/2010 8:22:27 AM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 07/04/2010 12:19:40 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MpCmdRun.exe, version: 2.1.6519.0, time stamp: 0x4b207819 Faulting module name: mssewat.dll, version: 1.0.1961.0, time stamp: 0x4b81283b Exception code: 0xc0000005 Fault offset: 0x00000000000045a4 Faulting process id: 0x1078 Faulting application start time: 0x01cad64c97bb8197 Faulting application path: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe Faulting module path: C:\Program Files\Microsoft Security Essentials\mssewat.dll Report Id: d64ef1f2-423f-11df-8f35-001e8cc947e7
Log: 'Application' Date/Time: 07/04/2010 12:17:00 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 07/04/2010 12:17:00 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 07/04/2010 12:09:54 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MpCmdRun.exe, version: 2.1.6519.0, time stamp: 0x4b207819 Faulting module name: mssewat.dll, version: 1.0.1961.0, time stamp: 0x4b81283b Exception code: 0xc0000005 Fault offset: 0x00000000000045a4 Faulting process id: 0xb48 Faulting application start time: 0x01cad64b326178ec Faulting application path: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe Faulting module path: C:\Program Files\Microsoft Security Essentials\mssewat.dll Report Id: 7909a3ed-423e-11df-8f35-001e8cc947e7
Log: 'Application' Date/Time: 07/04/2010 12:09:32 PM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x80070005.
Log: 'Application' Date/Time: 07/04/2010 1:58:03 AM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program Poker3d.exe version 1.0.0.110 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: c74 Start Time: 01cad5f1e2c50390 Termination Time: 530 Application Path: C:\Program Files (x86)\Play+Smile\Texas Hold'em Poker 3D - Deluxe Edition\Poker3d.exe Report Id: bf70216a-41e8-11df-8e47-001e8cc947e7
Log: 'Application' Date/Time: 06/04/2010 5:09:13 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MpCmdRun.exe, version: 2.1.6519.0, time stamp: 0x4b207819 Faulting module name: mssewat.dll, version: 1.0.1961.0, time stamp: 0x4b81283b Exception code: 0xc0000005 Fault offset: 0x00000000000045a4 Faulting process id: 0x2dc Faulting application start time: 0x01cad5abe0aa628c Faulting application path: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe Faulting module path: C:\Program Files\Microsoft Security Essentials\mssewat.dll Report Id: 1f04b1e0-419f-11df-8e47-001e8cc947e7
Log: 'Application' Date/Time: 06/04/2010 5:03:47 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 06/04/2010 5:03:47 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 06/04/2010 4:59:26 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MpCmdRun.exe, version: 2.1.6519.0, time stamp: 0x4b207819 Faulting module name: mssewat.dll, version: 1.0.1961.0, time stamp: 0x4b81283b Exception code: 0xc0000005 Fault offset: 0x00000000000045a4 Faulting process id: 0x9b8 Faulting application start time: 0x01cad5aa7b0c5bb6 Faulting application path: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe Faulting module path: C:\Program Files\Microsoft Security Essentials\mssewat.dll Report Id: c1b2c1ab-419d-11df-8e47-001e8cc947e7
Log: 'Application' Date/Time: 06/04/2010 4:59:00 PM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x80070005.
Log: 'Application' Date/Time: 06/04/2010 4:03:49 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 06/04/2010 4:03:49 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 06/04/2010 12:18:27 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MpCmdRun.exe, version: 2.1.6519.0, time stamp: 0x4b207819 Faulting module name: mssewat.dll, version: 1.0.1961.0, time stamp: 0x4b81283b Exception code: 0xc0000005 Fault offset: 0x00000000000045a4 Faulting process id: 0x10dc Faulting application start time: 0x01cad58342a1160c Faulting application path: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe Faulting module path: C:\Program Files\Microsoft Security Essentials\mssewat.dll Report Id: 806a316f-4176-11df-8e2a-001e8cc947e7
Log: 'Application' Date/Time: 06/04/2010 12:15:32 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
Log: 'Application' Date/Time: 06/04/2010 12:15:32 PM
Type: Error Category: 0
Event: 3012 Source: Microsoft-Windows-LoadPerf
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.
Log: 'Application' Date/Time: 06/04/2010 12:08:41 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MpCmdRun.exe, version: 2.1.6519.0, time stamp: 0x4b207819 Faulting module name: mssewat.dll, version: 1.0.1961.0, time stamp: 0x4b81283b Exception code: 0xc0000005 Fault offset: 0x00000000000045a4 Faulting process id: 0x9e4 Faulting application start time: 0x01cad581dd027844 Faulting application path: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe Faulting module path: C:\Program Files\Microsoft Security Essentials\mssewat.dll Report Id: 23ac781e-4175-11df-8e2a-001e8cc947e7
Log: 'Application' Date/Time: 06/04/2010 12:08:18 PM
Type: Error Category: 0
Event: 4103 Source: Microsoft-Windows-Winlogon
Windows license activation failed. Error 0x80070005.
Log: 'Application' Date/Time: 05/04/2010 9:56:22 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: MpCmdRun.exe, version: 2.1.6519.0, time stamp: 0x4b207819 Faulting module name: mssewat.dll, version: 1.0.1961.0, time stamp: 0x4b81283b Exception code: 0xc0000005 Fault offset: 0x00000000000045a4 Faulting process id: 0xedc Faulting application start time: 0x01cad50ad401c12a Faulting application path: c:\Program Files\Microsoft Security Essentials\MpCmdRun.exe Faulting module path: C:\Program Files\Microsoft Security Essentials\mssewat.dll Report Id: 11fcc9d2-40fe-11df-8ec0-001e8cc947e7
Log: 'Application' Date/Time: 05/04/2010 9:51:00 PM
Type: Error Category: 0
Event: 3011 Source: Microsoft-Windows-LoadPerf
Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 06/04/2010 4:58:49 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 01/04/2010 10:19:23 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 01/04/2010 9:36:54 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 01/04/2010 9:29:21 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 27/03/2010 2:45:45 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 27/03/2010 2:38:18 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Log: 'System' Date/Time: 27/03/2010 2:32:32 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 07/04/2010 12:10:09 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL
Log: 'System' Date/Time: 07/04/2010 12:10:06 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 07/04/2010 12:09:19 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASDIFSV.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Log: 'System' Date/Time: 07/04/2010 12:09:19 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASKUTIL.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Log: 'System' Date/Time: 07/04/2010 3:39:01 AM
Type: Error Category: 0
Event: 7016 Source: Service Control Manager
The NVIDIA Stereoscopic 3D Driver Service service has reported an invalid current state 0.
Log: 'System' Date/Time: 06/04/2010 4:59:41 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL
Log: 'System' Date/Time: 06/04/2010 4:59:37 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 06/04/2010 4:58:49 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASDIFSV.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Log: 'System' Date/Time: 06/04/2010 4:58:49 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASKUTIL.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Log: 'System' Date/Time: 06/04/2010 4:58:58 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 12:58:04 PM on ?4/?6/?2010 was unexpected.
Log: 'System' Date/Time: 06/04/2010 3:59:55 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk6\DR6.
Log: 'System' Date/Time: 06/04/2010 12:08:53 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL
Log: 'System' Date/Time: 06/04/2010 12:08:52 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 06/04/2010 12:08:04 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASDIFSV.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Log: 'System' Date/Time: 06/04/2010 12:08:04 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASKUTIL.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Log: 'System' Date/Time: 06/04/2010 4:35:29 AM
Type: Error Category: 0
Event: 7016 Source: Service Control Manager
The NVIDIA Stereoscopic 3D Driver Service service has reported an invalid current state 0.
Log: 'System' Date/Time: 05/04/2010 9:46:51 PM
Type: Error Category: 0
Event: 7026 Source: Service Control Manager
The following boot-start or system-start driver(s) failed to load: SASDIFSV SASKUTIL
Log: 'System' Date/Time: 05/04/2010 9:46:51 PM
Type: Error Category: 0
Event: 7009 Source: Service Control Manager
A timeout was reached (30000 milliseconds) while waiting for the Roxio Hard Drive Watcher 12 service to connect.
Log: 'System' Date/Time: 05/04/2010 9:46:04 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASDIFSV.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Log: 'System' Date/Time: 05/04/2010 9:46:04 PM
Type: Error Category: 0
Event: 1060 Source: Application Popup
\??\C:\Program Files (x86)\SUPERAntiSpyware\SASKUTIL.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
Thank you to anyone who can help me with this!
#2
Posted 07 April 2010 - 02:30 PM
***** A. If you have more than one RAM module installed, try starting computer with one RAM stick at a time.
NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A
B. If you have only one RAM stick installed...
...run memtest...
1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

10. Once the CD is created, boot from it, and memtest will automatically start to run.
The running program will look something like this depending on the size and number of ram modules installed:

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.
This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

The following image is the test results area:

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.
Also how many anti-virus's do you have installed i see super and Microsoft security suite. any others?
This post has been edited by computerxpds: 07 April 2010 - 02:31 PM
-Welcome To BC!! Follow me on twitter:
Please DO NOT PM me for personal help or advice, that is what our forums are for.
If I have replied to a topic and you reply and I havent gotten back to you within 48 hours (2 days) then PM me by going to my profile and clicking the PM button.
Some important links: Malwarebytes|BC Rules|
#3
Posted 08 April 2010 - 03:41 PM
i have 4 x 1gb sticks
the system runs fine but randomly crashes on games. i have not seen any major problems. but i want to find this problem. should i test them one at a time or all 4 at once.
#4
Posted 08 April 2010 - 04:07 PM
-Welcome To BC!! Follow me on twitter:
Please DO NOT PM me for personal help or advice, that is what our forums are for.
If I have replied to a topic and you reply and I havent gotten back to you within 48 hours (2 days) then PM me by going to my profile and clicking the PM button.
Some important links: Malwarebytes|BC Rules|
#5
Posted 08 April 2010 - 04:28 PM
The Memtest suggestion was a good one...but I would not limit myself to that.
Louis
#6
Posted 08 April 2010 - 05:42 PM
#7
Posted 08 April 2010 - 06:08 PM
q6600 cpu with thermalright ultra 120 cooler
asus maximus formula board
4gb mem with corsair 3 fan cooler
320gb wd hd
evga 9800gx2 graphics
dvd
silverstone 1000 watt psu
silverstone tjo6 case 3 x 120mm fans, 1 x 80mm fan
case runs at 32 all the time it seems
fresh install of win 7 64bit no overclocking just memory settings at 5-5-5-15 at 2.1v on 1066
all latest driver and bios
#9
Posted 08 April 2010 - 06:31 PM
spyware utilites:
super antispyware
malwarebytes
spybot s&d
advanced uninstaller pro
#10
Posted 08 April 2010 - 07:52 PM
Quote
- Microsoft Security Essentials Review: Installing and Using
- Paul Thurrott's SuperSite for Windows: MSE Installing and Using
- Review: Microsoft Security Essentials
- Microsoft Security Essentials Support - How to Videos
No single product is 100% foolproof and can prevent, detect and remove all threats at any given time. The security community is in a constant state of change as new infections appear. Each vendor has its own definition of what constitutes malware and scanning your computer using different criteria will yield different results. The fact that each program has its own definition files means that some malware may be picked up by one that could be missed by another. Thus, a multi-layered defense using several anti-spyware products (including an effective firewall) to supplement your anti-virus combined with common sense and safe surfing habits provides the most complete protection.
As a general rule, using more than one anti-spyware program like Malwarebytes' Anti-Malware, SuperAntispyware, Spybot S&D, Ad-Aware, etc will not conflict with each other or your anti-virus if using only one of them for real time protection and others as stand-alone scanners. In fact, doing so increases your protection coverage without causing the same kind of conflicts or affecting the stability of your system that can occur when using more than one anti-virus. The overlap of protection from using different signature databases will aid in detection and removal of more threats when scanning your system for malware. However, if using all their real-time resident shields (TeaTimer, Ad-Watch, MBAM Protection Module, Spyware Terminator Shields, etc) together at the same time, there can be conflicts when each application tries to compete for resources and exclusive rights to perform an action. Additionally, competing tools may even provide redundant alerts which can be annoying and/or confusing.
See Bleeping Computer's Freeware Replacements For Common Commercial Apps and List of Virus & Malware Resources.
Uninstalling your current AV (MSE) is the next step in diagnosing your BSOD's. I've seen the Kernel crash reported in the memory dumps due to AV software a lot lately. Uninstall the AV and use a different one...BSOD's stop.
Note: MSE may not be the cause of your BSOD's, but it's certainly a possibility. The only way to know for sure is to uninstall it and try without it. If you still get the BSOD's, you can put MSE back on if you want to. But if the BSOD's suddenly stop after removing MSE, you get to decide on a new AV.
Personally, I do not like MSE. There are much better free AV's out there (Avast, Avira, etc..).
I'm assuming you game with this PC? Based on the specs you posted, it seems like a gaming computer. Do the BSOD's happen while you're gaming? What kind of temps are you seeing (CPU, graphics card, etc...). I noticed you mentioned a lot of fans in your specs, but overheating can also cause BSOD's (doubt this is your cause, though).
Any other relevant information you have on your computer, what you do with it, etc...?
#11
Posted 08 April 2010 - 08:48 PM
#12
Posted 08 April 2010 - 09:13 PM
Well, if you remove one AV, you have to install another....there's no getting around it. My advice was to remove MSE and try a different AV to see if MSE was causing the blue screens. My opinion was that Avast is the best choice.
Let me know whether or not you still have problems after removing MSE.
One thing I would like you to do: download Speccy, but don't run it just yet.
Do some gaming for a little while (30 minutes should be long enough), then run Speccy and post a screenshot of the Summary. It should look like this (with your specs, of course):
http://img402.imageshack.us/img402/1944/speccy.png
This post has been edited by keyboardNinja: 09 April 2010 - 12:22 AM
#13
Posted 08 April 2010 - 10:36 PM

here is what i got after 2 rounds on modern warfare 2
and im running avast free now
#14
Posted 08 April 2010 - 10:43 PM
#15
Posted 08 April 2010 - 11:49 PM
We'll see if Avast treats your system a little better. Like I said, we'll only know MSE was the problem if you don't get anymore BSOD's. Regardless, I think Avast is a much better AV anyway...
What setting do you have your memory set to now? If you were overclocking it, that could be another possible cause of your BSOD's.

Help

Back to top












