morpheus85
21-01-2010, 09:44
Ieri sera mentre stavo provando la demo di crashday (noto solo ora la coincidenza.. :asd:) dopo circa 1 ora il pc si è riavviato, non sono riuscito a leggere nulla dalla shermata blu.. cmq l'errore è il seguente:
Codice errore 1000007f, parametro1 00000008, parametro2 80042000, parametro3 00000000, parametro4 00000000.
analizzando il minidump con whocrashed esce fuori:
Welcome to WhoCrashed Home Edition 2.00
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though 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, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------
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. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 20/01/2010 22.46.15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
Dump file: C:\WINDOWS\Minidump\Mini012010-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
Ho letto qualcosa in merito a quella applicazione.. spero veramente non sia la ram :rolleyes:
Codice errore 1000007f, parametro1 00000008, parametro2 80042000, parametro3 00000000, parametro4 00000000.
analizzando il minidump con whocrashed esce fuori:
Welcome to WhoCrashed Home Edition 2.00
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though 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, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report ...
--------------------------------------------------------------------------------
Home Edition notice
--------------------------------------------------------------------------------
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. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
--------------------------------------------------------------------------------
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 20/01/2010 22.46.15 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000007F (0x8, 0x80042000, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
Dump file: C:\WINDOWS\Minidump\Mini012010-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.
Ho letto qualcosa in merito a quella applicazione.. spero veramente non sia la ram :rolleyes: