PROBLEMA Bluescreen Windows 7 x64

Pubblicità
H

holahola

Nuovo Utente
Messaggi
13
Reazioni
0
Punteggio
25
Salve ragazzi è un po' di tempo che ho un problema di blue screen. Dato che so che questo genere di problema è vago dipendente sia da driver che da pezzi hardware come scheda video,ram,harddisk vi spiego cosa ho fatto.

Ho sostituito ram, harddisk, scheda video, ma nonostante ciò continua a darmi problemi. Il mio dubbio è sulla scheda video perchè praticamente quando ora provo ad installare ati catalyst(ho aquistato una ati radeon hd 7750) questi crasha e nel bluee screen escono questi errori:

080813-40014-01.dmp 08/08/2013 19:54:23 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007e ffffffff`c0000005 fffff880`00e39c4c fffff880`031c47a8 fffff880`031c4000 tcpip.sys tcpip.sys+17d600 Driver TCP/IP Sistema operativo Microsoft® Windows® Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) x64 Wdf01000.sys+7c4c C:\Windows\Minidump\080813-40014-01.dmp 4 15 7601 275.536 08/08/2013 23:08:56


cosa posso fare? Grazie.

P.s.: Aggiungo che avevo capito che forse era la scheda video vecchia(la ati radeon hd 5750) che dava problemi quindi la tolsi dallo slot pci edisinstallai i driver e attaccando la vga alla mia scheda madre con scheda video integrata non andò in blue screen, avendo capito quindi che era la scheda ne ho ordianta una nuova (la 7750) ma quest'ultima continua a dare problemi.
 
Ultima modifica:
ciao scarica whocrashed e posta la lettura del file dmp così da capirne la causa.
 
Ecco:
[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 Fri 09/08/2013 18:39:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080913-19203-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x17CA67)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002FDEA67, 0xFFFFF88003316628, 0xFFFFF88003315E80)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/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 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.
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 09/08/2013 18:39:37 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntkrnlmp.exe[/FONT] (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80002FDEA67, 0xFFFFF88003316628, 0xFFFFF88003315E80)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/FONT]
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 08/08/2013 21:43:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-26598-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x3EA576)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003208576, 0xFFFFF880031B6468, 0xFFFFF880031B5CC0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/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 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.
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 08/08/2013 17:54:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-40014-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]wdf01000.sys[/FONT] (Wdf01000+0x7C4C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88000E39C4C, 0xFFFFF880031C47A8, 0xFFFFF880031C4000)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]
file path: C:\Windows\system32\drivers\wdf01000.sys
product: [FONT=Segoe UI, Arial]Sistema operativo Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Runtime framework driver modalità kernel
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.
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 08/08/2013 17:44:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-38423-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x1A (0x41287, 0x38, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Thu 08/08/2013 17:34:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-26192-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F9AA67, 0xFFFFF88003EFAFA0, 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]On Thu 08/08/2013 17:26:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-30139-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xC5 (0x8, 0x2, 0x1, 0xFFFFF80003009147)
Error: [FONT=Segoe UI, Arial]DRIVER_CORRUPTED_EXPOOL[/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 the system attempted to access invalid 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. 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Wed 07/08/2013 20:02:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080813-19780-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFD8, 0x2, 0x0, 0xFFFFF80002C8627B)
Error: [FONT=Segoe UI, Arial]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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 05/08/2013 19:28:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080613-16692-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]MEMORY_MANAGEMENT[/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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 05/08/2013 17:36:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-18142-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002DCDA67, 0xFFFFF8800815CA40, 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]On Mon 05/08/2013 17:25:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080513-18688-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xA (0x40, 0x2, 0x0, 0xFFFFF80002C8646B)
Error: [FONT=Segoe UI, Arial]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 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 that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 04/08/2013 13:03:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080413-16629-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D58EC8, 0xFFFFF88006EB5BE0, 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]On Sun 04/08/2013 12:25:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080413-14445-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]atikmdag.sys[/FONT] (atikmdag+0x9C28D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800489C28D, 0xFFFFF88002EFC048, 0xFFFFF88002EFB8A0)
Error: [FONT=Segoe UI, Arial]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/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 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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: [FONT=Segoe UI, Arial]Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sun 04/08/2013 11:48:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080413-14695-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0xA (0x10, 0x2, 0x0, 0xFFFFF80002A5EC05)
Error: [FONT=Segoe UI, Arial]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 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 that cannot be identified at this time.
[/FONT]
 
ciao sembra la ram ad aver problemi scarica memtest dalla mia firma mettilo su pen e fai girare per qualche ora
 
La ram l ho sostituita, come può essere ancora lei?
P.s. ho creatonla pen drive boot. Solo che quando la starto da boot mi dice missing operative system. Perché?
 
Ultima modifica:
ho provato a fare come dici tu ma niente. Da cosa dipende?

Ti Spiego come ho fatto:

Ho scaricato memtest for USB.exe, ho formattato la pennetta lentamente, successivamente ho aperto l'exe di memtest ho dato la spunta della formattazione( l'ho fato anche senza la spunta) una volta creato da bios ho selezionato la usb e all'avvio mi esce missing operativing system.
 
Ultima modifica:
Ho fatto un cd boot. Comunque ha fatto un pass intero senza errori, scrivo dal cell mentre lo sto favendo continuare con il secondo.

Cos altro devo fare?
 
Ho sostituito Ram, Harddisk, Scheda video. Per quanto riguarda la scheda video ho scaricato l'ultima versione stabile dei driver e dell'ati catalyst dal sito amd. Che driver può essere corrotto?

Sto seriamente pensando che sia proprio la scheda madre a dare problemi.
 
Ultima modifica:
Pubblicità
Pubblicità
Indietro
Top