Julyyyyyy
23-10-2011, 15:49
Poco fa mentre stavo mettendo dei file dal pc al cellulare con il cavo USB mi è uscita la schermata blu e ho dovuto riavviare il sistema!
Ho analizzato con Whocrashed e il risultato:
System Information (local)
computer name: 452E162DD0634A9
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Athlon(tm) 64 Processor 3700+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 1073070080 total
VM: 2147352576, free: 2044284928
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 2011-10-23 14.22.35 your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102311-01.dmp
This was probably caused by the following module: Unknown (0x5C0EB5A8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8057203D, 0xFFFFFFFFB6F93ACC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 2011-10-23 14.22.35 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntoskrnl.exe (nt!KeBugCheckEx+0x1B)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF8057203D, 0xFFFFFFFFB6F93ACC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft(R) Windows(R) Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a kernel-mode application 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 which cannot be identified at this time.
Conclusion
2 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:
unknown
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.
Credo che sia colpa del mio cell, giusto?
E che dovrei fare?
:)
Ho analizzato con Whocrashed e il risultato:
System Information (local)
computer name: 452E162DD0634A9
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Athlon(tm) 64 Processor 3700+ AMD586, level: 15
1 logical processors, active mask: 1
RAM: 1073070080 total
VM: 2147352576, free: 2044284928
Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 2011-10-23 14.22.35 your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102311-01.dmp
This was probably caused by the following module: Unknown (0x5C0EB5A8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8057203D, 0xFFFFFFFFB6F93ACC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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.
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: Unknown .
Google query: Unknown KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 2011-10-23 14.22.35 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntoskrnl.exe (nt!KeBugCheckEx+0x1B)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF8057203D, 0xFFFFFFFFB6F93ACC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft(R) Windows(R) Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a kernel-mode application 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 which cannot be identified at this time.
Conclusion
2 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:
unknown
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.
Credo che sia colpa del mio cell, giusto?
E che dovrei fare?
:)