robix761
21-01-2009, 14:07
Buongiorno a tutti.
Sto impazzendo con le schermate blu sul mio pc.
(Breve storia: 2 anni fa un fulmine me lo rende inutilizzabile. Ufficialmente Mb bruciata.
1 - Cambio Ali,Mb,Processore,HD, modem adsl. Sporadicamente ho bluescreen che non avevo prima. Sarà la Ram, sembra esserlo perchè memtest mi rileva errori su un banco. 2 - Cambio la Ram. Inizialmente sembra tutto ok. Per un po' di tempo sono fuori Italia, torno una volta ogni tanto e in quelle volte si rimanifesta il problema. Sono tornato in Italia, ci resterò qualche mese. Devo usare il pc, ma in vista di una nuova partenza entro pochi mesi, non ne voglio comprare un altro, e questo non è da buttare.
3 - Allora mi regalo una scheda video, l'unico pezzo che non avevo ancora cambiato, anche per sostituire l'altra ormai vecchiotta. Cosa succede? blue screen of death. Almeno uno al giorno, ma impediscono di lavorare seriamente e serenamente.
Conseguenza: non ce la faccio più. O sistemo il problema, o cambio qualche pezzo (mb? ram? proce? insomma mi costerebbe meno un pc nuovo..)
Non riesco a capire se sia un problema hardware o software.
Ho cambiato tutti i pezzi tranne il case, ho sempre il s.o., i drivers, gli antivirus e anti-tutto aggiornati. Mai spegnimenti brutali.Insomma, un pc tenuto bene, e non ritengo di essere un newbie. Il sistema è pulito.
Mi son procurato un paio di programmi per analizzare le schermate blu, o meglio, i crash report.
Onestamente, non mi aiutano granchè.
Incollo l'ultimo. Ringrazio anticipatamente chiunque mi possa dare una mano.
Mb Asus P5vdc-x
Pentium 4 3,0ghz mod. 630
1024 mb ram ddr2
2 hd sAta
1 dvd-rw , 1 cd-rw
Sapphire Ati RAdeon HD4350
Xp Home originale con Sp3
Welcome to WhoCrashed v1.00
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled for your computer.
On Tue 20/01/2009 20.08.44 your computer crashed
This was likely caused by the following module: rdbss.sys
Bugcheck code: 0x1000008E (0x80000003, 0x804E2A46, 0xAB3589CC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Tue 20/01/2009 11.04.15 your computer crashed
This was likely caused by the following module: saskutil.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8057C031, 0xAC118858, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: c:\programmi\superantispyware\saskutil.sys
product: SUPERAntiSpyware
company: SUPERAdBlocker.com and SUPERAntiSpyware.com
description: SASKUTIL.SYS
On Mon 19/01/2009 21.40.04 your computer crashed
This was likely caused by the following module: ati2cqag.dll
Bugcheck code: 0x100000EA (0x85B5BB38, 0x8655EEE0, 0xF7C6ECBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
On Mon 19/01/2009 19.44.40 your computer crashed
This was likely caused by the following module: afd.sys
Bugcheck code: 0x1000008E (0x80000003, 0x804E2A46, 0xAA3FA9CC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Mon 19/01/2009 17.30.11 your computer crashed
This was likely caused by the following module: ati2cqag.dll
Bugcheck code: 0xEA (0x85B4B020, 0x866831E8, 0x85C1C478, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
On Sun 18/01/2009 21.17.10 your computer crashed
This was likely caused by the following module: ati2cqag.dll
Bugcheck code: 0xEA (0x85B7DC38, 0x85A95138, 0x864F42F0, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
On Sun 18/01/2009 17.38.00 your computer crashed
This was likely caused by the following module: ati2dvag.dll
Bugcheck code: 0x1000008E (0xC0000005, 0x100000, 0xABD0B4B0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ati2dvag.dll
product: ATI Radeon WindowsNT Display Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Display Driver
On Sun 18/01/2009 9.24.16 your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x100000EA (0x85B7DC38, 0x85A95138, 0xF7C6ECBC, 0x2)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver
On Fri 09/01/2009 18.32.37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8063081B, 0xAADECC34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Wed 07/01/2009 18.06.17 your computer crashed
This was likely caused by the following module: afd.sys
Bugcheck code: 0x1000008E (0x80000003, 0x804E2A46, 0xAB19E9D0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Fri 02/01/2009 19.43.44 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE28FB000, 0x1, 0x8058AB4D, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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 the 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.
Sto impazzendo con le schermate blu sul mio pc.
(Breve storia: 2 anni fa un fulmine me lo rende inutilizzabile. Ufficialmente Mb bruciata.
1 - Cambio Ali,Mb,Processore,HD, modem adsl. Sporadicamente ho bluescreen che non avevo prima. Sarà la Ram, sembra esserlo perchè memtest mi rileva errori su un banco. 2 - Cambio la Ram. Inizialmente sembra tutto ok. Per un po' di tempo sono fuori Italia, torno una volta ogni tanto e in quelle volte si rimanifesta il problema. Sono tornato in Italia, ci resterò qualche mese. Devo usare il pc, ma in vista di una nuova partenza entro pochi mesi, non ne voglio comprare un altro, e questo non è da buttare.
3 - Allora mi regalo una scheda video, l'unico pezzo che non avevo ancora cambiato, anche per sostituire l'altra ormai vecchiotta. Cosa succede? blue screen of death. Almeno uno al giorno, ma impediscono di lavorare seriamente e serenamente.
Conseguenza: non ce la faccio più. O sistemo il problema, o cambio qualche pezzo (mb? ram? proce? insomma mi costerebbe meno un pc nuovo..)
Non riesco a capire se sia un problema hardware o software.
Ho cambiato tutti i pezzi tranne il case, ho sempre il s.o., i drivers, gli antivirus e anti-tutto aggiornati. Mai spegnimenti brutali.Insomma, un pc tenuto bene, e non ritengo di essere un newbie. Il sistema è pulito.
Mi son procurato un paio di programmi per analizzare le schermate blu, o meglio, i crash report.
Onestamente, non mi aiutano granchè.
Incollo l'ultimo. Ringrazio anticipatamente chiunque mi possa dare una mano.
Mb Asus P5vdc-x
Pentium 4 3,0ghz mod. 630
1024 mb ram ddr2
2 hd sAta
1 dvd-rw , 1 cd-rw
Sapphire Ati RAdeon HD4350
Xp Home originale con Sp3
Welcome to WhoCrashed v1.00
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled for your computer.
On Tue 20/01/2009 20.08.44 your computer crashed
This was likely caused by the following module: rdbss.sys
Bugcheck code: 0x1000008E (0x80000003, 0x804E2A46, 0xAB3589CC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\rdbss.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Redirected Drive Buffering SubSystem Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Tue 20/01/2009 11.04.15 your computer crashed
This was likely caused by the following module: saskutil.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8057C031, 0xAC118858, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: c:\programmi\superantispyware\saskutil.sys
product: SUPERAntiSpyware
company: SUPERAdBlocker.com and SUPERAntiSpyware.com
description: SASKUTIL.SYS
On Mon 19/01/2009 21.40.04 your computer crashed
This was likely caused by the following module: ati2cqag.dll
Bugcheck code: 0x100000EA (0x85B5BB38, 0x8655EEE0, 0xF7C6ECBC, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
On Mon 19/01/2009 19.44.40 your computer crashed
This was likely caused by the following module: afd.sys
Bugcheck code: 0x1000008E (0x80000003, 0x804E2A46, 0xAA3FA9CC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Mon 19/01/2009 17.30.11 your computer crashed
This was likely caused by the following module: ati2cqag.dll
Bugcheck code: 0xEA (0x85B4B020, 0x866831E8, 0x85C1C478, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
On Sun 18/01/2009 21.17.10 your computer crashed
This was likely caused by the following module: ati2cqag.dll
Bugcheck code: 0xEA (0x85B7DC38, 0x85A95138, 0x864F42F0, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
On Sun 18/01/2009 17.38.00 your computer crashed
This was likely caused by the following module: ati2dvag.dll
Bugcheck code: 0x1000008E (0xC0000005, 0x100000, 0xABD0B4B0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ati2dvag.dll
product: ATI Radeon WindowsNT Display Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Display Driver
On Sun 18/01/2009 9.24.16 your computer crashed
This was likely caused by the following module: ati2mtag.sys
Bugcheck code: 0x100000EA (0x85B7DC38, 0x85A95138, 0xF7C6ECBC, 0x2)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\ati2mtag.sys
product: ATI Radeon WindowsNT Miniport Driver
company: ATI Technologies Inc.
description: ATI Radeon WindowsNT Miniport Driver
On Fri 09/01/2009 18.32.37 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8063081B, 0xAADECC34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Wed 07/01/2009 18.06.17 your computer crashed
This was likely caused by the following module: afd.sys
Bugcheck code: 0x1000008E (0x80000003, 0x804E2A46, 0xAB19E9D0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
On Fri 02/01/2009 19.43.44 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE28FB000, 0x1, 0x8058AB4D, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver in your system which cannot be identified.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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 the 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.