- 65
- 3
- CPU
- i5 750
- Scheda Madre
- Asus P7P55D PRO
- HDD
- 1.5T
- RAM
- DDR3 2x2giga
- GPU
- Club 3d ati 6950 2gb
- Audio
- integrata via
- Monitor
- samsung syncmaster 22" 2 ms 1920x1080
- PSU
- Corsair 750W
- Case
- thermaltake
- OS
- win7 ultimate x64
salve a tutti
ho un pc (preso usato) che soffre principalmente di due problemi
1-hang del suono intermittente ad intervalli casuali (un rumore tipo *bzrrrrrrt* che dura da pochi ms ad un secondo) molto fastidioso. Al volume di quello che sto ascoltando e non blocca il suono principale, semplicemente si sovrappone
2 - poi bsod in media uno ogni 2 giorni (il rumore invece di smettere diventa persistente e dura fino al riavvio del pc) normalmente succede quando faccio tante cose contemporaneamente (chrome e firefox con molte finestre aperte, player audio video, giochi e download tutto in contemporanea (l'ho sempre fatto con i pc precedenti e mai un problema) con i giochi mi è capitato solo un crash con bf3, mentre capita sempre quando uso pesantemente internet e flussi audio video.
Programmi che uso solitamente: avira antivirus, chrome e firefox con adblock plus, vlc, windows media player, cdisplay, jdownloader,bittorrent, razer profile tray,gtalk, visual studio 2010, battlefield 3, dead space 2, starcraft 2
avevo provato di tutto memtest e tanta altra roba, tutti i test conclusi con esito positivo (ogni tanto partiva la schermata blu se facevo il test da windows ma era casuale perchè poi ripetevo il test e andava tutto bene). Driver straggiornati ma non ha cambiato nulla, ho pure formattato una volta.
Dopo la formattazione non ho avuto il problema dell'audio per un po, ma dopo 3 o 4 bsod ha ricominciato a fare sti suoni.
Ho anche provato ad aggiornare i drivers trovando chipset, ahci e esata da aggiornare... ho trovato le versioni più recenti su driver station ma non è migliorato nulla. Ho anche provato gli ultimi driver beta della nvidia pensando che gli utlimi officiali fossero il problema, ma niente....
windows è originale e aggiornato al 100%, tutte le periferiche sono riconosciute, installate ed aggiornate
ogni bsod è diversa (principalmente esplode ntoskrnl.exe) e whocrashed mi identificava la causa sempre per un problema diverso ma sempre legato al software/driver. Solo in uno era crashato il driver della nvidia ma poi non si è più ripresentato. Non mi ha mai segnato come causa un problema hardware.
Quelli che mi sono capitati sono questi
[FONT=&]BSOD ERROR: STOP: 0×0000000A | Error - IRQL_NOT_LESS_OR_EQUAL
[/FONT][FONT=&]BSOD Error: STOP: 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA
[/FONT][FONT=&]BSOD Error - STOP: 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED
[/FONT][FONT=&]BSOD STOP Error: 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL
[/FONT][FONT=&]BSOD Error - STOP: 0x00000024 | Stop 0x24 or NTFS_FILE_SYSTEM
[/FONT]
ecco alcuni esempi
stasera mi sono messo a trafficare su gpuz perchè mi era venuto il tarlo che la ram non fosse compatibili con la scheda madre (asus p7p55d pro).
E guardate che sigle è saltato fuori
slot 1
DIMM # 1
SMBus address 0x50
Memory type DDR3
Module format UDIMM
Manufacturer (ID) Corsair (7F7F9E0000000000)
Size 2048 MBytes
Max bandwidth PC3-10700H (667 MHz)
Part number CMX6GX3M3A1600C9
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.2
DIMM # 2
SMBus address 0x52
Memory type DDR3
Module format UDIMM
Manufacturer (ID) Corsair (7F7F9E0000000000)
Size 2048 MBytes
Max bandwidth PC3-10700H (667 MHz)
Part number CMX4GX3M2A1600C9
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.2
una delle due ha la sigla del kit triple channel mentra l'altra quella del kit dual channel
mi chiedo è questo il problema? la CMX6GX3M3A1600C9 non ha nella lista la compatibilità la mia mobo, ma ho letto in giro che una memoria triple channel dovrebbe adattarsi senza prolemi ad una dual, infatti le frequenze ed i timings coincidono
sono altre cose? inoltre di cui non mi capacito di quei strani suoni...
un mio amico mi ha suggerito che potrebbe trattarsi di qualche problema di messa a terra pc, anche se ho revisionato l'impianto elettrico a settembre e le prese sono del tipo tripolare anche se sono quelle del tipo a 10A. Inoltre non mi è mai capitato di prendere la scossa, che è di solito l'indice che ci sono problemi di questo tipo.
in allegato il report di cpuz
Visualizza allegato ALPE-PCNUOVO.zip
altro hardware non presente: ali hx750w, tastiera multifunzione trust, mouse razer lachesis, schermo samsung syncmaster che non mi ricordo, full hd con collegamento dvi
insomma aiuto non so più che fare o cosa provare. l'unica cosa che mi manca è swappare i componenti hardware, ma non ne ho di ricambio, non riesco proprio a capire quale componente o driver sta dando problemi
mi viene voglia di buttare tutto :cav::mad:
ho un pc (preso usato) che soffre principalmente di due problemi
1-hang del suono intermittente ad intervalli casuali (un rumore tipo *bzrrrrrrt* che dura da pochi ms ad un secondo) molto fastidioso. Al volume di quello che sto ascoltando e non blocca il suono principale, semplicemente si sovrappone
2 - poi bsod in media uno ogni 2 giorni (il rumore invece di smettere diventa persistente e dura fino al riavvio del pc) normalmente succede quando faccio tante cose contemporaneamente (chrome e firefox con molte finestre aperte, player audio video, giochi e download tutto in contemporanea (l'ho sempre fatto con i pc precedenti e mai un problema) con i giochi mi è capitato solo un crash con bf3, mentre capita sempre quando uso pesantemente internet e flussi audio video.
Programmi che uso solitamente: avira antivirus, chrome e firefox con adblock plus, vlc, windows media player, cdisplay, jdownloader,bittorrent, razer profile tray,gtalk, visual studio 2010, battlefield 3, dead space 2, starcraft 2
avevo provato di tutto memtest e tanta altra roba, tutti i test conclusi con esito positivo (ogni tanto partiva la schermata blu se facevo il test da windows ma era casuale perchè poi ripetevo il test e andava tutto bene). Driver straggiornati ma non ha cambiato nulla, ho pure formattato una volta.
Dopo la formattazione non ho avuto il problema dell'audio per un po, ma dopo 3 o 4 bsod ha ricominciato a fare sti suoni.
Ho anche provato ad aggiornare i drivers trovando chipset, ahci e esata da aggiornare... ho trovato le versioni più recenti su driver station ma non è migliorato nulla. Ho anche provato gli ultimi driver beta della nvidia pensando che gli utlimi officiali fossero il problema, ma niente....
windows è originale e aggiornato al 100%, tutte le periferiche sono riconosciute, installate ed aggiornate
ogni bsod è diversa (principalmente esplode ntoskrnl.exe) e whocrashed mi identificava la causa sempre per un problema diverso ma sempre legato al software/driver. Solo in uno era crashato il driver della nvidia ma poi non si è più ripresentato. Non mi ha mai segnato come causa un problema hardware.
Quelli che mi sono capitati sono questi
[FONT=&]BSOD ERROR: STOP: 0×0000000A | Error - IRQL_NOT_LESS_OR_EQUAL
[/FONT][FONT=&]BSOD Error: STOP: 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA
[/FONT][FONT=&]BSOD Error - STOP: 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED
[/FONT][FONT=&]BSOD STOP Error: 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL
[/FONT][FONT=&]BSOD Error - STOP: 0x00000024 | Stop 0x24 or NTFS_FILE_SYSTEM
[/FONT]
ecco alcuni esempi
On Tue 24/01/2012 21:39:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012412-42915-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1D6D20)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF960001F6D20, 0xFFFFF8800ABC1520, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.
On Tue 24/01/2012 21:39:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngLpkInstalled+0x4BC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF960001F6D20, 0xFFFFF8800ABC1520, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.
On Sat 21/01/2012 00:11:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-45349-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 05/01/2012 14:27:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010512-45396-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xD29D28D7, 0x6, 0x0, 0xFFFFF8800F7B6E1F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 22/12/2011 22:45:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122211-47845-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF80002EFBF00)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 22/12/2011 22:45:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF80002EFBF00)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 18/12/2011 15:47:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121811-42541-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8007531C50, 0xFFFFF8800C713000, 0xFFFFF8A00BADAAA1)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 17/12/2011 00:26:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121711-43337-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF80002814000, 0x0, 0xFFFFF80002FBB6DA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
crash dump file: C:\Windows\Minidump\012412-42915-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1D6D20)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF960001F6D20, 0xFFFFF8800ABC1520, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.
On Tue 24/01/2012 21:39:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngLpkInstalled+0x4BC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF960001F6D20, 0xFFFFF8800ABC1520, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver Win32 multiutente
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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.
On Sat 21/01/2012 00:11:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-45349-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 05/01/2012 14:27:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010512-45396-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0xD29D28D7, 0x6, 0x0, 0xFFFFF8800F7B6E1F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 22/12/2011 22:45:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122211-47845-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF80002EFBF00)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 22/12/2011 22:45:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFFA7FFFFFFFE0, 0x2, 0x1, 0xFFFFF80002EFBF00)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 18/12/2011 15:47:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121811-42541-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8007531C50, 0xFFFFF8800C713000, 0xFFFFF8A00BADAAA1)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 17/12/2011 00:26:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121711-43337-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF80002814000, 0x0, 0xFFFFF80002FBB6DA, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
stasera mi sono messo a trafficare su gpuz perchè mi era venuto il tarlo che la ram non fosse compatibili con la scheda madre (asus p7p55d pro).
E guardate che sigle è saltato fuori
slot 1
DIMM # 1
SMBus address 0x50
Memory type DDR3
Module format UDIMM
Manufacturer (ID) Corsair (7F7F9E0000000000)
Size 2048 MBytes
Max bandwidth PC3-10700H (667 MHz)
Part number CMX6GX3M3A1600C9
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.2
DIMM # 2
SMBus address 0x52
Memory type DDR3
Module format UDIMM
Manufacturer (ID) Corsair (7F7F9E0000000000)
Size 2048 MBytes
Max bandwidth PC3-10700H (667 MHz)
Part number CMX4GX3M2A1600C9
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.2
una delle due ha la sigla del kit triple channel mentra l'altra quella del kit dual channel
mi chiedo è questo il problema? la CMX6GX3M3A1600C9 non ha nella lista la compatibilità la mia mobo, ma ho letto in giro che una memoria triple channel dovrebbe adattarsi senza prolemi ad una dual, infatti le frequenze ed i timings coincidono
sono altre cose? inoltre di cui non mi capacito di quei strani suoni...
un mio amico mi ha suggerito che potrebbe trattarsi di qualche problema di messa a terra pc, anche se ho revisionato l'impianto elettrico a settembre e le prese sono del tipo tripolare anche se sono quelle del tipo a 10A. Inoltre non mi è mai capitato di prendere la scossa, che è di solito l'indice che ci sono problemi di questo tipo.
in allegato il report di cpuz
Visualizza allegato ALPE-PCNUOVO.zip
altro hardware non presente: ali hx750w, tastiera multifunzione trust, mouse razer lachesis, schermo samsung syncmaster che non mi ricordo, full hd con collegamento dvi
insomma aiuto non so più che fare o cosa provare. l'unica cosa che mi manca è swappare i componenti hardware, ma non ne ho di ricambio, non riesco proprio a capire quale componente o driver sta dando problemi
mi viene voglia di buttare tutto :cav::mad:
Ultima modifica:
