PROBLEMA blue screen

Pubblicità
I

Isabella Venusia Carli

Nuovo Utente
Messaggi
5
Reazioni
0
Punteggio
24
Salve ragazzi sono nuovissima del forum, ho pochissimo tempo perchè ho un bel pargolo di 18 mesi che non mi permette come un tempo di aggiornarmi e risovere da sola alcuni problemi del mio pc, chè è sttao formattato una settimana fa, ma...subito BLUE SCREEN; codice errore

BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF96000078047
BCP3: FFFFF8800697FF10
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Non ho certo soldi per un tecnico di nuovo, e mi sono pesantemete arrugginita
Sistema

Intel core Duo CPU E8400 @3.00 GHz 2.99 Ghz

Windows Seven 64 bit...

i crash avvengono sia se elaboro foto he se guardo film
Mi potete aiutare?
 
lunedì appena ho un attimo di tregua, grazie!!!

- - - Updated - - -

Federico83 ha detto:
scarica whocrashed dalla mia firma e copia e incolla qui la lettura dei dmp
Clicca per espandere...
[FONT=Segoe UI, Arial]Crash Dump Analysis
[/FONT]
[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sat 27/07/2013 11:15:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-25812-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xD1 (0x326B003F, 0x2, 0x0, 0xFFFFF880019E0FAE)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 27/07/2013 11:15:58 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]tcpip.sys[/FONT] (tcpip+0x49779)
Bugcheck code: 0xD1 (0x326B003F, 0x2, 0x0, 0xFFFFF880019E0FAE)
Error: [FONT=Segoe UI, Arial]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\tcpip.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Driver TCP/IP
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sat 27/07/2013 00:42:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072713-24015-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x4A (0x77CA13BA, 0x2, 0x0, 0xFFFFF8800A373CA0)
Error: [FONT=Segoe UI, Arial]IRQL_GT_ZERO_AT_SYSTEM_SERVICE[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 25/07/2013 23:12:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072613-25625-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k+0x78047)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000078047, 0xFFFFF8800697FF10, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 25/07/2013 22:03:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072613-25125-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]atikmdag.sys[/FONT] (atikmdag+0x827C7)
Bugcheck code: 0xA (0x1CE4, 0x2, 0x1, 0xFFFFF80002C980C9)
Error: [FONT=Segoe UI, Arial]IRQL_NOT_LESS_OR_EQUAL[/FONT]
file path: C:\Windows\system32\drivers\atikmdag.sys
product: [FONT=Segoe UI, Arial]ATI Radeon Family[/FONT]
company: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc.[/FONT]
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Thu 25/07/2013 10:58:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072513-39031-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 24/07/2013 10:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072413-33203-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFFA8004932C10, 0x1, 0x0)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Fri 19/07/2013 12:25:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071913-21546-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002A9C146, 0xFFFFF88006B0D1B0, 0x0)
Error: [FONT=Segoe UI, Arial]SYSTEM_SERVICE_EXCEPTION[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]
Conclusion
[/FONT]
[FONT=Segoe UI, Arial]8 crash dumps have been found and analyzed. A third party driver has 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:

[FONT=Segoe UI, Arial]atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)[/FONT]

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.


fatto, di giorno non ho mai tempo!!![/FONT]
 
ciao metà dei bsod fanno pensare alla ram l'altra metà fanno pensare ai driver ati... testa la ram con memtest puoi prenderlo dalla mia firma metterlo su cd o su chiavetta. Puoi anche provare a rimuovere i driver della vga con driver sveeper e metterne di aggiornati o una versione precedente così da testare se va ancora in bsod
 
Federico83 ha detto:
ciao metà dei bsod fanno pensare alla ram l'altra metà fanno pensare ai driver ati... testa la ram con memtest puoi prenderlo dalla mia firma metterlo su cd o su chiavetta. Puoi anche provare a rimuovere i driver della vga con driver sveeper e metterne di aggiornati o una versione precedente così da testare se va ancora in bsod
Clicca per espandere...

la ram è stata testata dal tecnico lunedì scorso, comunque rifaccio, coi driver, si posso avere fatto confusione io, provo!!!GRAZIE!!!
 
Ultima modifica:
Federico83 ha detto:
ciao metà dei bsod fanno pensare alla ram l'altra metà fanno pensare ai driver ati... testa la ram con memtest puoi prenderlo dalla mia firma metterlo su cd o su chiavetta. Puoi anche provare a rimuovere i driver della vga con driver sveeper e metterne di aggiornati o una versione precedente così da testare se va ancora in bsod
Clicca per espandere...

Ciao, ho fatto il test alla ram ed effettivamente da una marea di problemai, i driver sono quelli giusti...
Mi fa strano visto che il pc è appena stato formattato e controllato dal tecnico...
Lui sostiene che sia il monitor ad essere rotto, ma attaccato ad altro pc va....
ho notato che crasha solo se faccio partire video, sia youtube che streaming...
Tutto ieri nessun problema, oggi al terzo video crash.Dd ora va...
 
se ti da tutte righe rosse durante il memtest direi di cambiare la ram o di controllare se sono alloggiate correttamente
 
Pubblicità
Pubblicità
Indietro
Top