PC Crash
- Onderwerp starter kayvp
- Startdatum
- Status
Lange Pier
Inventaris
- Lid geworden
- 30 dec 2005
- Berichten
- 31.659
http://www.malwareinfo.nl/automatisch-opnieuw-opstarten-bij-een-bsod-uitschakelen/
Zo schakel het automatisch opnieuw opstarten uit.
Of met Whocrashed even kijken.
http://www.resplendence.com/whocrashed
Zo schakel het automatisch opnieuw opstarten uit.
Of met Whocrashed even kijken.
http://www.resplendence.com/whocrashed
Er staat windows 7 op mijn computer
processor : Intel(R) Core(TM) i5-2500K CPU @3.3GHz 3.3GHz
RAM: 4,00 GB
32 bitsbesturing systeem
NVIDIA GeForce GTX 560 TI
Ik speel alleen League of Legends. Bij het opstarten en afsluiten van deze game crasht de pc vaker.
Als ik dat automatisch opnieuw opstarten uitschakel crasht hij dan niet meer? is dit dan niet slecht voor mijn computer?
Dit geeft hij aan bij WhoCrashed
computer name: KAY
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8P67 PRO REV 3.1
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3742277632 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050315-18922-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sun 5-4-2015 23:08:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040615-20451-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x37DE)
Bugcheck code: 0x50 (0xFFFFFFFFFE5CC5BC, 0x0, 0xFFFFFFFF821937DE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 2 third party drivers have 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:
kerneld.sys
hal.sys
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 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.
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050315-18922-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sun 5-4-2015 23:08:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040615-20451-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x37DE)
Bugcheck code: 0x50 (0xFFFFFFFFFE5CC5BC, 0x0, 0xFFFFFFFF821937DE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 2 third party drivers have 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:
kerneld.sys
hal.sys
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 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.
processor : Intel(R) Core(TM) i5-2500K CPU @3.3GHz 3.3GHz
RAM: 4,00 GB
32 bitsbesturing systeem
NVIDIA GeForce GTX 560 TI
Ik speel alleen League of Legends. Bij het opstarten en afsluiten van deze game crasht de pc vaker.
Als ik dat automatisch opnieuw opstarten uitschakel crasht hij dan niet meer? is dit dan niet slecht voor mijn computer?
Dit geeft hij aan bij WhoCrashed
computer name: KAY
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8P67 PRO REV 3.1
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3742277632 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050315-18922-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sun 5-4-2015 23:08:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040615-20451-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x37DE)
Bugcheck code: 0x50 (0xFFFFFFFFFE5CC5BC, 0x0, 0xFFFFFFFF821937DE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 2 third party drivers have 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:
kerneld.sys
hal.sys
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 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.
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050315-18922-01.dmp
This was probably caused by the following module: kerneld.sys (kerneld+0xAD8)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 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: kerneld.sys .
Google query: kerneld.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sun 3-5-2015 15:10:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFFA4B95AD8, 0xFFFFFFFF8A9F1904, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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: hal.sys .
Google query: hal.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Sun 5-4-2015 23:08:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040615-20451-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x37DE)
Bugcheck code: 0x50 (0xFFFFFFFFFE5CC5BC, 0x0, 0xFFFFFFFF821937DE, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 2 third party drivers have 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:
kerneld.sys
hal.sys
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 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.
Laatst bewerkt:
Lange Pier
Inventaris
- Lid geworden
- 30 dec 2005
- Berichten
- 31.659
Dat opnieuw opstarten uitschakelen geeft een BSOD die in beeld blijft.
En je hebt het alleen bij die game?
En je hebt het alleen bij die game?
Lange Pier
Inventaris
- Lid geworden
- 30 dec 2005
- Berichten
- 31.659
Welke versie driver wordt er gebruikt voor de nVida?
Indien een oudere, die eerst deïnstalleren, rebooten en installeren, je kunt een groot beeld krijgen die je eerst even op een hogere resolutie kan zetten om alles te zien.
http://www.nvidia.com/download/driverResults.aspx/83818/en-us
Om mee te beginnen want het zijn algemene stopfouten, veel over te vinden i.c.m. Lol maar geen oplossingen.
Indien een oudere, die eerst deïnstalleren, rebooten en installeren, je kunt een groot beeld krijgen die je eerst even op een hogere resolutie kan zetten om alles te zien.
http://www.nvidia.com/download/driverResults.aspx/83818/en-us
Om mee te beginnen want het zijn algemene stopfouten, veel over te vinden i.c.m. Lol maar geen oplossingen.
- Status
