Random BSODs

[exile]

Hey guys,

For a long time I have been experiencing random BSODs in my Windows 7 Ultimate 64-bit system. I have not noticed any pattern in which they occur, but the errors are usually 0x0000001E and similar errors.

EDIT: Here is my crash report as the sticky advises, it wouldn't upload onto the forum though, so it's being hosted on mediafire.

Crash Info.zip

Here is an error report of an 0x0000003B error I just got:


BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF80002A7764C
BCP3: FFFFF88008FC1EA0
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Full WhoCrashed report:

On Fri 16/7/2010 2:50:26 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A7764C, 0xFFFFF88008FC1EA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\071610-26332-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 Thu 15/7/2010 8:51:32 AM your computer crashed
This was likely caused by the following module: intelppm.sys
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\071510-30232-01.dmp
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 Mon 12/7/2010 2:53:27 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\071210-41480-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 Sun 4/7/2010 7:36:07 AM your computer crashed
This was likely caused by the following module: rt64win7.sys
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\070410-23056-01.dmp
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8136/8168/8169 NDIS 6.20 64-bit Driver



On Sun 27/6/2010 6:05:29 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF880FFFD7E40, 0xE, 0x0, 0xFFFFF80002AC9A60)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\062710-29312-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 Wed 23/6/2010 12:32:32 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A78FA2, 0xFFFFF88006E7A100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\062310-24632-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 Tue 15/6/2010 10:16:46 AM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002A7964C, 0xFFFFF880092700B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\061510-27424-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 Sun 6/6/2010 5:46:01 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\060610-27253-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 5/6/2010 10:49:29 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFFA8005F583E0, 0x2, 0x1, 0xFFFFF80002A8B64C)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\060510-26239-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 Thu 22/4/2010 11:37:26 AM your computer crashed
This was likely caused by the following module: intelppm.sys
Bugcheck code: 0xA (0xFFFFF800BEC5CBD4, 0x2, 0x0, 0xFFFFF80002ADC43C)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\042210-31137-01.dmp
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 Tue 20/4/2010 6:20:49 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000288D64C, 0xFFFFF88007AC80B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\042010-24928-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 17/4/2010 7:33:14 AM your computer crashed
This was likely caused by the following module: intelppm.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002B6C94C, 0xFFFFF88008DA8110, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\041710-23415-01.dmp
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 16/4/2010 5:38:49 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028D564C, 0xFFFFF880094D30B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\041610-52213-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 Thu 15/4/2010 9:57:18 AM your computer crashed
This was likely caused by the following module: intelppm.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800028CB64C, 0xFFFFF8800845B120, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\041510-24991-01.dmp
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
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 10/4/2010 6:40:43 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x9F (0x3, 0xFFFFFA8002E8F060, 0xFFFFF80000B9C518, 0xFFFFFA8004A6F8C0)
Error: DRIVER_POWER_STATE_FAILURE
Dump file: C:\Windows\Minidump\041010-28860-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 9/4/2010 7:41:03 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0xFFFFF80000A0DBC8, 0x2, 0x0, 0xFFFFF8000288B8A2)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\040910-29125-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 Mon 5/4/2010 12:04:07 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA0 (0xB, 0x8FEDE000, 0x3, 0x903A000)
Error: INTERNAL_POWER_ERROR
Dump file: C:\Windows\Minidump\040510-24133-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.



Any help regarding this problem is greatly appreciated.

 

[ttran]

As you can see in the result that you got, there are several things are being blamed. First of all it is intelppm.sys, which is intel processor driver. Please download and install fresh copy of it
Secondly, Realtek Ethernet driver Rt64win7.sys was blamed. Please download and install fresh copy of it as well

Look like all of these crash dump are memory related as I can see the exception code c000005, I would suggest you to download third party called memtestx86, burn it to CD using ISO Recorder v3 and let it run for at least 6,7 passes.

Please update following drivers to most up-to-date version:

AF15BDA  AF15BDA.sys  Tue Apr 29 15:34:37 2008 (4816DD9D) [/I][/I][COLOR=Blue]DigitalNow TinyTwin DVB-T Receiver

Please remove virtual CD program such as Deamon tool or Alcohol 120%, they use sptd.sys, which I found in the loaded drivers, known for causing BSODs. Please use this tool to remove sptd.sys
DuplexSecure - Downloads

What third party antivirus software are you using?

BUGCHECK SUMMARY:

BugCheck 3B, {c0000005, fffff80002a7764c, fffff88008fc1ea0, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )

Followup: MachineOwner
---------[/U][/I]
BugCheck A, {fffffa8005f583e0, 2, 1, fffff80002a8b64c}

Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )

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

BugCheck A, {fffff800bec5cbd4, 2, 0, fffff80002adc43c}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002b6c94c, fffff88008da8110, 0}

Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )

Followup: MachineOwner
---------
BugCheck 9F, {3, fffffa8002e8f060, fffff80000b9c518, fffffa8004a6f8c0}

Probably caused by : pci.sys

Followup: MachineOwner
BugCheck A0, {b, 8fede000, 3, 903a000}

Probably caused by : ntkrnlmp.exe ( nt!PopWriteHiberPages+a3 )

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

---------

Let us know if you need help

Tuan

[/COLOR]

 

[exile]

Hello, thanks for the reply.

I have successfully removed SPTD. In regards to your question, I am using Avast! Antivirus, and occasionally running MBAM scans.

What is the process for updating CPU drivers? I am unfamiliar with it, as I have never had to update them.

 

[reventon]

Hi,

A few other things for you to take care of immediately.

1. Uninstall Avast. While I do not think it is the cause in this case I have seen it at fault before and it pays to get rid of it just in case.

