bombcat
Utente Èlite
- Messaggi
- 2,502
- Reazioni
- 278
- Punteggio
- 118
whochased ?
hai il link gentilmente?
Da cellulare mi trova solo articoli di giornale inglesi o libri...
Pubblicità
CREARE DUAL BOOT AHCI con win7 installato, problemi / impiccio con partizioni per dual boot
- Autore discussione bombcat
- Data d'inizio
Pubblicità
whochased ?
hai il link gentilmente?
Da cellulare mi trova solo articoli di giornale inglesi o libri...
- Messaggi
- 35,404
- Reazioni
- 6,305
- Punteggio
- 246
ti ho messo il link... guarda il mio penultimo post
bombcat
Utente Èlite
- Messaggi
- 2,502
- Reazioni
- 278
- Punteggio
- 118
Si si grazie ... Ho visto... Da cellulare mi fa i doppi post
- - - Updated - - -
eccolo ->
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 20/11/2012 11:53:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112012-24289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000378F781, 0xFFFFF8800B5BBD10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
On Tue 20/11/2012 11:53:23 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: 0x3B (0xC0000005, 0xFFFFF8000378F781, 0xFFFFF8800B5BBD10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
On Tue 23/10/2012 16:43:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102312-12339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x66725045, 0x2, 0x1, 0xFFFFFA8009CE31A0)
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 that cannot be identified at this time.
On Tue 23/10/2012 16:13:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102312-16894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003743D3F, 0xFFFFF88002E48AB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
On Mon 24/09/2012 12:42:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092412-12511-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80066C3060, 0xFFFFF80000BA2748, 0xFFFFFA800B02C010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
On Sat 22/09/2012 14:16:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-12152-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800948E028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.
On Sun 16/09/2012 16:40:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-15802-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF800032D71C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800109B974)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Conclusion
7 crash dumps have been found and analyzed.
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.
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 20/11/2012 11:53:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112012-24289-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000378F781, 0xFFFFF8800B5BBD10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
On Tue 20/11/2012 11:53:23 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: 0x3B (0xC0000005, 0xFFFFF8000378F781, 0xFFFFF8800B5BBD10, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
On Tue 23/10/2012 16:43:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102312-12339-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x66725045, 0x2, 0x1, 0xFFFFFA8009CE31A0)
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 that cannot be identified at this time.
On Tue 23/10/2012 16:13:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102312-16894-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003743D3F, 0xFFFFF88002E48AB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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.
On Mon 24/09/2012 12:42:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092412-12511-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80066C3060, 0xFFFFF80000BA2748, 0xFFFFFA800B02C010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.
On Sat 22/09/2012 14:16:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-12152-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800948E028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.
On Sun 16/09/2012 16:40:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-15802-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF800032D71C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800109B974)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
A third party driver was identified as the probable root cause of this system error.
Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Conclusion
7 crash dumps have been found and analyzed.
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.
- - - Updated - - -
ora @Federico83 ?
- - - Updated - - -
allora i BSOD erano dovuti al vcore su unigine heaven quando arrivava a meta' del 2' giro (non in bench)
e il problema con i programmi che smettevano di funzionare... alzato il vcore da 1.24 1.25 per i 4.5ghz ho risolto (ho notato che a 4.2 non me lo faceva mentre a 4.5 si allora ho dedotto fosse il vcore)
per l'altro problema non mi fa salvare sul desktop non saprei... XD
Ultima modifica:
- Messaggi
- 35,404
- Reazioni
- 6,305
- Punteggio
- 246
quale altro problema hai che non me lo ricordo... sto a diventà vecchio
bombcat
Utente Èlite
- Messaggi
- 2,502
- Reazioni
- 278
- Punteggio
- 118
- Messaggi
- 35,404
- Reazioni
- 6,305
- Punteggio
- 246
cambia il percorso di salvataggio te lo dice proprio li
bombcat
Utente Èlite
- Messaggi
- 2,502
- Reazioni
- 278
- Punteggio
- 118
me lo fa solo col desktop quando provo a salvarci ...
per altri percorsi non lo fa...
ma ogni tanto qualcosa la salvo sul desk per comodita'
Pubblicità