Problema con windows 7 64 bit quando avvio lo scandisk dopo crash

Pubblicità

ippio1985

Nuovo Utente
Messaggi
54
Reazioni
0
Punteggio
26
Salve da due giorni mi succede un fatto strano ho avuto un creash mentre giocavo e il pc si è raiavviato da solo al riavvio ho fatto fare lo scandisk ma al suo avvio mi è comparsa questa schermata blu http://i50.tinypic.com/ndkiol.jpg che si riavvia all infinito poi cosa ancor più strana è che collegando il joypad o una chiavetta usb lo scandisk parte senza problemi. Vi posto gli errori con Blue Screen View http://i39.tinypic.com/34hxsus.png e con WhocCrashed http://i43.tinypic.com/i3cpz5.png .
Per il crash sembra essere dovuto all'ultimo driver nvidia il beta infatti rimettendo l'ultimo whql va tutto ok.
Grazie in anticipo
 
Re: Problema con windows 7 65 bit quando avvio lo scandisk dopo crash

Io ho il tuo stesso problema, quando gioco a Modern Warfare 2 mi crasha, e appare il BSOD :sisi:
Ma scusami, se rimettendo l'ultimo driver Nvidia whql va tutto ok, di cosa si discute? xD
E un altra cosa, che driver usi, che versione?
 
Re: Problema con windows 7 65 bit quando avvio lo scandisk dopo crash

Io ho il tuo stesso problema, quando gioco a Modern Warfare 2 mi crasha, e appare il BSOD :sisi:
Ma scusami, se rimettendo l'ultimo driver Nvidia whql va tutto ok, di cosa si discute? xD
E un altra cosa, che driver usi, che versione?
Si hai ragione forse m i sono spiegato male va tutto ok riguardo i giochi che non mi crasha più il driver è 320.49 whql ma la schermata blu rimane imperterrita li quando avvio lo scandisk.

- - - Updated - - -

@ippio1985 posta la lettura con whocrashed prendilo dalla mia firma
Scusa non ho capito :)
 
Ultima modifica:
dalla mia firma clicca e scarica whocrashed e posta la lettura dei bsod così vediamo cosa origina questo bsod
 
dalla mia firma clicca e scarica whocrashed e posta la lettura dei bsod così vediamo cosa origina questo bsod

Ok ho scaricato dalla tua firma ma è ugale a quello che avevo se non mi sbaglio cmq la lettura dei bsod dove la trovo per caso è questa http://i43.tinypic.com/wj89s9.png o questa http://i43.tinypic.com/i3cpz5.png questo poi è quello che c'è scritto alla fine http://i43.tinypic.com/fz9mbt.png sonon tutti uguali tranne uno il penultimo partendo da sopra
 
Ultima modifica:
report seleziona tutto e incolla qui

ok ecco qui

[FONT=Segoe UI, Arial]This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought 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, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
[/FONT]
[FONT=Segoe UI, Arial]To obtain technical support visit www.resplendence.com/support

[/FONT][FONT=Segoe UI, Arial]Click here to check if you have the latest version or if an update is available.

[/FONT][FONT=Segoe UI, Arial]Just click the Analyze button for a comprehensible report ...


[/FONT][FONT=Segoe UI, Arial]
Home Edition Notice

[/FONT]
[FONT=Segoe UI, Arial]This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
[/FONT]
[FONT=Segoe UI, Arial]
System Information (local)

[/FONT]
[FONT=Segoe UI, Arial]computer name: ALESSANDRO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17092030464 total
VM: 2147352576, free: 1925390336


[/FONT]
[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 03/08/2013 16:07:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080313-24039-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 03/08/2013 16:07:27 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: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/FONT]
Bug check description: This bug check appears very infrequently.
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 03/08/2013 15:31:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080313-24336-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 03/08/2013 10:05:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080313-23540-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 02/08/2013 17:56:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-24195-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 02/08/2013 17:41:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-23696-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 02/08/2013 17:23:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-24258-02.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 02/08/2013 15:50:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-24258-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 02/08/2013 15:14:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080213-24195-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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 01/08/2013 19:09:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080113-15990-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x5A (0x1, 0x1, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]CRITICAL_SERVICE_FAILED[/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 bug check appears very infrequently.
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]10 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.



[/FONT]
 
quindi cosa dovrei fare non sono uno pratico e non ci capisco molto :)

Allora fatta la scansione con malwarebutes con microsoft security essentials e combofix pulito al mille pre mille poi disinstallato tutto ciò che riguardava nvidia e reinstallato il driver di fabbrica apposta per la mia scheda riprovo a fare lo scandisk e ok funziona poi installo gli aggiornamenti uno ad uno tranno gli ultimi tre perchè poi mi ero stufato e puff schermata ble all avvio dello scandisk allora ero quasi propenso al format ma prima ho voluto installare direttamente l'ultimo driver che mi ha installato geforce experience e miracolo sono gia due volte che provo a farglielo fare e parte senza problemi
 
Pubblicità
Pubblicità
Indietro
Top