Download the Avast Removal Tool (ART) from here -> save to desktop.

Boot into SAFEMODE - NO Networking. Then go to desktop, RIGHT-click on the ART icon and select Run as Administrator.

When complete - re-boot.

Install MS Security Essentials --> http://www.microsoft.com/Security_Essentials/

Then reset the Windows Firewall to its default settings -
START -> type cmd.exe -> right-click -> run as administrator -> type netsh advfirewall reset press enter

2. Enable driver verifier. No 3rd Party drivers were explicitly named so hopefully driver verifier can cause one to BSOD.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Regards,
Reventon

BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 16 14:45:45.164 2010 (GMT+12)
System Uptime: 0 days 2:04:55.130
BugCheck 3B, {c0000005, fffff80002a7764c, fffff88008fc1ea0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )
BUGCHECK_STR:  0x3B
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 15 20:49:09.813 2010 (GMT+12)
System Uptime: 0 days 4:27:06.780
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon Jul 12 02:51:23.543 2010 (GMT+12)
System Uptime: 0 days 9:41:15.120
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jul  4 19:34:35.490 2010 (GMT+12)
System Uptime: 0 days 6:00:32.456
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : Rt64win7.sys ( Rt64win7+27c9 )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun 27 18:03:55.970 2010 (GMT+12)
System Uptime: 0 days 6:03:11.937
BugCheck A, {fffff880fffd7e40, e, 0, fffff80002ac9a60}
Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+60 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun 24 00:31:01.779 2010 (GMT+12)
System Uptime: 0 days 4:27:45.745
BugCheck 3B, {c0000005, fffff80002a78fa2, fffff88006e7a100, 0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+74a78 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Jun 15 22:14:59.018 2010 (GMT+12)
System Uptime: 0 days 4:25:38.985
BugCheck 3B, {c0000005, fffff80002a7964c, fffff880092700b0, 0}
Probably caused by : win32k.sys ( win32k!AllocThreadBufferWithTag+24 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 17:44:30.410 2010 (GMT+12)
System Uptime: 0 days 3:20:36.376
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 22:47:33.846 2010 (GMT+12)
System Uptime: 0 days 7:56:16.812
BugCheck A, {fffffa8005f583e0, 2, 1, fffff80002a8b64c}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )
BUGCHECK_STR:  0xA
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 22 23:34:32.787 2010 (GMT+12)
System Uptime: 0 days 5:40:41.753
BugCheck A, {fffff800bec5cbd4, 2, 0, fffff80002adc43c}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Apr 20 18:18:00.584 2010 (GMT+12)
System Uptime: 0 days 0:22:22.550
BugCheck 3B, {c0000005, fffff8000288d64c, fffff88007ac80b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avgemc.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Apr 17 19:32:14.524 2010 (GMT+12)
System Uptime: 0 days 3:55:22.491
BugCheck 3B, {c0000005, fffff80002b6c94c, fffff88008da8110, 0}
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Apr 16 17:36:31.485 2010 (GMT+12)
System Uptime: 0 days 6:05:14.077
BugCheck 3B, {c0000005, fffff800028d564c, fffff880094d30b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Apr 15 21:55:24.472 2010 (GMT+12)
System Uptime: 0 days 6:58:19.064
BugCheck 3B, {c0000005, fffff800028cb64c, fffff8800845b120, 0}
Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Apr 10 18:33:39.155 2010 (GMT+12)
System Uptime: 0 days 3:57:57.122
BugCheck 9F, {3, fffffa8002e8f060, fffff80000b9c518, fffffa8004a6f8c0}
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Apr  9 19:39:30.477 2010 (GMT+12)
System Uptime: 0 days 7:23:17.444
BugCheck A, {fffff80000a0dbc8, 2, 0, fffff8000288b8a2}
Probably caused by : ntkrnlmp.exe ( nt!KiDeferredReadyThread+1c2 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Apr  5 01:26:35.108 2010 (GMT+12)
System Uptime: 0 days 2:58:47.684
BugCheck A0, {b, 8fede000, 3, 903a000}
Probably caused by : ntkrnlmp.exe ( nt!PopWriteHiberPages+a3 )
BUGCHECK_STR:  0xA0
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨[/FONT]

 

[exile]

I don't think it's Avast's problem, as I was using AVG untill this week, but it began to not let me activate the resident shield, so I switched to Avast.

 

[reventon]

I don't think it's Avast's problem, as I was using AVG untill this week, but it began to not let me activate the resident shield, so I switched to Avast.

AVG was also running at the time of one of your BSODs:

[font=lucida console]Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue Apr 20 18:18:00.584 2010 (GMT+12)
System Uptime: 0 days 0:22:22.550
BugCheck 3B, {c0000005, fffff8000288d64c, fffff88007ac80b0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+cc )
BUGCHECK_STR:  0x3B
PROCESS_NAME:  [COLOR=Red]avgemc.exe[/COLOR]
[/font]

Which confused me a lot as I could see that you had Avast not AVG loaded at the time of the most recent crash.

My advice still stands, however I am pretty sure that it is not at fault.

 

[exile]

Apparently that BSOD happened on April 20, which is a long time before I installed AVG.

 

[reventon]

avgemc.exe - Google Search

It is definitely part of AVG, and it is very unusual for the dumps to be incorrect.

 

[exile]

Oops, sorry, I meant avast.

 

[ttran]

Please remove any third party Antivirus software that you are using, they are known for causing BSOD, no exception. You can always reinstall them later if they are not the causes. For now, just use one antivirus software which is known for BSODs free, it is Microsoft Security Essential as Reventon suggest