I agree with Greg, anytime you get a virus, trojan, you should consider re-installing the OS. It's actually the fastest way to get your system up and running with no chance of the trojan returning.
After following Greg's advice, if you are still having crashes, try the suggestions below.
Your crashes are:
Code:
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility
This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003714100
GetUlongFromAddress: unable to read from fffff800037141c0
00000000000000ec Nonpaged pool
FAILURE_BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115
----------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x000000C5: DRIVER_CORRUPTED_EXPOOL
Usual causes: Device driver, ?Memory
The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.
PROCESS_NAME: wmpnscfg.exe
IMAGE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0xC5_2_nt!ExDeferredFreePool+249
--------------------------------------------------------------------------------------------------------------------------------------------
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
This is a very common bug check.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
PROCESS_NAME: wmpnetwk.exe
FAILURE_BUCKET_ID: X64_0x1E_c0000005_R_nt!ObpCreateHandle+29a
----------------------------------------------------------------------------------------------------------------------------------------------
IRQL_NOT_LESS_OR_EQUAL (a)
ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys - Nvidia driver
MODULE_NAME: nvlddmkm
FAILURE_BUCKET_ID: X64_0xA_nvlddmkm+17ea00
----------------------------------------------------------------------------------------------------------------------------
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes: Device driver
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c8100
GetUlongFromAddress: unable to read from fffff800036c81c0
0000000000000030 Nonpaged pool
PROCESS_NAME: TeaTimer.exe
IMAGE_NAME: afd.sys - Windows Ancillary Function Driver for WinSock
FAILURE_BUCKET_ID: X64_0xD1_afd!AfdTLConnectComplete+24
-----------------------------------------------------------------------------------------------------------------------------
IRQL_NOT_LESS_OR_EQUAL (a)
Probably caused by : ntkrnlmp.exe ( nt!KeStackAttachProcess+115 )
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000370f100
GetUlongFromAddress: unable to read from fffff8000370f1c0
00000000000000dc Nonpaged pool
FAILURE_BUCKET_ID: X64_0xA_nt!KeStackAttachProcess+115
-----------------------------------------------------------------------------------------------------------------------------
System Event Logs:
Code:
Event[216]:
Log Name: System
Source: Microsoft-Windows-SharedAccess_NAT
Date: 2012-02-18T12:37:27.000
Event ID: 34005
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
The ICS_IPV6 was unable to allocate bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.
Event[287]:
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 2012-02-18T15:40:16.000
Event ID: 10000
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Unable to start a DCOM Server: {DC0C2640-1415-4644-875C-6F4D769839BA}. The error:
"740"
Happened while starting this command:
"C:\Program Files (x86)\iTunes\iTunes.exe" -Embedding
Event[528]:
Log Name: System
Source: Microsoft-Windows-SharedAccess_NAT
Date: 2012-02-19T12:38:11.000
Event ID: 34005
Task: N/A
Level: Warning
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
The ICS_IPV6 was unable to allocate bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.
App Event LOgs:
Code:
Event[45]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20101219-2140.dmp
C:\Windows\Temp\WER-41506624-0.sysdata.xml
C:\Windows\Temp\WERAFFA.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0ae9b038
Analysis symbol:
Rechecking for solution: 0
Report Id: b7cb9440-0bfb-11e0-9dbc-8397591cef01
Report Status: 0
Event[46]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Minidump\030510-18985-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-35349-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERFC93.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0af4fc96
Analysis symbol:
Rechecking for solution: 0
Report Id: 030510-18985-01
Report Status: 0
Event[47]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Minidump\021210-21824-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB46B.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b46f
Analysis symbol:
Rechecking for solution: 0
Report Id: 021210-21824-01
Report Status: 0
Event[48]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Minidump\011810-17082-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB49B.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b49e
Analysis symbol:
Rechecking for solution: 0
Report Id: 011810-17082-01
Report Status: 0
Event[49]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Minidump\011210-17706-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB4CA.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b4bd
Analysis symbol:
Rechecking for solution: 0
Report Id: 011210-17706-01
Report Status: 0
Event[50]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\Minidump\010410-18298-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-34055-0.sysdata.xml
C:\Users\Alex\AppData\Local\Temp\WERB4EB.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0b44b4dd
Analysis symbol:
Rechecking for solution: 0
Report Id: 010410-18298-01
Report Status: 0
Event[51]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100909-1627.dmp
C:\Windows\Temp\WER-538156-0.sysdata.xml
C:\Windows\Temp\WER5031.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0db85031
Analysis symbol:
Rechecking for solution: 0
Report Id: d8e44a00-bc69-11df-900c-d5ccb3e2ce0c
Report Status: 0
Event[52]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100910-2025.dmp
C:\Windows\Temp\WER-46593411-0.sysdata.xml
C:\Windows\Temp\WERF91B.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0dbef91b
Analysis symbol:
Rechecking for solution: 0
Report Id: 4c2c2bf0-bd54-11df-b213-9c7a70ad1806
Report Status: 0
Event[53]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100904-1015.dmp
C:\Windows\Temp\WER-1064145-0.sysdata.xml
C:\Windows\Temp\WER5E07.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0ed85e16
Analysis symbol:
Rechecking for solution: 0
Report Id: 012890a0-b848-11df-aa7c-d95696c7ac0a
Report Status: 0
Event[54]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100926-2148.dmp
C:\Windows\Temp\WER-40530151-0.sysdata.xml
C:\Windows\Temp\WER8B69.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_10fa8b79
Analysis symbol:
Rechecking for solution: 0
Report Id: 752c0520-c9f2-11df-9e84-a2ca5b42110f
Report Status: 0
Event[55]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20101219-1931.dmp
C:\Windows\Temp\WER-33741175-0.sysdata.xml
C:\Windows\Temp\WERFB97.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_1186fbb6
Analysis symbol:
Rechecking for solution: 0
Report Id: a33b60d0-0be9-11e0-9dbc-8397591cef01
Report Status: 0
Event[56]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100815-1713.dmp
C:\Windows\Temp\WER-7352077-0.sysdata.xml
C:\Windows\Temp\WER51B9.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_133051c9
Analysis symbol:
Rechecking for solution: 0
Report Id: 1ed8eaa0-a8cb-11df-8c77-90e6ba4980ad
Report Status: 0
Event[57]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100818-1847.dmp
C:\Windows\Temp\WER-31283114-0.sysdata.xml
C:\Windows\Temp\WER79DA.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_138179e9
Analysis symbol:
Rechecking for solution: 0
Report Id: ca510f60-ab33-11df-b544-90e6ba4980ad
Report Status: 0
Event[58]:
Log Name: Application
Source: Windows Error Reporting
Date: 2011-09-27T09:51:33.000
Event ID: 1001
Task: N/A
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0
Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20100826-2220.dmp
C:\Windows\Temp\WER-46416412-0.sysdata.xml
C:\Windows\Temp\WER4E8B.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_169c4eaa
Analysis symbol:
Rechecking for solution: 0
Report Id: e11194f0-b19a-11df-9bf7-b50d7985b702
Report Status: 0
Event[59]:
Log Name: Application
Source: gupdate
Date: 2011-09-27T10:14:00.000
Event ID: 0
Task: None
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
N/A
Event[60]:
Log Name: Application
Source: gupdate
Date: 2011-09-27T10:14:00.000
Event ID: 0
Task: None
Level: Information
Opcode: Info
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
N/A
Event[61]:
Log Name: Application
Source: SideBySide
Date: 2011-09-27T10:16:34.000
Event ID: 59
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: Alex-PC
Description:
Activation context generation failed for "c:\program files (x86)\microsoft\search enhancement pack\search helper\searchhelper.dll".Error in manifest or policy file "c:\program files (x86)\microsoft\search enhancement pack\search helper\searchhelper.dll" on line 2. Invalid Xml syntax.
Go to your HP site and check for an updates for your drivers.
Install all with a more recent date than yours are now.
Run memtest86+ for a minimum on 7 full passes with all RAM cards installed, best to run overnight.
Stop the test if you get any errors.
RAM - Test with Memtest86+
What Nvidia driver are you using?
You need to check for an update, if you are using the latest then try a previous driver.
D/L and run Western Digital Lifeguard – Quick Test and Extended Test
Un-install itunes for testing purposes.
Check if there is a BIOS update.
Yours:
BIOS Date: 09/08/09 15:16:20 Ver: 5.18