BikerBill64
Terugkerende gebruiker
- Lid geworden
- 5 mei 2008
- Berichten
- 1.996
Eeh, is je Microsoft Office 2007 wel legitiem? (Los van je windows dus)
Bekijk de onderstaande video om te zien hoe je onze site als een web app op je startscherm installeert.
Opmerking: Deze functie is mogelijk niet beschikbaar in sommige browsers.
Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.0.6002.2.2.0.768.3
Landinstelling-id: 1043
Aanvullende informatie over dit probleem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 93894EFC
BCP3: A7DC5AE0
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Bestanden die helpen bij het beschrijven van het probleem:
C:\Windows\Minidump\Mini060414-01.dmp
C:\Users\Gebruiker\AppData\Local\temp\WER-113303-0.sysdata.xml
C:\Users\Gebruiker\AppData\Local\temp\WER864E.tmp.version.txt
Lees onze privacyverklaring:
[url]http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0413[/url]
System Information (local)
--------------------------------------------------------------------------------
computer name: PC_VAN_GEBRUIKE
windows version: Windows Vista Service Pack 2, 6.0, build: 6002
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 1071005696 total
VM: 2147352576, free: 1981685760
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 4-6-2014 7:53:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini060414-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x94EFC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF93894EFC, 0xFFFFFFFFA7DC5AE0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Multi-User Win32-stuurprogramma
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.
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 Wed 4-6-2014 7:53:46 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!KfLowerIrql+0x64)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF93894EFC, 0xFFFFFFFFA7DC5AE0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
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 kernel-mode application 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 that cannot be identified at this time.
On Sun 18-5-2014 20:47:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini051814-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x19E400)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF931FE400, 0xFFFFFFFF999AAB50, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Multi-User Win32-stuurprogramma
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.
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. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
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.
We gebruiken essentiële cookies om deze site te laten werken, en optionele cookies om de ervaring te verbeteren.