Olimpo Informatico

[Amira]

Salve,
Malwarebytes Anti-Malware mi dà queste infezioni:
mbam-log-2012-11-19 (16-54-33).txt
mbam-log-2012-11-19 (21-28-46).txt 1.txt
Ho provato a rimuoverli. Intanto ho notato che mi nega l'accesso ad alcuni elementi di C (impossibile accedere a C:\Users....accesso negato)

[menatwork]

ciao Amira fai una scansione con combofix come indicato in questa guida e allega il log che rilascia secondo il regolamento

[Amira]

Ciao!
ecco a te!
combofix.txt

[Amira]

intanto mi accadono frequenti episodi di pagine blu...
chi mi aiuta?

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 20/11/2012 14.10.20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini112012-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1128C3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF955138C3, 0xFFFFFFFF93946704, 0xFFFFFFFF93946400)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 179.30
company: NVIDIA Corporation
description: NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 179.30
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.
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: nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 179.30 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Tue 20/11/2012 14.10.20 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF955138C3, 0xFFFFFFFF93946704, 0xFFFFFFFF93946400)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED




On Mon 19/11/2012 19.40.51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini111912-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x7C046)
Bugcheck code: 0x116 (0xFFFFFFFF8D939510, 0xFFFFFFFF9520D650, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Compatible Windows Vista Kernel Mode Driver, Version 179.30 , NVIDIA Corporation)

ntkrpamp.exe

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.