Pagina 1 van 1

BSOD bij Sluimerstand activeren

Geplaatst: 14 mei 2014 19:58
door vando
Wanneer ik mijn laptop met Windows 7 Home Edition met sluimerstand wil afsluiten dan verschijnt er af en toe een BSOD, dit is de melding die ik na een herstart krijg:

Probleemhandtekening:
Gebeurtenisnaam van probleem: BlueScreen
Versie van besturingssysteem: 6.1.7601.2.1.0.768.3
Landinstelling-id: 1043

Aanvullende informatie over dit probleem:
BCCode: 1000007e
BCP1: FFFFFFFF80000003
BCP2: FFFFF80003EC19D0
BCP3: FFFFF88002677538
BCP4: FFFFF88002676D90
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1



WhoCrashed geeft het volgende resultaat:

computer name: VANDO-HP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: HP G62 Notebook PC , Hewlett-Packard, 143C
CPU: AuthenticAMD AMD Athlon(tm) II P340 Dual-Core Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4021186560 total
VM: 2147352576, free: 1949904896

On Mon 12-5-2014 18:05:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051214-136329-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x18790)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80003EC19D0, 0xFFFFF88002677538, 0xFFFFF88002676D90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Kernel Mode Driver Framework-runtime
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 that cannot be identified at this time.



On Mon 12-5-2014 18:05:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x18790)
Bugcheck code: 0x7E (0xFFFFFFFF80000003, 0xFFFFF80003EC19D0, 0xFFFFF88002677538, 0xFFFFF88002676D90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Kernel Mode Driver Framework-runtime
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 that cannot be identified at this time.



On Mon 12-5-2014 17:50:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051214-249086-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x18790)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80003EB69D0, 0xFFFFF8800A42C538, 0xFFFFF8800A42BD90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Kernel Mode Driver Framework-runtime
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 that cannot be identified at this time.



On Fri 9-5-2014 17:03:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050914-38547-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x18790)
Bugcheck code: 0x1000007E (0xFFFFFFFF80000003, 0xFFFFF80003E759D0, 0xFFFFF8800AEE8538, 0xFFFFF8800AEE7D90)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Besturingssysteem Microsoft® Windows®
company: Microsoft Corporation
description: Kernel Mode Driver Framework-runtime
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 that cannot be identified at this time.


IK ben heel benieuwd of iemand een eenvoudige oplossing heeft voor dit probleem.
Het gebeurt alleen wanneer ik naar de sluimerstand ga, normaal uitzetten en aanzetten geeft geen probleem.

Mvg

Vando

Re: BSOD bij Sluimerstand activeren

Geplaatst: 14 mei 2014 22:10
door OB1
Doe eens het volgende:

- ga naar start en tik daar "CMD" in, vervolgens rechtsklik -> "Als administrator uitvoeren"
Kopieer en plak het volgende in dat venster, en druk op enter.

Code: Selecteer alles

SFC /scannow
Vertel wat de melding is op het einde van de scan, het beste gebruik je de computer niet tijdens de scan.

Re: BSOD bij Sluimerstand activeren

Geplaatst: 15 mei 2014 19:16
door vando
"Er zijn geen schendingen van de integriteit gevonden" is wat er als resultaat uit de SFC /Scannow komt.

Re: BSOD bij Sluimerstand activeren

Geplaatst: 15 mei 2014 20:07
door OB1
Waarschijnlijk een probleem met het geheugen.
Test dat eens met MemTest: http://www.memtest86.com