Elke keer blauw error scherm als ik mijn pc opstart
- Onderwerp starter Skander
- Startdatum
- Status
Harry Snor
Giga Honourable Senior Member †
- Lid geworden
- 1 mrt 2004
- Berichten
- 12.409
Hoi !
Download en installeer WhoCrashed: http://www.resplendence.com/downloads
Laat het programma draaien, en plaats een printscreen ervan hier, dan kunnen we gericht proberen te helpen.
Greetz,
Harry.
Download en installeer WhoCrashed: http://www.resplendence.com/downloads
Laat het programma draaien, en plaats een printscreen ervan hier, dan kunnen we gericht proberen te helpen.
Greetz,
Harry.
On Sun 8/7/2011 9:48:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080711-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AB617)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800031C1617, 0xFFFFF880033AE728, 0xFFFFF880033ADF80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 8/7/2011 9:48:20 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: acpi.sys (ACPI+0x22D46)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800031C1617, 0xFFFFF880033AE728, 0xFFFFF880033ADF80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\acpi.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: ACPI-stuurprogramma voor NT
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 which cannot be identified at this time.
On Sun 8/7/2011 9:35:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080711-29484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xC5 (0x24, 0x2, 0x1, 0xFFFFF800031B9B32)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 8/6/2011 3:59:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-32947-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x8, 0x1C)
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 which cannot be identified at this time.
On Sat 8/6/2011 6:33:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-28126-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xAD5FC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000046, 0xFFFFF800030C95FC, 0xFFFFF880033B3DB0, 0xFFFFF880033B3E50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 8/4/2011 7:15:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080411-21684-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x1187)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000096, 0xFFFFF8800453E187, 0xFFFFF880033A62E8, 0xFFFFF880033A5B40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a system thread 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.
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 which cannot be identified at this time.
crash dump file: C:\Windows\Minidump\080711-23556-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AB617)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800031C1617, 0xFFFFF880033AE728, 0xFFFFF880033ADF80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 8/7/2011 9:48:20 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: acpi.sys (ACPI+0x22D46)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF800031C1617, 0xFFFFF880033AE728, 0xFFFFF880033ADF80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\acpi.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: ACPI-stuurprogramma voor NT
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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 which cannot be identified at this time.
On Sun 8/7/2011 9:35:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080711-29484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xC5 (0x24, 0x2, 0x1, 0xFFFFF800031B9B32)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid 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. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 8/6/2011 3:59:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-32947-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x8, 0x1C)
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 which cannot be identified at this time.
On Sat 8/6/2011 6:33:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080611-28126-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xAD5FC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000046, 0xFFFFF800030C95FC, 0xFFFFF880033B3DB0, 0xFFFFF880033B3E50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 8/4/2011 7:15:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080411-21684-01.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x1187)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000096, 0xFFFFF8800453E187, 0xFFFFF880033A62E8, 0xFFFFF880033A5B40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a system thread 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.
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 which cannot be identified at this time.
Laatst bewerkt door een moderator:
Harry Snor
Giga Honourable Senior Member †
- Lid geworden
- 1 mrt 2004
- Berichten
- 12.409
Hoi !
Duik in je bios en kijk of ACPI is ingeschakeld (enabled).
Ga naar de Medion -site, trommel je gegevens in en kijk of er software-update's voor je PC en graka zijn.
http://www.medion.com/nl/service/download/
Greetz,
Harry.
Duik in je bios en kijk of ACPI is ingeschakeld (enabled).
Ga naar de Medion -site, trommel je gegevens in en kijk of er software-update's voor je PC en graka zijn.
http://www.medion.com/nl/service/download/
Greetz,
Harry.
Harry Snor
Giga Honourable Senior Member †
- Lid geworden
- 1 mrt 2004
- Berichten
- 12.409
Hoi !
Kijk het eerst even aan, mogelijk is je probleem hiermee al verholpen.
Greetz,
Harry.
Kijk het eerst even aan, mogelijk is je probleem hiermee al verholpen.
Greetz,
Harry.
- Status
Nieuwste berichten
-
WiFi adapter werkt niet meer geen Wifi verbinding mogelijk.
- Nieuwste: Lange Pier
-
-
